WO2021136324A1 - 一种共享车辆的信息推送方法和系统 - Google Patents

一种共享车辆的信息推送方法和系统 Download PDF

Info

Publication number
WO2021136324A1
WO2021136324A1 PCT/CN2020/141152 CN2020141152W WO2021136324A1 WO 2021136324 A1 WO2021136324 A1 WO 2021136324A1 CN 2020141152 W CN2020141152 W CN 2020141152W WO 2021136324 A1 WO2021136324 A1 WO 2021136324A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
vehicle
shared
information
preset
Prior art date
Application number
PCT/CN2020/141152
Other languages
English (en)
French (fr)
Inventor
陈方健
刘宇
陈燕莉
彭颖茵
Original Assignee
北京骑胜科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201911406331.4A external-priority patent/CN111861624A/zh
Priority claimed from CN201911424973.7A external-priority patent/CN111858624A/zh
Priority claimed from CN201911412463.8A external-priority patent/CN111860877A/zh
Application filed by 北京骑胜科技有限公司 filed Critical 北京骑胜科技有限公司
Publication of WO2021136324A1 publication Critical patent/WO2021136324A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry

Definitions

  • This application relates to the technical field of shared equipment, and in particular to a method and system for pushing information of shared vehicles.
  • One of the embodiments of the present application provides a method for pushing information of a shared vehicle, which is executed by at least one processor, and the method includes: in response to a user's operation instruction to a terminal device, acquiring characteristic information related to the operation instruction; at least The display information of the terminal device is determined based on the characteristic information, the display information includes vehicle recommendation information and/or usage information of the shared vehicle; and the display information is sent to the terminal device.
  • the characteristic information related to the operation instruction includes the first position where the user executes the operation instruction, the initiation time of the operation instruction, and the travel information of the user; the display information includes all The vehicle recommendation information of the shared vehicle; determining the vehicle recommendation information based at least on the characteristic information includes: based on the first location, the initiation time of the operation instruction, and the travel information of the user , Determine the travel destination of the user; based on the distance between the travel destination and the preset return area, determine the first shared vehicle from multiple shared vehicles within a preset distance range from the first location Recommended vehicle.
  • the travel information includes multiple pieces of historical travel information of the user; and, the determining the travel destination of the user includes: determining multiple pieces of historical travel based on the multiple pieces of historical travel information Route, and the travel start time corresponding to each historical travel route; among the multiple historical travel routes, the historical travel route whose travel start time is closest to the initiation time of the operation instruction is determined as Estimated travel route; determining that the destination corresponding to the estimated travel route is the travel destination of the user.
  • the travel information includes planned travel information of the user; and, determining the travel destination of the user includes: obtaining the travel mode and travel mode of the planned travel information of the user. Time; based on the travel mode, determine the travel origin of the planned travel information; based on the distance between the first location and the travel origin of the planned travel information, determine from the first The estimated time of arrival from the location to the travel origin of the planned travel information; in response to the estimated arrival time being earlier than the travel time of the planned travel information, determining the travel start of the planned travel information The origin is the travel destination of the user.
  • the determination is made from the plurality of shared vehicles within a preset distance range from the first location
  • the first recommended vehicle includes: determining the remaining cruising range of each shared vehicle among the plurality of shared vehicles; responding to that the distance between the travel destination and the preset return area is less than a first preset distance value , Determine the estimated travel mileage between the first location and the preset return area; determine based on the remaining cruising range and the estimated travel mileage of each shared vehicle in the plurality of shared vehicles Among the plurality of shared vehicles, the shared vehicle that meets the first preset condition is the first recommended vehicle; wherein, the first preset condition includes the difference between the remaining cruising range of the shared vehicle and the travel mileage The distance difference is greater than the second preset distance value, and the remaining cruising range value is the smallest among the multiple shared vehicles.
  • the determination is made from the plurality of shared vehicles within a preset distance range from the first location
  • the first recommended vehicle includes: in response to the distance between the travel destination and the preset return area being not less than the first preset distance value, determining the remaining cruising range value in the plurality of shared vehicles The largest shared vehicle is the first recommended vehicle.
  • the method further includes: displaying the remaining cruising range corresponding to the first recommended vehicle to the user, and obtaining first feedback information of the user; and responding to the first feedback information indicating The user determines not to use the first recommended vehicle, and determines a second recommended vehicle from the plurality of shared vehicles based on the remaining cruising range of the plurality of shared vehicles and/or the input destination of the user .
  • the characteristic information related to the operation instruction includes a shared vehicle status tag input by the user; the determining the vehicle recommendation information of the terminal device at least based on the characteristic information includes: The status tag input by the user selects the shared vehicle corresponding to the status tag from various types of shared vehicles as the third recommended vehicle.
  • the method further includes: obtaining a second location of the recommended vehicle and a third location of the user; and according to the third location of the user and the second location of the recommended vehicle, Provide navigation information from the third location to the second location.
  • the shared vehicle is equipped with a reminding device
  • the method further includes: calculating the distance between the third position of the user and the second position of the recommended vehicle; if the third position of the user is If the distance between the position and the second position of the recommended vehicle is less than the third preset distance value, the reminding device is controlled to send a reminding signal.
  • the reminding device is a flashing light
  • the controlling the reminding device to send a reminding signal includes: controlling the flashing light to flash, wherein the third position of the user is the same as the second position of the recommended vehicle. The smaller the distance between the positions, the higher the frequency of controlling the flash to blink.
  • the method further includes: acquiring second feedback information of the user; if the second feedback information indicates that the user has not found the recommended vehicle, determining that the fourth recommended vehicle is an updated Recommended vehicle.
  • the method further includes: changing the state of the vehicle corresponding to the recommended vehicle to a reserved state; when receiving a riding start instruction sent by the user, controlling the recommended vehicle to unlock.
  • the various types of shared vehicles are located in a plurality of pre-divided preset areas, and the method further includes: counting the number of selected shared vehicles included in each preset area; Assuming the number of the filtered shared vehicles included in the area, determine the target area that needs to be upgraded.
  • the determining the target area that needs to be upgraded according to the number of filtered shared vehicles included in each preset area includes: selecting from each of the selected shared vehicles.
  • a reference area is selected from the preset area, and the number of the shared vehicles selected in each preset area except the reference area among the preset areas including the selected shared vehicles is calculated and The data difference of the number of the shared vehicles selected in the reference area; and the target area that needs to be upgraded according to the data difference is determined.
  • the method further includes: obtaining a preset upgrade rule corresponding to the status label; and performing the function upgrade on the shared vehicles that are screened out in the target area according to the preset upgrade rule .
  • the status tag of the shared vehicle is determined by: acquiring at least one status data sent by at least one shared vehicle; for each status data sent by each shared vehicle, Obtain the state type to which the state data belongs, and obtain the preset evaluation strategy corresponding to the state type; for each of the state data sent by the shared vehicle and belonging to each of the state types, use the state type The corresponding preset evaluation strategy is analyzed to obtain the status label corresponding to the shared vehicle that sends the status data belonging to the status type.
  • the method further includes: respectively sending a control instruction to each of the selected shared vehicles to prohibit the selected shared vehicles from sending status data corresponding to the shared vehicle.
  • the preset evaluation strategy is obtained by: providing a policy configuration interface; obtaining the preset evaluation strategy in response to a configuration operation on the strategy configuration interface.
  • the determining the display information based on at least the characteristic information includes: acquiring shared vehicle usage conditions in a plurality of preset areas at the first moment; wherein, the shared vehicle usage status includes the shared vehicle usage status The number of vehicles; the shared vehicle usage status stored in the preset area at the second time is updated according to the shared vehicle usage status at the first moment, and the display information carrying the shared vehicle usage status is generated.
  • the terminal device includes an operation and maintenance terminal; the acquiring the shared vehicle usage status in the plurality of preset areas at the first moment includes: receiving a data from the operation and maintenance terminal The number of the shared vehicles placed in the preset area; or, when the first scan code information of one of the shared vehicles in the preset area sent by the operation and maintenance terminal is received, the The number of shared vehicles corresponding to the preset area is increased by one to update the number of shared vehicles.
  • the terminal device includes a client; the acquiring the shared vehicle usage status in the plurality of preset areas at the first moment includes: when receiving the current status sent by the client When the second scan code information of one of the shared vehicles in the preset area is used, the number of shared vehicles corresponding to the preset area is reduced by one to update the number of shared vehicles.
  • the shared vehicle usage status includes the failure status of the shared vehicle; the acquiring the shared vehicle usage status in the plurality of preset areas at the first moment includes: receiving the The vehicle identification information sent by the user to the terminal device; wherein the vehicle identification information is used to mark whether the shared vehicle in the preset area is faulty.
  • the method further includes: receiving the range of the preset area sent by the operation and maintenance terminal.
  • One of the embodiments of the present application provides a method for recommending information about shared vehicles, which is applied to a terminal device.
  • the method includes: receiving an operation instruction from a user to the terminal device; acquiring characteristic information related to the operation instruction; at least based on The characteristic information determines display information, and the display information includes vehicle recommendation information and/or usage information of the shared vehicle; the display information is displayed on the terminal device page.
  • One of the embodiments of the present application provides an information push system for a shared vehicle.
  • the system includes: a first acquisition module for acquiring characteristic information related to the operation instruction in response to a user's operation instruction to the terminal device; A determination module, configured to determine the display information of the terminal device based on at least the characteristic information, the display information including vehicle recommendation information and/or usage information of the shared vehicle; a transmission module, configured to send to the terminal device The display information.
  • the terminal device includes: a receiving module for receiving an operation instruction from a user to open the terminal device; and a second acquiring module for acquiring Characteristic information related to the operation instruction; a second determining module for determining display information based on at least the characteristic information, the display information including vehicle recommendation information and/or usage information of shared vehicles; a display module for The display information is displayed on the page of the terminal device.
  • One of the embodiments of the present application provides an electronic device that includes at least one processor and at least one memory; the at least one memory is used to store computer instructions; the at least one processor is used to execute the computer instructions. At least part of the instructions to implement the information push method for shared vehicles as described above.
  • One of the embodiments of the present application provides a computer-readable storage medium that stores computer instructions. After the computer reads the computer instructions in the storage medium, the computer executes the aforementioned method for pushing information of shared vehicles.
  • Fig. 1 is a schematic diagram of an application scenario of an information push system for shared vehicles according to some embodiments of the present application
  • Fig. 2 is a schematic diagram of exemplary hardware components and/or software components of an exemplary computing device according to some embodiments of the present application;
  • Fig. 3 is a schematic diagram of exemplary hardware components and/or software components of an exemplary mobile device according to some embodiments of the present application;
  • Fig. 4 is an exemplary module diagram of an exemplary processing device according to some embodiments of the present application.
  • Fig. 5 is an exemplary module diagram of an exemplary terminal device according to some embodiments of the present application.
  • Fig. 6 is an exemplary flowchart of a method for pushing information of a shared vehicle according to some embodiments of the present application
  • FIG. 7 is an exemplary flowchart of a method for pushing information of a shared vehicle according to other embodiments of the present application.
  • FIG. 8 is an exemplary flowchart of a method for pushing information of a shared vehicle according to other embodiments of the present application.
  • FIG. 9 is an exemplary flowchart of a method for pushing information of a shared vehicle according to still other embodiments of the present application.
  • FIG. 10 is an exemplary flowchart of a method for determining a status label of a shared vehicle according to some embodiments of the present application.
  • FIG. 11 is an exemplary flowchart of a method for pushing information of a shared vehicle according to still other embodiments of the present application.
  • Fig. 12 is an exemplary flowchart of a method for pushing information of a shared vehicle according to still other embodiments of the present application.
  • system is a method for distinguishing different components, elements, parts, parts, or assemblies of different levels.
  • the words can be replaced by other expressions.
  • Application scenarios of different embodiments of the present application may include, but are not limited to, one or more web pages, browser plug-ins and/or extensions, user terminals, customized systems, internal company analysis systems, artificial intelligence robots, etc., or any combination thereof. It should be understood that the application scenarios of the system and method disclosed herein are only some examples or embodiments. Those with ordinary skills in this field can apply these methods to other application scenarios without further creative efforts. For example, other similar servers.
  • the "user”, “requester”, “service requester”, and “use requester” described in this application are interchangeable and refer to the party who needs or subscribes to the service, which can be an individual, a tool or Other entities, etc.
  • "operations and maintenance personnel”, “management personnel”, “maintenance personnel”, and “service providers” described in this application are also interchangeable and refer to individuals, tools, or other entities that provide services or assist in providing services.
  • the "user” described in this application may be a party that needs or subscribes to services, or a party that provides services or assists in providing services.
  • the "terminal device” described in this application may refer to a user terminal used by a party that needs or subscribes to a service, or a user terminal used by a party that provides services or assists in providing services.
  • operation instructions can be used to refer to users, requesters, service requesters, operation and maintenance personnel, providers, and services. Or any combination thereof, and can be used interchangeably.
  • the service request can be chargeable or free.
  • the position and/or trajectory of the user in the present application can be obtained by the positioning technology embedded in the user terminal, and the position and/or trajectory of the shared vehicle can be obtained by the positioning technology embedded in the shared vehicle.
  • the location of the user and/or the location of the shared vehicle can be tracked and acquired in real time through positioning technology.
  • the positioning technology used in this application may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), Beidou Navigation System (COMPASS), Galileo Positioning System (GLONASS), Quasi-Zenith Satellite System (QZSS), base station positioning technology , One or any combination of Wi-Fi positioning technology, etc.
  • GPS Global Positioning System
  • GLONASS Global Navigation Satellite System
  • COMPASS Beidou Navigation System
  • GLONASS Galileo Positioning System
  • QZSS Quasi-Zenith Satellite System
  • base station positioning technology One or any combination of Wi-Fi positioning technology, etc.
  • Wi-Fi positioning technology etc.
  • Fig. 1 is a schematic diagram of an application scenario of an information push system for a shared vehicle according to some embodiments of the present application.
  • the information push system 100 for shared vehicles may include a server 110, a network 120, a user terminal (user terminal) 130, a sharing device 140 and a storage 150.
  • the server 110 may, in response to the user's operation instruction to the user terminal 130, obtain the characteristic information related to the operation instruction from the user terminal 130 through the network 120, and determine the vehicle including the shared vehicle based on at least the characteristic information. Recommend information and/or display information of usage information; and send the display information to the user terminal 130 so as to display the display information to the user.
  • the server 110 may process data and/or information obtained from at least one component of the system 100 (for example, the client 130, the shared device 140, and the storage 150) or an external data source (for example, a cloud data center). For example, the server 110 may determine the recommended vehicle based on the characteristic information related to the user's operation instruction and display it to the user. For another example, the server 110 may receive the unlocking instruction sent by the client 130 through the mobile communication network, and control the unlocking of the shared vehicle. For another example, the server 110 may determine the shared vehicle that needs to be upgraded in function according to the shared vehicle status tag.
  • the server 110 may be local or remote.
  • the server 110 may access information and/or data stored in the client 130, the sharing device 140, and the storage 150 via the network 120.
  • the server 110 may directly connect to the client 130, the sharing device 140, and the storage 150 to access the data and/or information stored therein.
  • the server 110 may be implemented on a cloud platform.
  • the cloud platform may include private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, internal cloud, multi-layer cloud, etc., or any combination thereof.
  • the server 110 may be a server or a server group.
  • the server group may be centralized, such as a data center.
  • the server group may also be distributed, such as a distributed system.
  • the server 110 may include a processing device 112.
  • the processing device 112 may process the information and/or data of the service request related to the shared device to perform one or more functions described in this specification. For example, the processing device 112 may obtain the shared vehicle usage status of multiple preset areas at the first time from the user terminal 130 or the memory 150, and compare the shared vehicle usage status at the second time to the preset area stored at the second time according to the shared vehicle usage status at the first time. The usage status of the shared vehicle is updated to generate display information carrying the usage status of the shared vehicle.
  • the processing device 112 may include at least one processing unit (for example, a single-core processing engine or a multi-core processing engine).
  • the processing device 112 includes a central processing unit (CPU), an application specific integrated circuit (ASIC), an application specific instruction set processor (ASIP), a graphics processing unit (GPU), a physical processing unit (PPU), and a digital signal processor.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • ASIP application specific instruction set processor
  • GPU graphics processing unit
  • PPU physical processing unit
  • DSP digital signal processor
  • FPGA Field Programmable Gate Array
  • PLD Programmable Logic Device
  • Controller Microcontroller Unit
  • RISC Reduced Instruction Set Computer
  • Microprocessor etc., or any combination thereof.
  • the processing device 112 may be a part of a terminal device.
  • the processing device 112 may be integrated in the user terminal 130 to receive an operation instruction from the user to the user terminal 130, obtain characteristic information related to the operation instruction; and determine, based at least on the characteristic information, a vehicle recommendation including a shared vehicle The display information of the information and/or usage information, and the display information is displayed on the page of the user terminal 130.
  • the network 120 may provide channels for information exchange.
  • the network 120 may be a single network or a combination of multiple networks.
  • the network 120 may include a cable network, a wired network, an optical fiber network, a telecommunication network, an internal network, the Internet, a local area network (LAN), a wide area network (WAN), a wireless local area network (WLAN), a metropolitan area network ( MAN), Public Switched Telephone Network (PSTN), Bluetooth Network, Zigbee Network, Near Field Communication (NFC) Network, Global System for Mobile Communications (GSM) Network, Code Division Multiple Access (CDMA) Network, Time Division Multiple Access (TDMA) Network, general packet radio service (GPRS) network, enhanced data rate GSM evolution (EDGE) network, broadband code division multiple access (WCDMA) network, high-speed downlink packet access (HSDPA) network, long-term evolution (LTE) network, User Datagram Protocol (UDP) network, Transmission Control Protocol/Internet Protocol (TCP/IP) network, Short Message Service (SMS) network, Wireless Application
  • the network 120 may include one or more network access points.
  • the network 120 may include wired or wireless network access points, such as base stations and/or Internet exchange points 120-1, 120-2, ..., and one or more components of the system 100 may be connected to the network 120 through the access points. To exchange data and/or information.
  • the owner of the user terminal 130 may be the user himself or someone other than the user himself.
  • the owner A of the user terminal 130 may use the user terminal 130 to send a service request for the user B, and/or receive service confirmation and/or information or instructions from the server 110.
  • the owner of the user terminal 130 may be a user of the shared device, or may be an operation and maintenance personnel of the shared device.
  • the user terminal 130 may include various types of devices with information receiving and/or sending functions.
  • the user terminal 130 may include, but is not limited to, a tablet computer 130-1, a notebook computer 130-2, a mobile device 130-3, a desktop computer, etc., or any combination thereof.
  • the user terminal 130 may be a device with a positioning function, so that the user terminal 130 and/or location information of the user may be provided.
  • the location-related information may include location, altitude, speed, acceleration, time, and so on.
  • the system 100 may also include other devices with positioning functions (for example, satellite positioning devices, GPS positioning devices), and these devices may interact with components in the system 100 (for example, the user terminal 130, the sharing device 140, etc.) Communicate to determine information about its location.
  • the user terminal 130 may include a short-range communication device.
  • Short-distance communication technology refers to wireless communication technology that works in a local range with a distance of millimeters to kilometers.
  • short-range communication technologies can include Huawei Hilink protocol, WiFi (IEEE 802.11 protocol), Mesh, Bluetooth, ZigBee, Thread, Z-Wave, NFC (Near Field Communication), UWB (No Carrier Communication) Technology, Ultra Wideband), LiFi (Light Fidelity), etc.
  • the user terminal 130 may establish communication with the sharing device 140 through a short-range communication device.
  • the client 130 may process information and/or data.
  • the user terminal 130 may respond to the user's operation instruction to process characteristic information related to the operation instruction.
  • the client 130 may be used to receive and/or display the information sent by the server 110.
  • the user end 130 may display the display information of the shared vehicle obtained from the server 110 on a page of the user end to output to the user.
  • the user terminal 130 may send the operation instruction and/or characteristic information related to the operation instruction to one or more components in the system 100.
  • the user terminal 130 may send the first location where the user executes the operation instruction, the user's historical travel information and/or planned travel information to the server 110 for processing, or to the memory 150 for storage.
  • the shared device 140 may include a shared vehicle.
  • shared vehicles may include, but are not limited to, shared bicycles 140-1, shared motorcycles 140-2, shared electric motorcycles, shared cars, and the like.
  • the shared vehicle may include a vehicle terminal, and the vehicle terminal may implement network communication with the server 110.
  • signal connection with server 110 through a mobile communication network receiving various control instructions and information issued by server 110, or uploading its own status information to server 110, including but not limited to whether locks are opened or closed, and remaining battery power , Moving speed or positioning information, etc.
  • a short-range communication device may be integrated in the vehicle terminal, and the vehicle terminal may implement short-range communication with the user terminal 130 through the short-range communication device.
  • the vehicle terminal may have signal connections with various sensors on the vehicle, and may also have signal connections with various execution components on the vehicle.
  • the vehicle terminal can be connected to a speed sensor on the vehicle.
  • the vehicle terminal may have signal connections with components such as locks and indicator lights on the vehicle to control the opening or closing of components such as locks and indicator lights.
  • the shared vehicle may include an input device and an output device.
  • Exemplary input devices may include keyboard, mouse, touch screen, microphone, etc., or any combination thereof.
  • Exemplary output devices may include display devices, speakers, printers, projectors, etc., or any combination thereof.
  • Exemplary display devices may include liquid crystal displays (LCD), light emitting diode (LED)-based displays, flat panel displays, curved displays, television equipment, cathode ray tubes (CRT), etc., or any combination thereof.
  • the shared vehicle may include a positioning device for providing location-related information (for example, GPS signal information) of the shared vehicle.
  • Exemplary location-related information may include location, altitude, speed, acceleration, time, and so on.
  • the shared vehicle may include a wireless module for scanning wireless information, for example, wifi signal information, Bluetooth signal information, and so on.
  • a shared vehicle is mainly used as an example to describe the information pushing method of a shared vehicle. It is understandable that in some embodiments, the information pushing method provided in this specification can also be applied to other shared devices, such as shared umbrellas, Shared skateboards, shared charging treasure 140-3 and other types of shared items.
  • the memory 150 may store data and/or instructions that can be executed or used by the processing device 112 to complete the exemplary methods described in this specification.
  • the memory 150 may include mass memory, removable memory, volatile read-write memory, read-only memory (ROM), etc., or any combination thereof.
  • Exemplary mass storage devices may include magnetic disks, optical disks, solid state disks, and the like.
  • Exemplary removable storage may include flash drives, floppy disks, optical disks, memory cards, compact disks, magnetic tapes, and the like.
  • An exemplary volatile read-write memory may include random access memory (RAM).
  • Exemplary RAM may include dynamic random access memory (DRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), static random access memory (SRAM), thyristor random access memory (T-RAM), zero capacitance Random access memory (Z-RAM), etc.
  • Exemplary read-only memory may include mask-type read-only memory (MROM), programmable read-only memory (PROM), erasable programmable read-only memory (PEROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM, digital versatile disk read-only memory, etc.
  • the storage 150 may be implemented on a cloud platform.
  • the cloud platform may include private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, internal cloud, multi-layer cloud, etc., or any combination thereof.
  • At least one component in the system 100 can access data or instructions stored in the memory 150 via the network 120.
  • the storage 150 may be directly connected to the server 110 as a back-end storage. In some embodiments, the storage 150 may be a part of the server 110, the client 130, and/or the shared device 140.
  • Fig. 2 is a schematic diagram of exemplary hardware components and/or software components of an exemplary computing device according to some embodiments of the present application.
  • the computing device may be a computer, such as the server 110 in FIG. 1 and/or a computer with specific functions, configured to implement any specific system according to some embodiments of the present application.
  • the computing device 200 may be configured to implement one or more functions disclosed in this application.
  • the server 110 may be implemented by a computer hardware device such as a computing device 200, a software program, firmware, or any combination thereof.
  • Figure 2 only depicts one computing device.
  • the function of the computing device which provides functions that may be required for sharing vehicle display information, can be implemented by a group of similar platforms in a distributed mode to disperse the processing load of the system.
  • the computing device 200 may include a processor 210, a memory 220, an input/output 230, and a communication port 240.
  • the processor 210 can execute calculation instructions (program code) and perform the functions of the shared vehicle information pushing system 100 described in this specification.
  • the calculation instructions may include programs, objects, components, data structures, procedures, modules, and functions (the functions refer to the specific functions described in this specification).
  • the processor 210 may process feature information related to operating instructions obtained from any other components of the system 100.
  • the processor 210 may include a microcontroller, a microprocessor, a reduced instruction set computer (RISC), an application specific integrated circuit (ASIC), an application specific instruction set processor (ASIP), a central processing unit (CPU) , Graphics processing unit (GPU), physical processing unit (PPU), microcontroller unit, digital signal processor (DSP), field programmable gate array (FPGA), advanced RISC machine (ARM), programmable logic device, and Any circuit, processor, etc. that perform one or more functions, or any combination thereof.
  • RISC reduced instruction set computer
  • ASIC application specific integrated circuit
  • ASIP application specific instruction set processor
  • CPU central processing unit
  • GPU Graphics processing unit
  • PPU physical processing unit
  • DSP digital signal processor
  • FPGA field programmable gate array
  • ARM advanced RISC machine
  • operation A and operation B may also be shared or shared by two or more different processors in the computing device 200. They are performed separately (for example, the first processor performs operation A and the second processor performs operation B, or the first processor and the second processor jointly perform operations A and B).
  • the memory 220 may store data/information obtained from any other components of the system 100 (for example, the processing device 112, the client 130, and/or the sharing device 140).
  • the memory 220 may include mass memory, removable memory, volatile read and write memory, read-only memory (ROM), etc., or any combination thereof.
  • Exemplary mass storage devices may include magnetic disks, optical disks, solid state drives, and the like.
  • Removable storage can include flash drives, floppy disks, optical disks, memory cards, compact disks, and magnetic tapes.
  • Volatile read and write memory may include random access memory (RAM).
  • RAM can include dynamic RAM (DRAM), double-rate synchronous dynamic RAM (DDR SDRAM), static RAM (SRAM), thyristor RAM (T-RAM), zero capacitance (Z-RAM), and so on.
  • ROM can include mask ROM (MROM), programmable ROM (PROM), erasable programmable ROM (PEROM), electrically erasable programmable ROM (EEPROM), compact disk ROM (CD-ROM) and digital universal disk ROM Wait.
  • the memory 220 may store one or more programs and/or instructions for executing the exemplary methods described in this application.
  • the input/output 230 may be used to input or output signals, data or information. In some embodiments, the input/output 230 may enable the user to communicate with the system 100. In some embodiments, the input/output 230 may include an input device and an output device. Exemplary input devices may include a keyboard, a mouse, a touch screen, a microphone, etc., or any combination thereof. Exemplary output devices may include display devices, speakers, printers, projectors, etc., or any combination thereof. Exemplary display devices may include liquid crystal displays (LCD), light emitting diode (LED)-based displays, flat panel displays, curved displays, television equipment, cathode ray tubes (CRT), etc., or any combination thereof.
  • LCD liquid crystal displays
  • LED light emitting diode
  • CRT cathode ray tubes
  • the communication port 240 may be connected to a network (for example, the network 120) for data communication.
  • the communication port 240 can establish a connection between the processing device 112 and the client 130, the sharing device 140, and/or the storage 150.
  • the connection may be a wired connection, a wireless connection, or a combination of both. Wired connections can include cables, optical cables, or telephone lines, etc., or any combination thereof.
  • the wireless connection may include Bluetooth, Wi-Fi, WiMax, WLAN, ZigBee, mobile networks (for example, 3G, 4G, or 5G, etc.), etc., or any combination thereof.
  • the communication port 240 may be a standardized port, such as RS232, RS485, and so on.
  • the communication port 240 may be a specially designed port.
  • Fig. 3 is a schematic diagram of exemplary hardware components and/or software components of an exemplary mobile device according to some embodiments of the present application.
  • the mobile device 300 may include a communication unit 310, a display unit 320, a graphics processing unit (GPU) 330, a central processing unit (CPU) 340, an input/output unit 350, a memory 360, and a storage unit 390.
  • the mobile device 300 may also include any other suitable components, including but not limited to a system bus or a controller (not shown in the figure).
  • mobile operating system 370 e.g., Android, Windows Etc.
  • application program 380 can be loaded from the storage unit 390 into the memory 360 so as to be executed by the central processing unit 340.
  • the application program 380 may include a browser or any other suitable mobile application program for receiving and presenting display information or other information related information from the server 110.
  • the user interaction of the information flow may be implemented through the input/output unit 350, and provided to the server 110 and/or other components of the information push system 100 of the shared vehicle through the network 120.
  • a computer hardware platform may be used as a hardware platform for one or more elements described in this application.
  • a computer with user interface elements can be used to implement the functions of a personal computer (PC) or any other type of workstation or terminal device. If properly programmed, the computer can also act as the server described in this application.
  • PC personal computer
  • Fig. 4 is an exemplary block diagram of an exemplary processing device according to some embodiments of the present application.
  • the processing device may include a first acquisition module 410, a first determination module 420, a control module 430, an analysis module 440, and a transmission module 450.
  • These modules can also be implemented as an application program or a set of instructions read and executed by a processing device.
  • the module can be any combination of hardware circuits and applications/instructions. For example, when a processing device or processor executes an application program/a set of instructions, the module may be a part of the processor.
  • the first obtaining module 410 may be used to obtain data or information.
  • the first obtaining module 410 may be used to obtain characteristic information related to the operation instruction.
  • the feature information may include user input information (for example, the starting place, destination, shared vehicle status tag of the user input, etc.), the first position where the user executes the operation instruction, the initiation time of the operation instruction, and User’s travel information, etc.
  • the first obtaining module 410 may be used to obtain user information.
  • the user information may include, but is not limited to, the user's historical travel information, historical order information, planned travel information, user feedback information (for example, first feedback information, second feedback information), etc., or any combination thereof.
  • the first obtaining module 410 may be used to obtain shared vehicle usage information input by a user through a terminal device (for example, an operation and maintenance terminal or a client). In some embodiments, the first obtaining module 410 may obtain the location information of the user or the shared device. For example, the first obtaining module 410 may obtain the positioning position of the user terminal 130 through the positioning device of the user terminal 130 as the first position where the user executes the operation instruction or the third position of the user. For another example, the first obtaining module 410 may obtain the second location of the shared vehicle from the positioning device of the shared vehicle. In some embodiments, the first obtaining module 410 may be used to receive the range of the preset area sent by the terminal device (for example, the operation and maintenance terminal). In some embodiments, the first obtaining module 410 may be used to obtain the preset upgrade rule corresponding to the selected status label of the shared vehicle.
  • a terminal device for example, an operation and maintenance terminal or a client.
  • the first obtaining module 410 may obtain the location information of the user or the
  • the first determining module 420 may be used to determine the display information.
  • the display information may include vehicle recommendation information and/or usage information of the shared vehicle.
  • the first determining module 420 may be used to determine the travel destination of the user. For example, the first determining module 420 may determine multiple historical travel routes based on multiple historical travel information of the user, and the travel start time corresponding to each historical travel route; among the multiple historical travel routes, the travel start The historical travel route whose time is closest to the initiation time of the user operation instruction is determined as the estimated travel route; the destination corresponding to the estimated travel route is determined as the user's travel destination.
  • the first determination module 420 may obtain the travel mode and travel time of the user's planned travel information; determine the travel origin of the planned travel information based on the travel mode; and based on the first location where the user executes the operation instruction and the planned travel time The distance between the travel origin of the travel information, determine the estimated arrival time from the first location to the travel origin of the planned travel information; and respond to the estimated arrival time earlier than the planned Based on the travel time of the travel information, it is determined that the travel origin of the planned travel information is the travel destination of the user.
  • the first determining module 420 may further include a destination determining unit for determining the travel destination of the user.
  • the first determining module 420 may further include a recommendation unit 422, a screening unit 424, an information update unit 426, and the like.
  • the recommendation unit 422 may be used to determine a recommended vehicle. For example, the recommendation unit 422 may determine the first recommended vehicle from a plurality of shared vehicles within a preset distance range value from the first location where the user executes the operation instruction based on the determined travel destination of the user. Specifically, the recommendation unit 422 may determine the remaining cruising range of each shared vehicle among the plurality of shared vehicles; in response to the distance between the user’s travel destination and the preset return area being less than the first preset distance value, determine The estimated travel mileage between the first location and the preset return area; based on the remaining cruising range and estimated travel mileage of each of the multiple shared vehicles, it is determined that among the multiple shared vehicles The shared vehicle that meets the first preset condition is the first recommended vehicle.
  • the first preset condition may include that the distance difference between the remaining cruising range of the shared vehicle and the estimated travel distance is greater than the second preset distance value, and the remaining cruising range value is the smallest among the plurality of shared vehicles .
  • the recommending unit 422 may determine the shared vehicle with the largest remaining cruising range among the multiple shared vehicles in response to the distance between the user’s travel destination and the preset return area being not less than the first preset distance value. The vehicle is the first recommended vehicle.
  • the recommendation unit 422 may instruct the user to determine not to use the first recommended vehicle in response to the user's first feedback information about the first recommended vehicle, based on the remaining cruising range of the multiple shared vehicles and/or the user's input For the destination, the second recommended vehicle is determined from the plurality of shared vehicles.
  • the recommendation unit 422 may filter the shared vehicles corresponding to the status tags from various types of shared vehicles according to the status tags of the shared vehicles input by the user as the third recommended vehicle.
  • the recommendation unit 422 may determine that the fourth recommended vehicle is the updated recommended vehicle when the second feedback information indicates that the user has not found the recommended vehicle.
  • the recommending unit 422 may further include a first recommending unit, a second recommending unit, a third recommending unit, and a fourth recommending unit, which are used to determine the first recommended vehicle, the second recommended vehicle, and the third recommended vehicle, respectively. Recommended vehicle and fourth recommended vehicle.
  • the screening unit 424 may be used to screen the corresponding shared vehicles according to the status tags. For example, the screening unit 424 may filter the shared vehicles corresponding to the status tags from various types of shared vehicles according to the status tags of the shared vehicles input by the user.
  • the information update unit 426 may be used to update the usage status of the shared vehicle.
  • the information update unit 426 may update the shared vehicle usage status stored in the preset area at the second time according to the acquired shared vehicle usage status at the first moment, and generate display information carrying the shared vehicle usage status.
  • the information update unit 426 may receive the number of shared vehicles placed in the preset area sent by the operation and maintenance end; or when it receives one of the shared vehicles in the preset area sent by the operation and maintenance end When scanning the code information for the first time, add one to the number of shared vehicles corresponding to the preset area to update the number of shared vehicles.
  • the information update unit 426 may reduce the number of shared vehicles corresponding to the preset area by one when receiving the second scan code information of one of the shared vehicles in the preset area sent by the client. Update the number of shared vehicles.
  • the information update unit 426 may receive the vehicle identification information sent by the user through the terminal device, and update the fault condition of the shared vehicle according to the vehicle representation information. Among them, the vehicle identification information is used to mark whether the shared vehicle in the preset area is faulty.
  • the control module 430 can be used to control the shared device.
  • the shared vehicle may be equipped with a reminder device, and the control module 430 may calculate the distance between the user’s third position and the recommended vehicle’s second position; when the distance between the user’s third position and the recommended vehicle’s second position is less than At the third preset distance value, control the reminding device of the shared vehicle to send a reminding signal.
  • the reminding device may be a flashlight.
  • the control module 430 may control the flashlight to flash, wherein the smaller the distance between the third position of the user and the second position of the recommended vehicle, the higher the frequency of controlling the flash to flash.
  • control module 430 may also be used to change the vehicle state corresponding to the recommended vehicle to the reserved state; and when receiving the riding start instruction sent by the user, control the recommended vehicle to unlock. In some embodiments, the control module 430 may also be used to upgrade the functions of the selected shared vehicles located in the target area according to a preset upgrade rule corresponding to the status label.
  • control module 430 may further include a calculation unit 432 and a control unit 434.
  • the calculation unit 432 may be used to calculate the distance between the third position of the user and the second position of the recommended vehicle
  • control unit 434 may be used to calculate the distance between the third position of the user and the second position of the recommended vehicle when the distance between the third position of the user and the second position of the recommended vehicle is less than the third position.
  • the reminder device that controls the shared vehicle sends a reminder signal.
  • the analysis module 440 may be used to analyze the status tag of the shared vehicle.
  • the analysis module 440 may be used to obtain at least one state data sent by at least one shared vehicle; for each state data sent by each shared vehicle, obtain the state type to which the state data belongs, and obtain the preset evaluation corresponding to the state type Strategy: For the status data of each status type sent by each shared vehicle, the preset evaluation strategy corresponding to the status type is used to analyze, and the status label corresponding to the shared vehicle sending the status data of the status type is obtained.
  • the analysis module 440 may obtain a preset evaluation strategy in response to a configuration operation on the strategy configuration interface of the terminal.
  • the analysis module 440 may further include a statistics unit 442 and an analysis unit 444.
  • the statistical unit 442 may be used to count the number of shared vehicles included in each preset area that are filtered out and correspond to the status tag input by the user, and the analysis unit 444 may be used to calculate the number of shared vehicles included in each preset area that are filtered out. The number of vehicles determines the target area that needs to be upgraded.
  • the statistical unit 442 may select a reference area from each preset area including the filtered shared vehicle, and calculate each preset area except the reference area among the preset areas including the filtered shared vehicle. The data difference between the number of shared vehicles selected in the reference area and the number of shared vehicles selected in the reference area; the analysis unit 444 may determine the target area that needs to be upgraded according to the data difference.
  • the transmission module 450 may be used to transmit information. For example, the transmission module 450 may transmit the determined display information to the terminal device. In some embodiments, the transmission module 450 may be used to send relevant information about the recommended vehicle to the terminal device. For example, the transmission module 450 may send the remaining cruising range corresponding to the first recommended vehicle to the user terminal 130 for display to the user. In some embodiments, the transmission module 450 may be used to send navigation information to a terminal device (for example, the user terminal 130). For example, the transmission module 450 may send navigation information from the third position to the second position to the user terminal 130 according to the user's third position and the second position of the recommended vehicle, and the user terminal 130 may send the navigation information to the user terminal 130. Show it to users. In some embodiments, the transmission module 450 may also be used to separately send a control instruction to each of the selected shared vehicles to prohibit the selected shared vehicles from sending status data corresponding to the shared vehicle.
  • processing device 400 and its modules shown in FIG. 4 may be implemented in various ways.
  • the processing device 400 and its modules may be implemented by hardware, software, or a combination of software and hardware.
  • the hardware part can be implemented using dedicated logic;
  • the software part can be stored in a memory and executed by an appropriate instruction execution system, such as a microprocessor or dedicated design hardware.
  • processor control codes for example on a carrier medium such as a disk, CD or DVD-ROM, such as a read-only memory (firmware Such codes are provided on a programmable memory or a data carrier such as an optical or electronic signal carrier.
  • the system and its modules of this application can not only be implemented by hardware circuits such as very large-scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, etc., or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc. It may also be implemented by software executed by various types of processors, or may be implemented by a combination of the above hardware circuit and software (for example, firmware).
  • the above description of the processing device 400 and its modules is only for convenience of description, and does not limit this specification within the scope of the embodiments mentioned. It can be understood that for those skilled in the art, after understanding the principle of the system, it is possible to arbitrarily combine various modules, or form a subsystem to connect with other modules without departing from this principle.
  • the first acquisition module 410, the first determination module 420, the control module 430, the analysis module 440, and the transmission module 450 may be different modules in a system, or may be a module to implement the above two or two. The functions of more than one module.
  • the first acquisition module 410, the first determination module 420, the control module 430, the analysis module 440, and the transmission module 450 may share a storage module, and each module may also have its own storage module. Such deformations are all within the protection scope of this specification.
  • Fig. 5 is an exemplary module diagram of an exemplary terminal device according to some embodiments of the present application.
  • the terminal device may include a receiving module 510, a second acquiring module 520, a second determining module 530, and a display module 540.
  • These modules can also be implemented as an application program or a set of instructions read and executed by the processor.
  • the module can be any combination of hardware circuits and applications/instructions.
  • the central processing unit 340 executes an application program/a set of instructions, the module may be a part of the processor.
  • the receiving module 510 may be used to receive operation instructions of the user on the terminal device.
  • the operation instruction may include the user opening the display page of the terminal device, sharing service APP, etc., and/or the user initiates a car service request, location acquisition request, etc. through the terminal device, and/or the user inputs feedback information through the terminal device.
  • the receiving module 510 may also be used to receive instructions and/or information sent by a server (for example, the server 110).
  • the receiving module 510 may receive display information, reminder information, alarm information, etc. of the shared vehicle from the server 110.
  • the second obtaining module 520 may be used to obtain characteristic information related to the operation instruction.
  • the second obtaining module 520 may obtain characteristic information related to the operation instruction from the terminal device.
  • the second obtaining module 520 may obtain the first position of the user executing the operation instruction, the third position of the user, etc. through the positioning device of the user terminal 130.
  • the second acquiring module 520 may acquire the travel information, status label, feedback information, and the initiation time of the operation instruction input by the user through the user terminal 130.
  • the second obtaining module 520 may obtain feature information related to the operation instruction from a server (for example, the server 110).
  • the second obtaining module 520 may obtain corresponding characteristic information from the server 110 based on a user operation instruction.
  • the second determining module 530 may be used to determine the display information.
  • the display information may include vehicle recommendation information and/or usage information of the shared vehicle, prompt information, and the like.
  • the second determining module 530 may determine the display information based on the characteristic information related to the operation instruction through the processor (for example, the central processing unit 340). For example, the second determination module 530 may determine recommended vehicles such as the first recommended vehicle and the second recommended vehicle and/or vehicle recommendation information based on the first location where the user executes the operation instruction, the initiation time of the operation instruction, and the user's travel information.
  • the second determining module 530 may filter out the shared vehicles corresponding to the status tags from various types of shared vehicles based on the shared vehicle status tags input by the user, and/or filter out the shared vehicles included in each preset area. The number of shared vehicles determines the target area that needs to be upgraded. In some embodiments, the second determining module 530 may obtain related display information from the server based on the feature information related to the operation instruction.
  • the display module 540 may be used to display display information.
  • the display module 540 may be used to display information such as the recommended vehicle, the remaining cruising range of the recommended vehicle, the navigation information of the recommended vehicle, the usage information of the vehicle, etc., or any combination thereof on the display interface.
  • the terminal device 500 may further include a transmission module.
  • the transmission module may be used to transmit data or information with the server.
  • the terminal device 500 may transmit or obtain display information, operation instruction characteristic information, etc. from the server through its transmission module.
  • the terminal device 500 and its modules shown in FIG. 5 can be implemented in various ways.
  • the terminal device 500 and its modules may be implemented by hardware, software, or a combination of software and hardware.
  • the hardware part can be implemented using dedicated logic;
  • the software part can be stored in a memory and executed by an appropriate instruction execution system, such as a microprocessor or dedicated design hardware.
  • processor control codes for example on a carrier medium such as a disk, CD or DVD-ROM, such as a read-only memory (firmware Such codes are provided on a programmable memory or a data carrier such as an optical or electronic signal carrier.
  • the system and its modules of this application can not only be implemented by hardware circuits such as very large-scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, etc., or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc. It may also be implemented by software executed by various types of processors, or may be implemented by a combination of the above hardware circuit and software (for example, firmware).
  • terminal device 500 and its modules is only for convenience of description, and does not limit this specification within the scope of the embodiments mentioned. It can be understood that for those skilled in the art, after understanding the principle of the system, it is possible to arbitrarily combine various modules, or form subsystems to connect with other modules without departing from this principle.
  • Fig. 6 is an exemplary flowchart of a method for pushing information of a shared vehicle according to some embodiments of the present application.
  • the process 600 may be executed by a processing device (for example, the processing device 112 shown in FIG. 1).
  • the process 600 may be stored in a storage device (for example, the memory 150 or a storage unit of a processing device) in the form of a program or instruction.
  • the process 600 may be implemented.
  • the process 600 may utilize one or more additional operations not described below, and/or not be completed by one or more operations discussed below.
  • the order of operations shown in FIG. 6 is not restrictive. As shown in FIG. 6, the process 600 may include the following steps.
  • Step 610 In response to the user's operation instruction to the terminal device, obtain characteristic information related to the operation instruction. In some embodiments, step 610 may be performed by the first obtaining module 410.
  • the terminal device may include a client used by users of the shared vehicle, and/or an operation and maintenance terminal used by the operation and maintenance personnel of the shared platform, and the like.
  • users of shared vehicles can initiate service requests related to shared vehicles, return vehicles, and search for vehicles through the client.
  • Operation and maintenance personnel refer to management personnel who maintain, schedule, and repair shared equipment. Operation and maintenance personnel can initiate requests for vehicle upgrades, maintenance, scheduling, and failure reporting through the operation and maintenance terminal.
  • the operation instruction may be used to reflect the operation of the terminal device by the user (for example, a shared vehicle user and/or operation and maintenance personnel).
  • the operation instructions may include but are not limited to the user opening the shared vehicle APP of the terminal device, or clicking the button, page or link in the APP after opening the APP, or inputting search instructions in the browser or other pages.
  • the form of the operation instruction may include voice, text, facial motion (for example, blinking), gesture, touch screen operation, etc., or any combination thereof.
  • the characteristic information related to the operation instruction may include, but is not limited to, the initiation time of the operation instruction, the first position when the user executes the operation instruction, the user's travel information, the user's order information, and the shared vehicle status tag input by the user. , The destination entered by the user, etc., or any combination thereof.
  • the processing device may obtain feature information related to the operation instruction from a server (for example, the server 110). In some embodiments, the processing device may obtain feature information related to the operation instruction from the terminal device (for example, the user terminal 130). In some embodiments, the processing device may obtain the characteristic information related to the operation instruction from any reasonable channel and/or through any feasible method, which is not limited in this specification.
  • Step 620 Determine display information of the terminal device based on at least the characteristic information.
  • step 620 may be performed by the first determining module 420.
  • Display information refers to information related to operation instructions presented to the user through a terminal device (for example, the user terminal 130).
  • the display information may include vehicle recommendation information of the shared vehicle, and/or usage information, and/or status information of the vehicle.
  • shared vehicle recommendation information may include the recommended vehicle, location information of the recommended vehicle, and mileage information of the recommended vehicle
  • shared vehicle usage information may include the number of available shared vehicles nearby, whether the vehicle is faulty, etc.
  • vehicle status information may include Vehicle age, model, color, life, fuel/power consumption, etc.
  • the processing device may determine based on at least one of the first position when the user executes the operation instruction, the initiation time of the operation instruction, the user travel information, the user input destination, the shared vehicle status tag input by the user, etc. Recommended vehicle.
  • the first determination module 420 may determine the travel destination of the user based on the first location, the initiation time of the operation instruction, and the travel information of the user; based on the distance between the travel destination and the preset return area, from the distance The first recommended vehicle is determined among the multiple shared vehicles within the preset distance range value of the first position.
  • the first determination module 420 may respond to the user’s first feedback information indicating that the user determines not to use the first recommended vehicle, based on the remaining cruising range of the multiple shared vehicles and/or the user’s input destination, from The second recommended vehicle is determined among the plurality of shared vehicles.
  • the first determining module 420 may filter various types of shared vehicles according to the status tag input by the user, and select the shared vehicle corresponding to the status tag as the third recommended vehicle.
  • the determination of recommended vehicles please refer to other parts of this specification (for example, Figures 7-8 and related descriptions), which will not be repeated here.
  • the processing device may determine shared vehicle usage information based on the characteristic information.
  • the first determining module 420 may obtain the usage of shared vehicles in multiple preset areas at the first moment; according to the usage of the shared vehicles at the first moment, use the shared vehicles in the preset area stored at the second moment. The situation is updated to generate display information carrying the usage of the shared vehicle.
  • the determination of the shared vehicle usage information please refer to other parts of this specification (for example, Figure 11 and related descriptions), which will not be repeated here.
  • Step 630 Send the display information to the terminal device.
  • step 630 may be performed by the transmission module 450.
  • the processing device may send the determined display information to the terminal device, so that the terminal device can display the display information to the user.
  • the processing device may provide the user with navigation information from the third location to the second location based on the user's third location and the recommended vehicle's second location.
  • the third position of the user refers to the current position of the user.
  • the third position of the user may be the same as or different from the first position when the user executes the operation instruction. For example, after the terminal device receives the display information and displays it to the user, the user has walked a certain distance from the first position, and the third position of the user at this time is the position after the user sees the display information.
  • the processing device may update the user’s third position in real time and calculate the distance between the user’s third position and the second position of the recommended vehicle.
  • control the reminding device of the shared vehicle to send a reminding signal.
  • the processing device may control the flashlight to flash more frequently as the distance between the third position of the user and the second position of the recommended vehicle is smaller.
  • the processing device may control the corresponding recommended vehicle to automatically unlock when receiving the riding start instruction sent by the user.
  • the riding start instruction may be the user clicking the "OK to use the shared vehicle" button in the APP, or the user clicking the "Unlock” button in the shared vehicle APP, etc.
  • the processing device may also count the number of shared vehicles included in each preset area that are filtered out according to the status label; according to the number of filtered shared vehicles included in each preset area, it is determined that a function upgrade is required Target area.
  • the operation and maintenance personnel or the server can upgrade the functions of the selected shared vehicles located in the target area according to the preset upgrade rules corresponding to the status tags. For more information about status labels and function upgrades, you can refer to other parts of this manual (for example, Figure 9-10 and related descriptions), which will not be repeated here.
  • Fig. 7 is an exemplary flowchart of a method for pushing information of a shared vehicle according to other embodiments of the present application.
  • the information push method provided in this embodiment can predict the user’s travel destination based on the predicted travel destination based on the first location where the user executes the operation instruction, the initiation time of the operation instruction, and the user’s travel information.
  • Vehicle recommendation is based on the distance between the user’s travel destination and the preset return area.
  • This method can recommend a vehicle suitable for the user based on the distance between the user’s travel destination and the preset return area to meet the user’s travel needs. .
  • the probability that the vehicle can be returned to the preset return area can be improved, and the management and scheduling of the vehicle can be realized through the reasonable use of the user, which helps to improve the rationality of vehicle scheduling and vehicle management The convenience.
  • the process 700 may be executed by a processing device (for example, the processing device 112 shown in FIG. 1).
  • the process 700 may be stored in a storage device (for example, the memory 150 or a storage unit of a processing device) in the form of a program or instruction.
  • the process 700 may be implemented.
  • the process 700 may utilize one or more additional operations not described below, and/or not be completed by one or more operations discussed below.
  • the order of operations shown in FIG. 7 is not restrictive. As shown in FIG. 7, the process 700 may include the following steps.
  • Step 710 Determine the travel destination of the user based on the first location where the user executes the operation instruction, the initiation time of the operation instruction, and the user travel information. In some embodiments, step 710 may be performed by the first determining module 420.
  • the processing device may acquire the first position where the user executes the operation instruction, the initiation time of the operation instruction, and the user travel information when detecting that the user's operation instruction to the terminal device is to initiate a car service request. In some embodiments, the processing device may determine that the user initiates a car service request when detecting that the user opens an application on the terminal device that matches the sharing platform; or, when the interface of the corresponding application is designed, Design a start or other related buttons. When the user clicks to trigger this button, it is determined that the user initiates a car service request.
  • the processing device may, when detecting the user’s car service request, obtain the user’s first location when the car service request is received and the request time when the car service request is detected (that is, the initiation of the operation instruction). time).
  • the user's first location is the location where the user is when he initiates the car service request.
  • the location of the first location of the user may be the location of the terminal device used by the user when the user sends a car service request, which is tracked by the positioning device; or the first location of the user may be that the user is in the application
  • the application pops up a query window, and then the user enters the starting place of the car service request, and the location determined according to the input starting place.
  • the processing device may determine that the user is requesting the use of the car based on the obtained travel information of the user, the user's first location, and the request time when the user initiates a car service request (that is, the initiation time of the operation instruction).
  • a car service is requested, a travel route may be selected, and the user's travel destination this time is predicted based on the travel route.
  • the user's travel information may include two aspects.
  • One aspect is the historical travel information of the vehicle used by the user before, and the historical travel information includes the user's travel start time and travel route information; the other
  • the aspect is the user's planned travel information, which includes the user's planned travel time, planned travel destination, planned travel mode, and other information.
  • the requested time may be used in multiple pieces of historical travel information to determine a filter condition that is closer to the user's travel information this time, or may be used as a basis for whether the user considers using a vehicle in the planned travel information.
  • the processing device may determine multiple historical travel routes based on the multiple pieces of historical travel information of the user, and the travel start time corresponding to each historical travel route; In the historical travel route, the historical travel route that is closest to the travel start time and the initiation time of the operation instruction (for example, the request time when the user initiates a car service request) is determined as the target route (that is, the estimated travel route); and determine The destination corresponding to the target route is the user's travel destination this time.
  • the target route that is, the estimated travel route
  • the user’s historical travel information When the user uses the app to select vehicles and ride, the user’s historical travel information will be saved in the app. According to the analysis of the user’s historical travel information, it can be known that the user is more inclined to ride in a certain period of time destination. For example, the user’s historical travel information shows that in the time period of 8:00-9:00 am, under normal circumstances, users are accustomed to riding to the company by bicycle, so it can be based on whether the time when the user initiates a car service request is within this time period. Inside, to determine the travel destination that the user may want to go to.
  • a horizontal comparison can be used to comprehensively count which historical travel route the user has in the same period of time (for example, several days or weeks, etc.) If the number of occurrences is the most, the destination of the historical travel route with the most occurrences is determined as the user's travel destination this time.
  • the processing device can obtain the planned travel mode and planned travel time of the planned travel information; based on the planned travel mode, determine the travel origin of the planned travel information; based on the user's first The distance between a location and the travel origin of the planned travel information, determining the estimated arrival time from the first location to the travel origin of the planned travel information; in response to the estimated arrival time being earlier than the planned travel Time, determine the travel origin of the planned travel information as the user's travel destination this time.
  • the planned travel destination of the user's planned travel information is far away from the user's current location, for example, cross-provincial, cross-border, and cross-city travel.
  • the user can choose the corresponding travel mode according to the travel destination, such as , It can be by plane, train, passenger car or even ship, etc.
  • users need to take the corresponding transportation means such as the airport, railway station, passenger station and wharf.
  • the airport, railway station, passenger station, and wharf are determined as the user's travel origin.
  • the user needs to take a train from City B to City S on a business trip.
  • the planned trip information shows that the driving time of the train selected by the user is 10:00 am, and the user’s location is 15km away from the train station in City B.
  • the processing device receives the user
  • the service request time is 8:00 in the morning.
  • the average human riding speed is 15km/h-22km/h. Calculated at the slowest riding speed, it will arrive at 9:00 in one hour.
  • the train station is before the driving time of 10:00. Therefore, the user can reach the train station by cycling, and the train station can be used as the user's destination for this trip.
  • the processing device may obtain the user's information within a preset time interval (for example, according to the user's identity on the application (for example, user name, user ID, user mobile phone number, etc.) Multiple historical travel information within half a month, within one month, within three months, within one year, etc.).
  • the processing device may obtain the user's historical travel information from a database (for example, the memory 150).
  • the processing device may obtain it from the user's travel plan table.
  • the processing device may obtain the user's historical travel information and/or planned travel information in any other feasible manner and from any other reasonable channel, which is not limited in this specification.
  • Step 720 Obtain multiple shared vehicles within a preset distance range value from the first position, and the remaining cruising range of each shared vehicle.
  • step 720 may be performed by the first obtaining module 410 or the first determining module 420.
  • the maximum distance that the user can find the shared vehicle can be used as a reference. For example, 20 meters, 50 meters, 100 meters, 200 meters, 300 meters, 500 meters, 1 kilometers and other users can walk from the first location to the current parking location of the shared vehicle. Take shared motorcycles as an example. Under normal circumstances, shared motorcycles will stop at a fixed return point (that is, the preset return area). When calculating the distance between the user's first position and the vehicle, it can be approximated as the user's first position. The distance between the location and the fixed drop-off point. In some embodiments, whether it is a vehicle or a fixed drop-off point, the service platform can be located at their location.
  • a positioning device can be installed in a shared vehicle to ensure that the background can track the location of the vehicle in real time. Ensure that the vehicle is located quickly and prevent the vehicle from being lost.
  • the processing device may set the preset distance range to 0-300 meters, and obtain multiple shared vehicles in the return point within 300 meters from the user's first position.
  • the multiple shared vehicles may be all shared vehicles, or some shared vehicles, or available shared vehicles within a drop-off point that meets a preset distance range.
  • the remaining cruising range can reflect the maximum mileage that the vehicle can travel based on the current fuel or power.
  • the processing device may obtain the remaining power/fuel amount of the shared vehicle, and determine its remaining cruising range according to the remaining power/fuel amount of the shared vehicle.
  • the processing device may directly obtain the remaining cruising range of the vehicle from the database (for example, the memory 150) or the shared vehicle (for example, the shared motorcycle 140-2).
  • Step 730 Determine the first recommended vehicle from the plurality of shared vehicles based on the distance between the travel destination and the preset return area. In some embodiments, step 730 may be performed by the first determining module 420.
  • the preset return area refers to the vehicle return point designated by the shared service platform.
  • the preset return area may be determined based on the following information: road condition information of geographic location (for example, main traffic road, auxiliary road, fork road, subway entrance, bus station, etc.), area type (for example, residential area, Business districts, schools, etc.), user needs, traffic control information, etc., or any combination thereof.
  • the processing device may detect whether the return distance between a vehicle return point within a preset return distance range from the travel destination (that is, the preset return area) and the travel destination is Less than the first preset distance.
  • the return point of the vehicle within the preset return distance range of the travel destination refers to the calculation of the meaningful distance between the two.
  • the travel destination is in city A, and the return point in city B is calculated The distance between the point and the travel destination is meaningless.
  • searching for a vehicle return point within the preset return distance of the travel destination can ensure the feasibility of this solution.
  • the preset return distance range may be defined based on the distance between two preset return points.
  • the first preset distance may indicate the maximum distance between the travel destination and the return point, which means that the user can reach the travel destination soon after parking the shared vehicle at the return point.
  • the first preset distance may be a short distance such as 50 meters, 150 meters, 280 meters, 700 meters, 800 meters, and 1000 meters.
  • the processing device may respond to the distance between the preset return area within the preset return distance range from the user's travel destination and the travel destination being less than the first preset distance value, and calculate the user's The driving distance between the first location and the preset return area (that is, the estimated travel mileage). If the return distance between the travel destination and the preset return area within the preset return distance range is less than the first preset distance value, in this case, after the user returns the shared vehicle to the preset return area, It is very convenient to reach the travel destination. For the unified management of shared vehicles, the shared vehicle is generally parked in the preset return area, so in this case, it is necessary to calculate the driving distance between the user's first position and the preset return area.
  • calculate the driving distance between the car drop-off spot and the user's first position that is, the estimated travel mileage. For example, there are two drop-off points A and B within the preset drop-off distance range of the travel destination.
  • the user's cycling route passes through the return point A, but does not pass Car return point B, what needs to be calculated at this time is the driving distance between return point A and the user's first position.
  • the processing device may determine that the shared vehicle that meets the first preset condition among the multiple shared vehicles is the first based on the remaining cruising range of each shared vehicle in the multiple shared vehicles and the estimated travel distance.
  • the first preset condition may be that the distance difference between the remaining cruising range of the shared vehicle and the estimated travel distance is greater than the second preset distance value, and the remaining cruising range value of the shared vehicle is between the plurality of shared vehicles The smallest.
  • the processing device may first be based on the distance difference between the remaining driving distance (that is, the remaining cruising range) corresponding to the remaining power of each shared vehicle among the plurality of shared vehicles and the distance between the driving distance (that is, the estimated travel distance) Value, multiple candidate vehicles whose distance difference is greater than the second preset distance value are determined.
  • the second preset distance value is the minimum distance that can ensure that the remaining driving distance corresponding to the shared vehicle recommended to the user can reach the travel destination of the user
  • the first preset distance value may be at least 0.
  • the processing device may determine the candidate vehicle with the smallest remaining driving distance among the plurality of candidate vehicles as the first recommended vehicle for the user to ride.
  • the vehicle with the smallest remaining driving distance among the candidate vehicles needs to be recommended as the first choice for the user.
  • the distance between each candidate vehicle and the user's first position can be determined again, and the one closest to the user's first position can be selected from the multiple candidate vehicles
  • the candidate vehicle is determined as the first recommended vehicle for the user to ride. Due to the positioning accuracy of the positioning system, there may be at least two candidate vehicles that are relatively close to the user’s first position. In some embodiments, these candidate vehicles can be compared to the user’s first position according to whether the vehicle’s position is at the user’s first position.
  • the connection between the travel destinations is further screened, that is, a candidate vehicle closer to the connection between the first location and the travel destination is selected as the first recommended vehicle.
  • the processing device may determine the shared vehicle with the largest remaining cruising range among the plurality of shared vehicles in response to the distance between the user's travel destination and the preset return area being not less than the first preset distance value It is the first recommended vehicle for users to ride. If the return distance between the travel destination and the return point within the preset return distance range is greater than or equal to the first preset distance value, it is necessary to consider whether the user can still provide services after riding the shared vehicle to the destination. The next user rides the car to the return point, so that the car can be managed in the future. Therefore, in this case, the shared vehicle with the largest remaining cruising range among the multiple shared vehicles can be directly determined as The first recommended vehicle for users to ride.
  • the location of each shared vehicle with the largest remaining cruising range value can be calculated between the location of each shared vehicle with the largest remaining cruising range value and the current location of the user (eg, the user's first position) Select the vehicle closest to the user as the first recommended vehicle to recommend to the user.
  • the user's first location and the request time when the user initiates the service request are obtained, and the user's travel destination is predicted based on the user's travel information; according to the predicted travel
  • the first recommended vehicle for the user to ride is determined from the user’s surroundings, and it can be determined by the user’s travel destination and the vehicle return point.
  • the user can use the vehicle rationally to increase the probability that the vehicle can be returned to the vehicle return point, and the user’s reasonable use assists to achieve
  • the management and dispatch of vehicles helps to improve the rationality of vehicle dispatch and the convenience of vehicle management.
  • Step 740 Display the remaining cruising range corresponding to the first recommended vehicle to the user, and obtain first feedback information of the user.
  • step 740 may be performed by the first acquisition module 410 and/or the transmission module 450.
  • the processing device may send the remaining cruising range of the first recommended vehicle to the terminal device for display to the user after or at the same time after sending the determined first recommended vehicle to the terminal device, and obtain the user's first recommended vehicle.
  • the first feedback information may indicate that the user determines whether to use or not apply the first recommended vehicle.
  • the processing device may further obtain the user's first feedback information by sending information to the user asking whether to use the first recommended vehicle.
  • the processing device may send the user the remaining cruising range of the first recommended vehicle at the same time or after a certain time interval to send the user a message asking whether to use the first recommended vehicle.
  • displaying the remaining cruising range to the user and asking the user whether to use the first recommended vehicle may be displayed to the user in the form of a pop-up window, and may be displayed in the window asking the user whether to use the first recommended vehicle.
  • Design two buttons for example, you can simply set as “Yes” and “No” buttons, and determine the content indicated by the user's first feedback information according to the user's click on the button.
  • the processing device may also send other information related to the shared vehicle to the user.
  • the processing device 112 may send information such as the age, life, and device status of the recommended vehicle to the user.
  • step 750 in response to the user not using the first recommended vehicle, based on the remaining cruising range of the shared vehicle and/or the input destination of the user, determine the second recommended vehicle from the plurality of shared vehicles. In some embodiments, step 750 may be performed by the first determining module 420.
  • the processing device may obtain the input destination input by the user; The return distance between the vehicle point and the input destination is determined from the plurality of vehicles, and the second recommended vehicle recommended to the user is determined.
  • prompting the user to input the destination may be displayed to the user in the form of a pop-up window, and the user may input the destination in the pop-up window or other input boxes on the page.
  • the processing device may obtain the input destination input by the user, and respond to the preset return area within the preset return distance from the input destination and The distance between the input destinations is less than the first preset distance value, and the travel mileage between the first location and the preset return area is determined; based on the travel mileage value and each of the multiple shared vehicles If the distance difference of the remaining cruising range is greater than the second preset distance value and the remaining cruising range value is the smallest among the plurality of shared vehicles, the shared vehicle is determined as the second recommended vehicle.
  • the processing device may also calculate the travel distance between the input destination and the first location, and share the travel distance value with the multiple vehicles based on the travel distance value. If the distance difference between the remaining cruising range of each shared vehicle in the vehicle is greater than the second preset distance value, and the shared vehicle with the smallest remaining cruising range value among the multiple shared vehicles is determined as the second Recommended vehicle.
  • the processing device may obtain the actual travel mileage input by the user; based on the vehicle return point within the preset return distance from the travel destination The vehicle return distance from the travel destination, the actual travel mileage and the remaining cruising mileage of the vehicle are used to determine the second recommended vehicle recommended to the user from the plurality of vehicles.
  • the processing device may send the remaining cruising range of the second recommended vehicle or other related information to the user at the same time or after sending the determined second recommended vehicle to the user.
  • the reason why the user does not use the first recommended vehicle It may be that the remaining cruising range of the vehicle is not enough for the user to ride to the travel destination that the user wants to go, because the first recommended vehicle displayed to the user at this stage is already the remaining cruising range value of the vehicles that can be recommended to the user. The biggest, in the case that the first recommended vehicle still does not meet the user's car needs, at this stage there is no other shared vehicle that can meet the user's car needs to be recommended to the user. At this time, the user can send the user a failure to obtain the recommended vehicle information , And end the current shared vehicle recommendation process.
  • Step 760 Provide the user with location information of the recommended vehicle.
  • step 760 may be performed by the first determining module 420.
  • the processing device may provide the user with location information of the first recommended vehicle in response to the first feedback information indicating that the user determines to use the first recommended vehicle. In some embodiments, the processing device may provide the user with the location information of the second recommended vehicle after sending the second recommended vehicle to the user or while sending the second recommended vehicle.
  • the processing device may obtain the user's third position and the second position of the recommended vehicle, and provide the user with the third position to reach the second position based on the user's third position and the second position of the recommended vehicle Navigation information.
  • the processing device 112 may display a navigation route from the third location to the second location on the map interface of the user terminal 130.
  • the processing device may provide the user with the location information of the recommended vehicle through the reminding device of the shared vehicle.
  • the control module 430 of the processing device may control the sound device of the recommended vehicle, and send a voice prompt similar to "user nickname + I am here" to the user, or directly ring a bell prompt, so that the user can locate the recommended vehicle more easily.
  • the processing device may control the reminding device of the recommended vehicle to send a reminder signal when the distance between the third position of the user and the second position of the recommended vehicle is less than the third preset distance value.
  • the control module 430 may control the flashing lights of the recommended vehicle to blink, and may control the flashing frequency of the flashing lights as the distance between the third position of the user and the second position of the recommended vehicle is smaller.
  • Step 770 When the second feedback information indicates that the user has not found the recommended vehicle, it is determined that the fourth recommended vehicle is the updated recommended vehicle. In some embodiments, step 770 may be performed by the first determining module 420.
  • the processing device may send query information asking the user whether the user finds the recommended vehicle to the user at a preset time interval, and obtain second feedback information of the user for the query information.
  • the first time to send the user the inquiry information about whether to find the recommended vehicle may be calculated based on the distance between the second position of the recommended vehicle and the third position of the user, and the average walking speed of the user Of users arrive at the recommended vehicle parking place.
  • the calculated distance between the second position of the recommended vehicle and the third position of the user may be the straight-line distance displayed on the map, which may deviate from the path actually selected by the user, that is, the user finds the recommended vehicle There may be a deviation between the time and the time when the user first asked.
  • the system will no longer send inquiry information to the user; If the time the user finds the vehicle is after the system sends out the inquiry message about whether to find the recommended vehicle, it can send the second inquiry message to the user again within a preset time interval (for example, within 20 seconds, within 3 minutes, within 5 minutes, etc.) , And ask the user again if they found the recommended vehicle.
  • a preset time interval for example, within 20 seconds, within 3 minutes, within 5 minutes, etc.
  • the processing device may recommend the first recommended vehicle or a fourth recommended vehicle other than the second recommended vehicle among the plurality of shared vehicles to the user. For example only, when the recommended vehicle is a shared vehicle that meets the first preset condition among the multiple shared vehicles, the processing device may determine the candidate vehicle closest to the user’s current location among the multiple shared vehicles In order for the user to ride the fourth recommended vehicle; when the recommended vehicle is the shared vehicle with the largest remaining cruising range among the multiple shared vehicles, the multiple shared vehicles may be excluded from the first recommended vehicle, The shared vehicle with the largest remaining cruising range value is determined as the fourth recommended vehicle for users to ride.
  • the processing device can change the vehicle status corresponding to the recommended vehicle (for example, the first recommended vehicle, or the second recommended vehicle, or the fourth recommended vehicle, etc.) sent to the user to the reserved status;
  • the corresponding recommended vehicle is controlled to automatically unlock.
  • the status of the recommended vehicle is changed to the reserved state.
  • the recommended vehicle is It will no longer be recommended as a recommended vehicle.
  • the recommended vehicle is controlled to automatically unlock, and the user starts this riding, which can reduce the process of the user requesting unlocking through scanning and other methods, and improve the user Experience.
  • the first location of the user when the car service request is detected and the detection of the car service The request time at the time of request; based on the obtained travel information of the user, the first location of the user, and the request time when the car service request is detected, predict the travel destination of the user; and detect Whether the return distance between the return point of the vehicle within the preset return distance from the travel destination and the travel destination is less than the first preset distance; if the return distance is preset at the travel destination If the return distance between the return point of the vehicle within the vehicle distance range and the travel destination is less than the first preset distance, the travel distance between the first position of the user and the return point of the vehicle is calculated; The distance difference between the remaining driving distance corresponding to the remaining power of each of the multiple shared vehicles and the driving distance is determined to determine a plurality of candidate vehicles, wherein the remaining driving distance of each candidate vehicle is equal to the The distance difference between the driving distances is greater than the second
  • the user's car service request when the user's car service request is detected, the user's first location and the user's request time are obtained, and the user's travel destination is predicted based on the user's travel information, and the distance between the predicted travel destinations is detected Whether it is less than the first preset distance, if less than the first preset distance, determine the driving distance between the user's first position and the vehicle return point, and based on the driving distance and multiple shared vehicles around the user's first position
  • the candidate vehicle that can be used by the user to drive to the destination and is closest to the user is recommended to the user.
  • the vehicle with a lower remaining battery power can be dispatched back to the vehicle return point, and the battery of the vehicle can be replaced in time, which helps improve the rationality of vehicle scheduling And the convenience of vehicle management.
  • Fig. 8 is an exemplary flowchart of a method for pushing information of a shared vehicle according to other embodiments of the present application.
  • the process 800 may be executed by a processing device (for example, the processing device 112 shown in FIG. 1).
  • the process 800 may be stored in a storage device (for example, the memory 150 or a storage unit of a processing device) in the form of a program or instruction.
  • the processor 210 or the module shown in FIG. 4 executes the program or instruction, the process 800 may be implemented.
  • the process 800 may utilize one or more additional operations not described below, and/or not be completed by one or more operations discussed below.
  • the order of operations shown in FIG. 8 is not restrictive.
  • the shared vehicle information pushing method provided in this embodiment can filter out one or more shared vehicles corresponding to the status tag according to the status tag input by the user.
  • the process 800 can include the following steps.
  • Step 810 Obtain the shared vehicle status tag input by the user.
  • step 810 may be performed by the first obtaining module 410.
  • the status label of a shared vehicle can include, but is not limited to, "low battery”, “sufficient battery”, “located in a designated area”, “out of a designated area”, “low voltage”, “sufficient voltage”, “equipment version number consistent” “Inconsistent device version numbers”, etc., or any combination thereof.
  • the user may be a user of a shared vehicle, and the user may input at least one status tag through the client to obtain the shared vehicle corresponding to each status tag. For example, if a user wants to select shared vehicles that are not more than 50m away from their location and have sufficient power, they can enter status labels with "full power" and "located in a designated area".
  • the user may also be an operation and maintenance personnel.
  • the operation and maintenance personnel can input at least one status label through the operation and maintenance terminal to obtain the shared vehicle corresponding to each status label. For example, if the operation and maintenance personnel want to filter out the shared vehicles that need to be repaired, they can enter the status label of "Insufficient battery". In this way, the shared vehicles with insufficient battery can be filtered out, which is convenient for the operation and maintenance personnel to check the shared vehicles with insufficient battery. Carry out repairs.
  • At least one shared vehicle status tag input by the user can be obtained.
  • Step 820 According to the status tag, the shared vehicle corresponding to the status tag is selected from various types of shared vehicles as the third recommended vehicle. In some embodiments, step 820 may be performed by the first determining module 420.
  • the processing device may filter one or more shared vehicles corresponding to the status tag from various types of shared vehicles based on the status data of the shared vehicles stored in the background database according to the status tag input by the user.
  • the various types of shared vehicles may be shared vehicles located in multiple preset areas, and the various types of shared vehicles may be all vehicles, or some vehicles, etc., in the multiple preset areas.
  • the multiple preset regions may be multiple regions pre-divided according to administrative regions of different provinces and cities.
  • the preset area may include one or more designated shared device return areas (for example, a preset return area).
  • the processing device may use the selected shared vehicle as the third recommended vehicle and recommend it to the user.
  • Step 830 Provide the user with navigation information from the third position of the user to the second position of the recommended vehicle.
  • step 830 may be performed by the transmission module 450.
  • the processing device may also obtain the current third position of the user and the selected shared vehicles after filtering out the shared vehicles corresponding to the state tags from various types of shared vehicles according to the state tags input by the user.
  • the second position of the vehicle, and the navigation information from the third position to the second position is provided to the user according to the third position and the second position.
  • the processing equipment can also obtain navigation information from the current location of the operation and maintenance personnel to the location of the filtered shared vehicle, and the operation and maintenance personnel can find the filtered out based on the navigation information. Sharing vehicles improves work efficiency.
  • the processing device can also obtain navigation information from the user’s current location to the location of the selected shared vehicle, and the user can quickly find and filter based on the navigation information.
  • the shared vehicle improves the user experience.
  • each of the shared vehicles in the embodiments of the present application may be equipped with a reminding device, and the processing device may calculate the distance between the third position and the second position, if the distance is less than the third preset distance , The reminding device is controlled to send a reminding signal.
  • the third preset distance may be 2m, 3m, 4m, 5m, etc.
  • the reminder device on the filtered shared vehicles will start to send a reminder signal , To remind the operation and maintenance personnel to pay attention to the selected shared vehicles, which effectively shortens the time for the operation and maintenance personnel to search for the selected shared vehicles, and further improves work efficiency.
  • the reminding device may be a flashlight
  • the step of controlling the flashlight to emit a reminder signal may include: controlling the flashlight to blink, wherein the distance between the third position and the second position The smaller the distance, the higher the frequency of controlling the flash to flash.
  • the reminding device may be a buzzer or a voice module
  • the step of controlling the buzzer or the voice module to send a reminding signal may include: controlling the buzzer or the voice module to sound; Wherein, the smaller the distance between the third position and the second position, the shorter the time interval for controlling the buzzer or the voice module to sound.
  • the above-mentioned reminding device may also be other devices, as long as it can serve as a reminder to the user and the reminding effect is related to the distance between the third position and the second position, which is not limited here. .
  • the processing device may also send an inquiry message asking the user whether the user finds the third recommended vehicle to the user at a preset time interval, and obtain the user's second information regarding the inquiry information. Feedback. If the second feedback information indicates that the user has not found the third recommended vehicle, the fourth recommended vehicle is determined to be the updated recommended vehicle and recommended to the user. In some embodiments, the processing device may also change the state of the vehicle corresponding to the third recommended vehicle or the fourth recommended vehicle to the reserved state; and when receiving the riding start instruction sent by the user, control the third or The fourth recommendation is to automatically unlock the vehicle.
  • Fig. 9 is an exemplary flowchart of a method for pushing information of a shared vehicle according to still other embodiments of the present application.
  • the process 900 may be executed by a processing device (for example, the processing device 112 shown in FIG. 1).
  • the process 900 may be stored in a storage device (for example, the memory 150 or a storage unit of a processing device) in the form of a program or instruction.
  • the processor 210 or the module shown in FIG. 4 executes the program or instruction, the process 900 may be implemented.
  • the process 900 may utilize one or more additional operations not described below, and/or not be completed by one or more operations discussed below.
  • the order of operations shown in FIG. 9 is not restrictive.
  • the process 900 based on the shared vehicles that correspond to the status tags input by the user in each of the selected preset areas, the target area that needs to be upgraded is determined, so as not to affect In the case of the use of shared vehicles in other preset areas, the function of the selected shared vehicles in the target area is upgraded to realize unified management of all shared vehicles and reduce management costs.
  • the process 900 may include the following steps.
  • Step 910 Count the number of selected shared vehicles included in each preset area.
  • step 910 may be performed by the statistics unit 442.
  • multiple pre-divided regions can be obtained by dividing the administrative regions of different provinces and cities.
  • the pre-divided areas may be Chaoyang District, Haidian District, Xicheng District, Shunyi District, and Fangshan District in Beijing.
  • the pre-divided areas can be Wuhou District, High-tech District, Qingyang District, Jinjiang District, etc. in Chengdu.
  • the multiple pre-divided regions may also be divided according to geographic regions. For example, the multiple pre-divided regions may be North China, Northeast, East, Southwest, Northwest, and so on.
  • the processing device may obtain statistics on the number of shared vehicles included in each preset area based on the location information of the shared vehicles. In some embodiments, the processing device may collect statistics on the number of shared vehicles included in each preset area based on the usage information of the shared vehicles in the preset area.
  • Step 920 according to the number of filtered shared vehicles included in each preset area, determine a target area that needs to be upgraded. In some embodiments, step 920 may be performed by the analysis unit 444.
  • the processing device may determine the area with the largest number of filtered shared vehicles as the target area that needs to be upgraded by comparing the size of the number of filtered shared vehicles included in different preset areas.
  • the pre-divided areas as Chaoyang District, Haidian District, Xicheng District, Shunyi District, and Fangshan District in Beijing as an example
  • the number of shared vehicles filtered out by statistics is 1,000 in Chaoyang District, and in Haidian District
  • Haidian District There are 4000 vehicles in Xicheng District, 300 vehicles in Xicheng District, 2000 vehicles in Shunyi District, and 3,200 vehicles in Fangshan District.
  • Haidian District has the largest number of shared vehicles, and it can be determined that the target area that needs to be upgraded is Haidian District.
  • the processing device may select a reference area from each preset area including the filtered shared vehicle, and calculate that the reference area is excluded from each preset area including the filtered shared vehicle.
  • the data difference between the number of shared vehicles selected in each of the other preset areas and the number of shared vehicles selected in the reference area; and the target area that needs to be upgraded in accordance with the data difference is determined.
  • Chaoyang District is selected from each area as the reference area, the difference between the number of shared vehicles selected in Haidian District and the number of shared vehicles selected in Chaoyang District is 3000, and the number of shared vehicles selected in Xicheng District is equal to
  • the difference between the number of shared vehicles selected in Chaoyang District is 700, the difference between the number of shared vehicles selected in Shunyi District and the number of shared vehicles selected in Chaoyang District is 1000, and the number of shared vehicles selected in Fangshan District is 1000.
  • the difference between the number of vehicles and the data of shared vehicles selected in Chaoyang District is 1200. Then it can be determined that the target area that needs to be upgraded is the Haidian area.
  • the processing device may compare the number of filtered shared vehicles included in different preset areas with the size of the preset number, and determine that the area where the number of filtered shared vehicles is greater than the preset number is necessary.
  • the target area of the function upgrade may compare the number of filtered shared vehicles included in different preset areas with the size of the preset number, and determine that the area where the number of filtered shared vehicles is greater than the preset number is necessary. The target area of the function upgrade.
  • Step 930 Obtain a preset upgrade rule corresponding to the filtered status label of the shared vehicle.
  • step 930 may be performed by the first obtaining module 410.
  • the processing device may obtain the preset upgrade rule of the filtered status label of the shared vehicle based on the mapping relationship between the state label and the preset upgrade rule. It is understandable that different status labels correspond to different preset upgrade rules. For example, if the status label is "Inconsistent device version numbers", the corresponding preset upgrade rule may be: first roll back the device version of the shared vehicle corresponding to the status label to the pre-stored device version, and then change the status label to the pre-stored device version. The corresponding shared vehicle is upgraded to the next device version. For another example, if the status label is "the same device version numbers", the corresponding preset upgrade rule may be: directly upgrade the next device version of the shared vehicle corresponding to the status label. In this way, unified management of all shared vehicles can be facilitated, and management costs can be reduced.
  • mapping relationship between the status label and the preset upgrade rule can be adjusted reasonably according to the actual scenario, which is not limited in this specification.
  • Step 940 Perform a function upgrade on the selected shared vehicles located in the target area according to the preset upgrade rule.
  • step 940 may be performed by the control module 430.
  • the selected shared vehicles in the target area may be selected to perform functional upgrades in a preset time period.
  • the preset time period can be from 1 o'clock at night to 5 o'clock in the morning to avoid the time when users need to use the shared vehicle, avoid the unavailability of the shared vehicle due to function upgrades, and thereby increase the availability of shared vehicles .
  • the function of the selected shared vehicles located in the target area may be upgraded in an artificial manner. For example, if the state data of the selected shared vehicles in the target area indicates that the tire pressure of the shared vehicles in the target area is often at a low level, it can be inferred that the road conditions in the target area are poor. In this case, the tires of shared vehicles placed in this target area can be upgraded, for example, using more wear-resistant tires. In this way, the shared vehicles in different regions can be accurately upgraded in different ways, so that the service life of the shared vehicles in the target area is longer while the cost is controlled.
  • the solar panels of shared vehicles placed in the target area can be upgraded, for example, the shared vehicles can be equipped with solar panels with a higher solar conversion rate; or the power generation device can be used to replace the shared vehicles in the target area.
  • Solar panels convert the mechanical energy generated by users of shared vehicles into electrical energy during riding, so as to provide sufficient power for shared vehicles.
  • a control instruction can also be sent to each of the selected shared vehicles to prohibit the selected shared vehicles.
  • the shared vehicle sends status data corresponding to the shared vehicle to the server. For example, for a newly launched shared vehicle, it can be prohibited from sending status data to the server within a preset time period. For another example, for a shared vehicle whose status label is "sufficient battery", the shared vehicle may be prohibited from sending the status data corresponding to the power to the server within a preset time period.
  • the shared vehicle can be prohibited from sending voltage-corresponding status data to the server within a preset time period, so as to reduce the power consumption of the shared vehicle, so that the shared vehicle The service life is longer, reducing the frequency of upgrading or repairing shared vehicles, thereby reducing the operating and management costs of shared vehicles.
  • Fig. 10 is an exemplary flowchart of a method for determining a status label of a shared vehicle according to some embodiments of the present application.
  • the method for determining the status tag of a shared vehicle can obtain status data sent by the shared vehicle, analyze the status data according to a preset evaluation strategy, and obtain the corresponding status data of the shared vehicle that sent the status data.
  • the status tag allows users to filter out the corresponding shared vehicles based on the status tag, so that each shared vehicle can be conveniently analyzed based on the status tag, which simplifies the operation and management process of shared vehicles and effectively reduces costs.
  • the process 1000 may be executed by a processing device (for example, the processing device 112 shown in FIG. 1).
  • the process 1000 may be stored in a storage device (for example, the memory 150 or a storage unit of a processing device) in the form of a program or instruction.
  • the process 1000 may be implemented.
  • the process 1000 may utilize one or more additional operations not described below, and/or not be completed by one or more operations discussed below.
  • the order of operations shown in FIG. 10 is not restrictive. As shown in FIG. 10, the process 1000 may include the following steps.
  • Step 1010 Obtain at least one state data sent by at least one shared vehicle.
  • step 1010 may be performed by the first acquisition module 410 or the analysis module 440.
  • the status data can be used to reflect the current status of the shared vehicle's battery, voltage, power, tire pressure and other vehicle attributes.
  • the status data of the shared vehicle may include, but is not limited to, the power data, voltage data, device identification number information, latitude and longitude information, tire pressure information, device version number information, etc. of the shared vehicle, or any combination thereof.
  • the processing device may obtain the status data sent by the shared vehicle through a network (for example, the network 120).
  • the processing device may simultaneously receive one or more status data sent by multiple shared vehicles.
  • the processing device may respectively receive one or more status data sent by multiple shared vehicles.
  • Step 1020 For each state data sent by each shared vehicle, obtain the state type to which the state data belongs, and obtain the preset evaluation strategy corresponding to the state type. In some embodiments, step 1020 may be performed by the analysis module 440.
  • the status type is the type of status data. It is understandable that the status data sent by each shared vehicle can be one or more, and correspondingly, the status type to which the status data sent by each shared vehicle belongs can also be one or more.
  • the status type to which the status data sent by each shared vehicle belongs can be multiple.
  • the status type can include power, voltage, device identification number, latitude and longitude, tire pressure, device version number, etc.; correspondingly, the status data can be power data, voltage data, device identification number information, latitude and longitude information, tire pressure information, equipment Version number information, etc.
  • the preset evaluation strategy refers to a strategy that can be used to determine the type of status label. For example, if the status type is electric quantity, the corresponding preset evaluation strategy may be: if the electric quantity of the shared vehicle is less than 15%, then the status label of "Insufficient Electricity” will be obtained; otherwise, the status label of "Enough Electricity” will be obtained.
  • the preset evaluation strategy may be obtained by providing a strategy configuration interface on the terminal device in response to a user's configuration operation on the strategy configuration interface.
  • the policy configuration interface may be an interactive interface of a webpage or application software, and the user can perform configuration operations on the policy configuration interface to set a preset evaluation strategy. For example, the user can manually input the preset evaluation strategy in the strategy configuration interface of the terminal device.
  • the preset evaluation strategy can be adjusted according to actual application scenarios, which is not limited in this specification.
  • Step 1030 For the status data belonging to each status type sent by each shared vehicle, analyze using a preset evaluation strategy corresponding to the status type, and obtain the status data corresponding to the shared vehicle sending the status data belonging to the status type. Status label. In some embodiments, step 1030 may be performed by the analysis module 440.
  • the processing device may separately analyze each status data sent by each shared vehicle.
  • the state type is voltage
  • the corresponding preset evaluation strategy may be: if the voltage of the shared vehicle is lower than 3V, a status label of "undervoltage” is obtained, otherwise, a status label of "sufficient voltage” is obtained.
  • the status type is latitude and longitude
  • the corresponding preset evaluation strategy can be: according to the latitude and longitude of the shared vehicle, determine whether the shared vehicle is in the designated area, and if the shared vehicle is not in the designated area, a status label of "out of designated area” will be obtained. Otherwise, the status label of "located in the designated area” is obtained.
  • the corresponding preset evaluation strategy can be: compare the device version number of the shared vehicle with the pre-stored device version number of the shared vehicle. If they are the same, get "the device version number is consistent If the status label is inconsistent, the status label of "device version number is inconsistent" will be obtained.
  • the processing device may analyze the historical status data sent by each shared vehicle. For example, the state data sent by the shared vehicle every preset time interval can be obtained, and the state data of the same state type can be analyzed and predicted according to the preset evaluation strategies corresponding to different state types, and the state prediction result of the shared vehicle can be obtained.
  • the preset time can be one week, two weeks, three weeks, one month, two months, and so on.
  • shared vehicle F sends status data with a status type of power to server 110 every one week. The status data sent for the first time indicates that the power of shared vehicle F is 90%, and the status data sent for the second time indicates that shared vehicle F is The power level is 87%.
  • the status data sent for the third time indicates that the power level of shared vehicle F is 83%.
  • the status data sent for the fourth time indicates that the power level of shared vehicle F is 80%. It can be predicted that shared vehicle F will be 21 weeks later. Its power may be less than 15%.
  • the shared vehicle may be repaired in advance based on the predicted result of the shared vehicle status data, so as to increase the service life of the shared vehicle.
  • the preset evaluation strategy corresponding to each status type is used to analyze the status data sent by each shared vehicle belonging to each status type. Later, there are also multiple status tags for the shared vehicle.
  • the status label of "Insufficient battery” can be obtained according to the preset evaluation strategy corresponding to the power; if the voltage of shared vehicle A is 2V, the status label of "Insufficient power” can be obtained according to the preset evaluation strategy corresponding to the voltage Insufficient voltage” status label; in this way, according to the two status data of "power is 10%” and “voltage is 2V" sent by shared vehicle A, there are two status labels that can be analyzed, namely, "power is insufficient” and " Insufficient voltage”.
  • the obtained state tag and the state data sent by the shared vehicle may also be stored in a database (for example, the memory 150) , It is convenient to retrieve the status data of the shared vehicle during use. For example, it can be used to filter the corresponding shared vehicle based on the status tag input by the user.
  • the status label corresponding to the shared vehicle sending the status data is obtained, thereby simplifying the operation and management process of the shared vehicle. Effectively reduce costs. It can be specifically combined with Figures 8-9 of this specification and related descriptions, and will not be repeated here.
  • Fig. 11 is an exemplary flowchart of a method for pushing information of a shared vehicle according to still other embodiments of the present application.
  • the shared vehicle information push method provided in this implementation can update the use of shared vehicles in the preset area at the previous moment according to the obtained use of shared vehicles in the preset area at a certain time, and update the updated information.
  • the vehicle usage is displayed to the user, so that the user can know the number of related vehicles that can be used in the preset return area corresponding to the preset area, that is to say, the user can be provided with a more accurate vehicle parking location, so that the user You can go to the preset area where there are available vehicles to find available shared vehicles according to your needs.
  • the process 1100 may be executed by a processing device (for example, the processing device 112 shown in FIG. 1).
  • the process 1100 may be stored in a storage device (for example, the memory 150 or a storage unit of a processing device) in the form of a program or instruction.
  • the process 1100 may be implemented.
  • the process 1100 may utilize one or more additional operations not described below, and/or not be completed by one or more operations discussed below.
  • the order of operations shown in FIG. 11 is not restrictive. As shown in FIG. 11, the process 1100 may include the following steps.
  • Step 1110 Obtain shared vehicle usage conditions in multiple preset areas at the first moment.
  • step 1110 may be performed by the first obtaining module 410.
  • the preset area may be a geographic area designated by the staff. After using the shared vehicle, the user of the shared vehicle can park the shared vehicle in the designated geographical area, and the operation and maintenance personnel can drop the shared vehicle in the designated preset area.
  • the preset area may be a geographic area calculated by the processing device based on data such as the parking situation of shared vehicles, the flow of people in each area, the situation of using vehicles, and traffic control. Similarly, the user of the shared vehicle can park the shared vehicle in the geographical area calculated above after using the shared vehicle, and the operation and maintenance personnel can drop the shared vehicle in the geographical area calculated above.
  • the preset area may be a geographic area delineated by the operation and maintenance personnel during the process of placing the shared vehicle, and the shared vehicle user can park the shared vehicle in the above delineated geographic area after using the shared vehicle. Area.
  • the processing device may receive the information sent by the operation and maintenance personnel through the operation and maintenance terminal before obtaining the usage status of the shared vehicle.
  • the scope of the preset area is a geographic area delineated by the operation and maintenance personnel during the process of launching the shared vehicle.
  • the operation and maintenance personnel can transport all the shared vehicles they transport Or part of it is placed there, and the geographic information of the place is uploaded to the server through its own operation and maintenance terminal as a new preset area, so that the server can add the preset area in the database and share it in the preset area
  • the vehicle usage is updated.
  • the range of the preset area can be divided by the operation and maintenance personnel according to the location of the shared vehicles they place, so that the user can know the number of shared vehicles that can be used in the shared vehicle storage point corresponding to the preset area, so that the user can According to the needs, go to the preset area where the shared vehicles can be used to find the available shared vehicles.
  • the first moment may indicate the moment when the vehicle usage status is newly collected.
  • the shared vehicle usage situation corresponding to the first moment may be expressed as the first vehicle usage situation
  • the shared vehicle usage situation corresponding to the second moment may be expressed as the second vehicle usage situation.
  • the usage of the first vehicle is the updated usage of the vehicle relative to the usage of the second vehicle.
  • shared vehicle usage may include the number of shared vehicles.
  • the shared vehicle usage situation may include a failure situation of the shared vehicle.
  • the shared vehicle usage status may also include both the number of shared vehicles and the failure status of the shared vehicles.
  • both the first vehicle usage status and the second vehicle usage status may include at least the number of vehicles and the vehicle breakdown status.
  • the number of shared vehicles may be the total number of shared vehicles in multiple preset areas, and/or the respective numbers of different types of shared vehicles in the multiple preset areas, etc.
  • those skilled in the art can appropriately adjust the data type of the number of shared vehicles according to the actual situation, which is not specifically limited in the embodiments of the present application.
  • the processing device may obtain that the total number of shared vehicles in a preset area at the first moment is 20, where the number of vehicles of the first type is 8, the number of vehicles of the second type is 10, and the number of vehicles of the third type Is 2.
  • the type of vehicle may refer to vehicles with different functions such as bicycles, electric vehicles, and automobiles, and may also refer to different bicycle vendors, which are also not specifically limited in the embodiments of the present application.
  • the first type can represent bicycles
  • the second type can represent electric vehicles
  • the third type can represent automobiles.
  • the processing device may obtain the number of shared vehicles in the preset area through the data uploaded by the operation and maintenance personnel through the operation and maintenance terminal. Operation and maintenance personnel can search for scattered shared vehicles in the streets and alleys, and then transport them to a preset area.
  • the method for determining the preset area has been described in detail in the above embodiments, and will not be repeated here. . Therefore, the change in the number of shared vehicles in the preset area may be that the operation and maintenance personnel have placed a certain number of shared vehicles in the preset area. Therefore, the number of shared vehicles in the preset area can be determined according to the number of shared vehicles released by the operation and maintenance personnel. The number is updated in real time, so as to ensure that the accuracy of the number of shared vehicles that can be used in the preset area is high.
  • the processing device may receive the number of shared vehicles delivered to the preset area sent by the operation and maintenance terminal. Since the operation and maintenance personnel only need to enter a value at the end, this method is simple and quick.
  • the operation and maintenance personnel can use the operation and maintenance terminal to record a delivery operation when each shared vehicle is placed in the preset area.
  • the number of shared vehicles in the preset area is in the operation and maintenance personnel. Increase by one after each placement action is completed.
  • the operation and maintenance personnel can use the operation and maintenance terminal to scan the two-dimensional code, barcode, etc. on the shared vehicle; or, the operation and maintenance personnel can manually enter a shared vehicle on the operation and maintenance terminal and so on. Since the operation and maintenance personnel need to scan the code when placing each shared vehicle, it is possible to avoid missing the number of shared vehicles placed, so that the number of shared vehicles placed is not prone to errors.
  • the operation and maintenance personnel can not only update the number of shared vehicles in the preset area after the delivery process or after the delivery is completed, but also perform daily inspections on the shared vehicles in each preset area to count each preset The number of shared vehicles in the area, and upload the statistical number of shared vehicles to the server to correct the usage of shared vehicles, thereby improving the accuracy of the usage of shared vehicles in the preset area.
  • the processing device may obtain the number of shared vehicles in the preset area from the data uploaded by the user of the shared vehicle through the client.
  • the change in the number of shared vehicles in the preset area may be that the user uses the shared vehicles in it. Therefore, the number of shared vehicles in the preset area can be updated in real time according to the number of shared vehicles used by the user to ensure that the preset area is available. The accuracy of the number of shared vehicles used is high.
  • the failure condition of the shared vehicle may be the number of shared vehicles that have a failure or no failure in a plurality of preset areas, or it may be the specific vehicle that has the failure, and so on.
  • those skilled in the art can make appropriate adjustments to the data type of the fault condition of the shared vehicle according to the actual situation, which is not specifically limited in the embodiments of the present application.
  • the processing device can obtain that a total of 3 vehicles have failed in the first preset area at the first moment, and 12 vehicles have no failure; or the processing device can obtain that a vehicle numbered 56395782 has appeared in the first preset area. Fault.
  • Operation and maintenance personnel can simultaneously check whether the delivered shared vehicle and the shared vehicle already parked in the preset area can be used (that is, whether there is a malfunction) when placing the shared vehicle. If the operation and maintenance personnel find that a shared vehicle is unavailable, they can upload the vehicle identification information of the shared vehicle through the operation and maintenance terminal. For example, the operation and maintenance personnel can use the operation and maintenance terminal to scan the two-dimensional code, barcode, etc. on the shared vehicle; or, the operation and maintenance personnel can manually input the information of the shared vehicle on the operation and maintenance terminal. Among them, the vehicle identification information can be used to mark a failure or no failure of the shared vehicle in the preset area.
  • operation and maintenance personnel can not only inspect shared vehicles during the delivery process, but also conduct daily inspections of shared vehicles in each preset area, check the failure of shared vehicles in each preset area, and check the situation. Upload to the server to correct the usage of shared vehicles in each preset area, thereby improving the accuracy of the usage of shared vehicles in the preset area.
  • the operation and maintenance personnel can identify the vehicle information of the faulty shared vehicle when placing the shared vehicle or patrolling, so that the processing device can update the number of available shared vehicles in the preset area in real time.
  • the user of the shared vehicle may input feedback on the failure of the shared vehicle through the client when using or returning the vehicle. For example, when a user is preparing to use a shared vehicle and discovers that the shared vehicle chain, and/or handlebars, and/or seats, and/or tires, and/or locks and other vehicle components are faulty, which affects riding,
  • the feedback information of the shared vehicle can be input on the feedback interface of the shared vehicle APP to upload the status of the shared vehicle to the server to correct the usage of the shared vehicle in each preset area.
  • the server may send the location information and/or identification information of the faulty shared vehicle fed back by the shared vehicle user to the operation and maintenance terminal, so that the operation and maintenance personnel can verify or repair the faulty shared vehicle.
  • step 1120 the shared vehicle usage status stored in the preset area at the second time is updated according to the shared vehicle usage status at the first moment.
  • step 1120 may be performed by the first determining module 420.
  • the processing device after the processing device obtains the shared vehicle usage at a certain moment, it can store it in the database. After obtaining the shared vehicle usage at the latest moment, it can use the updated shared vehicle usage pair The stored usage of shared vehicles is updated.
  • the second moment may indicate the moment when the usage of the shared vehicle was collected last time. It can be understood that the descriptions of the first moment and the second moment are only used to characterize the sequence of the two moments, that is, the first moment is a certain moment later than the second moment. For example, when collecting the usage of shared vehicles in a periodic manner, the first moment may indicate the latest moment of collecting the usage of the shared vehicles, and the second moment indicates the corresponding moment of collecting the usage of the shared vehicles in the previous cycle.
  • the processing device may periodically obtain the usage of shared vehicles in a preset area at a certain time, or it may obtain the usage of shared vehicles in a preset area at a certain time in real time.
  • the processing device may periodically obtain the usage of shared vehicles in a preset area at a certain time, or it may obtain the usage of shared vehicles in a preset area at a certain time in real time.
  • the processing device may periodically obtain the usage of shared vehicles, assuming that the acquisition period is one hour, the first moment is 10 o'clock every morning, and the second moment can be 9 o'clock every morning; if the processing device obtains the sharing in real time Vehicle usage status, once the usage status of the shared vehicle in the preset area changes, the processing device will obtain the usage status of the shared vehicle once. Assuming that the first moment is 10:50 in the morning, the second moment can be the morning Ten ten.
  • the processing device may receive the first scan code information of one of the shared vehicles in the preset area sent by the operation and maintenance terminal (that is, the information of the operation and maintenance personnel scanning the QR code on the shared vehicle), The current number of shared vehicles in the preset area is increased by one to update the number of shared vehicles in the preset area.
  • the processing device may, when receiving the second scan code information of a certain shared vehicle in the preset area (that is, the information of the user scanning the two-dimensional code on the shared vehicle) sent by the client,
  • the current number of shared vehicles in the preset area is reduced by one to update the number of shared vehicles in the preset area.
  • the server correspondingly receives the user through the client to a certain area in the preset area.
  • the second scan code information generated after the vehicle scans the code determines that the number of shared vehicles in the preset area is reduced by one. Therefore, the server decrements the current number of shared vehicles in the preset area by one to determine the preset area.
  • the number of shared vehicles in the area is updated.
  • the server when the server receives the parking information for a shared vehicle in the preset area sent by the client (for example, it receives the operation instruction of the user clicking the "return the car” button on the client), it will indicate that the user After using a shared vehicle, the shared vehicle is parked in a preset area. At this time, the server can reduce the current number of shared vehicles in the preset area by one to share the vehicle in the preset area The quantity is updated.
  • first scan code information and the second scan code information in the embodiment of the present application is to distinguish the scan code information generated by different operation and maintenance terminals or the scan code information generated by the client.
  • the processing device may, after receiving the vehicle identification information sent by the operation and maintenance terminal, subtract one from the number of usable vehicles in the corresponding preset area, or directly identify the specific vehicle that has failed in the corresponding preset area , To update the number of available shared vehicles in each preset area.
  • the update method of the shared vehicle usage status is not specifically limited, and those skilled in the art can make appropriate adjustments according to the actual situation.
  • Step 1130 Based on the update result, it is determined to carry the display information of the usage of the shared vehicle. In some embodiments, step 1130 may be performed by the first determining module 420.
  • the processing device may generate the use of the shared vehicle.
  • the display object of the situation i.e. display information.
  • the processing device may provide the above-mentioned display object to the terminal device in response to the user's operation instruction to the terminal device. That is, when the user of the shared vehicle wants to obtain the usage status of the shared vehicle in each preset area through the client, the processing device can output the corresponding usage status of the shared vehicle through the client.
  • the display object may be a map, and the map may display multiple preset areas and the usage of shared vehicles in each preset area. For example, red can be used on the map to indicate that the shared vehicle is being used, green to indicate that the shared vehicle is idle, and yellow to indicate that the shared vehicle is malfunctioning; or the usage of the shared vehicle in the preset area can be directly displayed in text at the corresponding location of each preset area.
  • the display object may be a list, and the list may sort each preset area by distance, and correspondingly display the usage of shared vehicles corresponding to each preset area.
  • the output mode of the display object may be any reasonable form.
  • the display is performed on the screen of the client of the shared vehicle user, and the display mode may include text, image, video, etc., or any combination thereof.
  • the voice output of the shared vehicle user's client can be used to broadcast the usage of the shared vehicle in each preset area.
  • this method can be mainly aimed at the elderly, users who are using the shared vehicle, etc. Inconvenient through text Crowd viewing and displaying information in a form.
  • the display information may also be sent to the shared vehicle, and output to the user through the display device or voice device of the shared vehicle.
  • the usage status of the shared vehicles in the preset area at a certain moment can be updated according to the usage status of the shared vehicles in the preset area at a certain moment, and the updated usage status of the shared vehicles can be displayed to
  • the user who uses the terminal device so that the user can know the number of shared vehicles that can be used in the vehicle storage point corresponding to the preset area, that is to say, the user can be provided with a more accurate vehicle parking place, so that the user can according to the needs Go to the preset area where shared vehicles are available to find available shared vehicles.
  • Fig. 12 is an exemplary flowchart of a method for pushing information of a shared vehicle according to still other embodiments of the present application.
  • an embodiment of the present application also provides a sharing method applied to the terminal device (for example, the user terminal 130 shown in FIG. 1) Vehicle information push method. That is, the process 1200 may be executed by the terminal device.
  • the process 1200 may be stored in a storage device (for example, the storage unit 390) in the form of a program or instruction.
  • the central processing unit 340 or the module shown in FIG. 5 executes the program or instruction, the process 1200 may be implemented.
  • the process 1200 may utilize one or more additional operations not described below, and/or not be completed by one or more operations discussed below.
  • the order of operations shown in FIG. 12 is not restrictive. As shown in FIG. 12, the process 1200 may include the following steps.
  • Step 1210 Receive a user's operation instruction to the terminal device.
  • step 1210 may be performed by the receiving module 510.
  • the operation instruction may include, but is not limited to, the user opening the shared vehicle APP of the terminal device, or clicking a button, page or link in the APP after opening the APP, or entering a search instruction in a browser or other pages.
  • the terminal device can determine the user's needs. For example, by obtaining the operation instruction of the user to open the display page in the shared vehicle APP on the user end 130, it can be determined that the user may need to obtain the usage of the surrounding shared vehicles; or by obtaining the operation instruction of the user clicking the "unlock" button on the user end 130 , It can be determined that the user needs to use the corresponding shared vehicle.
  • the form of the operation instruction may include voice, text, facial motion (for example, blinking), gesture, touch screen operation, etc., or any combination thereof.
  • the terminal device may transmit the operation instruction or the service request corresponding to the operation instruction to the background server (for example, the server 110).
  • the client 130 may generate a corresponding service request based on the user's operation instruction and send it to the server 110, and the processing device 112 in the server 110 may perform related analysis and processing based on the service request.
  • Step 1220 Obtain feature information related to the operation instruction.
  • step 1220 may be performed by the second acquisition module 520.
  • the characteristic information related to the operation instruction may include, but is not limited to, the initiation time of the operation instruction, the first position when the user executes the operation instruction, the user's travel information, the user's order information, and the shared vehicle status tag input by the user. , The destination entered by the user, etc., or any combination thereof.
  • the terminal device may obtain characteristic information related to the operation instruction from its built-in database (for example, the storage unit 390).
  • the terminal device may obtain feature information related to the operation instruction from the server.
  • the user terminal 130 may obtain user historical travel information, historical service request orders, etc. related to the user as characteristic information related to the operation instruction from the server 110 based on the ID information of the user who triggered the operation instruction.
  • Step 1230 Determine display information based at least on the characteristic information, where the display information includes vehicle recommendation information and/or usage information of the shared vehicle. In some embodiments, step 1230 may be performed by the second determining module 530.
  • the display information may include vehicle recommendation information of the shared vehicle, and/or usage information, and/or status information of the vehicle.
  • shared vehicle recommendation information may include the recommended vehicle, location information of the recommended vehicle, and mileage information of the recommended vehicle
  • shared vehicle usage information may include the number of available shared vehicles nearby, whether the vehicle is faulty, etc.
  • vehicle status information may include Vehicle age, model, color, life, fuel/power consumption, etc.
  • the terminal device may determine based on at least one of the first position when the user executes the operation instruction, the initiation time of the operation instruction, the user travel information, the user input destination, the shared vehicle status tag input by the user, etc. Recommended vehicle. In some embodiments, the terminal device may determine the shared vehicle usage information based on the characteristic information.
  • the terminal device may obtain the display information from the server.
  • the client 130 may obtain the corresponding display information from the server 110 based on the user account information corresponding to the operation instruction, or the service request number corresponding to the operation instruction.
  • the client 130 may send the characteristic information related to the operation instruction to the server 110, and obtain the display information determined by the server 110 through analysis and processing.
  • Step 1240 Display the display information on the terminal device page.
  • step 1240 may be performed by the display module 540.
  • the terminal device may output and display the display information obtained from the server to the user. In some embodiments, after determining the display information, the terminal device may display its output to the user through the display device. In some embodiments, the terminal device may display the display information on the page opened by the user. Just as an example, the user can open a page through the client. In contrast, the terminal device can respond to the user's operation instruction to open the page and display the display information on the page. In some embodiments, the terminal device may display the display information on the display interface of the terminal device.
  • the terminal device may display the display information in the form of a pop-up window, and the user may obtain the content of the display information on the interface of the pop-up window or by clicking a link or button in the pop-up window.
  • the terminal device may transmit the display information to the user in the form of voice broadcast.
  • the possible beneficial effects may be any one or a combination of the above, or any other beneficial effects that may be obtained.
  • numbers describing the number of ingredients and attributes are used. It should be understood that such numbers used in the description of the embodiments use the modifier "about”, “approximately” or “substantially” in some examples. Retouch. Unless otherwise stated, “approximately”, “approximately” or “substantially” indicates that the number is allowed to vary by ⁇ 20%.
  • the numerical parameters used in the specification and claims are approximate values, and the approximate values can be changed according to the required characteristics of individual embodiments. In some embodiments, the numerical parameter should consider the prescribed effective digits and adopt the method of general digit retention. Although the numerical ranges and parameters used to confirm the breadth of the ranges in some embodiments of this specification are approximate values, in specific embodiments, the setting of such numerical values is as accurate as possible within the feasible range.

Landscapes

  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Primary Health Care (AREA)
  • Tourism & Hospitality (AREA)
  • Traffic Control Systems (AREA)

Abstract

一种共享车辆的信息推送方法和系统，所述方法由至少一个处理器执行，其包括：响应于用户对终端设备的操作指令，获取与所述操作指令相关的特征信息(610)；至少基于所述特征信息确定所述终端设备的展示信息(620)，所述展示信息包括共享车辆的车辆推荐信息和/或共享车辆使用情况信息；以及，向所述终端设备发送所述展示信息(630)。

Description

一种共享车辆的信息推送方法和系统
优先权声明
本申请要求2019年12月31日提交的中国申请号201911424973.7的优先权，2019年12月31日提交的中国申请号201911406331.4的优先权，2019年12月31日提交的中国申请号201911412463.8的优先权，全部内容通过引用并入本文。
技术领域
本申请涉及共享设备技术领域，特别涉及一种共享车辆的信息推送方法和系统。
背景技术
随着互联网技术的飞速发展，越来越多的用户选择利用共享车辆出行。现阶段，用户在寻找共享车辆时，一般是根据个人经验去寻找可使用的车辆，或者根据用户终端上打开的手机软件(Application，APP)的界面中显示的可用车辆，去到该位置寻找对应的车辆。但是，当APP获取的共享车辆的位置不准确时，用户去到该位置可能找不到车。此外，用户在选择共享车辆的过程中，由于不知道共享车辆状态，可能会因为共享车辆故障、车辆电量不足、环境等因素导致开锁失败，而且在骑行过程中，还可能会遇到电量无法支撑用户到达目的地而被迫在中途归还车辆等问题，车辆无法满足用户的使用需求，并且车辆停放位置散乱，车辆维护和调度的难度大。
因此，希望提供一种共享车辆的的信息推送方法。
发明内容
本申请实施例之一提供一种共享车辆的信息推送方法，由至少一个处理器执行，所述方法包括：响应于用户对终端设备的操作指令，获取与所述操作指 令相关的特征信息；至少基于所述特征信息确定所述终端设备的展示信息，所述展示信息包括共享车辆的车辆推荐信息和/或使用情况信息；向所述终端设备发送所述展示信息。
在一些实施例中，与所述操作指令相关的所述特征信息包括用户执行所述操作指令的第一位置、所述操作指令的发起时间和所述用户的出行信息；所述展示信息包括所述共享车辆的所述车辆推荐信息；至少基于所述特征信息确定所述车辆推荐信息，包括：基于所述第一位置、所述操作指令的所述发起时间和所述用户的所述出行信息，确定所述用户的出行目的地；基于所述出行目的地与预设还车区域之间的距离，从距离所述第一位置的预设距离范围值内的多台共享车辆中确定第一推荐车辆。
在一些实施例中，所述出行信息包括所述用户的多条历史出行信息；以及，所述确定所述用户的所述出行目的地包括：基于所述多条历史出行信息确定多条历史出行路线，以及每条历史出行路线对应的出行起始时间；在所述多条历史出行路线中，将所述出行起始时间与所述操作指令的所述发起时间最接近的历史出行路线确定为预估出行路线；确定所述预估出行路线对应的目的地为所述用户的所述出行目的地。
在一些实施例中，所述出行信息包括所述用户的计划出行信息；以及，所述确定所述用户的所述出行目的地包括：获取所述用户的所述计划出行信息的出行方式以及出行时间；基于所述出行方式，确定所述计划出行信息的出行起始地；基于所述第一位置与所述计划出行信息的所述出行起始地之间的距离，确定从所述第一位置到所述计划出行信息的所述出行起始地的预估到达时间；响应于所述预估到达时间早于所述计划出行信息的出行时间，确定所述计划出行信息的所述出行起始地为所述用户的所述出行目的地。
在一些实施例中，基于所述出行目的地与所述预设还车区域之间的距离，从距离所述第一位置的预设距离范围值内的所述多台共享车辆中确定所述第一推荐车辆，包括：确定所述多台共享车辆中每台共享车辆的剩余续航里程；响应 于所述出行目的地与所述预设还车区域之间的距离小于第一预设距离值，确定所述第一位置与所述预设还车区域之间的预估出行里程；基于所述多台共享车辆中每台共享车辆的所述剩余续航里程与所述预估出行里程，确定所述多台共享车辆中满足第一预设条件的共享车辆为所述第一推荐车辆；其中，所述第一预设条件包括共享车辆的所述剩余续航里程与所述出行里程之间的距离差值大于第二预设距离值，且所述剩余续航里程值在所述多台共享车辆中最小。
在一些实施例中，基于所述出行目的地与所述预设还车区域之间的距离，从距离所述第一位置的预设距离范围值内的所述多台共享车辆中确定所述第一推荐车辆包括：响应于所述出行目的地与所述预设还车区域之间的距离不小于所述第一预设距离值，确定所述多台共享车辆中所述剩余续航里程值最大的共享车辆为所述第一推荐车辆。
在一些实施例中，所述方法还包括：将所述第一推荐车辆对应的剩余续航里程显示给所述用户，并获取所述用户的第一反馈信息；响应于所述第一反馈信息指示所述用户确定不使用所述第一推荐车辆，基于所述多台共享车辆的所述剩余续航里程和/或所述用户的输入目的地，从所述多台共享车辆中确定第二推荐车辆。
在一些实施例中，与所述操作指令相关的所述特征信息包括所述用户输入的共享车辆状态标签；所述至少基于所述特征信息确定所述终端设备的所述车辆推荐信息包括：根据所述用户输入的所述状态标签，从各类型共享车辆中筛选出与所述状态标签对应的共享车辆为第三推荐车辆。
在一些实施例中，所述方法还包括：获取推荐车辆的第二位置以及所述用户的第三位置；根据所述用户的第三位置与所述推荐车辆的第二位置，为所述用户提供从所述第三位置到达所述第二位置的导航信息。
在一些实施例中，所述共享车辆配置有提醒装置，所述方法还包括：计算所述用户的第三位置与所述推荐车辆的第二位置之间的距离；若所述用户的第三位置与所述推荐车辆的第二位置之间的距离小于第三预设距离值，则控制所 述提醒装置发出提醒信号。
在一些实施例中，所述提醒装置为闪光灯；所述控制所述提醒装置发出提醒信号，包括：控制所述闪光灯进行闪烁，其中，所述用户的第三位置与所述推荐车辆的第二位置之间的所述距离越小，控制所述闪光灯进行闪烁的频率越高。
在一些实施例中，所述方法还包括：获取所述用户的第二反馈信息；若所述第二反馈信息指示所述用户未寻找到所述推荐车辆，确定第四推荐车辆为更新后的推荐车辆。
在一些实施例中，所述方法还包括：将所述推荐车辆对应的车辆状态更改为预约状态；当接收到所述用户发送的骑行开始指令时，控制所述推荐车辆开锁。
在一些实施例中，所述各类型共享车辆分别位于预先划分的多个预设区域，所述方法还包括：统计各预设区域中包括的筛选出的共享车辆的数量；根据所述各预设区域中包括的所述筛选出的共享车辆的数量，确定需要进行功能升级的目标区域。
在一些实施例中，所述根据各预设区域中包括的筛选出的共享车辆的数量，确定所述需要进行功能升级的目标区域，包括：从包括所述筛选出的共享车辆的所述各预设区域中选取参考区域，计算包括所述筛选出的共享车辆的所述各预设区域中除所述参考区域之外的其他每个预设区域中筛选出的所述共享车辆的数量与所述参考区域中筛选出的所述共享车辆的数量的数据差值；根据所述数据差值确定所述需要进行功能升级的目标区域。
在一些实施例中，所述方法还包括：获取所述状态标签对应的预设升级规则；按照所述预设升级规则对位于所述目标区域的筛选出的所述共享车辆进行所述功能升级。
在一些实施例中，所述共享车辆的所述状态标签通过以下方式确定：获取至少一个所述共享车辆发送的至少一个状态数据；针对每个所述共享车辆发送的每个所述状态数据，获取该状态数据所属的状态类型，并获取所述状态类型对应的预设评估策略；针对每个所述共享车辆发送的属于每种所述状态类型的所 述状态数据，采用与所述状态类型对应的所述预设评估策略进行分析，得到与发送属于所述状态类型的状态数据的共享车辆对应的所述状态标签。
在一些实施例中，所述方法还包括：向所述筛选出的每个共享车辆分别发送控制指令，以禁止所述筛选出的共享车辆发送与该共享车辆对应的状态数据。
在一些实施例中，所述预设评估策略通过以下方式获得：提供策略配置界面；响应在所述策略配置界面的配置操作，获得所述预设评估策略。
在一些实施例中，所述至少基于所述特征信息确定所述展示信息包括：获取第一时刻的多个预设区域内的共享车辆使用情况；其中，所述共享车辆使用情况包括所述共享车辆的数量；根据所述第一时刻的共享车辆使用情况对第二时刻存储的所述预设区域内的共享车辆使用情况进行更新，生成携带所述共享车辆使用情况的所述展示信息。
在一些实施例中，所述终端设备包括运维端；所述获取所述第一时刻的所述多个预设区域内的所述共享车辆使用情况，包括：接收所述运维端发送的投放到所述预设区域内的所述共享车辆数量；或，当接收到所述运维端发送的在所述预设区域内的其中一辆共享车辆的第一扫码信息时，将所述预设区域对应的所述共享车辆数量加一以对所述共享车辆数量进行更新。
在一些实施例中，所述终端设备包括客户端；所述获取所述第一时刻所述多个预设区域内的所述共享车辆使用情况，包括：当接收到所述客户端发送的在所述预设区域内的其中一辆共享车辆的第二扫码信息时，将所述预设区域对应的所述共享车辆数量减一以对所述共享车辆数量进行更新。
在一些实施例中，所述共享车辆使用情况包括所述共享车辆的故障情况；所述获取所述第一时刻所述多个预设区域内的所述共享车辆使用情况，包括：接收所述用户对所述终端设备发送的车辆标识信息；其中，所述车辆标识信息用于标记所述预设区域内的所述共享车辆是否故障。
在一些实施例中，所述方法还包括：接收所述运维端发送的所述预设区域的范围。
本申请实施例之一提供一种共享车辆的信息推荐方法，应用于终端设备，所述方法包括：接收用户对所述终端设备的操作指令；获取与所述操作指令相关的特征信息；至少基于所述特征信息确定展示信息，所述展示信息包括共享车辆的车辆推荐信息和/或使用情况信息；在所述终端设备页面上显示所述展示信息。
本申请实施例之一提供一种共享车辆的信息推送系统，所述系统包括：第一获取模块，用于响应于用户对终端设备的操作指令，获取与所述操作指令相关的特征信息；第一确定模块，用于至少基于所述特征信息确定所述终端设备的展示信息，所述展示信息包括共享车辆的车辆推荐信息和/或使用情况信息；传输模块，用于向所述终端设备发送所述展示信息。
本申请实施例之一提供一种用于共享车辆的信息推送的终端设备，所述终端设备包括：接收模块，用于接收用户打开所述终端设备的操作指令；第二获取模块，用于获取与所述操作指令相关的特征信息；第二确定模块，用于至少基于所述特征信息确定展示信息，所述展示信息包括共享车辆的车辆推荐信息和/或使用情况信息；显示模块，用于在所述终端设备页面上显示所述展示信息。
本申请实施例之一提供一种电子设备，所述电子设备包括至少一个处理器以及至少一个存储器；所述至少一个存储器用于存储计算机指令；所述至少一个处理器用于执行所述计算机指令中的至少部分指令以实现如前所述的共享车辆的信息推送方法。
本申请实施例之一提供一种计算机可读存储介质，所述存储介质存储计算机指令，当计算机读取存储介质中的计算机指令后，计算机执行如前所述的共享车辆的信息推送方法。
附图说明
本申请将以示例性实施例的方式进一步说明，这些示例性实施例将通过附图进行详细描述。这些实施例并非限制性的，在这些实施例中，相同的编号表示相同的结构，其中：
图1是根据本申请一些实施例所示的共享车辆的信息推送系统的应用场景示意图；
图2是根据本申请一些实施例所示的示例性计算设备的示例性硬件组件和/或软件组件的示意图；
图3是根据本申请一些实施例所示的示例性移动设备的示例性硬件组件和/或软件组件的示意图；
图4是根据本申请一些实施例所示的示例性处理设备的示例性模块图；
图5是根据本申请一些实施例所示的示例性终端设备的示例性模块图；
图6是根据本申请一些实施例所示的共享车辆的信息推送方法的示例性流程图；
图7是根据本申请另一些实施例所示的共享车辆的信息推送方法的示例性流程图；
图8是根据本申请另一些实施例所示的共享车辆的信息推送方法的示例性流程图；
图9是根据本申请再一些实施例所示的共享车辆的信息推送方法的示例性流程图；
图10是根据本申请一些实施例所示的共享车辆状态标签确定方法的示例性流程图；
图11是根据本申请再一些实施例所示的共享车辆的信息推送方法的示例性流程图；以及
图12是根据本申请再一些实施例所示的共享车辆的信息推送方法的示例性流程图。
具体实施方式
为了更清楚地说明本申请实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单的介绍。显而易见地，下面描述中的附图仅仅是本申请的 一些示例或实施例，对于本领域的普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图将本申请应用于其它类似情景。除非从语言环境中显而易见或另做说明，图中相同标号代表相同结构或操作。
应当理解，本文使用的“系统”、“装置”、“单元”和/或“模块”是用于区分不同级别的不同组件、元件、部件、部分或装配的一种方法。然而，如果其他词语可实现相同的目的，则可通过其他表达来替换所述词语。
如本申请和权利要求书中所示，除非上下文明确提示例外情形，“一”、“一个”、“一种”和/或“该”等词并非特指单数，也可包括复数。一般说来，术语“包括”与“包含”仅提示包括已明确标识的步骤和元素，而这些步骤和元素不构成一个排它性的罗列，方法或者设备也可能包含其它的步骤或元素。
本申请中使用了流程图用来说明根据本申请的实施例的系统所执行的操作。应当理解的是，前面或后面操作不一定按照顺序来精确地执行。相反，可以按照倒序或同时处理各个步骤。同时，也可以将其他操作添加到这些过程中，或从这些过程移除某一步或数步操作。
本申请的不同实施例的应用场景可以包括但不限于一个或以上网页、浏览器插件和/或扩展、用户终端、定制系统、公司内部分析系统、人工智能机器人等，或其任何组合。应当理解，本文披露的系统和方法的应用场景仅是一些示例或实施例。具有普通技能的本领域，没有进一步的创造性努力，可以将这些方法应用于其他应用场景。例如，其他类似的服务器。
本申请描述的“使用者”、“请求者”、“服务请求者”、“使用请求者”等是可以互换的，是指需要或者订购服务的一方，可以是个人，也可以是工具或者其他实体等。同样地，本申请描述的“运维人员”、“管理人员”、“维修人员”、“服务者”等也是可以互换的，是指提供服务或者协助提供服务的个人、工具或者其他实体等。另外，本申请描述的“用户”可以是需要或者订购服务的一方，也可以是提供服务或者协助提供服务的一方。本申请描述的“终端设备”可以是指需要或者订购服务的一方使用的用户终端，也可以是提供服务或者协 助提供服务的一方使用的用户终端。
本申请中的术语“操作指令”、“请求”、“服务”、“服务请求”和“订单”可以用于指代由使用者、请求者、服务请求者、运维人员、提供者、服务者等或其任何组合发起的，并且可以互换使用。其中，服务请求可以是计费的也可是免费的。
本申请中的用户位置和/或轨迹可以通过嵌入在用户终端中的定位技术来获取，共享车辆的位置和/或轨迹可以通过嵌入在共享车辆中的定位技术来获取。在一些实施例中，可以通过定位技术实时跟踪获取用户位置和/或共享车辆的位置。本申请中使用的定位技术可以包括全球定位系统(GPS)、全球卫星导航系统(GLONASS)、北斗导航系统(COMPASS)、伽利略定位系统(GLONASS)、准天顶卫星系统(QZSS)、基站定位技术、无线保真(Wi-Fi)定位技术等中的一种或其任意组合。以上定位技术中的一个或多个可以在本申请中交换使用。
图1是根据本申请一些实施例所示的共享车辆的信息推送系统的应用场景示意图。
如图1所示，共享车辆的信息推送系统100可以包括服务器110、网络120、用户端(用户终端)130、共享设备140和存储器150。在一些实施例中，服务器110可以响应于用户对用户端130的操作指令，通过网络120从用户端130获取与该操作指令相关的特征信息，以及至少基于所述特征信息确定包括共享车辆的车辆推荐信息和/或使用情况信息的展示信息；并向用户端130发送所述展示信息，以便将所述展示信息显示给用户。
服务器110可以处理从系统100的至少一个组件(例如，用户端130、共享设备140和存储器150)或外部数据源(例如，云数据中心)获取的数据和/或信息。例如，服务器110可以与用户操作指令相关的特征信息，确定推荐车辆并将其展示给用户。又例如，服务器110可以通过移动通信网络接收用户端130发送的开锁指令，并控制共享车辆开锁。再例如，服务器110可以根据共享车辆状态标签，确定需要进行功能升级的共享车辆。
在一些实施例中，服务器110可以是本地的，也可以是远程的。例如，服务器110可以经由网络120访问存储在用户端130、共享设备140和存储器150中的信息和/或数据。又例如，服务器110可以直接与用户端130、共享设备140和存储器150连接已访问存储于其中的数据和/或信息。在一些实施例中，服务器110可以在云平台上实施。仅作为示例，云平台可以包括私有云、公共云、混合云、社区云、分布云、内部云、多层云等或其任意组合。
服务器110可以是一个服务器，还可以是服务器群组。所述服务器群组可以是集中式的，例如数据中心。所述服务器群组也可以是分布式的，例如分布式系统。
在一些实施例中，服务器110可以包括处理设备112。处理设备112可以处理与共享设备相关的服务请求的信息和/或数据以执行本说明书中描述的一个或多个功能。例如，处理设备112可以从用户端130或存储器150获取第一时刻的多个预设区域的共享车辆使用情况，根据第一时刻的共享车辆使用情况对第二时刻存储的所述预设区域内的共享车辆使用情况进行更新，以生成携带所述共享车辆使用情况的展示信息。在一些实施例中，处理设备112可包括至少一个处理单元(例如，单核处理引擎或多核处理引擎)。仅作为示例，处理设备112包括中央处理单元(CPU)、专用集成电路(ASIC)、专用应用指令集处理器(ASIP)、图形处理单元(GPU)、物理处理单元(PPU)、数字信号处理器(DSP)、现场可程序门阵列(FPGA)、可程序逻辑设备(PLD)、控制器、微控制器单元、精简指令集计算机(RISC)、微处理器等，或其任意组合。
在一些实施例中，处理设备112可以为终端设备的一部分。例如，处理设备112可以集成在用户端130中，用于接收用户对用户端130的操作指令，获取与所述操作指令相关的特征信息；以及至少基于所述特征信息确定包括共享车辆的车辆推荐信息和/或使用情况信息的展示信息，并在用户端130的页面上显示所述展示信息。
网络120可以提供信息交换的渠道。网络120可以是单一网络，也可以 是多种网络组合的。仅作为示例，网络120可以包括缆线网络、有线网络、光纤网络、远程通信网络、内部网络、互联网、局域网络(LAN)、广域网路(WAN)、无线局域网络(WLAN)、城域网(MAN)、公共开关电话网络(PSTN)、蓝牙网络、紫蜂网络、近场通讯(NFC)网络、全球行动通讯系统(GSM)网络、码分多址(CDMA)网络、时分多址(TDMA)网络、通用分组无线服务(GPRS)网络、增强数据速率GSM演进(EDGE)网络、宽带码分多址接入(WCDMA)网络、高速下行分组接入(HSDPA)网络、长期演进(LTE)网络、用户数据报协议(UDP)网络、传输控制协议/互联网协议(TCP/IP)网络、短讯息服务(SMS)网络、无线应用协议(WAP)网络、超宽带(UWB)网络、红外线等，或其任意组合。在一些实施例中，网络120可以包括一个或多个网络接入点。例如，网络120可以包括有线或无线网络接入点，如基站和/或互联网交换点120-1、120-2、……，系统100的一个或多个部件可以通过接入点连接到网络120以交换数据和/或信息。
用户端130的所有者可以是用户本人或用户本人之外的其他人。例如，用户端130的所有者A可以使用用户端130发送针对用户B的服务请求，和/或从服务器110接收服务确认和/或信息或指令。在一些实施例中，用户端130的所有者可以是共享设备的使用者，也可以为共享设备的运维人员。在一些实施例中，用户端130可以包括各类具有信息接收和/或发送功能的设备。例如，用户端130可以包括但不限于平板电脑130-1、笔记本电脑130-2、移动设备130-3、台式电脑等，或其任意组合。在一些实施例中，用户端130可以是具有定位功能的设备，从而可以提供用户端130和/或用户的位置信息。位置相关信息可包括位置、高度、速度、加速度、时间等。在一些实施例中，系统100也可以包括其他具有定位功能的设备(例如，卫星定位设备、GPS定位设备)，这些设备可以与系统100中的组件(例如，用户端130、共享设备140等)通信以确定其位置相关信息。
在一些实施例中，用户端130可以包括短距离通信装置。短距离通信技术指作用在距离在毫米级到千米级的，局部范围内的无线通信技术。例如，短距 离通信技术可以包括基于华为Hilink协议、WiFi(IEEE 802.11协议)、Mesh、蓝牙、ZigBee、Thread、Z-Wave、NFC(近距离无线通讯技术，Near Field Communication)、UWB(无载波通信技术，Ultra Wideband)、LiFi(光保真技术，LightFidelity)等。在一些实施例中，用户端130可以通过短距离通信装置与共享设备140建立通信。
在一些实施例中，用户端130可以处理信息和/或数据。例如，用户端130可以响应于用户的操作指令，处理与该操作指令相关的特征信息。在一些实施例中，用户端130可以用于接收和/或展示服务器110发送的信息。例如，用户端130可以将从服务器110获取的共享车辆的展示信息显示在用户端的页面上，以输出给用户。在一些实施例中，用户端130可以将操作指令和/或与操作指令相关的特征信息发送至系统100中的一个或多个组件中。例如，用户端130可以将用户执行操作指令的第一位置、用户的历史出行信息和/或计划出行信息发送至服务器110进行处理，或发送至存储器150进行存储。
在一些实施例中，共享设备140可以包括共享车辆。例如，共享车辆可以包括但不限于共享自行车140-1、共享电单车140-2、共享电动摩托、共享汽车等。在一些实施例中，共享车辆可以包括车辆终端，车辆终端可以与服务器110实现网络通信。例如，通过移动通信网络与服务器110进行信号连接，接收服务器110下发的各种控制指令、信息等，或向服务器110上传其自身状态信息，包括但不限于锁具是否开启或关闭、电池剩余电量、移动速度或定位信息等。在一些实施例中，车辆终端中可以集成短距离通信装置，车辆终端可以通过短距离通信装置与用户端130实现短距离通信。在一些实施例中，车辆终端可以与车辆上的各类传感器进行信号连接，还可以与车辆上的各执行部件具有信号连接。例如，车辆终端可以与车辆上的速度传感器进行信号连接。再例如，车辆终端可以与车辆上的锁具、指示灯执行等部件具有信号连接，控制锁具、指示灯等部件的开启或关闭。
在一些实施例中，共享车辆可以包括输入装置和输出装置。示例性输入装 置可以包括键盘、鼠标、触摸屏和麦克风等，或其任意组合。示例性输出装置可以包括显示设备、扬声器、打印机、投影仪等，或其任意组合。示例性显示设备可以包括液晶显示器(LCD)、基于发光二极管(LED)的显示器、平板显示器、曲面显示器、电视设备、阴极射线管(CRT)等，或其任意组合。在一些实施例中，共享车辆可以包括定位装置，用于提供共享车辆的位置相关信息(例如，GPS信号信息)。示例性地位置相关信息可包括位置、高度、速度、加速度、时间等。在一些实施例中，共享车辆可以包括无线模块，用于扫描无线信息，例如，wifi信号信息、蓝牙信号信息等。
本说明书实施例中，主要以共享车辆为例描述共享车辆的信息推送方法，可以理解的是，在一些实施例中，本说明书提供的信息推送方法也可以适用于其他共享设备，例如共享雨伞、共享滑板、共享充电宝140-3等其他类型的共享物品。
在一些实施例中，存储器150可以存储处理设备112可以执行或使用以完成本说明书描述的示例性方法的数据和/或指令。在一些实施例中，存储器150可包括大容量存储器、可移动存储器、易失性读写存储器、只读存储器(ROM)等或其任意组合。示例性的大容量存储器可以包括磁盘、光盘、固态磁盘等。示例性可移动存储器可以包括闪存驱动器、软盘、光盘、存储卡、压缩盘、磁带等。示例性易失性读写存储器可以包括随机存取存储器(RAM)。示例性RAM可包括动态随机存取存储器(DRAM)、双倍数据速率同步动态随机存取存储器(DDRSDRAM)、静态随机存取存储器(SRAM)、晶闸管随机存取存储器(T-RAM)、零电容随机存取存储器(Z-RAM)等。示例性只读存储器可以包括掩模型只读存储器(MROM)、可编程只读存储器(PROM)、可擦除可编程只读存储器(PEROM)、电可擦除可编程只读存储器(EEPROM)、光盘只读存储器(CD-ROM)、数字多功能磁盘只读存储器等。在一些实施例中，存储器150可在云平台上实现。仅作为示例，云平台可以包括私有云、公共云、混合云、社区云、分布云、内部云、多层云等或其任意组合。
在一些实施例中，系统100中的至少一个组件可以经由网络120访问存储在存储器150中的数据或指令。在一些实施例中，存储器150可以作为后端存储器直接连接到服务器110。在一些实施例中，存储器150可以是服务器110、用户端130和/或共享设备140的一部分。
应当注意的是，上述有关系统100的描述仅仅是为了示例和说明，而不限定本申请的适用范围。对于本领域技术人员来说，在本申请的指导下可以对系统100进行各种修正和改变。然而，这些修正和改变仍在本申请的范围之内。
图2是根据本申请一些实施例所示的示例性计算设备的示例性硬件组件和/或软件组件的示意图。
计算设备可以是计算机，例如图1中的服务器110和/或具有特定功能的计算机，被配置用于实现根据本申请的一些实施例的任何特定系统。计算设备200可以被配置用于实现执行本申请中披露的一个或以上功能。例如，服务器110可以用计算设备200之类的计算机的硬件设备、软件程序、固件或其任何组合来实现。为简洁起见，图2仅描绘了一个计算设备。在一些实施例中，计算设备的功能，提供共享车辆展示信息可能需要的功能，可以由分布式模式中的一组类似平台实现，以分散系统的处理负荷。如图2所示，计算设备200可以包括处理器210、存储器220、输入/输出230和通信端口240。
处理器210可以执行计算指令(程序代码)并执行本说明书描述的共享车辆信息推送系统100的功能。所述计算指令可以包括程序、对象、组件、数据结构、过程、模块和功能(所述功能指本说明书中描述的特定功能)。例如，处理器210可以处理从系统100的其他任何组件获得的操作指令相关的特征信息。在一些实施例中，处理器210可以包括微控制器、微处理器、精简指令集计算机(RISC)、专用集成电路(ASIC)、应用特定指令集处理器(ASIP)、中央处理器(CPU)、图形处理单元(GPU)、物理处理单元(PPU)、微控制器单元、数字信号处理器(DSP)、现场可编程门阵列(FPGA)、高级RISC机(ARM)、可编程逻辑器件以及能够执行一个或多个功能的任何电路和处理器等，或其任意组合。仅为了说明，图2中的 计算设备200只描述了一个处理器，但需要注意的是本说明书中的计算设备200还可以包括多个处理器。本申请中描述的由一个处理器执行的操作和/或方法也可以由多个处理器共同或分别执行。例如，如果本申请中描述的计算设备200的处理器执行操作A和操作B，应当理解的是，操作A和操作B也可以由计算设备200中的两个或两个以上不同处理器共同或分别执行(例如，第一处理器执行操作A和第二处理器执行操作B，或第一处理器和第二处理器共同执行操作A和B)。
存储器220可以存储从系统100的任何其他组件(例如，处理设备112、用户端130和/或共享设备140)获得的数据/信息。在一些实施例中，存储器220可以包括大容量存储器、可移动存储器、易失性读取和写入存储器和只读存储器(ROM)等，或其任意组合。示例性大容量存储器可以包括磁盘、光盘和固态驱动器等。可移动存储器可以包括闪存驱动器、软盘、光盘、存储卡、压缩盘和磁带等。易失性读取和写入存储器可以包括随机存取存储器(RAM)。RAM可以包括动态RAM(DRAM)、双倍速率同步动态RAM(DDR SDRAM)、静态RAM(SRAM)、晶闸管RAM(T-RAM)和零电容(Z-RAM)等。ROM可以包括掩模ROM(MROM)、可编程ROM(PROM)、可擦除可编程ROM(PEROM)、电可擦除可编程ROM(EEPROM)、光盘ROM(CD-ROM)和数字通用盘ROM等。在一些实施例中，存储器220可以存储一个或多个程序和/或指令，用于执行本申请中描述的示例性方法。
输入/输出230可以用于输入或输出信号、数据或信息。在一些实施例中，输入/输出230可以使用户与系统100进行联系。在一些实施例中，输入/输出230可以包括输入装置和输出装置。示例性输入装置可以包括键盘、鼠标、触摸屏和麦克风等，或其任意组合。示例性输出装置可以包括显示设备、扬声器、打印机、投影仪等，或其任意组合。示例性显示设备可以包括液晶显示器(LCD)、基于发光二极管(LED)的显示器、平板显示器、曲面显示器、电视设备、阴极射线管(CRT)等，或其任意组合。
通信端口240可以连接到网络(例如，网络120)以便数据通信。通信端口240可以在处理设备112和用户端130、共享设备140和/或存储器150之间建立连接。所述连接可以是有线连接、无线连接或两者的组合。有线连接可以包括电缆、光缆或电话线等，或其任意组合。无线连接可以包括蓝牙、Wi-Fi、WiMax、WLAN、ZigBee、移动网络(例如，3G、4G或5G等)等，或其任意组合。在一些实施例中，通信端口240可以是标准化端口，如RS232、RS485等。在一些实施例中，通信端口240可以是专门设计的端口。
图3是根据本申请一些实施例所示的示例性移动设备的示例性硬件组件和/或软件组件的示意图。
在一些实施例中，终端设备(例如，用户端130)的部分或全部功能可以通过移动设备300实现。如图3所示，移动设备300可包括通信单元310、显示单元320、图形处理器(GPU)330、中央处理器(CPU)340、输入/输出单元350、内存360和存储单元390。在一些实施例中，移动设备300也可以包括任何其它合适的组件，包括但不限于系统总线或控制器(图中未显示)。在一些实施例中，移动操作系统370(例如，
Figure PCTCN2020141152-appb-000001
Android，Windows
Figure PCTCN2020141152-appb-000002
等)和一个或多个应用程序380可以从存储单元390装载入内存360，以便能够由中央处理器340执行。应用程序380可以包括浏览器或任何其他合适的移动应用程序，用于从服务器110接收和呈现展示信息或其他信息相关的信息。信息流的用户交互可以通过输入/输出单元350实现，并且通过网络120提供给服务器110和/或共享车辆的信息推送系统100的其他组件。
为了实现本申请中描述的各种模块、单元及其功能，计算机硬件平台可以用作本申请中描述的一个或多个元素的硬件平台。具有用户界面元素的计算机可用于实现个人计算机(PC)或任何其他类型的工作站或终端设备的功能。如果适当编程，所述计算机也可以充当本申请描述的服务器。
图4是根据本申请一些实施例所示的示例性处理设备的示例性模块图。
如图4所示，在一些实施例中，处理设备(例如，处理设备112)可以包 括第一获取模块410、第一确定模块420、控制模块430、分析模块440以及传输模块450。这些模块也可以作为应用程序或一组由处理设备读取和执行的指令实现。此外，模块可以是硬件电路和应用/指令的任何组合。例如，当处理设备或处理器执行应用程序/一组指令时，模块可以是处理器的一部分。
第一获取模块410可以用于获取数据或信息。例如，第一获取模块410可以用于获取与操作指令相关的特征信息。在一些实施例中，所述特征信息可以包括用户输入信息(例如，用户输入的起始地、目的地、共享车辆状态标签等)、用户执行操作指令的第一位置、操作指令的发起时间和用户的出行信息等。在一些实施例中，第一获取模块410可以用于获取用户信息。在一些实施例中，用户信息可以包括但不限于用户的历史出行信息、历史订单信息、计划出行信息、用户反馈信息(例如，第一反馈信息、第二反馈信息)等，或其任意组合。在一些实施例中，第一获取模块410可以用于获取用户通过终端设备(例如，运维端或客户端)输入的共享车辆使用情况信息。在一些实施例中，第一获取模块410可以获取用户或共享设备的位置信息。例如，第一获取模块410可以通过用户端130的定位装置获取用户端130的定位位置作为用户执行操作指令的第一位置或用户的第三位置。又例如，第一获取模块410可以从共享车辆的定位装置获取该共享车辆的第二位置。在一些实施例中，第一获取模块410可以用于接收终端设备(例如，运维端)发送的预设区域的范围。在一些实施例中，第一获取模块410可以用于获取筛选出的共享车辆的状态标签对应的预设升级规则。
第一确定模块420可以用于确定展示信息。在一些实施例中，展示信息可以包括共享车辆的车辆推荐信息和/或使用情况信息。在一些实施例中，第一确定模块420可以用于确定用户的出行目的地。例如，第一确定模块420可以基于用户的多条历史出行信息确定多条历史出行路线，以及每条历史出行路线对应的出行起始时间；在所述多条历史出行路线中，将出行起始时间与用户操作指令的发起时间最接近的历史出行路线确定为预估出行路线；确定所述预估出行路线对应的目的地为用户的出行目的地。又例如，第一确定模块420可以获 取用户计划出行信息的出行方式以及出行时间；基于所述出行方式，确定计划出行信息的出行起始地；基于用户执行操作指令的第一位置与所述计划出行信息的出行起始地之间的距离，确定从所述第一位置到所述计划出行信息的出行起始地的预估到达时间；并响应于所述预估到达时间早于所述计划出行信息的出行时间，确定所述计划出行信息的出行起始地为所述用户的出行目的地。在一些实施例中，第一确定模块420可以进一步包括目的地确定单元，用于确定用户的出行目的地。
在一些实施例中，第一确定模块420可以进一步包括推荐单元422、筛选单元424以及信息更新单元426等。
推荐单元422可以用于确定推荐车辆。例如，推荐单元422可以基于确定的用户的出行目的地，从距离用户执行操作指令的第一位置的预设距离范围值内的多台共享车辆中确定第一推荐车辆。具体地，推荐单元422可以确定所述多台共享车辆中每台共享车辆的剩余续航里程；响应于用户出行目的地与预设还车区域之间的距离小于第一预设距离值，确定所述第一位置与所述预设还车区域之间的预估出行里程；基于所述多台共享车辆中每台共享车辆的剩余续航里程与预估出行里程，确定所述多台共享车辆中满足第一预设条件的共享车辆为所述第一推荐车辆。其中，所述第一预设条件可以包括共享车辆的剩余续航里程与预估出行里程之间的距离差值大于第二预设距离值，且剩余续航里程值在所述多台共享车辆中最小。在一些实施例中，推荐单元422可以响应于用户出行目的地与预设还车区域之间的距离不小于第一预设距离值，确定所述多台共享车辆中剩余续航里程值最大的共享车辆为第一推荐车辆。在一些实施例中，推荐单元422可以响应于用户关于第一推荐车辆的第一反馈信息指示用户确定不使用第一推荐车辆，基于所述多台共享车辆的剩余续航里程和/或用户的输入目的地，从所述多台共享车辆中确定第二推荐车辆。在一些实施例，推荐单元422可以根据用户输入的共享车辆的状态标签，从各类型共享车辆中筛选出与所述状态标签对应的共享车辆为第三推荐车辆。在一些实施例中，推荐单元422可 以当第二反馈信息指示用户未寻找到推荐车辆时，确定第四推荐车辆为更新后的推荐车辆。在一些替代性实施例中，推荐单元422可以进一步包括第一推荐单元、第二推荐单元、第三推荐单元和第四推荐单元，分别用于确定第一推荐车辆、第二推荐车辆、第三推荐车辆和第四推荐车辆。
筛选单元424可以用于根据状态标签筛选对应的共享车辆。例如，筛选单元424可以根据用户输入的共享车辆的状态标签，从各类型共享车辆中筛选出与所述状态标签对应的共享车辆。
信息更新单元426可以用于更新共享车辆使用情况。在一些实施例中，信息更新单元426可以根据获取的第一时刻的共享车辆使用情况对第二时刻存储的预设区域内的共享车辆使用情况进行更新，生成携带共享车辆使用情况的展示信息。在一些实施例中，信息更新单元426可以接收运维端发送的投放到预设区域内的所述共享车辆数量；或当接收到运维端发送的在预设区域内的其中一辆共享车辆的第一扫码信息时，将该预设区域对应的共享车辆数量加一以对共享车辆数量进行更新。在一些实施例中，信息更新单元426可以当接收到客户端发送的在预设区域内的其中一辆共享车辆的第二扫码信息时，将该预设区域对应的共享车辆数量减一以对共享车辆数量进行更新。在一些实施例中，信息更新单元426可以接收用户通过终端设备发送的车辆标识信息，根据车辆表示信息更新共享车辆的故障情况。其中，车辆标识信息用于标记预设区域内的共享车辆是否故障。
控制模块430可以用于控制共享设备。例如，共享车辆可以配置有提醒装置，控制模块430可以计算用户的第三位置与推荐车辆的第二位置之间的距离；当用户的第三位置与推荐车辆的第二位置之间的距离小于第三预设距离值时，控制共享车辆的提醒装置发出提醒信号。在一些实施例中，所述提醒装置可以为闪光灯。控制模块430可以控制所述闪光灯进行闪烁，其中，用户的第三位置与推荐车辆的第二位置之间的距离越小，控制闪光灯进行闪烁的频率越高。在一些实施例中，控制模块430还可以用于将推荐车辆对应的车辆状态更改为预 约状态；并当接收到用户发送的骑行开始指令时，控制推荐车辆开锁。在一些实施例中，控制模块430还可以用于按照与状态标签对应的预设升级规则，对位于目标区域的筛选出的共享车辆进行功能升级。
在一些实施例中，控制模块430可以进一步包括计算单元432和控制单元434。计算单元432可以用于计算用户的第三位置与推荐车辆的第二位置之间的距离，控制单元434可以用于当用户的第三位置与推荐车辆的第二位置之间的距离小于第三预设距离值时，控制共享车辆的提醒装置发出提醒信号。
分析模块440可以用于分析共享车辆的状态标签。例如，分析模块440可以用于获取至少一个共享车辆发送的至少一个状态数据；针对每个共享车辆发送的每个状态数据，获取该状态数据所属的状态类型，并获取状态类型对应的预设评估策略；针对每个共享车辆发送的属于每种状态类型的状态数据，采用与状态类型对应的预设评估策略进行分析，得到与发送属于状态类型的状态数据的共享车辆对应的状态标签。在一些实施例中，分析模块440可以响应在终端的策略配置界面的配置操作，获得预设评估策略。
在一些实施例中，分析模块440可以进一步包括统计单元442和分析单元444。统计单元442可以用于统计各预设区域中包括的筛选出的与用户输入的状态标签对应的共享车辆的数量，分析单元444可以用于根据所述各预设区域中包括的筛选出的共享车辆的数量，确定需要进行功能升级的目标区域。具体地，统计单元442可以从包括筛选出的共享车辆的各预设区域中选取参考区域，并计算包括筛选出的共享车辆的各预设区域中除参考区域之外的其他每个预设区域中筛选出的共享车辆的数量与所述参考区域中筛选出的所述共享车辆的数量的数据差值；分析单元444可以根据所述数据差值确定需要进行功能升级的目标区域。
传输模块450可以用于传输信息。例如，传输模块450可以将确定的展示信息传输给终端设备。在一些实施例中，传输模块450可以用于向终端设备发送推荐车辆的相关信息。例如，传输模块450可以将第一推荐车辆对应的剩 余续航里程发送给用户端130以显示给用户。在一些实施例中，传输模块450可以用于向终端设备(例如，用户端130)发送导航信息。例如，传输模块450可以根据用户的第三位置与推荐车辆的第二位置，向用户端130发送从所述第三位置到达所述第二位置的导航信息，用户端130可以将所述导航信息展示给用户。在一些实施例中，传输模块450还可以用于向筛选出的每个共享车辆分别发送控制指令，以禁止筛选出的共享车辆发送与该共享车辆对应的状态数据。
应当理解，图4所示的处理设备400及其模块可以利用各种方式来实现。例如，在一些实施例中，处理设备400及其模块可以通过硬件、软件或者软件和硬件的结合来实现。其中，硬件部分可以利用专用逻辑来实现；软件部分则可以存储在存储器中，由适当的指令执行系统，例如微处理器或者专用设计硬件来执行。本领域技术人员可以理解上述的方法和系统可以使用计算机可执行指令和/或包含在处理器控制代码中来实现，例如在诸如磁盘、CD或DVD-ROM的载体介质、诸如只读存储器(固件)的可编程的存储器或者诸如光学或电子信号载体的数据载体上提供了这样的代码。本申请的系统及其模块不仅可以有诸如超大规模集成电路或门阵列、诸如逻辑芯片、晶体管等的半导体、或者诸如现场可编程门阵列、可编程逻辑设备等的可编程硬件设备的硬件电路实现，也可以用例如由各种类型的处理器所执行的软件实现，还可以由上述硬件电路和软件的结合(例如，固件)来实现。
需要注意的是，以上对于处理设备400及其模块的描述，仅为描述方便，并不能把本说明书限制在所举实施例范围之内。可以理解，对于本领域的技术人员来说，在了解该系统的原理后，可能在不背离这一原理的情况下，对各个模块进行任意组合，或者构成子系统与其他模块连接。在一些实施例中，第一获取模块410、第一确定模块420、控制模块430、分析模块440以及传输模块450可以是一个系统中的不同模块，也可以是一个模块实现上述的两个或两个以上模块的功能。在一些实施例中，第一获取模块410、第一确定模块420、控制模块430、分析模块440以及传输模块450可以共用一个存储模块，各个模块也可以 分别具有各自的存储模块。诸如此类的变形，均在本说明书的保护范围之内。
图5是根据本申请一些实施例所示的示例性终端设备的示例性模块图。
如图5所示，在一些实施例中，终端设备(例如，用户端130)可以包括接收模块510、第二获取模块520、第二确定模块530以及显示模块540。这些模块也可以作为应用程序或一组由处理器读取和执行的指令实现。此外，模块可以是硬件电路和应用/指令的任何组合。例如，当中央处理器340执行应用程序/一组指令时，模块可以是处理器的一部分。
接收模块510可以用于接收用户对终端设备的操作指令。例如，操作指令可以包括用户打开终端设备的显示页面、共享服务APP等，和/或用户通过终端设备发起用车服务请求、位置获取请求等，和/或用户通过终端设备输入反馈信息等。在一些实施例中，接收模块510还可以用于接收服务器(例如，服务器110)发送的指令和/或信息。例如，接收模块510可以从服务器110接收共享车辆的展示信息、提醒信息、警报信息等。
第二获取模块520可以用于获取与操作指令相关的特征信息。在一些实施例中，第二获取模块520可以从终端设备获取与操作指令相关的特征信息。例如，第二获取模块520可以通过用户端130的定位装置获取用户执行操作指令的第一位置、用户的第三位置等。又例如，第二获取模块520可以通过用户端130获取用户输入的出行信息、状态标签、反馈信息、操作指令的发起时间等。在一些实施例中，第二获取模块520可以从服务器(例如，服务器110)获取与操作指令相关的特征信息。例如，第二获取模块520可以基于用户操作指令，从服务器110获取相应的特征信息。
第二确定模块530可以用于确定展示信息。在一些实施例中，展示信息可以包括共享车辆的车辆推荐信息和/或使用情况信息、以及提示信息等。在一些实施例中，第二确定模块530可以通过处理器(例如，中央处理器340)，基于操作指令相关的特征信息确定展示信息。例如，第二确定模块530可以基于用户执行操作指令的第一位置、操作指令的发起时间和用户的出行信息，确定第 一推荐车辆、第二推荐车辆等推荐车辆和/或车辆推荐信息。又例如，第二确定模块530可以基于用户输入的共享车辆状态标签，从各类型共享车辆中筛选出与所述状态标签对应的共享车辆，和/或根据各预设区域中包括的筛选出的共享车辆的数量，确定需要进行功能升级的目标区域。在一些实施例中，第二确定模块530可以基于操作指令相关的特征信息，从服务器获取相关的展示信息。
显示模块540可以用于显示展示信息。例如，显示模块540可以用于在显示界面显示推荐车辆、推荐车辆的剩余续航里程、推荐车辆的导航信息、车辆的使用情况信息等信息，或其任意组合。
在一些实施例中，终端设备500还可以包括传输模块。传输模块可以用于与服务器进行数据或信息传输，例如，终端设备500可以通过其传输模块向服务器传输或从服务器获取展示信息、操作指令特征信息等。
应当理解，图5所示的终端设备500及其模块可以利用各种方式来实现。例如，在一些实施例中，终端设备500及其模块可以通过硬件、软件或者软件和硬件的结合来实现。其中，硬件部分可以利用专用逻辑来实现；软件部分则可以存储在存储器中，由适当的指令执行系统，例如微处理器或者专用设计硬件来执行。本领域技术人员可以理解上述的方法和系统可以使用计算机可执行指令和/或包含在处理器控制代码中来实现，例如在诸如磁盘、CD或DVD-ROM的载体介质、诸如只读存储器(固件)的可编程的存储器或者诸如光学或电子信号载体的数据载体上提供了这样的代码。本申请的系统及其模块不仅可以有诸如超大规模集成电路或门阵列、诸如逻辑芯片、晶体管等的半导体、或者诸如现场可编程门阵列、可编程逻辑设备等的可编程硬件设备的硬件电路实现，也可以用例如由各种类型的处理器所执行的软件实现，还可以由上述硬件电路和软件的结合(例如，固件)来实现。
需要注意的是，以上对于终端设备500及其模块的描述，仅为描述方便，并不能把本说明书限制在所举实施例范围之内。可以理解，对于本领域的技术人员来说，在了解该系统的原理后，可能在不背离这一原理的情况下，对各个模块 进行任意组合，或者构成子系统与其他模块连接。
为了使得本领域技术人员能够使用本申请内容，结合特定应用场景“共享单车”，给出以下实施方式。对于本领域技术人员来说，在不脱离本申请的精神和范围的情况下，可以将这里定义的一般原理应用于其它实施例和应用场景。虽然本申请主要围绕共享单车进行描述，但是应该理解，这仅是一个示例性实施例。本申请可以应用于任何其它场景。例如，本申请可以应用于共享电动车、共享电动摩托、共享滑板等其他共享出行设备，也可以是共享充电宝、共享雨伞等共享物品。
图6是根据本申请一些实施例所示的共享车辆的信息推送方法的示例性流程图。
在一些实施例中，流程600可以由处理设备(例如，图1所示的处理设备112)执行。例如，流程600可以以程序或指令的形式存储在存储设备(例如，存储器150或处理设备的存储单元)中，当处理器210或图4所示的模块执行程序或指令时，可以实现流程600。在一些实施例中，流程600可以利用以下未描述的一个或以上附加操作，和/或不通过以下所讨论的一个或以上操作完成。另外，如图6所示的操作的顺序并非限制性的。如图6所示，流程600可以包括以下步骤。
步骤610，响应于用户对终端设备的操作指令，获取与所述操作指令相关的特征信息。在一些实施例中，步骤610可以由第一获取模块410执行。
在一些实施例中，终端设备可以包括共享车辆使用者使用的客户端、和/或共享平台的运维人员使用的运维端等。例如，共享车辆使用者可以通过客户端发起共享车辆相关的用车、还车、找车等服务请求。运维人员是指对共享设备进行维护、调度、维修等的管理人员。运维人员可以通过运维端发起车辆升级、维修、调度、故障申报等请求。
操作指令可以用于反映用户(例如，共享车辆使用者和/或运维人员)对终端设备的操作。例如，操作指令可以包括但不限于用户打开终端设备的共享车 辆APP，或者打开APP后点击其中的按钮、页面或链接等，或在浏览器或其他页面中输入搜索指令等。通过获取终端设备的操作指令，可以确定用户的需求。例如，通过获取用户打开用户端130的共享车辆APP中的显示页面的操作指令，可以确定该用户可能需要获取周围可用共享车辆；或者通过获取用户在用户端130点击“开锁”按钮的操作指令，可以确定该用户需要使用对应共享车辆。在一些实施例中，操作指令的形式可以包括语音、文本、面部动作(例如，眨眼)、手势、触屏操作等，或其任意组合。
在一些实施例中，操作指令相关的特征信息可以包括但不限于操作指令的发起时间、用户执行操作指令时的第一位置、用户的出行信息、用户的订单信息、用户输入的共享车辆状态标签、用户输入的目的地等，或其任意组合。
在一些实施例中，处理设备可以从服务器(例如，服务器110)获取操作指令相关的特征信息。在一些实施例中，处理设备可以从终端设备(例如，用户端130)获取与操作指令相关的特征信息。在一些实施例中，处理设备可以从任意合理的渠道，和/或通过任何可行的方式获取操作指令相关的特征信息，本说明书对此不做限制。
步骤620，至少基于所述特征信息确定所述终端设备的展示信息。在一些实施例中，步骤620可以由第一确定模块420执行。
展示信息是指通过终端设备(例如，用户端130)呈现给用户的与操作指令相关的信息。在一些实施例中，展示信息可以包括共享车辆的车辆推荐信息、和/或使用情况信息、和/或车辆的状态信息。例如，共享车辆推荐信息可以包括推荐车辆、推荐车辆的位置信息、推荐车辆的续航里程信息等；共享车辆使用情况信息可以包括附近可用共享车辆数量、车辆是否有故障等；车辆的状态信息可以包括车龄、型号、颜色、寿命、耗油/耗电量等。
在一些实施例中，处理设备可以基于用户执行操作指令时的第一位置、操作指令的发起时间、用户出行信息、用户输入目的地、用户输入的共享车辆状态标签等中的至少一种，确定推荐车辆。例如，第一确定模块420可以基于所述第 一位置、操作指令的发起时间和用户的出行信息，确定用户的出行目的地；基于出行目的地与预设还车区域之间的距离，从距离所述第一位置的预设距离范围值内的多台共享车辆中确定第一推荐车辆。又例如，第一确定模块420可以响应于用户的第一反馈信息指示该用户确定不使用第一推荐车辆时，基于所述多台共享车辆的剩余续航里程和/或用户的输入目的地，从所述多台共享车辆中确定第二推荐车辆。再例如，第一确定模块420可以根据用户输入的状态标签，从各类型共享车辆中筛选出与所述状态标签对应的共享车辆为第三推荐车辆。更多关于推荐车辆确定的相关内容，可以参见本说明书其他部分(例如，图7-8及其相关描述)，此处不再赘述。
在一些实施例中，处理设备可以基于特征信息确定共享车辆使用情况信息。例如，第一确定模块420可以获取第一时刻的多个预设区域内的共享车辆使用情况；根据第一时刻的共享车辆使用情况对第二时刻存储的所述预设区域内的共享车辆使用情况进行更新，生成携带共享车辆使用情况的展示信息。更多关于共享车辆使用情况信息确定的内容，可以参见本说明书其他部分(例如，图11及其相关描述)，此处不再赘述。
步骤630，向所述终端设备发送所述展示信息。在一些实施例中，步骤630可以由传输模块450执行。
在一些实施例中，处理设备可以将确定的展示信息发送给终端设备，以便终端设备将该展示信息显示给用户。
在一些实施例中，处理设备可以根据用户的第三位置和推荐车辆的第二位置，为用户提供从第三位置到第二位置的导航信息。用户的第三位置是指用户的当前位置。在一些实施例中，用户的第三位置可以与用户执行操作指令时的第一位置相同或不同。例如，终端设备接收到展示信息并将其显示给用户后，用户已经从第一位置步行了一段距离，此时用户的第三位置为用户看到展示信息后的位置。在一些实施例中，处理设备可以实时更新用户的第三位置，并计算用户第三位置与推荐车辆第二位置之间的距离，当用户第三位置与推荐车辆第二位 置之间的距离小于第三预设距离值时，控制共享车辆的提醒装置发出提醒信号。在一些实施例中，当提醒装置为闪光灯时，处理设备可以在用户的第三位置与推荐车辆的第二位置之间的距离越小，控制闪光灯进行闪烁的频率越高。
在一些实施例中，处理设备向用户发送推荐车辆及其相关信息后，可以将推荐车辆的状态更改为预约状态。在一些实施例中，处理设备可以在接收到用户发送的骑行开始指令时，控制相应推荐车辆自动开锁。仅作为示例，骑行开始指令可以为用户点击APP中“确定使用共享车辆”按钮，或用户点击共享车辆APP中“开锁”按钮等。
在一些实施例中，处理设备还可以统计各预设区域中包括的根据状态标签筛选出的共享车辆的数量；根据各预设区域中包括的筛选出的共享车辆的数量，确定需要进行功能升级的目标区域。运维人员或服务器可以根据状态标签对应的预设升级规则，对位于目标区域的筛选出的共享车辆进行功能升级。关于状态标签以及功能升级的更多内容，可以参见本说明书其他部分(例如，图9-10及其相关描述)，此处不再赘述。
应当注意的是，上述有关流程600的描述仅仅是为了示例和说明，而不限定本申请的适用范围。对于本领域技术人员来说，在本申请的指导下可以对流程600进行各种修正和改变。然而，这些修正和改变仍在本申请的范围之内。
图7是根据本申请另一些实施例所示的共享车辆的信息推送方法的示例性流程图。
如图7所示，本实施例中提供的信息推送方法可以通过用户执行操作指令的第一位置和操作指令的发起时间以及用户出行信息，预测用户的出行目的地，并基于预测的出行目的地与预设还车区域之间的距离进行车辆推荐，该方法可以基于用户的出行目的地与预设还车区域之间的距离，向用户推荐适合其使用的车辆，满足用户的出行需求的同时，可以通过用户的合理使用车辆，提高车辆可以被归还至预设还车区域的概率，进而通过用户的合理使用辅助实现对车辆的管理和调度，有助于提高车辆调度的合理性以及车辆管理的便捷性。
在一些实施例中，流程700可以由处理设备(例如，图1所示的处理设备112)执行。例如，流程700可以以程序或指令的形式存储在存储设备(例如，存储器150或处理设备的存储单元)中，当处理器210或图4所示的模块执行程序或指令时，可以实现流程700。在一些实施例中，流程700可以利用以下未描述的一个或以上附加操作，和/或不通过以下所讨论的一个或以上操作完成。另外，如图7所示的操作的顺序并非限制性的。如图7所示，流程700可以包括以下步骤。
步骤710，基于用户执行操作指令的第一位置、操作指令的发起时间和用户出行信息，确定用户出行目的地。在一些实施例中，步骤710可以由第一确定模块420执行。
在一些实施例中，处理设备可以在检测到用户对终端设备的操作指令为发起用车服务请求时，获取用户执行操作指令的第一位置、操作指令的发起时间和用户出行信息。在一些实施例中，处理设备可以在检测到用户打开与共享平台相匹配的位于终端设备上的应用程序时，确定用户发起了用车服务请求；或可以在对应的应用程序的界面设计时，设计一个开始或其他相关按钮，在用户点击触发这个按钮时，确定检测到用户发起用车服务请求。
仅作为示例，处理设备可以当检测到用户的用车服务请求时，获取接收到用车服务请求时用户所处的第一位置和检测到用车服务请求时的请求时间(即操作指令的发起时间)。其中，用户的第一位置是用户在发起用车服务请求时所处的位置。对于用户所处的第一位置的定位，可以是通过定位装置追踪到的用户在发出用车服务请求时，用户所用的终端设备的位置；或者用户所处的第一位置可以是，用户在应用程序上点击触发用车服务请求后，所述应用程序弹出询问窗口，然后由用户输入此次用车服务请求的起始地，根据输入的起始地确定的位置。
在一些实施例中，处理设备可以根据获取到的用户的出行信息，用户的第一位置以及用户发起用车服务请求时的请求时间(即操作指令的发起时间)，确定用户在提出此次用车服务请求时，可能会选择的出行路线，并根据所述出行路 线预测用户此次的出行目的地。
在一些实施例中，用户的出行信息可以包括两个方面，一个方面是，用户之前使用车辆的历史出行信息，所述历史出行信息中包括用户的出行起始时间以及出行路线等信息；另一方面是，用户的计划出行信息，所述计划出行信息中包括用户的计划出行时间、计划出行目的地以及计划出行方式等信息。这里，所述请求时间可以是在多条历史出行信息中，用来确定更接近此次用户出行信息的筛选条件，也可以是在计划出行信息中作为用户是否考虑使用车辆的依据。
仅作为示例，当用户出行信息为历史出行信息时，处理设备可以基于用户的多条历史出行信息确定多条历史出行路线，以及每条历史出行路线对应的出行起始时间；在所述多条历史出行路线中，将出行起始时间与操作指令的发起时间(例如，用户发起用车服务请求时的请求时间)最接近的历史出行路线确定为目标路线(即预估出行路线)；并确定目标路线对应的目的地为用户此次的出行目的地。
在用户使用应用程序进行车辆选择以及骑行时，在应用程序中会保存用户的历史出行信息，根据对用户的历史出行信息的分析，可以得知在某一时间段内用户更倾向的骑行目的地。例如，用户的历史出行信息显示，在上午8:00-9:00这个时间段，一般情况下，用户都习惯骑车去公司，所以可以根据用户发起用车服务请求的时间是否在该时间段内，来确定用户可能要去的出行目的地。
其中，在同一时间段可能存在不止一条历史出行路线，这时可以通过横向比较，综合统计一段时间内(例如，几天或几周等)在同一时间段内，用户的哪一条历史出行路线的出现次数最多，将出现次数最多的历史出行路线的目的地，确定为用户此次的出行目的地。
作为又一示例，当用户出行信息为计划出行信息时，处理设备可以获取计划出行信息的计划出行方式以及计划出行时间；基于计划出行方式，确定计划出行信息的出行起始地；基于用户的第一位置与计划出行信息的出行起始地之间的距离，确定从所述第一位置到所述计划出行信息的出行起始地的预估到达时 间；响应于预估到达时间早于计划出行时间，确定计划出行信息的出行起始地为用户此次的出行目的地。
一般情况下，用户的计划出行信息的计划出行目的地都是距离用户当前位置比较远的地方，例如，跨省、跨国、跨市出行等，用户可以根据出行目的地选择对应的出行方式，例如，可以是搭乘飞机、火车、客车甚至是轮船等，针对于不同的出行方式用户需要到机场、火车站、客车站以及码头等搭乘对应的交通工具出行。在本实施例中，将机场、火车站、客车站以及码头确定为用户的出行起始地。
例如，用户需要从B市搭乘火车到S市出差，计划出行信息显示用户所选车次的开车时间为上午10:00，用户此时位置距离B市火车站的距离为15km，处理设备接收到用户服务请求的时间为上午8:00，以历史经验来看，人类的平均骑行速度为15km/h-22km/h，以最慢的骑行速度计算，一个小时后即9:00就可以到达火车站，在开车时间10:00之前，因此，用户可以通过骑行到达火车站，可以把火车站作为用户此次的出行目的地。
在一些实施例中，对于用户的历史出行信息，处理设备可以根据用户在应用程序上的身份标识(例如，用户名、用户ID、用户手机号等)获取用户在预设时间间隔内(例如，半个月内、一个月内、三个月内、一年内等)的多条历史出行信息。在一些实施例中，处理设备可以从数据库(例如，存储器150)获取用户历史出行信息。对于用户的计划出行信息，在一些实施例中，处理设备可以从用户的出行计划表中获取。在一些实施例中，处理设备可以通过其他任意可行的方式以及从其他任意合理的渠道获取用户历史出行信息和/或计划出行信息，本说明书对此不做限制。
步骤720，获取距离所述第一位置的预设距离范围值内的多台共享车辆，以及每台共享车辆的剩余续航里程。在一些实施例中，步骤720可以由第一获取模块410或第一确定模块420执行。
在一些实施例中，在设置与用户第一位置的预设距离范围时，可以用户能 够找到共享车辆的最大距离为参考。例如，20米、50米、100米、200米、300米、500米、1千米等用户可以通过步行就能够从第一位置到达共享车辆当前停车位置的距离。以共享电单车为例，一般情况下，共享电单车都会停靠在固定的还车点(即预设还车区域)，在计算用户第一位置与车辆之间的距离可以近似认为是用户第一位置与固定还车点之间的距离。在一些实施例中，无论是车辆还是固定的还车点，服务平台都可以定位在它们所在位置，例如，可以通过在共享车辆中安装定位装置的方式来保证后台可以实时追踪到车辆的位置，保证快速定位车辆，防止车辆丢失。仅作为示例，处理设备可以将预设距离范围设置为0-300米，获取距离用户第一位置300米以内的还车点内的多台共享车辆。在一些实施例中，所述多台共享车辆可以为满足预设距离范围的还车点内的所有共享车辆、或部分共享车辆、或可用共享车辆等。
剩余续航里程可以反映车辆在当前油量或电量的基础上，所能够行驶的最大里程。在一些实施例中，处理设备可以获取共享车辆的剩余电量/油量，根据共享车辆的剩余电量/油量确定其剩余续航里程。在一些实施例中，处理设备可以直接从数据库(例如，存储器150)或共享车辆(例如，共享电单车140-2)端获取车辆的剩余续航里程。
步骤730，基于出行目的地与预设还车区域之间的距离，从所述多台共享车辆中确定第一推荐车辆。在一些实施例中，步骤730可以由第一确定模块420执行。
预设还车区域是指共享服务平台指定的车辆还车点。在一些实施例中，预设还车区域可以根据以下信息确定：地理位置的路况信息(例如，交通主路、辅路、岔路口、地铁口、公交站等)、区域类型(例如，住宅区、商圈、学校等)、用户需求、交通管控信息等，或其任意组合。
在一些实施例中，处理设备可以检测在距离所述出行目的地预设还车距离范围内的车辆还车点(即预设还车区域)与所述出行目的地之间的还车距离是否小于第一预设距离。可以理解，出行目的地预设还车距离范围内的车辆还车点 是在指计算两者之间距离有意义的距离范围，例如，出行目的地在A市，而要计算B市的还车点与出行目的地之间的距离是没有意义的。本实施例中，限定在出行目的地预设还车距离范围内查找车辆还车点，可以保证本方案的可实施性。在一些实施例中，所述预设还车距离范围可以以与预设的两个还车点之间的距离为基准进行限定。
第一预设距离可以表示出行目的地靠近还车点的最大距离，即是指用户在将共享车辆停放在还车点之后能够很快到达出行目的地。例如，第一预设距离可以为50米、150米、280米、700米、800米、1000米等较短距离。
在一些实施例中，处理设备可以响应于距离用户出行目的地预设还车距离范围内的预设还车区域与所述出行目的地之间的距离小于第一预设距离值，计算用户的第一位置与所述预设还车区域之间的行驶距离(即预估出行里程)。如果出行目的地与预设还车距离范围内的预设还车区域之间的还车距离小于第一预设距离值，在这种情况下用户将共享车辆归还到预设还车区域之后，可以很便捷的到达出行目的地。为了共享车辆的统一管理，一般是将共享车辆停放在预设还车区域，所以在这种情况下，需要计算用户的第一位置与预设还车区域之间的行驶距离。
在一些实施例中，在所述出行目的地的预设还车距离范围内可能存在不止一个预设还车点。这种情况下可以有两种处理方式：一种是计算每一个还车点(即预设还车区域)与所述出行目的地之间的还车距离，选取距离所述出行目的地最近的还车点，计算该还车点与用户第一位置之间的行驶距离(即预估出行里程)；另一种是在至少一个还车点中确定出位于用户的可能骑行路线上的还车点，计算该还车点与用户第一位置之间的行驶距离(即预估出行里程)。例如，在出行目的地的预设还车距离范围内存在A、B两个还车点，根据用户的出行信息以及用户的第一位置可知，用户的骑行路线经过A还车点，没有经过B还车点，此时需要计算的就是还车点A与用户的第一位置的行驶距离。
在一些实施例中，处理设备可以基于所述多台共享车辆中每台共享车辆 的剩余续航里程与所述预估出行里程，确定多台共享车辆中满足第一预设条件的共享车辆为第一推荐车辆。其中，第一预设条件可以为共享车辆的剩余续航里程与预估出行里程之间的距离差值大于第二预设距离值，且该共享车辆的剩余续航里程值在所述多台共享车辆中最小。
具体地，处理设备可以先基于所述多台共享车辆中每台共享车辆的剩余电量对应的剩余行驶距离(即剩余续航里程)与所述行驶距离(即预估出行里程)之间的距离差值，确定出所述距离差值大于第二预设距离值的多台候选车辆。所述第二预设距离值是可以保证推荐给用户的共享车辆对应的剩余行驶距离可以到达用户的出行目的地的最小距离，第一预设距离值最小可以为0。进一步地，处理设备可以将所述多台候选车辆中，剩余行驶距离最小的候选车辆确定为供用户骑行的第一推荐车辆。对于推荐给用户的车辆，从更容易给车辆换电瓶的角度来考虑，需要将候选车辆中剩余行驶距离最小的一台车辆作为推荐给用户使用的首选车辆。在一些实施例中，如果存在最小的剩余行驶距离的车辆不止一台，可以再次确定每台候选车辆与用户第一位置的距离，从多台候选车辆中选择距离用户第一位置最近的一台候选车辆，将其确定为供用户骑行的第一推荐车辆。由于定位系统的定位精度问题，可能存在与用户的第一位置之间的距离比较接近的至少两台候选车辆，在一些实施例中，对于这些候选车辆可以根据车辆位置是否在用户第一位置与出行目的地之间的连线上来进一步筛选，即选择更靠近第一位置与出行目的地之间连线的一台候选车辆作为第一推荐车辆。
在一些实施例中，处理设备可以响应于用户出行目的地与预设还车区域之间的距离不小于第一预设距离值，确定所述多台共享车辆中剩余续航里程值最大的共享车辆为供用户骑行的第一推荐车辆。如果出行目的地与预设还车距离范围内的还车点之间的还车距离大于或等于第一预设距离值，需要考虑用户在将共享车辆骑行到目的地之后，是否还可以供下一个用户将这辆车骑到还车点，以便后续对该车辆进行换电管理，因此，在这种情况下可以直接将所述多台共享车辆中剩余续航里程值最大的共享车辆确定为供用户骑行的第一推荐车辆。
在一些实施例中，当存在不止一台共享车辆的剩余续航里程值最大时，可以计算对应剩余续航里程值最大的每台共享车辆的位置与用户当前位置(如，用户第一位置)之间的距离，选择距离用户最近的一台车辆作为第一推荐车辆推荐给用户。
本实施例中，在检测到用户的用车服务请求时，获取用户的第一位置以及用户发起服务请求的请求时间，并根据用户的出行信息，预测用户的出行目的地；根据预测出来的出行目的地与预设还车范围内车辆还车点之间的还车距离，从用户的周围确定出能够供用户骑行的第一推荐车辆，可以通过用户的出行目的地与车辆还车点之间的距离，向用户推荐适合使用的车辆，满足用户的出行需求的同时，可以通过用户的合理使用车辆，提高车辆可以被归还至车辆还车点的概率，进而通过用户的合理使用辅助实现对车辆的管理和调度，有助于提高车辆调度的合理性以及车辆管理的便捷性。
步骤740，将所述第一推荐车辆对应的剩余续航里程显示给用户，并获取用户的第一反馈信息。在一些实施例中，步骤740可以由第一获取模块410和/或传输模块450执行。
在一些实施例中，处理设备可以在将确定的第一推荐车辆发送终端设备的之后或同时，将该第一推荐车辆的剩余续航里程发送给终端设备以显示给用户，并获取用户的第一反馈信息。其中，所述第一反馈信息可以指示用户确定使用或不适用所述第一推荐车辆。在一些实施例中，处理设备可以通过向用户发送询问是否使用第一推荐车辆的信息，进一步获取用户的第一反馈信息。在一些实施例中，处理设备可以在向用户发送第一推荐车辆剩余续航里程的同时，或间隔特定时间后向用户发送询问是否使用第一推荐车辆的信息。
在一些实施例中，将剩余续航里程显示给用户、询问用户是否使用第一推荐车辆的形式均可以为通过弹窗的形式展示给用户，并且可以在询问用户是否使用第一推荐车辆的窗口中设计两个按钮，例如，可以简单的设置为“是”和“否”按钮，根据用户对按钮的点击情况确定用户第一反馈信息指示的内容。
在一些实施例中，处理设备还可以向用户发送其他与共享车辆相关的信息。例如，处理设备112可以向用户发送推荐车辆的车龄、寿命、器件状态等信息。
步骤750，响应于用户不使用第一推荐车辆，基于共享车辆的剩余续航里程和/或用户的输入目的地，从多台共享车辆中确定第二推荐车辆。在一些实施例中，步骤750可以由第一确定模块420执行。
在一些实施例中，若第一反馈信息指示用户确定不使用第一推荐车辆，处理设备可以获取用户输入的输入目的地；基于在距离所述输入目的地预设还车距离范围内的车辆还车点与所述输入目的地之间的还车距离，从所述多台车辆中确定向所述用户推荐的第二推荐车辆。在一些实施例中，提示用户输入目的地可以通过弹窗形式展示给用户，用户可以在弹窗中或页面的其他输入框中输入目的地。
仅作为示例，若第一反馈信息指示用户确定不使用第一推荐车辆，处理设备可以获取用户输入的输入目的地，响应于距离输入目的地预设还车距离范围内的预设还车区域与输入目的地之间的距离小于第一预设距离值，确定第一位置与所述预设还车区域之间的出行里程；基于该出行里程值和所述多台共享车辆中每台共享车辆的所述剩余续航里程的距离差，将该距离差值大于第二预设距离值，且剩余续航里程值在所述多台共享车辆中最小的共享车辆确定为第二推荐车辆。
在一些实施例中，若第一反馈信息指示用户确定不使用第一推荐车辆，处理设备还可以计算所述输入目的地与第一位置的出行里程，基于该出行里程值和所述多台共享车辆中每台共享车辆的所述剩余续航里程的距离差，将该距离差值大于第二预设距离值，且剩余续航里程值在所述多台共享车辆中最小的共享车辆确定为第二推荐车辆。
在一些实施例中，若第一反馈信息指示用户确定不使用第一推荐车辆，处理设备可以获取用户输入的实际出行里程；基于在距离出行目的地预设还车距 离范围内的车辆还车点与所述出行目的地之间的还车距离，以及实际出行里程和车辆剩余续航里程，从所述多台车辆中确定向所述用户推荐的第二推荐车辆。
在一些实施例中，处理设备可以在将确定的第二推荐车辆发送给用户的同时或之后，向用户发送第二推荐车辆的剩余续航里程或其他相关信息。
当第一推荐车辆为所述多台共享车辆中剩余续航里程值最大的车辆时，如果所述第一反馈信息指示用户确定不使用该第一推荐车辆，用户不使用该第一推荐车辆的原因可能是该车辆的剩余续航里程至不足以使用户骑行到达用户想要去的出行目的地，由于现阶段显示给用户的第一推荐车辆已经是在可以推荐给用户的车辆中剩余续航里程值最大的，在该第一推荐车辆还是不满足用户的用车需求的情况下，现阶段没有其他满足用户用车需求的共享车辆可以推荐给用户，此时，可以向用户发送获取推荐车辆失败信息，并结束当前共享车辆推荐流程。
步骤760，为用户提供推荐车辆的位置信息。在一些实施例中，步骤760可以由第一确定模块420执行。
在一些实施例中，处理设备可以响应于第一反馈信息指示用户确定使用第一推荐车辆时，为用户提供第一推荐车辆的位置信息。在一些实施例中，处理设备可以在向用户发送第二推荐车辆后或发送第二推荐车辆的同时，为用户提供第二推荐车辆的位置信息。
仅作为示例，处理设备可以获取用户的第三位置和推荐车辆的第二位置，根据用户的第三位置与推荐车辆的第二位置，为用户提供从所述第三位置到达所述第二位置的导航信息。例如，处理设备112可以在用户端130的地图界面，显示从所述第三位置到所述第二位置的导航路线。在一些实施例中，处理设备可以通过共享车辆的提醒装置为用户提供推荐车辆的位置信息。例如，处理设备的控制模块430可以控制推荐车辆的声音装置，向用户发出类似“用户昵称+我在这里啊”语音提示，或是直接响铃提示，以便用户可以更加轻松地定位到推荐车辆。在一些实施例中，处理设备可以当用户的第三位置与推荐车辆的第二位置之 间的距离小于第三预设距离值时，控制推荐车辆的提醒装置发出提醒信号。例如，控制模块430可以控制推荐车辆的闪光灯进行闪烁，并可以为用户的第三位置与推荐车辆的第二位置之间的距离越小，控制闪光灯进行闪烁的频率越高。
步骤770，当第二反馈信息指示用户未寻找到推荐车辆时，确定第四推荐车辆为更新后的推荐车辆。在一些实施例中，步骤770可以由第一确定模块420执行。
在一些实施例中，进一步地，处理设备可以按照预设时间间隔向用户发送询问用户是否找到推荐车辆的询问信息，并获取用户对于该询问信息的第二反馈信息。在一些实施例中，第一次向用户发送是否找到推荐车辆的询问信息的时间可以是根据推荐车辆的第二位置与用户的第三位置之间的距离，以及用户的平均步行速度，计算出来的用户到达推荐车辆停车处的时间。
对于后台系统来说，计算的推荐车辆的第二位置与用户的第三位置之间的距离可能是地图上显示的直线距离，与用户实际选择的路径可能会存在偏差，即用户找到推荐车辆的时间与用户的第一次询问时间可能存在偏差。如果用户找到推荐车辆的时间在系统发出是否找到推荐车辆的询问信息之前，即系统还没有发出询问信息，就收到了用户的骑行开始指令，这时，系统将不再向用户发送询问信息；如果用户找到车辆的时间在系统发出是否找到推荐车辆的询问信息之后，可以再次在预设时间间隔内(例如，20秒内、3分钟内、5分钟内等)向用户发送第二次询问信息，再次询问用户是否找到推荐车辆。
若获取的第二反馈信息指示用户没有找到推荐车辆，处理设备可以在所述多台共享车辆中，将所述第一推荐车辆或第二推荐车辆之外的第四推荐车辆，推荐给用户。仅作为示例，当推荐车辆为所述多台共享车辆中满足所述第一预设条件的共享车辆时，处理设备可以将所述多台共享车辆中，与用户的当前位置最近的候选车辆确定为供用户骑行第四推荐车辆；当推荐车辆为所述多台共享车辆中剩余续航里程值最大的共享车辆时，可以将所述多台共享车辆中除所述第一推荐车辆之外，剩余续航里程值最大的共享车辆，确定为供用户骑行的第四推 荐车辆。
在一些实施例中，处理设备可以将发送给用户的推荐车辆(例如，第一推荐车辆、或第二推荐车辆、或第四推荐车辆等)对应的车辆状态更改为预约状态；并可以当接收到用户发送的骑行开始指令时，控制对应的推荐车辆自动开锁。本实施例中，在确定推荐给用户的推荐车辆之后，将所述推荐车辆的状态更改为预约状态，在用户确定是否使用所述推荐车辆或开始使用所述推荐车辆之前，所述推荐车辆都不会再作为推荐车辆被推荐，在接收到用户发送的骑行开始指令时，控制所述推荐车辆自动开锁，用户开始本次骑行，可以减少用户通过扫描等方式请求开锁的过程，提高用户体验。
本实施例提供的共享车辆的信息推送方法，当检测到用户的用车服务请求时，获取检测到所述用车服务请求时所述用户所处的第一位置和检测到所述用车服务请求时的请求时间；基于获取到的所述用户的出行信息、所述用户所处的第一位置以及检测到所述用车服务请求时的请求时间，预测所述用户的出行目的地；检测在距离所述出行目的地预设还车距离范围内的车辆还车点与所述出行目的地之间的还车距离是否小于第一预设距离；若在距离所述出行目的地预设还车距离范围内的车辆还车点与所述出行目的地之间的还车距离小于第一预设距离，计算所述用户的第一位置与所述车辆还车点之间的行驶距离；基于所述多台共享车辆中每台车辆的剩余电量对应的剩余行驶距离与所述行驶距离之间的距离差值，确定出多台候选车辆，其中，每台候选车辆的剩余行驶距离与所述行驶距离之间的距离差值大于第二预设距离值；将所述多台候选车辆中，剩余行驶距离最小的候选车辆确定为供用户骑行的第一推荐车辆。
这样，在检测到用户的用车服务请求时，获取用户的第一位置以及用户的请求时间，并根据用户的出行信息，预测用户的出行目的地，检测预测出来的出行目的地之间的距离是否小于第一预设距离，如果小于第一预设距离，则确定用户第一位置与车辆还车点之间的行驶距离，并根据所述行驶距离以及用户第一位置周围的多台共享车辆中可供用户行驶到目的地并且距离用户最近的候选车 辆推荐给用户，可以将剩余电量较低的车辆调度回车辆还车点，及时给所述车辆换电瓶，有助于提高车辆调度的合理性以及车辆管理的便捷性。
应当注意的是，上述有关流程700的描述仅仅是为了示例和说明，而不限定本申请的适用范围。对于本领域技术人员来说，在本申请的指导下可以对流程700进行各种修正和改变。然而，这些修正和改变仍在本申请的范围之内。
图8是根据本申请另一些实施例所示的共享车辆的信息推送方法的示例性流程图。
在一些实施例中，流程800可以由处理设备(例如，图1所示的处理设备112)执行。例如，流程800可以以程序或指令的形式存储在存储设备(例如，存储器150或处理设备的存储单元)中，当处理器210或图4所示的模块执行程序或指令时，可以实现流程800。在一些实施例中，流程800可以利用以下未描述的一个或以上附加操作，和/或不通过以下所讨论的一个或以上操作完成。另外，如图8所示的操作的顺序并非限制性的。
如图8所示，本实施例中提供的共享车辆信息推送方法，可以根据用户输入的状态标签筛选出与该状态标签对应的一台或多台共享车辆，具体地流程800可以包括以下步骤。
步骤810，获取用户输入的共享车辆状态标签。在一些实施例中，步骤810可以由第一获取模块410执行。
通过对共享车辆发送给处理设备的状态数据，分别进行数据解码、数据解析、数据异构、结构化打标签、生成标签等一系列处理，最终得到的多个状态类型与共享车辆之间的关联关系即为共享车辆的状态标签。例如，共享车辆的状态标签可以包括但不限于“电量不足”、“电量充足”、“位于指定区域”、“超出指定区域”、“电压不足”、“电压充足”、“设备版本号一致”“设备版本号不一致”等，或其任意组合。
在一些实施例中，用户可以是共享车辆的使用者，使用者可通过客户端输入至少一个状态标签，获得与各状态标签对应的共享车辆。例如，使用者想要筛 选出距离自己所在的位置不超过50m，且电量充足的共享车辆，则可以输入内容为“电量充足”以及“位于指定区域”的状态标签。
在一些实施例中，用户也可以是运维人员。运维人员可通过运维端输入至少一个状态标签，获得与各状态标签对应的共享车辆。例如，运维人员想要筛选出存在需要维修的共享车辆，则可以输入内容为“电量不足”的状态标签，如此，可筛选出电量不足的共享车辆，便于运维人员对电量不足的共享车辆进行维修。
在一些实施例中，可以通过在终端设备提供筛选操作界面，响应用户在该筛选操作界面的筛选操作，获取用户输入的至少一个共享车辆的状态标签。
步骤820，根据所述状态标签，从各类型共享车辆中筛选出与所述状态标签对应的共享车辆为第三推荐车辆。在一些实施例中，步骤820可以由第一确定模块420执行。
在一些实施例中，处理设备可以根据用户输入的状态标签，基于后台数据库中存储的共享车辆的状态数据，从各类型共享车辆中筛选出与该状态标签对应的一台或多台共享车辆。在一些实施例中，所述各类型共享车辆可以为分别位于多个预设区域的共享车辆，所述各类型共享车辆可以为所述多个预设区域内的所有车辆，或部分车辆等。在一些实施例中，所述多个预设区域可以为根据不同省市的行政区域预先划分的多个区域。在一些实施例中，预设区域可以包括一个或多个指定的共享设备归还区域(如，预设还车区域)。
在一些实施例中，处理设备可以将筛选出的共享车辆作为第三推荐车辆，并推荐给用户。
步骤830，为用户提供从用户第三位置到达推荐车辆第二位置的导航信息。在一些实施例中，步骤830可以由传输模块450执行。
在一些实施例中，处理设备在根据用户输入的状态标签，从各类型共享车辆中筛选出与该状态标签对应的共享车辆之后，还可以获取所述用户当前的第三位置以及筛选出的共享车辆的第二位置，并根据所述第三位置与所述第二位置为所述用户提供从所述第三位置到达所述第二位置的导航信息。例如，运维人 员筛选出电量不足的共享车辆后，处理设备还可获得从运维人员的当前位置到筛选出的共享车辆的位置的导航信息，运维人员可根据导航信息寻找到筛选出的共享车辆，提高了工作效率。又例如，共享车辆的使用者筛选出满意的共享车辆后，处理设备还可获得从使用者的当前位置到筛选出的共享车辆的位置的导航信息，使用者可根据导航信息快速寻找到筛选出的共享车辆，提高了用户体验。
更进一步地，本申请实施例中各所述共享车辆可以配置有提醒装置，处理设备可以计算所述第三位置与所述第二位置之间的距离，若所述距离小于第三预设距离，则控制所述提醒装置发出提醒信号。其中，第三预设距离可以是2m、3m、4m或5m等。例如，运维人员在根据导航信息寻找筛选出的共享车辆的过程中，与筛选出的共享车辆的距离小于第三预设距离阈值时，筛选出的共享车辆上的提醒装置将开始发出提醒信号，以提醒运维人员注意到筛选出的共享车辆，有效的缩短了运维人员寻找筛选出的共享车辆的时间，进一步地提高了工作效率。
作为一种可选的实施方式，所述提醒装置可以为闪光灯，控制闪光灯发出提醒信号的步骤可以包括：控制所述闪光灯进行闪烁，其中，所述第三位置与所述第二位置之间的距离越小，控制所述闪光灯进行闪烁的频率越高。
作为另一种可选的实施方式，所述提醒装置可以为蜂鸣器或语音模块，控制蜂鸣器或语音模块发出提醒信号的步骤可以包括：控制所述蜂鸣器或语音模块进行发声，其中，所述第三位置与所述第二位置之间的距离越小，控制所述蜂鸣器或语音模块进行发声的时间间隔越短。
可以理解的是，上述提醒装置还可以是其他装置，只要可以起到提醒用户的作用且提醒效果与所述第三位置和所述第二位置之间的距离相关即可，在此不做限制。
在一些实施例中，当用户为共享车辆的使用者时，处理设备还可以按照预设时间间隔向用户发送询问用户是否找到第三推荐车辆的询问信息，并获取用户对于该询问信息的第二反馈信息。若所述第二反馈信息指示用户未寻找到所 述第三推荐车辆，则确定第四推荐车辆为更新后的推荐车辆，并推荐给所述用户。在一些实施例中，处理设备还可以将所述第三推荐车辆或第四推荐车辆对应的车辆状态更改为预约状态；并当接收到用户发送的骑行开始指令时，控制所述第三或第四推荐车辆自动开锁。
应当注意的是，上述有关流程800的描述仅仅是为了示例和说明，而不限定本申请的适用范围。对于本领域技术人员来说，在本申请的指导下可以对流程800进行各种修正和改变。然而，这些修正和改变仍在本申请的范围之内。
图9是根据本申请再一些实施例所示的共享车辆的信息推送方法的示例性流程图。
在一些实施例中，流程900可以由处理设备(例如，图1所示的处理设备112)执行。例如，流程900可以以程序或指令的形式存储在存储设备(例如，存储器150或处理设备的存储单元)中，当处理器210或图4所示的模块执行程序或指令时，可以实现流程900。在一些实施例中，流程900可以利用以下未描述的一个或以上附加操作，和/或不通过以下所讨论的一个或以上操作完成。另外，如图9所示的操作的顺序并非限制性的。
如图9所示，在一些实施例中，在流程900中可以基于筛选出的各预设区域中与用户输入的状态标签对应的共享车辆，确定需要进行功能升级的目标区域，进而在不影响其他预设区域的共享车辆的使用的情况下，对目标区域的筛选出的共享车辆进行功能升级，以实现对所有共享车辆的统一管理，降低管理成本。在一些实施例中，流程900可包括以下步骤。
步骤910，统计各预设区域中包括的筛选出的共享车辆的数量。在一些实施例中，步骤910可以由统计单元442执行。
在一些实施例中，预先划分的多个区域(即预设区域)可以根据不同省市的行政区域划分得到。例如，针对北京市内，预先划分的多个区域可以是北京市内的朝阳区、海淀区、西城区、顺义区及房山区等。针对成都市内，预先划分的多个区域可以是成都市内的武侯区、高新区、青羊区以及锦江区等。在一些实施 例中，预先划分的多个区域还可以根据地理区域划分得到，例如，预先划分的多个区域可以是华北区、东北区、华东区、西南区以及西北区等。
在一些实施例中，处理设备可以基于共享车辆的位置信息，统计获得各预设区域中包括的筛选出的共享车辆的数量。在一些实施例中，处理设备可以基于预设区域的共享车辆的使用情况信息，统计获得各预设区域中包括的筛选出的共享车辆的数量。
步骤920，根据各预设区域中包括的筛选出的共享车辆的数量，确定需要进行功能升级的目标区域。在一些实施例中，步骤920可以由分析单元444执行。
在一些实施例中，处理设备可以通过比较不同预设区域中包括的筛选出的共享车辆的数量的大小，确定筛选出的共享车辆的数量的最多的区域为需要进行功能升级的目标区域。以预先划分的多个区域是北京市内的朝阳区、海淀区、西城区、顺义区及房山区为例，假设统计得到筛选出的共享车辆的数量在朝阳区内为1000辆，在海淀区内为4000辆，在西城区内为300辆，在顺义区内为2000辆，在房山区为3200辆。比较可知，海淀区内筛选出的共享车辆的数量最多，则可以确定需要进行功能升级的目标区域为海淀区。
在一些实施例中，处理设备可以从包括所述筛选出的共享车辆的各预设区域中选取参考区域，计算包括所述筛选出的共享车辆的各预设区域中除所述参考区域之外的其他每个预设区域中筛选出的共享车辆的数量与所述参考区域中筛选出的共享车辆的数量的数据差值；根据所述数据差值确定需要进行功能升级的目标区域。
同样以预先划分的多个区域是北京市内的朝阳区、海淀区、西城区、顺义区及房山区为例，假设统计得到筛选出的共享车辆的数量在朝阳区内为1000辆，在海淀区内为4000辆，在西城区内为300辆，在顺义区内为2000辆，在房山区为3200辆。从各区域中选取朝阳区为参考区域，则海淀区中筛选出的共享车辆的数量与朝阳区中筛选出的共享车辆的数量的差值为3000，西城区中筛选出 的共享车辆的数量与朝阳区中筛选出的共享车辆的数量的差值为700，顺义区中筛选出的共享车辆的数量与朝阳区中筛选出的共享车辆的数量的差值为1000，房山区中筛选出的共享车辆的数量与朝阳区中筛选出的共享车辆的数据的差值为1200。则可以确定需要进行功能升级的目标区域为海淀区域。
作为又一种实施方式，处理设备可以通过比较不同预设区域中包括的筛选出的共享车辆的数量与预设数量的大小，确定筛选出的共享车辆的数量大于预设数量的区域为需要进行功能升级的目标区域。
同样以预先划分的多个区域是北京市内的朝阳区、海淀区、西城区、顺义区及房山区为例，假设统计得到筛选出的共享车辆的数量在朝阳区内为1000辆，在海淀区内为4000辆，在西城区内为300辆，在顺义区内为2000辆，在房山区为3200辆。假设，预设数量为1500，比较可知，每个区域中筛选出的共享车辆的数量大于预设数量的区域有海淀区、顺义区以及房山区。则可以确定需要进行功能升级的目标区域为海淀区、顺义区以及房山区。
步骤930，获取筛选出的共享车辆的状态标签对应的预设升级规则。在一些实施例中，步骤930可以由第一获取模块410执行。
在一些实施例中，处理设备可以基于状态标签与预设升级规则的映射关系，获取筛选出的共享车辆的状态标签的预设升级规则。可以理解的是，不同的状态标签对应的预设升级规则不同。例如，状态标签为“设备版本号不一致”，则其对应的预设升级规则可以为：先将该状态标签所对应的共享车辆的设备版本回滚至预存的设备版本，再对该状态标签所对应的共享车辆进行下一个设备版本的升级。又例如，状态标签为“设备版本号一致”，则其对应的预设升级规则可以为：直接对该状态标签所对应的共享车辆进行下一个设备版本的升级。如此，可便于对所有的共享车辆进行统一管理，降低管理成本。
在一些实施例中，状态标签与预设升级规则之间的映射关系，可以根据实际场景合理调整，本说明书对此不做限制。
步骤940，按照所述预设升级规则对位于所述目标区域的筛选出的共享车 辆进行功能升级。在一些实施例中，步骤940可以由控制模块430执行。
在一些实施例中，可选择在预设时间段对目标区域的筛选出的共享车辆进行功能升级。例如，预设时间段可以是在夜晚的1点至凌晨的5点钟，以避开用户需要使用共享车辆的时间，避免因功能升级造成共享车辆不能被使用，进而提高共享车辆的可使用率。
在一些实施例中，可以通过人为的方式对位于目标区域的筛选出的共享车辆进行功能升级。例如，若目标区域内的筛选出的共享车辆的状态数据表明该目标区域内的共享车辆的胎压常常处于较低的水平，可以推测该目标区域内的路面状况较差。此种情况下，可针对投放于此目标区域内的共享车辆的轮胎进行升级，例如，使用更加耐磨的轮胎。如此，可精准的对不同区域的共享车辆进行不同的升级，进而在控制成本的情况下，使得目标区域内的共享车辆的使用寿命更长。
又例如，若目标区域内的筛选出的共享车辆的状态数据表明该目标区域内的共享车辆的太阳能板的太阳能转化率较低，可以推断该目标区域内的日照可能不充足，无法满足共享车辆的正常工作电量。此种情况下，可以对投放于此目标区域内的共享车辆的太阳能板进行升级，例如，给共享车辆配置太阳能转化率更高的太阳能板；或者使用发电装置替换该目标区域内的共享车辆的太阳能板，将共享车辆的使用者在骑行过程中产生的机械能转换为电能，以为共享车辆提供充足的电量。
进一步地，为了使得共享车辆的使用寿命更长久，降低对共享车辆进行升级或维修的频率，本申请实施例中，还可向筛选出的每个共享车辆分别发送控制指令，以禁止筛选出的共享车辆向服务器发送与该共享车辆对应的状态数据。例如，对于新投放的共享车辆，可以禁止其在预设的时间段内向服务器发送状态数据。又例如，对于状态标签为“电量充足”的共享车辆，可以禁止该共享车辆在预设时间段内向服务器发送电量对应的状态数据。再例如，对于状态标签为“电压充足”的共享车辆，则可以禁止该共享车辆在预设时间段内向服务器发送电压 对应的状态数据，以达到减小共享车辆的功耗的目的，使得共享车辆的使用寿命更长久，降低对共享车辆进行升级或维修的频率，从而降低了共享车辆的运营与管理成本。
应当注意的是，上述有关流程900的描述仅仅是为了示例和说明，而不限定本申请的适用范围。对于本领域技术人员来说，在本申请的指导下可以对流程900进行各种修正和改变。然而，这些修正和改变仍在本申请的范围之内。
图10是根据本申请一些实施例所示的共享车辆状态标签确定方法的示例性流程图。
如图10所示，本实施例中提供的共享车辆状态标签确定方法，可以通过获取共享车辆发送的状态数据，根据预设评估策略对状态数据进行分析，得到与发送该状态数据的共享车辆对应的状态标签，使得用户可根据状态标签筛选出对应的共享车辆，从而基于状态标签对各共享车辆进行便捷分析，简化了共享车辆的运营与管理流程，有效降低了成本。下面通过可能的实现方式对本实施例的技术方案进行详细阐述。
在一些实施例中，流程1000可以由处理设备(例如，图1所示的处理设备112)执行。例如，流程1000可以以程序或指令的形式存储在存储设备(例如，存储器150或处理设备的存储单元)中，当处理器210或图4所示的模块执行程序或指令时，可以实现流程1000。在一些实施例中，流程1000可以利用以下未描述的一个或以上附加操作，和/或不通过以下所讨论的一个或以上操作完成。另外，如图10所示的操作的顺序并非限制性的。如图10所示，流程1000可以包括以下步骤。
步骤1010，获取至少一个共享车辆发送的至少一个状态数据。在一些实施例中，步骤1010可以由第一获取模块410或分析模块440执行。
状态数据可以用于反映共享车辆的电池、电压、电量、胎压等车辆属性的当前状态。在一些实施例中，共享车辆的状态数据可以包括但不限于共享车辆的电量数据、电压数据、设备标识号信息、经纬度信息、胎压信息、设备版本号信 息等，或其任意组合。在一些实施例中，处理设备可以通过网络(例如，网络120)获取共享车辆发送的状态数据。在一些实施例中，处理设备可以同时接收多台共享车辆发送的一个或多个状态数据。在一些实施例中，处理设备可以分别接收多台共享车辆发送的一个或多个状态数据。
步骤1020，针对每个共享车辆发送的每个状态数据，获取该状态数据所属的状态类型，并获取该状态类型对应的预设评估策略。在一些实施例中，步骤1020可以由分析模块440执行。
状态类型即状态数据的所属类型。可以理解的是，每个共享车辆发送的状态数据可以为一个或多个，对应的，每个共享车辆发送的状态数据所属的状态类型也可以为一个或多个。每个共享车辆发送的状态数据所属的状态类型可以为多种。例如，状态类型可以包括电量、电压、设备标识号、经纬度、胎压、设备版本号等；对应地，状态数据可以为电量数据、电压数据、设备标识号信息、经纬度信息、胎压信息、设备版本号信息等。
本实施例中，预设评估策略是指可以用于确定状态标签类型的策略。例如，若状态类型为电量，其对应的预设评估策略可以为：若共享车辆的电量低于15％，则得到“电量不足”的状态标签，反之，则得到“电量充足”的状态标签。
在一些实施例中，所述预设评估策略可以通过在终端设备提供策略配置界面，响应用户在所述策略配置界面的配置操作获得。在一些实施例中，策略配置界面可以是网页或应用软件的交互界面，用户可在该策略配置界面进行配置操作，以设定预设评估策略。例如，用户可以在终端设备的策略配置界面中手动输入预设评估策略。在一些实施例中，所述预设评估策略可以根据实际应用场景进行调整，本说明书对此不做限制。
步骤1030，针对每个共享车辆发送的属于每种状态类型的状态数据，采用与所述状态类型对应的预设评估策略进行分析，得到与发送属于所述状态类型的状态数据的共享车辆对应的状态标签。在一些实施例中，步骤1030可以由分析模块440执行。
在一些实施例中，处理设备可以针对每个共享车辆发送的每个状态数据分别进行分析。例如，状态类型为电压，其对应的预设评估策略可以为：若共享车辆的电压低于3V，则得到“电压不足”的状态标签，反之，则得到“电压充足”的状态标签。又例如，状态类型为经纬度，其对应的预设评估策略可以为：根据共享车辆的经纬度，确定共享车辆是否在指定区域，若共享车辆不在指定区域，则得到“超出指定区域”的状态标签，反之，则得到“位于指定区域”的状态标签。再例如，状态类型为设备版本号，其对应的预设评估策略可以为：比较共享车辆的设备版本号与预存的该共享车辆的设备版本号是否一致，若一致，则得到“设备版本号一致”的状态标签，若不一致，则得到“设备版本号不一致”的状态标签。
在一些实施例中，处理设备可以针对每个共享车辆的发送的历史状态数据进行分析。例如，可以获取共享车辆每间隔预设时间发送的状态数据，根据不同状态类型对应的预设评估策略对同一状态类型的状态数据进行分析预测，获得该共享车辆的状态预测结果。其中，预设时间可以为一周、两周、三周、一个月、两个月等等。例如，共享车辆F每间隔一周时间向服务器110发送状态类型为电量的状态数据，第一次发送的状态数据表明共享车辆F的电量为90％，第二次发送的状态数据表明共享车辆F的电量为87％，第三次发送的状态数据表明共享车辆F的电量为83％，第四次发送的状态数据表明共享车辆F的电量为80％，则可以预测共享车辆F在21周后，其电量可能低于15％。在一些实施例中，可根据对共享车辆状态数据的预测结果，提前对共享车辆进行维修处理，以提高共享车辆的使用寿命。
可以理解的是，若共享车辆发送的多个状态数据属于多种状态类型，利用与各状态类型对应的预设评估策略对每个所述共享车辆发送的属于每种状态类型的状态数据进行分析后，得到的该共享车辆状态标签也为多个。例如，若共享车辆A的电量为10％，根据电量对应的预设评估策略可获得“电量不足”的状态标签；若共享车辆A的电压为2V，根据电压对应的预设评估策略可获得“电 压不足”的状态标签；如此，根据共享车辆A发送的“电量为10％”和“电压为2V”两个状态数据，可以分析得到的状态标签为两个，分别为“电量不足”和“电压不足”。
可以理解的是，上述具体数值均为阐述说明所作出的举例，在实际使用中，上述预设评估策略还可以是其他评估规则，上述举例中的具体数值还可以是其他数值。
在一些实施例中，在得到与发送属于该状态类型的状态数据的共享车辆对应的状态标签之后，还可以将得到的状态标签与共享车辆发送的状态数据共同存储于数据库(例如，存储器150)中，便于使用时调取共享车辆的状态数据，例如，可以用于基于用户输入的状态标签筛选对应的共享车辆。
本实施例中，通过获取共享车辆发送的状态数据，根据预设评估策略对状态数据进行分析，得到与发送该状态数据的共享车辆对应的状态标签，从而简化了共享车辆的运营与管理流程，有效降低了成本。具体可结合本说明书图8-9及其相关描述，此处不再赘述。
应当注意的是，上述有关流程1000的描述仅仅是为了示例和说明，而不限定本申请的适用范围。对于本领域技术人员来说，在本申请的指导下可以对流程1000进行各种修正和改变。例如，根据不同应用场景下的状态标签，可以组合使用，同时还可以根据多场景标签规划属性数据大盘，便于更直观的查看多维度属性数据趋势。然而，这些修正和改变仍在本申请的范围之内。
图11是根据本申请再一些实施例所示的共享车辆的信息推送方法的示例性流程图。
本实施中提供的共享车辆信息推送方法，可以根据获取的某一时刻预设区域内共享车辆的使用情况，对上一时刻该预设区域内共享车辆的使用情况进行更新，并将更新后的车辆使用情况展示给用户，从而使得用户可以获知预设区域对应的预设还车区域中可以使用的关系车辆数量，也就是说，可以给该用户提供准确度较高的车辆停放地点，使得用户可以根据需求去到有可使用车辆的预 设区域找到可使用的共享车辆。
在一些实施例中，流程1100可以由处理设备(例如，图1所示的处理设备112)执行。例如，流程1100可以以程序或指令的形式存储在存储设备(例如，存储器150或处理设备的存储单元)中，当处理器210或图4所示的模块执行程序或指令时，可以实现流程1100。在一些实施例中，流程1100可以利用以下未描述的一个或以上附加操作，和/或不通过以下所讨论的一个或以上操作完成。另外，如图11所示的操作的顺序并非限制性的。如图11所示，流程1100可以包括以下步骤。
步骤1110，获取第一时刻的多个预设区域内的共享车辆使用情况。在一些实施例中，步骤1110可以由第一获取模块410执行。
在一些实施例中，预设区域可以为工作人员划定的一个地理区域。共享车辆使用者在使用完共享车辆后可以将该共享车辆停放在所述划定的地理区域中，运维人员可以将共享车辆投放在所述划定的预设区域中。在一些实施例中，预设区域可以为处理设备根据共享车辆停放情况、各地区的人流量、使用车辆的情况和交通管控等数据计算得到的一个地理区域。同样的，共享车辆使用者在使用完共享车辆后可以将该共享车辆停放在上述计算得到的地理区域中，运维人员可以将共享车辆投放在上述计算得到的地理区域中。在一些实施例中，预设区域可以是运维人员在投放共享车辆的过程中划定的一个地理区域，共享车辆使用者在使用完共享车辆后可以将该共享车辆停放在上述划定的地理区域中。
在一些实施例中，当预设区域为由运维人员在投放共享车辆的过程中划定的地理区域时，处理设备可以在获取共享车辆使用情况之前，接收运维人员通过运维端发送的预设区域的范围。
仅作为示例，运维人员在投放共享车辆的过程中，发现某一处没有停放共享车辆且该处可能有一定数量的人群需要使用共享车辆时，该运维人员可以将自己运输的共享车辆全部或部分投放在该处，并通过自己的运维端向服务器上传该处的地理信息作为新的预设区域，以使服务器可以在数据库中添加该预设 区域并对该预设区域中的共享车辆使用情况进行更新。需要说明的是，该示例仅为本申请实施例提供的一个实例，可以理解，运维人员在投放共享车辆的过程中划定的一个地理区域的过程还可能存在其他的情况，本领域技术人员可以根据实际情况进行合适的调整。
因此，预设区域的范围可以是运维人员根据其所投放的共享车辆的位置进行划分得到，从而使得用户可以获知预设区域对应的共享车辆存放点中可以使用的共享车辆数量，使得用户可以根据需求去到有可使用共享车辆的预设区域找到可使用的共享车辆。
第一时刻可以表示最新采集车辆使用情况的时刻。为方便理解，本实施例中，第一时刻对应的共享车辆使用情况可以表示为第一车辆使用情况，相应地，第二时刻对应的共享车辆使用情况可以表示为第二车辆使用情况。其中，第一车辆使用情况相对于第二车辆使用情况而言，为更新后的车辆使用情况。
在一些实施例中，共享车辆使用情况可以包括共享车辆的数量。在一些实施例中，共享车辆使用情况可以包括共享车辆的故障情况。在一些实施例中，共享车辆使用情况也可以同时包括共享车辆的数量以及共享车辆的故障情况。例如，第一车辆使用情况和第二车辆使用情况可以均至少包括车辆数量和车辆故障情况。
在一些实施例中，共享车辆的数量可以为多个预设区域内共享车辆的总数量，和/或所述多个预设区域内不同类型的共享车辆分别的数量等。在一些实施例中，本领域技术人员可以根据实际情况对共享车辆数量的数据类型进行合适的调整，本申请实施例中对此不作具体的限定。仅作为示例，处理设备可以获取第一时刻某预设区域内共享车辆的总数量为20，其中，第一类型的车辆数量为8、第二类型的车辆数量为10、第三类型的车辆数量为2。需要说明的是，车辆的类型可以表示自行车、电动车、汽车等不同功能的车辆，还可以表示不同的自行车商家等，本申请实施例中对此同样不作具体的限定。例如，上述示例中的第一类型可以表示自行车、第二类型可以表示电动车、第三类型可以表示汽车。
在一些实施例中，处理设备可以通过运维人员通过运维端上传的数据获取预设区域的共享车辆数量。运维人员可以在大街小巷中寻找散落的共享车辆，然后统一运输到一个预设区域中，其中，预设区域的确定方式已经在上述实施例中进行了详细的介绍，此处不再赘述。因此，预设区域内共享车辆数量的改变可能是运维人员在该预设区域内投放了一定数量的共享车辆，所以可以根据运维人员投放的共享车辆数量对该预设区域内的共享车辆数量进行实时更新，从而保证该预设区域内可使用共享车辆的数量的准确度高。
在一些实施例中，运维人员可以在预设区域投放完所有的共享车辆后，在运维端输入投放至该预设区域的共享车辆总数，作为该预设区域新增的共享车辆数量，此时，处理设备可以接收运维端发送的投放到预设区域的共享车辆数量。由于运维人员仅仅需要在最后输入一个数值，因此该方式简便快捷。
作为另一种实施方式，运维人员可以在预设区域内投放每一辆共享车辆时，均使用运维端记录一次投放操作，对应的，该预设区域内的共享车辆数量在运维人员每次投放动作完成后加一。例如，运维人员可以使用运维端扫描共享车辆上的二维码、条形码等；或者，运维人员可以手动在运维端上输入投放了一辆共享车辆等。由于运维人员需要在投放每一辆共享车辆时均进行扫码操作，因此可以避免遗漏投放的共享车辆数量，从而使得投放的共享车辆数量不容易出现错误。
在一些实施例中，运维人员除了可以在投放过程或者投放完成后对预设区域内的共享车辆数量进行更新，也可以对各个预设区域内的共享车辆进行日常巡检，统计各个预设区域内共享车辆的数量，并将统计的共享车辆数量上传至服务器，以对共享车辆的使用情况进行校正，从而提高预设区域内共享车辆的使用情况的准确度。
在一些实施例中，处理设备可以通过共享车辆使用者通过客户端上传的数据获取预设区域的共享车辆数量。预设区域内共享车辆数量的改变可能是用户使用了其中的共享车辆，所以可以根据用户使用的共享车辆数量对该预设区 域内的共享车辆数量进行实时更新，从而保证该预设区域内可使用共享车辆的数量的准确度高。
在一些实施例中，共享车辆的故障情况可以为多个预设区域内出现故障或者没有故障的共享车辆数量，也可以为出现故障的具体为哪一辆车等。在一些实施例中，本领域技术人员可以根据实际情况对共享车辆故障情况的数据类型进行合适的调整，本申请实施例中对此不作具体的限定。仅作为示例，处理设备可以获取第一时刻第一预设区域内总共有3辆车出现故障，有12辆车没有故障；或者处理设备可以获取该第一预设区域内编号为56395782的车辆出现了故障。
运维人员在对共享车辆进行投放时，可以同时检查投放的共享车辆以及预设区域本已停放的共享车辆是否可以使用(即是否出现故障)。如果运维人员发现某一共享车辆不可使用，则可以通过运维端上传该共享车辆的车辆标识信息。例如，运维人员可以使用运维端扫描共享车辆上的二维码、条形码等；或者，运维人员可以手动在运维端上输入该共享车辆的信息等。其中，车辆标识信息可以用于标记预设区域内的共享车辆故障或者没有故障。
此外，运维人员除了可以在投放的过程中对共享车辆进行检查，也可以对各个预设区域内的共享车辆进行日常巡检，检查各个预设区域内共享车辆的故障情况，并将检查情况上传至服务器，以对各预设区域内的共享车辆的使用情况进行校正，从而提高预设区域内共享车辆的使用情况的准确度。
因此，运维人员在投放共享车辆或者在巡逻时，可以将故障的共享车辆的车辆信息进行标识，以使处理设备可以对预设区域内可使用共享车辆的数量进行实时的更新。
在一些实施例中，共享车辆使用者在用车或还车过程中，可以通过客户端输入对共享车辆故障情况的反馈。例如，用户在准备使用某一共享车辆时，发现该共享车辆链条、和/或车把、和/或座椅、和/或轮胎、和/或锁具等车辆组件存在故障，影响骑行，则可以通过在共享车辆APP反馈界面输入对该共享车辆的反馈信息，以将共享车辆的情况上传至服务器，以对各预设区域内的共享车辆的使 用情况进行校正。在一些实施例中，服务器可以将共享车辆使用者反馈的存在故障的共享车辆的位置信息和/或标识信息发送给运维端，以便运维人员对该故障共享车辆进行验证或维修。
步骤1120，根据所述第一时刻的共享车辆使用情况对第二时刻存储的所述预设区域内的共享车辆使用情况进行更新。在一些实施例中，步骤1120可以由第一确定模块420执行。
在一些实施例中，处理设备在获取某一时刻的共享车辆使用情况后，可以将其存储至数据库中，当获取最新时刻的共享车辆使用情况后，可以使用该更新后的共享车辆使用情况对存储的共享车辆使用情况进行更新。其中，所述第二时刻可以表示上一次采集共享车辆使用情况的时刻。可以理解，采用第一时刻以及第二时刻的描述方式只是为了表征这两个时刻的先后顺序，即第一时刻为晚于第二时刻的某个时刻。例如，当采用周期方式采集共享车辆使用情况时，第一时刻可以表示采集共享车辆使用情况的最新时刻，而第二时刻表示上一个周期采集共享车辆使用情况的对应时刻。
因此，可以根据获取的某一时刻(即第一时刻)预设区域内共享车辆的使用情况，对存储的上一时刻(即第二时刻)该预设区域内共享车辆使用情况进行更新，并将更新后的共享车辆使用情况展示给使用客户端的用户，从而使得用户可以获知预设区域对应的共享车辆存放点中可以使用的共享车辆及其数量。
在一些实施例中，处理设备可以周期性的获取某一时刻预设区域内的共享车辆使用情况，也可以实时获取某一时刻预设区域内的共享车辆使用情况，本申请实施例中对此不作具体的限定。仅作为示例，若处理设备周期性的获取共享车辆使用情况，假设获取的周期为一小时，第一时刻为每天早上十点，则第二时刻可以为每天早上九点；若处理设备实时获取共享车辆使用情况，那么一旦该预设区域内共享车辆的使用情况发生了变化，处理设备将获取一次共享车辆的使用情况，假设第一时刻为早上十点五十分，则第二时刻可以为早上十点十分。
在一些实施例中，处理设备可以当接收到运维端发送的在预设区域内的 其中一共享车辆的第一扫码信息(即运维人员扫描共享车辆上二维码的信息)时，将该预设区域的当前的共享车辆数量加一，以对该预设区域的共享车辆数量进行更新。
在一些实施例中，处理设备可以当接收到客户端发送的在预设区域内的某一共享车辆的第二扫码信息(即使用者扫描共享车辆上二维码的信息)时，将该预设区域的当前的共享车辆数量减一，以对该预设区域内的共享车辆数量进行更新。具体的，该种情况即用户在预设区域使用了共享车辆(例如，通过扫描共享车辆上二维码使用)后，服务器对应的接收到使用者通过客户端对该预设区域内的某一车辆进行扫码后生成的第二扫码信息，确定该预设区域内的共享车辆数量减少了一辆，因此，服务器将该预设区域内当前的共享车辆数量减一，以对该预设区域内共享车辆数量进行更新。
同理，服务器在接收到客户端发送的在预设区域内对某一共享车辆的停放信息(例如，接收到使用者点击客户端上“还车”按钮的操作指令)时，说明该使用者在使用完一辆共享车辆后，将该共享车辆停放在了某一预设区域，此时，服务器可以将该预设区域内当前的共享车辆数量减一，以对该预设区域内共享车辆数量进行更新。
需要说明的是，本申请实施例中的第一扫码信息以及第二扫码信息的描述方式是为了区别不同运维端生成的扫码信息或者客户端生成的扫码信息。
在一些实施例中，处理设备可以在接收到运维端发送的车辆标识信息之后，在对应预设区域的可使用车辆数量上减一，或者直接标识出对应预设区域内出现故障的具体车辆，以对各预设区域内可用共享车辆的数量进行更新。本申请实施例中对共享车辆使用情况的更新方式不作具体的限定，本领域技术人员可以根据实际情况进行合适的调整。
步骤1130，基于更新结果，确定携带共享车辆使用情况的展示信息。在一些实施例中，步骤1130可以由第一确定模块420执行。
在一些实施例中，处理设备在获取到第一时刻的第一车辆使用情况，并且 利用第一车辆使用情况对存储的第二时刻的第二车辆使用情况进行更新之后，可以生成携带共享车辆使用情况的展示对象(即展示信息)。进一步地，处理设备可以响应于用户对终端设备的操作指令，向该终端设备提供上述展示对象。即，当共享车辆使用者想要通过客户端获取各个预设区域内的共享车辆使用情况时，处理设备可以通过该客户端输出对应的共享车辆使用情况。
在一些实施例中，所述展示对象可以为一张地图，该地图上可以显示有多个预设区域，以及每一预设区域内共享车辆的使用情况。例如，可以在地图上用红色表示共享车辆正在被使用，绿色表示共享车辆空闲，黄色表示共享车辆故障；或者直接在每一预设区域对应位置通过文字显示该预设区域的共享车辆使用情况。在一些实施例中，展示对象可以为一个列表，该列表可以对各个预设区域以距离进行排序，并对应显示每个预设区域对应的共享车辆使用情况等。在一些实施例中，展示对象的输出方式可以为任意合理的形式。例如，在共享车辆使用者的客户端的屏幕上进行显示，显示方式可以包括文字、图像、视频等，或其任意组合。又例如，可以通过共享车辆使用者的客户端语音输出，播报各个预设区域内的共享车辆使用情况等，优选地，此方式可以主要针对老年人、正在使用共享车辆的用户等不方便通过文字形式观看展示信息的人群。在一些实施例中，对于正在使用共享车辆的用户，还可以将展示信息发送至共享车辆，通过共享车辆的显示装置或语音装置输出给用户。
本实施例中，可以根据获取的某一时刻预设区域内共享车辆的使用情况，对上一时刻该预设区域内共享车辆的使用情况进行更新，并将更新后的共享车辆使用情况展示给使用终端设备的用户，从而使得用户可以获知预设区域对应的车辆存放点中可以使用的共享车辆数量，也就是说，可以给该用户提供准确度较高的车辆停放地点，使得用户可以根据需求去到有可使用共享车辆的预设区域找到可使用的共享车辆。
应当注意的是，上述有关流程1100的描述仅仅是为了示例和说明，而不限定本申请的适用范围。对于本领域技术人员来说，在本申请的指导下可以对流 程1100进行各种修正和改变。然而，这些修正和改变仍在本申请的范围之内。
图12是根据本申请再一些实施例所示的共享车辆的信息推送方法的示例性流程图。
如图12所示，与上述服务器响应用户对终端设备的操作指令，提供展示信息相对应，本申请实施例还提供一种应用于终端设备(例如，图1所示的用户端130)的共享车辆信息推送方法。即，流程1200可以由终端设备执行。例如，流程1200可以以程序或指令的形式存储在存储设备(例如，存储单元390)中，当中央处理器340或图5所示的模块执行程序或指令时，可以实现流程1200。在一些实施例中，流程1200可以利用以下未描述的一个或以上附加操作，和/或不通过以下所讨论的一个或以上操作完成。另外，如图12所示的操作的顺序并非限制性的。如图12所示，流程1200可以包括以下步骤。
步骤1210，接收用户对终端设备的操作指令。在一些实施例中，步骤1210可以由接收模块510执行。
在一些实施例中，操作指令可以包括但不限于用户打开终端设备的共享车辆APP，或者打开APP后点击其中的按钮、页面或链接等，或在浏览器或其他页面中输入搜索指令等。通过操作指令，终端设备可以确定用户的需求。例如，通过获取用户打开用户端130的共享车辆APP中的显示页面的操作指令，可以确定该用户可能需要获取周围共享车辆使用情况；或者通过获取用户在用户端130点击“开锁”按钮的操作指令，可以确定该用户需要使用对应共享车辆。在一些实施例中，操作指令的形式可以包括语音、文本、面部动作(例如，眨眼)、手势、触屏操作等，或其任意组合。
在一些实施例中，终端设备接收用户的操作指令后，可以将该操作指令或与该操作指令对应的服务请求传输至后台服务器(例如，服务器110)。例如，用户端130可以基于用户的操作指令生成相应的服务请求，并将其发送至服务器110，服务器110中处理设备112可以基于该服务请求进行相关的分析和处理。
步骤1220，获取与操作指令相关的特征信息。在一些实施例中，步骤1220可以由第二获取模块520执行。
在一些实施例中，操作指令相关的特征信息可以包括但不限于操作指令的发起时间、用户执行操作指令时的第一位置、用户的出行信息、用户的订单信息、用户输入的共享车辆状态标签、用户输入的目的地等，或其任意组合。在一些实施例中，终端设备可以从其内置数据库(例如，存储单元390)中获取与操作指令相关的特征信息。在一些实施例中，终端设备可以从服务器获取操作指令相关的特征信息。例如，用户端130可以基于触发操作指令的用户的ID信息，从服务器110获取与该用户相关的用户历史出行信息、历史服务请求订单等为与该操作指令相关的特征信息。
步骤1230，至少基于所述特征信息确定展示信息，所述展示信息包括共享车辆的车辆推荐信息和/或使用情况信息。在一些实施例中，步骤1230可以由第二确定模块530执行。
在一些实施例中，展示信息可以包括共享车辆的车辆推荐信息、和/或使用情况信息、和/或车辆的状态信息。例如，共享车辆推荐信息可以包括推荐车辆、推荐车辆的位置信息、推荐车辆的续航里程信息等；共享车辆使用情况信息可以包括附近可用共享车辆数量、车辆是否有故障等；车辆的状态信息可以包括车龄、型号、颜色、寿命、耗油/耗电量等。
在一些实施例中，终端设备可以基于用户执行操作指令时的第一位置、操作指令的发起时间、用户出行信息、用户输入目的地、用户输入的共享车辆状态标签等中的至少一种，确定推荐车辆。在一些实施例中，终端设备可以基于特征信息确定共享车辆使用情况信息。
在一些实施例中，终端设备可以从服务器获取所述展示信息。例如，用户端130可以基于操作指令对应的用户账户信息，或操作指令对应的服务请求编号，从服务器110获取对应的展示信息。又例如，用户端130可以将与所述操作指令相关的特征信息发送给服务器110，并获取由服务器110通过分析处理等确 定的展示信息。
步骤1240，在终端设备页面上显示所述展示信息。在一些实施例中，步骤1240可以由显示模块540执行。
在一些实施例中，终端设备可以将从服务器获取的展示信息输出显示给用户。在一些实施例中，终端设备可以在确定展示信息后，通过显示装置将其输出展示给用户。在一些实施例中，终端设备可以将展示信息显示在用户打开的页面上。仅作为示例，用户可以通过客户端打开一个页面，相对的，终端设备可以响应用户打开页面的操作指令，在该页面上显示展示信息。在一些实施例中，终端设备可以将展示信息显示在终端设备的显示界面上。例如，终端设备可以通过弹窗的形式显示所述展示信息，用户可以在所述弹窗的界面，或通过点击弹窗中链接、按钮等获取所述展示信息的内容。在一些实施例中，终端设备可以通过语音播报形式，将所述展示信息传输给用户。
应当注意的是，上述有关流程1200的描述仅仅是为了示例和说明，而不限定本申请的适用范围。对于本领域技术人员来说，在本申请的指导下可以对流程1200进行各种修正和改变。然而，这些修正和改变仍在本申请的范围之内。
需要说明的是，不同实施例可能产生的有益效果不同，在不同的实施例里，可能产生的有益效果可以是以上任意一种或几种的组合，也可以是其他任何可能获得的有益效果。
上文已对基本概念做了描述，显然，对于本领域技术人员来说，上述详细披露仅仅作为示例，而并不构成对本说明书的限定。虽然此处并没有明确说明，本领域技术人员可能会对本说明书进行各种修改、改进和修正。该类修改、改进和修正在本说明书中被建议，所以该类修改、改进、修正仍属于本说明书示范实施例的精神和范围。
同时，本说明书使用了特定词语来描述本说明书的实施例。如“一个实施例”、“一实施例”、和/或“一些实施例”意指与本说明书至少一个实施例相关的某一特征、结构或特点。因此，应强调并注意的是，本说明书中在不同位置两次或 多次提及的“一实施例”或“一个实施例”或“一个替代性实施例”并不一定是指同一实施例。此外，本说明书的一个或多个实施例中的某些特征、结构或特点可以进行适当的组合。
此外，除非权利要求中明确说明，本说明书所述处理元素和序列的顺序、数字字母的使用、或其他名称的使用，并非用于限定本说明书流程和方法的顺序。尽管上述披露中通过各种示例讨论了一些目前认为有用的发明实施例，但应当理解的是，该类细节仅起到说明的目的，附加的权利要求并不仅限于披露的实施例，相反，权利要求旨在覆盖所有符合本说明书实施例实质和范围的修正和等价组合。例如，虽然以上所描述的系统组件可以通过硬件设备实现，但是也可以只通过软件的解决方案得以实现，如在现有的服务器或移动设备上安装所描述的系统。
同理，应当注意的是，为了简化本说明书披露的表述，从而帮助对一个或多个发明实施例的理解，前文对本说明书实施例的描述中，有时会将多种特征归并至一个实施例、附图或对其的描述中。但是，这种披露方法并不意味着本说明书对象所需要的特征比权利要求中提及的特征多。实际上，实施例的特征要少于上述披露的单个实施例的全部特征。
一些实施例中使用了描述成分、属性数量的数字，应当理解的是，此类用于实施例描述的数字，在一些示例中使用了修饰词“大约”、“近似”或“大体上”来修饰。除非另外说明，“大约”、“近似”或“大体上”表明所述数字允许有±20％的变化。相应地，在一些实施例中，说明书和权利要求中使用的数值参数均为近似值，该近似值根据个别实施例所需特点可以发生改变。在一些实施例中，数值参数应考虑规定的有效数位并采用一般位数保留的方法。尽管本说明书一些实施例中用于确认其范围广度的数值域和参数为近似值，在具体实施例中，此类数值的设定在可行范围内尽可能精确。
针对本说明书引用的每个专利、专利申请、专利申请公开物和其他材料，如文章、书籍、说明书、出版物、文档等，特此将其全部内容并入本说明书作为 参考。与本说明书内容不一致或产生冲突的申请历史文件除外，对本说明书权利要求最广范围有限制的文件(当前或之后附加于本说明书中的)也除外。需要说明的是，如果本说明书附属材料中的描述、定义、和/或术语的使用与本说明书所述内容有不一致或冲突的地方，以本说明书的描述、定义和/或术语的使用为准。
最后，应当理解的是，本说明书中所述实施例仅用以说明本说明书实施例的原则。其他的变形也可能属于本说明书的范围。因此，作为示例而非限制，本说明书实施例的替代配置可视为与本说明书的教导一致。相应地，本说明书的实施例不仅限于本说明书明确介绍和描述的实施例。

Claims (29)

  1. 一种共享车辆的信息推送方法，由至少一个处理器执行，其特征在于，所述方法包括：
    响应于用户对终端设备的操作指令，获取与所述操作指令相关的特征信息；
    至少基于所述特征信息确定所述终端设备的展示信息，所述展示信息包括共享车辆的车辆推荐信息和/或共享车辆使用情况信息；
    向所述终端设备发送所述展示信息。
  2. 根据权利要求1所述的方法，其特征在于，与所述操作指令相关的所述特征信息包括所述用户执行所述操作指令的第一位置、所述操作指令的发起时间和所述用户的出行信息；所述展示信息包括所述共享车辆的所述车辆推荐信息；
    所述至少基于所述特征信息确定所述车辆推荐信息，包括：
    基于所述第一位置、所述操作指令的所述发起时间和所述用户的所述出行信息，确定所述用户的出行目的地；
    基于所述出行目的地与预设还车区域之间的距离，从距离所述第一位置的预设距离范围值内的多台共享车辆中确定第一推荐车辆。
  3. 根据权利要求2所述的方法，其特征在于，所述出行信息包括所述用户的多条历史出行信息；以及
    所述确定所述用户的所述出行目的地包括：
    基于所述多条历史出行信息确定多条历史出行路线，以及每条历史出行路 线对应的出行起始时间；
    在所述多条历史出行路线中，将所述出行起始时间与所述操作指令的所述发起时间最接近的历史出行路线确定为预估出行路线；
    确定所述预估出行路线对应的目的地为所述用户的所述出行目的地。
  4. 根据权利要求2所述的方法，其特征在于，所述出行信息包括所述用户的计划出行信息；以及
    所述确定所述用户的所述出行目的地包括：
    获取所述用户的计划出行信息的出行方式以及出行时间；
    基于所述出行方式，确定所述用户的计划出行信息的出行起始地；
    基于所述第一位置与所述用户的计划出行信息的所述出行起始地之间的距离，确定从所述第一位置到所述计划出行信息的所述出行起始地的预估到达时间；
    响应于所述预估到达时间早于所述用户的计划出行信息的出行时间，确定所述用户的计划出行信息的所述出行起始地为所述用户的所述出行目的地。
  5. 根据权利要求2-4中任一项所述的方法，其特征在于，所述基于所述出行目的地与所述预设还车区域之间的距离，从距离所述第一位置的预设距离范围值内的所述多台共享车辆中确定所述第一推荐车辆，包括：
    确定所述多台共享车辆中每台共享车辆的剩余续航里程；
    响应于所述出行目的地与所述预设还车区域之间的距离小于第一预设距离值，确定所述第一位置与所述预设还车区域之间的预估出行里程；
    基于所述多台共享车辆中每台共享车辆的所述剩余续航里程与所述预估出 行里程，确定所述多台共享车辆中满足第一预设条件的共享车辆为所述第一推荐车辆；
    其中，所述第一预设条件包括共享车辆的所述剩余续航里程与所述预估出行里程之间的距离差值大于第二预设距离值，且所述剩余续航里程值在所述多台共享车辆中最小。
  6. 根据权利要求5所述的方法，其特征在于，所述基于所述出行目的地与所述预设还车区域之间的距离，从距离所述第一位置的预设距离范围值内的所述多台共享车辆中确定所述第一推荐车辆包括：
    响应于所述出行目的地与所述预设还车区域之间的距离不小于所述第一预设距离值，确定所述多台共享车辆中所述剩余续航里程值最大的共享车辆为所述第一推荐车辆。
  7. 根据权利要求5-6中任一项所述的方法，其特征在于，所述方法还包括：
    将所述第一推荐车辆对应的剩余续航里程显示给所述用户，并获取所述用户的第一反馈信息；
    响应于所述第一反馈信息指示所述用户确定不使用所述第一推荐车辆，基于所述多台共享车辆的所述剩余续航里程和/或所述用户的输入目的地，从所述多台共享车辆中确定第二推荐车辆。
  8. 根据权利要求1所述的方法，其特征在于，与所述操作指令相关的所述特征信息包括所述用户输入的共享车辆状态标签；
    所述至少基于所述特征信息确定所述终端设备的所述车辆推荐信息包括：
    根据所述用户输入的所述状态标签，从各类型共享车辆中筛选出与所述状态标签对应的共享车辆为第三推荐车辆。
  9. 根据权利要求1-8中任一项所述的方法，其特征在于，所述方法还包括：
    获取推荐车辆的第二位置以及所述用户的第三位置；
    根据所述用户的第三位置与所述推荐车辆的第二位置，为所述用户提供从所述第三位置到达所述第二位置的导航信息。
  10. 根据权利要求9所述的方法，其特征在于，所述共享车辆配置有提醒装置，所述方法还包括：
    计算所述用户的第三位置与所述推荐车辆的第二位置之间的距离；
    若所述用户的第三位置与所述推荐车辆的第二位置之间的距离小于第三预设距离值，则控制所述提醒装置发出提醒信号。
  11. 根据权利要求10所述的方法，其特征在于，所述提醒装置为闪光灯；
    所述控制所述提醒装置发出提醒信号，包括：
    控制所述闪光灯进行闪烁，其中，所述用户的第三位置与所述推荐车辆的第二位置之间的所述距离越小，控制所述闪光灯进行闪烁的频率越高。
  12. 根据权利要求10或11所述的方法，其特征在于，所述方法还包括：
    获取所述用户的第二反馈信息；
    若所述第二反馈信息指示所述用户未寻找到所述推荐车辆，确定第四推荐 车辆为更新后的推荐车辆。
  13. 根据权利要求1-12中任一项所述的方法，其特征在于，所述方法还包括：
    将所述推荐车辆对应的车辆状态更改为预约状态；
    当接收到所述用户发送的骑行开始指令时，控制所述推荐车辆开锁。
  14. 根据权利要求8所述的方法，其特征在于，所述各类型共享车辆分别位于预先划分的多个预设区域，所述方法还包括：
    统计各预设区域中包括的筛选出的共享车辆的数量；
    根据所述各预设区域中包括的所述筛选出的共享车辆的数量，确定需要进行功能升级的目标区域。
  15. 根据权利要求14所述的方法，其特征在于，所述根据各预设区域中包括的筛选出的共享车辆的数量，确定所述需要进行功能升级的目标区域，包括：
    从包括所述筛选出的共享车辆的所述各预设区域中选取参考区域，计算包括所述筛选出的共享车辆的所述各预设区域中除所述参考区域之外的其他每个预设区域中筛选出的所述共享车辆的数量与所述参考区域中筛选出的所述共享车辆的数量的数据差值；
    根据所述数据差值确定所述需要进行功能升级的目标区域。
  16. 根据权利要求14或15所述的方法，其特征在于，所述方法还包括：
    获取所述状态标签对应的预设升级规则；
    按照所述预设升级规则对位于所述目标区域的筛选出的所述共享车辆进行所述功能升级。
  17. 根据权利要求14-16中任一项所述的方法，其特征在于，所述共享车辆的所述状态标签通过以下方式确定：
    获取至少一个所述共享车辆发送的至少一个状态数据；
    针对每个所述共享车辆发送的每个所述状态数据，获取该状态数据所属的状态类型，并获取所述状态类型对应的预设评估策略；
    针对每个所述共享车辆发送的属于每种所述状态类型的所述状态数据，采用与所述状态类型对应的所述预设评估策略进行分析，得到与发送属于所述状态类型的状态数据的共享车辆对应的所述状态标签。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    向所述筛选出的每个共享车辆分别发送控制指令，以禁止所述筛选出的共享车辆发送与该共享车辆对应的状态数据。
  19. 根据权利要求17所述的方法，其特征在于，所述预设评估策略通过以下方式获得：
    提供策略配置界面；
    响应在所述策略配置界面的配置操作，获得所述预设评估策略。
  20. 根据权利要求1所述的方法，其特征在于，所述至少基于所述特征信息确定所述展示信息包括：
    获取第一时刻的多个预设区域内的共享车辆使用情况；其中，所述共享车辆使用情况包括所述共享车辆的数量；
    根据所述第一时刻的共享车辆使用情况对第二时刻存储的所述预设区域内的共享车辆使用情况进行更新，生成携带所述共享车辆使用情况的所述展示信息。
  21. 根据权利要求20所述的方法，其特征在于，所述终端设备包括运维端；
    所述获取所述第一时刻的所述多个预设区域内的所述共享车辆使用情况，包括：
    接收所述运维端发送的投放到所述预设区域内的所述共享车辆数量；或
    当接收到所述运维端发送的在所述预设区域内的其中一辆共享车辆的第一扫码信息时，将所述预设区域对应的所述共享车辆数量加一以对所述共享车辆数量进行更新。
  22. 根据权利要求20或21所述的方法，其特征在于，所述终端设备包括客户端；
    所述获取所述第一时刻的所述多个预设区域内的所述共享车辆使用情况，包括：
    当接收到所述客户端发送的在所述预设区域内的其中一辆共享车辆的第二扫码信息时，将所述预设区域对应的所述共享车辆数量减一以对所述共享车辆数量进行更新。
  23. 根据权利要求20-22中任一项所述的方法，其特征在于，所述共享车辆使用情况包括所述共享车辆的故障情况；
    所述获取所述第一时刻的所述多个预设区域内的所述共享车辆使用情况，包括：
    接收所述用户对所述终端设备发送的车辆标识信息；其中，所述车辆标识信息用于标记所述预设区域内的所述共享车辆是否故障。
  24. 根据权利要求23所述的方法，其特征在于，所述方法还包括：
    接收所述运维端发送的所述预设区域的范围。
  25. 一种共享车辆的信息推荐方法，其特征在于，应用于终端设备，所述方法包括：
    接收用户对所述终端设备的操作指令；
    获取与所述操作指令相关的特征信息；
    至少基于所述特征信息确定展示信息，所述展示信息包括共享车辆的车辆推荐信息和/或共享车辆使用情况信息；
    在所述终端设备页面上显示所述展示信息。
  26. 一种共享车辆的信息推送系统，其特征在于，所述系统包括：
    第一获取模块，用于响应于用户对终端设备的操作指令，获取与所述操作指令相关的特征信息；
    第一确定模块，用于至少基于所述特征信息确定所述终端设备的展示信息，所述展示信息包括共享车辆的车辆推荐信息和/或共享车辆使用情况信息；
    传输模块，用于向所述终端设备发送所述展示信息。
  27. 一种用于共享车辆的信息推送的终端设备，其特征在于，所述终端设备包括：
    接收模块，用于接收用户打开所述终端设备的操作指令；
    第二获取模块，用于获取与所述操作指令相关的特征信息；
    第二确定模块，用于至少基于所述特征信息确定展示信息，所述展示信息包括共享车辆的车辆推荐信息和/或共享车辆使用情况信息；
    显示模块，用于在所述终端设备页面上显示所述展示信息。
  28. 一种电子设备，其特征在于，包括：处理器、存储介质和总线，所述存储介质存储有所述处理器可执行的机器可读指令，当电子设备运行时，所述处理器与所述存储介质之间通过总线通信，所述处理器执行所述机器可读指令，以执行如权利要求1-25任一项所述的方法。
  29. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器运行时执行如权利要求1-25任一项所述的方法。
PCT/CN2020/141152 2019-12-31 2020-12-30 一种共享车辆的信息推送方法和系统 WO2021136324A1 (zh)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CN201911406331.4 2019-12-31
CN201911412463.8 2019-12-31
CN201911406331.4A CN111861624A (zh) 2019-12-31 2019-12-31 一种车辆的推荐方法、装置、电子设备及可读存储介质
CN201911424973.7A CN111858624A (zh) 2019-12-31 2019-12-31 一种车辆使用情况更新方法及装置
CN201911424973.7 2019-12-31
CN201911412463.8A CN111860877A (zh) 2019-12-31 2019-12-31 共享车辆管理方法、装置、服务器和可读存储介质

Publications (1)

Publication Number Publication Date
WO2021136324A1 true WO2021136324A1 (zh) 2021-07-08

Family

ID=76686537

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/141152 WO2021136324A1 (zh) 2019-12-31 2020-12-30 一种共享车辆的信息推送方法和系统

Country Status (1)

Country Link
WO (1) WO2021136324A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114212022A (zh) * 2021-12-16 2022-03-22 浙江吉利控股集团有限公司 车辆灯效共享方法、装置、设备、介质及程序产品
CN114564655A (zh) * 2021-12-23 2022-05-31 北京中交兴路信息科技有限公司 基于协同过滤的车辆推荐方法、装置、设备及存储介质
CN114973519A (zh) * 2022-04-24 2022-08-30 江苏中州科技有限公司 一种基于物联网的智能监控管理系统及方法
CN115240299A (zh) * 2022-07-07 2022-10-25 上海钧正网络科技有限公司 资源的使用方法和系统
CN117787669A (zh) * 2024-02-26 2024-03-29 北京阿帕科蓝科技有限公司 车辆管理方法、装置、计算机设备和存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106846881A (zh) * 2017-03-30 2017-06-13 上海卓易科技股份有限公司 共享车辆方法、装置及系统
CN108629652A (zh) * 2018-03-27 2018-10-09 深圳市元征科技股份有限公司 一种共享汽车使用方案推荐方法及服务器
CN109409980A (zh) * 2018-09-10 2019-03-01 中国联合网络通信集团有限公司 单车推荐方法、装置、设备及计算机可读存储介质
CN109409982A (zh) * 2018-09-18 2019-03-01 杭州的蓝科技有限公司 共享车辆推荐方法及装置
CN111861624A (zh) * 2019-12-31 2020-10-30 北京骑胜科技有限公司 一种车辆的推荐方法、装置、电子设备及可读存储介质
CN111858624A (zh) * 2019-12-31 2020-10-30 北京骑胜科技有限公司 一种车辆使用情况更新方法及装置
CN111860877A (zh) * 2019-12-31 2020-10-30 北京骑胜科技有限公司 共享车辆管理方法、装置、服务器和可读存储介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106846881A (zh) * 2017-03-30 2017-06-13 上海卓易科技股份有限公司 共享车辆方法、装置及系统
CN108629652A (zh) * 2018-03-27 2018-10-09 深圳市元征科技股份有限公司 一种共享汽车使用方案推荐方法及服务器
CN109409980A (zh) * 2018-09-10 2019-03-01 中国联合网络通信集团有限公司 单车推荐方法、装置、设备及计算机可读存储介质
CN109409982A (zh) * 2018-09-18 2019-03-01 杭州的蓝科技有限公司 共享车辆推荐方法及装置
CN111861624A (zh) * 2019-12-31 2020-10-30 北京骑胜科技有限公司 一种车辆的推荐方法、装置、电子设备及可读存储介质
CN111858624A (zh) * 2019-12-31 2020-10-30 北京骑胜科技有限公司 一种车辆使用情况更新方法及装置
CN111860877A (zh) * 2019-12-31 2020-10-30 北京骑胜科技有限公司 共享车辆管理方法、装置、服务器和可读存储介质

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114212022A (zh) * 2021-12-16 2022-03-22 浙江吉利控股集团有限公司 车辆灯效共享方法、装置、设备、介质及程序产品
CN114564655A (zh) * 2021-12-23 2022-05-31 北京中交兴路信息科技有限公司 基于协同过滤的车辆推荐方法、装置、设备及存储介质
CN114973519A (zh) * 2022-04-24 2022-08-30 江苏中州科技有限公司 一种基于物联网的智能监控管理系统及方法
CN115240299A (zh) * 2022-07-07 2022-10-25 上海钧正网络科技有限公司 资源的使用方法和系统
CN115240299B (zh) * 2022-07-07 2024-05-24 上海钧正网络科技有限公司 资源的使用方法和系统
CN117787669A (zh) * 2024-02-26 2024-03-29 北京阿帕科蓝科技有限公司 车辆管理方法、装置、计算机设备和存储介质

Similar Documents

Publication Publication Date Title
WO2021136324A1 (zh) 一种共享车辆的信息推送方法和系统
JP6934024B2 (ja) 経路計画システムおよび方法
US9689693B2 (en) Systems and methods for learning and displaying customized geographical navigational options
US11305780B2 (en) Road condition status prediction method, device, and server, and storage medium
Motta et al. Personal mobility service system in urban areas: The IRMA project
US20170213273A1 (en) Customer-centered transportation aggregator
WO2016119704A1 (zh) 一种为按需服务提供信息的方法及系统
US20140122190A1 (en) System and methods for detection and selection of a resource among available resources
CN113851016B (zh) 泊车管理方法、装置、电子设备及存储介质
US20170178511A1 (en) Determining parking status and parking availability
CN116362370A (zh) 智慧城市停车场车位状态预估方法、物联网系统及装置
US20220005140A1 (en) Method, apparatus, and system for providing a contextually relevant vehicle comparison
US11741565B1 (en) Method, internet of things system and storage medium of public transport management in a smart urban
WO2020239108A1 (zh) 一种定位方法、装置、电子设备及存储介质
Fadda et al. A social internet of things smart city solution for traffic and pollution monitoring in cagliari
CN112418556B (zh) 一种基于互联网共享平台下的网格化服务系统
Yang et al. Taxi operation optimization based on big traffic data
Guan et al. A unified framework for predicting kpis of on-demand transport services
Barker et al. Investigating the use of machine learning for smart parking applications
CN114492927A (zh) 气象信息的推送方法、存储介质及计算机终端
CN113657681A (zh) 联结智能公交站台和共享交通的方法、系统和存储介质
Stojanović et al. Web information system for transport telematics and fleet management
Rémy et al. Green fleet management architecture: Application to economic itinerary planning
US20230011007A1 (en) Information processing device and information processing method
Sperling et al. Mobility data and models informing smart cities

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20910239

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20910239

Country of ref document: EP

Kind code of ref document: A1