Vehicle information processing method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a vehicle information processing method and device, equipment and a storage medium. The method comprises the steps that in response to a detected interface request of a user, a vehicle model information interface is presented, the vehicle model information interface comprises at least one first area associated with at least one vehicle type, and each first area comprises vehicle attribute information and vehicle availability information of the associated vehicle type, one or more first areas in the at least one first area respectively comprise a first interface element, and the first interface element indicates the to-be-stored state of the corresponding vehicle type; in response to the detected triggering of a target first interface element in the one or more first interface elements, determining a target vehicle type corresponding to the target first interface element as a collected vehicle type of the user; and switching the target first interface element into a second interface element, wherein the second interface element indicates that the target vehicle type is in a collected state.

Description

Technical Field

[0001] The exemplary embodiments disclosed herein generally relate to the field of computers, and particularly to methods, apparatus, devices, computer-readable storage media, and computer program products for vehicle information processing. Background Technology

[0002] With the development of computer and internet technology, platforms providing car rental, ride-hailing, and carpooling services are becoming increasingly widespread. Not only are there more and more car users, but also more and more vehicle providers, and the types of vehicles are becoming more diverse. If users could easily search for the type of vehicle they need, it would reduce the time and difficulty of selecting a car, thereby improving the overall car service experience. Summary of the Invention

[0003] In a first aspect of this disclosure, a method for processing vehicle information is provided. The method includes: in response to detecting a user's interface request, presenting a vehicle model information interface, the vehicle model information interface including at least one first region associated with at least one vehicle type, each first region including vehicle attribute information and vehicle availability information of the associated vehicle type, and one or more of the at least one first region respectively including a first interface element, the first interface element indicating a pending collection status of the corresponding vehicle type; in response to detecting a triggering of a target first interface element among the one or more first interface elements, determining a target vehicle type corresponding to the target first interface element as the user's collected vehicle model; and switching the target first interface element to a second interface element, the second interface element indicating that the target vehicle type is in a collected state.

[0004] In a second aspect of this disclosure, an apparatus for vehicle information processing is provided. The apparatus includes: an interface presentation module configured to present a vehicle model information interface in response to detecting a user's interface request. The vehicle model information interface includes at least one first region associated with at least one vehicle type. Each first region includes vehicle attribute information and vehicle availability information for the associated vehicle type. One or more of the at least one first region each include a first interface element, the first interface element indicating a vehicle type's pending collection status. A collection vehicle model determination module configured to determine a target vehicle type corresponding to the target first interface element as the user's collection vehicle model in response to detecting a triggering of a target first interface element among the one or more first interface elements. An interface element switching module configured to switch the target first interface element to a second interface element, the second interface element indicating that the target vehicle type is in a collected state.

[0005] In a third aspect of this disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the electronic device to perform the method of the first aspect.

[0006] In a fourth aspect of this disclosure, a computer-readable storage medium is provided. A computer program is stored on the medium, which, when executed by a processor, implements the method of the first aspect.

[0007] In a fifth aspect of this disclosure, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the method according to a first aspect of this disclosure.

[0008] It should be understood that the description in this section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0009] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0010] Figure 1 A schematic diagram of an example environment in which embodiments of the present disclosure can be implemented is shown;

[0011] Figure 2 A flowchart of a process for vehicle information processing according to some embodiments of the present disclosure is shown;

[0012] Figures 3A to 3F Schematic diagrams of example interfaces for applications according to some embodiments of the present disclosure are shown respectively;

[0013] Figure 4 A schematic structural block diagram of an apparatus for vehicle information processing according to some embodiments of the present disclosure is shown; and

[0014] Figure 5 A block diagram of an electronic device that can implement one or more embodiments of the present disclosure is shown. Detailed Implementation

[0015] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0016] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below.

[0017] In this document, unless explicitly stated otherwise, performing a step in response to A does not mean that the step is performed immediately after A, but may include one or more intermediate steps.

[0018] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition, use, storage or deletion of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0019] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, relevant users should be informed of the type, scope of use, and usage scenarios of the information involved in this disclosure through appropriate means in accordance with relevant laws and regulations, and authorization should be obtained from the relevant users. Among them, relevant users may include any type of rights holder, such as individuals, enterprises, and groups.

[0020] For example, in response to receiving an active request from a user, a prompt message is sent to the relevant user to clearly inform the user that the requested operation will require obtaining and using the user's information, thereby enabling the relevant user to choose whether to provide information to the software or hardware such as the electronic device, application, server, or storage medium that performs the operation of the technical solution disclosed herein based on the prompt message.

[0021] As an optional but non-restrictive implementation, in response to a user's active request, a prompt message can be sent to the user, such as a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide information to the electronic device.

[0022] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0023] As mentioned earlier, with the development of computer and internet technology, platforms providing car rental, ride-hailing, and carpooling services are becoming increasingly widespread. Not only are there more and more car users, but also more and more vehicle providers, and the types of vehicles are becoming more diverse. When users search for vehicles, they may encounter a large number of models and prices. Car service platforms typically have pre-set options (such as price, distance, rating, etc.) that can be used to sort vehicles so that users can prioritize viewing the most popular options. However, these methods are relatively inflexible and inaccurate, often failing to meet users' personalized needs. Therefore, providing users with an efficient and convenient way to select their desired vehicle type would reduce the time and difficulty of vehicle selection, thereby improving the overall car rental service experience.

