WO2015085798A1 - 交通工具系统控制方法以及控制系统 - Google Patents

交通工具系统控制方法以及控制系统 Download PDF

Info

Publication number
WO2015085798A1
WO2015085798A1 PCT/CN2014/085765 CN2014085765W WO2015085798A1 WO 2015085798 A1 WO2015085798 A1 WO 2015085798A1 CN 2014085765 W CN2014085765 W CN 2014085765W WO 2015085798 A1 WO2015085798 A1 WO 2015085798A1
Authority
WO
WIPO (PCT)
Prior art keywords
program
application system
security
driving
running
Prior art date
Application number
PCT/CN2014/085765
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 华为技术有限公司
Priority to EP14870624.5A priority Critical patent/EP3069949A4/en
Publication of WO2015085798A1 publication Critical patent/WO2015085798A1/zh
Priority to US15/180,572 priority patent/US20160288801A1/en

Links

Classifications

    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W60/00Drive control systems specially adapted for autonomous road vehicles
    • B60W60/005Handover processes
    • B60W60/0059Estimation of the risk associated with autonomous or manual driving, e.g. situation too complex, sensor failure or driver incapacity
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W30/00Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05DSYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
    • G05D1/00Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
    • G05D1/0055Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots with safety arrangements
    • G05D1/0061Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots with safety arrangements for transition from automatic pilot to manual pilot and vice versa
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60KARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60KARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • B60K35/10Input arrangements, i.e. from user to vehicle, associated with vehicle functions or specially adapted therefor
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60KARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • B60K35/20Output arrangements, i.e. from vehicle to user, associated with vehicle functions or specially adapted therefor
    • B60K35/29Instruments characterised by the way in which information is handled, e.g. showing information on plural displays or prioritising information according to driving conditions
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60RVEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R16/00Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
    • B60R16/02Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
    • B60R16/023Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
    • B60R16/0231Circuits relating to the driving or the functioning of the vehicle
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W30/00Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units
    • B60W30/18Propelling the vehicle
    • B60W30/18009Propelling the vehicle related to particular drive situations
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W30/00Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units
    • B60W30/18Propelling the vehicle
    • B60W30/182Selecting between different operative modes, e.g. comfort and performance modes
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W60/00Drive control systems specially adapted for autonomous road vehicles
    • B60W60/005Handover processes
    • B60W60/0051Handover processes from occupants to vehicle
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60KARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K2360/00Indexing scheme associated with groups B60K35/00 or B60K37/00 relating to details of instruments or dashboards
    • B60K2360/18Information management
    • B60K2360/186Displaying information according to relevancy
    • B60K2360/1868Displaying information according to relevancy according to driving situations
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60KARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K2360/00Indexing scheme associated with groups B60K35/00 or B60K37/00 relating to details of instruments or dashboards
    • B60K2360/18Information management
    • B60K2360/195Blocking or enabling display functions
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2540/00Input parameters relating to occupants
    • B60W2540/229Attention level, e.g. attentive to driving, reading or sleeping

