WO2019227451A1 - 一种共享车辆的管理方法和服务器 - Google Patents
一种共享车辆的管理方法和服务器 Download PDFInfo
- Publication number
- WO2019227451A1 WO2019227451A1 PCT/CN2018/089408 CN2018089408W WO2019227451A1 WO 2019227451 A1 WO2019227451 A1 WO 2019227451A1 CN 2018089408 W CN2018089408 W CN 2018089408W WO 2019227451 A1 WO2019227451 A1 WO 2019227451A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- vehicle
- client
- shared vehicle
- lease
- shared
- Prior art date
Links
- 238000007726 management method Methods 0.000 title claims abstract description 9
- 238000000034 method Methods 0.000 claims abstract description 48
- 238000004590 computer program Methods 0.000 claims description 32
- 230000008569 process Effects 0.000 claims description 14
- 238000012790 confirmation Methods 0.000 claims description 7
- 230000006399 behavior Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000001133 acceleration Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
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
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0621—Item configuration or customization
-
- 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
- G06Q30/0645—Rental transactions; 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
- G06Q10/00—Administration; Management
- G06Q10/02—Reservations, e.g. for tickets, services or events
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/14—Payment architectures specially adapted for billing systems
- G06Q20/145—Payments according to the detected use or quantity
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
- H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
- H04L9/0637—Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
- H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
-
- 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
- G06Q2220/00—Business processing using cryptography
-
- 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
- G06Q2240/00—Transportation facility access, e.g. fares, tolls or parking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/84—Vehicles
Definitions
- the present application belongs to the technical field of vehicles, and in particular, to a method and a server for managing a shared vehicle.
- the sharing schemes implemented in some enterprises are not true resource sharing.
- the original intention of resource sharing is to share some idle or unused cars with the rental service platform. While realizing the full use of car resources, It can also bring some benefits to car owners, but due to credit risk in the leasing service platform or opaque transaction data during the transaction process, some car owners are unwilling to share their cars with the leasing service platform.
- the leasing service platform had to purchase vehicles for lease outside, which not only increased the operating costs of leasing service enterprises, but also departed from the original intention of resource sharing.
- embodiments of the present application provide a management method and server for shared vehicles, which can solve the problems of insufficient disclosure of shared platform sharing information and being easily tampered with in the prior art, resulting in the owner's reluctance to share his vehicle.
- a first aspect of the embodiments of the present application provides a method for managing a shared vehicle, where the method for managing a shared vehicle includes:
- the lease request including personal information and lease requirements of a user who initiated the lease request;
- the use right of the target shared vehicle is released to the rental client.
- the method before the receiving the shared information sent by the vehicle owner client and using the smart contract, the method includes:
- the service agreement and the service smart contract are registered in a blockchain network, and the service smart contract is generated according to the service agreement.
- the shared information includes vehicle owner identity information.
- the method further includes:
- the method includes:
- the usage data is registered in the blockchain network.
- the method further includes:
- the method further includes:
- Dividing is performed according to the allocation scheme.
- a second aspect of the embodiments of the present application provides a server, where the server includes: a memory storing an executable computer program;
- the lease request including personal information and lease requirements of a user who initiated the lease request;
- the use right of the target shared vehicle is released to the rental client.
- the processor before receiving the shared information sent by the vehicle owner client and using the smart contract, the processor calls an executable computer program in the memory, and is further configured to:
- the service agreement and the service smart contract are registered in a blockchain network, and the service smart contract is generated according to the service agreement.
- the processor calls an executable computer program in the memory, and is further configured to:
- the processor calls an executable computer program in the memory, and is further configured to:
- the usage data is registered in the blockchain network.
- the processor calls an executable computer program in the memory, and is further configured to:
- the processor calls an executable computer program in the memory, and is further configured to:
- Dividing is performed according to the allocation scheme.
- a computer-readable storage medium stores a computer program, which is characterized in that, when the computer program is executed by a processor, it implements extremely any one of the first aspects described above.
- the steps of the method for managing a shared vehicle provided in an optional embodiment.
- the shared information sent by the owner client and the personal information and rental requirements of the user sent by the rental client are registered in the blockchain network, thereby ensuring the owner of the shared vehicle.
- the real information of the user can be obtained in time, and the rental and usage of the shared vehicle within each time period can be learned, so that the owner can safely share his vehicle to each shared vehicle service platform.
- FIG. 1 is a schematic structural diagram of a shared vehicle management system according to an embodiment of the present application.
- FIG. 2 is a schematic flowchart of a method for managing a shared vehicle according to an embodiment of the present application
- FIG. 3 is a schematic structural diagram of a server according to an embodiment of the present application.
- FIG. 1 shows a schematic structural diagram of a shared vehicle management system according to an embodiment of the present application.
- the shared vehicle management system includes a vehicle owner client 11, a rental client 12, a server 13, and a number of areas as blockchain nodes.
- the blockchain network device 14, the vehicle owner client 11, the leasing client 12, and the blockchain network device 14 are connected to the server 13, respectively.
- the buyer client 12 is configured to send shared information to the server 13 and use a smart contract.
- the use smart contract includes a usage rule of the shared vehicle, and the shared information includes shared vehicle information and identity information of an owner of the shared vehicle.
- the lease client 12 is used to send a lease request to the server, and the server 13 is used to register the received shared information and use smart contracts in the blockchain network device 14 and broadcast the entire network.
- the leasing request finds a matching shared vehicle for the client of the rental client to use the target shared vehicle after determining the target shared vehicle.
- the above-mentioned blockchain network device 14 is configured to receive the relevant data sent by the server 13 and store it. Further, the above-mentioned owner client 11 and rental client 12 may each be one of smart terminals such as a personal computer, a smart phone, a tablet computer, and a smart wearable device.
- the server 13 can send information to the blockchain network device 14 and the blockchain network device can register the information in the blockchain and broadcast it on the entire network, or it can register in the blockchain to become a node device of the blockchain.
- FIG. 2 shows a flowchart of a method for managing a shared vehicle provided by an embodiment of the present application.
- the method for managing a shared vehicle includes steps S21 to S26, which are described in detail as follows:
- step S21 the sharing information and the smart contract used by the vehicle owner client are received.
- the server receives the shared information sent by the owner client and uses the smart contract.
- the owner client is used to receive the shared vehicle information and the identity information of the owner input by the owner of the shared vehicle, and then the owner customer
- the terminal sends the information of the shared vehicle and the identity information of the owner to the server.
- the information of the shared vehicle includes information such as the license plate number of the shared vehicle, the driving license of the vehicle, the age of the vehicle, the operating status of the engine, the operating status of the safety equipment and electronic equipment, and the mileage.
- the identity information of the above vehicle owner includes one or more of the vehicle owner's name, ID number, contact information, and the like.
- the above-mentioned smart contract for use specifies the rules for using the shared vehicle, including information such as the charging rules and payment methods when using the shared vehicle.
- Step S22 Register the shared information and the used smart contract in a blockchain network and broadcast the entire network.
- the server sends the received shared information and the above-mentioned smart contract to the blockchain network device, and the blockchain network device is registered in the blockchain and broadcasted on the entire network, or when the server itself is a node device of the blockchain At that time, the server directly registers the received shared information and the above-mentioned smart contract in the blockchain and broadcasts the entire network so that other blockchain network devices can also obtain the same information and instruct the other blockchain networks.
- the device stores the received information.
- the server may package the shared information and the used smart contract before sending.
- step S23 the lease request sent by the lease client is received and registered in the blockchain network, and the lease request contains the personal information and lease requirements of the user who initiated the lease request.
- the server waits to receive the lease request from the leasing client, and if the lease request is received, the above lease request is registered in the blockchain network; the above lease request contains the personal information and lease requirements of the user who sent the lease request.
- Personal information includes personal identification and driving behavior preferences, and rental requirements include information such as model preferences, location information, and cost estimates.
- Step S24 Calculate the user level of the user who initiated the lease request according to the pre-stored credit smart contract and the personal information in the blockchain.
- the server After receiving the lease request, the server retrieves specific user information stored in the blockchain network, such as driving behavior information, traffic violation information, driving mileage information, and transaction information using shared cars, according to the personal identification in the lease request.
- the user level of the user is calculated according to the specific user information, and the user level includes a user credit level and a driving level, and at the same time, a matching shared vehicle is found for the user based on the rental requirements of the user.
- the credit rating can be determined according to the ratio of the user's driving mileage to the violations and violation information within the driving mileage (for example, the corresponding number of violations or violations within a 1,000 km driving mileage). For example, assuming that the user's basic credit rating is average, the user information shows that the driving mileage is longer, and there is no violation in driving mileage, and there is no traffic violation information, it can be determined that the user's credit rating is good. If the user information shows that his driving mileage is short, there are no violations in the driving mileage process, and there is no traffic violation; or the user's driving mileage and driving violations remain at a low ratio (for example, the corresponding violations within 1,000 kilometers of driving mileage) Or the number of violations is within 5 times.), The user's credit rating can be considered average. If the user information shows that his driving mileage is within the driving mileage, there is a high rate of violations and violations (for example, the corresponding violations or violations are more than 10 times in a 1,000 km driving mileage), the user's credit is considered Poor grade.
- the driving level of the user may be determined according to driving mileage and driving behavior information. The longer the driving mileage, the fewer the number of driving violations in the corresponding driving behavior information, and the higher the driving level of the user.
- Step S25 Find a matching shared vehicle according to the user level and the rental requirements.
- the user level (credit level and driving level) calculated according to the above calculation can be used to determine the range of shared vehicles that match the user, including the range of tolls and vehicle types, etc., combined with the user's rental requirements such as model preferences, location information, and cost budget Wait to determine the matching shared vehicle, so as to provide users with matching shared vehicle information.
- Step S26 Send the matched shared vehicle to a rental client, so that the rental client determines a target shared vehicle.
- Step S27 Release the use right of the target shared vehicle to the rental client.
- a suitable shared vehicle is found in the shared vehicle for it, and the information of the found target shared vehicle is sent to the above rental client for selection by the above user. If the user's selection information of the target shared vehicle sent by the leasing client is received, the use right of the target shared vehicle is released to the user.
- the specific way of releasing the use right of the target shared vehicle to the user may be directly controlling the door opening of the shared vehicle and making the engine in a usable state, or sending the control password of the vehicle to the rental client, and the user Open the door and start the engine according to the control password to obtain the right to use the shared vehicle.
- each block contains two parts, a block header and a block body.
- the block header is used to record the feature values of the current block, and the block body is the actual data.
- the block header contains multiple feature values of the current block.
- the multiple characteristic values include: a generation time, a hash value of a block body, and a hash value of a previous block.
- the hash value of the block is calculated for the block header. In other words, the various feature values of the block header are connected together in order to form a long string, and the hash value is calculated for this string, so the hash value of each block is different. Yes, the block can be identified by a hash.
- the block header contains a lot of content, including the hash of the current block body and the hash of the previous block. Due to the consensus mechanism of the blockchain, it is almost impossible to modify multiple blocks in a short time, unless someone has mastered more than 51% of the computing power of the entire network. This has formed the decentralized and immutable characteristics of the blockchain.
- the data in the blockchain is used to be decentralized and cannot be tampered with, and information such as usage data and transaction data generated during the vehicle rental process is sent to the node device of the blockchain.
- the storage is performed to ensure that the vehicle owner can obtain real vehicle usage data and transaction data, so that the vehicle owner can safely share the vehicle with a service platform such as a user terminal.
- the smart contract is a computer-executable program capable of automatically executing contract terms. It does not generate or modify smart contracts; it exists only to allow a complex set of digital commitments with triggering conditions to be correctly executed according to the wishes of the participants. Therefore, after the smart contract is deployed on the blockchain, it is waiting to be called and cannot be changed.
- the identifier of the smart contract may be the name of the smart contract, which is used for Uniquely identifies the smart contract deployed on the blockchain. Therefore, the information sent by the user terminal to the blockchain can carry the identification of different smart contracts, so that the blockchain network can call the corresponding smart contract to execute the corresponding program after receiving the relevant data carrying the smart contract identification information. .
- before the receiving the shared information sent by the vehicle owner client and using the smart contract includes:
- the service agreement and the service smart contract are registered in a blockchain network, and the service smart contract is generated according to the service agreement.
- the server will pre-publish the service agreement of the shared vehicle to guide the owners to submit shared information and use smart contracts according to the service agreement.
- the above service agreement may specify the basic requirements of the shared vehicle (such as the age of the vehicle, the driving distance, etc.), the requirements of the owner certification (such as what information the vehicle mainly provides to authenticate its identity), and so on.
- the server may also install a vehicle-mounted terminal for the shared vehicle of the certified vehicle owner.
- the service agreement may further include a request method for installing a vehicle-mounted terminal and a charging rule for installing a vehicle-mounted terminal.
- the above service agreement is also used to inform vehicle owners that driving data of shared vehicles will be registered in the blockchain network.
- the server issues the above service agreement and specifies a service smart contract according to the above service agreement to facilitate subsequent review of the shared information sent by the owner.
- the server registers the service agreement and service smart contract issued in the blockchain network.
- the shared information includes vehicle owner identity information
- the method further includes:
- the identity of the owner is authenticated. For example, all the relationship between the sender and the shared vehicle can be determined by using the information in the vehicle driving license of the shared vehicle. The information is included in the shared information sent by the owner's client.
- the on-board terminal and the on-board terminal identification are assigned to the shared vehicle, and the above-mentioned on-board terminal is used to record and send the user data during the use of the vehicle to the user terminal;
- after the releasing the use right of the target shared vehicle to the rental client includes:
- the usage data is registered in the blockchain network.
- the use data generated during the use of the target shared vehicle is monitored in real time by the on-board terminal, and the above usage number can be driven by the user.
- the data generated in the process of the above target shared vehicle includes: the length of use of the target shared vehicle, the driving trajectory, driving behavior (such as sharp turns), lane change and other data, and the operating condition data of the target shared vehicle (such as vehicle speed, acceleration) , Engine data flow, transmission data flow), etc.
- the vehicle-mounted terminal sends the collected usage data to the server. If the server receives the usage data of the target shared vehicle, it sends the above usage data to the blockchain network for storage.
- the method further includes:
- the server determines the use data in the current use process based on the user ’s end instruction based on the real-time uploaded use data, and performs the use data according to the attributes.
- Classification for example, determines the use time, driving trajectory, and driving behavior data of the target shared vehicle as driving data; determines the vehicle speed, acceleration data, engine data, and transmission data as vehicle condition data.
- the ownership of the classification data is determined according to the classification attribute of the use data, for example, the ownership of the driving data belongs to the user who initiated the lease request, and the ownership of the vehicle condition data belongs to the owner.
- the classification data is sent to the corresponding owner, and the ownership is marked at the same time. For example, driving data is sent to a user, vehicle condition data is sent to a vehicle owner, and ownership is marked by means of marking or adding a watermark.
- the method further includes:
- Dividing is performed according to the allocation scheme.
- the server invokes the smart contract for the use of the shared vehicle to initiate a payment transaction request to the leasing client, including providing the itinerary list and charging details , For the user to complete the payment transaction according to the itinerary list and charge details.
- the leasing client sends a confirmation of the payment transaction to the server.
- the server will call the service smart contract to form a distribution plan based on the amount paid, and distribute the revenue among the relevant parties according to the distribution plan. Since the operator of the server also provides corresponding services during the transaction, the allocation scheme is mainly distributed between the owner and the operator.
- the car owner allocates 90% of the payment amount, and the server operator allocates 10% of the payment amount. Then according to the distribution plan, the corresponding part of the payment amount is transferred to the corresponding accounts of the owner and the operator.
- This is just a list, and there are many other distribution schemes, which are not specifically limited here.
- the violation of fines and other matters will be processed after the order, such as charging the above users for violations of fines.
- the received shared information sent by the owner client and the personal information and rental request of the user sent by the rental client are registered in the blockchain network, thereby ensuring the owner of the shared vehicle It can timely obtain the real information of users, and understand the rental and use of the vehicles they share within each time period, so that owners can rest assured that they can share their vehicles with the service platform of each shared vehicle, improving the owners The enthusiasm of shared vehicles also improves the efficiency of shared use of vehicles.
- FIG. 3 is a schematic structural diagram of a server according to an embodiment of the present application.
- the server 3 of this embodiment includes a processor 30, a memory 31, and a computer program 32 stored in the memory 31 and executable on the processor 30, such as a program in a management method of a shared vehicle.
- the processor 30 executes the computer program 32, the steps in the embodiments of the method for managing shared vehicles are implemented, for example, steps S21 to S26 shown in FIG. 2, and when the processor 30 executes the computer program 32, it is implemented. Steps S21 to S26 shown in FIG. 2.
- the server may include, but is not limited to, a processor 30 and a memory 31.
- FIG. 3 is only an example of the terminal device 3, and does not constitute a limitation on the server 3. It may include more or fewer components than shown in the figure, or combine some components or different components.
- the server 3 may further include an input-output device, a network access device, and a bus.
- the so-called processor 30 may be a central processing unit (Central Processing Unit (CPU), or other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (Application Specific Integrated Circuits) Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
- CPU Central Processing Unit
- DSP Digital Signal Processor
- ASIC Application Specific Integrated Circuits
- FPGA Field-Programmable Gate Array
- a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
- the memory 31 may be an internal storage unit of the server 3, such as a hard disk or a memory of the server 3.
- the memory 31 may also be an external storage device of the server 3, such as a plug-in hard disk, a Smart Media Card (SMC), and a Secure Digital (SD) card provided on the server 3. Flash card, etc.
- the memory 31 may include both an internal storage unit of the server 3 and an external storage device.
- the memory 31 is configured to store the computer program and other programs and data required for the insurance underwriting.
- the memory 31 may also be used to temporarily store data that has been output or is to be output.
- the processor 30 executing the computer program 32 stored in the memory 31 includes:
- the lease request including personal information and lease requirements of a user who initiated the lease request;
- the use right of the target shared vehicle is released to the rental client.
- the processor before receiving the shared information sent by the vehicle owner client and using the smart contract, the processor calls an executable computer program in the memory, and is further configured to:
- the service agreement and the service smart contract are registered in a blockchain network, and the service smart contract is generated according to the service agreement.
- the processor calls an executable computer program in the memory, and is further configured to:
- the processor calls an executable computer program in the memory, and is further configured to:
- the usage data is registered in the blockchain network.
- the processor calls an executable computer program in the memory, and is further configured to:
- the processor calls an executable computer program in the memory, and is further configured to:
- Dividing is performed according to the allocation scheme.
- the computer program 32 may be divided into one or more units / modules, and the one or more units / modules are stored in the memory 31 and executed by the processor 30 to complete the present application.
- the server 3 may be a cloud server, a smart device, a computing device such as a computer, a notebook, and a palm computer.
- the server 3 may include, but is not limited to, a processor 30 and a memory 31.
- FIG. 3 is only an example of the server 3, and does not constitute a limitation on the server 3. It may include more or fewer components than shown in the figure, or combine some components, or different components, such as
- the server 3 may further include an input / output device, a network access device, a bus, and the like.
- the so-called processor 30 may be a central processing unit (Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSP), and application-specific integrated circuits (Application Specific Integrated Circuit (ASIC), off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
- CPU Central Processing Unit
- DSP digital signal processors
- ASIC Application Specific Integrated Circuit
- ASIC Application Specific Integrated Circuit
- FPGA Field-Programmable Gate Array
- a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
- the memory 31 may be an internal storage unit of the server 3, such as a hard disk or a memory of the server 3.
- the memory 31 may also be an external storage device of the server 3, for example, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a flash memory card ( Flash Card) and so on. Further, the memory 31 may further include both an internal storage unit of the server 3 and an external storage device.
- the memory 31 is used to store the computer program and other programs and data required by the server 3.
- the above-mentioned memory 31 may also be used to temporarily store data that has been output or is to be output.
- the technical solution of the present application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product.
- the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application.
- the aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), and a random access memory (RAM, Random Access) Memory), magnetic disks or optical disks, and other media that can store program code.
- the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:
- the lease request including personal information and lease requirements of a user who initiated the lease request;
- the use right of the target shared vehicle is released to the rental client.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Computer Security & Cryptography (AREA)
- Tourism & Hospitality (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Human Resources & Organizations (AREA)
- Entrepreneurship & Innovation (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computing Systems (AREA)
- Primary Health Care (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
本申请提供了一种共享车辆的管理方法及服务器,包括:接收车主客户端发送的共享信息以及使用智能合约;将其登记在区块链网络中并全网广播;接收租赁客户端发送的租赁请求并登记在所述区块链网络中;根据所述区块链中预存的信用智能合约和用户的个人信息计算发起租赁请求的用户的用户等级;进而查找匹配的共享车辆;将所述匹配的共享车辆发送至租赁客户端,以使所属租赁客户端确定目标共享车辆;释放所述目标共享车辆的使用权给所述租赁客户端保证了车主能够及时获取到用户的真实信息,并了解到自己共享的车辆在每个时间段内的出租以及被使用情况,从而使车主能够放心的将自己的车辆分享给各个共享车辆的服务平台。
Description
本申请属于车辆技术领域,尤其涉及一种共享车辆的管理方法和服务器。
随着资源共享的概念不断深入人心,越来越多的企业开始涉足资源共享领域,如共享单车、共享汽车等。
但目前一些企业中施行的共享方案并非真正的资源共享,以汽车租赁企业为例,资源共享的本意是将一些车主闲置或不常用的汽车共享给租赁服务平台,在实现汽车资源充分利用的同时也可为车主带来一定的收益,但由于租赁服务平台存在信用风险,或交易过程中交易数据不透明等因素,造成一些车主并不愿意将自己的车共享给租赁服务平台。租赁服务平台不得不自己购买车辆向外出租,这不仅增加了租赁服务企业的运营成本,也背离了资源共享的本意。
有鉴于此,本申请实施例提供一种共享车辆的管理方法和服务器,可以解决现有技术中共享平台共享信息公开不足,且容易被篡改,导致车主不愿意将其车辆共享的问题。
本申请实施例第一方面提供一种共享车辆的管理方法,所述共享车辆的管理方法包括:
接收车主客户端发送的共享信息以及使用智能合约;
将所述共享信息和所述使用智能合约登记在区块链网络中并全网广播;
接收租赁客户端发送的租赁请求并登记在所述区块链网络中,所述租赁请求中包含发起租赁请求的用户的个人信息和租赁要求;
根据所述区块链中预存的信用智能合约和所述个人信息计算所述发起租赁请求的用户的用户等级;
根据所述用户等级和所述租赁要求查找匹配的共享车辆;
将所述匹配的共享车辆发送至租赁客户端,以使所述租赁客户端确定目标共享车辆;
释放所述目标共享车辆的使用权给所述租赁客户端。
可选地,在所述接收车主客户端发送的共享信息以及使用智能合约之前,所述方法包括:
发布共享车辆的服务协议,所述服务协议用于指导共享车辆的车主提交共享信息以及使用智能合约;
将所述服务协议和服务智能合约登记在区块链网络中,所述服务智能合约根据所述服务协议生成。
可选地,所述共享信息包括车主身份信息,在所述接收车主客户端发送的共享信息以及使用智能合约之后,所述方法还包括:
根据所述车主身份信息对所述车主进行身份认证;
若认证通过,则根据所述使用智能合约向所述车主的共享车辆分配车载终端和车载终端标识;
根据所述车载终端标识将所述车载终端作为区块链网络的一个节点登记在区块链网络中。
可选地,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述方法包括:
接收所述目标共享车辆在被使用过程中产生的使用数据,所述使用数据由所述车载终端提交;
将所述使用数据登记在所述区块链网络中。
可选地,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述方法还包括:
当接收到所述租赁客户端发送租赁结束请求时,将所述使用数据进行分类;根据分类属性确定分类数据的所有权;
将分类数据发送至对应的所有权方。
可选地,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述方法还包括:
当接收到所述租赁客户端发送租赁结束请求时,调用所述使用智能合约向所述租赁客户端发起支付交易请求;
在接收到所述租赁客户端的支付交易确认信息后,调用服务智能合约根据所述支付交易产生的收益生成分配方案;
按照所述分配方案进行分成。
本申请实施例第二方面提供一种服务器,所述服务器包括:存储有可执行计算机程序的存储器;
与所述存储器耦合的处理器,所述处理器调用所述存储器中的可执行计算机程序,用于:
接收车主客户端发送的共享信息以及使用智能合约;
将所述共享信息和所述使用智能合约登记在区块链网络中并全网广播;
接收租赁客户端发送的租赁请求并登记在所述区块链网络中,所述租赁请求中包含发起租赁请求的用户的个人信息和租赁要求;
根据所述区块链中预存的信用智能合约和所述个人信息计算所述发起租赁请求的用户的用户等级;
根据所述用户等级和所述租赁要求查找匹配的共享车辆;
将所述匹配的共享车辆发送至租赁客户端,以使所述租赁客户端确定目标共享车辆;
释放所述目标共享车辆的使用权给所述租赁客户端。
可选地,在所述接收车主客户端发送的共享信息以及使用智能合约之前,所述处理器调用所述存储器中的可执行计算机程序,还用于:
发布共享车辆的服务协议,所述服务协议用于指导共享车辆的车主提交共享信息以及使用智能合约;
将所述服务协议和服务智能合约登记在区块链网络中,所述服务智能合约根据所述服务协议生成。
可选地,在所述接收车主客户端发送的共享信息以及使用智能合约之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:
根据所述车主身份信息对所述车主进行身份认证;
若认证通过,则根据所述使用智能合约向所述车主的共享车辆分配车载终端和车载终端标识;
根据所述车载终端标识将所述车载终端作为区块链网络的一个节点登记在区块链网络中。
可选地,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:
接收所述目标共享车辆在被使用过程中产生的使用数据,所述使用数据由所述车载终端提交;
将所述使用数据登记在所述区块链网络中。
可选地,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:
当接收到所述租赁客户端发送租赁结束请求时,将所述使用数据进行分类;根据分类属性确定分类数据的所有权;
将分类数据发送至对应的所有权方。
可选地,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:
当接收到所述租赁客户端发送租赁结束请求时,调用所述使用智能合约向所述租赁客户端发起支付交易请求;
在接收到所述租赁客户端的支付交易确认信息后,调用服务智能合约根据所述支付交易产生的收益生成分配方案;
按照所述分配方案进行分成。
本申请实施例第三方面提供一种计算机可读存储介质,所述计算机可读存储介质存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现如上述第一方面极其任意一种可选的实施方式中提供的共享车辆的管理方法的步骤。
本申请提供的实施例中通过将接收到的车主客户端发送的共享信息以及租赁客户端发送的用户的个人信息和租赁要求等信息均登记在区块链网络中,从而保证了共享车辆的车主能够及时获取到用户的真实信息,并了解到自己共享的车辆在每个时间段内的出租以及被使用情况,从而使车主能够放心的将自己的车辆分享给各个共享车辆的服务平台。
为了更清楚地说明本申请实施例的技术方案,下面将对实施例中所需要使用的附图作简单地介绍。
图1是本申请实施例提供的一种共享车辆的管理系统结构示意图;
图2是本申请实施例提供的一种共享车辆的管理方法的流程示意图;
图3是本申请实施例提供的一种服务器的结构示意图。
为了使本申请的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本申请进行进一步详细说明。在本申请的描述中,术语“第一”、“第二”等仅用于区分描述,而不能理解为指示或暗示相对重要性。
为了说明本申请所述的技术方案,下面通过具体实施例来进行说明。
图1示出了本申请实施例提供的一种共享车辆的管理系统的结构示意图,该共享车辆的管理系统包括车主客户端11、租赁客户端12、服务器13以及若干作为区块链节点的区块链网络设备14,上述车主客户端11、租赁客户端12以及区块链网络设备14分别与上述服务器13相连接。买方客户端12用于向服务器13发送共享信息以及使用智能合约,所述使用智能合约中包括所述共享车辆的使用规则,所述共享信息包括共享车辆信息和所述共享车辆的车主的身份信息;租赁客户端12用于向服务器发送租赁请求,所述服务器13用于将接收的共享信息以及使用智能合约登记在区块链网络设备14中并全网广播,还用于根据租赁客户端12的租赁请求查找匹配的共享车辆,以供所述租赁客户端的客户在确定目标共享车辆后使用该目标共享车辆。上述区块链网络设备14用于接收服务器13发送的相关数据,并将其进行存储。进一步地,上述车主客户端11和租赁客户端12均可以是个人电脑、智能手机、平板电脑以及智能穿戴设备等智能终端中的一种。上述服务器13可以通过向区块链网络设备14发送信息进而由区块链网络设备将信息登记在区块链中全网广播,也可以登记在区块链中成为区块链的一个节点设备。
实施例1
图2示出了本申请实施例提供一种共享车辆的管理方法的实现流程示意图,上述共享车辆的管理方法包括步骤S21-步骤S26,详述如下:
步骤S21,接收车主客户端发送的共享信息以及使用智能合约。
本申请提供的实施例中服务器接收车主客户端发送来的共享信息以及使用智能合约,上述车主客户端用于接收共享车辆的车主输入的共享车辆的信息以及上述车主的身份信息,然后由车主客户端将上述共享车辆的信息和车主的身份信息发送给服务器。上述共享车辆的信息包括共享车辆的车牌号、车辆行驶证、车龄、发动机的运行状况、安全设备和电子设备的运行状态以及行车里程等信息。上述车主的身份信息包括车主的姓名、身份证号、联系方式等中的一种或多种。上述使用智能合约中规定了共享车辆的使用规则,包括使用该共享车辆时的计费规则,支付方式等信息。
步骤S22,将所述共享信息和所述使用智能合约登记在区块链网络中并全网广播。
服务器将接收到的上述共享信息和上述使用智能合约发送给区块链网络设备,由区块链网络设备登记在区块链中并全网广播,或者当服务器本身为区块链的一个节点设备时,服务器将接收到的上述共享信息和上述使用智能合约直接登记在区块链中并全网广播以使其他区块链网络设备也可获取到同样的信息,并指示上述其他区块链网络设备对接收到的信息进行存储。可选地,服务器在向上述区块链网络发送上述共享信息和上述使用智能合约时可以将上述共享信息和上述使用智能合约打包后再进行发送。
步骤S23,接收租赁客户端发送的租赁请求并登记在所述区块链网络中,所述租赁请求中包含发起租赁请求的用户的个人信息和租赁要求。
服务器等待接收租赁客户端发来的租赁请求,若接收到租赁请求则将上述租赁请求登记在区块链网络中;上述租赁请求中包含有发送租赁请求的用户的个人信息和租赁要求。个人信息包括个人身份标识和驾驶行为偏好等,租赁要求包括车型偏好、位置信息、费用预算等信息。
步骤S24,根据所述区块链中预存的信用智能合约和所述个人信息计算所述发起租赁请求的用户的用户等级。
服务器在接收到租赁请求后,根据租赁请求中的个人身份标识调取存储在区块链网络中具体用户信息如驾驶行为信息、交通违章信息、驾驶里程信息、使用共享车俩的交易信息等,根据上述具体用户信息对上述用户的用户等级进行计算,该用户等级包括用户信用等级以及驾驶等级,同时结合上述用户的租赁要求为其找到匹配的共享车辆。
具体的,可以根据用户的驾驶里程与该驾驶里程内的违规行为及违章信息的比率(例如1000公里的驾驶里程内对应的违规行为或违章行为次数)确定信用等级。比如,假设用户的基本信用等级为一般,用户信息显示其驾驶里程越长,且在驾驶里程中的行为无违规行为,没有交通违章信息,则可以确定该用户的信用等级为良好。若用户信息显示其驾驶里程较短,驾驶里程过程无违规行为,也没有交通违章;或者用户的驾驶里程与驾驶违规行为保持在一个较低的比率(例如1000公里的驾驶里程内对应的违规行为或违章行为次数在5次以内。),则可以认为该用户的信用等级一般。若用户信息显示其驾驶里程于该驾驶里程内的违规行为及违章信息的比率较高(例如1000公里的驾驶里程内对应的违规行为或违章行为次数超过10次。),则认为该用户的信用等级较差。
具体的,可以根据驾驶里程和驾驶行为信息确定用户的驾驶等级。驾驶里程越长,对应的驾驶行为信息中的驾驶违规次数越少,则该用户的驾驶等级越高。
步骤S25,根据所述用户等级和所述租赁要求查找匹配的共享车辆。
根据上述计算得到的用户等级(信用等级和驾驶等级)可以用于确定匹配该用户的共享车辆的范围,包括收费范围、车型范围等,再结合用户的租赁要求如车型偏好、位置信息、费用预算等确定匹配的共享车辆,从而为用户提供匹配的共享车辆信息。
步骤S26,将所述匹配的共享车辆发送至租赁客户端,以使所述租赁客户端确定目标共享车辆。
步骤S27,释放所述目标共享车辆的使用权给所述租赁客户端。
根据对发起租赁请求的用户的用户等级的计算在共享车辆中为其查找合适的共享车辆,并将查找到的目标共享车辆的信息发送到上述租赁客户端,以供上述用户选择。若接收到租赁客户端发送的用户对目标共享车辆的选择信息,则将该目标共享车辆的使用权释放给该用户。具体的,将目标共享车辆的使用权释放给该用户的具体方式可以为直接控制共享车辆的车门开启以及使发动机处于可使用状态,也可以是将车辆的控制口令发送至租赁客户端,由用户根据控制口令开启车门并启动发动机,进而获得该共享车辆的使用权。
需要说明的是,上述数据是以区块的形式存储在区块链网络中的。每个区块包含两个部分,区块头和区块体,区块头用来记录当前区块的特征值,区块体为实际数据。区块头包括了当前区块的多项特征值。所述多项特征值包括:生成时间、区块体的哈希值和上一个区块的哈希值。区块的哈希值是针对区块头计算的。也就是说,把区块头的各项特征值,按照顺序连接在一起,组成一个很长的字符串,再对这个字符串计算哈希值,因此每个区块的哈希值都是不一样的,可以通过哈希标识区块。
由于区块头包含很多内容,其中有当前区块体的哈希,还有上一个区块的哈希。由于区块链的共识机制,短时间内修改多个区块几乎不可能发生,除非有人掌握了全网51%以上的计算能力。由此形成了区块链的去中心化和不可篡改的特点。
因此,在本申请实施例中,利用区块链中的数据具有去中心化和不可篡改的特性,将车辆租赁过程中所产生的使用数据和交易数据等信息均发送到区块链的节点设备进行存储,保证车主能够获得真实的车辆使用数据和交易数据,从而使其可以放心的将车辆共享给用户终端等服务平台。
另外,所述智能合约是一段能够自动执行合约条款的计算机执行程序。它不产生智能合约,也不会修改智能合约;它的存在只是为了让一组复杂的、带有触发条件的数字化承诺能够按照参与者的意志,正确执行。因此,智能合约部署在区块链上后,即等待被调用,无法被改变。
所述区块链上一般部署有较多的智能合约,智能合约带有标识,用于标志智能合约的作用,可选地,所述智能合约的标识可以为所述智能合约的名称,用于唯一标识所述区块链上部署的智能合约。因此,用户终端向区块链发送的信息可以携带不同的智能合约的标识,以使得区块链网络接收到携带所述智能合约标识信息的相关数据后,可以调用相应的智能合约执行相应的程序。
可选地,在本申请提供的另一实施例中,在所述接收车主客户端发送的共享信息以及使用智能合约之前包括:
发布共享车辆的服务协议,所述服务协议用于指导共享车辆的车主提交共享信息以及使用智能合约;
将所述服务协议和服务智能合约登记在区块链网络中,所述服务智能合约根据所述服务协议生成。
该步骤中,为了鼓励更多的车主共享其拥有所有权的车辆,服务器会预先发布共享车辆的服务协议,以指导车主根据服务协议提交共享信息以及使用智能合约。例如上述服务协议中可以规定共享车辆的基本要求(如车辆的车龄、行车路程等)、对车主认证的要求(如车主要提供哪些信息才能对其身份进行认证)等。可选地,服务器还可为通过认证的车主的共享车辆安装车载终端,此时上述服务协议中还可以包括安装车载终端的请求方式以及安装车载终端的收费规则等情况。另外,上述服务协议还用于告知车主共享车辆的行车数据均会被登记到区块链网络中。服务器发布上述服务协议,并根据上述服务协议指定服务智能合约,以方便后续对车主发送的共享信息的审核。服务器将发布的服务协议以及服务智能合约均登记在区块链网络中。
可选地,在本申请提供的另一实施例中,所述共享信息包括车主身份信息,在所述接收车主客户端发送的共享信息以及使用智能合约之后,所述方法还包括:
根据所述车主身份信息对所述车主进行身份认证;
若认证通过,则根据所述使用智能合约向所述车主的共享车辆分配车载终端和车载终端标识;
根据所述车载终端标识将所述车载终端作为区块链网络的一个节点登记在区块链网络中。
本申请实施例中为了确保共享车辆的安全,对车主的身份进行认证,例如可以通过共享车辆的车辆行驶证中的信息确定发送者共享信息者与该共享车辆的所有关系,上述车辆行驶证中的信息包含在车主客户端发送的共享信息中。若发送者(车主)的身份通过认证,则向该共享车辆分配车载终端和车载终端标识,上述车载终端用于记录并向用户终端发送车辆被使用过程中的使用数据;上述车载终端标识用于对用户终端所分配的不同共享车辆上的车载终端进行唯一标识;将所述车载终端作为所述区块链的节点设备的一个节点记录在区块链中,以便将共享车辆使用过程中产生的使用数据及时上传到区块链中。
可选地,在本申请提供的另一实施例中,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,包括:
接收所述目标共享车辆在被使用过程中产生的使用数据,所述使用数据由所述车载终端提交;
将所述使用数据登记在所述区块链网络中。
本申请提供的实施例中,若服务器向租赁客户端释放了目标共享车辆的使用权,则通过上述车载终端实时监测上述目标共享车辆使用过程中产生的使用数据,上述的使用数可以为用户驾驶上述目标共享车辆过程中产生的数据,包括:目标共享车辆使用时长、行驶轨迹、驾驶行为(如急转弯)、变道等数据、使用过程中的目标共享车辆的工况数据(如车速、加速度、发动机数据流、变速箱数据流)等。车载终端将采集到的使用数据发送给服务器。若服务器接收到目标共享车辆的使用数据,则将上述使用数据发送至区块链网络中进行存储。
可选地,在本申请提供的另一实施例中,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述方法还包括:
当接收到所述租赁客户端发送租赁结束请求时,将所述使用数据进行分类;根据分类属性确定分类数据的所有权;
将分类数据发送至对应的所有权方。
本申请提供的实施例中,若上述用户结束对上述目标共享车辆的租赁,服务器基于实时上传的使用数据,根据用户的结束指令确定此次使用过程中的使用数据,并将使用数据按照属性进行分类,例如将目标共享车辆使用时长、行驶轨迹、驾驶行为数据等确定为驾驶数据;将车辆的车速、加速度数据、发动机数据、变速箱数据等确定为车况数据。并根据使用数据的分类属性确定分类数据的所有权,比如确定驾驶数据的所有权属于发起租赁请求的用户,确定车况数据的所有权属于车主。确定所有权后,将分类数据发送给对应的所有权方,同时进行所有权标记。例如将驾驶数据发送给用户,将车况数据发送给车主,并通过打标记或者添加水印的方式进行所有权标记。
可选地,在本申请提供的另一实施例中,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述方法还包括:
当接收到所述租赁客户端发送租赁结束请求时,调用所述使用智能合约向所述租赁客户端发起支付交易请求;
在接收到所述租赁客户端的支付交易确认信息后,调用服务智能合约根据所述支付交易产生的收益生成分配方案;
按照所述分配方案进行分成。
在该实施例中,当发起租赁请求的用户结束对上述目标共享车辆的租赁使用时,服务器调用该共享车辆的使用智能合约向租赁客户端发起支付交易请求,包括提供此次行程清单及收费明细,以供该用户根据行程清单及收费明细完成支付交易。在用户完成交易支付后,租赁客户端会向服务器发送一个支付交易的确认信息。此时,服务器会调用服务智能合约根据支付的金额形成一个分配方案,并根据分配方案在各相关方分配收益。由于服务器的运营方在交易过程中也提供了相应的服务,因此分配方案主要在车主和运营方之间分配。比如车主分配支付金额的90%,服务器的运营方分配支付金额的10%。然后根据该分配方案将支付金额的相应部分转账至车主和运营方对应的账户。此处仅是列举,还可以有其他多种分配方案,这里不做具体限定。若此次租赁过程中产生违章罚款等事项,根据服务智能合约对违章罚款等事项做单后处理,例如向上述用户收取违章罚款费等处理。
本申请提供的实施例中通过将接收到的车主客户端发送的共享信息以及租赁客户端发送的用户的个人信息和租赁请求等信息均登记在区块链网络中,从而保证了共享车辆的车主能够及时获取到用户的真实信息,并了解到自己共享的车辆在每个时间段内的出租以及被使用情况,从而使车主能够放心的将自己的车辆分享给各个共享车辆的服务平台,提高车主共享车辆的积极性,也提升车辆的共享使用效率。
实施例2
图3是本申请实施例提供的服务器的结构示意图。该实施例的服务器3包括:处理器30、存储器31以及存储在所述存储器31中并可在所述处理器30上运行的计算机程序32,例如共享车辆的管理方法中的程序。所述处理器30执行所述计算机程序32时实现上述各个共享车辆的管理方法实施例中的步骤,例如图2所示的步骤S21至S26,所述处理器30执行所述计算机程序32时实现图2所示的步骤S21至S26。
所述服务器可包括,但不仅限于,处理器30、存储器31。本领域技术人员可以理解,图3仅仅是终端设备3的示例,并不构成对服务器3的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件,例如所述服务器3还可以包括输入输出设备、网络接入设备、总线等。
所称处理器30可以是中央处理单元(Central
Processing Unit,CPU),还可以是其他通用处理器、数字信号处理器 (Digital Signal Processor,DSP)、专用集成电路 (Application
Specific Integrated Circuit,ASIC)、现场可编程门阵列 (Field-Programmable Gate Array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
所述存储器31可以是所述服务器3的内部存储单元,例如服务器3的硬盘或内存。所述存储器31也可以是所述服务器3的外部存储设备,例如所述服务器3上配备的插接式硬盘,智能存储卡(Smart Media Card,SMC),安全数字(Secure Digital,SD)卡,闪存卡(Flash Card)等。进一步地,所述存储器31还可以既包括所述服务器3的内部存储单元也包括外部存储设备。所述存储器31用于存储所述计算机程序以及所述保险承保所需的其他程序和数据。所述存储器31还可以用于暂时地存储已经输出或者将要输出的数据。
示例性的,所述服务器进行二手车交易时,所述处理器30执行存储在存储器31计算机程序32包括:
接收车主客户端发送的共享信息以及使用智能合约;
将所述共享信息和所述使用智能合约登记在区块链网络中并全网广播;
接收租赁客户端发送的租赁请求并登记在所述区块链网络中,所述租赁请求中包含发起租赁请求的用户的个人信息和租赁要求;
根据所述区块链中预存的信用智能合约和所述个人信息计算所述发起租赁请求的用户的用户等级;
根据所述用户等级和所述租赁要求查找匹配的共享车辆;
将所述匹配的共享车辆发送至租赁客户端,以使所述租赁客户端确定目标共享车辆;
释放所述目标共享车辆的使用权给所述租赁客户端。
可选地,在所述接收车主客户端发送的共享信息以及使用智能合约之前,所述处理器调用所述存储器中的可执行计算机程序,还用于:
发布共享车辆的服务协议,所述服务协议用于指导共享车辆的车主提交共享信息以及使用智能合约;
将所述服务协议和服务智能合约登记在区块链网络中,所述服务智能合约根据所述服务协议生成。
可选地,在所述接收车主客户端发送的共享信息以及使用智能合约之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:
根据所述车主身份信息对所述车主进行身份认证;
若认证通过,则根据所述使用智能合约向所述车主的共享车辆分配车载终端和车载终端标识;
根据所述车载终端标识将所述车载终端作为区块链网络的一个节点登记在区块链网络中。
可选地,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:
接收所述目标共享车辆在被使用过程中产生的使用数据,所述使用数据由所述车载终端提交;
将所述使用数据登记在所述区块链网络中。
可选地,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:
当接收到所述租赁客户端发送租赁结束请求时,将所述使用数据进行分类;根据分类属性确定分类数据的所有权;
将分类数据发送至对应的所有权方。
可选地,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:
当接收到所述租赁客户端发送租赁结束请求时,调用所述使用智能合约向所述租赁客户端发起支付交易请求;
在接收到所述租赁客户端的支付交易确认信息后,调用服务智能合约根据所述支付交易产生的收益生成分配方案;
按照所述分配方案进行分成。
示例性的,上述计算机程序32可以被分割成一个或多个单元/模块,上述一个或者多个单元/模块被存储在上述存储器31中,并由上述处理器30执行,以完成本申请。
上述服务器3可以是云端服务器,智能设备,计算机、笔记本及掌上电脑等计算设备。上述服务器3可包括,但不仅限于,处理器30、存储器31。本领域技术人员可以理解,图3仅仅是服务器3的示例,并不构成对服务器3的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件,例如上述服务器3还可以包括输入输出设备、网络接入设备、总线等。
所称处理器30可以是中央处理单元(Central
Processing Unit,CPU),还可以是其它通用处理器、数字信号处理器 (Digital Signal Processor,DSP)、专用集成电路 (Application
Specific Integrated Circuit,ASIC)、现成可编程门阵列 (Field-Programmable Gate Array,FPGA) 或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
上述存储器31可以是服务器3的内部存储单元,例如服务器3的硬盘或内存。上述存储器31也可以是上述服务器3的外部存储设备,例如上述服务器3上配备的插接式硬盘,智能存储卡(Smart Media Card, SMC),安全数字(Secure Digital, SD)卡,闪存卡(Flash
Card)等。进一步地,上述存储器31还可以既包括上述服务器3的内部存储单元也包括外部存储设备。上述存储器31用于存储上述计算机程序以及上述服务器3所需的其它程序和数据。上述存储器31还可以用于暂时地存储已经输出或者将要输出的数据。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、数据管理服务器和方法,可以通过其它的方式实现。所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
实施例3
本申请中上述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access
Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
所述计算机可读存储介质存储有计算机程序,所述计算机程序被处理器执行时实现如下步骤:
接收车主客户端发送的共享信息以及使用智能合约;
将所述共享信息和所述使用智能合约登记在区块链网络中并全网广播;
接收租赁客户端发送的租赁请求并登记在所述区块链网络中,所述租赁请求中包含发起租赁请求的用户的个人信息和租赁要求;
根据所述区块链中预存的信用智能合约和所述个人信息计算所述发起租赁请求的用户的用户等级;
根据所述用户等级和所述租赁要求查找匹配的共享车辆;
将所述匹配的共享车辆发送至租赁客户端,以使所述租赁客户端确定目标共享车辆;
释放所述目标共享车辆的使用权给所述租赁客户端。
以上仅为本申请的较佳实施例而已,并不用以限制本申请,凡在本申请的精神和原则之内所作的任何修改、等同替换和改进等,均应包含在本申请的保护范围之内。
Claims (13)
- 一种共享车辆的管理方法,其特征在于,所述共享车辆的管理方法包括:接收车主客户端发送的共享信息以及使用智能合约;将所述共享信息和所述使用智能合约登记在区块链网络中并全网广播;接收租赁客户端发送的租赁请求并登记在所述区块链网络中,所述租赁请求中包含发起租赁请求的用户的个人信息和租赁要求;根据所述区块链中预存的信用智能合约和所述个人信息计算所述发起租赁请求的用户的用户等级;根据所述用户等级和所述租赁要求查找匹配的共享车辆;将所述匹配的共享车辆发送至租赁客户端,以使所述租赁客户端确定目标共享车辆;释放所述目标共享车辆的使用权给所述租赁客户端。
- 如权利要求1所述的共享车辆的管理方法,其特征在于,在所述接收车主客户端发送的共享信息以及使用智能合约之前,所述方法包括:发布共享车辆的服务协议,所述服务协议用于指导共享车辆的车主提交共享信息以及使用智能合约;将所述服务协议和服务智能合约登记在区块链网络中,所述服务智能合约根据所述服务协议生成。
- 如权利要求1所述的共享车辆的管理方法,其特征在于,所述共享信息包括车主身份信息,在所述接收车主客户端发送的共享信息以及使用智能合约之后,所述方法还包括:根据所述车主身份信息对所述车主进行身份认证;若认证通过,则根据所述使用智能合约向所述车主的共享车辆分配车载终端和车载终端标识;根据所述车载终端标识将所述车载终端作为区块链网络的一个节点登记在区块链网络中。
- 如权利要求3所述的共享车辆的管理方法,其特征在于,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述方法包括:接收所述目标共享车辆在被使用过程中产生的使用数据,所述使用数据由所述车载终端提交;将所述使用数据登记在所述区块链网络中。
- 如权利要求4所述的方法,其特征在于,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述方法还包括:当接收到所述租赁客户端发送租赁结束请求时,将所述使用数据进行分类;根据分类属性确定分类数据的所有权;将分类数据发送至对应的所有权方。
- 如权利要求1-5任一项所述的共享车辆的管理方法,其特征在于,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述方法还包括:当接收到所述租赁客户端发送租赁结束请求时,调用所述使用智能合约向所述租赁客户端发起支付交易请求;在接收到所述租赁客户端的支付交易确认信息后,调用服务智能合约根据所述支付交易产生的收益生成分配方案;按照所述分配方案进行分成。
- 一种服务器,其特征在于,所述服务器包括:存储有可执行计算机程序的存储器;与所述存储器耦合的处理器,所述处理器调用所述存储器中的可执行计算机程序,用于:接收车主客户端发送的共享信息以及使用智能合约;将所述共享信息和所述使用智能合约登记在区块链网络中并全网广播;接收租赁客户端发送的租赁请求并登记在所述区块链网络中,所述租赁请求中包含发起租赁请求的用户的个人信息和租赁要求;根据所述区块链中预存的信用智能合约和所述个人信息计算所述发起租赁请求的用户的用户等级;根据所述用户等级和所述租赁要求查找匹配的共享车辆;将所述匹配的共享车辆发送至租赁客户端,以使所述租赁客户端确定目标共享车辆;释放所述目标共享车辆的使用权给所述租赁客户端。
- 如权利要求7所述的服务器,其特征在于,在所述接收车主客户端发送的共享信息以及使用智能合约之前,所述处理器调用所述存储器中的可执行计算机程序,还用于:发布共享车辆的服务协议,所述服务协议用于指导共享车辆的车主提交共享信息以及使用智能合约;将所述服务协议和服务智能合约登记在区块链网络中,所述服务智能合约根据所述服务协议生成。
- 如权利要求7所述的服务器,其特征在于,在所述接收车主客户端发送的共享信息以及使用智能合约之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:根据所述车主身份信息对所述车主进行身份认证;若认证通过,则根据所述使用智能合约向所述车主的共享车辆分配车载终端和车载终端标识;根据所述车载终端标识将所述车载终端作为区块链网络的一个节点登记在区块链网络中。
- 如权利要求9所述的服务器,其特征在于,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:接收所述目标共享车辆在被使用过程中产生的使用数据,所述使用数据由所述车载终端提交;将所述使用数据登记在所述区块链网络中。
- 如权利要求10所述的服务器,其特征在于,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:当接收到所述租赁客户端发送租赁结束请求时,将所述使用数据进行分类;根据分类属性确定分类数据的所有权;将分类数据发送至对应的所有权方。
- 如权利要求7-11任一项所述的服务器,其特征在于,在所述释放所述目标共享车辆的使用权给所述租赁客户端之后,所述处理器调用所述存储器中的可执行计算机程序,还用于:当接收到所述租赁客户端发送租赁结束请求时,调用所述使用智能合约向所述租赁客户端发起支付交易请求;在接收到所述租赁客户端的支付交易确认信息后,调用服务智能合约根据所述支付交易产生的收益生成分配方案;按照所述分配方案进行分成。
- 一种计算机可读存储介质,所述计算机可读存储介质存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现如权利要求1至6任一项所述方法的步骤。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/061,334 US20200286162A1 (en) | 2018-05-31 | 2018-05-31 | Method and server for managing shared vehicles |
PCT/CN2018/089408 WO2019227451A1 (zh) | 2018-05-31 | 2018-05-31 | 一种共享车辆的管理方法和服务器 |
CN201880000487.XA CN108701324A (zh) | 2018-05-31 | 2018-05-31 | 一种共享车辆的管理方法和服务器 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2018/089408 WO2019227451A1 (zh) | 2018-05-31 | 2018-05-31 | 一种共享车辆的管理方法和服务器 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019227451A1 true WO2019227451A1 (zh) | 2019-12-05 |
Family
ID=63841499
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/089408 WO2019227451A1 (zh) | 2018-05-31 | 2018-05-31 | 一种共享车辆的管理方法和服务器 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20200286162A1 (zh) |
CN (1) | CN108701324A (zh) |
WO (1) | WO2019227451A1 (zh) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111061982A (zh) * | 2019-12-11 | 2020-04-24 | 电子科技大学 | 一种基于区块链的新闻资讯发布及管理系统 |
CN111127227A (zh) * | 2019-12-26 | 2020-05-08 | 深圳市元征科技股份有限公司 | 一种车辆定损方法、装置和相关设备 |
CN112101604A (zh) * | 2020-09-15 | 2020-12-18 | 广东安居宝数码科技股份有限公司 | 一种基于区块链的停车管理系统 |
EP3866082A1 (en) * | 2020-02-12 | 2021-08-18 | Mettler-Toledo (Changzhou) Precision Instruments Co., Ltd | Method and apparatus for leasing measurement device based on blockchain |
CN113283757A (zh) * | 2021-05-31 | 2021-08-20 | 上海旺链信息科技有限公司 | 一种基于区块链技术的汽车信息登记管理系统 |
CN114205109A (zh) * | 2021-09-30 | 2022-03-18 | 徐敏 | 一种车联网信息管理方法及芯片 |
CN114422578A (zh) * | 2021-10-21 | 2022-04-29 | 北京骑胜科技有限公司 | 共享车辆控制方法、装置、设备、可读存储介质及产品 |
WO2024045859A1 (zh) * | 2022-08-30 | 2024-03-07 | 广东美的制冷设备有限公司 | 共享设备的控制方法、设备、客户端、服务器及存储介质 |
Families Citing this family (58)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107437308B (zh) * | 2017-08-02 | 2022-01-18 | 京东方科技集团股份有限公司 | 共享物品的管理系统和方法、共享物品以及共享服务器 |
CN110009439A (zh) * | 2018-11-23 | 2019-07-12 | 阿里巴巴集团控股有限公司 | 一种基于区块链的出租车营运方法和装置 |
CN109472675A (zh) * | 2018-11-29 | 2019-03-15 | 阿里巴巴集团控股有限公司 | 租赁业务的处理方法、装置、系统及设备 |
CN109934662B (zh) * | 2018-11-30 | 2020-10-30 | 创新先进技术有限公司 | 基于区块链的共享资源租赁方法、装置和计算机设备 |
CN109615475A (zh) * | 2018-12-12 | 2019-04-12 | 睿驰达新能源汽车科技(北京)有限公司 | 一种车辆租赁业务服务的提供方法、装置、设备和介质 |
CN111355754B (zh) * | 2018-12-21 | 2023-06-27 | 西安佰才邦网络技术有限公司 | 一种基于区块链购买业务的方法及设备 |
CN109903151A (zh) * | 2019-01-21 | 2019-06-18 | 苏宁易购集团股份有限公司 | 基于区块链技术的抵押车电子围栏实现方法及系统 |
CN110311941B (zh) * | 2019-01-31 | 2022-05-10 | 林德(中国)叉车有限公司 | 一种基于边缘计算的工业车辆链构建方法及数据同步方法 |
CN110009388A (zh) * | 2019-02-02 | 2019-07-12 | 阿里巴巴集团控股有限公司 | 设备租赁方法、装置、设备及存储介质 |
CN110009441B (zh) * | 2019-02-02 | 2021-05-28 | 创新先进技术有限公司 | 基于区块链的租赁信息处理方法、装置和设备 |
US11568006B1 (en) * | 2019-02-12 | 2023-01-31 | State Farm Mutual Automobile Insurance Company | Systems and methods for electronically matching online user profiles |
CN109948813B (zh) * | 2019-02-28 | 2021-06-11 | 深圳市轱辘车联数据技术有限公司 | 一种基于区块链的维修设备共享的方法、装置及服务器 |
CN111695961A (zh) * | 2019-03-13 | 2020-09-22 | 阿里巴巴集团控股有限公司 | 共享设备管理方法、装置、系统以及计算装置和存储介质 |
CN110135803B (zh) * | 2019-04-29 | 2023-12-08 | 深圳市元征科技股份有限公司 | 一种事项管理方法及区块链节点设备 |
CN110148036A (zh) * | 2019-04-30 | 2019-08-20 | 深圳市轱辘汽车维修技术有限公司 | 一种随车资源共享方法及终端 |
CN111986389A (zh) * | 2019-05-22 | 2020-11-24 | 上海博泰悦臻网络技术服务有限公司 | 车辆托管方法及系统 |
CN112039935B (zh) * | 2019-06-04 | 2022-12-20 | 上海博泰悦臻网络技术服务有限公司 | 一种动态车队驾驶共享控制方法、服务端、客户端及数据平台 |
US20200402149A1 (en) * | 2019-06-18 | 2020-12-24 | Toyota Motor North America, Inc. | Identifying changes in the condition of a transport |
US11227490B2 (en) | 2019-06-18 | 2022-01-18 | Toyota Motor North America, Inc. | Identifying changes in the condition of a transport |
US11481836B2 (en) * | 2019-06-19 | 2022-10-25 | Toyota Motor North America, Inc. | Transport sharing and ownership among multiple entities |
CN110363314A (zh) * | 2019-06-28 | 2019-10-22 | 深圳市轱辘汽车维修技术有限公司 | 一种共享检测设备的方法、装置、移动终端及服务器 |
US11720120B2 (en) | 2019-08-08 | 2023-08-08 | Toyota Motor North America, Inc. | Tracking of transport transfers |
US11488094B2 (en) | 2019-08-08 | 2022-11-01 | Toyota Motor North America, Inc. | Tracking of transport transfers |
CN112417922B (zh) * | 2019-08-20 | 2024-06-28 | 杭州海康威视数字技术股份有限公司 | 目标识别方法和装置 |
JP7223665B2 (ja) * | 2019-08-28 | 2023-02-16 | 本田技研工業株式会社 | 行動計画生成装置、行動計画生成方法、及びプログラム |
CN110689237B (zh) * | 2019-09-09 | 2023-08-18 | 深圳市元征科技股份有限公司 | 一种车辆管理人员的管理方法及其相关产品 |
CN110599697A (zh) * | 2019-09-12 | 2019-12-20 | 腾讯科技(深圳)有限公司 | 基于区块链的车辆共享方法、装置、设备及存储介质 |
CN110503781A (zh) * | 2019-09-19 | 2019-11-26 | 腾讯科技(深圳)有限公司 | 基于区块链的车辆租赁业务数据处理方法和装置 |
US11082283B2 (en) | 2019-09-23 | 2021-08-03 | International Business Machines Corporation | Contextual generation of ephemeral networks |
CN110852851B (zh) * | 2019-11-14 | 2024-06-18 | 腾讯科技(深圳)有限公司 | 基于区块链的交通工具共享方法、装置及可读存储介质 |
CN111049800A (zh) * | 2019-11-14 | 2020-04-21 | 深圳市朗仁科技有限公司 | 车辆服务管理方法、装置、区块链节点设备及其存储介质 |
CN110969771A (zh) * | 2019-11-27 | 2020-04-07 | 深圳市朗仁科技有限公司 | 车辆管理方法、装置、车载终端及其存储介质 |
CN111091216A (zh) * | 2019-12-13 | 2020-05-01 | 贾自超 | 一种网约智能交通工具的方法及服务器 |
CN111275418A (zh) * | 2020-01-16 | 2020-06-12 | 深圳市元征科技股份有限公司 | 租车管理方法及相关设备 |
CN113254947B (zh) * | 2020-02-13 | 2023-04-14 | 宁波吉利汽车研究开发有限公司 | 一种车辆数据保护方法、系统、设备和存储介质 |
CN111429224A (zh) * | 2020-03-26 | 2020-07-17 | 上海云会贸易有限公司 | 一种分享管理系统 |
CN111639836B (zh) * | 2020-04-29 | 2024-04-02 | 亚美智联数据科技有限公司 | 基于区块链的车辆调度处理方法、装置和计算机设备 |
CN111507811A (zh) * | 2020-06-14 | 2020-08-07 | 支付宝(杭州)信息技术有限公司 | 基于区块链的租赁处理方法、装置、设备及系统 |
CN111754100A (zh) * | 2020-06-19 | 2020-10-09 | 上海新共赢信息科技有限公司 | 共享车辆资源分配方法和系统 |
CN111970322B (zh) * | 2020-07-01 | 2023-04-28 | 佛山科学技术学院 | 一种基于区块链的无人驾驶汽车出行方法及系统 |
CN112164245A (zh) * | 2020-10-12 | 2021-01-01 | 河南耀辉实业有限公司 | 车位销售与车位共享系统 |
CN112232922A (zh) * | 2020-10-28 | 2021-01-15 | 昆明理工大学 | 基于区块链的工业设备产品租赁系统及方法 |
CN112583913A (zh) * | 2020-12-10 | 2021-03-30 | 支付宝(杭州)信息技术有限公司 | 基于区块链的车辆租赁处理方法及装置 |
CN115907750A (zh) * | 2020-12-12 | 2023-04-04 | 深圳市一聪微付科技有限公司 | 一种基于短距离通信支付的方法及装置 |
CN114666328B (zh) * | 2020-12-23 | 2024-07-16 | 京东科技信息技术有限公司 | 区块链的组建方法和装置、以及设备租赁方法和装置 |
CN112883411A (zh) * | 2020-12-29 | 2021-06-01 | 杭州趣链科技有限公司 | 基于区块链的数据处理方法、系统、电子设备及存储介质 |
CN112819277A (zh) * | 2020-12-31 | 2021-05-18 | 深圳市元征科技股份有限公司 | 车辆使用管理方法、装置、电子设备及存储介质 |
CN112991583A (zh) * | 2021-02-01 | 2021-06-18 | 上海钧正网络科技有限公司 | 一种车辆权限数据处理系统和方法 |
CN113763121A (zh) * | 2021-08-05 | 2021-12-07 | 深圳市星砺达科技有限公司 | 车辆租赁系统和方法 |
CN113674483A (zh) * | 2021-08-25 | 2021-11-19 | 安徽高山科技有限公司 | 一种基于区块链的汽车租赁方法 |
CN115854478A (zh) * | 2021-09-23 | 2023-03-28 | 佛山市顺德区美的电子科技有限公司 | 基于共享传感器的数据控制空调的方法、装置和存储介质 |
CN113888000A (zh) * | 2021-10-18 | 2022-01-04 | 支付宝(杭州)信息技术有限公司 | 一种共享单车的调度方法及装置 |
WO2023080012A1 (ja) * | 2021-11-08 | 2023-05-11 | ソニーグループ株式会社 | 情報処理装置、および情報処理方法、並びにプログラム |
CN115086394A (zh) * | 2022-06-15 | 2022-09-20 | 亚信科技(中国)有限公司 | 业务信息处理方法、装置及电子设备 |
CN115086065B (zh) * | 2022-07-12 | 2024-01-19 | 北斗星通智联科技有限责任公司 | 一种基于区块链的数据同步方法、装置、电子设备及介质 |
CN115545829B (zh) * | 2022-09-29 | 2024-05-31 | 中航信移动科技有限公司 | 一种服务器标识的勾选显示系统、电子设备及存储介质 |
CN116152967A (zh) * | 2023-04-17 | 2023-05-23 | 成都赛力斯科技有限公司 | 一种车辆远程分享方法、装置、系统和电子设备 |
CN117408789A (zh) * | 2023-12-14 | 2024-01-16 | 北京新能源汽车股份有限公司 | 自动驾驶汽车的共享装置、汽车、方法及服务器 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104794640A (zh) * | 2015-05-04 | 2015-07-22 | 常州永安公共自行车系统股份有限公司 | 基于云服务器端的车辆管理方法及其云服务器 |
CN107563846A (zh) * | 2017-08-10 | 2018-01-09 | 深圳市易成自动驾驶技术有限公司 | 共享车辆管理方法、服务器、系统和计算机可读存储介质 |
US20180097883A1 (en) * | 2016-09-30 | 2018-04-05 | The Toronto-Dominion Bank | Automated implementation of provisioned services based on captured sensor data |
CN108009878A (zh) * | 2017-11-24 | 2018-05-08 | 深圳市轱辘车联数据技术有限公司 | 一种信息处理方法及其装置 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2011057217A2 (en) * | 2009-11-06 | 2011-05-12 | University Of Utah Research Foundation | Method for gathering, processing, and analyzing data to determine crash risk associated with driving behavior |
CN107341700A (zh) * | 2017-01-20 | 2017-11-10 | 麦特汽车服务股份有限公司 | 优化的预约租车方法及一种智能租车装置 |
CN107424044A (zh) * | 2017-06-23 | 2017-12-01 | 深圳市盛路物联通讯技术有限公司 | 一种车辆租赁方法及装置 |
CN107169584A (zh) * | 2017-07-14 | 2017-09-15 | 北京途歌科技有限公司 | 共享汽车的用车方法和系统 |
CN107741995A (zh) * | 2017-11-17 | 2018-02-27 | 郑州云海信息技术有限公司 | 一种基于云计算的共享单车推荐方法及系统 |
-
2018
- 2018-05-31 US US16/061,334 patent/US20200286162A1/en not_active Abandoned
- 2018-05-31 WO PCT/CN2018/089408 patent/WO2019227451A1/zh active Application Filing
- 2018-05-31 CN CN201880000487.XA patent/CN108701324A/zh active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104794640A (zh) * | 2015-05-04 | 2015-07-22 | 常州永安公共自行车系统股份有限公司 | 基于云服务器端的车辆管理方法及其云服务器 |
US20180097883A1 (en) * | 2016-09-30 | 2018-04-05 | The Toronto-Dominion Bank | Automated implementation of provisioned services based on captured sensor data |
CN107563846A (zh) * | 2017-08-10 | 2018-01-09 | 深圳市易成自动驾驶技术有限公司 | 共享车辆管理方法、服务器、系统和计算机可读存储介质 |
CN108009878A (zh) * | 2017-11-24 | 2018-05-08 | 深圳市轱辘车联数据技术有限公司 | 一种信息处理方法及其装置 |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111061982A (zh) * | 2019-12-11 | 2020-04-24 | 电子科技大学 | 一种基于区块链的新闻资讯发布及管理系统 |
CN111061982B (zh) * | 2019-12-11 | 2023-04-18 | 电子科技大学 | 一种基于区块链的新闻资讯发布及管理系统 |
CN111127227A (zh) * | 2019-12-26 | 2020-05-08 | 深圳市元征科技股份有限公司 | 一种车辆定损方法、装置和相关设备 |
EP3866082A1 (en) * | 2020-02-12 | 2021-08-18 | Mettler-Toledo (Changzhou) Precision Instruments Co., Ltd | Method and apparatus for leasing measurement device based on blockchain |
CN112101604A (zh) * | 2020-09-15 | 2020-12-18 | 广东安居宝数码科技股份有限公司 | 一种基于区块链的停车管理系统 |
CN112101604B (zh) * | 2020-09-15 | 2024-01-23 | 广东安居宝数码科技股份有限公司 | 一种基于区块链的停车管理系统 |
CN113283757A (zh) * | 2021-05-31 | 2021-08-20 | 上海旺链信息科技有限公司 | 一种基于区块链技术的汽车信息登记管理系统 |
CN114205109A (zh) * | 2021-09-30 | 2022-03-18 | 徐敏 | 一种车联网信息管理方法及芯片 |
CN114422578A (zh) * | 2021-10-21 | 2022-04-29 | 北京骑胜科技有限公司 | 共享车辆控制方法、装置、设备、可读存储介质及产品 |
WO2024045859A1 (zh) * | 2022-08-30 | 2024-03-07 | 广东美的制冷设备有限公司 | 共享设备的控制方法、设备、客户端、服务器及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
US20200286162A1 (en) | 2020-09-10 |
CN108701324A (zh) | 2018-10-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019227451A1 (zh) | 一种共享车辆的管理方法和服务器 | |
WO2019227449A1 (zh) | 一种二手车交易方法及服务器 | |
WO2018068682A1 (zh) | 一种智能汽车支付系统以及支付方法 | |
WO2018121370A1 (zh) | T-box、基于t-box的车载支付系统及其方法 | |
WO2019227345A1 (zh) | 维修厂的管理方法、系统及数据管理服务器 | |
WO2019153447A1 (zh) | 快递盒传送方法、装置、终端设备及存储介质 | |
WO2020103565A1 (zh) | 一种基于区块链的出租车营运方法和装置 | |
US20230044261A1 (en) | Wireless energy transfer to transport based on route data | |
JP2023532179A (ja) | 要望に基づくエネルギー共有 | |
US20220281340A1 (en) | Battery preservation amid transport disuse | |
US20240025293A1 (en) | Transport battery health | |
WO2019232676A1 (zh) | 一种设备提醒方法、设备提醒装置及移动终端 | |
US20240073037A1 (en) | Internal certificate authority for electronic control unit | |
US20230276482A1 (en) | Resource selection for 5g nr v2x communications | |
US20230322107A1 (en) | Decentralized charging locations | |
US20230226941A1 (en) | Electric transport charging determination | |
US20230219446A1 (en) | Power distribution based on mobile data | |
US20230202336A1 (en) | Power allocation based on energy source | |
US11987144B2 (en) | Transport energy transfer using real-time cost information | |
CN108416933A (zh) | 共享单车的使用方法、系统及计算机可读存储介质 | |
CN110717752B (zh) | 电子资源处理方法、装置、服务器及可读存储介质 | |
US20230419234A1 (en) | Ev battery degradation in a fleet | |
US12000706B2 (en) | Vehicle carbon footprint management | |
US20230276409A1 (en) | Resource selection for 5g nr v2x pc5 mode 2 | |
US20230004905A1 (en) | Energy offset benefits |
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: 18920370 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: 18920370 Country of ref document: EP Kind code of ref document: A1 |