[0024] In view of this, embodiments of the present disclosure provide an improved solution for vehicle information processing. In this solution, if a user request is detected, a vehicle model information interface is presented. The vehicle model information interface includes at least one first area associated with at least one vehicle type. Each first area includes vehicle attribute information and vehicle availability information for the associated vehicle type. One or more of the at least one first area includes a first interface element, which indicates the pending collection status of the corresponding vehicle type. If a triggering of a target first interface element among the one or more first interface elements is detected, the target vehicle type corresponding to the target first interface element is determined as the user's collected vehicle model. Furthermore, the target first interface element is switched to a second interface element, which indicates that the target vehicle type is in a collected state.

[0025] According to embodiments of this disclosure, users can save vehicle models (i.e., vehicle types) by triggering a first interface element. The saved models are then visualized by switching from the first interface element to a second interface element. This allows users to efficiently, conveniently, and accurately save the vehicles they need, facilitating subsequent vehicle selection, reducing the time and difficulty of selection, and ultimately improving the user experience of car-related services.

[0026] Example Environment

[0027] Figure 1A schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented is shown. In this example environment 100, an application 120 is installed on a terminal device 110. A user 140 can interact with the application 120 via the terminal device 110 and / or an attached device of the terminal device 110.

[0028] In embodiments of this disclosure, application 120 can be any suitable application associated with vehicle services, such as an application for vehicle rental, a ride-hailing application, a carpooling application, etc. Figure 1 In the environment, if application 120 is active, terminal device 110 can display the interface 150 of application 120. Interface 150 may include various interfaces that application 120 can provide, such as an interface for inputting car usage requirements, an interface for displaying vehicles, etc.

[0029] In some embodiments, terminal device 110 communicates with server device 130 to provide services to application 120. Terminal device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, terminal device 110 can also support any type of user-facing interface (such as "wearable" circuitry). Server device 130 can be various types of computing systems / servers capable of providing computing power, including but not limited to mainframes, edge computing nodes, computing devices in cloud environments, etc.

[0030] It should be understood that the structure and function of the various elements in environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of this disclosure.

[0031] Example process

[0032] The following description will continue with reference to the accompanying drawings, which will provide some exemplary embodiments of this disclosure.

[0033] Figure 2 A flowchart of a process 200 for vehicle information processing according to some embodiments of the present disclosure is shown. Process 200 may be implemented at a terminal device 110. In some embodiments, operations performed on the terminal device 110 may be performed with the assistance of a server device 130.

[0034] In box 210, if a user's interface request is detected, terminal device 110 presents a vehicle model information interface. In some embodiments, terminal device 110 has an application 120 installed, which can provide functions such as vehicle rental, ride-hailing, and carpooling. The vehicle model information interface can be an interface provided by application 120. In some embodiments, the vehicle model information interface can also be a website interface provided by a browser. For ease of discussion, the following description uses an application interface as an example.

[0035] This interface request is used to request terminal device 110 to display a vehicle model information interface. In practical applications, this vehicle model information interface can include various types of interfaces. Correspondingly, terminal device 110 can determine and detect the user's interface request in various application scenarios. As an example, terminal device 110 can respond to receiving a user's car-use request (such as a car rental request, a ride-hailing request, a carpooling request, etc.), determine and detect the user's interface request, and display a vehicle model information interface showing the vehicle type of the user's available vehicles. As another example, this vehicle model information interface can include the homepage of application 120. Terminal device 110 can respond to the launch of application 120, determine and receive an interface request, and display the homepage of application 120. As yet another example, this vehicle model information interface can include a recommendation interface of application 120. Terminal device 110 can respond to the user triggering a recommendation link, determine and receive an interface request, and display a recommendation interface.

[0036] The vehicle model information interface includes at least one first area associated with at least one vehicle type. The vehicle type (also referred to as the model number) can be categorized from different dimensions, such as by one or more of the following dimensions: vehicle manufacturer, model number, powertrain (e.g., engine type, displacement, transmission, drive type), vehicle size, number of seats, safety features, appearance, and economy (e.g., fuel consumption, emission standards). As an example, terminal device 110 can determine the vehicle type by "manufacturer" and "model number." That is, if multiple vehicles belong to the same "manufacturer" and the same "model number," terminal device 110 can determine that the multiple vehicles belong to the same vehicle type. Of course, the above-described vehicle type categorization method is merely exemplary, and the embodiments of this disclosure do not impose specific limitations in this regard.

[0037] In some embodiments, the at least one vehicle type can be a vehicle type capable of meeting the user's transportation needs. Specifically, the user can initiate a transportation request through terminal device 110 or an attached device of terminal device 110. If terminal device 110 detects the user's transportation request, determines the corresponding transportation needs, and then determines at least one vehicle type that meets the transportation needs. Each vehicle type may include at least one available vehicle, that is, a vehicle capable of providing transportation services such as car rental, ride-hailing, and carpooling to the user. Subsequently, terminal device 110 can display a vehicle model information interface. The transportation request here may include, but is not limited to, car rental requests, ride-hailing requests, carpooling requests, etc.

[0038] To better understand the example implementation, the following description will refer to the example interface of the application. Figures 3A to 3F Schematic diagrams of example interfaces 300A to 300F (also referred to simply as examples 300A to 300F) according to some embodiments of the present disclosure are shown. It should be understood that the interfaces shown in the drawings are merely examples, and various interface designs may actually exist. The various graphic elements in the interface may have different arrangements and different visual representations, one or more elements may be omitted or replaced, and one or more other elements may also be present. The embodiments of the present disclosure are not limited in this respect.

