Data calling method
By determining whether to replace it with virtual data based on the control mode and data type in the smart cockpit, the problem that data calling methods in the smart cockpit are difficult to balance privacy protection and driving functions, and the data security and user experience are improved.
Patent Information
- Application Number
- CN202411323435.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-23
- Publication Date
- 2025-01-10
AI Technical Summary
Existing data calling methods are difficult to balance privacy protection and driving function requirements in the smart cockpit, resulting in the risk of target data leakage. The method of users frequently logging in and out to reduce risks is unfriendly, affecting the user experience.
By detecting the call request of the target data, it is determined whether it is necessary to replace it with virtual data based on the current control mode and data type, and provides virtual data to respond to the call request to protect privacy, and replace the target data without affecting the driving function.
It effectively reduces the risk of real data leakage, improves data security, avoids the inconvenience caused by frequent login and logs out, and balances the needs of privacy protection and driving functions.
Smart Images
Figure CN119293838A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of vehicle technology, and in particular to a data calling method. Background Art
[0002] At present, with the development of smart cockpit technology, smart cockpits involve many user interactions, which generates more and more target data. If these target data are not desensitized, it is easy to cause target data leakage or passive leakage in the car use scenario. For example, when carrying passengers, the cockpit screen will inevitably show the historical data used by the owner, such as the geographical location just searched. If the user frequently logs in and out of the screen cockpit account to reduce the risk of data leakage, it is extremely unfriendly to the user itself. After logging out, some of the original historical records cannot be quickly viewed and used.
[0003] Existing data calling methods usually use pre-set user data as the data to be called, and replace the data to be called with virtual data, which makes it difficult to balance the needs of privacy protection and driving functions. Summary of the invention
[0004] In view of the above problems, an embodiment of the present application provides a data calling method, which is used to solve the technical problem in the prior art that pre-set user data is used as the data to be called, and the data to be called is replaced with virtual data, which makes it difficult to balance the requirements of privacy protection and driving functions.
[0005] According to one aspect of an embodiment of the present application, a data calling method is provided, the method comprising:
[0006] When a call request for target data is detected, judging whether it is necessary to call virtual data corresponding to the target data according to the current control mode and the data type of the target data;
[0007] If necessary, responding to the call request with the virtual data;
[0008] If not necessary, respond to the call request with the target data.
[0009] According to another aspect of an embodiment of the present application, a data calling device is provided, including:
[0010] A data calling judgment module is used to judge whether it is necessary to call the virtual data corresponding to the target data according to the current control mode and the data type of the target data when a calling request of the target data is detected;
[0011] A first call request response module, used for responding to the call request with the virtual data if necessary;
[0012] The second call request response module is used to respond to the call request with the target data if it is not necessary.
[0013] In an optional manner, the data call judgment module is further used to:
[0014] In the case where the current control mode is the normal control mode, if the target is a real-time data type or a non-real-time data type, it is determined that there is no need to call the virtual data corresponding to the target data;
[0015] When the current control mode is the privacy mode, if the target data is a real-time data type, it is determined that there is no need to call the virtual data corresponding to the target data; if the target data is a non-real-time data type, it is determined that the virtual data corresponding to the target data needs to be called, or whether the virtual data corresponding to the target data needs to be called is determined according to user-defined instructions.
[0016] In an optional manner, the data calling device further includes a data type determination module, which is used to:
[0017] Acquire calling data of the target data within a preset time period, and determine a calling mode of the target data according to the calling data;
[0018] The data type of the target data is determined according to the calling mode.
[0019] In an optional manner, determining the data type of the target data according to the calling mode includes:
[0020] When the calling mode is a high-frequency periodic mode, the target data is a real-time data type;
[0021] When the calling mode is a single mode, the target data is a non-real-time data type;
[0022] When the calling mode is one of the low-frequency non-periodic mode, the high-frequency non-periodic mode and the low-frequency periodic mode, a semantic analysis is performed on the calling interface function name of the target data, and the data type of the target data is determined according to the semantic analysis result.
[0023] In an optional manner, performing semantic analysis on the name of the calling interface function of the target data and determining the data type of the target data according to the semantic analysis result includes:
[0024] When the semantic analysis result includes preset keywords, determining that the target data is a real-time data type;
[0025] When the semantic analysis result does not include the preset keyword, it is determined that the target data is a non-real-time data type.
[0026] In an optional manner, the data calling device further includes a calling data acquisition module, which is used to:
[0027] Obtaining call data of the target data within a preset time period through diary events in the vehicle driving system;
[0028] In an optional manner, calling the data acquisition module is also used to:
[0029] The calling data of the target data within a preset time period is acquired by monitoring events, wherein the monitoring events are set at the interface points of the target data.
[0030] In an optional manner, calling the data acquisition module is also used to:
[0031] According to the call record of the target data by the execution unit, the call data of the target data within a preset time period is acquired according to the call record, wherein the execution unit includes at least one of an application program and a system task.
[0032] In an optional manner, the data calling device further includes a virtual data generating module, which is used to:
[0033] In response to a virtual data generation instruction input by a user, virtual data corresponding to the target data is generated within a preset range.
[0034] In an optional manner, the virtual data generation module is further used to:
[0035] In response to the virtual data configuration instruction input by the user, the pre-configured data is used as the virtual data of the target data.
[0036] In an optional manner, the virtual data is used for display by the first application that initiates the call request, or is used for the first application to generate and display response display data according to the virtual data.
[0037] According to another aspect of an embodiment of the present application, a data calling device is provided, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus;
[0038] The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute operations such as the above-mentioned data calling method.
[0039] According to another aspect of an embodiment of the present application, a computer-readable storage medium is provided, wherein at least one executable instruction is stored in the storage medium. When the executable instruction is executed on a data calling device / apparatus, the data calling device / apparatus performs operations such as the above-mentioned data calling method.
[0040] The embodiment of the present application determines whether it is necessary to call the virtual data corresponding to the target data based on the current control mode and the data type of the target data, takes into account the functional role of the target data in actual driving, determines the target data that can be replaced with virtual data, ensures that the normal driving function is not affected after the target data is replaced with virtual data, and can provide privacy protection for the target data involving privacy, thereby balancing the needs of privacy protection and driving functions.
[0041] Furthermore, the embodiment of the present application provides a normal control mode and a privacy control mode through a vehicle-side application. According to the control mode and target data type selected by the user, in the privacy control mode, the target data of the non-real-time data type responds to the call request with the virtual data, thereby replacing the current target data with the virtual data for display, which can effectively reduce the risk of real data leakage without affecting the normal driving function.
[0042] The above description is only an overview of the technical solution of the embodiment of the present application. In order to more clearly understand the technical means of the embodiment of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present application more obvious and easy to understand, the specific implementation mode of the present invention is specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] The accompanying drawings are only used to illustrate the embodiments and are not to be considered as limiting the present invention. In addition, the same reference symbols are used to represent the same components throughout the accompanying drawings. In the accompanying drawings:
[0044] Figure 1 A schematic diagram showing a flow chart of a data calling method provided in an embodiment of the present application is shown;
[0045] Figure 2 A schematic diagram of the structure of a data calling device provided in an embodiment of the present application is shown;
[0046] Figure 3 A schematic diagram of the structure of a data calling device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION
[0047] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be limited to the embodiments set forth herein.
[0048] Figure 1 FIG. 1 is a flow chart of a data calling method provided by an embodiment of the present application, and the method is executed by a data calling device. Figure 1 As shown, the method comprises the following steps:
[0049] Step 110: when a call request for target data is detected, judging whether it is necessary to call virtual data corresponding to the target data according to the current control mode and the data type of the target data;
[0050] Among them, whether there is a call request for target data can be detected through the vehicle-side application. The current control mode includes a normal control mode and a privacy control module, and the user can select the current control mode through the vehicle-side application. The target data includes at least one of positioning data, image data and text data for the user to interact with the vehicle driving system. The data type of the target data includes a real-time data type and a non-real-time data type.
[0051] In an embodiment of the present application, data of the real-time data type may be key driving data related to real-time navigation and intelligent driving. For this part of data, the call request is not responded to with virtual data, and the current real data continues to be used for display.
[0052] Data of non-real-time data type may be non-critical driving data for displaying historical tracks and other locations. For this part of non-real-time data, virtual data is used to respond to the call request so that the virtual data is displayed in the front-end application.
[0053] Step 120: If necessary, respond to the call request with the virtual data;
[0054] In the embodiment of the present invention, the virtual data may be generated according to a preset rule, or may be pre-set.
[0055] Step 130: If not required, respond to the call request with the target data.
[0056] The embodiment of the present application determines whether it is necessary to call the virtual data corresponding to the target data according to the current control mode and the data type of the target data on the vehicle side, takes into account the functional role of the target data in actual driving, determines the target data that can be replaced with virtual data, ensures that the normal driving function is not affected after the target data is replaced with virtual data, and can provide privacy protection for the target data involving privacy, thereby balancing the needs of privacy protection and driving functions.
[0057] Furthermore, after determining that the virtual data corresponding to the target data needs to be called, the calling request is responded to with the virtual data, so that virtual data that meets the requirements can be quickly and accurately generated during the real-time interaction process without exiting the current login state and without affecting the overall performance and user experience of the vehicle's driving system.
[0058] In an optional manner, the user can set specific data needs according to actual needs to call the virtual data corresponding to the target data. For example, the user explicitly specifies that certain applications or functions are not allowed to use real positioning data, image data or text, that is, the virtual data corresponding to the target data needs to be called.
[0059] In an optional manner, step 110: judging whether it is necessary to call the virtual data corresponding to the target data according to the current control mode and the data type of the target data, includes:
[0060] Step 111: when the current control mode is the normal control mode, if the target is a real-time data type or a non-real-time data type, it is determined that it is not necessary to call the virtual data corresponding to the target data;
[0061] In the embodiment of the present application, the normal control mode is a control mode in which virtual data replacement processing is not performed on the current target data.
[0062] Step 112: When the current control mode is the privacy mode, if the target data is a real-time data type, it is determined that there is no need to call the virtual data corresponding to the target data; if the target data is a non-real-time data type, it is determined that there is a need to call the virtual data corresponding to the target data, or it is determined whether there is a need to call the virtual data corresponding to the target data according to user-defined instructions.
[0063] In the embodiment of the present application, the privacy mode is a control mode that requires virtual data to be replaced and displayed for target data that meets the conditions.
[0064] The embodiment of the present application can provide a normal control mode and a privacy control mode through a vehicle-side application. According to the control mode and target data type selected by the user, in the privacy control mode, the target data of the non-real-time data type responds to the call request with the virtual data, thereby replacing the current target data with the virtual data for display, which can effectively avoid the risk of real data being leaked and improve data security.
[0065] In an optional manner, the data calling method further includes:
[0066] Acquire calling data of the target data within a preset time period, and determine a calling mode of the target data according to the calling data;
[0067] In the embodiment of the present application, the call data includes the call time and call count of the target data.
[0068] The data type of the target data is determined according to the calling mode.
[0069] The embodiment of the present application can determine the data type of the target data according to the calling mode of the target data, and thus can judge whether the corresponding virtual data needs to be called according to the data type of the target data, thereby effectively improving the accuracy of data calling.
[0070] In an optional manner, determining the data type of the target data according to the calling mode includes:
[0071] When the calling mode is a high-frequency periodic mode, the target data is a real-time data type;
[0072] When the calling mode is a single mode, the target data is a non-real-time data type;
[0073] When the calling mode is one of the low-frequency non-periodic mode, the high-frequency non-periodic mode and the low-frequency periodic mode, a semantic analysis is performed on the calling interface function name of the target data, and the data type of the target data is determined according to the semantic analysis result.
[0074] In the embodiment of the present application, when the calling mode of the target data is a high-frequency periodic mode, the function of the target data may be related to intelligent driving, that is, it is a real-time data type and cannot be replaced by virtual data. When the calling mode of the target data is a single mode, it is a single delivery configuration of the downstream function and is not used for real-time decision-making, that is, it is a non-real-time data type and can be replaced by corresponding virtual data.
[0075] When the calling mode is one of the low-frequency non-periodic mode, the high-frequency non-periodic mode and the low-frequency periodic mode, the data type of the target data is further determined in combination with the semantic analysis result.
[0076] The embodiment of the present application determines the data type of the target data according to the calling mode, and further responds to the calling request with virtual data, replacing the actual target data that meets the conditions with the virtual data, taking into account the actual usage of the target data, thereby effectively improving the accuracy of data calling, and further reducing the risk of data leakage involving user privacy, thereby improving data security.
[0077] In an optional manner, when the calling mode is one of a low-frequency non-periodic mode, a high-frequency non-periodic mode and a low-frequency periodic mode, it is also possible to further determine whether it is necessary to call the virtual data corresponding to the target data in combination with the sensitivity of the current target data. For example, the target data is positioning data, and high-sensitivity positioning data (such as location verification involving financial transactions) does not require calling the virtual data corresponding to the target data, while low-sensitivity positioning data (such as approximate location in weather applications) may require calling the virtual data corresponding to the target data.
[0078] In an optional manner, performing semantic analysis on the name of the calling interface function of the target data and determining the data type of the target data according to the semantic analysis result includes:
[0079] When the semantic analysis result includes preset keywords, determining that the target data is a real-time data type;
[0080] In an embodiment of the present application, preset keywords may include naming terms such as "adas", "navigation", and "live xx". The preset keywords are included in the semantic analysis results, which can determine that the target data is used for key driving functions such as real-time navigation and emergency rescue, that is, it is a real-time data type.
[0081] When the semantic analysis result does not include the preset keyword, it is determined that the target data is a non-real-time data type.
[0082] In an embodiment of the present application, when it is determined based on semantic analysis that the target data is used for non-critical personalized recommendations, advertising push, etc., that is, the target data is a non-real-time data type, the target data can be replaced by virtual data.
[0083] The embodiment of the present application performs semantic analysis on the calling interface function name of the target data, and can accurately determine the data type of the target data according to the semantic analysis result.
[0084] In an optional manner, whether it is necessary to call the virtual data corresponding to the target data may also be determined according to the timeliness of the data, including:
[0085] Determine the timeliness requirements of the target data function. For example, if real-time and accurate positioning is required to support the operation (such as real-time traffic information acquisition), there is no need to call the virtual data corresponding to the target data; if the timeliness requirements are not high (such as historical travel records), the virtual data corresponding to the target data can be called. The embodiment of the present application can be judged by identifying whether the function name contains key words such as "history".
[0086] In an optional manner, the acquiring the call data of the target data within a preset time period further includes:
[0087] The calling data of the target data within a preset time period is obtained through the diary events in the vehicle driving system.
[0088] In an embodiment of the present application, the diary event may also record the calling source of the target data, and the data type may be further determined in combination with the calling source.
[0089] In an optional manner, the acquiring the call data of the target data within a preset time period further includes:
[0090] The calling data of the target data within a preset time period is acquired by monitoring events, wherein the monitoring events are set at the interface points of the target data.
[0091] In an embodiment of the present application, the monitoring event is set at the interface point of the target data to monitor the calling status of the target data in real time, so as to accurately obtain the usage status of the target data, and then determine the calling mode of the target data within a preset time period, which is conducive to improving the accuracy of data calling.
[0092] In an optional manner, the acquiring the call data of the target data within a preset time period further includes:
[0093] According to the call record of the target data by the execution unit, the call data of the target data within a preset time period is acquired according to the call record, wherein the execution unit includes at least one of an application program and a system task.
[0094] In an embodiment of the present application, the user uses the target data to interact with the vehicle side through the execution unit. By obtaining the call record of the execution unit on the target data, the call data of the target data within a preset time period can be accurately obtained, so that the data type of the target data can be accurately determined, and then the target data that needs to call the corresponding virtual data to respond can be accurately determined, which can effectively improve the accuracy of data calling.
[0095] In an optional manner, the data calling method further includes:
[0096] In response to a virtual data generation instruction input by a user, virtual data corresponding to the target data is generated within a preset range.
[0097] In the embodiment of the present application, corresponding virtual data can be automatically generated according to the virtual data generation instruction input by the user.
[0098] For example, when logged in, the user can select the one-click privacy mode through the vehicle-side application to generate virtual data. The one-click privacy mode can automatically generate virtual data within a preset range.
[0099] For example: the target data is the user's real location data, and the location address is County B, City A. According to the virtual data generation instruction input by the user, the corresponding virtual data is generated within the scope of City A, for example, County C, City A. County C, City A is replaced with County B, City A for display, so that the generated virtual data has a certain degree of authenticity and reduces the risk of leakage of the user's real location data.
[0100] The embodiment of the present application can quickly generate corresponding virtual data through a one-click privacy mode to replace the current target data, and can quickly replace the target data with the corresponding virtual data for display in the logged-in state, effectively improving the convenience of data call.
[0101] In an optional manner, the data calling method further includes:
[0102] In response to the virtual data configuration instruction input by the user, the pre-configured data is used as the virtual data of the target data.
[0103] In the embodiment of the present application, the personalized mode can be selected through the vehicle-side application, and the user can enter the pre-configured virtual data through the personalized mode, use the pre-configured virtual data as the virtual data of the target data, and respond to the call request with the virtual data, and replace the target data with the virtual data for display. For example, if the target data is the location data of city A, the pre-configured location data can be any location data such as city A, city B, etc.; if the target data is the picture data of the head portrait of person A, the pre-configured picture can be any picture data such as the head portrait of person B, the head portrait of person C, etc.; if the target data is the text data of the text content of A, the pre-configured location data can be any text data such as the text content of B, the text content of C, etc.
[0104] In the embodiment of the present application, when the target data is location data, in some cases the user may forget that the weather application actually calls the location data. In this case, the system only needs the user to configure the location data that he wants to present, and then all application data that calls this data will be linked to be updated accordingly. For example, if the location data that needs to be replaced is used to display historical tracks, or the location of "company" or "home", the personalized mode can be used to generate or display virtual data that the user prefers, effectively improving the flexibility of data calling.
[0105] It should be noted that virtual data is not used to replace the real data necessary to affect the driving function itself, but is only used to replace the target data for display.
[0106] In an embodiment of the present application, the data pre-configured by the user is used as the virtual data of the target data. The user can configure the corresponding virtual data to replace the reality according to actual needs, which can meet the data calling requirements of various specific scenarios, thereby effectively reducing the risk of target data leakage while ensuring necessary functions.
[0107] In an optional manner, the virtual data is used for display by the first application that initiates the call request, or is used for the first application to generate and display response display data according to the virtual data.
[0108] In the embodiment of the present application, the virtual data can be directly displayed by the first application, or display data of the display response can be generated based on the virtual data, thereby effectively improving the flexibility of data calling.
[0109] Implementing the embodiments of the present application has the following beneficial effects:
[0110] The embodiment of the present application determines whether it is necessary to call the virtual data corresponding to the target data based on the current control mode and the data type of the target data, takes into account the functional role of the target data in actual driving, determines the target data that can be replaced with virtual data, ensures that the normal driving function is not affected after the target data is replaced with virtual data, and can provide privacy protection for the target data involving privacy, thereby balancing the needs of privacy protection and driving functions.
[0111] Furthermore, the embodiment of the present application provides a normal control mode and a privacy control mode through a vehicle-side application. According to the control mode and target data type selected by the user, in the privacy control mode, the target data of the non-real-time data type responds to the call request with the virtual data, thereby replacing the current target data with the virtual data for display, which can effectively avoid the risk of real data leakage and improve data security.
[0112] Figure 2 FIG. 2 shows a schematic diagram of the structure of an embodiment of a data calling device of the present invention. Figure 2 As shown, the device 200 includes: a data call determination module 210, a first call request response module 220 and a second call request response module 230.
[0113] In an optional manner, the data call determination module 210 is further configured to:
[0114] In the case where the current control mode is the normal control mode, if the target is a real-time data type or a non-real-time data type, it is determined that there is no need to call the virtual data corresponding to the target data;
[0115] When the current control mode is the privacy mode, if the target data is a real-time data type, it is determined that there is no need to call the virtual data corresponding to the target data; if the target data is a non-real-time data type, it is determined that the virtual data corresponding to the target data needs to be called, or whether the virtual data corresponding to the target data needs to be called is determined according to user-defined instructions.
[0116] In an optional manner, the data calling device further includes a data type determination module, which is used to:
[0117] Acquire calling data of the target data within a preset time period, and determine a calling mode of the target data according to the calling data;
[0118] The data type of the target data is determined according to the calling mode.
[0119] In an optional manner, determining the data type of the target data according to the calling mode includes:
[0120] When the calling mode is a high-frequency periodic mode, the target data is a real-time data type;
[0121] When the calling mode is a single mode, the target data is a non-real-time data type;
[0122] When the calling mode is one of the low-frequency non-periodic mode, the high-frequency non-periodic mode and the low-frequency periodic mode, a semantic analysis is performed on the calling interface function name of the target data, and the data type of the target data is determined according to the semantic analysis result.
[0123] In an optional manner, performing semantic analysis on the name of the calling interface function of the target data and determining the data type of the target data according to the semantic analysis result includes:
[0124] When the semantic analysis result includes preset keywords, determining that the target data is a real-time data type;
[0125] When the semantic analysis result does not include the preset keyword, it is determined that the target data is a non-real-time data type.
[0126] In an optional manner, the data calling device further includes a calling data acquisition module, which is used to:
[0127] Obtaining call data of the target data within a preset time period through diary events in the vehicle driving system;
[0128] In an optional manner, calling the data acquisition module is also used to:
[0129] The calling data of the target data within a preset time period is acquired by monitoring events, wherein the monitoring events are set at the interface points of the target data.
[0130] In an optional manner, the data acquisition module is called to:
[0131] According to the call record of the target data by the execution unit, the call data of the target data within a preset time period is acquired according to the call record, wherein the execution unit includes at least one of an application program and a system task.
[0132] In an optional manner, the data calling device further includes a virtual data generating module, which is used to:
[0133] In response to a virtual data generation instruction input by a user, virtual data corresponding to the target data is generated within a preset range.
[0134] In an optional manner, the virtual data generation module is further used to:
[0135] In response to the virtual data configuration instruction input by the user, the pre-configured data is used as the virtual data of the target data.
[0136] In an optional manner, the virtual data is used for display by the first application that initiates the call request, or is used for the first application to generate and display response display data according to the virtual data.
[0137] The embodiment of the present application determines whether it is necessary to call the virtual data corresponding to the target data based on the current control mode and the data type of the target data, takes into account the functional role of the target data in actual driving, determines the target data that can be replaced with virtual data, ensures that the normal driving function is not affected after the target data is replaced with virtual data, and can provide privacy protection for the target data involving privacy, thereby balancing the needs of privacy protection and driving functions.
[0138] Furthermore, the embodiment of the present application provides a normal control mode and a privacy control mode through a vehicle-side application. According to the control mode and target data type selected by the user, in the privacy control mode, the target data of the non-real-time data type responds to the call request with the virtual data, thereby replacing the current target data with the virtual data for display, which can effectively avoid the risk of real data leakage and improve data security.
[0139] Figure 3 The schematic diagram of the structure of the embodiment of the data calling device of the present invention is shown. The specific embodiment of the present invention does not limit the specific implementation of the data calling device.
[0140] like Figure 3As shown, the data calling device may include: a processor (processor) 302 , a communication interface (Communications Interface) 304 , a memory (memory) 306 , and a communication bus 308 .
[0141] The processor 302, the communication interface 304, and the memory 306 communicate with each other via the communication bus 308. The communication interface 304 is used to communicate with other devices such as a client or other server network elements. The processor 302 is used to execute the program 310, which can specifically execute the relevant steps in the above-mentioned data calling method embodiment.
[0142] Specifically, the program 310 may include program code including computer executable instructions.
[0143] The processor 302 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the data calling device may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.
[0144] The memory 306 is used to store the program 310. The memory 306 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
[0145] Program 310 may be specifically called by processor 302 to enable device XXX to perform the following operations:
[0146] When a call request for target data is detected, judging whether it is necessary to call virtual data corresponding to the target data according to the current control mode and the data type of the target data;
[0147] If necessary, responding to the call request with the virtual data;
[0148] If not necessary, respond to the call request with the target data.
[0149] In an optional manner, the program 310 is called by the processor 302 to enable the data calling device to perform the following operations:
[0150] In the case where the current control mode is the normal control mode, if the target is a real-time data type or a non-real-time data type, it is determined that there is no need to call the virtual data corresponding to the target data;
[0151] When the current control mode is the privacy mode, if the target data is a real-time data type, it is determined that there is no need to call the virtual data corresponding to the target data; if the target data is a non-real-time data type, it is determined that the virtual data corresponding to the target data needs to be called, or whether the virtual data corresponding to the target data needs to be called is determined according to user-defined instructions.
[0152] In an optional manner, the program 310 is called by the processor 302 to enable the data calling device to perform the following operations:
[0153] Acquire calling data of the target data within a preset time period, and determine a calling mode of the target data according to the calling data;
[0154] The data type of the target data is determined according to the calling mode.
[0155] In an optional manner, the program 310 is called by the processor 302 to enable the data calling device to perform the following operations:
[0156] When the calling mode is a high-frequency periodic mode, the target data is a real-time data type;
[0157] When the calling mode is a single mode, the target data is a non-real-time data type;
[0158] When the calling mode is one of the low-frequency non-periodic mode, the high-frequency non-periodic mode and the low-frequency periodic mode, a semantic analysis is performed on the calling interface function name of the target data, and the data type of the target data is determined according to the semantic analysis result.
[0159] In an optional manner, the program 310 is called by the processor 302 to enable the data calling device to perform the following operations:
[0160] When the semantic analysis result includes preset keywords, determining that the target data is a real-time data type;
[0161] When the semantic analysis result does not include the preset keyword, it is determined that the target data is a non-real-time data type.
[0162] In an optional manner, the program 310 is called by the processor 302 to enable the data calling device to perform the following operations:
[0163] The calling data of the target data within a preset time period is obtained through the diary events in the vehicle driving system.
[0164] In an optional manner, the program 310 is called by the processor 302 to enable the data calling device to perform the following operations:
[0165] The calling data of the target data within a preset time period is acquired by monitoring events, wherein the monitoring events are set at the interface points of the target data.
[0166] In an optional manner, the program 310 is called by the processor 302 to enable the data calling device to perform the following operations:
[0167] According to the call record of the target data by the execution unit, the call data of the target data within a preset time period is acquired according to the call record, wherein the execution unit includes at least one of an application program and a system task.
[0168] In an optional manner, the program 310 is called by the processor 302 to enable the data calling device to perform the following operations:
[0169] In response to a virtual data generation instruction input by a user, virtual data corresponding to the target data is generated within a preset range.
[0170] In an optional manner, the program 310 is called by the processor 302 to enable the data calling device to perform the following operations:
[0171] In response to the virtual data configuration instruction input by the user, the pre-configured data is used as the virtual data of the target data.
[0172] In an optional manner, the program 310 is called by the processor 302 to enable the data calling device to perform the following operations:
[0173] The virtual data is used for display by the first application that initiates the call request, or is used for the first application to generate and display response display data according to the virtual data.
[0174] The embodiment of the present application determines whether it is necessary to call the virtual data corresponding to the target data based on the current control mode and the data type of the target data, takes into account the functional role of the target data in actual driving, determines the target data that can be replaced with virtual data, ensures that the normal driving function is not affected after the target data is replaced with virtual data, and can provide privacy protection for the target data involving privacy, thereby balancing the needs of privacy protection and driving functions.
[0175] Furthermore, the embodiment of the present application provides a normal control mode and a privacy control mode through a vehicle-side application. According to the control mode and target data type selected by the user, in the privacy control mode, the target data of the non-real-time data type responds to the call request with the virtual data, thereby replacing the current target data with the virtual data for display, which can effectively avoid the risk of real data leakage and improve data security.
[0176] An embodiment of the present application provides a computer-readable storage medium, which stores at least one executable instruction. When the executable instruction is executed on a data calling device / apparatus, the data calling device / apparatus executes the data calling method in any of the above method embodiments.
[0177] The executable instructions may be specifically used to enable the data calling device / apparatus to perform the following operations:
[0178] When a call request for target data is detected, judging whether it is necessary to call virtual data corresponding to the target data according to the current control mode and the data type of the target data;
[0179] If necessary, responding to the call request with the virtual data;
[0180] If not necessary, respond to the call request with the target data.
[0181] In an optional manner, the executable instruction enables the data calling device / apparatus to perform the following operations:
[0182] In the case where the current control mode is the normal control mode, if the target is a real-time data type or a non-real-time data type, it is determined that there is no need to call the virtual data corresponding to the target data;
[0183] When the current control mode is the privacy mode, if the target data is a real-time data type, it is determined that there is no need to call the virtual data corresponding to the target data; if the target data is a non-real-time data type, it is determined that the virtual data corresponding to the target data needs to be called, or whether the virtual data corresponding to the target data needs to be called is determined according to user-defined instructions.
[0184] In an optional manner, the executable instruction enables the data calling device / apparatus to perform the following operations:
[0185] Acquire calling data of the target data within a preset time period, and determine a calling mode of the target data according to the calling data;
[0186] The data type of the target data is determined according to the calling mode.
[0187] In an optional manner, the executable instruction enables the data calling device / apparatus to perform the following operations:
[0188] When the calling mode is a high-frequency periodic mode, the target data is a real-time data type;
[0189] When the calling mode is a single mode, the target data is a non-real-time data type;
[0190] When the calling mode is one of the low-frequency non-periodic mode, the high-frequency non-periodic mode and the low-frequency periodic mode, a semantic analysis is performed on the calling interface function name of the target data, and the data type of the target data is determined according to the semantic analysis result.
[0191] In an optional manner, the executable instruction enables the data calling device / apparatus to perform the following operations:
[0192] When the semantic analysis result includes preset keywords, determining that the target data is a real-time data type;
[0193] When the semantic analysis result does not include the preset keyword, it is determined that the target data is a non-real-time data type.
[0194] In an optional manner, the executable instruction enables the data calling device / apparatus to perform the following operations:
[0195] The calling data of the target data within a preset time period is obtained through the diary events in the vehicle driving system.
[0196] In an optional manner, the executable instruction enables the data calling device / apparatus to perform the following operations:
[0197] The calling data of the target data within a preset time period is acquired by monitoring events, wherein the monitoring events are set at the interface points of the target data.
[0198] In an optional manner, the executable instruction enables the data calling device / apparatus to perform the following operations:
[0199] According to the call record of the target data by the execution unit, the call data of the target data within a preset time period is acquired according to the call record, wherein the execution unit includes at least one of an application program and a system task.
[0200] In an optional manner, the executable instruction enables the data calling device / apparatus to perform the following operations:
[0201] In response to a virtual data generation instruction input by a user, virtual data corresponding to the target data is generated within a preset range.
[0202] In an optional manner, the executable instruction enables the data calling device / apparatus to perform the following operations:
[0203] In response to the virtual data configuration instruction input by the user, the pre-configured data is used as the virtual data of the target data.
[0204] In an optional manner, the executable instruction enables the data calling device / apparatus to perform the following operations:
[0205] The virtual data is used for display by the first application that initiates the call request, or is used for the first application to generate and display response display data according to the virtual data.
[0206] The embodiment of the present application determines whether it is necessary to call the virtual data corresponding to the target data based on the current control mode and the data type of the target data, takes into account the functional role of the target data in actual driving, determines the target data that can be replaced with virtual data, ensures that the normal driving function is not affected after the target data is replaced with virtual data, and can provide privacy protection for the target data involving privacy, thereby balancing the needs of privacy protection and driving functions.
[0207] Furthermore, the embodiment of the present application provides a normal control mode and a privacy control mode through a vehicle-side application. According to the control mode and target data type selected by the user, in the privacy control mode, the target data of the non-real-time data type responds to the call request with the virtual data, thereby replacing the current target data with the virtual data for display, which can effectively avoid the risk of real data leakage and improve data security.
[0208] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system or other device. In addition, the embodiments of the present application are not directed to any particular programming language.
[0209] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. Similarly, in order to simplify the present invention and help understand one or more of the various inventive aspects, in the above description of exemplary embodiments of the present invention, the various features of the embodiments of the present application are sometimes grouped together into a single embodiment, figure, or description thereof. Wherein, the claims that follow the specific embodiment are thus clearly incorporated into the specific embodiment, wherein each claim itself is a separate embodiment of the present invention.
[0210] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and further may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive.
[0211] It should be noted that the above embodiments illustrate the present invention rather than limit it, and that those skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets shall not be construed as a limitation on the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention may be implemented by means of hardware comprising a number of different elements and by means of a suitably programmed computer. In a unit claim enumerating a number of devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.
Claims
1. A data calling method, characterized in that: Applicable to a vehicle riding system, characterized by comprising: When a call request for target data is detected, judging whether it is necessary to call virtual data corresponding to the target data according to the current control mode and the data type of the target data; If necessary, responding to the call request with the virtual data; If not necessary, respond to the call request with the target data.
2. The data calling method according to claim 1, characterized in that: The determining whether it is necessary to call the virtual data corresponding to the target data according to the current control mode and the data type of the target data includes: In the case where the current control mode is the normal control mode, if the target is a real-time data type or a non-real-time data type, it is determined that there is no need to call the virtual data corresponding to the target data; When the current control mode is the privacy mode, if the target data is a real-time data type, it is determined that there is no need to call the virtual data corresponding to the target data; if the target data is a non-real-time data type, it is determined that the virtual data corresponding to the target data needs to be called, or whether the virtual data corresponding to the target data needs to be called is determined according to user-defined instructions.
3. The data calling method according to claim 2, characterized in that: Also includes: Acquire calling data of the target data within a preset time period, and determine a calling mode of the target data according to the calling data; The data type of the target data is determined according to the calling mode.
4. The data calling method according to claim 3, characterized in that: The determining the data type of the target data according to the calling mode comprises: When the calling mode is a high-frequency periodic mode, the target data is a real-time data type; When the calling mode is a single mode, the target data is a non-real-time data type; When the calling mode is one of the low-frequency non-periodic mode, the high-frequency non-periodic mode and the low-frequency periodic mode, a semantic analysis is performed on the calling interface function name of the target data, and the data type of the target data is determined according to the semantic analysis result.
5. The data calling method according to claim 4, characterized in that: The performing semantic analysis on the calling interface function name of the target data and determining the data type of the target data according to the semantic analysis result includes: When the semantic analysis result includes preset keywords, determining that the target data is a real-time data type; When the semantic analysis result does not include the preset keyword, it is determined that the target data is a non-real-time data type.
6. The data calling method according to claim 3, characterized in that: The acquiring of the call data of the target data within a preset time period also includes: The calling data of the target data within a preset time period is obtained through the diary events in the vehicle driving system.
7. The data calling method according to claim 3, characterized in that: The acquiring of the call data of the target data within a preset time period also includes: The calling data of the target data within a preset time period is acquired by monitoring events, wherein the monitoring events are set at the interface points of the target data.
8. The data calling method according to claim 3, characterized in that: The acquiring of the call data of the target data within a preset time period also includes: According to the call record of the target data by the execution unit, the call data of the target data within a preset time period is acquired according to the call record, wherein the execution unit includes at least one of an application program and a system task.
9. The data calling method according to claim 1, characterized in that: Also includes: In response to a virtual data generation instruction input by a user, virtual data corresponding to the target data is generated within a preset range; Or in response to a virtual data configuration instruction input by a user, using pre-configured data as virtual data of the target data.
10. The data calling method according to any one of claims 1 to 9, characterized in that: The virtual data is used for display by the first application that initiates the call request, or is used for the first application to generate and display response display data according to the virtual data.