Definitions

  • the present invention relates to the field of system control, and more particularly to a vehicle system control method, a related driving system, a related application system, and a vehicle control system. Background technique
  • Embodiments of the present invention provide a vehicle control method, a related driving system, a related application system, and an associated vehicle control system, which can improve driving safety and ensure driving safety.
  • a first aspect of the embodiments of the present invention provides a vehicle control method, including:
  • the driving system receives a first signal from an application system for controlling the vehicle Application within
  • the driving system determines a type of a program running in the application system according to the first signal
  • the driving system determines that the current driving mode is the manual driving mode, the driving system switches the current driving mode to the automatic driving mode.
  • the non-security program includes: a program or a video playing program that requires a user to input information.
  • a second aspect of the embodiments of the present invention provides a vehicle control method, including:
  • An application system receives a second signal from a driving system for controlling an application within the vehicle
  • the application system determines a current driving mode according to the second signal
  • the application system determines that the running program is a non-safety type program, the application system switches the non-safety type program.
  • the non-security program includes: a program or a video playing program that requires a user to input information.
  • the application system switching the non-security application includes:
  • the application system closes the non-security class program, or the application system switches the non-security class program to the background.
  • the application system determines that the running program is a non-security program.
  • the application system acquires a security identifier of the running program
  • the application system determines whether the running program is a non-secure type program according to the security identifier.
  • the security identifier of the application system that is obtained by the application system includes: The application system acquires an installation file of the program when the program is installed, and obtains the security identifier from the installation file;
  • the application system sets a security identifier of the program when the program is installed; or, when the application system installs the program, acquires a security identifier of the program input by a user.
  • the acquiring, by the application system, the security identifier of the running program includes:
  • the application system receives an operation signal of the program
  • the application system generates a security identification of the program.
  • a third aspect of the embodiments of the present invention provides a driving system, including:
  • a first receiving module configured to receive a first signal from an application system
  • a first determining module configured to determine, according to the first signal received by the first receiving module, a type of a program that is running in the application system
  • a first switching module configured to switch the current driving mode to the automatic driving mode if the first determining module determines that the running program is a non-safety program and the current driving mode is manual driving.
  • a fourth aspect of the embodiments of the present invention provides an application system, including:
  • a second receiving module configured to receive a second signal from the driving system
  • a second determining module configured to determine a current driving mode according to the second signal received by the second receiving module
  • a second switching module configured to switch the non-security class program if the second determining module determines that the current driving mode is a manual driving mode, and the running program is a non-safety type program.
  • the second switching module includes:
  • a determining submodule configured to determine, according to the security identifier obtained by the obtaining submodule, whether the running program is a non-security program
  • a switching submodule for switching the non-security class program is specifically configured to:
  • the acquiring submodule includes: Unit, used to obtain an installation file of the program to be installed;
  • the second obtaining unit is configured to obtain a security identifier of the installed program.
  • the acquiring submodule includes: a receiving unit, An operation signal for receiving the program;
  • An identification unit configured to generate a security identifier of the program.
  • a fifth aspect of the embodiments of the present invention provides a vehicle control system including an application system and a driving system provided by the third aspect of the embodiments of the present invention.
  • a sixth aspect of the embodiments of the present invention provides a vehicle control system, including a driving system, and the implementation of any of the first to fourth implementations of the fourth aspect or the fourth aspect of the embodiments of the present invention.
  • the driving system receives the first signal from the application system, and further determines whether the running program in the application system is a non-safe program. If yes, and the current driving mode is manual driving, the driving system switches. The current driving mode is automatic driving.
  • the application system receives a second signal from the driving system to determine whether the current driving mode is manual driving. If the program that is running is a non-safety program, the application system switches the running program.
  • the driving mode must be automatic driving.
  • the running program must not be a non-safety program. It avoids or reduces the risk of distraction when the driver uses non-safety programs during manual driving and ensures driving safety.
  • FIG. 1 is a flow chart of an embodiment of a vehicle system control method according to an embodiment of the present invention
  • 2 is a flow chart of another embodiment of a method for controlling a vehicle system according to an embodiment of the present invention
  • FIG. 3 is a flow chart of another embodiment of a method for controlling a vehicle system according to an embodiment of the present invention
  • FIG. 5 is a flowchart of an embodiment of a method for generating a security identifier according to an embodiment of the present invention
  • FIG. 6 is a flowchart of another embodiment of a vehicle system according to an embodiment of the present invention
  • FIG. 7 is a structural diagram of an embodiment of a driving system according to an embodiment of the present invention
  • FIG. 8 is a structural diagram of another embodiment of a driving system according to an embodiment of the present invention
  • FIG. 10 is a structural diagram of another embodiment of an application system according to an embodiment of the present invention
  • FIG. 11 is a structural diagram of another embodiment of an application system according to an embodiment of the present invention
  • FIG. 13 is a structural diagram of another embodiment of an application system according to an embodiment of the present invention
  • FIG. 14 is a vehicle control according to an embodiment of the present invention.
  • Embodiments of the present invention provide a vehicle system control method that can improve driving safety.
  • the present invention also proposes related driving systems, application systems, and vehicle control systems, which will be separately described below.
  • FIG. 1 for the basic flow of a vehicle control method provided by an embodiment of the present invention, which mainly includes the steps:
  • the driving system receives the first signal from the application system
  • the vehicle's control system generally includes a driving system and an application system.
  • the driving system is used to control the driving of the vehicle, and the application system is used to control the applications within the vehicle.
  • the driving system can receive a first signal from the application system, the first signal being used to indicate the type of program being run in the application system.
  • the driving system can receive the first signal at a plurality of time points.
  • the first signal when the application system switches the program, the first signal is generated, and the first signal indicates the type of the program running in the application system after the application system switching program, and the driving system receives the first signal;
  • the first signal is automatically received at regular intervals to detect the type of program being run in the application system at this time.
  • the driving system can also use other methods to receive the first signal from the application system, which is not specifically limited herein.
  • the driving system determines, according to the first signal, a type of a program that is running in the application system; after acquiring the first signal, the driving system determines, according to the first signal, a type of a program that is running in the application system.
  • the types of programs described here mainly include: security programs and non-security programs. If a program attracts more attention from the driver during normal operation, the program is considered to be a non-safety program. If a program does not attract more attention from the driver during normal operation, it is considered a safety program.
  • the specific method of distinguishing between the security program and the non-security program will be described in detail below, and is not specifically limited herein.
  • the driving system switches the current driving mode to the automatic driving mode.
  • the driving system determines, according to the first signal, that the program that the application system is running is a non-safety program, and the current driving mode of the driving system is the manual driving mode, the driver is driving at a time when the attention is dispersed. Operation, security is not guaranteed. Therefore, the driving system switches the current driving mode to the automatic driving mode.
  • the driving system receives the first signal from the application system, and further determines whether the program running in the application system is a non-security program. If yes, and the current driving mode is manual driving, the driving system switches the current driving mode to automatic driving.
  • a security program there are many methods for distinguishing between a security program and a non-security program.
  • the program is considered to be a non-safe program, such as a video player, or a program that requires the user to input information;
  • the program is considered to be a safety program such as a radio receiving program, a music playing program, and the like.
  • an application can classify a program installed on a vehicle into three levels: a high-risk program, an intermediate program, and a low-risk program.
  • the application system sets the high-risk program as a non-safe program, and the intermediate program and the low-risk program as a safety program; when the car is driving on a dense road At high speeds, the application sets high-risk programs and intermediate programs as non-safe programs and low-risk programs as security programs.
  • the application system can also classify the programs installed in the vehicle into more levels.
  • the distinction between the security class and the non-safety class can also have other standards, which are not specifically limited herein.
  • the application system determines whether the program is a non-safe class is first completed in the application system, and the application system generates a first signal according to the judgment result, and the driving system determines whether the program is based on the first signal.
  • Non-safety program How the application system determines whether the program is a non-safety type program will be described in detail in the following embodiments, and is not specifically limited herein.
  • the driving system can control the manual driving mode and the automatic driving mode, and the application system can control the operation of the application.
  • the driver drives the car while driving the MP3 program in the app to listen to music.
  • the driving system of the car can receive the signal of the MP3 program running.
  • the MP3 program is considered a safety program, so the driving system still allows the driver to manually drive the car.
  • the driver After driving for a while, the driver opens the video player in the app to watch the movie. In this car, the video player is considered a non-security program.
  • the application runs the Video program, it generates a first signal indicating that the non-safe class program is running.
  • the application system sends the first signal to the information channel between the application system and the driving system, and the driving system receives the first signal to determine that the running program in the application system is a non-safety program. Since the driver is currently driving manually, the driving system switches the manual driving mode to the automatic driving mode, thereby automatically driving the car.
  • the above embodiment describes that the driving system switches the driving mode according to the signal of the application system to ensure Driving safety.
  • the following embodiment provides a vehicle system control method for an application system to switch programs according to signals of a driving system. The basic flow is shown in FIG. 2:
  • the application system receives a second signal from the driving system.
  • the vehicle's control system typically includes a driving system and an application system, the driving system is used to control the driving of the vehicle, and the application system is used to control the applications within the vehicle. There is an information channel between the driving system and the application system for information interaction.
  • the application system can receive a second signal from the driving system, the second signal being used to indicate the current driving mode of the driving system.
  • the application system can receive the second signal at a plurality of time points. For example: when the driving system switches the driving mode, a second signal is generated, which is used to indicate the driving mode after the driving system switches the driving mode, and the application system receives the second signal; or the application system is fixed every time. The time automatically receives the second signal to detect the driving mode of the current driving system.
  • the application system can also use other methods to receive the second signal from the driving system, which is not specifically limited herein.
  • the application system determines a current driving mode according to the second signal.
  • the current driving mode of the driving system is determined according to the second signal.
  • the driving modes here mainly include: manual driving mode or automatic driving mode.
  • the application system switches the non-safety type program.
  • the application system determines that the current driving mode is the manual driving mode according to the second signal, and the running program in the application system is a non-safety program, the driver is driving at a time when the attention is dispersed, and the safety is safe. Sex is not guaranteed. Therefore, the application system switches the currently running non-safety program to ensure that the driver's attention is not dispersed and the driving safety is improved.
  • the application system receives the second signal from the driving system to determine whether the current driving mode is manual driving. If the program that is running is a non-safety program, the application system switches the running program. In this way, when the driving mode is manual driving, the running program must not be an unsafe program, which reduces the distraction of the driver during manual driving caused by the non-safety program, and improves the driving safety. Sex.
  • the application system there are many methods for the application system to switch the non-security program, such as: an application system. Close the non-security class program, or switch the non-security class program to the background after the application system. It is also possible to forcibly close some functions of the non-safety program for the application system, and then set the non-security program that has closed some functions as a security program and continue to run. Other methods may be used for the application system to switch non-security programs, and are not specifically limited herein.
  • the application system receives a second signal from the driving system.
  • the application system determines a current driving mode according to the second signal.
  • Steps 301 and 302 are basically the same as 201 and 202 in the previous embodiment, and are not described herein.
  • the application system obtains a security identifier of the running program.
  • the application In order to determine the security category of a running program, the application first needs to obtain the security identity of the running program. This security identifier is used to indicate the security category of the running program. The security category is used to indicate whether the program is a non-security class.
  • the time at which the application system obtains the security identifier may be more than two, including the security identifier of the application obtained by the application system when the program is installed, or the security identifier of the application obtained by the application system when the program is running.
  • the application system may also obtain the security identifier of the program at other times, which is not specifically limited herein.
  • the security identifier of the program After the security identifier of the program is obtained in the application system, it can be saved in the ARF.
  • Application Register File can also be saved in other locations or not, and is not specified here.
  • the application system determines, according to the security identifier, whether the running program is a non-security class program.
  • the application system determines whether the running program is a non-security program according to the correspondence between the obtained security identifier and the security category. Wherein, if the security identifier of the program in the application system is stored in the ARF, the application system reads the security identifier of the running program from the ARF, and determines whether it is a security class program according to the security identifier.
  • the application system switches the non-security class program.
  • Step 305 is substantially the same as step 203 in the previous embodiment, and is not described herein.
  • steps 301, 302 and steps 303, 304 are not limited, and steps 303, 304 may also be before steps 301, 302.
  • This embodiment details how the application system determines the security category of a running program.
  • the application first obtains the security identity of the running program and then determines whether the running program is a non-security class based on the security identity.
  • the time at which the application system obtains the security identifier of the program may be when the program is installed or when the program is running.
  • the above embodiment gives a method for the application system to judge the security category of the running program, and the following embodiment will further explain the security identification step of the application in which the application system obtains the running program.
  • the application system can obtain the security identifier of the program when the running program is installed, as shown in Figure 4:
  • the application system receives a second signal from the driving system.
  • the application system determines a current driving mode according to the second signal.
  • Steps 401 and 402 are basically the same as 301 and 302 in the previous embodiment, and are not described herein.
  • the application system obtains an installation file of the program to be installed.
  • the application system can obtain the security identity of the program when the program is installed.
  • the application system obtains the installation file of the program to be installed.
  • the installation program can be installed according to the installation file.
  • the installation file is an installation package, and the application system installs the program according to the installation package.
  • the application system can also use the image installation method to install the program.
  • the image installation is a general program installation method, and the application system can obtain the installation files of one or more programs from the external source system in batches and complete the installation through the mirror operation, so that the application system can be conveniently installed in batches. Source system application.
  • the installer can also use other methods, which are not specifically limited here.
  • the application system obtains a security identifier of the installed program.
  • the application system obtains the security identifier of the installed program, and the method includes: obtaining, by the application system, the security identifier of the installed program from the installation file, or the security identifier of the installed program after the application system setting, or The application system obtains the security identifier of the installed program input by the user.
  • the application system may also use other methods to obtain the security identifier, which is not specifically limited herein.
  • the security identifier of the installed program obtained by the application system from the installation file includes: The program generates a security identifier during the compilation process, and saves the file in the installation file.
  • the application obtains the security identity from the installation file.
  • This embodiment also provides a method for generating a security identifier during the compilation process, as shown in FIG. 5:
  • the compiler identifies whether there is a preset code or a code set in the code of the program to be compiled or the code of the compiled program;
  • the application in the application system will generally be compiled and linked. This method is to obtain the security identifier of the program during the compilation phase.
  • the compiler In order to obtain the security identifier, the compiler first needs to identify whether there is a preset code or a code set in the code of the program to be compiled or the code of the compiled program.
  • the compiler may be located in the application system or may be independent of the application system.
  • the code of the program to be compiled is the source code, and the code of the compiled program is the target code.
  • the source code and the target code are only different in form, and the two are equivalent in function, so the compiler can achieve any purpose by identifying any one of the codes.
  • the preset code or code set may correspond to a certain function of the program, such as a video playing function, a function of acquiring information input by the user, etc., and the function may make the program distract the driver's attention during the running process.
  • the preset code or code set can also represent a mandatory security category feature that the programmer can force to set the security category of by writing the preset code or code set in the program code during programming. If there is a preset code in the code of the program to be compiled or the code of the compiled program, it is considered that the program will distract the driver during the running process.
  • the program is a non-safety program, and step 502 is executed. If there is no preset code in the code of the compiled program code or the compiled program, it is considered that the program does not distract the driver too much during the running process, and step 503 is executed.
  • the preset code refers to a preset sentence, a segment or a class of code.
  • a function such as DialogBox or InputBox indicates that the user's input needs to be acquired, and can be used as a preset code; Say, in machine instructions indicate that you need to get the user's input, or as a preset code.
  • the types of preset codes include not only DialogBox, InputBox, etc., but also other codes, which are not specifically limited here.
  • the preset code can also be a custom code that the programmer writes when the program is written for the compiler to recognize.
  • the preset code set refers to a preset code that repeatedly appears multiple times.
  • the source code such as The InputBox function only appears once in the source code, which means that the program only needs the user to input the information once during the running process, and does not distract the user more attention.
  • the program can be considered as a security program. However, if there are multiple DialogBox and InputBox in the source code, it means that the program needs the user to input information multiple times during the running process, which will distract the user more attention.
  • the program can be considered as a non-security program.
  • the compiler generates a security identifier corresponding to the non-security class program.
  • the program is a non-safe program, and the compiler generates a non-safe program. Corresponding security identifier.
  • the compiler generates a security identifier corresponding to the security class program.
  • the program is a security program, and the compiler generates security.
  • the security identifier corresponding to the class program.
  • the compiler saves the generated security identifier.
  • the security identifiers produced in steps 502 and 503 can be saved in the Data Segments file, and the application system can obtain the security identifier from the Data Segments file in subsequent operations and save the information to the ARF.
  • the security identifier can also be saved in other locations, which is not specifically limited herein.
  • the user-defined code can also be a user-defined function, such as the SafetyClassfication () class function.
  • the function is called, which means that the security category of the program is forcibly set. This category can be either a security program or a non-security program.
  • the compiler recognizes a SafetyClassfication ( ) class function, it should generate a corresponding security ID based on the security class set by the function.
  • SafetyClassfication ( ) is only a name for this kind of function, and the functions of such functions can also have other naming methods, which are not limited here.
  • the method of generating the security identifier during the compilation process may be other methods than the method shown in FIG. 5, and is not limited herein.
  • the application system obtains the security identifier of the installed program from the installation file, and further includes: when the application system installs the program through the mirroring operation, obtains the installation file of the program to be installed from the source system, and obtains the security from the installation file.
  • Sexual identity As the result of the mirroring operation is to make the application system have the same programs and functions as the source system, as long as the security of a program is stored in the source system. Identification, when the program is mirrored and installed in the application system, the application system can obtain the security identifier of the program.
  • the application system sets the security identifier of the installed program to include:
  • the application system sets a default security identifier for the installed program during the installation process.
  • the application system may set the security identifier of the installed program to the security identifier corresponding to the non-security program, or set the security identifier of the installed program to the identifier corresponding to the security program, or may be different.
  • the program sets different security identifiers, which are not specifically limited here.
  • the security identifier of the installed program that the application system obtains the user input includes: The application system requires the user to input the security category of the installed program in the process of installing the program, and the application system selects the post-installation program according to the user input.
  • the security category generates a corresponding security ID.
  • the security identifier can be saved. In this way, when the security identifier needs to be used, the application system can directly obtain the security identifier from the storage location of the security identifier.
  • the application system determines, according to the security identifier, whether the running program is a non-security class program
  • the application system switches the non-safety type program.
  • Steps 405 and 406 are substantially the same as steps 304 and 305 in the previous embodiment, and are not described herein.
  • the steps of the steps 401, 402 and the steps 403 to 405 are not limited in this embodiment, and the steps 403 to 405 may also be before the steps 401 and 402.
  • This embodiment describes in detail a method for the application system to obtain a security identifier when the program is installed.
  • the application system obtains an installation file of the program to be installed, installs the program to be installed, and obtains a security identifier of the program after installation.
  • the application system can determine the security category of the running program according to the generated security identifier. If the current driving mode is the manual driving mode, and the running program is a non-security program, the application system Switching the non-safety program to ensure that when the driving mode is manual driving, the program running in the application system must be a safety program, which reduces the distraction of the driver's attention by the non-safety program and improves driving safety.
  • the application system receives a second signal from the driving system.
  • the application system determines a current driving mode according to the second signal.
  • the steps 601 and 602 are basically the same as the 501 and 502 in the previous embodiment, and the operation signal of the application system receiving program is not described herein;
  • the application system not only obtains the security identifier of the program when the program is installed, but also obtains the security identifier of the program when the program is running. Before running the program, the application receives the running signal of the program and prepares to run the program.
  • the application system generates a security identifier of the program.
  • the application system After the application system receives the running signal of the program, it can generate the security identifier of the program.
  • the specific method for the security identifier of the application system at this time is more than one, including: The application system identifies whether there is a preset code or a code set in the code of the program to be run, and if so, it considers that the program has certain The function distracts the driver's attention, and the application system generates a security identifier corresponding to the non-safety program; if it does not exist, it is considered that the program does not have the function of distracting the driver's attention, and the application system generates a security program corresponding to the function. Security identity.
  • the meaning of the preset code or code set is basically the same as the preset code or code set in step 403, and is not mentioned here.
  • the application system may determine whether the security identifier of the to-be-running program has been obtained before the step, and if it is determined that the security identifier of the to-be-running program is not obtained, perform the step; if it is determined that the program to be run is obtained, For the security identification, you do not need to perform this step.
  • the application system may save the security identifier after generating the security identifier of the to-be-run program. In this way, the application system only needs to generate the security identifier when the program is run for the first time. When the program is run for the second time or later, the security identifier can be obtained directly from the storage location of the security identifier.
  • this step is only limited to be implemented after the application system receives the running signal of the program.
  • the application system may run the program before, or after the application system runs the program, it is not specifically limited herein.
  • the application system determines, according to the security identifier, whether the program is a non-security program
  • the application system switches the non-security class program.
  • Steps 605 and 606 are substantially the same as steps 506 and 507 in the previous embodiment, and are not described herein.
  • the steps 601, 602 and the steps 603 to 605 are not limited in this embodiment, and the steps 603 to 605 may also be before the steps 601 and 602.
  • This embodiment describes in detail a method for the application system to obtain a security identifier when the program is running.
  • the application system receives the running signal of the program and then generates a security identifier of the program. After the security identifier is generated, the application system can determine the security category of the running program according to the generated security identifier. If the current driving mode is the manual driving mode, and the running program is a non-security program, the application system Switching the non-safety program to ensure that when the driving mode is manual driving, the program running in the application system must be a safety program, which reduces the distraction of the driver's attention by the non-safety program and improves driving safety.
  • the driving system can control the manual driving mode and the automatic driving mode, and the application system can control the operation of the application.
  • the driver has to install the Video Player in the application system. First, the driver copies the installation file of the video player from the USB flash drive to the application system. When the application installs the program, the driver is required to enter the security category of the program. The driver thinks that the video player will attract too much attention and attention during the running process, so enter: Non-safety program.
  • the application system receives the information input by the driver and generates a security identifier corresponding to the non-security program, and the security identifier is stored in the APF of the application system. After that, the driver turns on the automatic driving mode to drive the car, and simultaneously opens the video player in the application to watch the movie.
  • the driving system After driving for a while, the car traveled to a more complex road, and the driver switched the automatic driving mode to the manual driving mode to manually drive the car.
  • the driving system now generates a second signal indicating that the current driving mode is manual driving and transmits the second signal to the information channel between the application system and the driving system.
  • the application system receives the second signal, and determines that the current driving mode is manual driving based on the second signal. Since the Video Player is a non-secure program, the application system forcibly closes the Video Player.
  • the invention also provides a driving system 700 for performing the work described in the above embodiments Yes, the basic structure is shown in Figure 7:
  • the first receiving module 701 is configured to receive a first signal from the application system.
  • the first determining module 702 is configured to determine, according to the first signal received by the first receiving module 701, a type of a program that is running in the application system;
  • the first switching module 703 is configured to switch the current driving mode to the automatic driving mode when the first determining module 702 determines that the running program is a non-safety program and the current driving mode is manual driving.
  • the first receiving module 701 receives the first signal from the application system, and the first determining module 702 determines whether the running program in the application system is a non-security program. If yes, and the current driving mode is manual driving, the first switching module 703 switches the current driving mode to automatic driving. In this way, when the vehicle application system is running a non-safety program, the driving mode must be automatic driving. . It avoids the risk of distraction when the driver uses non-safety programs and ensures driving safety.
  • the driving system can control the manual driving mode and the automatic driving mode, and the application system can control the operation of the application.
  • the driver drives the car while driving the MP3 program in the app to listen to music.
  • the driving system of the car can receive the signal of the MP3 program running.
  • the MP3 program is considered a safety program, so the driving system still allows the driver to manually drive the car.
  • the driver After driving for a while, the driver opens the video player in the app to watch the movie. In this car, the video player is considered a non-security program.
  • the application runs the Video program, it generates a first signal indicating that the non-safe class program is running.
  • the application system sends the first signal to an information channel between the application system and the driving system, the first receiving module 701 in the driving system receives the first signal, and the first determining module 702 determines a running program in the application system.
  • the first switching module 703 Since the driver is currently performing manual driving, the first switching module 703 switches the manual driving mode to the automatic driving mode, thereby automatically driving the vehicle.
  • the driving system in the embodiment of the present invention is described above from the perspective of a unitized functional entity.
  • the driving system in the embodiment of the present invention is described below from the perspective of hardware processing, please refer to the figure. 8.
  • Another embodiment of the driving system 800 in the embodiment of the present invention includes:
  • the input device 801, the output device 802, the processor 803, and the memory 804 (wherein the number of processors 803 in the driving system 800 may be one or more, and one processor 803 in Fig. 8 is taken as an example;).
  • the input device 801, the output device 802, the processor 803, and the memory 804 may be connected by a bus or other means, wherein the bus connection is taken as an example in FIG.
  • the processor 803 is configured to perform the following steps by calling an operation instruction stored in the memory 804:
  • the running program is a non-safety type program
  • the driving system determines that the current driving mode is the manual driving mode
  • the current driving mode is switched to the automatic driving mode.
  • the driving system 800 also performs the following steps:
  • the present invention also provides an application system 900 for performing the functions described in the above embodiments.
  • the basic structure is shown in Figure 9:
  • a second receiving module 901, configured to receive a second signal from the driving system
  • the second determining module 902 is configured to determine a current driving mode according to the second signal received by the second receiving module 901;
  • the second switching module 903 is configured to switch the non-security type program when the second determining module 902 determines that the current driving mode is the manual driving mode, and the running program is a non-safety type program.
  • the second receiving module 901 receives the second signal from the driving system, and the second determining module 902 determines whether the current driving mode is manual driving. If so, and the running program is a non-safety type program, the second switching module 903 switches the running program. In this way, it is ensured that when the driving mode is manual driving, the running program must not be a non-safety program, which reduces the distraction of the driver during manual driving caused by the non-safety program and improves the driving safety. Sex.
  • the application system 1000 includes:
  • the second receiving module 1001 is configured to receive a second signal from the driving system;
  • the second determining module 1002 is configured to determine a current driving mode according to the second signal received by the second receiving module 1001.
  • the second switching module 1003 is configured to switch the non-security type program when the second determining module 1002 determines that the current driving mode is the manual driving mode, and the running program is a non-safety type program.
  • the second switching module 1003 includes:
  • An obtaining submodule 10031 configured to obtain a security identifier of a running program
  • the determining sub-module 10032 is configured to determine, according to the security identifier acquired by the obtaining sub-module 10031, whether the running program is a non-security program;
  • the switching submodule 10033 is configured to switch the non-security class program.
  • This embodiment details how the application system determines the security category of a running program.
  • the obtaining submodule 10031 first obtains the security identifier of the running program, and then determines whether the submodule 10032 determines whether the running program is a non-security program according to the security identifier.
  • the time at which the application system obtains the security identifier of the program may be when the program is installed or when the program is running.
  • the above embodiment provides an application system that can implement a security category for determining a running program.
  • the following embodiment will further explain the acquisition sub-module 10031 in the application system.
  • the application system 1100 includes:
  • a second receiving module 1101, configured to receive a second signal from the driving system
  • a second determining module 1102 configured to determine a current driving mode according to the second signal received by the second receiving module 1101;
  • the second switching module 1103 is configured to switch the non-security type program when the second determining module 1102 determines that the current driving mode is the manual driving mode, and the running program is a non-safety type program.
  • the second switching module 1103 includes:
  • the obtaining submodule 11031 is configured to obtain a security identifier of a running program, where the obtaining submodule 11031 includes:
  • the first obtaining unit 110311 is configured to acquire an installation file of the program to be installed.
  • a second obtaining unit 110312 configured to acquire a security identifier of the program after the program installation unit 110311 is installed;
  • the determining sub-module 11032 is configured to determine, according to the security identifier acquired by the second obtaining unit 110312, whether the running program is a non-security program;
  • the switching submodule 11033 is configured to switch the non-security class program.
  • This embodiment describes in detail an application system that acquires a security identifier when the program is installed.
  • the first obtaining unit 110311 acquires an installation file of the program to be installed, and then the second obtaining unit 110312 acquires a security identifier of the installed program.
  • the determining sub-module 11032 can determine the security category of the running program according to the generated security identifier. If the current driving mode is the manual driving mode, and the running program is a non-security program, The switching sub-module 11033 switches the non-safety program to ensure that when the driving mode is manual driving, the program running in the application system must be a safety program, which reduces the distraction of the driver's attention by the non-safety program and improves driving. safety.
  • the above embodiment describes an application system for obtaining a security identifier when the program is installed.
  • the following embodiment will describe an application system for obtaining a security identifier when the program is running. Referring to FIG. 12, the application system is described.
  • the 1200 system includes:
  • a second receiving module 1201, configured to receive a second signal from the driving system
  • the second determining module 1202 is configured to determine a current driving mode according to the second signal received by the second receiving module 1201;
  • the second switching module 1203 is configured to switch the non-security class program when the second determining module 1202 determines that the current driving mode is the manual driving mode, and the running program is a non-safety type program.
  • the second switching module 1203 includes:
  • the obtaining sub-module 12031 is configured to obtain a security identifier of the running program, where the obtaining sub-module 12031 includes:
  • the receiving unit 120311 is configured to receive an operation signal of the program.
  • the determining sub-module 12032 is configured to determine, according to the security identifier generated by the identifying unit 120312, whether the running program is a non-security program;
  • the switching submodule 12033 is configured to switch the non-security class program.
  • This embodiment describes an application system in detail, which can obtain a security identifier when the program is running.
  • the receiving unit 120311 receives the running signal of the program, and then the identifying unit 120312 generates a security identifier of the program.
  • the determining sub-module 12032 can determine the security category of the running program according to the generated security identifier, if the current driving mode is manual driving.
  • the mode, and the running program is a non-safety type program
  • the switching sub-module 12033 switches the non-safety type program to ensure that when the driving mode is manual driving, the program running in the application system must be a safety program, which reduces the non- The safety program distracts the driver's attention and improves driving safety.
  • the driving system can control the manual driving mode and the automatic driving mode, and the application system can control the operation of the application.
  • the driver has to install the Video Player in the application system. First, the driver copies the installation file of the Video player from the USB flash drive to the first acquisition unit 110311 of the application system; afterwards, when the application system installs the program, the second acquisition unit 110312 requests the driver to input the security of the program. Sex category. The driver thinks that the video player will attract too much attention and attention during the running process, so enter: Non-safety program.
  • the second obtaining unit 110312 receives the information input by the driver, generates a security identifier corresponding to the non-security program, and saves the security identifier in the APF of the application system. After that, the driver turns on the automatic driving mode to drive the car, and simultaneously opens the video player in the application to watch the movie.
  • the driving system After driving for a while, the car traveled to a more complex road, and the driver switched the automatic driving mode to the manual driving mode to manually drive the car.
  • the driving system now generates a second signal indicating that the current driving mode is manual driving and transmits the second signal to the information channel between the application system and the driving system.
  • the second receiving module 1101 of the application system receives the second signal, and the second determining module 1102 determines, according to the second signal, that the current driving mode is manual driving. Since the judging sub-module 11032 judges that the video playing program is a non-secure type program, the switching sub-module 11033 forcibly closes the video playing program.
  • the application system in the embodiment of the present invention is described above from the perspective of a unitized functional entity.
  • the application system in the embodiment of the present invention is described from the perspective of hardware processing. Referring to FIG. 13, the application system in the embodiment of the present invention is described.
  • Another embodiment of 1300 includes:
  • the input device 1301, the output device 1302, the processor 1303, and the memory 1304 (wherein the number of processors 1303 in the application system 1300 may be one or more, and one processor 1303 in FIG. 13 is taken as an example).
  • the input device 1301, the output device 1302, the processor 1303, and the memory 1304 may be connected by a bus or other means, wherein Connection is an example.
  • the processor 1303 is configured to perform the following steps by calling an operation instruction stored in the memory 1304:
  • the current driving mode is the manual driving mode, and the application system determines that the running program is a non-safety type program, the non-safety type program is switched.
  • the application system 1300 also performs the following steps:
  • the above embodiment is an application system provided by the present invention.
  • the invention also provides a vehicle control system, the basic structure of which is shown in Figure 14:
  • the driving system is similar to the driving system shown in FIG. 7, and is not described here; 1402.
  • the application system is used to control the operation of the program in the application system.
  • the embodiment of the invention also provides a vehicle control system, as shown in FIG.
  • a driving system for controlling a driving mode of the vehicle
  • the application system is similar to the application system shown in FIG. 9 to FIG. 12, and details are not described herein again.
  • the disclosed systems and methods can be implemented in other ways.
  • the system embodiments described above are merely illustrative, examples.
  • the division of the unit is only a logical function division, and the actual implementation may have another division manner, for example, multiple units or components may be combined or may be integrated into another system, or some features may be ignored, or not. carried out.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect engagement or communication connection through some interface, module or unit, and may be in electrical, mechanical or other form.
  • the components displayed by the unit 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 storage medium.
  • 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 storage medium.
  • 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 storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Mechanical Engineering (AREA)
  • Transportation (AREA)
  • Automation & Control Theory (AREA)
  • Chemical & Material Sciences (AREA)
  • Combustion & Propulsion (AREA)
  • Human Computer Interaction (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Remote Sensing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Stored Programmes (AREA)
  • Traffic Control Systems (AREA)

Abstract

一种交通工具控制方法,包括:驾驶系统接收来自应用系统的第一信号、驾驶系统根据第一信号确定应用系统中正在运行的程序的类型、若正在运行的程序为非安全类程序,且当前驾驶模式为手动驾驶模式,则驾驶系统将当前驾驶模式切换为自动驾驶模式。另一种交通工具控制方法,包括:应用系统接收来自驾驶系统的第二信号、应用系统根据第二信号确定当前驾驶模式、若当前驾驶模式为手动驾驶模式,且正在运行的程序为非安全类程序,则应用系统切换该非安全类程序。本发明可以提高驾驶安全性。

Description

交通工具系统控制方法以及控制系统
本申请要求于 2013 年 12 月 13 日提交中国专利局、 申请号为 201310687888.6, 发明名称为 "交通工具系统控制方法以及控制系统" 的中国 专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及系统控制领域, 尤其涉及交通工具系统控制方法、相关驾驶系 统、 相关应用系统以及交通工具控制系统。 背景技术
随着科学技术的发展, 交通工具电子化越发普及, 交通工具的控制系统 中也引入了越来越多的应用程序。 以汽车为例,现阶段的许多汽车都安装有丰 富的应用程序, 可以实现许多功能, 如电台收听、 音乐播放、 视频通话等。 这 些程序使得驾驶员在驾驶交通工具的同时可以享受更多的服务,丰富了驾驶员 的驾驶体验。但是,这些程序在驾驶员的驾驶过程中的使用分散了驾驶员的注 意力, 导致驾驶员的驾驶安全得不到保障。
为了提高驾驶的安全性,现阶段许多交通工具都配备有自动驾驶功能,使 得该交通工具可以无需驾驶员而自动驾驶,以避免驾驶员在驾驶过程中注意力 分散而造成的驾驶风险。
但是, 现阶段的自动驾驶技术并不成熟, 不能完全替代手动驾驶。 在路面 情况复杂等许多情况下, 驾驶员仍需要将驾驶模式切换为手动驾驶。若此时驾 驶员正在使用上述程序, 则其注意力或视线仍然可能被分散, 驾驶安全仍然得 不到保障。 发明内容
本发明实施例提供了交通工具控制方法、相关驾驶系统、相关应用系统以 及相关的交通工具控制系统, 可以提高驾驶的安全性, 保障驾驶安全。
本发明实施例第一方面提供了一种交通工具控制方法, 包括:
驾驶系统接收来自应用系统的第一信号,所述应用系统用于控制交通工具 内的应用程序;
所述驾驶系统根据所述第一信号确定所述应用系统中正在运行的程序的 类型;
若所述正在运行的程序为非安全类程序,且所述驾驶系统确定当前驾驶模 式为手动驾驶模式, 则所述驾驶系统将当前驾驶模式切换为自动驾驶模式。
结合本发明实施例的第一方面,本发明实施例的第一方面的第一种实现方 式中, 所述非安全类程序包括: 需要用户输入信息的程序或视频播放程序。
本发明实施例第二方面提供了一种交通工具控制方法, 包括:
应用系统接收来自驾驶系统的第二信号,所述应用系统用于控制交通工具 内的应用程序;
所述应用系统根据所述第二信号确定当前驾驶模式;
若当前驾驶模式为手动驾驶模式,且所述应用系统确定正在运行的程序为 非安全类程序, 则所述应用系统切换所述非安全类程序。
结合本发明实施例的第二方面,本发明实施例的第二方面的第一种实现方 式中, 所述非安全类程序包括: 需要用户输入信息的程序或视频播放程序。
结合本发明实施例的第二方面与第二方面的第一种实现方式,本发明实施 例的第二方面的第二种实现方式中, 所述应用系统切换所述非安全类程序包 括:
所述应用系统关闭所述非安全类程序,或所述应用系统将所述非安全类程 序切换到后台。
结合本发明实施例的第二方面与第二方面的第一种实现方式,本发明实施 例的第二方面的第三种实现方式中,所述应用系统确定正在运行的程序为非安 全类程序包括:
所述应用系统获取所述正在运行的程序的安全性标识;
所述应用系统根据所述安全性标识判断正在运行的程序是否为非安全类 程序。
结合本发明实施例的第二方面的第三种实现方式,本发明实施例的第二方 面的第四种实现方式中,所述应用系统获取所述正在运行的程序的安全性标识 包括: 所述应用系统在安装所述程序时, 获取所述程序的安装文件, 并从所述安 装文件中获取所述安全性标识;
或, 所述应用系统在安装所述程序时, 设置所述程序的安全性标识; 或, 所述应用系统在安装所述程序时, 获取用户输入的所述程序的安全性 标识。
结合本发明实施例的第二方面的第三种实现方式,本发明实施例的第二方 面的第五种实现方式中,所述应用系统获取所述正在运行的程序的安全性标识 包括:
所述应用系统接收所述程序的运行信号;
所述应用系统生成所述程序的安全性标识。
本发明实施例第三方面提供了一种驾驶系统, 包括:
第一接收模块, 用于接收来自应用系统的第一信号;
第一确定模块,用于根据所述第一接收模块接收到的第一信号确定所述应 用系统中正在运行的程序的类型;
第一切换模块,用于在所述第一确定模块确定所述正在运行的程序为非安 全类程序,且当前驾驶模式为手动驾驶的情况下,将当前驾驶模式切换为自动 驾驶模式。
本发明实施例第四方面提供了一种应用系统, 包括:
第二接收模块, 用于接收来自驾驶系统的第二信号;
第二确定模块,用于根据所述第二接收模块接收到的第二信号确定当前驾 驶模式;
第二切换模块,用于在所述第二确定模块确定当前驾驶模式为手动驾驶模 式, 且正在运行的程序为非安全类程序的情况下, 切换所述非安全类程序。
结合本发明实施例的第四方面,本发明实施例的第四方面的第一种实现方 式中, 所述第二切换模块包括:
获取子模块, 用于获取正在运行的程序的安全性标识;
判断子模块,用于根据所述获取子模块获取的所述安全性标识判断正在运 行的程序是否为非安全类程序;
切换子模块, 用于切换所述非安全类程序。 结合本发明实施例的第四方面第一种实现方式,本发明实施例的第四方面 的第二种实现方式中, 切换子模块具体用于:
关闭所述非安全类程序, 或将所述非安全类程序切换到后台。
结合本发明实施例的第四方面第一种实现方式与第四方面第二种实现方 式, 本发明实施例的第四方面的第三种实现方式中, 所述获取子模块包括: 第一获取单元, 用于获取待安装程序的安装文件;
第二获取单元, 用于获取安装后程序的安全性标识。
结合本发明实施例的第四方面第一种实现方式与第四方面第二种实现方 式, 本发明实施例的第四方面的第四种实现方式中, 所述获取子模块包括: 接收单元, 用于接收所述程序的运行信号;
标识单元, 用于生成所述程序的安全性标识。
本发明实施例第五方面提供了一种交通工具控制系统,包括应用系统与本 发明实施例第三方面提供的驾驶系统。
本发明实施例第六方面提供了一种交通工具控制系统, 包括驾驶系统、与 本发明实施例第四方面或第四方面的第一至第四种实现方式中任一中实现方 式。
本发明实施例中, 驾驶系统接收来自应用系统的第一信号, 进而判断应用 系统中正在运行的程序是否为非安全类的程序, 若是,且当前驾驶模式为手动 驾驶, 则所述驾驶系统切换当前驾驶模式为自动驾驶。
或,应用系统接收来自驾驶系统的第二信号, 进而判断当前驾驶模式是否 为手动驾驶。 若是, 且正在运行的程序为非安全类程序, 则所述应用系统切换 正在运行的程序。
通过这种方法,保证了当非安全类程序运行时,驾驶模式一定为自动驾驶。 当驾驶模式为手动驾驶时,正在运行的程序一定不是非安全类程序。避免或减 少了驾驶员在手动驾驶过程中使用非安全类程序时注意力分散造成的风险,保 障了驾驶安全。 附图说明
图 1为本发明实施例中交通工具系统控制方法一个实施例流程图; 图 2为本发明实施例中另一交通工具系统控制方法的一个实施例流程图; 图 3为本发明实施例中另一交通工具系统控制方法的另一实施例流程图; 图 4为本发明实施例中另一交通工具系统控制方法的另一实施例流程图; 图 5为本发明实施例中生成安全性标识方法的实施例流程图; 图 6为本发明实施例中另一交通工具系统控制方法的另一实施例流程图; 图 7为本发明实施例中驾驶系统一个实施例结构图; 图 8为本发明实施例中驾驶系统另一个实施例结构图; 图 9为本发明实施例中应用系统一个实施例结构图; 图 10为本发明实施例中应用系统另一个实施例结构图; 图 11为本发明实施例中应用系统另一个实施例结构图; 图 12为本发明实施例中应用系统另一个实施例结构图; 图 13为本发明实施例中应用系统另一个实施例结构图; 图 14为本发明实施例中交通工具控制系统的一个实施例结构图。 具体实施方式
本发明实施例提供了交通工具系统控制方法, 可以提高驾驶的安全性。本 发明还提出了其相关驾驶系统、应用系统以及交通工具控制系统, 以下将分别 进行说明。
本发明实施例提供的一种交通工具控制方法的基本流程请参考图 1, 主要 包括步骤:
101、 驾驶系统接收来自应用系统的第一信号;
交通工具的控制系统一般包括驾驶系统与应用系统。驾驶系统用于控制交 通工具的驾驶, 而应用系统用于控制交通工具内的应用程序。 驾驶系统与应用 系统之间存在信息通道, 可以进行信息交互。 本实施例中, 驾驶系统可以接收 到来自应用系统的第一信号,该第一信号用于表示应用系统中正在运行的程序 的类型。 其中, 驾驶系统可以在很多时间点接收该第一信号。 例如: 应用系统在切 换程序时, 生成第一信号,该第一信号表示应用系统切换程序后应用系统中正 在运行的程序的类型, 此时驾驶系统接收该第一信号; 也可以为驾驶系统每隔 固定时间间隔自动接收该第一信号,以检测此时应用系统中正在运行的程序的 类型。 驾驶系统接收来自应用系统的第一信号也可以釆用其他方法, 此处不做 具体限定。
102、 驾驶系统根据第一信号确定应用系统中正在运行的程序的类型; 驾驶系统获取到第一信号之后,根据该第一信号确定应用系统中正在运行 的程序的类型。此处所述的程序的类型主要包括:安全类程序与非安全类程序。 若一个程序在正常运行过程中会吸引驾驶员较多的注意力,则认为该程序为非 安全类程序。若一个程序在正常运行过程中不会吸引驾驶员较多的注意力, 则 认为其为安全类程序。安全类程序与非安全类程序的具体区分方法将在下文详 述, 此处不做具体限定。
103、 若正在运行的程序为非安全类程序, 且驾驶系统确定当前驾驶模式 为手动驾驶, 则驾驶系统将当前驾驶模式切换为自动驾驶模式。
若驾驶系统根据所述第一信号确定应用系统正在运行的程序为非安全类 程序,且驾驶系统当前的驾驶模式为手动驾驶模式, 则说明此时驾驶员在注意 力被分散的情况下进行驾驶操作, 安全性得不到保障。所以驾驶系统将当前驾 驶模式切换为自动驾驶模式。
本实施例中, 驾驶系统接收来自应用系统的第一信号, 进而判断应用系统 中正在运行的程序是否为非安全类程序。 若是, 且当前驾驶模式为手动驾驶, 则所述驾驶系统切换当前驾驶模式为自动驾驶,通过这种方法,保证了当交通 工具应用系统在运行非安全类程序时, 驾驶模式一定为自动驾驶。避免了驾驶 员在使用非安全类程序时注意力分散造成的风险, 保障了驾驶安全。
本实施例中, 交通工具的种类有很多, 如汽车、 飞机、 轮船等, 此处不做 具体限定。
本实施例中, 安全类程序与非安全类程序的区分方法有很多。 一般的, 若 一个程序在正常运行过程中会吸引驾驶员较多的注意力,则认为该程序为非安 全类程序, 如视频播放程序、 或需要用户输入信息的程序等; 若一个程序在正 常运行时不会吸引驾驶员较多的注意力, 则认为该程序为安全类程序,如电台 接收程序、 音乐播放程序等等。
其中, 安全类与非安全类的程序的区分标准不需要是一成不变的,也可以 是变化的。 例如, 应用系统可以给交通工具所安装的程序分为三级: 高危险级 程序、中级程序与低危险级程序。当汽车在非密集型道路上行驶或低速行驶时, 应用系统将高危险级程序设置为非安全类程序,将中级程序与低危险级程序设 置为安全类程序; 当汽车在密集型道路上行驶或高速行驶时,应用系统将高危 险级程序与中级程序设置为非安全类程序, 将低危险级程序设置为安全类程 序。应用系统也可以给交通工具所安装的程序分为更多的级别, 安全类与非安 全类程序的区分也可以有其它标准, 此处均不做具体限定。
根据安全类与非安全类程序的区分标准来判断一个程序是否为非安全类 程序首先在应用系统中完成,应用系统根据判断结果生成第一信号, 驾驶系统 根据该第一信号确定该程序是否为非安全类程序。应用系统如何判断该程序是 否为非安全类程序将在后面的实施例中详述, 此处不做具体限定。
为了便于理解上述实施例,下面将以上述实施例的一个具体应用场景为例 进行说明:
现有一位驾驶员驾驶一辆汽车, 该汽车具有驾驶系统与应用系统, 驾驶系 统可以控制手动驾驶模式与自动驾驶模式, 应用系统可以控制应用程序的运 行。 驾驶员一边手动驾驶汽车, 一边打开应用程序中的 MP3程序听音乐。 这 时, 汽车的驾驶系统可以接收到 MP3程序运行的信号。 在该汽车中, MP3程 序被认为是安全类程序, 所以驾驶系统仍然允许驾驶员手动驾驶汽车。
驾驶员驾驶一段时间之后, 打开了应用程序中的 Video播放程序观看电 影。 而在该汽车中, Video播放程序被认为是非安全类程序。 应用系统在运行 Video程序时, 会生成第一信号, 表示非安全类程序正在运行。 应用系统将该 第一信号发送至应用系统与驾驶系统之间的信息通道中,驾驶系统接收到该第 一信号,确定应用系统中正在运行的程序为非安全类程序。 由于此时驾驶员正 在进行手动驾驶, 所以驾驶系统将手动驾驶模式切换为自动驾驶模式, 进而自 动驾驶汽车。
上述实施例描述的是驾驶系统根据应用系统的信号来切换驾驶模式,以保 证驾驶安全。下面的实施例提供了一种应用系统根据驾驶系统的信号来切换程 序的交通工具系统控制方法, 其基本流程请参阅图 2:
201、 应用系统接收来自驾驶系统的第二信号;
交通工具的控制系统一般包括驾驶系统与应用系统,驾驶系统用于控制交 通工具的驾驶, 而应用系统用于控制交通工具内的应用程序。 驾驶系统与应用 系统之间存在信息通道, 可以进行信息交互。 本实施例中, 应用系统可以接收 来自驾驶系统的第二信号, 该第二信号用于表示驾驶系统当前的驾驶模式。
其中, 应用系统可以在很多时间点接收该第二信号。 例如: 驾驶系统在切 换驾驶模式时, 生成第二信号, 该第二信号用于表示驾驶系统切换驾驶模式后 的驾驶模式, 此时应用系统接收该第二信号; 也可以为应用系统每隔固定时间 自动接收该第二信号, 以检测当前驾驶系统的驾驶模式。应用系统接收来自驾 驶系统的第二信号也可以釆用其他方法, 此处不做具体限定。
202、 应用系统根据第二信号确定当前驾驶模式;
应用系统获取到第二信号后,根据该第二信号确定驾驶系统当前的驾驶模 式。 此处的驾驶模式主要包括: 手动驾驶模式或自动驾驶模式。
203、 若当前驾驶模式为手动驾驶模式, 且应用系统确定正在运行的程序 为非安全类程序, 则应用系统切换该非安全类程序。
若应用系统根据第二信号确定当前的驾驶模式为手动驾驶模式,且应用系 统中正在运行的程序为非安全类程序,则说明此时驾驶员在注意力被分散的情 况下进行驾驶操作, 安全性得不到保障。 所以应用系统切换当前正在运行的非 安全类程序, 以保证驾驶员的注意力不被分散, 提高驾驶的安全性。
本实施例中,应用系统接收来自驾驶系统的第二信号, 进而判断当前驾驶 模式是否为手动驾驶。 若是, 且正在运行的程序为非安全类程序, 则应用系统 切换正在运行的程序。 通过这种方法, 保证了当驾驶模式为手动驾驶时, 正在 运行的程序一定不是非安全类程序,减少了非安全类程序造成的驾驶员手动驾 驶过程中的注意力分散, 提高了驾驶的安全性。
本实施例中, 交通工具的种类有很多, 如汽车、 飞机、 轮船等, 此处不做 具体限定。
本实施例中, 应用系统切换该非安全类程序的方法有^ ^多, 如: 应用系统 关闭该非安全类程序、或应用系统后将该非安全类程序切换到后台等。也可以 为应用系统强制关闭该非安全类程序的部分功能,然后将关闭了部分功能的非 安全类程序设置为安全性程序, 并继续运行。应用系统切换非安全类程序也可 以使用其他方法, 此处不做具体限定。
本实施例中安全类程序与非安全类程序的概念与上一实施例基本相同,此 处不再赘述。 其区分方法也有很多, 此处不做具体限定。
上面的实施例详细描述了应用系统如何根据驾驶系统来切换非安全性程 序,下面的实施例将进一步描述应用系统如何判断正在运行的程序是否为非安 全类程序, 请参阅图 3:
301、 应用系统接收来自驾驶系统的第二信号;
302、 应用系统根据第二信号确定当前驾驶模式;
步骤 301、 302与上一实施例中的 201、 202基本相同, 此处不做赘述
303、 应用系统获取正在运行的程序的安全性标识;
为了判断正在运行的程序的安全性类别,应用系统首先要获取正在运行的 程序的安全性标识。该安全性标识用于表示正在运行的程序的安全性类别。所 述安全性类别用于表示该程序是否为非安全类程序。
应用系统获取该安全性标识的时刻可以有^^多,包括应用系统在程序安装 时获取该程序的安全性标识、或应用系统在程序运行时获取该程序的安全性标 识。应用系统也可以在其它时刻获取该程序的安全性标识,此处不做具体限定。
其中, 应用系统中在获取了程序的安全性标识后, 可以将其保存在 ARF
(程序注册文件, Application Register File )中, 也可以保存在其它位置, 也可 以不保存, 此处不做具体限定。
304、 应用系统根据该安全性标识判断正在运行的程序是否为非安全类程 序。
应用系统在程序运行时,根据获得的安全性标识与安全性类别的对应关系 判断正在运行的程序是否为非安全类程序。其中, 若应用系统中程序的安全性 标识均保存在 ARF中,则应用系统从 ARF中读取正在运行的程序的安全性标 识, 并根据安全性标识判断其是否为安全类程序。
305、 若当前驾驶模式为手动驾驶模式, 且应用系统确定正在运行的程序 为非安全类程序, 则应用系统切换该非安全类程序。
步骤 305与上一实施例中步骤 203基本相同, 此处不做赞述。
其中, 步骤 301、 302与步骤 303、 304的顺序不做限制, 步骤 303、 304 也可以在步骤 301、 302之前。
本实施例详细描述了应用系统如何判断正在运行的程序的安全性类别。应 用系统首先获取正在运行的程序的安全性标识,然后根据该安全性标识判断正 在运行的程序是否为非安全类程序。其中,应用系统获取程序的安全性标识的 时刻可以为程序安装时或程序运行时。
上面的实施例给出了应用系统判断正在运行的程序的安全性类别的方法, 下面的实施例将对其中的应用系统获取正在运行的程序的安全性标识步骤做 出进一步解释。 其中, 应用系统可以在安装该正在运行的程序时, 获取该程序 的安全性标识, 请参阅图 4:
401、 应用系统接收来自驾驶系统的第二信号;
402、 应用系统根据第二信号确定当前驾驶模式;
步骤 401、 402与上一实施例中的 301、 302基本相同, 此处不做赘述
403、 应用系统获取待安装程序的安装文件;
应用系统可以在程序安装时获取程序的安全性标识。 为了安装程序,应用 系统获取待安装程序的安装文件。应用系统获取安装文件后, 就可以根据安装 文件来安装所述待安装程序。 其中, 安装程序的方法有很多, 一般情况下, 所 述安装文件为安装包,应用系统根据安装包来安装程序。但是应用系统也可以 釆用镜像安装的方法来安装程序。 所述镜像安装为一种普遍的程序安装方法, 应用系统通过镜像操作,可以批量的从外界的源系统中获取一个或多个程序的 安装文件并完成安装, 使得本应用系统得以便捷地批量安装源系统的应用程 序。 安装程序也可以釆用其他方法, 此处不做具体限定。
404、 应用系统获取安装后程序的安全性标识;
应用系统获取安装后的程序的安全性标识有许多方法,包括应用系统从安 装文件中获取所述安装后的程序的安全性标识、或应用系统设置所述安装后的 程序的安全性标识、 或应用系统获取用户输入的安装后的程序的安全性标识。 应用系统也可以釆用其他方法来获取安全性标识, 此处不做具体限定。 其中,应用系统从安装文件中获取安装后的程序的安全性标识包括: 该程 序在编译过程中生成安全性标识, 并保存在安装文件中。应用系统从安装文件 中获取该安全性标识。
本实施例还提供一种在编译过程中生成安全性标识的方法, 如图 5:
501、 编译器识别待编译程序的代码或编译后程序的代码中是否存在预置 代码或代码集合;
应用系统中的应用程序一般都会经过编译链接这个生成过程,本方法即为 编译器在该编译阶段获取程序的安全性标识。 为了获取该安全性标识, 编译器 首先要识别待编译程序的代码或编译后程序的代码中是否存在预置代码或代 码集合。 其中, 所述编译器可以位于应用系统中, 也可以独立于应用系统。
其中, 待编译程序的代码为源代码, 编译后程序的代码为目标代码。 源代 码与目标代码只是在形式上有差别,二者在作用上是等价的, 所以编译器对其 中任一种代码进行识别都能达到目的。
其中, 预置代码或代码集合可以对应程序的某种功能, 如视频播放功能、 获取用户输入的信息的功能等,该功能会使得该程序在运行过程中分散驾驶员 较多的注意力。预置代码或代码集合也可以表示强制设置安全性类别功能,程 序员可以在编程的过程中通过在程序代码里写入该预置代码或代码集合来强 制设置该程序的安全性类别。若待编译的程序的代码或编译后的程序的代码中 如果存在预置代码, 则认为该程序在运行过程中会分散驾驶员注意力, 该程序 为非安全类程序, 执行步骤 502、 若待编译的程序代码或编译后的程序的代码 中不存在预置代码, 则认为该程序在运行过程中不会过多的分散驾驶员注意 力, 执行步骤 503。
其中, 所述预置代码指的是预置的一句、 一段或一类代码, 如对于源代码 来说, DialogBox、 InputBox等函数表示需要获取用户的输入, 可以作为预置 代码; 对于目标码来说, in等机器指令表示需要获取用户的输入, 也可以作为 预置代码。 预置代码的种类不仅包括 DialogBox、 InputBox等, 也包括其他代 码, 此处不做具体限定。 预置代码也可以为自定义的代码, 程序员在编写程序 时, 写入该自定义代码供编译器识别。
其中, 预置代码集合指的是重复多次出现的预置代码。 以源代码为例, 如 果源代码中只出现一次 InputBox函数, 即表示该程序在运行过程中只需要用 户输入一次信息,不会分散用户较多的注意力,可以认为该程序为安全类程序。 但是如果源代码中出现了多次 DialogBox与 InputBox,即表示该程序在运行过 程中需要用户多次输入信息,会分散用户较多的注意力, 可以认为该程序为非 安全类程序。
502、 编译器生成非安全类程序对应的安全性标识;
若待编译的程序的代码或编译后的程序的代码中存在预置代码,则认为该 程序在运行过程中会分散驾驶员注意力, 该程序为非安全类程序, 编译器生成 非安全类程序对应的安全性标识。
503、 编译器生成安全类程序对应的安全性标识;
若待编译的程序代码或编译后的程序的代码中不存在预置代码,则认为该 程序在运行过程中不会过多的分散驾驶员注意力, 该程序为安全类程序, 编译 器生成安全类程序对应的安全性标识。
504、 编译器保存生成的安全性标识。
步骤 502、 503中生产的安全性标识可以保存在 Data Segments文件中,应 用系统在后续操作中可以从 Data Segments文件中获得该安全性标识, 并保存 到 ARF中。 该安全性标识也可以保存在其它位置, 此处不做具体限定。
其中, 用户自定义代码也可以为用户自定义函数, 如 SafetyClassfication ( )类函数。 程序员在编写程序时, 调用该函数, 即表示强制设置该程序的安 全性类别。该类别可以为安全类程序,也可以为非安全类程序。在这种情况下, 编译器若识别到 SafetyClassfication ( )类函数, 应根据该函数设置的安全性类 别生成相对应的安全性标识。 其中, SafetyClassfication ( )仅仅为该类函数的 一种命名, 此类功能的函数也可以有其它命名方式, 此处不做限定。
在编译过程中生成安全性标识的方法除了图 5所示的方法外,也可以为其 他方法, 此处不做限定。
其中,应用系统从安装文件中获取安装后的程序的安全性标识还包括: 应 用系统通过镜像操作来安装程序时, 从源系统中获取待安装程序的安装文件, 进而从该安装文件中获取安全性标识。由于镜像操作的结果是使得本应用系统 具有与源系统相同的程序与功能,所以只要源系统中保存有某个程序的安全性 标识,在该程序在被镜像安装到本应用系统中时, 本应用系统就能够获取该程 序的安全性标识。
其中,应用系统设置所述安装后的程序的安全性标识包括: 应用系统在安 装程序的过程中, 为安装后的程序设置一个默认的安全性标识。应用系统可以 将安装后的程序的安全性标识均设为非安全性程序对应的安全性标识、也可以 将安装后的程序的安全性标识均设为安全性程序对应的标识、也可以为不同的 程序设置不同的安全性标识, 此处不做具体限定。
其中,应用系统获取用户输入的安装后的程序的安全性标识包括: 应用系 统在安装程序的过程中,要求用户输入安装后的程序的安全性类别,应用系统 才艮据用户输入的安装后程序的安全性类别生成对应的安全性标识。
应用系统在获取了安装后程序的安全性标识之后, 可以保存该安全性标 识。这样在需要使用该安全性标识时,应用系统可以直接从该安全性标识的保 存位置中获取该安全性标识。
405、 应用系统根据该安全性标识判断正在运行的程序是否为非安全类程 序;
406、 若当前驾驶模式为手动驾驶模式, 且应用系统确定正在运行的程序 为非安全类程序, 则应用系统切换该非安全类程序。
步骤 405、 406与上一实施例中步骤 304、 305基本相同, 此处不做赞述。 其中, 步骤 401、 402与步骤 403至 405的顺序本实施例不做限制, 步骤 403至 405也可以位于步骤 401、 402之前。
本实施例详细描述了应用系统在程序安装时获取安全性标识的方法。 其 中,应用系统获取待安装程序的安装文件、安装所述待安装程序并获取安装后 程序的安全性标识。获取了安全性标识之后,应用系统就可以根据生成的安全 性标识判断正在运行的程序的安全性类别, 若当前驾驶模式为手动驾驶模式, 且正在运行的程序为非安全类程序, 则应用系统切换该非安全类程序, 以保证 在驾驶模式为手动驾驶时,应用系统内运行的程序一定为安全性程序, 减少了 非安全性程序对驾驶员注意力的分散, 提高了驾驶安全性。
上面的实施例描述的是应用系统在程序安装时获取安全性标识的方法,下 面的实施例将详细描述应用系统在程序运行时获取安全性标识的方法,请参阅 图 6:
601、 应用系统接收来自驾驶系统的第二信号;
602、 应用系统根据第二信号确定当前驾驶模式;
步骤 601、 602与上一实施例中的 501、 502基本相同, 此处不做赘述 603、 应用系统接收程序的运行信号;
应用系统不仅可以在安装程序时获取程序的安全性标识,也可以在程序运 行时获取程序的安全性标识。在运行程序之前,应用系统接收该程序的运行信 号, 准备运行该程序。
604、 应用系统生成该程序的安全性标识;
应用系统接收到程序的运行信号后, 可以生成该程序的安全性标识。应用 系统此时生成程序的安全性标识的具体方法有^ L多, 包括: 应用系统识别待运 行的程序的代码中是否存在预置代码或代码集合, 若存在, 则认为该程序具有 的某些功能会分散驾驶员的注意力,应用系统生成非安全类程序对应的安全性 标识; 若不存在, 则认为该程序中不具有可能分散驾驶员注意力的功能, 应用 系统生成安全类程序对应的安全性标识。
其中,预置代码或代码集合的含义与步骤 403中的预置代码或代码集合基 本相同, 此处不做赞述。
特别的,应用系统在本步骤之前, 可以先判断是否已经获取待运行程序的 安全性标识, 若确定未获取待运行的程序的安全性标识, 则执行本步骤; 若确 定已获取待运行的程序的安全性标识, 则无需执行本步骤。
其中,应用系统在生成待运行程序的安全性标识后, 可以将该安全性标识 保存下来。 这样, 应用系统只需在首次运行该程序时生成安全性标识, 第二次 或以后运行该程序时, 可以直接从安全性标识的保存位置中获取该安全性标 识。
其中, 本步骤仅限定为在应用系统接收到程序的运行信号后实施。具体可 以在应用系统运行该程序前,也可以在应用系统运行该程序后, 此处不做具体 限定。
605、 应用系统根据该安全性标识判断该程序是否为非安全类程序;
606、 若当前驾马史模式为手动驾马史模式, 且应用系统确定该程序为非安全 类程序, 则应用系统切换该非安全类程序。
步骤 605、 606与上一实施例中步骤 506、 507基本相同, 此处不做赞述。 其中, 步骤 601、 602与步骤 603至 605的顺序本实施例不做限制, 步骤 603至 605也可以位于步骤 601、 602之前。
本实施例详细描述了应用系统在程序运行时获取安全性标识的方法。 其 中, 应用系统接收程序的运行信号, 然后生成该程序的安全性标识。 生成了安 全性标识之后,应用系统就可以根据生成的安全性标识判断正在运行的程序的 安全性类别, 若当前驾驶模式为手动驾驶模式,且正在运行的程序为非安全类 程序, 则应用系统切换该非安全类程序, 以保证在驾驶模式为手动驾驶时, 应 用系统内运行的程序一定为安全性程序,减少了非安全性程序对驾驶员注意力 的分散, 提高了驾驶安全性。
为了便于理解上述实施例,下面将以上述实施例的一个具体应用场景为例 进行说明:
现有一辆汽车, 该汽车具有驾驶系统与应用系统, 驾驶系统可以控制手动 驾驶模式与自动驾驶模式,应用系统可以控制应用程序的运行。 驾驶员要在应 用系统中安装 Video播放程序。 首先, 驾驶员将该 Video播放程序的安装文件 从 U盘中拷贝到应用系统中。 应用系统在安装该程序时, 要求驾驶员输入该 程序的安全性类别。驾驶员认为 Video播放程序在运行过程中会吸引自己过多 的视线与注意力, 于是输入: 非安全类程序。 应用系统接收到驾驶员输入的信 息, 并生成非安全类程序对应的安全性标识, 该安全性标识保存在应用系统的 APF中。之后, 驾驶员开启自动驾驶模式来驾驶汽车, 同时打开应用程序中的 Video播放程序观看电影。
自动驾驶了一段时间后, 该汽车行驶到了一个路况较为复杂的地带, 驾驶 员将自动驾驶模式切换为手动驾驶模式来人工驾驶汽车。驾驶系统此时生成第 二信号, 用于表示当前的驾驶模式为手动驾驶, 并将该第二信号发送至应用系 统与驾驶系统之间的信息通道中。应用系统接收到该第二信号,根据该第二信 号确定当前的驾驶模式为手动驾驶。 由于 Video播放程序为非安全类程序, 所 以应用系统强制关闭该 Video播放程序。
本发明还提供了一种驾驶系统 700, 用于完成上面的实施例所描述的功 能, 其基本结构请参阅图 7:
第一接收模块 701、 用于接收来自应用系统的第一信号;
第一确定模块 702、 用于根据第一接收模块 701接收到的第一信号确定应 用系统中正在运行的程序的类型;
第一切换模块 703、 用于在第一确定模块 702确定正在运行的程序为非安 全类程序,且当前驾驶模式为手动驾驶的情况下,将当前驾驶模式切换为自动 驾驶模式。
本实施例中, 第一接收模块 701接收来自应用系统的第一信号,进而第一 确定模块 702判断应用系统中正在运行的程序是否为非安全类程序。若是,且 当前驾驶模式为手动驾驶, 则第一切换模块 703 切换当前驾驶模式为自动驾 驶, 通过这种方法, 保证了当交通工具应用系统在运行非安全类程序时, 驾驶 模式一定为自动驾驶。避免了驾驶员在使用非安全类程序时注意力分散造成的 风险, 保障了驾驶安全。
为了便于理解上述实施例,下面将以上述实施例的一个具体应用场景为例 进行说明:
现有一位驾驶员驾驶一辆汽车, 该汽车具有驾驶系统与应用系统, 驾驶系 统可以控制手动驾驶模式与自动驾驶模式, 应用系统可以控制应用程序的运 行。 驾驶员一边手动驾驶汽车, 一边打开应用程序中的 MP3程序听音乐。 这 时, 汽车的驾驶系统可以接收到 MP3程序运行的信号。 在该汽车中, MP3程 序被认为是安全类程序, 所以驾驶系统仍然允许驾驶员手动驾驶汽车。
驾驶员驾驶一段时间之后, 打开了应用程序中的 Video播放程序观看电 影。 而在该汽车中, Video播放程序被认为是非安全类程序。 应用系统在运行 Video程序时, 会生成第一信号, 表示非安全类程序正在运行。 应用系统将该 第一信号发送至应用系统与驾驶系统之间的信息通道中,驾驶系统中的第一接 收模块 701接收到该第一信号,第一确定模块 702确定应用系统中正在运行的 程序为非安全类程序。 由于此时驾驶员正在进行手动驾驶, 所以第一切换模块 703将手动驾驶模式切换为自动驾驶模式, 进而自动驾驶汽车。
上面从单元化功能实体的角度对本发明实施例中的驾驶系统进行了描述, 下面从硬件处理的角度对本发明实施例中的驾驶时系统进行描述, 请参阅图 8, 本发明实施例中的驾驶系统 800另一实施例包括:
输入装置 801、 输出装置 802、 处理器 803和存储器 804 (其中驾驶系统 800中的处理器 803的数量可以一个或多个, 图 8中以一个处理器 803为例;)。 在本发明的一些实施例中, 输入装置 801、 输出装置 802、 处理器 803和存储 器 804可通过总线或其它方式连接, 其中, 图 8中以通过总线连接为例。
其中, 通过调用存储器 804存储的操作指令, 处理器 803, 用于执行如下 步骤:
接收来自应用系统的第一信号;
根据所述第一信号确定所述应用系统中正在运行的程序的类型;
若所述正在运行的程序为非安全类程序,且所述驾驶系统确定当前驾驶模 式为手动驾驶模式, 将当前驾驶模式切换为自动驾驶模式。
本发明的一些实施例中, 驾驶系统 800还执行如下步骤:
本发明还提供了一种应用系统 900, 用于完成上面的实施例所描述的功 能, 其基本结构请参阅图 9:
第二接收模块 901、 用于接收来自驾驶系统的第二信号;
第二确定模块 902、 用于根据第二接收模块 901接收到的第二信号确定当 前驾驶模式;
第二切换模块 903、 用于在第二确定模块 902确定当前驾驶模式为手动驾 驶模式, 且正在运行的程序为非安全类程序的情况下, 切换该非安全类程序。
本实施例中, 第二接收模块 901接收来自驾驶系统的第二信号,进而第二 确定模块 902判断当前驾驶模式是否为手动驾驶。若是,且正在运行的程序为 非安全类程序, 则第二切换模块 903切换正在运行的程序。 通过这种方法, 保 证了当驾驶模式为手动驾驶时,正在运行的程序一定不是非安全类程序, 减少 了非安全类程序造成的驾驶员手动驾驶过程中的注意力分散,提高了驾驶的安 全性。
上面的实施例详细描述了应用系统如何根据驾驶系统来切换非安全性程 序,下面的实施例将进一步描述应用系统如何判断正在运行的程序是否为非安 全类程序, 请参阅图 10, 该应用系统 1000包括:
第二接收模块 1001、 用于接收来自驾驶系统的第二信号; 第二确定模块 1002、 用于根据第二接收模块 1001接收到的第二信号确定 当前驾驶模式;
第二切换模块 1003、 用于在第二确定模块 1002确定当前驾驶模式为手动 驾驶模式,且正在运行的程序为非安全类程序的情况下,切换该非安全类程序。 其中, 该第二切换模块 1003包括:
获取子模块 10031、 用于获取正在运行的程序的安全性标识;
判断子模块 10032、 用于根据所述获取子模块 10031获取的安全性标识判 断正在运行的程序是否为非安全类程序;
切换子模块 10033、 用于切换该非安全类程序。
本实施例详细描述了应用系统如何判断正在运行的程序的安全性类别。获 取子模块 10031 首先获取正在运行的程序的安全性标识, 然后判断子模块 10032根据该安全性标识判断正在运行的程序是否为非安全类程序。 其中, 应 用系统获取程序的安全性标识的时刻可以为程序安装时或程序运行时。
上面的实施例给出了可以实现判断正在运行的程序的安全性类别的应用 系统, 下面的实施例将对应用系统中的获取子模块 10031做出进一步解释。
请参阅图 11, 该应用系统 1100包括:
第二接收模块 1101、 用于接收来自驾驶系统的第二信号;
第二确定模块 1102、 用于根据第二接收模块 1101接收到的第二信号确定 当前驾驶模式;
第二切换模块 1103、 用于在第二确定模块 1102确定当前驾驶模式为手动 驾驶模式,且正在运行的程序为非安全类程序的情况下,切换该非安全类程序。 其中, 该第二切换模块 1103包括:
获取子模块 11031、 用于获取正在运行的程序的安全性标识, 该获取子模 块 11031包括:
第一获取单元 110311、 用于获取待安装程序的安装文件;
第二获取单元 110312、 用于获取所述程序安装单元 110311安装后程序的 安全性标识;
判断子模块 11032、 用于根据第二获取单元 110312获取的安全性标识判 断正在运行的程序是否为非安全类程序; 切换子模块 11033、 用于切换该非安全类程序。
本实施例详细描述了一种在程序安装时获取安全性标识的应用系统。 其 中, 第一获取单元 110311 获取待安装程序的安装文件、 然后第二获取单元 110312获取安装后程序的安全性标识。 获取了安全性标识之后, 判断子模块 11032就可以根据生成的安全性标识判断正在运行的程序的安全性类别, 若当 前驾驶模式为手动驾驶模式,且正在运行的程序为非安全类程序, 则切换子模 块 11033切换该非安全类程序, 以保证在驾驶模式为手动驾驶时,应用系统内 运行的程序一定为安全性程序, 减少了非安全性程序对驾驶员注意力的分散, 提高了驾驶安全性。
上面的实施例描述的是一种在程序安装时获取安全性标识的应用系统,下 面的实施例将详细描述一种在程序运行时获取安全性标识的应用系统,请参阅 图 12, 该应用系 1200统包括:
第二接收模块 1201、 用于接收来自驾驶系统的第二信号;
第二确定模块 1202、 用于根据第二接收模块 1201接收到的第二信号确定 当前驾驶模式;
第二切换模块 1203、 用于在第二确定模块 1202确定当前驾驶模式为手动 驾驶模式,且正在运行的程序为非安全类程序的情况下,切换该非安全类程序。 其中, 该第二切换模块 1203包括:
获取子模块 12031、 用于获取正在运行的程序的安全性标识, 其中, 该获 取子模块 12031包括:
接收单元 120311、 用于接收程序的运行信号;
标识单元 120312、 用于生成该程序的安全性标识;
判断子模块 12032、 用于根据标识单元 120312生成的安全性标识判断正 在运行的程序是否为非安全类程序;
切换子模块 12033、 用于切换该非安全类程序。
本实施例详细描述了一种应用系统, 可以在程序运行时获取安全性标识。 其中,接收单元 120311接收程序的运行信号, 然后标识单元 120312生成该程 序的安全性标识。生成了安全性标识之后, 判断子模块 12032就可以根据生成 的安全性标识判断正在运行的程序的安全性类别,若当前驾驶模式为手动驾驶 模式,且正在运行的程序为非安全类程序, 则切换子模块 12033切换该非安全 类程序, 以保证在驾驶模式为手动驾驶时,应用系统内运行的程序一定为安全 性程序, 减少了非安全性程序对驾驶员注意力的分散, 提高了驾驶安全性。
为了便于理解上述实施例,下面将以上述实施例的一个具体应用场景为例 进行说明:
现有一辆汽车, 该汽车具有驾驶系统与应用系统, 驾驶系统可以控制手动 驾驶模式与自动驾驶模式,应用系统可以控制应用程序的运行。 驾驶员要在应 用系统中安装 Video播放程序。 首先, 驾驶员将该 Video播放程序的安装文件 从 U盘中拷贝到应用系统第一获取单元 110311中; 之后, 应用系统在安装该 程序时, 第二获取单元 110312要求驾驶员输入该程序的安全性类别。 驾驶员 认为 Video播放程序在运行过程中会吸引自己过多的视线与注意力, 于是输 入: 非安全类程序。 第二获取单元 110312接收到驾驶员输入的信息, 生成非 安全类程序对应的安全性标识,并将该安全性标识保存在应用系统的 APF中。 之后, 驾驶员开启自动驾驶模式来驾驶汽车, 同时打开应用程序中的 Video播 放程序观看电影。
自动驾驶了一段时间后, 该汽车行驶到了一个路况较为复杂的地带, 驾驶 员将自动驾驶模式切换为手动驾驶模式来人工驾驶汽车。驾驶系统此时生成第 二信号, 用于表示当前的驾驶模式为手动驾驶, 并将该第二信号发送至应用系 统与驾驶系统之间的信息通道中。 应用系统的第二接收模块 1101接收到该第 二信号,第二确定模块 1102根据该第二信号确定当前的驾驶模式为手动驾驶。 由于判断子模块 11032判断 Video播放程序为非安全类程序,所以切换子模块 11033强制关闭该 Video播放程序。
上面从单元化功能实体的角度对本发明实施例中的应用系统进行了描述, 下面从硬件处理的角度对本发明实施例中的应用系统进行描述, 请参阅图 13, 本发明实施例中的应用系统 1300另一实施例包括:
输入装置 1301、 输出装置 1302、 处理器 1303和存储器 1304 (其中应用 系统 1300中的处理器 1303的数量可以一个或多个,图 13中以一个处理器 1303 为例)。 在本发明的一些实施例中, 输入装置 1301、 输出装置 1302、 处理器 1303和存储器 1304可通过总线或其它方式连接, 其中, 图 13中以通过总线 连接为例。
其中, 通过调用存储器 1304存储的操作指令, 处理器 1303, 用于执行如 下步骤:
接收来自驾驶系统的第二信号;
根据所述第二信号确定当前驾驶模式;
若当前驾驶模式为手动驾驶模式,且所述应用系统确定正在运行的程序为 非安全类程序, 则切换所述非安全类程序。
本发明的一些实施例中, 应用系统 1300还执行如下步骤:
关闭所述非安全类程序, 或所述应用系统将所述非安全类程序切换到后 台;
获取所述正在运行的程序的安全性标识;
根据所述安全性标识判断正在运行的程序是否为非安全类程序;
获取待安装程序的安装文件;
获取安装后程序的安全性标识;
接收所述程序的运行信号;
生成所述程序的安全性标识。
上面的实施例为本发明提供的应用系统。本发明还提供一种交通工具控制 系统, 其基本结构请参阅图 14:
1401、驾驶系统,该驾驶系统与图 7所示的驾驶系统类似,此处不再赘述; 1402、 应用系统, 用于控制该应用系统内的程序的运行。
本发明实施例还提供一种交通工具控制系统, 如图 14所示:
1401、 驾驶系统, 用于控制交通工具的驾驶模式;
1402、 应用系统, 该应用系统与图 9至图 12中所示的应用系统类似, 此 处不再赘述。
所属领域的技术人员可以清楚地了解到, 为描述的方便和简洁, 上述描述 的系统,模块和单元的具体工作过程,可以参考前述方法实施例中的对应过程, 在此不再赘述。
在本申请所提供的几个实施例中, 应该理解到, 所揭露的系统和方法, 可 以通过其它的方式实现。 例如, 以上所描述的系统实施例仅仅是示意性的, 例 如, 所述单元的划分, 仅仅为一种逻辑功能划分, 实际实现时可以有另外的划 分方式, 例如多个单元或组件可以结合或者可以集成到另一个系统, 或一些特 征可以忽略, 或不执行。 另一点, 所显示或讨论的相互之间的耦合或直接辆合 或通信连接可以是通过一些接口,模块或单元的间接辆合或通信连接, 可以是 电性, 机械或其它的形式。 单元显示的部件可以是或者也可以不是物理单元, 即可以位于一个地方, 或者 也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部 单元来实现本实施例方案的目的。
另外, 在本发明各个实施例中的各功能单元可以集成在一个处理单元中, 也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元 中。上述集成的单元既可以釆用硬件的形式实现,也可以釆用软件功能单元的 形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售 或使用时, 可以存储在一个计算机可读取存储介质中。基于这样的理解, 本发 明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全 部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储 介质中, 包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器, 或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。 而前述 的存储介质包括: U盘、 移动硬盘、 只读存储器( ROM, Read-Only Memory )、 随机存取存储器(RAM, Random Access Memory ), 磁碟或者光盘等各种可以 存储程序代码的介质。

Claims

权 利 要 求
1、 一种交通工具系统控制方法, 其特征在于, 包括:
应用系统接收来自驾驶系统的第二信号,所述应用系统用于控制交通工具 内的应用程序;
所述应用系统根据所述第二信号确定当前驾驶模式;
若当前驾驶模式为手动驾驶模式,且所述应用系统确定正在运行的程序为 非安全类程序, 则所述应用系统切换所述非安全类程序。
2、 根据权利要求 1所述的交通工具系统控制方法, 其特征在于, 所述非 安全类程序包括: 需要用户输入信息的程序或视频播放程序。
3、 根据权利要求 1或 2所述的交通工具系统控制方法, 其特征在于, 所 述应用系统切换所述非安全类程序包括:
所述应用系统关闭所述非安全类程序,或所述应用系统将所述非安全类程 序切换到后台。
4、 根据权利要求 1或 2所述的交通工具系统控制方法, 其特征在于, 所 述应用系统确定正在运行的程序为非安全类程序包括:
所述应用系统获取所述正在运行的程序的安全性标识;
所述应用系统根据所述安全性标识判断正在运行的程序是否为非安全类 程序。
5、 根据权利要求 4所述的交通工具系统控制方法, 其特征在于, 所述应 用系统获取所述正在运行的程序的安全性标识包括:
所述应用系统在安装所述程序时, 获取所述程序的安装文件, 并从所述安 装文件中获取所述安全性标识;
或, 所述应用系统在安装所述程序时, 设置所述程序的安全性标识; 或, 所述应用系统在安装所述程序时, 获取用户输入的所述程序的安全性 标识。
6、 根据权利要求 4所述的交通工具系统控制方法, 其特征在于, 所述应 用系统获取所述正在运行的程序的安全性标识包括:
所述应用系统接收所述程序的运行信号;
所述应用系统生成所述程序的安全性标识。
7、 一种交通工具控制方法, 其特征在于, 包括:
驾驶系统接收来自应用系统的第一信号,所述应用系统用于控制交通工具 内的应用程序;
所述驾驶系统根据所述第一信号确定所述应用系统中正在运行的程序的 类型;
若所述正在运行的程序为非安全类程序,且所述驾驶系统确定当前驾驶模 式为手动驾驶模式, 则所述驾驶系统将当前驾驶模式切换为自动驾驶模式。
8、 根据权利要求 7所述的交通工具系统控制方法, 其特征在于, 所述非 安全类程序包括: 需要用户输入信息的程序或视频播放程序。
9、 一种驾驶系统, 其特征在于, 包括:
第一接收模块, 用于接收来自应用系统的第一信号;
第一确定模块,用于根据所述第一接收模块接收到的第一信号确定所述应 用系统中正在运行的程序的类型;
第一切换模块,用于在所述第一确定模块确定所述正在运行的程序为非安 全类程序,且当前驾驶模式为手动驾驶的情况下,将当前驾驶模式切换为自动 驾驶模式。
10、 一种应用系统, 其特征在于, 包括:
第二接收模块, 用于接收来自驾驶系统的第二信号;
第二确定模块,用于根据所述第二接收模块接收到的第二信号确定当前驾 驶模式;
第二切换模块,用于在所述第二确定模块确定当前驾驶模式为手动驾驶模 式, 且正在运行的程序为非安全类程序的情况下, 切换所述非安全类程序。
11、 根据权利要求 10所述的应用系统, 其特征在于, 所述第二切换模块 包括:
获取子模块, 用于获取正在运行的程序的安全性标识;
判断子模块,用于根据所述获取子模块获取的所述安全性标识判断正在运 行的程序是否为非安全类程序;
切换子模块, 用于切换所述非安全类程序。
12、 根据权利要求 11所述的应用系统, 其特征在于, 所述切换子模块具 体用于:
关闭所述非安全类程序, 或将所述非安全类程序切换到后台。
13、 根据权利要求 11或 12所述的应用系统, 其特征在于, 所述获取子模 块包括:
第一获取单元, 用于获取待安装程序的安装文件;
第二获取单元, 用于获取安装后程序的安全性标识。
14、 根据权利要求 11或 12所述的应用系统, 其特征在于, 所述获取子模 块包括:
接收单元, 用于接收所述程序的运行信号;
标识单元, 用于生成所述程序的安全性标识。
15、 一种交通工具控制系统, 其特征在于, 包括: 应用系统与权利要求 9 所述的驾驶系统。
16、 一种交通工具控制系统, 其特征在于, 包括: 驾驶系统与权利要求 10至 14中任一项所述的应用系统。
17、 根据权利要求 16所述的系统, 其特征在于, 所述驾驶系统为权利要 求 9所述的驾驶系统。
PCT/CN2014/085765 2013-12-13 2014-09-02 交通工具系统控制方法以及控制系统 WO2015085798A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP14870624.5A EP3069949A4 (en) 2013-12-13 2014-09-02 METHOD FOR CONTROLLING VEHICLE SYSTEM AND CONTROL SYSTEM
US15/180,572 US20160288801A1 (en) 2013-12-13 2016-06-13 Vehicle System Control Method and Control System

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310687888.6A CN103693038B (zh) 2013-12-13 2013-12-13 交通工具系统控制方法以及控制系统
CN201310687888.6 2013-12-13

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/180,572 Continuation US20160288801A1 (en) 2013-12-13 2016-06-13 Vehicle System Control Method and Control System

Publications (1)

Publication Number Publication Date
WO2015085798A1 true WO2015085798A1 (zh) 2015-06-18

Family

ID=50354757

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/085765 WO2015085798A1 (zh) 2013-12-13 2014-09-02 交通工具系统控制方法以及控制系统

Country Status (4)

Country Link
US (1) US20160288801A1 (zh)
EP (1) EP3069949A4 (zh)
CN (1) CN103693038B (zh)
WO (1) WO2015085798A1 (zh)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103693038B (zh) * 2013-12-13 2016-06-22 华为技术有限公司 交通工具系统控制方法以及控制系统
US9684306B2 (en) * 2015-01-09 2017-06-20 Qualcomm Incorporated Transitioning from autonomous vehicle control to operator vehicle control
EP3043568B1 (en) * 2015-01-12 2017-11-15 Volvo Car Corporation A system and method for scheduling a video conference in an autonomous vehicle
JP6269546B2 (ja) * 2015-03-23 2018-01-31 トヨタ自動車株式会社 自動運転装置
DE102015209137A1 (de) 2015-05-19 2016-11-24 Robert Bosch Gmbh Verfahren und System zur Steuerung einer Fahrfunktion eines Fahrzeuges
JP6678311B2 (ja) * 2015-12-24 2020-04-08 パナソニックIpマネジメント株式会社 運転支援方法およびそれを利用した運転支援装置、情報提示装置、車両
CN107315359B (zh) * 2016-04-27 2019-09-20 华为技术有限公司 车辆控制方法及系统
JP2017220097A (ja) * 2016-06-09 2017-12-14 株式会社デンソー 運転支援装置
DE102017200432B4 (de) 2017-01-12 2022-08-18 Audi Ag Verfahren zum Betreiben eines Sicherheitssystems für ein Kraftfahrzeug und Sicherheitssystem
JP6520974B2 (ja) * 2017-03-14 2019-05-29 オムロン株式会社 運転切り替え判定装置、及び運転切り替え判定のためのプログラム
FR3070327B1 (fr) * 2017-08-24 2020-10-09 Psa Automobiles Sa Systeme de commande d’un moniteur principal de vehicule autonome
CN107697072A (zh) * 2017-09-25 2018-02-16 北京新能源汽车股份有限公司 驾驶模式的切换方法、车辆和整车控制器
JP6559204B2 (ja) * 2017-10-19 2019-08-14 本田技研工業株式会社 車両制御装置
CN108650401A (zh) * 2018-03-28 2018-10-12 维沃移动通信有限公司 一种应用程序控制方法及移动终端
FR3096151B1 (fr) * 2019-05-16 2021-04-23 Psa Automobiles Sa Procédé et dispositif de contrôle d’un système interactif pour véhicule
CN114257851A (zh) * 2020-09-21 2022-03-29 逸驾智能科技有限公司 用于控制内容呈现的方法、装置、设备和介质
US20240051545A1 (en) * 2022-08-15 2024-02-15 Ford Global Technologies, Llc Vehicle sensing with body coupled communication

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3792976B2 (ja) * 2000-01-20 2006-07-05 矢崎総業株式会社 車両用多重通信装置
CN101758855A (zh) * 2010-02-01 2010-06-30 中国科学院合肥物质科学研究院 一种无人驾驶车辆转向装置及其控制方法
CN101823435A (zh) * 2009-03-03 2010-09-08 珠海市智汽电子科技有限公司 便于外置安装、便于手动/自动切换的车辆自动驾驶系统
CN102053619A (zh) * 2009-11-06 2011-05-11 北京理工大学 微小型无人直升机自动驾驶和手动遥控飞行切换方法
CN103693038A (zh) * 2013-12-13 2014-04-02 华为技术有限公司 交通工具系统控制方法以及控制系统

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19743024A1 (de) * 1997-09-29 1999-04-08 Daimler Chrysler Ag Kraftfahrzeug mit autonomer Fahrzeugführung und elektronischen Kommunikationsmitteln
KR20060039229A (ko) * 2004-11-02 2006-05-08 엘지전자 주식회사 휴대단말기에서 운전 중 통화차단 방법
JP4735310B2 (ja) * 2005-04-15 2011-07-27 株式会社デンソー 走行支援装置
KR100663474B1 (ko) * 2005-10-26 2007-01-02 삼성전자주식회사 휴대용 단말기에서 주행 중 멀티미디어 방송 데이터를처리하는 방법
JP4985103B2 (ja) * 2007-05-28 2012-07-25 トヨタ自動車株式会社 車両の自動運転装置
JP4973687B2 (ja) * 2009-05-13 2012-07-11 トヨタ自動車株式会社 走行支援装置
DE102009048954A1 (de) * 2009-10-10 2011-04-14 Daimler Ag Verfahren und Vorrichtung zum automatischen Betreiben eines Fahrzeugs in einem keine Nutzeraktion erfordernden autonomen Fahrbetrieb
DE102010025894A1 (de) * 2010-07-02 2012-01-05 Audi Ag Verfahren zum Betrieb eines wenigstens eine Information an einen Fahrer ausgebende und/oder Informationen von einem Fahrer entgegennehmende Funktionalität aufweisenden Fahrzeugsystems eines Kraftfahrzeugs
JP6103620B2 (ja) * 2012-04-12 2017-03-29 クラリオン株式会社 車載情報システム、情報端末、アプリケーション実行方法、プログラム

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3792976B2 (ja) * 2000-01-20 2006-07-05 矢崎総業株式会社 車両用多重通信装置
CN101823435A (zh) * 2009-03-03 2010-09-08 珠海市智汽电子科技有限公司 便于外置安装、便于手动/自动切换的车辆自动驾驶系统
CN102053619A (zh) * 2009-11-06 2011-05-11 北京理工大学 微小型无人直升机自动驾驶和手动遥控飞行切换方法
CN101758855A (zh) * 2010-02-01 2010-06-30 中国科学院合肥物质科学研究院 一种无人驾驶车辆转向装置及其控制方法
CN103693038A (zh) * 2013-12-13 2014-04-02 华为技术有限公司 交通工具系统控制方法以及控制系统

Also Published As

Publication number Publication date
CN103693038A (zh) 2014-04-02
US20160288801A1 (en) 2016-10-06
CN103693038B (zh) 2016-06-22
EP3069949A1 (en) 2016-09-21
EP3069949A4 (en) 2016-12-07

Similar Documents

Publication Publication Date Title
WO2015085798A1 (zh) 交通工具系统控制方法以及控制系统
CN106293507B (zh) 具有外部存储器的电子设备及操作电子设备的方法
CN103020537B (zh) 数据加密方法和装置、数据解密方法和装置
US20150245198A1 (en) System for controlling a vehicle computer using a mobile telephone
US11059435B2 (en) Vehicle software control device
CN113183871A (zh) 一种迎宾灯的控制方法、装置、电子设备及存储介质
CN103744686A (zh) 智能终端中应用安装的控制方法和系统
KR20150089660A (ko) 단말의 애플리케이션 부팅 시스템 및 방법
KR102337990B1 (ko) 권한 설정 토큰을 이용하는 전자 장치
US11429425B2 (en) Electronic device and display and control method thereof to provide display based on operating system
US11356726B2 (en) In-vehicle device and method for managing user interfaces
EP2905700A1 (en) Operating system recovery method, apparatus and terminal device
US10776130B2 (en) Operating system startup acceleration
WO2020010192A1 (en) Vehicular data privacy management systems and methods
WO2022228528A1 (zh) 一种车辆仿真系统的模拟方法、装置、设备及存储介质
JP6564845B2 (ja) オペレーティングシステム起動加速
RU2676892C2 (ru) Способ и система для компенсации шума воздуходувного устройства в транспортном средстве
KR102177407B1 (ko) 가상화를 이용한 차량용 avn 시스템 및 그 작동 방법
CN104866088A (zh) 汽车娱乐主机、汽车娱乐主机控制方法及装置
US9691182B1 (en) System and method for adaptive display restriction in a headset computer
TW202022570A (zh) 使用者介面整合方法和車載裝置
EP3544860B1 (en) Vehicle operating method and vehicle operating apparatus
CN116016578A (zh) 一种基于设备状态和用户行为的智能语音引导方法
WO2014201967A1 (zh) 数据卡、数据卡切换方法及装置
EP3523745B1 (en) Electronic device, method for controlling thereof and computer-readable recording medium

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014870624

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014870624

Country of ref document: EP