[0039] like Figure 3A and Figure 3B As shown, Example 300A illustrates an example of the query interface of Application 120, and Example 300B illustrates an example of the vehicle information interface of Application 120. Terminal device 110 can respond to a triggering of a vehicle usage option for Application 120 by presenting the query interface shown in Example 300A. Example 300A includes input fields 301, 302, and 304, options 303, 305, and 306, and a confirmation control 307. Terminal device 110 can obtain the corresponding vehicle usage conditions through input fields 301, 302, and 304 and options 303, 305, and 306 respectively. Specifically, terminal device 110 can receive the pick-up city and pick-up location through input fields 301 and 302 respectively. Terminal device 110 can obtain time-related vehicle usage conditions such as pick-up time, return time, and usage duration through input field 304.

[0040] Terminal device 110 can also determine the corresponding user conditions based on the selection status of options 303, 305, and 306. Specifically, if option 303 is selected, terminal device 110 can use "allowing one-way car return" as a user condition. If option 305 is selected, terminal device 110 can use "deposit-free service" as a user condition. If option 306 is selected, terminal device 110 can determine "door-to-door car delivery service" as a user condition.

[0041] Terminal device 110 can respond to the triggering of confirmation control 307 and, based on the aforementioned user conditions indicating user needs (e.g., pick-up city, pick-up location, usage time, etc.), determine at least one vehicle type that meets the user's usage needs, such as "Manufacturer A1, Model B1", "Manufacturer A2, Model B2", "Manufacturer A3, Model B3", etc. Then, terminal device 110 can present the vehicle information interface shown in Example 300B. This vehicle information interface can include interface area 310, which includes first areas 311, 312, and 313. First areas 311, 312, and 313 respectively present information related to the "Manufacturer A1, Model B1", "Manufacturer A2, Model B2", and "Manufacturer A3, Model B3" vehicles.

[0042] It should be understood that the at least one vehicle type can include any vehicle type that application 120 can provide, and is not limited to vehicle types that meet the user's driving needs. For example, if the vehicle model information interface is the homepage of application 120, the at least one vehicle type can include the vehicle types presented on the homepage of application 120. As another example, if the vehicle model information interface is the recommendation interface of application 120, the at least one vehicle type can include vehicle types recommended to the user.

[0043] The various first areas in the vehicle information interface are used to present information about the associated vehicle type. These first areas can be presented in a card format and are therefore also called card areas. Vehicle type information may include vehicle attribute information and vehicle availability information. In some embodiments, the first area may be configured as a rectangular or approximately rectangular area (e.g., a rounded rectangle). As an example, such as... Figure 3B As shown, the vehicle information interface in Example 300B includes first regions 311, 312, and 313 that are approximately rectangular. Of course, in practical applications, the first region can be configured with any suitable shape and style, and the embodiments of this disclosure do not specifically limit this.

[0044] Vehicle attribute information describes the characteristics of a vehicle. This information may include, but is not limited to, manufacturer, model, engine type, displacement, transmission (e.g., manual or automatic), drive system, vehicle dimensions, number of seats, etc. Vehicle availability information may include details indicating the vehicle's availability to a user, such as the provider's name, resources required for its use, collateral required, resource waivers, mileage limits, and the number of available vehicles.

[0045] As an example, such as Figure 3B As shown, the first area 311 is used for information about the "A1 Manufacturer B1 Model" vehicle. The first area 311 presents the name 314 of the "A1 Manufacturer B1 Model" vehicle, vehicle attribute information 315, vehicle image 316, and vehicle availability information 317. Specifically, the vehicle attribute information 315 includes keywords indicating that the "A1 Manufacturer B1 Model" vehicle is an economy vehicle, the number of seats, transmission type, and engine displacement. The vehicle availability information 317 includes the average daily resource requirement and total resource requirement for vehicle use. It should be noted that the average daily resource requirement and total resource requirement presented here can be the average daily resource requirement and average total resource requirement of all available vehicles of the "A1 Manufacturer B1 Model" vehicle, or it can be the average daily resource requirement and total resource requirement of a given available vehicle of the "A1 Manufacturer B1 Model" vehicle (e.g., the recommended vehicle).

[0046] One or more first areas in the vehicle information interface may further include first interface elements, which indicate the pending-save status of the corresponding vehicle type. That is, the first area associated with the vehicle type pending-save status in at least one first area may display the first interface element. This first interface element may include various elements that indicate the vehicle type is pending-save status, such as icons, options, labels, and text.

[0047] In some embodiments, the first area in the at least one first region associated with a vehicle type that is in a saved state may display a second interface element. This second interface element differs from the first interface element and can indicate the saved state of the corresponding vehicle type. The second interface element may include various elements capable of indicating that a vehicle type is in a saved state, such as icons, options, labels, and text.

[0048] In some embodiments, the terminal device 110 may, in response to detecting a user's interface request, obtain vehicle attribute information, vehicle availability information, and status information for at least one vehicle type. The status information indicates whether the corresponding vehicle type is in a pending-for-favorites state or a favorited state. If the status information indicates that the corresponding vehicle type is in a pending-for-favorites state, the terminal device 110 may display a first interface element in the corresponding first area of ​​the vehicle model information interface. If the status information indicates that the corresponding vehicle type is in a favorited state, the terminal device 110 may display a second interface element in the corresponding first area of ​​the vehicle model information interface.

