WO2019148683A1 - 一种车辆共享方法及服务器 - Google Patents

一种车辆共享方法及服务器 Download PDF

Info

Publication number
WO2019148683A1
WO2019148683A1 PCT/CN2018/085874 CN2018085874W WO2019148683A1 WO 2019148683 A1 WO2019148683 A1 WO 2019148683A1 CN 2018085874 W CN2018085874 W CN 2018085874W WO 2019148683 A1 WO2019148683 A1 WO 2019148683A1
Authority
WO
WIPO (PCT)
Prior art keywords
vehicle
occupant information
occupant
information
shared use
Prior art date
Application number
PCT/CN2018/085874
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
Application filed by 深圳市元征软件开发有限公司 filed Critical 深圳市元征软件开发有限公司
Publication of WO2019148683A1 publication Critical patent/WO2019148683A1/zh

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/0042—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for hiring of objects
    • G07F17/0057—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for hiring of objects for the hiring or rent of vehicles, e.g. cars, bicycles or wheelchairs
    • 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/12—Payment architectures specially adapted for electronic shopping systems
    • G06Q20/127—Shopping or accessing services according to a time-limitation
    • 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
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user

Definitions

  • the present invention relates to the field of vehicle technologies, and in particular, to a vehicle sharing method and a server.
  • the shared vehicle can only report the running condition of the vehicle, such as the driving route and the parking position, to the owner in real time through the in-vehicle device, and cannot properly monitor and standardize the behavior of the occupant in the vehicle. On the one hand, it can not solve the concern of the owner of the vehicle to rationally regulate the use of the vehicle. On the other hand, if the data in the vehicle is monitored in real time, there is a suspicion of infringing the privacy of the user, and a large amount of real-time data also brings trouble to the owner. Therefore, a new technology is needed to regulate the rational use of shared vehicles to solve the problems of vehicle owners' use of vehicles and user privacy protection in the prior art.
  • the embodiments of the present invention provide a vehicle sharing method and a server, which are beneficial to solving the problem of the vehicle owner's use of the vehicle and the privacy protection of the user in the prior art, and improve the convenience and efficiency of the vehicle sharing.
  • an embodiment of the present invention provides a vehicle sharing method, which is applied to a server, where the method includes: receiving a shared use protocol of a vehicle, where the shared use protocol includes a normative constraint of the occupant information in the vehicle; when the user is detected When the vehicle is used, the in-vehicle device that controls the vehicle collects in-vehicle occupant information; and determines whether the in-vehicle occupant information collected by the in-vehicle device meets the normative constraint of the in-vehicle occupant information in the shared use agreement; Transmitting, the vehicle owner terminal that does not meet the prompt information to the vehicle, and transferring the authority for controlling the in-vehicle information of the vehicle to the vehicle owner terminal; and controlling the non-conformity according to the in-vehicle passenger information The vehicle performs the corresponding operation.
  • the normative constraints of the in-vehicle occupant information include the number of people in the vehicle and the code of conduct, the driver The safe driving behavior specification; the in-vehicle device that controls the vehicle collects in-vehicle occupant information, including: controlling the in-vehicle device to acquire the number of in-vehicle occupants and/or occupant behavior, and/or controlling the in-vehicle device to acquire the driving behavior of the driver.
  • the normative constraint of the in-vehicle occupant information in the shared usage agreement includes: comparing whether the number of occupants in the vehicle matches the occupant size specification; determining whether the occupant behavior matches the behavior specification of the occupant in the vehicle Analyzing whether the driver's driving behavior matches the driver's safe driving behavior specification; if the result of any of the above is a mismatch, determining that the in-vehicle occupant information does not meet the in-vehicle occupant information specification Sexual constraints.
  • the controlling the vehicle to perform the corresponding operation according to the degree of non-compliance of the occupant information in the vehicle includes: When the degree of non-compliance is slight, the control vehicle sends a warning message; when the degree of non-compliance is medium, the vehicle is controlled to send a warning message and decelerate; when the degree of non-compliance is serious, the vehicle is decelerated and the engine is locked when driving to a safe area. deal with.
  • a second aspect of the present invention provides a server, the server comprising: a memory storing executable program code; a processor coupled to the memory; a transceiver coupled to the processor; the processor controlling transmitting and receiving The device performs the following steps: receiving a shared use protocol of the vehicle, the shared use protocol including a normative constraint of the occupant information in the vehicle; the processor calling the executable program code stored in the memory, performing the following steps: When detecting that the user uses the vehicle, the in-vehicle device that controls the vehicle collects in-vehicle occupant information; and determines whether the in-vehicle occupant information collected by the in-vehicle device meets the normative constraint of the in-vehicle occupant information in the shared use agreement; If not, sending a vehicle owner terminal that does not meet the prompt information to the vehicle, and handing over the authority to control the in-vehicle device of the vehicle to the vehicle owner terminal; according to the degree of non-conformity of the passenger information in the vehicle The vehicle
  • the normative constraint of the in-vehicle occupant information includes the number of persons and behavior norms of the occupant in the vehicle, and the driver a safe driving behavior specification; the processor executing the in-vehicle device that controls the vehicle to collect in-vehicle occupant information by: controlling the in-vehicle device to acquire the number of occupants in the vehicle and/or occupant behavior, and/or controlling the in-vehicle device Get the driver's driving behavior.
  • the processor performs the determining that the vehicle is collected by the in-vehicle device Whether the internal occupant information meets the normative constraint of the in-vehicle occupant information in the shared usage agreement, in a specific manner: comparing whether the number of occupants in the vehicle matches the occupant number specification; determining whether the occupant behavior is Determining a behavioral specification of the occupant in the vehicle; analyzing whether the driver's driving behavior matches the driver's safe driving behavior specification; if the result of any of the above is a mismatch, determining that the in-vehicle occupant information is not Comply with the normative constraints of the occupant information in the car.
  • the processor performs the non-conformity according to the in-vehicle occupant information to control the vehicle to perform a corresponding Operation, the specific way is: when the degree of non-compliance is slight, the control vehicle sends warning information; when the non-conformity is medium, the control vehicle issues warning information and decelerates; when the non-conformity is serious, the vehicle is decelerated and travels to The engine is locked when the safety zone is locked.
  • the server is a node server of a blockchain
  • the processor invokes the The executive code also performs the steps of registering the shared usage agreement in a blockchain in the form of a smart contract and publishing it throughout the network.
  • a shared use agreement of a vehicle is included, the shared use agreement including a normative constraint of in-vehicle occupant information; when it is detected that the user uses the vehicle, controlling the onboard of the vehicle
  • the device collects the occupant information in the vehicle; determines whether the occupant information collected by the in-vehicle device conforms to the normative constraint of the occupant information in the shared use agreement; if not, sends the non-compliant prompt information to the vehicle
  • the vehicle owner terminal transfers the authority for controlling the in-vehicle information of the vehicle to the vehicle owner terminal; and controls the vehicle to perform a corresponding operation according to the degree of non-compliance of the in-vehicle passenger information.
  • the user's standard type of the vehicle is effectively ensured, which not only ensures the proper control of the vehicle owner, that is, the owner of the vehicle, but also ensures the privacy of the user, improves the convenience of use of the vehicle sharing, and effectiveness.
  • FIG. 1 is a schematic diagram of an application scenario of a vehicle sharing method according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a vehicle sharing method according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a server according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic structural diagram of another server according to an embodiment of the present disclosure.
  • references to "an embodiment” herein mean that a particular feature, structure, or characteristic described in connection with the embodiments can be included in at least one embodiment of the invention.
  • the appearances of the phrases in various places in the specification are not necessarily referring to the same embodiments, and are not exclusive or alternative embodiments that are mutually exclusive. Those skilled in the art will understand and implicitly understand that the embodiments described herein can be combined with other embodiments.
  • Multiple means two or more. "and/or”, describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately.
  • the character "/" generally indicates that the contextual object is an "or" relationship.
  • FIG. 1 is a schematic diagram of an application scenario of a vehicle sharing method according to an embodiment of the present invention.
  • the application scenario includes: a server 10, a vehicle owner terminal 20, a vehicle 30, an in-vehicle device 40 mounted on the vehicle 30, a user terminal 50.
  • the server 10 communicates with the vehicle owner terminal 20, the in-vehicle device 40, and the user through a communication network.
  • Terminal 50 establishes a communication connection and interacts with it.
  • the in-vehicle device 40 establishes a communication connection with the vehicle owner terminal 20 or the user terminal 50 via a communication network or a short-range communication method.
  • the in-vehicle device 40 receives the instructions of the server 10 or the owner terminal 20 or the user terminal 50 and controls the vehicle to perform the corresponding action according to the instruction, while the in-vehicle device 40 collects the vehicle information of the vehicle 30 and uploads it to the server 10 or to the vehicle owner terminal 20.
  • the server 10 in the embodiment of the present invention may be a server of a shared vehicle service management platform, and may be a node server in a blockchain, and may also be a vehicle owner terminal in some specific scenarios.
  • the embodiment of the invention is not specifically limited.
  • FIG. 2 is a schematic flowchart diagram of a vehicle sharing method according to an embodiment of the present invention. As shown in FIG. 2, the method is applied to a server, and the method includes the following steps.
  • S201 Receive a shared use protocol of the vehicle, where the shared use agreement includes a normative constraint of the occupant information in the vehicle.
  • the owner of the vehicle that is, the owner of the vehicle decides to provide the shared service of the vehicle
  • the user can use the condition of the vehicle, the final parking position of the vehicle, the information collection during use, the usage fee, the handling of the abnormal situation of the vehicle, and the occupant of the vehicle.
  • the owner submits the shared use agreement to the server through the owner terminal.
  • the normative constraints of the occupant information in the vehicle include: the number of people in the vehicle and the code of conduct, the driver's safe driving behavior specifications, and the like.
  • the number of passengers in the vehicle specifically includes the upper limit of the number of passengers in the vehicle (including the driver).
  • the upper limit can be set according to the vehicle type. For example, the upper limit of the occupant of a car or a sport utility vehicle SUV is 5; the upper limit of the occupant of the utility vehicle MPV is 8 or the like. Of course, the upper limit value can also be set according to the preference of the owner, such as setting the upper limit of the vehicle occupant to 4 persons.
  • the behavioral norms of the occupants in the vehicle include the behavioral norms of the occupants in the vehicle.
  • the behavioral norms of the occupants in the vehicle can be set in the form of a negative list.
  • the driver's safe driving behavior specification includes the driver's driving speed specification, driving operation behavior specification, driving state specification, and the like.
  • the safe driving behavior specification can be set in the form of a negative list. For example, the driving speed must not exceed 120 km/h, the driving operation behavior must not cause high-frequency sudden braking, and the driving state must not cause fatigue driving.
  • the in-vehicle device that controls the vehicle collects the in-vehicle occupant information.
  • the server controlling the in-vehicle device of the vehicle to collect the in-vehicle occupant information comprises: controlling the in-vehicle device to acquire the number of occupants in the vehicle and/or the occupant behavior, and/or controlling the in-vehicle device to acquire the driving behavior of the driver.
  • the in-vehicle device can be connected to the in-vehicle camera preset by the vehicle, and acquire relevant information in the car through the in-vehicle camera.
  • the in-vehicle device can capture the image information of the occupant in the vehicle through the camera in the vehicle, obtain the number of occupants in the vehicle according to the number of portraits in the image information, and obtain the occupant behavior of the vehicle according to the action behavior of the person in the image information and the smoke condition;
  • the driver's driving behavior can be obtained by combining the in-vehicle camera and the OBD device.
  • the in-vehicle camera captures the driver's image information, and obtains the driver's image according to the blinking state of the driver's eyes in the image and the driver's current driving duration.
  • the speed and acceleration of the vehicle are collected by the OBD to obtain the driving speed and the braking behavior of the driver.
  • the server After the server obtains the in-vehicle occupant information through the in-vehicle device, the server further analyzes and judges whether the occupant information conforms to the in-vehicle occupant information specification constraint in the shared use agreement. Specifically, determining whether the in-vehicle occupant information collected by the in-vehicle device conforms to the normative constraint of the in-vehicle occupant information in the shared use protocol includes: comparing whether the number of the in-vehicle occupants matches the number of the occupant; Determining whether the occupant behavior matches the behavioral norm of the in-vehicle occupant; analyzing whether the driver's driving behavior matches the driver's safe driving behavior specification; if the result of any of the above is a mismatch, then It is judged that the in-vehicle occupant information does not conform to the normative constraint of the in-vehicle occupant information.
  • the obtained blinking state of the driver and the current driving duration of the driver is used to determine whether the driving state of the driver is fatigue driving, according to the obtained
  • the vehicle speed and acceleration data analyze the relationship between the maximum value of the vehicle speed and the upper limit of the vehicle speed to determine whether there is overspeed behavior; analyze the change of the acceleration data to determine the sudden braking behavior, and judge whether there is a high frequency according to the frequency of occurrence of the sudden braking behavior.
  • the sudden brakes and so on When all the above results match, it is judged that the in-vehicle occupant information conforms to the in-vehicle occupant information specification constraint. As long as the result of any one is a mismatch, it is judged that the occupant information in the vehicle does not conform to the specification constraint of the occupant information in the vehicle.
  • the upper limit of the number of occupants in the vehicle is 4, if the number of occupants in the vehicle is 5, the occupant information in the vehicle does not conform to the specification of the occupant information in the vehicle. Or, by comparing and judging that the occupant in the vehicle has a smoking behavior, and the driver frequently brakes or fatigues at a high frequency, it can be judged that the occupant information in the vehicle does not conform to the specification constraint of the occupant information in the vehicle.
  • the vehicle owner terminal that does not meet the prompt information is sent to the vehicle owner terminal, so that the owner understands the overall interior condition of the vehicle at this time, and the server monitors the condition of the vehicle inside the vehicle.
  • the authority is to transfer the authority of the in-vehicle device of the vehicle to collect the information of the passengers in the vehicle to the owner, so that the owner understands the condition inside the vehicle.
  • controlling the vehicle to perform the corresponding operation according to the degree of non-compliance of the occupant information in the vehicle specifically includes: when the degree of non-compliance is slight, controlling the vehicle to issue warning information; when the degree of non-conformity is medium, controlling the vehicle to issue the warning information And decelerate; when the degree of non-compliance is serious, the engine is stopped when the vehicle is decelerated and driven to a safe area.
  • the level calculation rule may be set in advance in the server setting the degree of incompatibility of the occupant information in the vehicle.
  • in-vehicle occupant information with a slight degree of non-compliance includes: the occupant behavior in the car does not meet the specifications, the smoking behavior occurs, or the car seat is stepped on without taking off the shoes; the driver's short-term driving behavior does not meet the specifications.
  • short-term such as within 10min
  • speeding behavior short-term (within 1min) driving fatigue.
  • the server controls the vehicle to issue a warning message, prompting the occupant of the vehicle to appear irregular behavior needs to be corrected in time.
  • In-vehicle occupant information that does not meet the requirements is: the driver has a higher frequency of sudden braking behavior, and after a warning, the fatigue driving or overspeed behavior occurs again in a short time (such as 30 minutes).
  • the server controls the vehicle to issue a warning message while controlling the vehicle to slow down.
  • the in-vehicle occupant information with a serious degree of non-compliance includes: the number of occupants in the vehicle exceeds the upper limit of the number of occupants in the vehicle, and the driver's non-standard driving behavior for a long period of time is over 30 minutes of overspeed, and fatigue driving for more than 10 minutes.
  • the server controls the vehicle to decelerate and drive to the safe area to lock the engine to stop processing.
  • the shared use agreement includes a normative constraint of the in-vehicle occupant information
  • the in-vehicle device controlling the vehicle collects the in-vehicle occupant Determining whether the in-vehicle occupant information collected by the in-vehicle device conforms to the normative constraint of the in-vehicle occupant information in the shared use agreement; if not, sending a non-compliance prompt message to the vehicle owner terminal of the vehicle, and The authority to control the in-vehicle device of the vehicle to collect the in-vehicle occupant information is handed over to the vehicle owner terminal; and the vehicle is controlled to perform a corresponding operation according to the degree of non-compliance of the in-vehicle occupant information.
  • the user's standard type of the vehicle is effectively ensured, which not only ensures the proper control of the vehicle owner, that is, the owner of the vehicle, but also ensures the privacy of the user, improves the convenience of use of the vehicle sharing, and effectiveness.
  • the user is allowed to continue to use the vehicle and continue to acquire the in-vehicle occupant information.
  • the vehicle is controlled to lock the engine and transfer control of the vehicle to the owner.
  • the occupant information in the car can be acquired again at the preset time length after the transaction (for example, 5 min), and when the occupant is found in the car, the alarm information is sent. Go to the owner's terminal and call the police.
  • the server is a blockchain node server. After receiving the shared use protocol of the vehicle, the server registers the shared use protocol in a blockchain in the form of a smart contract and publishes the entire network.
  • Blockchain technology uses blockchain data structures to validate and store data, use distributed node consensus algorithms to generate and update data, use cryptography to ensure data transfer and access security, and utilize intelligent script code A new distributed infrastructure and computing paradigm for contracting to program and manipulate data.
  • the owner of the vehicle that is, the owner of the vehicle
  • the blockchain node server ensures the authenticity and security of the vehicle information by receiving the information uploaded by the vehicle as the terminal node, thereby further improving the security and convenience of the shared use of the vehicle.
  • FIG. 3 is a schematic structural diagram of a server according to an embodiment of the present invention. As shown in Figure 3, the server includes:
  • the receiving unit 301 is configured to receive a shared use protocol of the vehicle, where the shared use agreement includes a normative constraint of the in-vehicle occupant information.
  • the owner of the vehicle that is, the owner of the vehicle decides to provide the shared service of the vehicle
  • the user can use the condition of the vehicle, the final parking position of the vehicle, the information collection during use, the usage fee, the handling of the abnormal situation of the vehicle, and the occupant of the vehicle.
  • the owner submits the shared use agreement to the server through the owner terminal.
  • the normative constraints of the occupant information in the vehicle include: the number of people in the vehicle and the code of conduct, the driver's safe driving behavior specifications, and the like.
  • the number of passengers in the vehicle specifically includes the upper limit of the number of passengers in the vehicle (including the driver).
  • the upper limit can be set according to the vehicle type. For example, the upper limit of the occupant of a car or a sport utility vehicle SUV is 5; the upper limit of the occupant of the utility vehicle MPV is 8 or the like. Of course, the upper limit value can also be set according to the preference of the owner, such as setting the upper limit of the vehicle occupant to 4 persons.
  • the behavioral norms of the occupants in the vehicle include the behavioral norms of the occupants in the vehicle.
  • the behavioral norms of the occupants in the vehicle can be set in the form of a negative list.
  • the driver's safe driving behavior specification includes the driver's driving speed specification, driving operation behavior specification, driving state specification, and the like.
  • the safe driving behavior specification can be set in the form of a negative list. For example, the driving speed must not exceed 120 km/h, the driving operation behavior must not cause high-frequency sudden braking, and the driving state must not cause fatigue driving.
  • the control unit 302 is configured to control the in-vehicle device of the vehicle to collect the in-vehicle occupant information when detecting that the user uses the vehicle.
  • controlling the in-vehicle device of the vehicle to collect the in-vehicle occupant information includes: controlling the in-vehicle device to acquire the number of occupants in the vehicle and/or occupant behavior, and/or controlling the in-vehicle device to acquire the driving behavior of the driver.
  • the in-vehicle device can be connected to the in-vehicle camera preset by the vehicle, and acquire relevant information in the car through the in-vehicle camera.
  • the in-vehicle device can capture the image information of the occupant in the vehicle through the camera in the vehicle, obtain the number of occupants in the vehicle according to the number of portraits in the image information, and obtain the occupant behavior of the vehicle according to the action behavior of the person in the image information and the smoke condition;
  • the driver's driving behavior can be obtained by combining the in-vehicle camera and the OBD device.
  • the in-vehicle camera captures the driver's image information, and obtains the driver's image according to the blinking state of the driver's eyes in the image and the driver's current driving duration.
  • the speed and acceleration of the vehicle are collected by the OBD to obtain the driving speed and the braking behavior of the driver.
  • the determining unit 303 is configured to determine whether the in-vehicle occupant information collected by the in-vehicle device conforms to the normative constraint of the in-vehicle occupant information in the shared use agreement.
  • the judging unit 303 further analyzes whether or not the occupant information conforms to the in-vehicle occupant information specification constraint in the shared use agreement. Specifically, the determining unit 303 determines whether the in-vehicle occupant information collected by the in-vehicle device conforms to the normative constraint of the in-vehicle occupant information in the shared use cooperative instrument, including: comparing whether the number of the in-vehicle occupants is equal to the number of the occupants a criterion matching; the determining unit 303 determines whether the occupant behavior matches the behavior norm of the in-vehicle occupant; and analyzes whether the driver's driving behavior matches the driver's safe driving behavior specification; The result is a mismatch, and the judging unit 303 judges that the in-vehicle occupant information does not conform to the normative constraint of the in-vehicle occupant information.
  • the judging unit 303 judges that the in-vehicle occupant information conforms to the in-vehicle occupant information specification type constraint. As long as the result of any one is a mismatch, the judging unit 303 judges that the in-vehicle occupant information does not conform to the in-vehicle occupant information specification type constraint.
  • the upper limit of the number of occupants in the vehicle is 4, if the number of occupants in the vehicle is 5, the occupant information in the vehicle does not conform to the specification of the occupant information in the vehicle. Or, by comparing and judging that the occupant in the vehicle has a smoking behavior, and the driver frequently brakes or fatigues at a high frequency, it can be judged that the occupant information in the vehicle does not conform to the specification constraint of the occupant information in the vehicle.
  • the prompting unit 304 is configured to: if the result of the determination by the determining unit 303 is non-conformity, send a vehicle owner terminal that does not meet the prompt information to the vehicle, and hand over the authority for controlling the in-vehicle device of the vehicle to collect the information of the in-vehicle passengers to the vehicle Describe the owner terminal.
  • the prompting unit 304 transmits the non-conforming prompt information to the vehicle owner terminal, so that the vehicle owner understands the overall in-vehicle condition of the vehicle at this time, and the server sets the vehicle.
  • the monitoring authority of the in-vehicle situation is to transfer the authority of the in-vehicle device of the vehicle to collect the in-vehicle occupant information to the owner, so that the owner understands the condition inside the car.
  • the control unit 305 is configured to control the vehicle to perform a corresponding operation according to the degree of non-compliance of the occupant information in the vehicle.
  • controlling the vehicle to perform the corresponding operation according to the degree of non-compliance of the occupant information in the vehicle specifically includes: when the degree of non-compliance is slight, the control unit 305 controls the vehicle to issue the warning information; when the degree of non-conformity is medium, the control unit 305 controls the vehicle to issue warning information and decelerates; when the degree of non-compliance is severe, the control unit 305 controls the vehicle to decelerate and locks the engine parking process when traveling to the safe area.
  • the level calculation rule may be set in advance in the server setting the degree of incompatibility of the occupant information in the vehicle.
  • in-vehicle occupant information with a slight degree of non-compliance includes: the occupant behavior in the car does not meet the specifications, the smoking behavior occurs, or the car seat is stepped on without taking off the shoes; the driver's short-term driving behavior does not meet the specifications.
  • short-term such as within 10min
  • speeding behavior short-term (within 1min) driving fatigue.
  • the control unit 305 controls the vehicle to issue the warning information
  • the prompting unit 304 prompts that the occupant of the vehicle has an irregular behavior and needs to be corrected in time.
  • In-vehicle occupant information that does not meet the requirements is: the driver has a higher frequency of sudden braking behavior, and after a warning, the fatigue driving or overspeed behavior occurs again in a short time (such as 30 minutes).
  • the control unit 305 controls the vehicle to issue warning information while controlling the vehicle to decelerate.
  • the in-vehicle occupant information with a serious degree of non-compliance includes: the number of occupants in the vehicle exceeds the upper limit of the number of occupants in the vehicle, and the driver's non-standard driving behavior for a long period of time is over 30 minutes of overspeed, and fatigue driving for more than 10 minutes.
  • the control unit 305 controls the vehicle to decelerate and travels to the safe area to lock up the engine parking process.
  • the shared use agreement includes a normative constraint of the in-vehicle occupant information
  • the in-vehicle device controlling the vehicle collects the in-vehicle occupant Determining whether the in-vehicle occupant information collected by the in-vehicle device conforms to the normative constraint of the in-vehicle occupant information in the shared use agreement; if not, sending a non-compliance prompt message to the vehicle owner terminal of the vehicle, and The authority to control the in-vehicle device of the vehicle to collect the in-vehicle occupant information is handed over to the vehicle owner terminal; and the vehicle is controlled to perform a corresponding operation according to the degree of non-compliance of the in-vehicle occupant information.
  • the user's standard type of the vehicle is effectively ensured, which not only ensures the proper control of the vehicle owner, that is, the owner of the vehicle, but also ensures the privacy of the user, improves the convenience of use of the vehicle sharing, and effectiveness.
  • the determining unit 303 determines that the in-vehicle occupant information collected by the in-vehicle device conforms to the normative constraint of the in-vehicle occupant information in the shared use agreement, the user is allowed to continue to use the vehicle and continue to acquire the in-vehicle occupant information.
  • the control unit 305 controls the vehicle to lock the engine and hand over the control of the vehicle to the owner.
  • the occupant information in the car can be acquired again at the preset time length after the transaction (for example, 5 min), and when the occupant is found in the car, the alarm information is sent. Go to the owner's terminal and call the police.
  • the server is a blockchain node server. After receiving the shared use protocol of the vehicle, the server registers the shared use protocol in a blockchain in the form of a smart contract and publishes the entire network.
  • Blockchain technology uses blockchain data structures to validate and store data, use distributed node consensus algorithms to generate and update data, use cryptography to ensure data transfer and access security, and utilize intelligent script code A new distributed infrastructure and computing paradigm for contracting to program and manipulate data.
  • the owner of the vehicle that is, the owner of the vehicle
  • the blockchain node server ensures the authenticity and security of the vehicle information by receiving the information uploaded by the vehicle as the terminal node, thereby further improving the security and convenience of the shared use of the vehicle.
  • FIG. 4 is a schematic structural diagram of another server according to an embodiment of the present invention.
  • the server includes a processor 401, a memory 402, a transceiver 403, and a bus 404, wherein the processor 401, the memory 402, and the transceiver 403 can be coupled by a bus or other means, and FIG. 4 is connected by a bus 404.
  • the processor 401, the memory 402, and the transceiver 403 can be coupled by a bus or other means
  • FIG. 4 is connected by a bus 404.
  • bus 404 for example.
  • the processor 401 can be digital signal processing (English: Digital Signal Processing, DSP) chip.
  • the processor 401 may include: a management/communication module (administration) Module/communication module, AM/CM) (center for voice exchange and information exchange), module for completing call processing, signaling processing, radio resource management, radio link management, and circuit maintenance functions, code rate Transform and sub-multiplex module (transcoder Submultiplexer, TCSM) (for completing the multiplexing demultiplexing and code conversion functions) and other modules.
  • a management/communication module administration
  • AM/CM center for voice exchange and information exchange
  • module for completing call processing
  • signaling processing radio resource management
  • radio link management radio link management
  • circuit maintenance functions code rate Transform and sub-multiplex module (transcoder Submultiplexer, TCSM) (for completing the multiplexing demultiplexing and code conversion functions) and other modules.
  • code rate Transform and sub-multiplex module for completing the multiplexing demultiplexing and code conversion functions
  • the memory 402 is used to store program codes shared by the vehicle.
  • the memory 402 can be a read-only memory (English: Read-Only Memory, ROM) or a random access memory (RAM). Program code shared by the storage vehicle.
  • the transceiver 403 is configured to perform a transmission process (eg, modulation) on the mobile communication signal generated by the processor 401, and is also used to perform reception processing (eg, demodulation) on the mobile communication signal received by the antenna.
  • a transmission process eg, modulation
  • reception processing eg, demodulation
  • Bus 404 can be an industry standard architecture (English: Industry Standard Architecture, ISA) bus, external device interconnection (English: Peripheral Component Interconnect, PCI) bus, extended standard architecture (English: Extended Industry Standard Architecture (EISA) bus, integrated circuit bus (English: Inter Integrated Circuit, IIC).
  • ISA Industry Standard Architecture
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • IIC Inter Integrated Circuit
  • the processor 401 controls the transceiver 403 to perform the following operations:
  • the shared use agreement including a normative constraint of the occupant information in the vehicle
  • the processor 401 is further configured to invoke executable application code stored in the memory 402, and perform the following operations:
  • the in-vehicle device controlling the vehicle collects in-vehicle occupant information
  • the vehicle is controlled to perform a corresponding operation according to the degree of non-compliance of the occupant information in the vehicle.
  • the normative constraints of the occupant information in the vehicle include a specification and a code of conduct of the occupant in the vehicle, and a safe driving behavior specification of the driver;
  • the processor executes the in-vehicle device that controls the vehicle to collect in-vehicle occupant information by: controlling the in-vehicle device to acquire the number of occupants in the vehicle and/or occupant behavior, and/or controlling the in-vehicle device to obtain driving behavior of the driver .
  • the processor performs the determining whether the in-vehicle occupant information collected by the in-vehicle device conforms to the normative constraint of the in-vehicle occupant information in the shared use protocol, and the specific manner is:
  • the processor performs the performing the corresponding operation according to the degree of non-compliance of the occupant information in the vehicle, and the specific manner is:
  • control vehicle issues a warning message
  • control vehicle When the degree of non-compliance is medium, the control vehicle issues a warning message and decelerates;
  • the engine is stopped when the vehicle is decelerated and traveled to a safe area.
  • the server is a node server of a blockchain.
  • the processor invokes the executable program code stored in the memory, and further performs the following steps:
  • the shared use agreement is registered in the blockchain in the form of a smart contract and published throughout the network.
  • the shared use agreement includes a normative constraint of the in-vehicle occupant information
  • the in-vehicle device controlling the vehicle collects the in-vehicle occupant Determining whether the in-vehicle occupant information collected by the in-vehicle device conforms to the normative constraint of the in-vehicle occupant information in the shared use agreement; if not, sending a non-compliance prompt message to the vehicle owner terminal of the vehicle, and The authority to control the in-vehicle device of the vehicle to collect the in-vehicle occupant information is handed over to the vehicle owner terminal; and the vehicle is controlled to perform a corresponding operation according to the degree of non-compliance of the in-vehicle occupant information.
  • the user's standard type of the vehicle is effectively ensured, which not only ensures the proper control of the vehicle owner, that is, the owner of the vehicle, but also ensures the privacy of the user, improves the convenience of use of the vehicle sharing, and effectiveness.
  • the embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium can store a program, and the program includes some or all of the steps of any one of the vehicle sharing methods described in the foregoing method embodiments.
  • the disclosed apparatus may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a memory.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing memory includes: a U disk, a read-only memory (ROM), a random access memory (RAM, Random Access). Memory, removable hard disk, disk or optical disk, etc., which can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Accounting & Taxation (AREA)
  • Medical Informatics (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Traffic Control Systems (AREA)

Abstract

本方案公开了一种车辆共享方法及服务器，所述车辆共享方法包括：接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束；当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息；判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束；若不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端；根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。采用本方案实施例保证了车辆所有权人的信息知情权，也保证了用户隐私，提高了车辆共享的使用效率。

Description

一种车辆共享方法及服务器 技术领域
本发明涉及车辆技术领域，尤其涉及一种车辆共享方法及服务器。
 背景技术
随着科技的进步，人类经历前所未有的繁荣，社会快速进步，创造了大量的生产生活工具，提升人类的幸福水平。但是过于快速的发展，已经造成了严重的浪费，导致环境污染。共享经济作为绿色发展理念，在节能环保和可持续发展方面具有巨大的优势，得到了快速的发展。共享汽车作为共享经济的主要实践方向，具有广泛的前景。在实际的使用过程中，共享汽车的车主希望能实时了解用户对车辆的使用情况，以确保自己的车辆被合理规范使用。而使用者则考虑个人隐私是否被泄露。现有的共享车辆技术中，共享车辆在使用过程中通过车载设备仅能将车辆的运行情况如行车路线、停车位置等实时报告给车主，并不能很好的监控和规范车内乘员的行为，一方面不能解决车主对使用者合理规范使用车辆的担忧，另一方面若实时监控车内数据又有侵犯使用者隐私的嫌疑，同时大量的实时数据也给车主带来了困扰。因此亟需要一种新的技术来规范共享车辆的合理使用，以解决现有技术中的车主对车辆使用的担忧和使用者隐私保护的问题。
 技术问题
本发明实施例提供一种车辆共享方法及服务器，有利于解决现有技术中车主对车辆使用的担忧和使用者隐私保护的问题，同时提高了车辆共享的使用便利性和效率。
 技术解决方案
第一方面，本发明实施例提供一种车辆共享方法，应用于服务器，所述方法包括：接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束；当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息；判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束；若不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端；根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。
结合本发明实施例第一方面，在本发明实施例第一方面的第一种可能实现的方式中，所述车内乘员信息的规范性约束包括车内乘员的人数规范和行为规范、驾驶员的安全驾驶行为规范；所述控制所述车辆的车载设备采集车内乘员信息，包括：控制车载设备获取车内乘员数量和/或乘员行为，和/或控制车载设备获取驾驶员的驾驶行为。
结合本发明实施例第一方面的第一种可能实现的方式，在本发明实施例第一方面的第二种可能实现的方式中，所述判断所述车载设备采集的车内乘员信息是否符合所述共享使用协仪中的车内乘员信息规范性约束包括：比对所述车内乘员数量是否与所述乘员人数规范匹配；判断所述乘员行为是否与所述车内乘员的行为规范匹配；分析所述驾驶员的驾驶行为是否与所述驾驶员的安全驾驶行为规范匹配；若上述任一项的结果为不匹配，则判断所述车内乘员信息不符合所述车内乘员信息规范性约束。
结合本发明实施例第一方面，在本发明实施例第一方面的第三种可能实现的方式中，所述根据车内乘员信息的不符合程度控制所述车辆执行相应的操作具体包括：当不符合程度为轻微时，控制车辆发出警示信息；当不符合程度为中等时，控制车辆发出警示信息并减速；当不符合程度为严重时，控制车辆减速并行驶到安全区域时锁死发动机停车处理。
结合本发明实施例第一方面、第一方面的第一种可能实现的方式、第一方面的第二种可能实现的方式中、第一方面的第三种可能实现的方式，在本发明实施例第一方面的第四种可能实现的方式中，所述服务器为区块链的节点服务器，在所述接收车辆的共享使用协议之后，所述方法还包括：将所述共享使用协议以智能合约的形式登记在区块链中并全网公布。
本发明第二方面提供了一种服务器，所述服务器包括：存储有可执行程序代码的存储器；与所述存储器耦合的处理器；与所述处理器耦合的收发器；所述处理器控制收发器执行下列步骤：接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束；所述处理器调用所述存储器中存储的所述可执行程序代码，执行如下步骤：当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息；判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束；若不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端；根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。
结合本发明实施例第二方面，在本发明实施例第二方面的第一种可能实现的方式中，所述车内乘员信息的规范性约束包括车内乘员的人数规范和行为规范、驾驶员的安全驾驶行为规范；所述处理器执行所述控制所述车辆的车载设备采集车内乘员信息，具体方式为：控制车载设备获取车内乘员数量和/或乘员行为，和/或控制车载设备获取驾驶员的驾驶行为。
结合本发明实施例第二方面的第一种可能实现的方式，在本发明实施例第二方面的第二种可能实现的方式中，所述处理器执行所述判断所述车载设备采集的车内乘员信息是否符合所述共享使用协仪中的车内乘员信息规范性约束，具体方式为：比对所述车内乘员数量是否与所述乘员人数规范匹配；判断所述乘员行为是否与所述车内乘员的行为规范匹配；分析所述驾驶员的驾驶行为是否与所述驾驶员的安全驾驶行为规范匹配；若上述任一项的结果为不匹配，则判断所述车内乘员信息不符合所述车内乘员信息规范性约束。
结合本发明实施例第一方面，在本发明实施例第一方面的第三种可能实现的方式中，所述处理器执行所述根据车内乘员信息的不符合程度控制所述车辆执行相应的操作，具体方式为：当不符合程度为轻微时，控制车辆发出警示信息；当不符合程度为中等时，控制车辆发出警示信息并减速；当不符合程度为严重时，控制车辆减速并行驶到安全区域时锁死发动机停车处理。
结合本发明实施例第二方面、第二方面的第一种可能实现的方式、第二方面的第二种可能实现的方式中、第二方面的第三种可能实现的方式，在本发明实施例第二方面的第四种可能实现的方式中，所述服务器为区块链的节点服务器，在所述接收车辆的共享使用协议之后，所述处理器调用所述存储器中存储的所述可执行程序代码还执行如下步骤：将所述共享使用协议以智能合约的形式登记在区块链中并全网公布。
 有益效果
可以看出，在本发明的实施例中，接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束；当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息；判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束；若不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端；根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。通过采取上述车辆共享方法，有效确保了使用者使用车辆的规范型，既保证了车辆所有权人即车主对车辆的适度控制权，也保证了使用者的隐私，提高了车辆共享的使用便利性和效率。
本发明的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的一种车辆共享方法的应用场景示意图；
图2为本发明实施例提供的一种车辆共享方法的流程示意图；
图3为本发明实施例提供的一种服务器结构示意图；
图4为本发明实施例提供的另一种服务器结构示意图；
 本发明的实施方式
为了使本技术领域的人员更好地理解本发明方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分的实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本发明保护的范围。
以下分别进行详细说明。
本发明的说明书和权利要求书及所述附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
在本文中提及“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本发明的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是，本文所描述的实施例可以与其它实施例相结合。
“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
下面结合附图对本申请的实施例进行描述。
请参见图1，图1为本发明实施例提供的一种车辆共享方法的应用场景示意图。如图1所示，该应用场景包括：服务器10，车主终端20，车辆30，安装在车辆30上的车载设备40，用户终端50.服务器10通过通信网络与车主终端20、车载设备40和用户终端50建立通信连接，并与之交互。车载设备40与车主终端20或者用户终端50通过通信网络或者近距离通信方式建立通信连接。车载设备40接收服务器10或者车主终端20或者用户终端50的指令并根据指令控制车辆执行相应的动作，同时车载设备40采集车辆30的车辆信息并上传到服务器10或者发送到车主终端20.
需要说明的是，本发明实施例中的服务器10可以是共享车辆服务管理平台的一个服务器，可以是一个区块链中的节点服务器，在一些具体的场景下也可以是车主终端。本发明实施例不做具体限定。
请参见图2，图2是本发明实施例提供的一种车辆共享方法的流程示意图。如图2所示，该方法应用于服务器，该方法包括如下步骤。
S201、接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束。
当车辆的所有权人也即车主决定提供车辆的共享服务时，可以与用户就车辆的使用条件、车辆的最终停放位置、使用过程中的信息收集、使用费用、车辆异常情况的处理以及车内乘员信息的规范性约束等达成共享使用协议后，由车主通过车主终端将共享使用协议提交到服务器。
具体的，车内乘员信息的规范性约束包括：车内乘员的人数规范和行为规范、驾驶员的安全驾驶行为规范等。其中，车内乘员的人数规范具体包括车内乘员数（包括驾驶员）的上限值。该上限值可以根据车型设定，如轿车、运动型多用途汽车SUV等的乘员上限值为5人；多用途汽车MPV的乘员上限值为8人等。当然，该上限值也可以根据车主的偏好设定，如设置车辆乘员上限值为4人等。车内乘员的行为规范包括车内乘员的行为动作规范，该车内乘员的行为规范可以负面清单的形式进行设定，如车内乘员不得有抽烟行为、车内乘员不能在未脱鞋的情况下直接踩在座椅上等。驾驶员的安全驾驶行为规范包括驾驶员的驾驶速度规范、驾驶操作行为规范、驾驶状态规范等。该安全驾驶行为规范可以负面清单的形式进行设定，如驾驶速度不得超过120km/h，驾驶操作行为不得出现高频次的急刹车、驾驶状态不得出现疲劳驾驶等。
S202、当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息。
具体的，服务器控制所述车辆的车载设备采集车内乘员信息包括：控制车载设备获取车内乘员数量和/或乘员行为，和/或控制车载设备获取驾驶员的驾驶行为。
其中，车载设备可以连接到车辆预置的车内摄像头，并通过车内摄像头获取车内的相关信息。例如，车载设备可以通过车内摄像头拍摄车内乘员的图像信息，根据图像信息中的人像数量获取车内乘员数量，根据图像信息中的人的动作行为以及烟雾情况获取车内乘员行为；车载设备可以通过结合车内摄像头和OBD设备获取驾驶员的驾驶行为，具体的，车内摄像头拍摄驾驶员的图像信息，根据图像中驾驶员眼睛的眨眼状态和驾驶员的当前驾驶时长来获取驾驶员的驾驶状态，通过OBD采集到车辆的速度及加速度来获取驾驶员的驾驶速度和急刹车行为。
S203、判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束。
服务器在通过车载设备获取到车内乘员信息后，进一步分析判断乘员信息是否符合共享使用协议中的车内乘员信息规范型约束。具体的，判断所述车载设备采集的车内乘员信息是否符合所述共享使用协仪中的车内乘员信息规范性约束包括：比对所述车内乘员数量是否与所述乘员人数规范匹配；判断所述乘员行为是否与所述车内乘员的行为规范匹配；分析所述驾驶员的驾驶行为是否与所述驾驶员的安全驾驶行为规范匹配；若上述任一项的结果为不匹配，则判断所述车内乘员信息不符合所述车内乘员信息规范性约束。
其中，可以根据获取到的车内乘员数量是否超过车内乘员数上限值，根据获取到的车内乘员行为判断是否有抽烟行为、是否在未脱鞋的情况下直接踩在座椅上，根据获取到的驾驶员的眨眼状态和驾驶员的当前驾驶时长，分析眨眼状态是否符合疲劳驾驶特征，分析当前驾驶时长是否超过3小时等来判断驾驶员的驾驶状态是否为疲劳驾驶，根据获取到的车速和加速度数据，分析车速的最大值与车速上限值的关系来判断是否有超速行为；分析加速度数据的变化情况判断急刹车行为，并根据急刹车行为的出现频次判断是否有高频次的急刹车等。当上述所有的结果匹配时，则判断车内乘员信息符合车内乘员信息规范型约束。只要有任何一项的结果为不匹配，则判断车内乘员信息不符合车内乘员信息规范型约束。
例如，当车内乘员数上限值为4人，若获取到车内乘员数量为5人，则说明车内乘员信息不符合车内乘员信息规范型约束。或者，通过比对分析判断发现车内乘员有抽烟行为，驾驶员高频次急刹车或者疲劳驾驶，则可以判断车内乘员信息不符合车内乘员信息规范型约束。
S204、若不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端。
若判断车内乘员信息不符合车内乘员信息规范型约束，则发送不符合提示信息至车辆的车主终端，使车主了解此时车辆的整体车内状况，同时服务器将车辆的车内情况的监控权限即将控制车辆的车载设备采集车内乘员信息的权限移交给车主，使车主了解车内的状况。
S205、根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。
具体的，根据车内乘员信息的不符合程度控制所述车辆执行相应的操作具体包括：当不符合程度为轻微时，控制车辆发出警示信息；当不符合程度为中等时，控制车辆发出警示信息并减速；当不符合程度为严重时，控制车辆减速并行驶到安全区域时锁死发动机停车处理。
可以预先在服务器设置车内乘员信息不符合程度的等级计算规则。例如，不符合程度为轻微的车内乘员信息包括：车内的乘员行为不符合规范，出现抽烟行为，或者在未脱鞋的情况下踩踏汽车座椅等；驾驶员的短期驾驶行为不符合规范如出现短时（如10min以内）超速行为、短时（1min以内）驾驶疲劳等。此时服务器控制车辆发出警示信息，提示车内乘员出现不规范行为需要及时纠正。不符合程度为中等的车内乘员信息包括：驾驶员出现较高频次的急刹车行为、警示后在较短时间内（如30min）再次出现疲劳驾驶或者超速行为等。此时服务器控制车辆发出警示信息，同时控制车辆减速。不符合程度为严重的车内乘员信息包括：车内乘员人数超出车内乘员数的上限值，驾驶员长时期的不规范驾驶行为如超速30min以上，疲劳驾驶10min以上等。此时服务器控制车辆减速并行驶到安全区域后锁死发动机停车处理。
在本实施例中，通过接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束；当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息；判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束；若不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端；根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。通过采取上述车辆共享方法，有效确保了使用者使用车辆的规范型，既保证了车辆所有权人即车主对车辆的适度控制权，也保证了使用者的隐私，提高了车辆共享的使用便利性和效率。
可选的，当判断所述车载设备采集的车内乘员信息符合所述共享使用协议中的车内乘员信息规范性约束时，允许用户继续使用车辆并继续获取车内乘员信息。当接收到用户终端的交易结束指令时，控制车辆锁死发动机并将车辆的控制权移交给车主。当然，为了避免交易结束后的资源占用或者用户遗忘小孩在车内，可以在交易结束后的预设时长（如5min）再次获取车内的乘员信息，当发现车内有乘员时，发送警报信息至车主终端并报警。
可选的，在本发明实施例中，服务器为区块链节点服务器，在接收到车辆的共享使用协议之后，服务器将共享使用协议以智能合约的形式登记在区块链中并全网公布。
区块链技术是利用块链式数据结构来验证与存储数据、利用分布式节点共识算法来生成和更新数据、利用密码学的方式保证数据传输和访问的安全、利用由自动化脚本代码组成的智能合约来编程和操作数据的一种全新的分布式基础架构与计算范式。在本发明实施例中，车辆的所有权人即车主可以将车辆登记为区块链的一个终端节点，具备查询和提交的功能。区块链节点服务器通过接收作为终端节点的车辆上传的信息，保证了车辆信息的真实性和安全性，从而进一步提高了车辆共享使用的安全性和便利性。
请参见图3，图3是本发明实施例提供的一种服务器结构示意图。如图3所示，该服务器包括：
接收单元301，用于接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束。
当车辆的所有权人也即车主决定提供车辆的共享服务时，可以与用户就车辆的使用条件、车辆的最终停放位置、使用过程中的信息收集、使用费用、车辆异常情况的处理以及车内乘员信息的规范性约束等达成共享使用协议后，由车主通过车主终端将共享使用协议提交到服务器。
具体的，车内乘员信息的规范性约束包括：车内乘员的人数规范和行为规范、驾驶员的安全驾驶行为规范等。其中，车内乘员的人数规范具体包括车内乘员数（包括驾驶员）的上限值。该上限值可以根据车型设定，如轿车、运动型多用途汽车SUV等的乘员上限值为5人；多用途汽车MPV的乘员上限值为8人等。当然，该上限值也可以根据车主的偏好设定，如设置车辆乘员上限值为4人等。车内乘员的行为规范包括车内乘员的行为动作规范，该车内乘员的行为规范可以负面清单的形式进行设定，如车内乘员不得有抽烟行为、车内乘员不能在未脱鞋的情况下直接踩在座椅上等。驾驶员的安全驾驶行为规范包括驾驶员的驾驶速度规范、驾驶操作行为规范、驾驶状态规范等。该安全驾驶行为规范可以负面清单的形式进行设定，如驾驶速度不得超过120km/h，驾驶操作行为不得出现高频次的急刹车、驾驶状态不得出现疲劳驾驶等。
控制单元302，用于当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息。
具体的，控制单元302控制所述车辆的车载设备采集车内乘员信息包括：控制车载设备获取车内乘员数量和/或乘员行为，和/或控制车载设备获取驾驶员的驾驶行为。
其中，车载设备可以连接到车辆预置的车内摄像头，并通过车内摄像头获取车内的相关信息。例如，车载设备可以通过车内摄像头拍摄车内乘员的图像信息，根据图像信息中的人像数量获取车内乘员数量，根据图像信息中的人的动作行为以及烟雾情况获取车内乘员行为；车载设备可以通过结合车内摄像头和OBD设备获取驾驶员的驾驶行为，具体的，车内摄像头拍摄驾驶员的图像信息，根据图像中驾驶员眼睛的眨眼状态和驾驶员的当前驾驶时长来获取驾驶员的驾驶状态，通过OBD采集到车辆的速度及加速度来获取驾驶员的驾驶速度和急刹车行为。
判断单元303，用于判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束。
服务器在通过车载设备获取到车内乘员信息后，判断单元303进一步分析判断乘员信息是否符合共享使用协议中的车内乘员信息规范型约束。具体的，判断单元303判断所述车载设备采集的车内乘员信息是否符合所述共享使用协仪中的车内乘员信息规范性约束包括：比对所述车内乘员数量是否与所述乘员人数规范匹配；判断单元303判断所述乘员行为是否与所述车内乘员的行为规范匹配；分析所述驾驶员的驾驶行为是否与所述驾驶员的安全驾驶行为规范匹配；若上述任一项的结果为不匹配，判断单元303则判断所述车内乘员信息不符合所述车内乘员信息规范性约束。
其中，可以根据获取到的车内乘员数量是否超过车内乘员数上限值，根据获取到的车内乘员行为判断是否有抽烟行为、是否在未脱鞋的情况下直接踩在座椅上，根据获取到的驾驶员的眨眼状态和驾驶员的当前驾驶时长，分析眨眼状态是否符合疲劳驾驶特征，分析当前驾驶时长是否超过3小时等来判断驾驶员的驾驶状态是否为疲劳驾驶，根据获取到的车速和加速度数据，分析车速的最大值与车速上限值的关系来判断是否有超速行为；分析加速度数据的变化情况判断急刹车行为，并根据急刹车行为的出现频次判断是否有高频次的急刹车等。当上述所有的结果匹配时，判断单元303则判断车内乘员信息符合车内乘员信息规范型约束。只要有任何一项的结果为不匹配，判断单元303则判断车内乘员信息不符合车内乘员信息规范型约束。
例如，当车内乘员数上限值为4人，若获取到车内乘员数量为5人，则说明车内乘员信息不符合车内乘员信息规范型约束。或者，通过比对分析判断发现车内乘员有抽烟行为，驾驶员高频次急刹车或者疲劳驾驶，则可以判断车内乘员信息不符合车内乘员信息规范型约束。
提示单元304，用于若判断单元303判断的结果为不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端。
若判断单元303判断车内乘员信息不符合车内乘员信息规范型约束，提示单元304则发送不符合提示信息至车辆的车主终端，使车主了解此时车辆的整体车内状况，同时服务器将车辆的车内情况的监控权限即将控制车辆的车载设备采集车内乘员信息的权限移交给车主，使车主了解车内的状况。
控制单元305，用于根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。
具体的，根据车内乘员信息的不符合程度控制所述车辆执行相应的操作具体包括：当不符合程度为轻微时，控制单元305控制车辆发出警示信息；当不符合程度为中等时，控制单元305控制车辆发出警示信息并减速；当不符合程度为严重时，控制单元305控制车辆减速并行驶到安全区域时锁死发动机停车处理。
可以预先在服务器设置车内乘员信息不符合程度的等级计算规则。例如，不符合程度为轻微的车内乘员信息包括：车内的乘员行为不符合规范，出现抽烟行为，或者在未脱鞋的情况下踩踏汽车座椅等；驾驶员的短期驾驶行为不符合规范如出现短时（如10min以内）超速行为、短时（1min以内）驾驶疲劳等。此时控制单元305控制车辆发出警示信息，提示单元304提示车内乘员出现不规范行为需要及时纠正。不符合程度为中等的车内乘员信息包括：驾驶员出现较高频次的急刹车行为、警示后在较短时间内（如30min）再次出现疲劳驾驶或者超速行为等。此时控制单元305控制车辆发出警示信息，同时控制车辆减速。不符合程度为严重的车内乘员信息包括：车内乘员人数超出车内乘员数的上限值，驾驶员长时期的不规范驾驶行为如超速30min以上，疲劳驾驶10min以上等。此时控制单元305控制车辆减速并行驶到安全区域后锁死发动机停车处理。
在本实施例中，通过接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束；当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息；判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束；若不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端；根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。通过采取上述车辆共享方法，有效确保了使用者使用车辆的规范型，既保证了车辆所有权人即车主对车辆的适度控制权，也保证了使用者的隐私，提高了车辆共享的使用便利性和效率。
可选的，当判断单元303判断所述车载设备采集的车内乘员信息符合所述共享使用协议中的车内乘员信息规范性约束时，允许用户继续使用车辆并继续获取车内乘员信息。当接收单元301接收到用户终端的交易结束指令时，控制单元305控制车辆锁死发动机并将车辆的控制权移交给车主。当然，为了避免交易结束后的资源占用或者用户遗忘小孩在车内，可以在交易结束后的预设时长（如5min）再次获取车内的乘员信息，当发现车内有乘员时，发送警报信息至车主终端并报警。
可选的，在本发明实施例中，服务器为区块链节点服务器，在接收到车辆的共享使用协议之后，服务器将共享使用协议以智能合约的形式登记在区块链中并全网公布。
区块链技术是利用块链式数据结构来验证与存储数据、利用分布式节点共识算法来生成和更新数据、利用密码学的方式保证数据传输和访问的安全、利用由自动化脚本代码组成的智能合约来编程和操作数据的一种全新的分布式基础架构与计算范式。在本发明实施例中，车辆的所有权人即车主可以将车辆登记为区块链的一个终端节点，具备查询和提交的功能。区块链节点服务器通过接收作为终端节点的车辆上传的信息，保证了车辆信息的真实性和安全性，从而进一步提高了车辆共享使用的安全性和便利性。
请参见图4，图4为本发明实施例提供的另一种服务器结构示意图。如图4所示，该服务器包括处理器401、存储器402、收发器403和总线404，其中处理器401、存储器402和收发器403可以通过总线或其他方式耦合连接，图4以通过总线404连接为例。
其中，处理器401可以是数字信号处理（英文：Digital Signal Processing，DSP）芯片。具体实现中，处理器401可包括：管理/通信模块（administration module/communication module，AM/CM）（用于话路交换和信息交换的中心）、用于完成呼叫处理、信令处理、无线资源管理、无线链路的管理和电路维护功能的模块、码速率变换与子复用模块（transcoder submultiplexer，TCSM）（用于完成复用解复用及码变换功能）等模块。具体信息可参考移动通讯相关知识。
存储器402用于存储车辆共享的程序代码，具体实现中，存储器402可以采用只读存储器（英文：Read-Only Memory，ROM）或随机存取存贮器（英文：Random Access Memory，RAM），可用于存储车辆共享的程序代码。
收发器403用于对处理器401生成的移动通信信号进行发射处理（例如调制），还用于对天线接收的移动通信信号进行接收处理（例如解调）。
总线404可以是工业标准体系结构（英文：Industry Standard Architecture，ISA）总线、外部设备互连（英文：Peripheral Component Interconnect，PCI）总线、扩展标准体系结构（英文：Extended Industry Standard Architecture，EISA）总线、集成电路总线（英文：Inter Integrated Circuit，IIC）等。
本发明实施例中，处理器401控制收发器403执行以下操作：
接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束；
所述处理器401还用于调用存储器402中存储的可执行应用程序代码，执行如下操作：
当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息；
判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束；
若不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端；
根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。
可选的，所述车内乘员信息的规范性约束包括车内乘员的人数规范和行为规范、驾驶员的安全驾驶行为规范；
所述处理器执行所述控制所述车辆的车载设备采集车内乘员信息，具体方式为：控制车载设备获取车内乘员数量和/或乘员行为，和/或控制车载设备获取驾驶员的驾驶行为。
可选的，所述处理器执行所述判断所述车载设备采集的车内乘员信息是否符合所述共享使用协仪中的车内乘员信息规范性约束，具体方式为：
比对所述车内乘员数量是否与所述乘员人数规范匹配；判断所述乘员行为是否与所述车内乘员的行为规范匹配；分析所述驾驶员的驾驶行为是否与所述驾驶员的安全驾驶行为规范匹配；
若上述任一项的结果为不匹配，则判断所述车内乘员信息不符合所述车内乘员信息规范性约束。
可选的，所述处理器执行所述根据车内乘员信息的不符合程度控制所述车辆执行相应的操作，具体方式为：
当不符合程度为轻微时，控制车辆发出警示信息；
当不符合程度为中等时，控制车辆发出警示信息并减速；
当不符合程度为严重时，控制车辆减速并行驶到安全区域时锁死发动机停车处理。
可选的，所述服务器为区块链的节点服务器，在所述接收车辆的共享使用协议之后，所述处理器调用所述存储器中存储的所述可执行程序代码，还执行如下步骤：
将所述共享使用协议以智能合约的形式登记在区块链中并全网公布。
在本实施例中，通过接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束；当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息；判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束；若不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端；根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。通过采取上述车辆共享方法，有效确保了使用者使用车辆的规范型，既保证了车辆所有权人即车主对车辆的适度控制权，也保证了使用者的隐私，提高了车辆共享的使用便利性和效率。
本发明实施例还提供一种计算机存储介质，其中，该计算机存储介质可存储有程序，该程序执行时包括上述方法实施例中记载的任何一种车辆共享方法的部分或全部步骤。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置，可通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储器中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储器中，包括若干指令用以使得一台计算机设备（可为个人计算机、服务器或者网络设备等）执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储器包括：U盘、只读存储器（ROM，Read-Only Memory）、随机存取存储器（RAM，Random Access Memory）、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读存储器中，存储器可以包括：闪存盘、只读存储器（英文：Read-Only Memory ，简称：ROM）、随机存取器（英文：Random Access Memory，简称：RAM）、磁盘或光盘等。
以上对本发明实施例进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上上述，本说明书内容不应理解为对本发明的限制。

Claims (10)

  1. 一种车辆共享方法，其特征在于，应用于服务器，所述方法包括：
    接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束；
    当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息；
    判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束；
    若不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端；
    根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。
  2. 根据权利要求1所述的车辆共享方法，其特征在于，所述车内乘员信息的规范性约束包括车内乘员的人数规范和行为规范、驾驶员的安全驾驶行为规范；
    所述控制所述车辆的车载设备采集车内乘员信息，包括：控制车载设备获取车内乘员数量和/或乘员行为，和/或控制车载设备获取驾驶员的驾驶行为。
  3. 根据权利要求2所述的车辆共享方法，其特征在于，所述判断所述车载设备采集的车内乘员信息是否符合所述共享使用协仪中的车内乘员信息规范性约束包括：
    比对所述车内乘员数量是否与所述乘员人数规范匹配；判断所述乘员行为是否与所述车内乘员的行为规范匹配；分析所述驾驶员的驾驶行为是否与所述驾驶员的安全驾驶行为规范匹配；
    若上述任一项的结果为不匹配，则判断所述车内乘员信息不符合所述车内乘员信息规范性约束。
  4. 根据权利要求1所述的方法，其特征在于，所述根据车内乘员信息的不符合程度控制所述车辆执行相应的操作具体包括：
    当不符合程度为轻微时，控制车辆发出警示信息；
    当不符合程度为中等时，控制车辆发出警示信息并减速；
    当不符合程度为严重时，控制车辆减速并行驶到安全区域时锁死发动机停车处理。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述服务器为区块链的节点服务器，在所述接收车辆的共享使用协议之后，所述方法还包括：
    将所述共享使用协议以智能合约的形式登记在区块链中并全网公布。
  6. 一种服务器，所述服务器包括：
    存储有可执行程序代码的存储器；
    与所述存储器耦合的处理器；
    与所述处理器耦合的收发器；
    所述处理器控制收发器执行下列步骤：
    接收车辆的共享使用协议，所述共享使用协议包括车内乘员信息的规范性约束；
    所述处理器调用所述存储器中存储的所述可执行程序代码，执行如下步骤：
    当检测到用户使用所述车辆时，控制所述车辆的车载设备采集车内乘员信息；
    判断所述车载设备采集的车内乘员信息是否符合所述共享使用协议中的车内乘员信息规范性约束；
    若不符合，则发送不符合提示信息至所述车辆的车主终端，并将控制所述车辆的车载设备采集车内乘员信息的权限移交给所述车主终端；
    根据车内乘员信息的不符合程度控制所述车辆执行相应的操作。
  7. 根据权利要求6所述的服务器，其特征在于，所述车内乘员信息的规范性约束包括车内乘员的人数规范和行为规范、驾驶员的安全驾驶行为规范；
    所述处理器执行所述控制所述车辆的车载设备采集车内乘员信息，具体方式为：控制车载设备获取车内乘员数量和/或乘员行为，和/或控制车载设备获取驾驶员的驾驶行为。
  8. 根据权利要求7所述的服务器，其特征在于，所述处理器执行所述判断所述车载设备采集的车内乘员信息是否符合所述共享使用协仪中的车内乘员信息规范性约束，具体方式为：
    比对所述车内乘员数量是否与所述乘员人数规范匹配；判断所述乘员行为是否与所述车内乘员的行为规范匹配；分析所述驾驶员的驾驶行为是否与所述驾驶员的安全驾驶行为规范匹配；
    若上述任一项的结果为不匹配，则判断所述车内乘员信息不符合所述车内乘员信息规范性约束。
  9. 根据权利要求6所述的服务器，其特征在于，所述处理器执行所述根据车内乘员信息的不符合程度控制所述车辆执行相应的操作，具体方式为：
    当不符合程度为轻微时，控制车辆发出警示信息；
    当不符合程度为中等时，控制车辆发出警示信息并减速；
    当不符合程度为严重时，控制车辆减速并行驶到安全区域时锁死发动机停车处理。
  10. 根据权利要求6-9任一项所述的方法，其特征在于，所述服务器为区块链的节点服务器，在所述接收车辆的共享使用协议之后，所述处理器调用所述存储器中存储的所述可执行程序代码，还执行如下步骤：
    将所述共享使用协议以智能合约的形式登记在区块链中并全网公布。
PCT/CN2018/085874 2018-01-30 2018-05-07 一种车辆共享方法及服务器 WO2019148683A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810089597.X 2018-01-30
CN201810089597.XA CN108447186A (zh) 2018-01-30 2018-01-30 一种车辆共享方法及服务器

Publications (1)

Publication Number Publication Date
WO2019148683A1 true WO2019148683A1 (zh) 2019-08-08

Family

ID=63191146

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085874 WO2019148683A1 (zh) 2018-01-30 2018-05-07 一种车辆共享方法及服务器

Country Status (2)

Country Link
CN (1) CN108447186A (zh)
WO (1) WO2019148683A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110852851A (zh) * 2019-11-14 2020-02-28 腾讯科技（深圳）有限公司 基于区块链的交通工具共享方法、装置及可读存储介质
CN112419733A (zh) * 2020-10-16 2021-02-26 杭州智行星科技有限公司 一种用户不规范停车的检测方法、装置、设备和存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109272379A (zh) * 2018-08-27 2019-01-25 广东工业大学 一种基于区块链的共享汽车监管方法和装置
WO2020051730A1 (en) * 2018-09-10 2020-03-19 Telefonaktiebolaget Lm Ericsson (Publ) Methods and devices for shared vehicle management
CN111976651A (zh) * 2019-05-22 2020-11-24 上海博泰悦臻网络技术服务有限公司 用车管理方法、用车管理服务器及用车管理终端
CN113098745B (zh) * 2020-01-08 2023-06-02 广州汽车集团股份有限公司 一种车内信息共享方法、系统及汽车

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1172768A2 (en) * 2000-06-28 2002-01-16 Honda Giken Kogyo Kabushiki Kaisha Method for efficient vehicle allocation in vehicle sharing system
US20110288891A1 (en) * 2010-05-03 2011-11-24 Gettaround, Inc. On-demand third party asset rental platform
CN202353708U (zh) * 2011-10-08 2012-07-25 张毅 行车安全记录装置
US20130325521A1 (en) * 2012-05-29 2013-12-05 Akhtar Jameel Shared vehicle rental system including vehicle availability determination
CN103810629A (zh) * 2012-11-07 2014-05-21 福特全球技术公司 用于个人车辆租用的资信证明核对和授权方案
CN103810630A (zh) * 2012-11-07 2014-05-21 福特全球技术公司 个人车辆租用的硬件和控制
CN103813262A (zh) * 2012-11-07 2014-05-21 福特全球技术公司 实现微业务移动汽车无线通信系统
CN105100189A (zh) * 2014-05-16 2015-11-25 福特全球技术公司 用于车辆计算系统与社交媒体网站进行通信的方法和系统
CN106575454A (zh) * 2014-06-11 2017-04-19 威尔蒂姆Ip公司 基于生物特征信息帮助用户访问车辆的系统和方法
CN107563846A (zh) * 2017-08-10 2018-01-09 深圳市易成自动驾驶技术有限公司 共享车辆管理方法、服务器、系统和计算机可读存储介质

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1172768A2 (en) * 2000-06-28 2002-01-16 Honda Giken Kogyo Kabushiki Kaisha Method for efficient vehicle allocation in vehicle sharing system
US20110288891A1 (en) * 2010-05-03 2011-11-24 Gettaround, Inc. On-demand third party asset rental platform
CN202353708U (zh) * 2011-10-08 2012-07-25 张毅 行车安全记录装置
US20130325521A1 (en) * 2012-05-29 2013-12-05 Akhtar Jameel Shared vehicle rental system including vehicle availability determination
CN103810629A (zh) * 2012-11-07 2014-05-21 福特全球技术公司 用于个人车辆租用的资信证明核对和授权方案
CN103810630A (zh) * 2012-11-07 2014-05-21 福特全球技术公司 个人车辆租用的硬件和控制
CN103813262A (zh) * 2012-11-07 2014-05-21 福特全球技术公司 实现微业务移动汽车无线通信系统
CN105100189A (zh) * 2014-05-16 2015-11-25 福特全球技术公司 用于车辆计算系统与社交媒体网站进行通信的方法和系统
CN106575454A (zh) * 2014-06-11 2017-04-19 威尔蒂姆Ip公司 基于生物特征信息帮助用户访问车辆的系统和方法
CN107563846A (zh) * 2017-08-10 2018-01-09 深圳市易成自动驾驶技术有限公司 共享车辆管理方法、服务器、系统和计算机可读存储介质

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110852851A (zh) * 2019-11-14 2020-02-28 腾讯科技（深圳）有限公司 基于区块链的交通工具共享方法、装置及可读存储介质
CN112419733A (zh) * 2020-10-16 2021-02-26 杭州智行星科技有限公司 一种用户不规范停车的检测方法、装置、设备和存储介质
CN112419733B (zh) * 2020-10-16 2023-05-05 杭州智行星科技有限公司 一种用户不规范停车的检测方法、装置、设备和存储介质

Also Published As

Publication number Publication date
CN108447186A (zh) 2018-08-24

Similar Documents

Publication Publication Date Title
WO2019148683A1 (zh) 一种车辆共享方法及服务器
WO2019128028A1 (zh) 一种道路交通数据的记录方法及车载设备
KR102169754B1 (ko) 환경 센서 데이터를 통신 데이터와 병합하기 위한 방법, 시스템, 및 그 시스템의 사용 방법
EP3882878B1 (en) Emergency call based on vehicle-to-vehicle communication
US20230101216A1 (en) Providing roadside assistance to vehicles
CN108551445B (zh) 一种车辆共享方法及服务器
CN112446761A (zh) 用于使用区块链进行共乘的系统和方法
WO2019179373A1 (zh) 信息处理方法、相关设备及计算机存储介质
US11627612B2 (en) Method and apparatus for efficient vehicle data reporting
CN107517197A (zh) 一种基于人脸认证技术的汽车云管理的方法和系统
CN109859437A (zh) 一种报警方法及设备、系统
WO2018179536A1 (ja) 情報処理装置、情報処理方法、プログラムとそれを記憶した記録媒体
CN110191437A (zh) 一种紧急车辆认证方法及相关设备
CN116432911A (zh) 数据处理方法、装置及存储介质
WO2022048643A1 (zh) 车辆控制方法和装置、介质、设备、程序
WO2021169248A1 (zh) 控制车辆的方法和装置
JP7392598B2 (ja) ログ管理装置及びセキュリティ攻撃検知・分析システム
CN112839064A (zh) 车辆的智能控制方法及装置
CN106162938B (zh) 一种信息处理方法和第一电子设备
WO2018179630A1 (ja) 情報処理装置、情報処理方法及びプログラム
CN219761329U (zh) 车辆通信系统及车辆
US20230094217A1 (en) System and method for providing information relating to a vehicle and/or a driver of a vehicle to an occupant of another vehicle
KR102425980B1 (ko) 서비스 맞춤형 v2x 지원 시스템 및 방법
US20230389095A1 (en) Enhanced wireless connectivity
CN117978502B (zh) 基于车联网技术的车辆数据安全管理方法及系统

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: 18904083

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: 18904083

Country of ref document: EP

Kind code of ref document: A1