Electronic license plate processing method and device
By linking user accounts with vehicle factory identification and using electronic license plates, the problem of time-consuming license plate allocation process is solved, and convenient and efficient management of license plate services is achieved.
Patent Information
- Application Number
- CN202311802243.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-08-12
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2041-08-12
AI Technical Summary
The current license plate allocation process is time-consuming and involves multiple management departments and agencies, resulting in a cumbersome and inefficient process for users to obtain license plates after purchasing a vehicle.
By linking user accounts with vehicle factory identification, users are certified as vehicle owners. The digital electronic license plate display method enables online processing of license plate application, sharing, modification and use, reducing offline processes and improving service efficiency.
This has made license plate services more convenient and efficient, reducing the time and human resources wasted by users during the license plate application process and improving the convenience and efficiency of license plate management.
Smart Images

Figure CN117786183B_ABST
Abstract
Description
[0001] This application is a divisional application of Chinese invention patent application filed on August 12, 2021, with application number CN202110925546.8 and title "Electronic License Plate Processing Method and Apparatus". Technical Field
[0002] This document relates to the field of data processing technology, and in particular to an electronic license plate processing method and apparatus. Background Technology
[0003] With continuous economic development and an increasing number of cars on the road, license plates remain the unique identifier for vehicles in traffic information management. They serve as vehicle identification, revealing important information such as the province, city, and county of origin, as well as the owner's information. After purchasing a vehicle, users must wait for the vehicle management department to allocate a license plate. This process involves multiple management departments, vehicle sellers, and vehicle buyers, making it quite complex. Therefore, providing efficient and convenient license plate services has become a key concern for users. Summary of the Invention
[0004] This specification provides one or more embodiments of an electronic license plate processing method. The electronic license plate processing method includes: obtaining a license plate service request submitted by a user terminal; querying a vehicle manufacturing identifier associated with an account identifier carried in the license plate service request; performing license plate service processing based on the vehicle manufacturing identifier and service request information carried in the license plate service request to obtain electronic license plate information; and if a display instruction for the electronic license plate information is detected, sending the electronic license plate information to a target vehicle; and displaying it on a license plate display component configured on the target vehicle.
[0005] This specification provides one or more embodiments of another electronic license plate processing method, including: determining the service type selected by the user, and submitting a license plate service request to a server based on the service type; obtaining electronic license plate information issued by the server after performing license plate service processing; detecting the user's display instruction for the electronic license plate information and forwarding it to the server; and displaying the electronic license plate information on a license plate display component configured on the target vehicle according to the electronic license plate information.
[0006] This specification provides one or more embodiments of an electronic license plate processing device, comprising: a request acquisition module configured to acquire a license plate service request submitted by a user terminal; an identifier query module configured to query a vehicle manufacturing identifier associated with an account identifier carried in the license plate service request; an information acquisition module configured to perform license plate service processing based on the vehicle manufacturing identifier and service request information carried in the license plate service request to obtain electronic license plate information; and an instruction detection module configured to send the electronic license plate information to a target vehicle if a display instruction for the electronic license plate information is detected, and to display it on a license plate display component configured on the target vehicle.
[0007] This specification provides one or more embodiments of another electronic license plate processing device, comprising: a request submission module configured to determine the service type selected by a user and submit a license plate service request to a server based on the service type; an information acquisition module configured to acquire electronic license plate information issued by the server after performing license plate service processing; and an instruction detection module configured to detect the user's display instruction for the electronic license plate information and forward it to the server; so as to display the electronic license plate information on a license plate display component configured on the target vehicle.
[0008] This specification provides one or more embodiments of an electronic license plate processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire a license plate service request submitted by a user terminal; query a vehicle manufacturing identifier associated with an account identifier carried in the license plate service request; perform license plate service processing based on the vehicle manufacturing identifier and service request information carried in the license plate service request to obtain electronic license plate information; and if a display instruction for the electronic license plate information is detected, send the electronic license plate information to a target vehicle; and display it on a license plate display component configured on the target vehicle.
[0009] This specification provides one or more embodiments of another electronic license plate processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: determine a service type selected by a user and submit a license plate service request to a server based on the service type; acquire electronic license plate information issued by the server after performing license plate service processing; detect a user's display instruction for the electronic license plate information and forward it to the server; and display the electronic license plate information on a license plate display component configured on a target vehicle according to the electronic license plate information.
[0010] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions that, when executed, implement the following process: obtaining a license plate service request submitted by a user terminal; querying a vehicle manufacturing identifier associated with an account identifier carried in the license plate service request; performing license plate service processing based on the vehicle manufacturing identifier and service request information carried in the license plate service request to obtain electronic license plate information; and, if a display instruction for the electronic license plate information is detected, sending the electronic license plate information to a target vehicle for display on a license plate display component configured on the target vehicle.
[0011] This specification provides one or more embodiments of another storage medium for storing computer-executable instructions that, when executed, perform the following process: determining a service type selected by a user and submitting a license plate service request to a server based on the service type; obtaining electronic license plate information issued by the server after processing the license plate service; detecting the user's display instruction for the electronic license plate information and forwarding it to the server; and displaying the electronic license plate information on a license plate display component configured on the target vehicle according to the electronic license plate information. Attached Figure Description
[0012] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0013] Figure 1 A flowchart illustrating an electronic license plate processing method provided in one or more embodiments of this specification;
[0014] Figure 2 A flowchart illustrating an electronic license plate processing method applied to a license plate application scenario, provided for one or more embodiments of this specification;
[0015] Figure 3 A flowchart illustrating an electronic license plate processing method for license plate change scenarios, provided for one or more embodiments of this specification;
[0016] Figure 4 A flowchart illustrating another electronic license plate processing method provided in one or more embodiments of this specification;
[0017] Figure 5 A schematic diagram of an electronic license plate processing device provided for one or more embodiments of this specification;
[0018] Figure 6 A schematic diagram of another electronic license plate processing device provided in one or more embodiments of this specification;
[0019] Figure 7 A schematic diagram of an electronic license plate processing device provided for one or more embodiments of this specification;
[0020] Figure 8 This is a schematic diagram of another electronic license plate processing device provided in one or more embodiments of this specification. Detailed Implementation
[0021] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.
[0022] This specification provides an example of an electronic license plate processing method:
[0023] Reference Figure 1 It shows a flowchart of an electronic license plate processing method provided in this embodiment, with reference to... Figure 2 It shows a flowchart of an electronic license plate processing method applied to a license plate application scenario provided in this embodiment, with reference to... Figure 3 The diagram illustrates a process flow chart of an electronic license plate processing method for license plate change scenarios provided in this embodiment.
[0024] Reference Figure 1 The electronic license plate processing method provided in this embodiment is applied to a server and specifically includes steps S102 to S108.
[0025] Step S102: Obtain the license plate service request submitted by the user terminal.
[0026] The electronic license plate processing method provided in this embodiment uses the vehicle's factory identification mark as the element for identifying the vehicle's uniqueness. The electronic license plate is displayed digitally through a license plate display component, replacing the original method of displaying license plates using metal materials. It also handles license plate services such as application, sharing, cancellation, modification, and use online. Specifically, by associating the vehicle's factory identification mark with the user's account identifier and authenticating the user as the vehicle owner, all subsequent license plate services can be accessed through the owner's account. The account's server is connected to a third-party platform, providing license plate services such as application, use, sharing, modification, and cancellation through data synchronization with the third-party platform. Furthermore, by connecting the server and the vehicle, electronic license plate information is synchronized in real time, thereby improving the convenience and efficiency of license plate services during the application, modification, and cancellation processes.
[0027] In this embodiment, the license plate service request includes at least one of the following: license plate application request, license plate change request, license plate sharing request, license plate usage request, and cancellation request. Specifically, the license plate service request may include all five of the above, or any one or more of the above five, and may also include other license plate service requests besides the above five. The license plate service request includes the user's account identifier, service type, and / or service request information corresponding to the service type; in addition, it also includes other information needed when providing license plate services. Optionally, if the license plate service request is a license plate sharing request, then the process of obtaining the license plate service request submitted by the user terminal is the process of obtaining the license plate sharing request submitted by the user terminal; the license plate sharing request carries the identifier of the license plate to be shared and the identifier of the account to be shared. The identifier of the license plate to be shared and the identifier of the account to be shared are the service request information corresponding to the license plate sharing request.
[0028] In practical applications, after purchasing a vehicle, users need to apply for a license plate from a third-party agency. After the agency allocates the license plate, it needs to produce it and then issue it to the user. This entire process is time-consuming, requiring users to visit multiple agencies offline, making it cumbersome. To address this, and to reduce the steps involved in license plate services and improve efficiency, the user's account is linked to the vehicle's factory identification document (VIN) when purchasing the vehicle, and the user is authenticated as the vehicle owner. Subsequently, the user can access license plate services through their account. The VIN includes a unique identifier for the vehicle, such as the Vehicle Identification Number (VIN). In one optional implementation of this embodiment, after purchasing the vehicle, the user's owner identity is authenticated using the following method:
[0029] Obtain the vehicle's factory identification number submitted by the user through the user terminal;
[0030] Establish the association between the vehicle's factory identification and the account identification;
[0031] Based on the aforementioned association, the user's identity as the owner of the vehicle to be certified corresponding to the vehicle's factory identification is verified, and if the verification is successful, the user is certified as the owner of the vehicle to be certified.
[0032] Specifically, the user terminal obtains the vehicle's factory identification number entered by the user and submits it to the server. After receiving the vehicle's factory identification number, the server establishes a link between the vehicle's factory identification number and the account identification number. After establishing the link, in order to effectively manage the vehicle, it is necessary to further verify the user's vehicle owner identity. During the process of verifying the user's vehicle owner identity, the vehicle seller assists in the verification to further confirm the validity of the vehicle owner's identity.
[0033] For example, if the vehicle factory identification submitted by the user's user terminal is obtained, an association is established between the vehicle factory identification and the account identification of the user account bound to the user terminal. After the association is established, the vehicle dealer's identification and the vehicle seller are obtained by interacting with the user's user terminal. A verification reminder is sent to the vehicle dealer's user terminal so that the vehicle dealer can verify the user's vehicle owner identity. If a confirmation instruction is obtained from the vehicle dealer's user terminal, the user is certified as the owner of the vehicle corresponding to the vehicle factory identification.
[0034] In addition, during the process of verifying the user's vehicle owner identity, the user's vehicle factory identification and account identification can be submitted through the user terminal of the certified vehicle seller to further verify the user's vehicle owner identity.
[0035] For example, after a user purchases a vehicle from a certified vehicle seller, the seller submits the vehicle's factory identification and the user's account identification through the user's terminal. After receiving the vehicle's factory identification and the account identification, the server sends a confirmation reminder to the user's terminal bound to the account identification based on the vehicle seller's identity and the vehicle's factory identification. The server then performs biometric identification on the user and establishes an association between the account identification and the vehicle's factory identification if the identification is successful. Based on this association, the server authenticates the user as the vehicle owner.
[0036] In practical applications, third-party platforms manage license plate services and vehicle-related fees (toll fees and fines). Therefore, in this embodiment, after authenticating a user as a vehicle owner, the vehicle's factory identification and owner information are synchronized with the third-party platform. The third-party platform refers to the platform that provides license plate services or manages vehicle-related fees.
[0037] Based on this, in one optional implementation of this embodiment, after authenticating the user as the vehicle owner, the following operations are performed:
[0038] Based on the account identifier, read the user's user information;
[0039] The association and the user information are sent to a third-party platform so that the third-party platform can store the association and the user information.
[0040] It should be noted that user information is, to a certain extent, considered user privacy. Accessing user information and synchronizing it with third-party platforms requires prior authorization from the user to ensure user privacy and security.
[0041] In practice, it connects with a third-party platform to establish a link between the user's account identifier and the vehicle's factory identifier. After the user is certified as the vehicle owner, the vehicle owner's user information is synchronized with the third-party platform. The user can then apply for license plate services through the account corresponding to the account identifier.
[0042] Step S104: Query the vehicle manufacturing identifier that is associated with the account identifier carried in the license plate service request.
[0043] In this embodiment, by establishing an association between a user's account identifier and the vehicle's factory identifier, the user is authenticated as the vehicle owner. In the stored association, the associated vehicle factory identifier can be queried based on the account identifier that submitted the license plate service request.
[0044] In practice, after authenticating their vehicle owner identity, users apply for license plate services using the account corresponding to their account identifier. During the application process, users submit a license plate service request through their user terminal. After receiving the request, the system queries the vehicle's factory identification number associated with the account identifier, based on the account identifier carried in the request. Furthermore, the license plate service request includes the service type and corresponding service request information; the specific service request information varies depending on the service type included in the application.
[0045] Step S106: Based on the vehicle's factory identification and the service request information carried in the license plate service request, perform license plate service processing to obtain electronic license plate information.
[0046] The electronic license plate information includes the electronic license plate color and the electronic license plate identifier, wherein the electronic license plate color includes the electronic base plate color and the electronic identifier color. The service request information includes information that the user needs to submit for each service type. For example, if the license plate service request is a license plate application request, the service request information includes the vehicle type and the application geographical area. As another example, if the license plate service request is a license plate change request, the service request information includes the target geographical area. It should be noted that the service request information corresponding to each service type is determined based on the information required during the license plate service processing, and this embodiment does not impose any limitations on this.
[0047] In this embodiment, the electronic license plate includes digital license plates displayed using LEDs (light-emitting diodes) and / or digital license plates displayed using AR (Augmented Reality) technology. In addition, it may also include digital license plates displayed using other visualization methods, which are not limited in this embodiment.
[0048] In this embodiment, different methods are used in the license plate service processing for different license plate service requests. The license plate service processing for different license plate service requests will be described in detail below.
[0049] (1) License plate application request
[0050] In one optional implementation of this embodiment, if a license plate application request containing the vehicle type and geographical region is obtained from a user's terminal after purchasing a vehicle and becoming a vehicle owner, the vehicle's factory identification number associated with the account identifier carried in the license plate application request is queried. After retrieving the vehicle's factory identification number, electronic license plate information that is mapped to the vehicle's factory identification number is obtained in the following manner:
[0051] The vehicle's factory identification, application identification, vehicle type and application geographic area carried in the license plate application request are transmitted to the service interface provided by the third-party platform, and the license plate information that is mapped to the vehicle's factory identification is obtained from the service interface.
[0052] Specifically, the vehicle's factory identification, application identification, vehicle type, and application geographic area are transmitted to the service interface of the third-party platform. After receiving the vehicle's factory identification, application identification, vehicle type, and application geographic area, the third-party platform determines the service type based on the application identification, and determines the electronic license plate color and electronic license plate identifier based on the vehicle type and application geographic area. The electronic license plate color and electronic license plate identifier are used as electronic license plate information, and a mapping relationship between the electronic license plate information and the vehicle's factory identification is established. The server obtains the electronic license plate information that is mapped to the vehicle's factory identification, which is returned by the service interface.
[0053] For example, upon receiving a license plate application request submitted by a user through a user terminal, where the vehicle type in the application request is a new energy vehicle and the geographical application area is City A in Province A, the system queries the vehicle's factory identification associated with the account identifier corresponding to the account that submitted the license plate application request. The system then transmits the retrieved vehicle factory identification, new energy vehicle information, application identification, and Province A identification information to the service interface provided by the license plate management platform. The platform determines the electronic license plate identifier based on the abbreviation of Province A and the initial and final codes of City A. For new energy vehicles, the platform determines the electronic base plate color to be green and the electronic identification color to be black. The electronic license plate identifier, electronic base plate color, and electronic identification color are used as the electronic license plate information. After establishing the mapping relationship between the electronic license plate information and the vehicle factory identification, the electronic license plate information and this mapping relationship are transmitted back to the server through the service interface.
[0054] It should be noted that during this process, the user submits a license plate application command through the license plate application control configured in the access page of the license plate service subroutine. After the user terminal detects that the user has triggered the license plate application control, it determines that the license plate service type is license plate application, queries the information collection template corresponding to the license plate application service, collects the corresponding service request information from the user based on the information identifier in the information collection template, and submits the license plate application request to the server based on the license plate application service type and the collected corresponding service request information.
[0055] Furthermore, in an optional implementation of this embodiment, after receiving electronic license plate information that maps to the vehicle's factory identification, the electronic license plate information is sent to the user terminal so that the user terminal can display the electronic license plate information. During the display of the electronic license plate, the user terminal can display the corresponding parameters for the electronic base plate color, electronic license plate identifier, and electronic identifier color, for example, the user terminal can display "License plate color: green; License plate identifier: xxxx; Identifier color: black". In addition, the user terminal can also render and display an example of the electronic license plate based on the electronic base plate color, electronic license plate identifier, and electronic identifier color.
[0056] (2) License plate change request
[0057] In practical applications, when a vehicle leaves the country, it is necessary to assign a license plate corresponding to the target geographical area to the vehicle based on the license plate allocation conditions of the target geographical area. During the allocation process, it is necessary to connect with multiple third-party institutions offline, which is time-consuming and inefficient.
[0058] In one optional implementation of this embodiment, the user submits a license plate change request through a user terminal. If the user terminal detects that the user has triggered the license plate change control, it displays a target geographic area collection reminder to allow the user to enter the target geographic area. After obtaining the target geographic area entered by the user, the server submits a license plate change request to the server based on the target geographic area and the license plate change service type. After querying the vehicle's factory identification, the server obtains the electronic license plate information in the following way:
[0059] The vehicle's factory identification, change identification, and the target geographical area carried in the license plate change request are passed to the service interface, and the electronic license plate information corresponding to the target geographical area is obtained from the service interface.
[0060] Specifically, the vehicle's factory identification, modification identification, and target geographic area are transmitted to the service interface of a third-party platform. The third-party platform first determines the service type based on the modification identification, and then determines the corresponding electronic license plate information based on the target geographic area. The target geographic area refers to an overseas region or a region with an inconsistent license plate system.
[0061] For example, if a user needs to leave China, they can trigger a license plate change control on their user terminal. After detecting that the license plate change control has been triggered, the user terminal determines the license plate change service request and displays an information collection reminder to the user based on the information required for the license plate change, so that the user can enter the regional identifier of the overseas region. The user terminal obtains the regional identifier of the overseas region entered by the user and submits a license plate change request to the server based on the regional identifier and the change type. After receiving the license plate change request, the server sends the queried vehicle manufacturing identifier, change type, and regional identifier of the overseas region to the third-party platform, so that the third-party platform can determine the corresponding electronic license plate information of the overseas region according to the license plate system of the overseas region.
[0062] Furthermore, in one optional implementation of this embodiment, after obtaining the electronic license plate information provided by the third-party platform, the electronic license plate information is sent to the user terminal. If the user wants to leave the country, they need to apply for the corresponding electronic license plate information in advance. When leaving the country, the user submits a display command for the electronic license plate information through the user terminal. If a display command for the electronic license plate is detected in the target geographical area, the user's location is queried according to the display command to determine whether the user's location meets the display conditions of the electronic license plate information, that is, whether the user's location is in a foreign area or near the boundary line. If so, a mapping relationship between the electronic license plate information and the vehicle's factory identification is established, the mapping relationship is synchronized to the third party, and the electronic license plate information is sent to the target vehicle.
[0063] (3) License plate sharing request
[0064] In practical implementation, to alleviate the pressure of license plate issuance, if a user has two vehicles, the two vehicles can share one license plate. To further alleviate the pressure of license plate issuance, users can share their license plates with other users when they are not using their vehicles. Corresponding to the license plate sharing request obtained above, in an optional implementation method provided in this embodiment, electronic license plate information is obtained in the following way:
[0065] Query the vehicle manufacturing identification of the vehicle to be shared that is associated with the account identification to be shared;
[0066] Remove the mapping relationship between the vehicle's factory identification and the license plate identification to be shared;
[0067] The electronic license plate information is determined based on the vehicle type of the vehicle to be shared and the license plate identifier of the vehicle to be shared, and a mapping relationship is established between the vehicle factory identifier of the vehicle to be shared and the electronic license plate information.
[0068] The mapping relationship between the vehicle's factory identification and the electronic license plate information of the vehicle to be shared is synchronized to a third-party platform.
[0069] Specifically, when a user shares their license plate identifier with another user, the system retrieves the vehicle's factory identifier based on the user identifier carried in the license plate sharing request. It then searches for the factory identifier of the vehicle associated with that user. First, it removes the mapping between the license plate identifier in the sharing request and the user's vehicle factory identifier. Next, based on the vehicle type and the license plate identifier, it determines the electronic license plate information and establishes a mapping between the electronic license plate information and the vehicle's factory identifier. To improve the effectiveness of the third-party platform's management of the electronic license plate information, the mapping relationship is synchronized and stored on the third-party platform after it is established.
[0070] For example, user A shares a license plate identifier of xxxx with user B. The system obtains the license plate identifier submitted by user A and user B's account identifier. First, it queries the vehicle's factory identifier associated with user B's account identifier and reads that the vehicle type corresponding to this factory identifier is a small vehicle. Therefore, it determines that user B's electronic license plate information has a blue background color, a white electronic identifier color, and an electronic license plate identifier of xxxx. Then, it removes the mapping relationship between user A's vehicle factory identifier and the electronic license plate information with electronic license plate identifier xxxx. Next, it establishes a mapping relationship between the electronic license plate information with a blue background color, a white electronic identifier color, and electronic license plate identifier xxxx, and user B's vehicle factory identifier. This mapping relationship is then synchronized to the license plate management platform.
[0071] It should be noted that during the license plate sharing process, the mapping relationship between the license plate identifier to be shared and the vehicle's factory identifier can be removed, and a mapping relationship between the electronic license plate information and the vehicle's factory identifier can be established before synchronizing the mapping relationship with the third-party platform. Alternatively, the license plate identifier to be shared, the vehicle's factory identifier, and the vehicle's factory identifier can be transmitted to the third-party platform so that the third-party platform can perform the license plate sharing process and obtain the electronic license plate information returned by the third-party platform that has a mapping relationship with the vehicle's factory identifier.
[0072] Furthermore, after determining the electronic license plate information, the electronic license plate information is sent to the user terminal of the user to be shared. In one optional implementation of this embodiment, the electronic license plate information is sent to the user terminal bound to the account identifier to be shared, so that the user to be shared can trigger a command to display the electronic license plate information.
[0073] (4) Request for license plate usage
[0074] In practical implementation, if a user's historical license plate list stores multiple license plate information, the user can select the corresponding license plate information according to the usage scenario. For example, if a user applies for an overseas electronic license plate but uses a domestic electronic license plate within the country, they can submit a request to use the overseas electronic license plate when leaving the country, improving the efficiency of license plate conversion when the user travels abroad multiple times. In an optional implementation provided in this embodiment, if the license plate service request submitted by the user is a license plate usage request, the license plate service is processed in the following manner:
[0075] Read the target electronic license plate information carried in the license plate usage request, and establish a mapping relationship between the vehicle's factory identification and the target electronic license plate information;
[0076] If the mapping is successfully established, the target electronic license plate information will be identified as the electronic license plate information, and the mapping relationship will be synchronized to the third-party platform.
[0077] or,
[0078] Read the target electronic license plate information carried in the license plate usage request, and pass the vehicle factory identification, the target electronic license plate information, and the usage identification to the service interface provided by the third-party platform;
[0079] Obtain the mapping result returned by the service interface after establishing the mapping relationship between the target electronic license plate information and the vehicle factory identification;
[0080] Based on the mapping result, the target electronic license plate information is determined as the electronic license plate information.
[0081] Specifically, the server can convert the electronic license plate mapped to the vehicle's factory identification and synchronize the conversion result to a third-party platform. Alternatively, the third-party platform can convert the mapping relationship and then send the mapping result back to the server.
[0082] The above describes the specific processes for different types of license plate service requests in license plate service processing. It should be noted that, to improve user awareness of the license plate service processing, after obtaining the electronic license plate information, it is sent to the user's terminal so that the user is aware of the electronic license plate information. Specifically, in the processes of license plate sharing, license plate change, and license plate use, after obtaining the electronic license plate information, it is sent to the user terminal bound to the account identifier corresponding to the vehicle's factory identification, i.e., to the user who initiated the license plate service request; in the process of license plate sharing, after obtaining the electronic license plate information, it is sent to the user terminal of the user to whom the license plate is to be shared.
[0083] The description of the service type for license plate service requests in this embodiment is merely illustrative. The service types corresponding to other license plate service requests are described above during the license plate service processing process, and will not be repeated here.
[0084] Step S108: If a display command for the electronic license plate information is detected, the electronic license plate information is sent to the target vehicle.
[0085] In this embodiment, if a display command for electronic license plate information is detected, the electronic license plate information is sent to the target vehicle to enable the license plate display component configured on the target vehicle to display the information. Optionally, the license plate display component includes at least one of the following: the license plate display component configured on the target vehicle at the time of vehicle manufacture, or a license plate display component after replacing the license plate material configured on the target vehicle; wherein the license plate display component is configured on the vehicle body area corresponding to the license plate material. Furthermore, the license plate display component can also be configured on other external visual areas of the vehicle body, such as LED display components configured on the vehicle body. The target vehicle includes the vehicle corresponding to the vehicle's factory identification mark, and also includes the vehicle corresponding to the vehicle's factory identification mark of the vehicle to be shared.
[0086] In specific implementation, corresponding to the different types of license plate service requests mentioned above, in order to improve the user's perception of the processing results of the license plate service, the obtained electronic license plate information is sent to the corresponding user terminal. When in use, the user terminal receiving the electronic license plate information can submit a display command for the electronic license plate information. The display command for the electronic license plate information is submitted by the user terminal receiving the electronic license plate information. In this embodiment, during license plate sharing, license plate change, and license plate usage, after obtaining the electronic license plate information, it is sent to the user terminal bound to the account identifier corresponding to the vehicle's factory identification. Based on this, if the user terminal submits the display command, the electronic license plate information is sent to the vehicle corresponding to the vehicle's factory identification. During license plate sharing, after obtaining the electronic license plate information, it is sent to the user terminal of the user to be shared. If the user terminal bound to the account identifier to be shared submits a display command for the electronic license plate information, the electronic license plate information is sent to the vehicle to be shared.
[0087] After sending the electronic license plate information to the target vehicle, the target vehicle displays the electronic license plate information through a configured license plate display component. Since the electronic license plate information is composed of data, and the electronic license plate is displayed based on the attributes recorded in it, in order to improve the visualization effect and effectiveness of the displayed electronic license plate, in an optional implementation method provided in this embodiment, the target vehicle displays the electronic license plate in the following manner:
[0088] The electronic license plate identifier carried in the electronic license plate information is displayed according to the color of the electronic license plate carried in the electronic license plate information;
[0089] or,
[0090] The color of the electronic license plate is determined based on the vehicle type, and the electronic license plate identifier carried in the electronic license plate information is displayed according to the determined electronic license plate color.
[0091] Specifically, the electronic license plate identifier can be displayed according to the color of the electronic base plate and the color of the electronic identifier carried in the electronic license plate information. Alternatively, the color of the electronic base plate and the color of the electronic identifier can be determined first according to the vehicle type of the target vehicle, and then the electronic connector identifier carried in the electronic license plate information can be displayed according to the determined electronic base plate and electronic identifier colors.
[0092] In practice, users can submit a license plate cancellation request for a specific license plate identifier. After receiving the request, the license plate cancellation process is initiated, thus saving users time and manpower during the license plate cancellation process. In one optional implementation method provided in this embodiment, license plate cancellation is performed in the following way:
[0093] Obtain the license plate cancellation request submitted by the user terminal;
[0094] The license plate identifier to be cancelled and the cancellation identifier carried in the license plate cancellation request are passed to the service interface provided by the third-party platform;
[0095] Obtain the cancellation result returned after the service interface performs the cancellation process, and send the cancellation result to the user terminal.
[0096] In addition, to improve the effectiveness of vehicle management for users, in one optional implementation of this embodiment, after connecting with a third-party platform, the toll bill information during passage can be processed in the following way: First, based on the toll bill information synchronized by the third-party platform, query the target vehicle's factory identification that has a mapping relationship with the target license plate identification carried in the toll bill information; then determine the target account identification that is associated with the target vehicle's factory identification; finally, send the toll bill information to the user terminal corresponding to the target account identification so that payment can be processed through the user terminal corresponding to the target account identification. This allows users to view their vehicle's toll bill in a timely manner, avoiding the accumulation of fees due to users not promptly going to the third-party institution to pay. It should be noted that after license plate sharing, the toll bill information generated by the license plate is sent to the account associated with the vehicle's factory identification that has a mapping relationship with the license plate.
[0097] In this embodiment, the vehicle's VIN number is used as a unique identifier for the vehicle. By digitizing the display method of the license plate, the manpower and resources required for applying for and using metal license plates are saved, thus improving the efficiency of license plate services. Specifically, for vehicles not yet manufactured, a license plate display component is configured at the factory. For vehicles already manufactured, the area for installing the metal license plate can be modified into a digital license plate display component. After purchasing the vehicle, the user's account identifier is associated with the vehicle's VIN number, and the user is authenticated as the vehicle owner. Subsequently, the entire lifecycle management of the license plate is achieved through the account corresponding to this account identifier.
[0098] The following description uses the application of an electronic license plate processing method provided in this embodiment in a license plate application scenario as an example to further illustrate the electronic license plate processing method provided in this embodiment. (See also...) Figure 2 The electronic license plate processing method applied to license plate application scenarios includes the following steps.
[0099] Step S204: Establish the association between the vehicle VIN number and the account identifier that submitted the vehicle VIN number.
[0100] Prior to this, the user terminal obtains the vehicle VIN number entered by the user and submits it to the server.
[0101] Step S206: Verify the user's identity based on the association relationship, and send an association result reminder to the user's terminal if the verification is successful.
[0102] Subsequently, when the user terminal detects that the license plate application control has been triggered, it displays an application information collection reminder. The license plate application control is configured on the access page of the license plate service subroutine. It obtains the vehicle type and the area identifier of the application geographical area entered by the user. Based on the vehicle type and area identifier, it generates a license plate application request and submits it to the server.
[0103] Step S214: Read the account identifier carried in the license plate application request and query the vehicle VIN number associated with the account identifier.
[0104] Step S216: Input the vehicle VIN number, vehicle type and area identifier into the service interface provided by the third-party platform, and obtain the electronic license plate information that is mapped to the vehicle VIN number returned by the service interface.
[0105] The electronic license plate information includes the color and logo of the electronic license plate.
[0106] Step S218: Send the electronic license plate information to the user terminal.
[0107] Subsequently, based on the user terminal's instruction to display the electronic license plate information, the electronic license plate information is sent to the vehicle corresponding to the vehicle's VIN number for display through the configured license plate display component.
[0108] The following description uses the application of an electronic license plate processing method provided in this embodiment in a license plate change scenario as an example to further illustrate the electronic license plate processing method provided in this embodiment. (See also...) Figure 3 The electronic license plate processing method applied to license plate change scenarios includes the following steps.
[0109] Step S302: If the license plate change control is detected to be triggered, a change information collection reminder is displayed.
[0110] Step S304: Obtain the region identifier of the overseas region entered by the user.
[0111] Step S306: Generate a license plate change request based on the area identifier and submit it to the server.
[0112] Step S308: Read the account identifier carried in the license plate change request.
[0113] Step S310: Query the vehicle VIN number that is associated with the account identifier.
[0114] Step S312: Input the vehicle VIN number and area identifier into the service interface provided by the third-party platform, and obtain the electronic license plate information corresponding to the overseas area returned by the service interface.
[0115] The electronic license plate information includes the color and logo of the electronic license plate.
[0116] Step S314: Send electronic license plate information to the user terminal.
[0117] Step S316: Based on the user terminal's instruction to display electronic license plate information, establish a mapping relationship between electronic license plate information and vehicle VIN number.
[0118] Subsequently, electronic license plate information is sent to the vehicle corresponding to the vehicle's VIN number for display through the configured license plate display component, and this mapping relationship is synchronized to a third-party platform.
[0119] In summary, the electronic license plate processing method provided in this embodiment first obtains the license plate service request submitted by the user terminal, then queries the vehicle manufacturing identifier associated with the account identifier carried in the license plate service request, and then performs license plate service processing based on the vehicle manufacturing identifier and the service request information carried in the license plate service request to obtain electronic license plate information. If a display instruction for electronic license plate information is detected, the electronic license plate information is sent to the target vehicle; and the license plate is displayed using the license plate display component configured on the target vehicle. This digital display method reduces the resource waste caused by metal license plates and saves efficiency in license plate service processing by providing license plate services online.
[0120] Another embodiment of the electronic license plate processing method provided in this manual:
[0121] Reference Figure 4 It shows a flowchart of an electronic license plate processing method provided in this embodiment, with reference to... Figure 2 It shows a flowchart of an electronic license plate processing method applied to a license plate application scenario provided in this embodiment, with reference to... Figure 3 The diagram illustrates a process flow chart of an electronic license plate processing method for license plate change scenarios provided in this embodiment.
[0122] Reference Figure 4 The electronic license plate processing method provided in this embodiment is applied to a user terminal and specifically includes steps S402 to S406.
[0123] The electronic license plate processing method provided in this embodiment is executed by a user terminal. Another embodiment of the electronic license plate processing method provided in this specification is executed by a server. The electronic license plate processing method applied to a user terminal provided in this embodiment cooperates with the electronic license plate processing method applied to a server provided in the above method embodiments during execution. Therefore, please refer to the corresponding content of the above method embodiments when reading this embodiment.
[0124] Step S402: Determine the service type selected by the user, and submit a license plate service request to the server based on the service type.
[0125] The electronic license plate processing method provided in this embodiment uses the vehicle's factory identification mark as a factor to identify the vehicle's uniqueness. The license plate is displayed digitally in the license plate display area on the vehicle body. Application, sharing, cancellation, modification, and use of the electronic license plate are realized online. Specifically, after purchasing a vehicle, the user associates the vehicle's factory identification mark with their account identifier and authenticates themselves as the vehicle owner. All subsequent license plate services can be accessed through the account corresponding to the account identifier. The account's server is connected to a third-party platform, providing license plate management services such as application, use, sharing, modification, and cancellation through data synchronization with the third-party platform. Simultaneously, the server and vehicle are connected to synchronize electronic license plate information in real time, thereby improving the convenience and efficiency of license plate processing, modification, and cancellation.
[0126] In one optional implementation of this embodiment, the license plate service request includes at least one of the following: a license plate application request, a license plate change request, a license plate sharing request, a license plate usage request, and a cancellation request. The license plate service request includes the user's account identifier, service type, and / or service request information corresponding to the service type; in addition, it also includes other information required when providing license plate services. The service request information includes information that the user needs to submit for each service type. For example, if the license plate service request is a license plate application request, the service request information includes the vehicle type and the application geographical area. As another example, if the license plate service request is a license plate change request, the service request information includes the target geographical area. It should be noted that the service request information corresponding to each service type is determined based on the information required during the license plate service processing, and this embodiment does not impose any limitations on this.
[0127] In practice, after determining the service type, it is also necessary to collect the corresponding service request information. In one optional implementation method provided in this embodiment, during the process of determining the service type selected by the user and submitting a license plate service request to the server based on the service type, the following operations are performed:
[0128] Collect the service type, and collect service request information based on the service type;
[0129] The license plate service request is generated based on the service type and the service request information and submitted to the server.
[0130] A license plate service request is submitted to the server, enabling the server to process the license plate service based on the request, obtain electronic license plate information, and distribute it. In one optional implementation of this embodiment, the electronic license plate information is obtained in the following manner:
[0131] (1) Query the vehicle's factory identification that is associated with the account identification carried in the license plate service request.
[0132] In practice, after purchasing a car, users need to apply for a license plate from a third-party platform. After the third-party platform allocates the license plate, it needs to produce the license plate and then issue it to the user. The whole process is time-consuming and involves multiple platforms, making it quite complicated.
[0133] In practice, to streamline the process and improve efficiency of license plate services, users' accounts are linked to the vehicle's factory identification when purchasing a vehicle, and the user is authenticated as the vehicle owner. Subsequently, users can access license plate services through their user accounts. The vehicle's factory identification includes unique identifiers such as the vehicle's VIN number. After a user purchases a vehicle, the server authenticates the user's ownership identity using the following method:
[0134] Obtain the vehicle's factory identification number submitted by the user through the user terminal;
[0135] Establish the association between the vehicle's factory identification and the account identification;
[0136] Based on the aforementioned association, the user's identity as the owner of the vehicle to be certified corresponding to the vehicle's factory identification is verified, and if the verification is successful, the user is certified as the owner of the vehicle to be certified.
[0137] Specifically, the system retrieves the vehicle's factory identification number entered by the user and submits it to the server. Upon receiving the identification number, the server establishes a link between it and the account identifier. After establishing this link, to effectively manage the vehicle, further authentication of the user's owner identity is required. During this authentication process, the vehicle seller assists in verifying the owner's identity to further confirm its validity.
[0138] For example, if the server obtains the vehicle factory identification submitted by the user's user terminal, it establishes an association between the vehicle factory identification and the account identification of the user account bound to the user terminal. After the association is established, it obtains the vehicle dealer's identification and the vehicle seller by interacting with the user's user terminal, and sends a verification reminder to the vehicle dealer's user terminal so that the vehicle dealer can verify the user's vehicle owner identity. If the server obtains the confirmation instruction submitted by the vehicle dealer's user terminal, it will authenticate the user as the owner of the vehicle corresponding to the vehicle factory identification.
[0139] In addition, during the process of verifying the user's vehicle owner identity, the user's vehicle factory identification and account identification can be submitted through the user terminal of the certified vehicle seller to further verify the user's vehicle owner identity.
[0140] For example, after a user purchases a vehicle from a certified vehicle seller, the seller submits the vehicle's factory identification and the user's account identification through the user's terminal. After receiving the vehicle's factory identification and the account identification, the server sends a confirmation reminder to the user's terminal bound to the account identification based on the vehicle seller's identity and the vehicle's factory identification. The server then performs biometric identification on the user and establishes an association between the account identification and the vehicle's factory identification if the identification is successful. Based on this association, the server authenticates the user as the vehicle owner.
[0141] In practical applications, the license plate management platform manages license plate services and vehicle-related expenses. Therefore, in this embodiment, after authenticating the user as the vehicle owner, the vehicle's factory identification and owner information are synchronized with a third-party platform. The third-party platform refers to a platform that provides license plate services or manages vehicle-related expenses.
[0142] Based on this, after authenticating the user as the car owner, the server performs the following operations:
[0143] Based on the account identifier, read the user's user information;
[0144] The association and the user information are sent to a third-party platform so that the third-party platform can store the association and the user information.
[0145] It should be noted that user information is, to a certain extent, considered user privacy. Accessing user information and synchronizing it with third-party platforms requires prior authorization from the user to ensure user privacy and security.
[0146] In practice, the server is connected to a third-party platform. After establishing the association between the user's account identifier and the vehicle's factory identifier, and after the user is certified as the vehicle owner, the vehicle owner's user information is synchronized with the third-party platform. The user can then apply for license plate services through the account corresponding to the account identifier.
[0147] After authenticating their vehicle owner identity, users apply for license plate services using the account corresponding to their account identifier. During the application process, users submit a license plate service request to the server. Upon receiving the request, the server queries the vehicle's factory identification number associated with the account identifier, based on the account identifier carried in the request. The license plate service request also includes the service type and corresponding service request information; the specific service request information varies depending on the service type included in the application.
[0148] (2) Based on the vehicle's factory identification and the service request information carried in the license plate service request, perform license plate service processing to obtain the electronic license plate information.
[0149] The electronic license plate information includes the electronic license plate color and the electronic license plate identifier, wherein the electronic license plate color includes the electronic base plate color and the electronic identifier color. The service request information includes information that the user needs to submit for each service type. For example, if the license plate service request is a license plate application request, the service request information includes the vehicle type and the application geographical area. As another example, if the license plate service request is a license plate change request, the service request information includes the target geographical area. It should be noted that the service request information corresponding to each service type is determined based on the information required during the license plate service processing, and this embodiment does not impose any limitations on this.
[0150] Different methods are used in the license plate service processing for different license plate service requests. The following is a detailed explanation of the license plate service processing for different license plate service requests.
[0151] In the first optional implementation provided in this embodiment, if the server receives a license plate application request submitted by a user through a user terminal after the user has purchased a vehicle and authenticated as the vehicle owner, specifying the vehicle type and the geographical region of the application, the server queries the vehicle manufacturing identifier associated with the account identifier based on the account identifier carried in the license plate application request. After retrieving the vehicle manufacturing identifier, the server obtains the electronic license plate information that is mapped to the vehicle manufacturing identifier in the following manner:
[0152] The vehicle's factory identification, application identification, vehicle type and application geographic area carried in the license plate application request are transmitted to the service interface provided by the third-party platform, and the license plate information that is mapped to the vehicle's factory identification is obtained from the service interface.
[0153] Specifically, the vehicle's factory identification, application identification, vehicle type, and application geographic area are transmitted to the service interface of the third-party platform. After receiving the vehicle's factory identification, application identification, vehicle type, and application geographic area, the third-party platform determines the service type based on the application identification, and determines the electronic license plate color and electronic license plate identifier based on the vehicle type and application geographic area. The electronic license plate color and electronic license plate identifier are used as electronic license plate information, and a mapping relationship between the electronic license plate information and the vehicle's factory identification is established. The server obtains the electronic license plate information that is mapped to the vehicle's factory identification, which is returned by the service interface.
[0154] For example, upon receiving a license plate application request submitted by a user through a user terminal, where the vehicle type in the application request is a new energy vehicle and the geographical application area is City A in Province A, the system queries the vehicle's factory identification associated with the account identifier corresponding to the account that submitted the license plate application request. The system then transmits the retrieved vehicle factory identification, new energy vehicle information, application identification, and Province A identification information to the service interface provided by the license plate management platform. The platform determines the electronic license plate identifier based on the abbreviation of Province A and the initial and final codes of City A. For new energy vehicles, the platform determines the electronic base plate color to be green and the electronic identification color to be black. The electronic license plate identifier, electronic base plate color, and electronic identification color are used as the electronic license plate information. After establishing the mapping relationship between the electronic license plate information and the vehicle factory identification, the electronic license plate information and this mapping relationship are transmitted back to the server through the service interface.
[0155] It should be noted that during this process, after detecting that the user has triggered the license plate application control, the license plate service type is determined to be license plate application. The information collection template corresponding to the license plate application service is queried. Based on the information identifier in the information collection template, the corresponding service request information is collected from the user. Based on the license plate application service type and the collected corresponding service request information, the license plate application request is submitted to the server.
[0156] Furthermore, after receiving the electronic license plate information that maps to the vehicle's factory identification, the server sends the electronic license plate information to the user terminal so that the user terminal can display the electronic license plate information. During the display of the electronic license plate, the user terminal can display the corresponding parameters for the electronic background color, electronic license plate identifier, and electronic identifier color. For example, the user terminal can display "License plate color: green; License plate identifier: xxxx; Identifier color: black". In addition, the user terminal can also render and display an example of the electronic license plate based on the electronic background color, electronic license plate identifier, and electronic identifier color.
[0157] In practical applications, when a vehicle leaves the country, it needs to be assigned a license plate corresponding to the target geographical area based on the license plate allocation conditions of the target geographical area. This allocation process requires interaction with multiple third parties, which is time-consuming and inefficient. Therefore, in the second optional implementation provided in this embodiment, the user submits a license plate change request through a user terminal. If the user triggers the license plate change control, a target geographical area collection reminder is displayed to allow the user to enter the target geographical area. After obtaining the user-entered target geographical area, the server submits a license plate change request to the server based on the target geographical area and the license plate change service type. After querying the vehicle's factory identification, the server obtains the electronic license plate information in the following way:
[0158] The vehicle's factory identification, change identification, and the target geographical area carried in the license plate change request are passed to the service interface, and the electronic license plate information corresponding to the target geographical area is obtained from the service interface.
[0159] Specifically, the vehicle's factory identification, modification identification, and target geographic area are transmitted to the service interface of a third-party platform. The third-party platform first determines the service type based on the modification identification, and then determines the corresponding electronic license plate information based on the target geographic area. The target geographic area refers to an overseas region or a region with an inconsistent license plate system.
[0160] For example, if a user needs to leave China, they can trigger a license plate change control on their user terminal. After detecting that the license plate change control has been triggered, the user terminal determines the license plate change service request and displays an information collection reminder to the user based on the information required for the license plate change, so that the user can enter the overseas region. The user terminal obtains the region identifier of the overseas region entered by the user and submits a license plate change request to the server based on the region identifier and the change type. After receiving the license plate change request, the server sends the queried vehicle manufacturing identifier, change type, and overseas region identifier to the third-party platform, so that the third-party platform can determine the corresponding electronic license plate information for the overseas region according to the license plate system of the overseas region.
[0161] Furthermore, in one optional implementation of this embodiment, after obtaining the electronic license plate information provided by the third-party platform, the electronic license plate information is sent to the user terminal. If the user wants to leave the country, they need to apply for the corresponding electronic license plate information in advance. When leaving the country, the user submits a display command for the electronic license plate information through the user terminal. If a display command for the electronic license plate is detected in the target geographical area, the user's location is queried according to the display command to determine whether the user's location meets the display conditions of the electronic license plate information, that is, whether the user's location is in a foreign area or near the boundary line. If so, a mapping relationship between the electronic license plate information and the vehicle's factory identification is established, the mapping relationship is synchronized to the third party, and the electronic license plate information is sent to the target vehicle.
[0162] In the third optional implementation provided in this embodiment, in order to alleviate the pressure of license plate issuance, if a user has two vehicles, the two vehicles can share one license plate. To further alleviate the pressure of license plate issuance, users can share their license plates with other users when they are not using the vehicle. Corresponding to the license plate sharing request obtained above, the server obtains the electronic license plate information in the following way:
[0163] Query the vehicle manufacturing identification of the vehicle to be shared that is associated with the account identification to be shared;
[0164] Remove the mapping relationship between the vehicle's factory identification and the license plate identification to be shared;
[0165] The electronic license plate information is determined based on the vehicle type of the vehicle to be shared and the license plate identifier of the vehicle to be shared, and a mapping relationship is established between the vehicle factory identifier of the vehicle to be shared and the electronic license plate information.
[0166] The mapping relationship between the vehicle's factory identification and the electronic license plate information of the vehicle to be shared is synchronized to a third-party platform.
[0167] Specifically, when a user shares their license plate identifier with another user, the server retrieves the vehicle's factory identifier and, based on the user's identifier carried in the license plate sharing request, queries the factory identifier of the vehicle associated with that user. First, the mapping between the license plate identifier to be shared and the user's vehicle's factory identifier is removed. Then, based on the vehicle type and the license plate identifier, the electronic license plate information is determined, and a mapping between the electronic license plate information and the vehicle's factory identifier is established. To improve the effectiveness of the third-party platform's management of electronic license plate information, the mapping relationship is synchronized and stored on the third-party platform after it is established.
[0168] For example, user A shares a license plate identifier of xxxx with user B. The server obtains the license plate identifier submitted by user A and user B's account identifier. First, it queries the vehicle manufacturing identifier associated with user B's account identifier and reads that the vehicle type corresponding to the vehicle manufacturing identifier is a small vehicle. Then, it determines that the electronic plate color of user B's electronic license plate information is blue, the electronic identifier color is white, and the electronic license plate identifier is xxxx. Next, it removes the mapping relationship between user A's vehicle manufacturing identifier and the electronic license plate information with electronic license plate identifier xxxx, and then establishes a mapping relationship between the electronic license plate information with electronic plate color of blue, electronic identifier color of white, and electronic license plate identifier xxxx and user B's vehicle manufacturing identifier. This mapping relationship is then synchronized to the license plate management platform.
[0169] It should be noted that during the license plate sharing process, the server may either de-map the license plate identifier to be shared with the vehicle's factory identifier, establish a mapping relationship between the electronic license plate information and the vehicle's factory identifier, and then synchronize the mapping relationship with the third-party platform; or it may transmit the license plate identifier to be shared, the vehicle's factory identifier, and the vehicle's factory identifier to the third-party platform so that the third-party platform can perform the license plate sharing process and obtain the electronic license plate information returned by the third-party platform that has a mapping relationship with the vehicle's factory identifier.
[0170] Furthermore, after determining the electronic license plate information, the server sends the electronic license plate information to the user terminal of the user to be shared, and the server sends the electronic license plate information to the user terminal bound to the user's account identifier. This allows the user to trigger a command to display the electronic license plate information.
[0171] In the fourth optional implementation provided in this embodiment, if a user's historical license plate list stores multiple license plate information, the user can select the corresponding license plate information according to the specific usage scenario. For example, if a user applies for an overseas electronic license plate and uses a domestic electronic license plate within the country, when the user needs to leave the country, they can submit a request to use the overseas electronic license plate, improving the efficiency of license plate conversion when the user travels abroad multiple times. If the submitted license plate service request is a license plate usage request, the server processes the license plate service in the following way:
[0172] Read the target electronic license plate information carried in the license plate usage request, and establish a mapping relationship between the vehicle's factory identification and the target electronic license plate information;
[0173] If the mapping is successfully established, the target electronic license plate information will be identified as the electronic license plate information, and the mapping relationship will be synchronized to the third-party platform.
[0174] or,
[0175] Read the target electronic license plate information carried in the license plate usage request, and pass the vehicle factory identification, the target electronic license plate information, and the usage identification to the service interface provided by the third-party platform;
[0176] Obtain the mapping result returned by the service interface after establishing the mapping relationship between the target electronic license plate information and the vehicle factory identification;
[0177] Based on the mapping result, the target electronic license plate information is determined as the electronic license plate information.
[0178] Specifically, the server can convert the electronic license plate mapped to the vehicle's factory identification and synchronize the conversion result to a third-party platform. Alternatively, the third-party platform can convert the mapping relationship and then send the mapping result back to the server.
[0179] The above describes the specific processes for different types of license plate service requests in license plate service processing. It should be noted that, to improve user awareness of the license plate service processing, after obtaining the electronic license plate information, it is sent to the user's terminal so that the user is aware of the electronic license plate information. Specifically, in the processes of license plate sharing, license plate change, and license plate use, after obtaining the electronic license plate information, it is sent to the user terminal bound to the account identifier corresponding to the vehicle's factory identification, i.e., to the user who initiated the license plate service request; in the process of license plate sharing, after obtaining the electronic license plate information, it is sent to the user terminal of the user to whom the license plate is to be shared.
[0180] The description of the service type for license plate service requests in this embodiment is merely illustrative. The service types corresponding to other license plate service requests are described above during the license plate service processing process, and will not be repeated here.
[0181] Step S404: Obtain the electronic license plate information issued by the server after performing license plate service processing.
[0182] In practice, after obtaining the issued electronic license plate information, to enhance users' perception of this information, the electronic license plate display process can show the corresponding parameters for the electronic background color, electronic license plate identifier, and electronic identification color. For example, the user terminal can display "License plate color: green; License plate identifier: xxxx; Identifier color: black". Furthermore, the user terminal can also render and display an example of the electronic license plate based on the electronic background color, electronic license plate identifier, and electronic identification color.
[0183] Step S406: Detect the user's display instruction for the electronic license plate information and forward it to the server.
[0184] In practice, after forwarding the display instruction to the server, the server sends the electronic license plate information to the target vehicle so that it can be displayed on the license plate display component configured on the target vehicle according to the electronic license plate information.
[0185] In this embodiment, if the server detects a command to display electronic license plate information, it sends the electronic license plate information to the target vehicle, so that the license plate display component configured on the target vehicle can display it.
[0186] Optionally, the license plate display component configured on the target vehicle is displayed, including:
[0187] Electronic license plate display is performed using the license plate display component configured on the target vehicle at the time of vehicle manufacture;
[0188] or,
[0189] The target vehicle's license plate information is replaced by displaying the license plate information electronically through the license plate display component.
[0190] The license plate display component is configured with a vehicle body area corresponding to the license plate material.
[0191] Furthermore, the license plate display component can also be configured in other external visible areas of the vehicle body. The target vehicle includes the vehicle corresponding to its factory identification mark, and also the vehicle corresponding to the factory identification mark of the vehicle to be shared. In practical applications, after a user sells or scraps a vehicle, the license plate needs to be cancelled. Discarding or destroying metal license plates results in significant resource loss. Therefore, the electronic license plate provided in this embodiment can avoid resource loss.
[0192] In specific implementation, corresponding to the different types of license plate service requests mentioned above, in order to improve the user's perception of the processing results of the license plate service, the obtained electronic license plate information is sent to the corresponding user terminal. When in use, the user terminal receiving the electronic license plate information can submit a display command for the electronic license plate information. The display command for the electronic license plate information is submitted by the user terminal receiving the electronic license plate information. In this embodiment, during license plate sharing, license plate change, and license plate usage, after obtaining the electronic license plate information, it is sent to the user terminal bound to the account identifier corresponding to the vehicle's factory identification. Based on this, if the user terminal submits the display command, the electronic license plate information is sent to the vehicle corresponding to the vehicle's factory identification. During license plate sharing, after obtaining the electronic license plate information, it is sent to the user terminal of the user to be shared. If the user terminal bound to the account identifier to be shared submits a display command for the electronic license plate information, the electronic license plate information is sent to the vehicle to be shared.
[0193] After sending the electronic license plate information to the target vehicle, the target vehicle displays the electronic license plate information through a configured license plate display component. Since the electronic license plate information is composed of data, and the electronic license plate is displayed based on the attributes recorded in it, in order to improve the visualization and effectiveness of the displayed electronic license plate, this embodiment provides an optional implementation method in which the target vehicle displays the electronic license plate in the following manner:
[0194] The electronic license plate identifier carried in the electronic license plate information is displayed according to the color of the electronic license plate carried in the electronic license plate information;
[0195] or,
[0196] The color of the electronic license plate is determined based on the vehicle type, and the electronic license plate identifier carried in the electronic license plate information is displayed according to the determined electronic license plate color.
[0197] Specifically, the electronic license plate identifier can be displayed according to the color of the electronic license plate and / or the color of the electronic identifier carried in the electronic license plate information. Alternatively, the color of the electronic license plate and / or the color of the electronic identifier can be determined first according to the vehicle type of the target vehicle, and then the electronic connector identifier carried in the electronic license plate information can be displayed according to the determined color of the electronic license plate and / or the electronic identifier.
[0198] In practical applications, after a user sells or scraps a vehicle, the license plate needs to be cancelled. Discarding or destroying metal license plates results in a significant loss of resources. Therefore, electronic license plates can help avoid this loss.
[0199] In practice, users can submit a license plate cancellation request for the license plate identifier to be cancelled. Upon receiving the request, the server will process the cancellation, thus saving users time and manpower during the license plate cancellation process. The server processes license plate cancellation in the following ways:
[0200] Obtain the license plate cancellation request submitted by the user terminal;
[0201] The license plate identifier to be cancelled and the cancellation identifier carried in the license plate cancellation request are passed to the service interface provided by the third-party platform;
[0202] Obtain the cancellation result returned after the service interface performs the cancellation process, and send the cancellation result to the user terminal.
[0203] In addition, to improve the effectiveness of vehicle management for users, in this embodiment, after the server is connected to the third-party platform, it can also process the billing information during the passage process in the following way: First, based on the passage billing information synchronized by the third-party platform, the target vehicle's factory identification that has a mapping relationship with the target license plate identification carried in the passage billing information is queried; then, the target account identification that is associated with the target vehicle's factory identification is determined; finally, the passage billing information is sent to the user terminal corresponding to the target account identification so that payment can be processed through the user terminal corresponding to the target account identification. In this way, users can view the vehicle's passage bill in a timely manner, avoiding the accumulation of fees due to users not going to the third-party institution to pay in a timely manner. It should be noted that after license plate sharing, the passage billing information generated by the license plate is sent to the account associated with the vehicle's factory identification that has a mapping relationship with the license plate.
[0204] The following description uses the application of an electronic license plate processing method provided in this embodiment in a license plate application scenario as an example to further illustrate the electronic license plate processing method provided in this embodiment. (See also...) Figure 2 The electronic license plate processing method applied to license plate application scenarios includes the following steps.
[0205] Step S202: Obtain the vehicle VIN number entered by the user and submit it to the server.
[0206] Subsequently, the server establishes an association between the vehicle VIN number and the account identifier that submitted the vehicle VIN number; it verifies the user's identity based on the association, and sends an association result notification to the user's terminal if the verification is successful.
[0207] Step S208: If the license plate application control is detected to be triggered, display an application information collection reminder.
[0208] The license plate application control is configured on the access page of the license plate service subroutine.
[0209] Step S210: Obtain the vehicle type entered by the user and the area identifier of the applied geographical area.
[0210] Step S212: Generate a license plate application request based on vehicle type and area identifier and submit it to the server.
[0211] Subsequently, the system reads the account identifier carried in the license plate application request and queries the vehicle VIN number associated with the account identifier; it then passes the vehicle VIN number, vehicle type, and region identifier to the service interface provided by the third-party platform and obtains the electronic license plate information mapped to the vehicle VIN number returned by the service interface; it then sends the electronic license plate information to the user terminal; and finally, based on the display instruction submitted by the user terminal, it sends the electronic license plate information to the vehicle corresponding to the vehicle VIN number for display through the configured license plate display component.
[0212] The following description uses the application of an electronic license plate processing method provided in this embodiment in a license plate change scenario as an example to further illustrate the electronic license plate processing method provided in this embodiment. (See also...) Figure 3 The electronic license plate processing method applied to license plate change scenarios includes the following steps.
[0213] Step S302: If the license plate change control is detected to be triggered, a change information collection reminder is displayed.
[0214] Step S304: Obtain the region identifier of the overseas region entered by the user.
[0215] Step S306: Generate a license plate change request based on the area identifier and submit it to the server.
[0216] Subsequently, the system reads the account identifier carried in the license plate change request; queries the vehicle VIN number associated with the account identifier; transmits the vehicle VIN number and region identifier to the service interface provided by the third-party platform, and obtains the electronic license plate information corresponding to the overseas region returned by the service interface; sends the electronic license plate information to the user terminal; establishes a mapping relationship between the electronic license plate information and the vehicle VIN number based on the display instructions submitted by the user terminal; sends the electronic license plate information to the vehicle corresponding to the vehicle VIN number for display through the configured license plate display component, and synchronizes the mapping relationship with the third-party platform.
[0217] In summary, the electronic license plate processing method provided in this embodiment first determines the service type selected by the user and submits a license plate service request to the server based on the service type. Then, it obtains the electronic license plate information issued by the server after processing the license plate service. Finally, it detects the user's display instruction for the electronic license plate information and forwards it to the server. The license plate is then displayed on the license plate display component configured on the target vehicle according to the electronic license plate information. This digital display method reduces the resource waste caused by metal license plates and saves efficiency in license plate service processing by providing license plate services online.
[0218] This specification provides an embodiment of an electronic license plate processing device as follows:
[0219] In the above embodiments, an electronic license plate processing method is provided, and correspondingly, an electronic license plate processing device is also provided, which will be described below with reference to the accompanying drawings.
[0220] Reference Figure 5 The diagram shows a schematic of an electronic license plate processing device provided in this embodiment.
[0221] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.
[0222] This embodiment provides an electronic license plate processing device, including:
[0223] The request acquisition module 502 is configured to acquire license plate service requests submitted by the user terminal;
[0224] The identifier query module 504 is configured to query the vehicle manufacturing identifier that is associated with the account identifier carried in the license plate service request;
[0225] Information acquisition module 506 is configured to perform license plate service processing based on the vehicle factory identification and the service request information carried in the license plate service request, and obtain electronic license plate information.
[0226] The instruction detection module 508 is configured to send the electronic license plate information to the target vehicle if a display instruction for the electronic license plate information is detected, so that it can be displayed on the license plate display component configured on the target vehicle.
[0227] Another embodiment of the electronic license plate processing device provided in this manual is as follows:
[0228] In the above embodiments, an electronic license plate processing method is provided, and correspondingly, an electronic license plate processing device is also provided, which will be described below with reference to the accompanying drawings.
[0229] Reference Figure 6 The diagram shows a schematic of an electronic license plate processing device provided in this embodiment.
[0230] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.
[0231] This embodiment provides an electronic license plate processing device, including:
[0232] The request submission module 602 is configured to determine the service type selected by the user and submit a license plate service request to the server based on the service type.
[0233] The information acquisition module 604 is configured to acquire the electronic license plate information issued by the server after performing license plate service processing;
[0234] The instruction detection module 606 is configured to detect the user's instruction to display the electronic license plate information and forward it to the server; so as to display the electronic license plate information in the license plate display component configured on the target vehicle.
[0235] This manual provides an example of an electronic license plate processing device as follows:
[0236] Corresponding to the electronic license plate processing method described above, based on the same technical concept, one or more embodiments of this specification also provide an electronic license plate processing device, which is used to execute the electronic license plate processing method provided above. Figure 7 This is a schematic diagram of the structure of an electronic license plate processing device provided for one or more embodiments of this specification.
[0237] This embodiment provides an electronic license plate processing device, comprising:
[0238] like Figure 7As shown, electronic license plate processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 701 and memory 702, with memory 702 storing one or more application programs or data. Memory 702 can be temporary or persistent storage. The application programs stored in memory 702 may include one or more modules (not shown), each module including a series of computer-executable instructions from the electronic license plate processing device. Furthermore, processor 701 may be configured to communicate with memory 702, executing the series of computer-executable instructions stored in memory 702 on the electronic license plate processing device. The electronic license plate processing device may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input / output interfaces 705, one or more keyboards 706, etc.
[0239] In one specific embodiment, the electronic license plate processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the electronic license plate processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:
[0240] Obtain the license plate service request submitted by the user terminal;
[0241] Query the vehicle's factory identification number that is associated with the account identifier carried in the license plate service request;
[0242] Based on the vehicle's factory identification and the service request information carried in the license plate service request, license plate service processing is performed to obtain electronic license plate information;
[0243] If a display instruction for the electronic license plate information is detected, the electronic license plate information is sent to the target vehicle and displayed on the license plate display component configured on the target vehicle.
[0244] Another embodiment of the electronic license plate processing device provided in this manual is as follows:
[0245] Corresponding to the electronic license plate processing method described above, based on the same technical concept, one or more embodiments of this specification also provide an electronic license plate processing device, which is used to execute the electronic license plate processing method provided above. Figure 8 This is a schematic diagram of the structure of an electronic license plate processing device provided for one or more embodiments of this specification.
[0246] This embodiment provides an electronic license plate processing device, comprising:
[0247] like Figure 8 As shown, electronic license plate processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 801 and a memory 802, with the memory 802 storing one or more application programs or data. The memory 802 can be temporary or persistent storage. The application programs stored in the memory 802 may include one or more modules (not shown), each module including a series of computer-executable instructions from the electronic license plate processing device. Furthermore, the processor 801 may be configured to communicate with the memory 802, executing the series of computer-executable instructions stored in the memory 802 on the electronic license plate processing device. The electronic license plate processing device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.
[0248] In one specific embodiment, the electronic license plate processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the electronic license plate processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:
[0249] Determine the service type selected by the user, and submit a license plate service request to the server based on the service type;
[0250] Obtain the electronic license plate information issued by the server after performing license plate service processing;
[0251] The system detects the user's instruction to display the electronic license plate information and forwards it to the server; the electronic license plate information is then displayed on the license plate display component configured on the target vehicle.
[0252] This specification provides an example of a storage medium as follows:
[0253] In accordance with the above-described electronic license plate processing method, and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.
[0254] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:
[0255] Obtain the license plate service request submitted by the user terminal;
[0256] Query the vehicle's factory identification number that is associated with the account identifier carried in the license plate service request;
[0257] Based on the vehicle's factory identification and the service request information carried in the license plate service request, license plate service processing is performed to obtain electronic license plate information;
[0258] If a display instruction for the electronic license plate information is detected, the electronic license plate information is sent to the target vehicle and displayed on the license plate display component configured on the target vehicle.
[0259] It should be noted that the embodiments concerning the storage medium in this specification and the embodiments concerning the electronic license plate processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.
[0260] Another embodiment of the storage medium provided in this specification is as follows:
[0261] In accordance with the above-described electronic license plate processing method, and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.
[0262] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:
[0263] Determine the service type selected by the user, and submit a license plate service request to the server based on the service type;
[0264] Obtain the electronic license plate information issued by the server after performing license plate service processing;
[0265] The system detects the user's instruction to display the electronic license plate information and forwards it to the server; the electronic license plate information is then displayed on the license plate display component configured on the target vehicle.
[0266] It should be noted that the embodiments concerning the storage medium in this specification and the embodiments concerning the electronic license plate processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.
[0267] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.
[0268] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.
[0269] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.
[0270] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.
[0271] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.
[0272] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0273] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0274] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0275] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0276] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0277] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.
[0278] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.
[0279] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0280] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.
[0281] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.
[0282] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.
Claims
1. A method for processing electronic license plates, comprising: Obtain the license plate change request submitted by the user terminal; The license plate change request carries the user's account identifier, target geographic area, and change identifier; Query the vehicle's factory identification associated with the account identifier; The vehicle's factory identification, the change identification, and the target geographical area are transmitted to the service interface of a third-party platform. The electronic license plate information corresponding to the target geographical area is obtained from the service interface and sent to the user terminal. If a display instruction for the electronic license plate information is detected submitted by the user terminal, the electronic license plate information is sent to the target vehicle for display on the license plate display component configured on the target vehicle.
2. The electronic license plate processing method according to claim 1, wherein the license plate display component comprises at least one of the following: The license plate display component configured on the target vehicle when the vehicle leaves the factory, and the license plate display component after replacing the license plate material configured on the target vehicle; in, The license plate display component is configured in the vehicle body area corresponding to the license plate material.
3. The electronic license plate processing method according to claim 1, wherein the target vehicle displays the electronic license plate information in the following manner: The electronic license plate identifier carried in the electronic license plate information is displayed according to the color of the electronic license plate carried in the electronic license plate information; or, The color of the electronic license plate is determined based on the vehicle type, and the electronic license plate identifier carried in the electronic license plate information is displayed according to the determined electronic license plate color.
4. The electronic license plate processing method according to claim 1 further includes: Send the determined electronic license plate information to the user terminal; If the user terminal submits a display instruction for the specified electronic license plate information, the specified electronic license plate information is sent to the vehicle corresponding to the user's vehicle factory identification.
5. The electronic license plate processing method according to claim 1 further includes: Obtain the license plate cancellation request submitted by the user terminal; The license plate identifier to be cancelled and the cancellation identifier carried in the license plate cancellation request are passed to the service interface provided by the third-party platform; Obtain the cancellation result returned after the service interface performs the cancellation process, and send the cancellation result to the user terminal.
6. The electronic license plate processing method according to claim 1, before the step of obtaining the license plate change request submitted by the user terminal is executed, it further includes: Obtain the vehicle factory identification number submitted by the user through the user terminal; Establish the association between the user's vehicle factory identifier and the account identifier; Based on the aforementioned association, the user's identity as the owner of the vehicle to be certified corresponding to the user's vehicle factory identification is verified, and if the verification is successful, the user is certified as the owner of the vehicle to be certified.
7. The electronic license plate processing method according to claim 6, after the step of verifying the user's identity as the owner of the vehicle to be certified based on the association relationship, and certifying the user as the owner of the vehicle to be certified if the verification is successful, further includes: Based on the account identifier, read the user's user information; Send the aforementioned relationship and the user information to a third-party platform; This enables the third-party platform to store the association and the user information.
8. The electronic license plate processing method according to claim 1 further includes: Based on the toll bill information synchronized by the third-party platform, query the target vehicle's factory identification that has a mapping relationship with the target license plate identification carried in the toll bill information; Identify the target account identifier that is associated with the target vehicle's factory identification; The toll bill information is sent to the user terminal corresponding to the target account identifier so that payment can be processed through the user terminal corresponding to the target account identifier.
9. A method for processing electronic license plates, comprising: Determine the service type selected by the user, and submit a license plate change request to the server based on the service type; The license plate change request carries the user's account identifier, target geographic area, and change identifier; Obtain the electronic license plate information issued by the server after performing license plate service processing; The electronic license plate information is transmitted back to the server by the service interface of the third-party platform after the server transmits the vehicle's factory identification, the change identification, and the target geographical area. The electronic license plate information corresponds to the target geographical area. The system detects the user's instruction to display the electronic license plate information and forwards it to the server so that the electronic license plate information can be displayed on the license plate display component configured on the target vehicle.
10. The electronic license plate processing method according to claim 9, wherein the license plate is displayed on a license plate display component configured on the target vehicle, comprising: Electronic license plate display is performed using the license plate display component configured on the target vehicle at the time of vehicle manufacture; or, The target vehicle's license plate information is replaced by displaying the license plate information electronically through the license plate display component. The license plate display component is configured with a vehicle body area corresponding to the license plate material.
11. The electronic license plate processing method according to claim 9, wherein the target vehicle displays the electronic license plate information in the following manner: The electronic license plate identifier carried in the electronic license plate information is displayed according to the color of the electronic license plate carried in the electronic license plate information; or, The color of the electronic license plate is determined based on the vehicle type, and the electronic license plate identifier carried in the electronic license plate information is displayed according to the determined electronic license plate color.
12. An electronic license plate processing device, comprising: The request acquisition module is configured to acquire license plate change requests submitted by user terminals; The license plate change request carries the user's account identifier, target geographic area, and change identifier; The identifier query module is configured to query the vehicle manufacturing identifier associated with the account identifier; The information acquisition module is configured to transmit the vehicle's factory identification, the change identification, and the target geographical area to the service interface of a third-party platform, acquire the electronic license plate information corresponding to the target geographical area returned by the service interface, and send it to the user terminal. The instruction detection module is configured to send the electronic license plate information to the target vehicle if it detects an instruction submitted by the user terminal for displaying the electronic license plate information, so as to display it on the license plate display component configured on the target vehicle.
13. An electronic license plate processing device, comprising: The request submission module is configured to determine the service type selected by the user and submit a license plate change request to the server based on the service type. The license plate change request carries the user's account identifier, target geographic area, and change identifier; The information acquisition module is configured to acquire the electronic license plate information issued by the server after performing license plate service processing; The electronic license plate information is transmitted back to the server by the service interface of the third-party platform after the server transmits the vehicle's factory identification, the change identification, and the target geographical area. The electronic license plate information corresponds to the target geographical area. The instruction detection module is configured to detect the user's display instruction for the electronic license plate information and forward it to the server so as to display the electronic license plate information in the license plate display component configured on the target vehicle.
14. An electronic license plate processing device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: Obtain a license plate change request submitted by a user terminal; the license plate change request carries the user's account identifier, target geographical area, and change identifier; Query the vehicle's factory identification associated with the account identifier; The vehicle's factory identification, the change identification, and the target geographical area are transmitted to the service interface of a third-party platform. The electronic license plate information corresponding to the target geographical area is obtained from the service interface and sent to the user terminal. If a display instruction for the electronic license plate information is detected submitted by the user terminal, the electronic license plate information is sent to the target vehicle for display on the license plate display component configured on the target vehicle.
15. An electronic license plate processing device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: Determine the service type selected by the user, and submit a license plate change request to the server based on the service type; The license plate change request carries the user's account identifier, target geographic area, and change identifier; Obtain the electronic license plate information issued by the server after performing license plate service processing; The electronic license plate information is transmitted back to the server by the service interface of the third-party platform after the server transmits the vehicle's factory identification, the change identification, and the target geographical area. The electronic license plate information corresponds to the target geographical area. The system detects the user's instruction to display the electronic license plate information and forwards it to the server so that the electronic license plate information can be displayed on the license plate display component configured on the target vehicle.
16. A storage medium for storing computer-executable instructions, which, when executed, perform the following process: Obtain a license plate change request submitted by a user terminal; the license plate change request carries the user's account identifier, target geographical area, and change identifier; Query the vehicle's factory identification associated with the account identifier; The vehicle's factory identification, the change identification, and the target geographical area are transmitted to the service interface of a third-party platform. The electronic license plate information corresponding to the target geographical area is obtained from the service interface and sent to the user terminal. If a display instruction for the electronic license plate information is detected submitted by the user terminal, the electronic license plate information is sent to the target vehicle for display on the license plate display component configured on the target vehicle.
17. A storage medium for storing computer-executable instructions, which, when executed, perform the following process: Determine the service type selected by the user, and submit a license plate change request to the server based on the service type; The license plate change request carries the user's account identifier, target geographic area, and change identifier; Obtain the electronic license plate information issued by the server after performing license plate service processing; The electronic license plate information is transmitted back to the server by the service interface of the third-party platform after the server transmits the vehicle's factory identification, the change identification, and the target geographical area. The electronic license plate information corresponds to the target geographical area. The system detects the user's instruction to display the electronic license plate information and forwards it to the server so that the electronic license plate information can be displayed on the license plate display component configured on the target vehicle.
Citation Information
Patent Citations
Electronic license plate management system and method and remote management electronic license plate
CN111114461A
KR20200134963A