[0049] As an example, such as Figure 3C As shown, Example 300C illustrates another example of the vehicle information interface of Application 120. The vehicle information interface in Example 300C includes first areas 311, 312, and 313, which are used to present information related to the "Manufacturer A1 Model B1", "Manufacturer A2 Model B2", and "Manufacturer A3 Model B3" vehicles, respectively. If it is determined that the "Manufacturer A1 Model B1" vehicle is in a state to be saved, the terminal device 110 can display icon 318 (i.e., the first interface element) in the first area 311. This icon 318 is an approximately square and hollow frame. If it is determined that the "Manufacturer A2 Model B2" and "Manufacturer A3 Model B3" vehicles are in a state to be saved, the terminal device 110 can display icons 321 and 322 (i.e., the second interface elements) in the first areas 312 and 313, respectively. Icons 321 and 322 are approximately square frames filled with a striped pattern.

[0050] It is understood that the first and second interface elements in the above examples are merely illustrative, and any appropriate elements can be selected to form the first and second interface elements according to actual needs. For example, a hollow pentagram icon can be selected to form the first interface element, and a pentagram icon filled with patterns or colors can be selected to form the second interface element.

[0051] In box 220, if a trigger on a target first interface element among one or more first interface elements is detected, the terminal device 110 determines the target vehicle type corresponding to the target first interface element as the user's favorite vehicle model. The trigger on the first interface element instructs the user to initiate a favorite request for the target vehicle type. The specific triggering operation can be set according to the actual application. In some examples, triggering the first interface element may include a click operation on the first user interface (e.g., mouse click, single-click gesture, double-click gesture, etc.). In one example, triggering the first interface element may include any other appropriate interaction method, as long as it allows a favorite request to be issued via the first interface element. Thus, users can easily and conveniently favorite the corresponding vehicle type by triggering the first interface element, creating a "one-click favorite" user experience.

[0052] In some embodiments, the terminal device 110 may add information about the target vehicle type (e.g., name, number, or vehicle attribute information) to the user's favorites list to identify the target vehicle type as a favorite vehicle model. Alternatively or additionally, the terminal device 110 may also modify the status information of the target vehicle type to indicate that the target vehicle type is a favorite vehicle model. Alternatively or additionally, the terminal device 110 may generate relationship information that indicates the favorite relationship between the user and the target vehicle type.

[0053] In box 230, terminal device 110 switches the target first interface element to a second interface element, indicating through the second interface element that the target vehicle type is in a saved state. As an example, such as... Figure 3B and Figure 3C As shown in Example 300B, the first areas 311, 312, and 313 of the vehicle information interface display icons 318, 319, and 320, respectively. Icons 318, 319, and 320 are all elements of the first interface. If a user triggers icons 319 and 320 through terminal device 110 or an attached device of terminal device 110, terminal device 110 can identify the "A2 manufacturer B2 model" and "A3 manufacturer B3 model" vehicles as the user's favorite vehicles. Terminal device 110 can also switch the icons 319 and 320 displayed in the first areas 312 and 313 of Example 300B to icons 321 and 322, respectively, as shown in Example 300C.

[0054] It is understandable that the process of switching from the first interface element to the second interface element may differ when the first interface element and the second interface element are different. For example, if the first interface element is a hollow pentagram icon and the second interface element is a pentagram icon filled with color, the terminal device 110 can, in response to detecting a trigger on the hollow pentagram icon, save the vehicle type corresponding to the triggered hollow pentagram icon, and switch the hollow pentagram icon corresponding to that vehicle type to a pentagram icon filled with color to indicate that the vehicle type has been saved. The embodiments of this disclosure do not limit the specific style, presentation position, or interaction method of these interface elements.

[0055] In some embodiments, the terminal device 110 may also present a favorites entry on the vehicle model information interface. If a trigger on the favorites entry is detected, the terminal device 110 presents the favorites interface. The trigger on the favorites entry indicates an interface request to the favorites interface; the specific triggering operation can be set according to the actual application. In some examples, triggering the favorites entry may include a click operation on the favorites entry (e.g., a single-click gesture, a long-press gesture, a double-click gesture, a swipe gesture, etc.). Of course, triggering the favorites entry may include any appropriate interaction method, and the embodiments of this disclosure do not specifically limit the triggering method.

[0056] Regarding the presentation of the favorites entry, in some embodiments, the terminal device 110 can determine whether the user has favorited car models. If it is determined that the user has favorited car models, the terminal device 110 can present the favorites entry on the car model information interface. If it is determined that the user has not favorited car models, the terminal device 110 can not present the favorites entry on the car model information interface.

[0057] As an example, such as Figure 3B and Figure 3C As shown, before adding "Manufacturer A2 Model B2" and "Manufacturer A3 Model B3" to the favorites, if the terminal device 110 determines that the user has not added any models to their favorites, the terminal device 110 can display a model information interface as shown in Example 300B, which does not display a favorites entry. After adding "Manufacturer A2 Model B2" and "Manufacturer A3 Model B3" to the favorites, the terminal device 110 determines that the current user has added any models to their favorites and displays a model information interface as shown in Example 300C, which displays a favorites entry 323.

[0058] Alternatively or additionally, if the user has favorite car models, the terminal device 110 can also determine whether there is a vehicle type belonging to the favorite car model among at least one vehicle type in the car model information interface. If it is determined that the user has favorite car models, and there is a vehicle type belonging to the favorite car model among at least one vehicle type, the terminal device 110 can display the favorite entry in the car model information interface.

[0059] It should be noted that the above presentation of the favorites entry is merely exemplary. Terminal device 110 may also present the favorites entry on each vehicle model information interface. Terminal device 110 can also determine whether the user is logged in; if the user is logged in, terminal device 110 may present the favorites entry on the vehicle model information interface.

[0060] In some embodiments, the terminal device 110 can determine the number of car models the user has favorited (i.e., a first number) and can display the number of the user's favorite car models in association with the favorites entry. As an example, such as Figure 3C As shown, if the terminal device determines that the number of car models the user has collected is 2, the terminal device can display the number "2" in parentheses in the collection entry 323.

[0061] Alternatively, the terminal device 110 may also determine the number of vehicle types belonging to the user's favorite vehicle types in at least one vehicle type in the vehicle type information interface (i.e., the second number), and the terminal device 110 may also present the second number in association with the favorite entry.

[0062] In some embodiments, a user's favorites interface may include at least one second area associated with at least one of the user's favorite vehicle models. Each second area includes information about the associated favorite vehicle model. This information may include at least one of the following: vehicle attribute information or vehicle availability information. In some embodiments, the second area may be configured as a rectangular or approximately rectangular area (e.g., a rounded rectangle). Of course, in practical applications, the second area may be configured with any suitable shape and style, and the embodiments of this disclosure do not specifically limit this.

[0063] As an example, such as Figure 3C and Figure 3D As shown in Example 300C, the vehicle information interface displays a favorites entry 323. If a trigger on favorites entry 323 is detected, terminal device 110 can display a favorites interface 330 as shown in Example 300D. The favorites interface includes second areas 331 and 332. Second area 331 displays the name 333, vehicle attribute information 334, vehicle image 335, and vehicle availability information 336 of the vehicle model "A2 Manufacturer B2 Model". Similarly, second area 332 displays the name, vehicle attribute information, vehicle image, and vehicle availability information of the vehicle model "A3 Manufacturer B3 Model".

[0064] The vehicle attribute information presented in the Favorites interface may be the same as or different from the vehicle attribute information presented in the Model Information interface. Similarly, the vehicle availability information presented in the Favorites interface may also be the same as or different from the vehicle availability information presented in the Model Information interface. For example, ... Figure 3B and Figure 3DAs shown, the vehicle attribute information 324 presented in the first area 312 includes the keyword "economy model," the number of seats, transmission type, and engine displacement. The vehicle attribute information 334 presented in the second area not only includes the keyword "economy model," the number of seats, transmission type, and engine displacement, but also the number of doors and the year of manufacture. The vehicle availability information 325 presented in the first area 312 includes the average daily resource requirement and the total resource requirement for vehicle use. The vehicle availability information 336 presented in the second area 331 includes the number of available vehicles corresponding to the favorite model (sometimes referred to as the third number in this document) and the total resource requirement for using a given available vehicle corresponding to the favorite model (e.g., the top-rated vehicle).

[0065] In some embodiments, the second area of ​​the favorites interface may only display vehicle attribute information or vehicle availability information. For example, if it is determined that there are available vehicles for the favorited models, the terminal device 110 may display vehicle availability information and vehicle attribute information in the second area associated with the favorited models. If it is determined that there are no available vehicles for the favorited models, the terminal device 110 may display vehicle attribute information in the second area associated with the favorited models, but not vehicle availability information. It should also be noted that the information on the favorited models displayed on the favorites interface is not limited to the above information, and any appropriate vehicle attribute information and vehicle availability information may be displayed according to actual needs. The embodiments of this disclosure do not limit this.

[0066] In some embodiments, if a triggering of a target second region within at least one second region is detected, and it is determined that the collectible vehicle models associated with the target second region include at least one available vehicle, a vehicle information interface corresponding to the collectible vehicle models associated with the target second region is presented. As an example, such as... Figure 3D As shown, if a user wishes to select a vehicle of model "A2 Manufacturer B2 Model", they can trigger the second area 331 by, for example, clicking. The terminal device 110 detects the triggering of the second area 331 and determines that there are five available vehicles of model "A2 Manufacturer B2 Model", then presents the vehicle information interface corresponding to model "A2 Manufacturer B2 Model". It should be noted that in practical applications, any appropriate interaction method can be selected to trigger the second area according to actual needs; the embodiments of this disclosure do not limit the triggering method of the second area.

[0067] In some embodiments, the second region may be configured to include a first sub-region and a second sub-region different from the first sub-region. If the terminal device 110 detects a trigger on the first sub-region of the target second region in the favorites interface, and determines that the favorite vehicle models associated with the target second region include at least one available vehicle model, the terminal device 110 presents a vehicle information interface corresponding to the favorite vehicle model associated with the target second region. If the terminal device 110 detects a trigger on the second sub-region of the target second region in the favorites interface, the terminal device 110 performs vehicle usage processing for a given available vehicle of the favorite vehicle model associated with the target second region.

[0068] As an example, such as Figure 3D and Figure 3E As shown, in Example 300D, the second area 332 displays the number of available vehicles (e.g., 8 offers) for the "A3 Manufacturer B3 Model" model, and also the total resources required to use the top-ranked vehicle among the eight available vehicles. The top-ranked vehicle can be one of the eight available vehicles determined by the terminal device 110 based on predetermined rules. The second area 332 can include a first sub-area 337 and a second sub-area 338. The first sub-area 337 can be the area displaying the number of available vehicles (i.e., 8 offers), and the second sub-area 338 can be the area outside the first sub-area 337 within the second area 332. If a trigger on the first sub-area 337 is detected, the terminal device 110 can display the vehicle information interface 340 shown in Example 300E. If a trigger on the second sub-area 338 is detected, the terminal device 110 can perform vehicle usage processing for the top-ranked vehicle, such as receiving confirmation of use of the top-ranked vehicle, signing a usage agreement, providing the resources required to use the top-ranked vehicle, etc.

[0069] In some embodiments, the vehicle information interface includes at least one third area associated with at least one available vehicle, each third area including at least vehicle availability information of the associated available vehicle. As an example, such as... Figure 3EAs shown, Example 300E illustrates a vehicle information interface 340 for the "A3 Manufacturer B3 Model" vehicle. The vehicle information interface 340 includes third areas 341, 342, and 343, each associated with a different available vehicle. Taking the third area 341 as an example, the third area 341 presents vehicle availability information for the associated available vehicle. This vehicle availability information includes the provider name 344 of the available vehicle and the total resources required to use the available vehicle 345. The third area 341 also presents vehicle attribute information for the available vehicle (e.g., "One-year-old car | Reversing camera | Reversing radar | XXXX model | 2.0L"). Furthermore, the vehicle information interface may also display the name 347 of the "A3 Manufacturer B3 Model" vehicle, some vehicle attribute information of the "A3 Manufacturer B3 Model" vehicle (e.g., common vehicle attribute information for this model), and a vehicle image 349 at the top of the interface.

[0070] In some embodiments, if a triggering of a target third area in the vehicle information interface is detected, vehicle usage processing is performed for the target available vehicle associated with the target third area. Specifically, the user can determine the desired vehicle (i.e., the target available vehicle) from multiple available vehicles based on the vehicle-related information presented in each third area of ​​the vehicle information interface, and trigger the third area associated with the target available vehicle through an input device (e.g., a touchscreen or mouse). In response to detecting a triggering of the third area associated with the target available vehicle, the terminal device 110 can perform actions such as confirming the use of the target available vehicle, signing a usage agreement, providing resources required for the use of the target available vehicle, etc., to complete the vehicle usage processing for the target available vehicle.

[0071] The trigger indication for the target third area is to initiate a vehicle request for the target available vehicle associated with the target third area. The specific trigger operation can be set according to the actual application. In some examples, the target third area can be triggered by click operations such as single-click gestures, double-click gestures, long-press gestures, and swipe gestures. Of course, the above interaction methods are only exemplary, and any other interaction method can be selected according to actual needs. The embodiments of this disclosure are not limited in this regard.

[0072] As an example, such as Figure 3EAs shown, the third areas 341, 342, and 343 can also display vehicle selection controls 351, 352, and 353, respectively. Users can trigger any one of the vehicle selection controls 351, 352, and 353. For example, if a user triggers vehicle selection control 351 by clicking, the terminal device 110 can display the corresponding vehicle usage processing interface. This interface can display usage plans and resource provision entry points, such as vehicle configuration information, usage conditions, driving insurance, mortgage rules, and the amount of resources required for vehicle use. The terminal device 110 can provide usage resources and / or mortgage resources through the resource provision entry point to rent the corresponding vehicle.

[0073] In some embodiments, if a predetermined operation is detected on a second area of ​​the favorites interface, the terminal device 110 may present a third interface element corresponding to the favorite car model associated with the operated second area. If a trigger on the third interface element is further detected, the terminal device 110 may remove the favorite car model corresponding to the third interface element from the user's favorite car models. The third interface element may include, for example, icons, options, controls, buttons, etc. The predetermined operation instruction for the second area initiates a request to present the third interface element, and the predetermined operation may include, for example, a swipe operation, a drag operation, a click operation, or a double-click operation, etc. Of course, the above-described operation methods are merely exemplary, and the embodiments of this disclosure do not specifically limit them.

[0074] As an example, such as Figure 3D and Figure 3F As shown, if a user wishes to unfavorite the "A3 Manufacturer B3 Model" car model, the user can perform a swipe or drag operation on the second area 332 in Example 300D to the left of the interface using terminal device 110 or an attached device of terminal device 110. In response to detecting this swipe or drag operation, terminal device 110 can display the icon 339 (i.e., the third interface element) corresponding to the "A3 Manufacturer B3 Model" car model, as shown in Example 300F. The user can select icon 339 by, for example, clicking, double-clicking, or long-pressing. In response to detecting the selection of icon 339, terminal device 110 removes the "A3 Manufacturer B3 Model" car model from the user's favorite car models. For example, terminal device 110 can remove the information of the "A3 Manufacturer B3 Model" car model from the user's favorites list and delete the second area 332 corresponding to the "A3 Manufacturer B3 Model" car model from the favorites interface. This allows for convenient unfavoriting of car models.

[0075] In summary, according to the embodiments of this disclosure, users can save vehicle models (i.e., vehicle types) by triggering a first interface element, and then visualize the saved models by switching from the first interface element to a second interface element. This allows users to efficiently, conveniently, and accurately save the desired vehicle models, facilitating subsequent vehicle selection, reducing the time and difficulty of selection, and ultimately improving the user experience of car-related services.

[0076] Example devices and equipment

[0077] Embodiments of this disclosure also provide corresponding apparatus for implementing the above methods or processes. Figure 4 A schematic structural block diagram of an apparatus 400 for vehicle information processing according to some embodiments of the present disclosure is shown. The apparatus 400 may be implemented in or included in a terminal device 110. Various modules / components in the apparatus 400 may be implemented by hardware, software, firmware, or any combination thereof.

[0078] like Figure 4 As shown, the device 400 includes a vehicle model interface presentation module 410, a vehicle model selection module 420, and an interface element switching module 430. The interface presentation module 410 is configured to present a vehicle model information interface in response to a detected user interface request. The vehicle model information interface includes at least one first area associated with at least one vehicle type. Each first area includes vehicle attribute information and vehicle availability information for the associated vehicle type. One or more of the at least one first area each include a first interface element, which indicates the desired status of the corresponding vehicle type. The vehicle model selection module 420 is configured to determine the target vehicle type corresponding to the target first interface element as the user's selected vehicle model in response to a detected triggering of a target first interface element among one or more first interface elements. The interface element switching module 430 is configured to switch the target first interface element to a second interface element, which indicates that the target vehicle type is in a selected status.

[0079] In some embodiments, the vehicle model interface presentation module 410 is further configured to: in response to detecting a user's vehicle use request, determine at least one vehicle type that meets the vehicle use requirements corresponding to the vehicle use request, each vehicle type including at least one available vehicle; and present a vehicle information interface.

[0080] In some embodiments, the vehicle model interface presentation module 410 is further configured to: in response to detecting a user's interface request, acquire vehicle attribute information, vehicle availability information, and status information for at least one vehicle type, wherein the status information indicates that the corresponding vehicle type is in a pending collection state or a collected state; in response to the status information indicating that the corresponding vehicle type is in a pending collection state, present a first interface element in the corresponding first area of ​​the vehicle model information interface; and in response to the status information indicating that the corresponding vehicle type is in a collected state, present a second interface element in the corresponding first area of ​​the vehicle model information interface.

[0081] In some embodiments, the vehicle model interface presentation module 410 is further configured to: present a favorites entry on the vehicle model information interface; and, in response to detecting a trigger on the favorites entry, present a favorites interface, the favorites interface including at least one second area associated with at least one favorite vehicle model of the user, each second area including vehicle attribute information and vehicle availability information of the associated favorite vehicle model.

[0082] In some embodiments, the vehicle model interface presentation module 410 is further configured to present a first number or a second number in association with the favorites entry, wherein the first number is the number of vehicle models in the user's favorites, and the second number is the number of vehicle types belonging to the user's favorite vehicle models among at least one vehicle type.

[0083] In some embodiments, the vehicle model interface presentation module 410 is further configured to: in response to determining that a user has a favorite vehicle model, present a favorite entry on the vehicle model information interface.

[0084] In some embodiments, the vehicle availability information for a collection model includes at least one of the following: a third number of available vehicles corresponding to the collection model, or the resources required to use a given available vehicle corresponding to the collection model.

[0085] In some embodiments, the device 400 further includes a vehicle interface presentation module configured to, in response to detecting a triggering of a target second region in at least one second region and determining that the favorite vehicle models associated with the target second region include at least one available vehicle, present a vehicle information interface corresponding to the favorite vehicle models associated with the target second region.

[0086] In some embodiments, the apparatus 400 further includes: a vehicle interface presentation module configured to, in response to detecting a triggering of a first sub-region of a target second region in at least one second region, and determining that the favorite vehicle models associated with the target second region include at least one available vehicle model, present a vehicle information interface corresponding to the favorite vehicle model associated with the target second region; and a vehicle usage processing module configured to, in response to detecting a triggering of a second sub-region of a target second region in at least one second region, perform vehicle usage processing on a given available vehicle of the favorite vehicle model associated with the target second region.

[0087] In some embodiments, the vehicle information interface includes at least one third area associated with at least one available vehicle, each third area including at least vehicle availability information of the associated available vehicle, and the apparatus 400 further includes: a vehicle use processing module configured to perform vehicle use processing for a target available vehicle associated with the target third area in response to detecting a triggering of a target third area in the at least one third area.

[0088] In some embodiments, the device 400 further includes: a favorite vehicle model removal module, configured to, in response to detecting a predetermined operation on a second region in at least one second region, present a third interface element corresponding to the favorite vehicle model associated with the operated second region; and, in response to detecting a triggering of the third interface element, remove the favorite vehicle model corresponding to the third interface element from the user's favorite vehicle models.

[0089] The units and / or modules included in device 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units and / or modules can be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. In addition to or as an alternative to machine-executable instructions, some or all of the units and / or modules in device 400 can be implemented at least partially by one or more hardware logic components. By way of example and not limitation, exemplary types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-chips (SoCs), complex programmable logic devices (CPLDs), and so on.

[0090] Figure 5 A block diagram of an electronic device 500 in which one or more embodiments of the present disclosure may be implemented is shown. It should be understood that... Figure 5 The electronic device 500 shown is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. Figure 5 The illustrated electronic device 500 may include or be implemented as Figure 1 Terminal equipment 110 or Figure 4 Device 400.

[0091] like Figure 5 As shown, electronic device 500 is in the form of a general-purpose electronic device. Components of electronic device 500 may include, but are not limited to, one or more processors or processing units 510, memory 520, storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. Processing unit 510 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 520. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 500.

[0092] Electronic device 500 typically includes multiple computer storage media. Such media can be any accessible media that is accessible to electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 520 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 530 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data and can be accessed within electronic device 500.

[0093] Electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not explicitly stated... Figure 5 As shown, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks can be provided. In these cases, each drive can be connected to a bus (not shown) via one or more data media interfaces. Memory 520 may include computer program product 525 having one or more program modules configured to perform various methods or actions of various embodiments of this disclosure.

[0094] Communication unit 540 enables communication with other electronic devices via a communication medium. Additionally, the functionality of components of electronic device 500 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, electronic device 500 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0095] Input device 550 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 560 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 500 can also communicate with one or more external devices (not shown) via communication unit 540 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 500, or with any device that enables electronic device 500 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interface (not shown).

[0096] According to an exemplary implementation of this disclosure, a computer-readable storage medium is provided that stores computer-executable instructions thereon, wherein the computer-executable instructions are executed by a processor to implement the methods described above. According to an exemplary implementation of this disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, which are executed by a processor to implement the methods described above.

[0097] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to this disclosure. It should 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-readable program instructions.

[0098] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0099] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0100] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0101] Various implementations of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for vehicle information processing, comprising: In response to a detected user interface request, a vehicle model information interface is presented. The vehicle model information interface includes at least one first area associated with at least one vehicle type. Each first area includes vehicle attribute information and vehicle availability information of the associated vehicle type. One or more of the at least one first areas respectively include a first interface element, and the first interface element indicates the favorite status of the corresponding vehicle type. In response to detecting a trigger on a target first interface element among the one or more first interface elements, the target vehicle type corresponding to the target first interface element is determined to be the user's favorite vehicle model; as well as The target first interface element is switched to a second interface element, and the second interface element indicates that the target vehicle type is in a saved state.

2. The method according to claim 1, wherein presenting the vehicle model information interface in response to detecting a user's interface request includes: In response to detecting the user’s car use request, at least one vehicle type that meets the car use requirements corresponding to the car use request is determined, and each vehicle type includes at least one available vehicle. as well as The vehicle information interface is then displayed.

3. The method according to claim 1, wherein presenting the vehicle model information interface in response to detecting a user's interface request includes: In response to detecting the user's interface request, vehicle attribute information, vehicle availability information and status information of each of the at least one vehicle type are obtained, wherein the status information indicates that the corresponding vehicle type is in a state of waiting to be saved or in a state of being saved. In response to the indication based on the status information that the corresponding vehicle type is in a state to be saved, the first interface element is displayed in the corresponding first area of ​​the vehicle information interface. as well as In response to the indication based on the status information that the corresponding vehicle type is in a saved state, the second interface element is displayed in the corresponding first area of ​​the vehicle information interface.

4. The method according to claim 1, further comprising: The vehicle information interface displays a collection entry; as well as In response to the detection of a trigger on the favorites entry, a favorites interface is presented, the favorites interface including at least one second area associated with at least one favorite car model of the user, each second area including vehicle attribute information and vehicle availability information of the associated favorite car model.

5. The method according to claim 4, further comprising: A first number or a second number is presented in association with the collection entry, the first number being the number of car models the user has collected, and the second number being the number of vehicle types belonging to the user's collected car models among the at least one vehicle type.

6. The method according to claim 4, wherein presenting the favorites entry on the vehicle information interface includes: In response to the determination that the user has a favorite car model, the favorite entry is displayed on the car model information interface.

7. The method according to claim 4, wherein the vehicle availability information of the collected vehicle models includes at least one of the following: The third number of available vehicles corresponding to the collected model, or The resources required to use the given available vehicle corresponding to the collected model.

8. The method according to claim 4, further comprising: In response to detecting a triggering of a target second region in the at least one second region, and determining that the collectible models associated with the target second region include at least one available vehicle, a vehicle information interface corresponding to the collectible models associated with the target second region is presented.

9. The method according to claim 4, further comprising: In response to detecting a triggering of a first sub-region of a target second region in the at least one second region, and determining that the collectible models associated with the target second region include at least one available model, a vehicle information interface corresponding to the collectible models associated with the target second region is presented; as well as In response to the detection of a triggering of a second sub-region of a target second region in the at least one second region, vehicle usage processing is performed on a given available vehicle of a collectible model associated with the target second region.

10. The method of claim 8 or 9, wherein the vehicle information interface includes at least one third region associated with the at least one available vehicle, each third region including at least vehicle availability information of the associated available vehicle, the method further comprising: In response to the detection of a triggering of a target third region in the at least one third region, vehicle use processing is performed for a target available vehicle associated with the target third region.

11. The method according to claim 4, further comprising: In response to detecting a predetermined operation on a second region within the at least one second region, a third interface element corresponding to the collected car model associated with the operated second region is presented; as well as In response to the detection of a trigger on the third interface element, the car model corresponding to the third interface element is removed from the user's favorite car models.

12. An apparatus for vehicle information processing, comprising: The interface presentation module is configured to present a vehicle model information interface in response to detecting a user's interface request. The vehicle model information interface includes at least one first area associated with at least one vehicle type. Each first area includes vehicle attribute information and vehicle availability information of the associated vehicle type. One or more of the at least one first areas respectively include a first interface element, and the first interface element indicates the favorite status of the corresponding vehicle type. The vehicle model selection module is configured to, in response to detecting a trigger on a target first interface element among the one or more first interface elements, determine the target vehicle type corresponding to the target first interface element as the user's vehicle model selection. as well as The interface element switching module is configured to switch the target first interface element to a second interface element, wherein the second interface element indicates that the target vehicle type is in a saved state.

13. An electronic device, comprising: At least one processing unit; as well as At least one memory, coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, which, when executed by the at least one processing unit, cause the electronic device to perform the method according to any one of claims 1 to 11.

14. A computer-readable storage medium having a computer program stored thereon, the computer program being executable by a processor to implement the method according to any one of claims 1 to 11.

15. A computer program product comprising a computer program, wherein the computer program, when executed by a processor, implements the method according to any one of claims 1 to 11.

Images