WO2023179435A1 - Adaptive configuration method for vehicle-mounted application, and vehicle-mounted terminal - Google Patents

Abstract

The present application relates to the technical field of terminals. Provided are an adaptive configuration method for a vehicle-mounted application, and a vehicle-mounted terminal. In the present application, the vehicle-mounted terminal displays a vehicle-mounted application interface according to acquired driving data. Therefore, a display configuration of a displayed vehicle-mounted application adapts to the current driving data, and a vehicle-mounted system adaptively matches, according to the driving data, a vehicle-mounted PWA configuration which is applicable to the current vehicle-mounted scenario, such that the vehicle-mounted PWA configuration can better meet user requirements, thus improving the use experience of a user. The method comprises: a vehicle-mounted terminal acquiring first driving data, and displaying a first interface of which a configuration is a first vehicle-mounted configuration; and the vehicle-mounted terminal acquiring second driving data, and displaying a second interface of which a configuration is a second vehicle-mounted configuration, wherein the first driving data is different from the second driving data, the first interface and the second interface are interfaces of the same vehicle-mounted application, and the first vehicle-mounted configuration is different from the second vehicle-mounted configuration.

Description

Vehicle-mounted application adaptive configuration method and vehicle-mounted terminal

This application claims priority to the Chinese patent application submitted to the State Intellectual Property Office on March 25, 2022, with application number 202210303222.5 and the invention title "Vehicle Application Adaptive Configuration Method and Vehicle-mounted Terminal", the entire content of which is incorporated by reference in in this application.

Technical field

Embodiments of the present application relate to the field of terminal technology, and in particular, to a vehicle application adaptive configuration method and a vehicle terminal.

Background technique

With the development of terminal technology, cars can implement more and more functions. For example, if different third-party applications are installed in the vehicle system, users can use the functions provided by the vehicle system such as music playback, map navigation, and phone calls through third-party applications. However, since each car company uses different in-vehicle systems, developers need to adapt different third-party applications according to different in-vehicle systems, making third-party application development more difficult.

Therefore, progressive web applications (PWA) are proposed that are not limited by the type of vehicle system. With the help of the running environment provided by the browser application, PWA can retain some capabilities of the corresponding third-party native application, provide users with the experience of web browsing applications, and meet user operation needs.

However, PWA cannot provide users with the optimal user experience in complex vehicle scenarios.

Contents of the invention

In order to solve the above technical problems, embodiments of the present application provide a vehicle application adaptive configuration method and a vehicle terminal. In the technical solution provided by the embodiment of this application, the vehicle-mounted terminal displays the vehicle-mounted application interface based on the acquired driving data. The display configuration of the displayed vehicle application interface is adapted to the current driving data to meet user needs and improve user experience.

In order to achieve the above technical objectives, the embodiments of this application provide the following technical solutions:

In the first aspect, an adaptive configuration method for vehicle-mounted applications is provided, which is applied to vehicle-mounted terminals. The method includes: obtaining first driving data. According to the first driving data, the first interface is displayed, and the display configuration of the first interface is the first vehicle configuration. Get the second driving data. According to the second driving data, a second interface is displayed, and the display configuration of the second interface is the second vehicle configuration; wherein the first driving data is different from the second driving data, and the first interface and the second interface are the same vehicle-mounted progressive web application. interface, the first vehicle configuration is different from the second vehicle configuration.

In this way, the vehicle-mounted terminal can adaptively display the vehicle-mounted progressive web application based on driving data. This ensures that the display of in-vehicle progressive web applications meets the needs of current driving scenarios, reduces the driver's driving risks, and improves the user experience.

According to the first aspect, before displaying the first interface according to the first driving data, the method further includes: obtaining vehicle configuration data. Displaying the first interface according to the first driving data includes: matching the first vehicle configuration corresponding to the first driving data according to the vehicle configuration data. According to the first vehicle configuration, a first interface of the vehicle progressive web application is displayed.

According to the first aspect, or any implementation of the above first aspect, the vehicle configuration data includes preset driving data and a preset vehicle configuration corresponding to the preset driving data, and the first driving data corresponding to the first driving data is matched according to the vehicle configuration data. On-board configuration, including: in the preset driving data, match the target preset that is the same as the first driving data. Set driving data. The first vehicle configuration among the preset vehicle configurations corresponding to the target preset driving data is determined.

In some embodiments, the configuration personnel configures the vehicle configuration corresponding to the driving data in different driving scenarios and generates the vehicle configuration data. In this way, after acquiring the driving data, the vehicle-mounted terminal can determine the vehicle-mounted configuration that matches the current driving data based on the vehicle-mounted configuration data. Through this vehicle configuration, the vehicle terminal displays the vehicle progressive web application. This enables the display of the display interface to meet the requirements of current driving data and ensure the driver's driving safety.

In some embodiments, the first driving data or the second driving data include one or more of the following: weather conditions, day and night conditions, road conditions, vehicle speed, call conditions, and light conditions.

For example, when the weather conditions are poor (such as rainy days), the display font of the corresponding vehicle configuration will be larger. In this way, after the vehicle-mounted terminal obtains the driving data on rainy days, it can display an interface with larger fonts based on the matched vehicle configuration, making it easier for the driver to view it. This prevents the driver from distracting more attention from distinguishing the displayed content due to the small display font, which may lead to danger.

According to the first aspect, or any implementation of the above first aspect, obtaining the vehicle configuration data includes: obtaining the vehicle configuration data stored in the storage unit; wherein the storage unit updates the vehicle configuration data from the server according to the first cycle. Or, in response to the operation of launching the in-vehicle progressive web application, requesting the server to obtain the in-vehicle configuration data.

In some embodiments, the vehicle-mounted terminal collects driving data according to the first cycle, stores the collected driving data in the storage unit, and updates historical driving data. Subsequently, after detecting the user's operation of launching the in-vehicle progressive web application, the vehicle-mounted terminal obtains the driving data from the storage unit.

In some other embodiments, after detecting the user's operation of launching the vehicle-mounted progressive web application, the vehicle-mounted terminal requests the server to obtain vehicle-mounted configuration data in real time. As a result, the vehicle configuration determined based on the vehicle configuration data meets the real-time demand for vehicle configuration based on current driving data. This avoids the problem that the display interface does not meet user needs due to the mismatch between the vehicle configuration update and the current driving data.

According to the first aspect, or any implementation of the above first aspect, the first vehicle configuration includes one or more of volume size, font size, and whether to support voice navigation during display of the first interface.

For example, map applications broadcast information such as routes and traffic conditions during navigation. Generally, drivers will turn up the volume of the in-car system in order to hear the broadcast information more clearly. However, since the map application cannot adaptively adjust the volume, during heavy traffic or traffic jams, the louder sound of information playback may affect the driver's attention to the horns and other warnings of surrounding vehicles, affecting driving safety.

For another example, changes in day and night or weather changes will affect the light in the car, but the car application will not adaptively adjust the display. The display fonts are small, making it difficult for users to identify the content in low light conditions. The driver may need to make manual adjustments, which affects driving safety.

For another example, since browser applications generally do not have speech recognition capabilities, map application web pages do not provide speech recognition capabilities. If the driver needs to switch destinations while the vehicle is driving, he cannot perform voice operations and can only input manually, which affects driving safety.

In this way, by configuring the on-board configuration corresponding to different driving data. The vehicle-mounted terminal displays the vehicle-mounted progressive web application interface according to the vehicle configuration, so that the display process meets the requirements of driving data and ensures the driver's driving safety.

According to the first aspect, or any implementation of the above first aspect, obtaining the first driving data includes: detecting an operation of starting a vehicle-mounted progressive web application and obtaining the first driving data. Or, obtain the first driving data according to the second period. Or, when the driving data changes, the first driving data is updated.

In some embodiments, after the vehicle-mounted terminal detects the user's operation of launching the vehicle-mounted progressive web application, it collects the first driving data, or obtains the first driving data in the storage unit.

In other embodiments, the vehicle-mounted terminal collects the first driving data according to the second cycle and stores the driving data in the storage unit. Later, when the operation of starting the in-vehicle progressive web application is detected, the first driving data can be obtained from the storage unit.

In some embodiments, the vehicle-mounted terminal collects driving data, and after determining that the driving data has changed, updates the first driving data stored in the storage unit.

In this way, the vehicle-mounted terminal obtains the first driving data, determines a display configuration that meets the current requirements of the first driving data, and thereby displays the vehicle-mounted progressive web application interface.

According to the first aspect, or any implementation of the above first aspect, before displaying the first interface according to the first driving data, the method further includes: determining that the running scenario of the browser application is a vehicle-mounted terminal scenario, and the smart device has been turned on experience.

For example, the configuration parameters are preset in the browser client in the vehicle-mounted terminal. After the browser client detects the user's operation to launch the in-vehicle progressive web application, it determines whether the browser client's running scenario is an in-vehicle terminal scenario and whether to start an intelligent experience based on the preset configuration parameter values. If both are yes, the browser client can obtain the driving data and adaptively adjust the running environment of the in-vehicle progressive web application based on the driving data.

According to the first aspect, or any implementation of the above first aspect, the first interface and the second interface are the same functional pages of the vehicle-mounted progressive web application.

In some embodiments, different functions in the vehicle-mounted progressive web application are configured with different function pages. For example, a map application has a navigation function page, a location search function page, etc. In the same function page, the vehicle application can also display the corresponding display configuration interface according to changes in driving data. This enables adaptive configuration of the running environment for in-vehicle progressive web applications, and ensures that the configured running environment for in-vehicle progressive web applications meets current driving data requirements, further ensuring driver driving safety.

In a second aspect, a vehicle-mounted terminal is provided. The vehicle-mounted terminal includes: a display screen, a processor and a memory. The display screen and the memory are coupled to the processor. The memory is used to store computer-readable instructions. When the processor reads the computer-readable instructions from the memory, the vehicle-mounted terminal executes: Get First driving data. According to the first driving data, the first interface is displayed, and the display configuration of the first interface is the first vehicle configuration. Get the second driving data. According to the second driving data, a second interface is displayed, and the display configuration of the second interface is the second vehicle configuration; wherein the first driving data is different from the second driving data, and the first interface and the second interface are the same vehicle-mounted progressive web application. interface, the first vehicle configuration is different from the second vehicle configuration.

According to the second aspect, according to the first driving data, when the processor reads the computer-readable instructions from the memory, it also causes the vehicle-mounted terminal to perform the following operations: obtain vehicle-mounted configuration data. Displaying the first interface according to the first driving data includes: matching the first vehicle configuration corresponding to the first driving data according to the vehicle configuration data. According to the first vehicle configuration, a first interface of the vehicle progressive web application is displayed.

According to the second aspect, or any implementation of the above second aspect, obtaining the vehicle configuration data includes: obtaining the vehicle configuration data stored in the storage unit; wherein the storage unit updates the vehicle configuration data from the server according to the first cycle. Or, in response to the operation of launching the in-vehicle progressive web application, requesting the server to obtain the in-vehicle configuration data.

According to the second aspect, or any implementation of the second aspect above, the vehicle configuration data includes preset The preset vehicle configuration corresponding to the driving data and the preset driving data is matched with the first vehicle configuration corresponding to the first driving data according to the vehicle configuration data, including: in the preset driving data, matching the target preset that is the same as the first driving data Driving data. The first vehicle configuration among the preset vehicle configurations corresponding to the target preset driving data is determined.

According to the second aspect, or any implementation of the second aspect above, the first vehicle configuration includes one or more of volume size, font size, and whether to support voice navigation during display of the first interface.

According to the second aspect, or any implementation of the above second aspect, obtaining the first driving data includes: detecting an operation of starting a vehicle-mounted progressive web application and obtaining the first driving data. Or, obtain the first driving data according to the second cycle. Or, when the driving data changes, the first driving data is updated.

According to the second aspect, or any implementation of the second aspect above, when the processor reads the computer-readable instructions from the memory, it also causes the vehicle-mounted terminal to perform the following operations: determine that the running scenario of the browser application is the vehicle-mounted terminal scenario, And the intelligent experience has been turned on.

According to the second aspect, or any implementation of the second aspect above, the first driving data or the second driving data includes one or more of the following: weather conditions, day and night conditions, road conditions, vehicle speed, call conditions, and light conditions. .

According to the second aspect, or any implementation manner of the second aspect above, the first interface and the second interface are the same functional pages of the vehicle-mounted progressive web application.

For the technical effects corresponding to the second aspect and any one of the implementation methods of the second aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, which will not be described again here.

In a third aspect, embodiments of the present application provide a vehicle-mounted terminal that has the function of implementing the vehicle-mounted application adaptive configuration method described in the above-mentioned first aspect and any possible implementation manner. This function can be implemented by hardware, or can be implemented by hardware and corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

For the technical effects corresponding to the third aspect and any one of the implementation methods of the third aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, which will not be described again here.

In a fourth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program (which may also be referred to as instructions or codes). When the computer program is executed by the vehicle-mounted terminal, the vehicle-mounted terminal causes the vehicle-mounted terminal to execute the method of the first aspect or any one of the embodiments of the first aspect.

For the technical effects corresponding to the fourth aspect and any one of the implementation methods of the fourth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, and will not be described again here.

In a fifth aspect, embodiments of the present application provide a computer program product. When the computer program product is run on a vehicle-mounted terminal, the vehicle-mounted terminal causes the vehicle-mounted terminal to execute the method of the first aspect or any one of the embodiments of the first aspect.

For the technical effects corresponding to the fifth aspect and any one of the implementation methods of the fifth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, which will not be described again here.

In a sixth aspect, embodiments of the present application provide a circuit system. The circuit system includes a processing circuit, and the processing circuit is configured to execute the method of the first aspect or any one of the implementation modes of the first aspect.

For the technical effects corresponding to the sixth aspect and any one of the implementation methods of the sixth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, which will not be described again here.

In a seventh aspect, embodiments of the present application provide a chip system, including at least one processor and at least one interface circuit. The at least one interface circuit is used to perform transceiver functions and send instructions to at least one processor. When at least one processor executes the instructions, at least one processor executes the method of the first aspect or any one of the implementation modes of the first aspect.

For the technical effects corresponding to the seventh aspect and any one of the implementation methods of the seventh aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, and will not be described again here.

Description of the drawings

Figure 1A is a schematic diagram 1 of the interface provided by the embodiment of the present application;

Figure 1B is a schematic diagram of the operation process of the vehicle-mounted PWA provided by the embodiment of the present application;

Figure 2 is a schematic diagram of a communication system applied by the vehicle application adaptive configuration method provided by the embodiment of the present application;

Figure 3 is a schematic diagram of the hardware structure of the vehicle-mounted terminal provided by the embodiment of the present application;

Figure 4 is a schematic flow chart of the driving data acquisition method provided by the embodiment of the present application;

Figure 5 is a module schematic diagram of the application of the vehicle application adaptive configuration method provided by the embodiment of the present application;

Figure 6 is a schematic flow chart of the vehicle PWA configuration data acquisition method provided by the embodiment of the present application;

Figure 7 is a schematic flowchart of the vehicle application adaptive configuration method provided by the embodiment of the present application;

Figure 8 is a second schematic diagram of the interface provided by the embodiment of the present application;

Figure 9 is a schematic diagram of a method for determining the running environment after the browser client receives the PWA running request provided by the embodiment of the present application;

Figure 10 is a schematic flowchart of the vehicle application adaptive configuration method provided by the embodiment of the present application;

Figure 11 is a schematic structural diagram of a vehicle-mounted terminal provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the specification and appended claims of this application, the singular expressions "a," "an," "the," "above," "the" and "the" are intended to include For example, the expression "one or more" unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more than two (including two).

Reference in this specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Therefore, the phrases "in one embodiment", "in some embodiments", "in other embodiments", "in other embodiments", etc. appearing in different places in this specification are not necessarily References are made to the same embodiment, but rather to "one or more but not all embodiments" unless specifically stated otherwise. The terms “including,” “includes,” “having,” and variations thereof all mean “including but not limited to,” unless otherwise specifically emphasized. The term "connected" includes both direct and indirect connections unless otherwise stated. “First” and “second” are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features.

In the embodiments of this application, words such as "exemplarily" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "such as" in the embodiments of the present application is not to be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

In some scenarios, with the development of terminal technology, in-vehicle systems (also known as vehicle computers and vehicle central control systems) can support the installation of third-party applications to provide users with a richer functional experience.

For example, in the vehicle system interface 101 shown in (a) of FIG. 1A , one or more third-party applications can be installed in the vehicle system, such as map applications, music applications, weather applications, etc.

However, since various car companies use different in-vehicle systems, developers need to develop third-party applications adapted to different in-vehicle systems. For example, taking map applications as an example, developers need to develop map applications that are adapted to different vehicle systems to meet the needs of users for navigation through the vehicle system while the vehicle is driving. But this also increases the difficulty for developers to develop applications.

From this, Progressive Web Apps (PWA) are proposed. PWA runs with the help of the operating environment provided by the browser application installed in the vehicle system, so it is not limited by the model of the vehicle system. PWA can provide users with some application capabilities while providing users with a World Wide Web (Web) interactive experience. Such as being added to the home screen, running in full screen mode, working offline, sending push notification messages, and being able to obtain the same level of permissions as the application, etc.

For example, as shown in (a) of Figure 1A, map applications, music applications, weather applications, etc. running in the vehicle system can be configured as vehicle PWAs. Figure 1B is a schematic diagram of the operation process of the vehicle-mounted PWA provided by the embodiment of the present application. As shown in step 1 of Figure 1B, the vehicle-mounted PWA detects the user's startup operation, such as detecting the user's click on the map application icon 11 as shown in (a) of Figure 1A. The vehicle-mounted PWA (map application) sends a vehicle-mounted PWA running request to the browser application (i.e. step 2). After receiving the vehicle-mounted PWA running request, the browser application can obtain the corresponding web page data, provide the vehicle-mounted PWA running environment based on the web page data, and render Web page (i.e. step three). Afterwards, the browser application sends the rendered web page data to the on-board PWA (step 4). Correspondingly, after the vehicle-mounted PWA receives the rendered web page data, it can run in the operating environment provided by the browser application based on the rendered web page data (step five). For example, the vehicle-mounted system displays the interface 102 shown in (b) of Figure 1A, and displays a map application Web page on the interface 102. At this time, the map application can receive user operations on the Web page, such as implementing navigation.

In this way, while effectively reducing the difficulty of application development for developers, it also meets the needs of users for using applications. However, since the in-vehicle PWA runs with the help of the operating environment provided by the browser application, the experience of the in-vehicle PWA is the same as that of visiting a web page. Then, it is impossible to achieve adaptive matching of complex vehicle scenarios.

For example, in the scenario shown in Figure 1A, the map application broadcasts information such as routes and traffic conditions during the navigation process. In order to hear the broadcast information more clearly, the average driver will turn up the volume of the vehicle system. However, since the map application cannot adaptively adjust the volume, during heavy traffic or traffic jams, the louder sound of information playback may affect the driver's attention to the horns and other warnings of surrounding vehicles, affecting driving safety.

For another example, changes in day and night or weather changes will affect the light in the car, but the in-car PWA will not adaptively adjust the display. As shown in the interface 102 shown in (b) of Figure 1A, the display font is small, and it is difficult for the user to recognize the content under insufficient light. The driver may need to make manual adjustments, which affects driving safety.

For another example, in the scenario shown in Figure 1A, since browser applications generally do not have voice recognition capabilities, the map application web page does not provide voice recognition capabilities. If the driver needs to switch destinations while the vehicle is driving, he cannot perform voice operations and can only input manually, which affects driving safety.

Based on the above problems, embodiments of the present application provide a vehicle-mounted application adaptive configuration method. The browser application can adaptively match the corresponding vehicle-mounted PWA configuration for the vehicle-mounted application (vehicle PWA) based on the driving data, and based on the matching vehicle-mounted PWA configuration Provides a running environment for in-vehicle applications. This enables vehicle-mounted applications to meet the needs of complex vehicle scenarios, ensuring user experience while reducing driving risks.

FIG. 2 is a schematic diagram of a communication system in which the vehicle application adaptive configuration method provided by the embodiment of the present application is applied. As shown in FIG. 2 , the communication system includes a vehicle-mounted terminal 100 and a server 200 .

Optionally, the vehicle-mounted terminal 100 may be a terminal such as a vehicle or an automobile. The operating systems installed on the vehicle terminal 100 include but are not limited to or other operating systems. The vehicle-mounted terminal 100 does not need to have an operating system installed. This application does not limit the specific type of the vehicle-mounted terminal 100, whether an operating system is installed, or the operating system installed.

Optionally, the server 200 may be a device or network device with computing functions such as a cloud server or a network server. The server 200 may be one server, a server cluster composed of multiple servers, or a cloud computing service center.

In some embodiments, a wireless communication connection is established between the vehicle-mounted terminal 100 and the server 200 . The server 200 sends the vehicle-mounted PWA configuration data to the vehicle-mounted terminal 100 through the wireless communication connection. Correspondingly, the vehicle-mounted terminal 100 receives the vehicle-mounted PWA configuration data sent by the server 200, thereby matching the corresponding vehicle-mounted PWA configuration in the vehicle-mounted PWA configuration data according to the acquired driving data, and configuring the operating environment of the vehicle-mounted PWA.

In some embodiments, the vehicle-mounted terminal 100 is configured with a vehicle-mounted system. As the control center of the vehicle-mounted terminal 100 , the vehicle-mounted system can be used to obtain driving data sent by one or more sensors in the vehicle-mounted terminal, thereby matching the vehicle-mounted PWA according to the driving data. Configuration Data.

For example, FIG. 3 shows a schematic structural diagram of the vehicle-mounted terminal 100.

The vehicle-mounted terminal 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a wireless communication module 160, an audio module 170, a sensor module 180, a button 190, and a motor 191 , indicator 192, camera 193, and display screen 194, etc.

It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the vehicle-mounted terminal 100 . In other embodiments of the present application, the vehicle-mounted terminal 100 may include more or fewer components than shown in the figures, or some components may be combined, or some components may be separated, or may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors.

The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. Interfaces may include integrated circuit (inter-integrated circuit, I2C) interface, integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, pulse code modulation (pulse code modulation, PCM) interface, universal asynchronous receiver and transmitter (universal) asynchronous receiver/transmitter (UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and/or universal serial bus (USB) interface, etc.

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 . MIPI interfaces include camera serial interface (CSI), display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate through the CSI interface to implement the shooting function of the vehicle-mounted terminal 100. The processor 110 and the display screen 194 communicate through the DSI interface to realize the display function of the vehicle-mounted terminal 100 .

The USB interface 130 is an interface that complies with the USB standard specification, and may be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the vehicle-mounted terminal 100, and can also be used to transmit data between the vehicle-mounted terminal 100 and peripheral devices. It can also be used to connect headphones to play audio through them. This interface can also be used to connect other terminal devices, such as AR devices.

It can be understood that the interface connection relationships between the modules illustrated in the embodiments of the present application are only schematic illustrations and do not constitute a structural limitation on the vehicle-mounted terminal 100 . In other embodiments of the present application, the vehicle-mounted terminal 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The wireless communication function of the vehicle-mounted terminal 100 can be implemented through the antenna, the wireless communication module 160, the modem processor and the baseband processor.

Antennas are used to transmit and receive electromagnetic wave signals. Each antenna in the vehicle-mounted terminal 100 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: the antenna can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.

The wireless communication module 160 can provide wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (BT), and global navigation satellites that are used on the vehicle-mounted terminal 100. System (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves through the antenna, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna for radiation.

In some embodiments, the vehicle-mounted terminal 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC , FM, and/or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (quasi -zenith satellite system (QZSS) and/or satellite based augmentation systems (SBAS).

The vehicle-mounted terminal 100 implements the display function through the GPU, the display screen 194, and the application processor. The GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, videos, etc. Display 194 includes a display panel. The display panel can use a liquid crystal display (LCD), such as an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix). Production and manufacturing of organic light emitting diodes (AMOLED), flexible light-emitting diodes (FLED), Mini-led, Micro-led, Micro-oled, quantum dot light emitting diodes (QLED), etc. . In some embodiments, the vehicle-mounted terminal 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

In some embodiments, the vehicle-mounted terminal 100 displays the vehicle-mounted PWA icon on the display screen 194, and the user can operate the corresponding vehicle-mounted PWA icon to start the vehicle-mounted PWA according to the needs. After detecting the user's operation to activate the vehicle-mounted PWA, the vehicle-mounted terminal 100 obtains the current driving data to match the corresponding vehicle-mounted PWA configuration. After that, complete the configuration of the vehicle PWA operating environment according to the vehicle PWA configuration. The rendered web page is displayed on the display screen 194 so that the display process is adapted to the current vehicle scene. If the light is dark, you can enlarge the display fonts, etc.

Camera 193 is used to capture still images or video. The object passes through the lens to produce an optical image that is projected onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to convert it into a digital image signal. ISP outputs digital image signals to DSP for processing. DSP converts digital image signals into standard RGB, YUV and other format image signals. In some embodiments, the vehicle-mounted terminal 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the vehicle-mounted terminal 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.). The storage data area may store data created during use of the vehicle-mounted terminal 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the vehicle-mounted terminal 100 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

In some embodiments, after acquiring the driving data and the vehicle-mounted PWA configuration data, the vehicle-mounted terminal 100 may store the driving data and the vehicle-mounted PWA configuration data in the internal memory 121 . In this way, when an application is needed, the corresponding data can be obtained from the internal memory 121 .

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. Audio module 170 may also be used to encode and decode audio signals. in some In embodiments, the audio module 170 may be disposed in the processor 110 , or some functional modules of the audio module 170 may be disposed in the processor 110 . The vehicle-mounted terminal 100 can perform, for example, music playback, recording, etc. through the audio module 170 . The audio module 170 may include a speaker, a receiver, a microphone, a headphone interface, and an application processor to implement audio functions.

The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

Touch sensor, also known as "touch device". The touch sensor can be disposed on the display screen 194, and the touch sensor and the display screen 194 form a touch screen, which is also called a "touch screen". Touch sensors are used to detect touches on or near them. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation may be provided through display screen 194 . In other embodiments, the touch sensor may also be disposed on the surface of the vehicle-mounted terminal 100 in a position different from that of the display screen 194 .

The buttons 190 include square control buttons, power buttons, volume buttons, etc. Key 190 may be a mechanical key. It can also be a touch button. The vehicle-mounted terminal 100 may receive key input and generate key signal input related to user settings and function control of the vehicle-mounted terminal 100 .

The vehicle-mounted terminal 100 includes a vehicle-mounted system and a browser client, the server 200 is a browser cloud, and the vehicle-mounted PWA is a map application. The vehicle-mounted application adaptive configuration method provided by the embodiment of the present application is described below.

It should be noted that the browser client is installed in the vehicle-mounted terminal 100 and is a browser application. In the embodiment of this application, for convenience of explanation, the vehicle system and the browser client are divided into two virtual modules. In some embodiments, the vehicle system and the browser client can be one virtual module. For example, the vehicle-mounted system serves as the central control system of the vehicle-mounted terminal 100, and the browser client is installed in the vehicle-mounted system, that is, the vehicle-mounted system includes the browser client, which will not be described below.

In some embodiments, different vehicle scenarios will generate different driving data, and different vehicle PWA configurations can provide users with a better experience in different vehicle scenarios. Therefore, when the browser client determines that the vehicle system needs to launch the vehicle PWA, it can configure the vehicle PWA based on the acquired driving data.

The following describes the process of the browser client obtaining driving data and vehicle PWA configuration data respectively.

Optionally, FIG. 4 is a schematic flowchart of a driving data acquisition method provided by an embodiment of the present application. As shown in Figure 4, the method includes the following steps.

S401. The vehicle-mounted PWA management unit obtains driving data.

In some embodiments, the driving data includes one or more of weather conditions, day and night conditions, road conditions, vehicle speed, light conditions, etc. As shown in Figure 3, the vehicle terminal 100 is equipped with a sensor module 180. The sensor module 180 can be used to detect driving data during the driving of the vehicle. Alternatively, the vehicle-mounted system can obtain driving data sent by other electronic devices (such as mobile phones) connected to it.

For example, as shown in Figure 5, the vehicle-mounted system includes a driving data collection unit 501, which is used to collect driving data detected during the driving of the vehicle. For example, the vehicle can be equipped with an acceleration sensor, which can be used to determine whether the vehicle is driving and measure the vehicle speed. Furthermore, it can also determine the road conditions based on the vehicle speed (for example, poor road conditions will cause the vehicle speed to decrease, etc.) or synchronize the road conditions with the map APP; the vehicle can also It can be equipped with a rain sensor or weather application, or other APP, which can be used to determine weather conditions; the vehicle can also be equipped with an ambient light sensor, which can be used for measurement Ambient light can also determine day and night conditions based on ambient light; the vehicle can also be configured with a clock application or the time of the terminal to determine time information, and then determine day and night conditions; the vehicle can also be configured with a map application, which can be used to determine road conditions.

The driving data acquisition unit 501 can obtain detection signals sent by various sensors in the vehicle, and determine the driving data of the vehicle based on the monitoring signals. For example, the driving data collection unit 501 determines that the current weather condition is a rainy day based on the detection signal sent by the rain sensor. For another example, the driving data collection unit 501 determines that it is currently daytime based on the information sent by the clock application or the detection signal sent by the ambient light sensor. For another example, the driving data collection unit 501 determines that the current road conditions are clear and the vehicle speed is (90-12) kilometers per hour (km/h) based on the detection signal sent by the acceleration sensor.

On the other hand, the driving data collection unit 501 obtains data through relevant APPs or related collection modules in the terminal device or vehicle-mounted system. For example, one or more of the above-mentioned weather conditions, day and night conditions, road conditions, vehicle speed, light conditions, etc. can be obtained through data collected by electronic devices or related APPs in the vehicle system. Among them, the electronic device is a device that establishes a communication connection with the vehicle-mounted terminal.

In some embodiments, the vehicle-mounted system includes a vehicle-mounted PWA management unit for managing the vehicle-mounted PWA. Determination of the vehicle-mounted PWA operating environment requires driving data, so the vehicle-mounted PWA application management unit requests the driving data collection unit to obtain driving data.

For example, as shown in FIG. 5 , the vehicle-mounted system includes a vehicle-mounted PWA management unit 502 , and the vehicle-mounted PWA application management unit 502 requests the driving data collection unit 501 to acquire driving data.

S402. The vehicle-mounted PWA management unit sends driving data to the browser client.

In some embodiments, after acquiring the driving data, the vehicle-mounted PWA management unit may send the driving data to the browser client. Correspondingly, the browser client receives the driving data sent by the vehicle-mounted PWA management unit.

For example, as shown in Figure 5, after acquiring the driving data, the vehicle-mounted PWA application management unit 502 sends the driving data to the browser client. As shown in Figure 5, the browser client may include a vehicle-mounted PWA intelligent control unit 504 for determining the operating environment of the vehicle-mounted PWA. To determine whether to enable the intelligent in-vehicle PWA experience, match the corresponding in-vehicle PWA configuration.

Optionally, the vehicle-mounted PWA management unit 502 sends driving data to the vehicle-mounted PWA intelligent control unit 504 through the JS interface according to a preset period or changes in driving data. Correspondingly, the intelligent control unit 504 receives the driving data through the JS interface.

For example, the vehicle PWA management unit 502 sends a vehicle data setting command (setVehiclesInfo) to the vehicle PWA intelligent control unit 504 through the VehiclesJsInterface interface, and the vehicle data setting command carries the vehicle system name (vehicleSystemName) and vehicle data (vehiclesInfo). Among them, the driving data can include weather conditions (String weather), such as sunny days, rainy days, etc.; vehicle speed (String speed), the unit is km/h; day and night conditions (String dayOrNight). Such as day and night; road conditions (String roadConditions), such as good, congested, etc.

S403. The browser client saves the driving data.

In some embodiments, after receiving the driving data, the browser client saves the driving data to facilitate the subsequent calling of the driving data in the process of matching the vehicle PWA configuration.

For example, as shown in Figure 5, after the vehicle-mounted PWA intelligent control unit 504 in the browser client receives the driving data (vehiclesInfo) sent by the vehicle-mounted PWA management unit through the JS interface, it will It is converted into a local vehicle data (VehicleDataLocal) object and sent to the storage unit 505. Correspondingly, after receiving the VehicleDataLocal object, the storage unit 505 saves the VehicleDataLocal object into the VehiclesPwaConfig.xml file.

Optionally, before the storage unit 505 receives the VehicleDataLocal object for the first time, the VehiclesPwaConfig.xml file is empty. Subsequently, each time a VehicleDataLocal object is received, the historical data will be overwritten, that is, only the latest local driving data will be stored in the storage unit 505.

Illustratively, the following shows an example of driving data sent by a vehicle-mounted PWA management unit obtained and saved by a browser client. Among them, the vehicle-mounted system is, for example, "Xiaoqi", and the driving data includes: sunny day, vehicle speed 100km/h, daytime, and smooth road conditions.

In some embodiments, the above driving data content is only an exemplary description, and the driving data may also include other data. For example, vehicle-mounted systems are generally equipped with a call function, and users can make calls through the vehicle-mounted system. Then, the driving data can also include call status, which is used to indicate whether the user is talking through the in-vehicle system. For example, during the user's call, the vehicle system does not provide voice services, and the vehicle PWA cannot support voice control.

For example, users generally use the call function of the car system through a Bluetooth headset, or use the call application in the car system to make calls. Then the vehicle system can determine whether the user is talking based on whether the Bluetooth function is being used or whether the calling application is being used, and then set the corresponding driving data.

Furthermore, the vehicle-mounted PWA management unit in the vehicle-mounted system does not need to send the driving data of such sudden scenes to the browser client periodically, but sends it to the browser client at the start and end times of the sudden scene. Corresponding driving data.

For example, at the start of a call, the vehicle-mounted PWA management unit sends the driving data of the following example to the browser client. The browser client can determine based on the driving data that the user is on a call (corresponding to the field "on the telephone: Yes"). Optionally, the driving data may include the above-mentioned driving data such as weather, or may not include the above-mentioned driving data such as weather.

Later, after the call ends, the vehicle-mounted PWA management unit can send driving data including the call situation to the browser client again. The driving data is as follows. The browser client can overwrite the driving data with the above driving data. The corresponding content in the data is to update the call status.

In this way, it can be avoided that due to delayed transmission of driving data, subsequent abnormalities in the browser client's configuration of the vehicle-mounted PWA will be avoided, affecting user use.

It should be noted that the browser client can update the corresponding content in the old driving data stored in the storage unit according to the content in the new driving data obtained. Take the above example of driving data corresponding to the call situation. For example, the driving data sent by the in-vehicle system to the browser client after the call ends only includes the call situation. Then, the browser client can overwrite the original call situation based on the updated call situation without updating other driving data.

Optionally, the driving data sent each time by the vehicle-mounted PWA management unit in the vehicle-mounted system can include all options (such as weather conditions, day and night conditions, road conditions, vehicle speed, and call conditions in the above examples), thereby preventing the browser client from further Confirm the updated content of old driving data to reduce power consumption.

Therefore, the browser client obtains the driving data through the above method. The method of obtaining the vehicle PWA configuration is introduced below.

Optionally, FIG. 6 is a schematic flowchart of a method for obtaining vehicle PWA configuration data provided by an embodiment of the present application. As shown in Figure 6, the method includes the following steps.

S601. The browser cloud obtains the vehicle PWA configuration data.

In some embodiments, the vehicle-mounted PWA configuration data includes driving data and vehicle-mounted PWA configurations corresponding to different driving data. Configuration personnel of different car companies can determine the in-vehicle PWA configuration data of different in-vehicle systems based on needs. For example, different in-vehicle systems have different positioning and provide different user experiences (such as safety, speed, suitability for elderly driving, etc.). Configurators can customize the in-vehicle PWA configuration corresponding to different driving data to complete the in-vehicle Configuration of PWA configuration data.

For example, the vehicle-mounted PWA configuration data is shown in Table 1 below. The configurer configures the vehicle-mounted system 1 on a sunny day, daytime, smooth road conditions, and the vehicle speed is (90-120) km/h. The vehicle-mounted PWA is configured with a volume of 50 Decibel, font size is 12pt, and voice navigation is not supported.

Table 1

It should be noted that the voice navigation in the vehicle PWA configuration data in Table 1 above is optional, and the configurer does not need to configure this content. In addition, the embodiment of the present application takes the vehicle-mounted PWA as a map application as an example. Therefore, the vehicle-mounted PWA configuration includes a voice navigation option, and this option can also be set to voice capabilities. This embodiment of the application does not specifically limit this.

Optionally, as shown in Table 2 below, if the driving data included in the vehicle PWA configuration data includes call status, the corresponding vehicle PWA configuration may include voice navigation options. If the configured call status is Yes, the corresponding car PWA does not support voice navigation; if the call status is No, the corresponding car PWA supports voice navigation. This avoids the problem of voice navigation failure due to the audio channel being occupied by calls.

Table 2

For example, the configurer logs in to the configuration interface and uploads or modifies the vehicle PWA configuration data (as shown in Table 1 or Table 2 above) on the configuration interface. As shown in Figure 5, the browser cloud includes a vehicle-mounted PWA configuration management unit 506, which is used to manage the vehicle-mounted PWA configuration data received by the browser cloud through the configuration interface.

S602. The browser client sends a vehicle PWA configuration data download request to the browser cloud.

S603. The browser cloud sends the vehicle PWA configuration data to the browser client according to the vehicle PWA configuration data download request.

In some embodiments, in steps S602 and S603, the browser client sends a vehicle-mounted PWA configuration data download request to the browser cloud according to a preset period (such as one hour) for requesting to download the vehicle-mounted PWA configuration. Setup data. Correspondingly, the browser cloud sends the vehicle PWA configuration data to the browser client according to the vehicle PWA configuration data download request.

Optionally, the vehicle PWA configuration data download request carries the identification of the vehicle terminal, or the device identification of the vehicle, or other identification used to distinguish different vehicle terminals. The browser cloud sends the vehicle-mounted PWA configuration data corresponding to the identifier to the browser client based on the identifier carried in the vehicle-mounted PWA configuration data download request. Thereby meeting the positioning needs of different vehicle-mounted terminals.

It should be noted that the browser cloud can also actively send the vehicle PWA configuration data to the browser client according to a preset cycle or after determining that the vehicle PWA configuration data has been updated.

Optionally, the browser cloud encapsulates the vehicle PWA configuration data in the cloud vehicle PWA configuration (VehiclesPwaConfigCloud) object and sends it to the browser client.

For example, as shown in Figure 5, the vehicle-mounted PWA intelligent control unit 504 in the browser client obtains the vehicle-mounted PWA configuration data sent by the vehicle-mounted PWA configuration management unit 506. Table 3 below exemplarily shows the vehicle-mounted PWA configuration data of a vehicle-mounted system (such as "Xiaoqi") obtained by a browser client.

table 3

S604. The browser client saves the vehicle PWA configuration data.

In some embodiments, after receiving the vehicle-mounted PWA configuration data, the browser client saves the vehicle-mounted PWA configuration data to facilitate calling the vehicle-mounted PWA configuration data in the subsequent process of matching the vehicle-mounted PWA configuration.

For example, as shown in Figure 5, after receiving the VehiclesPwaConfigCloud object sent by the browser cloud vehicle PWA configuration management unit 506, the vehicle PWA intelligent control unit 504 in the browser client sends the VehiclesPwaConfigCloud object to the storage unit 505. Correspondingly, after receiving the VehiclesPwaConfigCloud object, the storage unit 505 saves it in a default share (sharePreferences) file, and the file name is VehiclesPwaConfig.xml.

Optionally, before the storage unit 505 receives the VehiclesPwaConfigCloud object for the first time, the VehiclesPwaConfig.xml file is empty. Subsequently, each time the VehiclesPwaConfigCloud object is received, the historical data will be overwritten, that is, only the latest vehicle PWA configuration data will be stored in the storage unit 505.

Illustratively, an example of in-vehicle PWA data obtained and saved by a browser client is shown below.

Therefore, the browser client can obtain the driving data and vehicle PWA configuration data through the above method. The following describes the adaptive configuration method of on-board PWA during vehicle driving.

Exemplarily, FIG. 7 is a schematic flowchart of a vehicle application adaptive configuration method provided by an embodiment of the present application. As shown in Figure 7, the method includes the following steps.

S701. The vehicle-mounted PWA management unit detects the user's instruction to start the vehicle-mounted PWA operation.

In some embodiments, as shown in Figure 5, in response to the user's operation of clicking on the vehicle-mounted PWA icon, the vehicle-mounted PWA management unit in the vehicle-mounted system may obtain the click operation and determine that the user instructs to start the vehicle-mounted PWA.

For example, in the interface 801 shown in (a) of Figure 8, after detecting the user's click on the map application icon 81, the vehicle-mounted PWA management unit determines to start the map application corresponding to the map application icon 81.

S702. The vehicle-mounted PWA management unit sends a running request to the browser client.

In some embodiments, after determining that the user has instructed to start the vehicle-mounted PWA application, the vehicle-mounted PWA management unit sends a running request to the browser client to request the running environment, such as web page data.

Exemplarily, based on the scenario shown in (a) of Figure 8 described in step S701, as shown in Figure 5, the vehicle-mounted PWA management unit 502 determines that the map application is a vehicle-mounted PWA, and intelligentizes the map application to the vehicle-mounted PWA in the browser client. The control unit 504 sends a run request.

S703. The browser client determines the running environment of the vehicle-mounted PWA based on the driving data and the vehicle-mounted PWA configuration data.

In some embodiments, the browser client can obtain driving data and vehicle-mounted PWA configuration data, adaptively determine the vehicle-mounted PWA configuration that matches the driving data, and then determine the vehicle-mounted PWA operating environment. Optionally, the browser client can obtain the driving data and vehicle-mounted PWA configuration data stored in the storage unit; or, the browser client can trigger the active acquisition of driving data and/or vehicle-mounted PWA configuration data based on the running request. For example, the browser client requests driving data from the vehicle system, and requests the vehicle PWA configuration data from the browser cloud. For another example, the browser client requests driving data from the vehicle system and obtains the stored vehicle PWA configuration data from the storage unit. For another example, the browser client obtains the stored driving data from the storage unit and requests the browser cloud to obtain the vehicle PWA configuration data.

For example, as shown in Figure 5, the vehicle-mounted PWA intelligent control unit 504 in the browser client can obtain the vehicle-mounted PWA from the storage unit 505 after receiving the vehicle-mounted PWA running request sent by the vehicle-mounted PWA management unit 502 in the vehicle system. to the stored driving data and vehicle-mounted PWA configuration data, and then match the corresponding vehicle-mounted PWA configuration according to the driving data.

For example, the storage unit 505 stores the vehicle-mounted PWA configuration data as described in step S604 shown in FIG. 6 above. And corresponding to step S403 shown in the above-mentioned FIG. 4 , the storage unit 505 also stores the following driving data example 1 (such as the driving data saved through the step S403 shown in the above-mentioned FIG. 4 ). Then, the browser client matches the corresponding vehicle-mounted PWA configuration in the vehicle-mounted PWA configuration data described in step S604 according to the following driving data example 1 (such as determining that the driving data field in the vehicle-mounted PWA configuration data is the same as the stored driving data Corresponding function command field content). For example, it is determined that the corresponding car PWA is configured with a volume size of 50 decibels, a font size of 12pt, and does not support voice navigation. For example, the display interface corresponding to the vehicle PWA configuration is interface 802 as shown in (b) of Figure 8 .

Driving data example one:

For another example, take the following driving data example 2 (such as the driving data saved through step S403 described in FIG. 4), the vehicle-mounted PWA intelligent control unit 504 matches the vehicle-mounted PWA configuration data described in step S604. The corresponding car PWA configuration, if matched to the corresponding car PWA configuration, the volume size is 30 decibels, the font size is 15pt, and voice navigation is supported. For example, the display interface corresponding to the vehicle PWA configuration is interface 803 as shown in (c) of Figure 8 .

Driving data example two:

It should be noted that the browser client will only save one piece of the driving data in the above driving data example one and driving data example two, that is, the newly acquired driving data will overwrite the historical data. The above driving data example one and driving data example two are only used to illustrate the matching process of vehicle PWA configuration.

S704. The browser client provides a running environment and renders the web page.

In some embodiments, after the browser client matches the vehicle-mounted PWA configuration, it can set the corresponding running environment and render the web page according to the vehicle-mounted PWA configuration content.

For example, as shown in Figure 5, after determining the configuration of the vehicle PWA, the vehicle-mounted PWA intelligent control unit 504 in the browser client determines whether the current operating environment needs to be adjusted, such as the volume size, font size, and whether it supports voice navigation. Needs adjustment. If adjustment is needed, adjust the corresponding operating environment through the on-board PWA operating unit 503.

S705. The browser client sends a vehicle-mounted PWA running response to the vehicle-mounted PWA management unit.

In some embodiments, after the browser client completes rendering of the web page, it sends a vehicle-mounted PWA running response to the vehicle-mounted PWA management unit in the vehicle-mounted system, and the vehicle-mounted PWA running response carries the rendered web page.

For example, as shown in Figure 5, the vehicle-mounted PWA running unit 503 in the browser client is used to provide a running environment to the vehicle-mounted PWA management unit 502 in the vehicle system.

S706. The vehicle-mounted PWA management unit runs the vehicle-mounted PWA.

In some embodiments, after receiving the vehicle-mounted PWA running response, the vehicle-mounted PWA management unit in the vehicle-mounted system can run in the obtained running environment according to the content carried in the vehicle-mounted PWA running response, and display the rendered web page.

Illustratively, the browser client first obtains the driving data example 1 shown in step S703 above. Taking the scenario shown in (a) in Figure 8 as an example, after the browser client determines the corresponding vehicle PWA configuration (for example, the volume is 50 decibels, the font size is 12pt, and voice navigation is not supported), it provides an operating environment for the vehicle system. . Correspondingly, the vehicle-mounted system may display interface 802 as shown in (b) of Figure 8 .

Afterwards, the browser client obtains the driving data example 2 shown in the above step S703, which can overwrite the driving data example 1. Then, still taking the scenario shown in (a) in Figure 8 as an example, after the browser client determines the corresponding vehicle PWA configuration (such as the volume size is 30 decibels, the font size is 15pt, supports voice navigation), it provides the vehicle system with operating environment. Correspondingly, the vehicle-mounted system may display interface 803 as shown in (c) of Figure 8 .

In this way, in rainy days, vehicle congestion, etc., after the browser client obtains the driving data (such as driving data example 2), if it detects the user's instruction to start the vehicle PWA application, it can automatically adjust the volume of the vehicle PWA application. Low to avoid distracting users from the sound of horns from surrounding vehicles. Increase the font size displayed on the web page (such as The display font of interface 803 is larger than the display font of interface 802), making it easier for users to view the displayed content. Moreover, as shown in the interface 803 with the microphone mark 82, the vehicle-mounted PWA supports voice navigation to avoid driving risks caused by users manually inputting content.

In this way, the browser client can adaptively complete the vehicle PWA configuration based on driving data. This ensures that the in-vehicle PWA configuration meets the needs of the current scene, reduces the driver's driving risk, and improves the user experience.

In some scenarios, before step S703 shown in Figure 7, the browser client can also determine whether the current scene is a vehicle terminal scene, and determine whether the PWA enables an intelligent running experience. After it is determined that the scene is a vehicle-mounted terminal and the intelligent running experience has been enabled, step S703 can be performed.

In some embodiments, configuration parameters or values of configuration parameters in different versions of browser applications are different, and developers can define different browser client versions through configuration parameters. For example, configure the running scene (RunningScene) parameters and intelligent experience (IntelligentExperience) parameters as shown in Table 4 below in the browser client.

Table 4

Optionally, PWA can run in a variety of terminals, such as vehicle-mounted terminals, mobile phone terminals, PAD terminals, etc. Therefore, after receiving the running request (such as step S702 above), the browser client can first determine whether the current PWA running scene is a vehicle-mounted terminal scene based on the value of the RunningScene parameter. For example, after the browser client determines that it is a vehicle-mounted terminal scenario, it then determines whether the vehicle-mounted PWA enables an intelligent operating experience to provide a corresponding operating environment for the PWA.

Exemplarily, FIG. 9 is a flowchart of a method for determining the running environment after the browser client receives a PWA running request provided by an embodiment of the present application. As shown in Figure 9, the method includes the following steps.

S901. The browser client receives the PWA execution request.

Optionally, the content of step S901 may refer to the relevant content of step S702 above.

S902. The browser client determines the value of the running scene (RunningScene) parameter. If the value is 1, execute step S903; if the value is not 1, execute step S904.

S903. The browser client determines that the PWA running scenario is the vehicle terminal scenario.

S904. The browser client determines that the PWA running scenario is not the vehicle terminal scenario, and provides other PWA running environments.

In some embodiments, in steps S902 to S904, after the terminal downloads the browser client, the preconfigured RunningScene parameter in the browser client will determine the value corresponding to the current terminal. As shown in Table 4 above, different values have different meanings. After receiving the PWA running request, the browser client can Get the value to determine the current running scenario. For example, a value of 1 is used to indicate that the running scenario of the current PWA (the running scenario of PWA and browser client is the same) is the vehicle terminal scenario, and a value of 2 is used to indicate that the running scenario of the current PWA is the mobile phone terminal scenario. If it is determined that the value is not 1, it can be determined that the PWA running scenario is not the vehicle terminal running scenario, and the corresponding PWA intelligent running experience needs to be provided. If the value is 2, it can be determined that the running environment of the mobile phone terminal is provided.

S905. The browser client determines the value of the Intelligent Experience (IntelligentExperience) parameter. If the value is 1, step S906 is executed; if the value is 0, step S904 is executed.

S906 and browser client provide intelligent running experience of in-vehicle PWA.

In some embodiments, in steps S905 and S906, after determining that the PWA running scene is a vehicle-mounted terminal scene, the browser client can then determine whether the PWA enables an intelligent experience (that is, whether the PWA configuration can be adaptively completed). For example, as shown in Table 4 above, if the value of IntelligentExperience is 1, it can be determined that the intelligent experience is on; if the value of IntelligentExperience is 0, it can be determined that the intelligent experience is off. If it is determined that the intelligent experience is turned on, the vehicle PWA configuration can be adaptively matched through the method shown in the above step S703; if it is determined that the intelligent experience is turned off, the above step S904 can be executed to provide other PWA operating environments.

Optionally, the IntelligentExperience value can be pre-configured in the browser client, that is, whether the browser application supports PWA intelligent operation is pre-configured. Alternatively, the browser client can determine whether to support PWA intelligent experience based on user settings, and set the corresponding IntelligentExperience value.

For example, the user can set whether the browser client supports PWA intelligent experience through the system setting interface or the setting interface in the browser client, so as to meet the user's personalized needs.

In some embodiments, after receiving the vehicle-mounted PWA running request sent by the vehicle-mounted system, the browser client can request driving data from the vehicle-mounted system, or the vehicle-mounted system carries the driving data in the vehicle-mounted PWA running request. Moreover, after receiving the vehicle-mounted PWA running request sent by the vehicle-mounted system, the browser client requests the browser cloud to download the vehicle-mounted PWA configuration data.

In this way, the browser client can configure the operating environment for the in-vehicle PWA based on the latest acquired driving data and in-vehicle PWA configuration data, which can further ensure that the configured in-vehicle PWA operating environment meets the current driving data requirements, further ensuring driver driving safety.

As described above, the corresponding vehicle PWA configuration is matched during the startup process of the vehicle PWA. During the operation of the vehicle PWA, the browser client can also adjust the operating environment of the vehicle PWA based on the driving data and/or the vehicle PWA configuration data.

In some embodiments, the browser client receives driving data and/or vehicle PWA configuration data in the process of providing a running environment for the vehicle PWA (for example, the vehicle system is displaying the vehicle PWA page). The browser client can adjust the operating environment of the currently running vehicle-mounted PWA based on the latest received driving data and/or vehicle-mounted PWA configuration data to ensure that the vehicle-mounted PWA operating environment meets the current driving data requirements.

For example, the vehicle-mounted system sends driving data to the browser client according to a preset cycle. After receiving the driving data, the browser client determines that the driving data is different from the driving data obtained in the previous cycle. The browser client can then determine whether the in-car PWA is currently being displayed. If the browser client is displaying the vehicle PWA, it can obtain the vehicle PWA configuration data stored in the storage unit or actively request the browser cloud to download the vehicle PWA configuration data, and then add the vehicle PWA configuration data to the obtained vehicle PWA configuration data based on the latest driving data. Match the vehicle PWA configuration and determine whether the running environment of the currently running PWA application needs to be adjusted.

For another example, after determining that the driving data has changed, the vehicle-mounted system sends the driving data to the browser client. Then, after obtaining the driving data, the browser client directly determines whether the in-vehicle PWA is currently being displayed. If the browser client is displaying the vehicle PWA, it can obtain the vehicle PWA configuration data stored in the storage unit or actively request the browser cloud to download the vehicle PWA configuration data, and then add the vehicle PWA configuration data to the obtained vehicle PWA configuration data based on the latest driving data. Match the vehicle PWA configuration and determine whether the running environment of the currently running PWA application needs to be adjusted.

For another example, the browser client requests the browser cloud to download the vehicle-mounted PWA configuration data according to a preset cycle. After receiving the vehicle-mounted PWA configuration data, the browser client determines that the vehicle-mounted PWA configuration data is consistent with the vehicle-mounted PWA obtained in the previous cycle. The configuration data is different. The browser client can then determine whether the in-car PWA is currently being displayed. If the browser client is displaying the vehicle-mounted PWA, the browser client can obtain the driving data from the storage unit or request the vehicle-mounted system to obtain the driving data, and determine whether it is needed based on the obtained driving data and the latest obtained vehicle-mounted PWA configuration data. Adjust the running environment of the currently running PWA application.

For another example, after the browser cloud determines that the vehicle PWA configuration data has been updated, it actively sends the vehicle PWA configuration data to the browser client. Then, after obtaining the vehicle PWA configuration data, the browser client directly determines whether the vehicle PWA is currently being displayed. If the browser client is displaying the vehicle-mounted PWA, it can obtain the driving data from the storage unit or request the vehicle-mounted system to obtain the driving data. Based on the obtained driving data and the latest obtained vehicle-mounted PWA configuration data, determine whether the currently running PWA needs to be adjusted. The running environment of PWA applications.

For example, when the browser client displays the map application interface 802 as shown in (b) of Figure 8, it receives the driving data and determines that the driving data is different from the driving data obtained last time. Then, the browser client can match the vehicle PWA configuration in the vehicle PWA data based on the latest received driving data. According to the vehicle PWA configuration determined this time, the browser client displays the map application interface 803 as shown in (c) of Figure 8 . The display font of interface 803 is larger than that of interface 802, and supports voice navigation, enabling the browser client to adaptively adjust the running environment of the map application based on driving data.

In this way, the browser client can adaptively configure the operating environment for the vehicle-mounted PWA based on the latest acquired driving data and vehicle-mounted PWA configuration data, which can further ensure that the configured vehicle-mounted PWA operating environment meets the current driving data requirements, further ensuring that the driver's driving Safety.

Optionally, in the above scenario, the browser client may not change the operating environment of the currently running vehicle PWA, but adaptively adjust the operating environment of the vehicle PWA after the user instructs to start a new vehicle PWA. This prevents sudden changes in the operating environment from affecting user operations and causing driving hazards.

In some embodiments, the vehicle PWA configuration data includes one or more of volume size, font size, and voice navigation. In addition, the vehicle PWA cooperation data can also include display interface scale information.

For example, if the vehicle PWA is a map application, the configurer can configure different display interface scale information corresponding to different driving data. If you set the driving data under poor driving conditions, the corresponding display scale will be larger. This allows the vehicle-mounted system to display more detailed road condition information, helping the driver to more clearly determine the current road conditions, thereby ensuring driving safety.

It should be noted that each of the above embodiments takes a vehicle-mounted PWA as a map application as an example to describe the adaptive configuration method for vehicle-mounted applications provided by the embodiments of the present application. For configuration methods of other vehicle-mounted applications, please refer to the relevant content of each of the above embodiments. This application does not limit the type of vehicle-mounted PWA.

Optionally, the vehicle PWA configuration data of different vehicle PWAs may be the same or different. If the vehicle PWA configuration data of different vehicle PWAs are the same, the browser client responds to the user's operation of starting the vehicle PWA, Obtain the vehicle PWA configuration data and driving data, and display the vehicle PWA interface. Or, the vehicle PWA configuration data of different vehicle PWAs are different. The configurer can configure different vehicle PWA configuration data according to the functions of the vehicle PWA and other information. For example, if the music application does not support the voice navigation function, the vehicle PWA configuration data of the music application does not need to be included in the vehicle PWA configuration data. Configure whether to support voice navigation data. In response to the user's operation of starting the vehicle-mounted PWA, the browser client determines to obtain the driving data and the vehicle-mounted PWA configuration data corresponding to the current vehicle-mounted PWA, and displays the vehicle-mounted PWA interface.

For example, the car PWA is a music application. In response to the user's startup operation, the browser client obtains the driving data and the vehicle PWA configuration data, determines that the current vehicle PWA configuration is that the volume is 50 decibels, and the font size is 12pt. According to the vehicle PWA configuration, the music playback interface is displayed. Afterwards, the driving data changes (for example, the road conditions change from smooth to congested). The browser client obtains the changed driving data and determines that the on-board PWA corresponding to the current driving data is configured with a volume of 30 decibels, a font size of 15pt, and music display. Playback interface. In this way, the reduced music volume and enlarged display fonts ensure the driver's driving safety in a deteriorating traffic environment. Exemplarily, FIG. 10 is a schematic flowchart of the vehicle application adaptive configuration method provided by the embodiment of the present application. As shown in Figure 10, the method includes the following steps.

S1001. Obtain the first driving data.

In some embodiments, the first driving data includes one or more of the following: weather conditions, day and night conditions, road conditions, vehicle speed, call conditions, and light conditions.

In some embodiments, the vehicle-mounted terminal acquires the first driving data after detecting the operation of starting the vehicle-mounted progressive web application. Alternatively, the vehicle-mounted terminal obtains the first driving data according to the second cycle. Or, when the driving data changes, the first driving data is updated.

For example, as shown in Figure 5, the vehicle-mounted PWA management unit 502 in the vehicle-mounted terminal (such as a vehicle-mounted system) detects the user's operation of starting the vehicle-mounted progressive web application, and requests the driving data collection unit 501 to obtain driving data. The driving data collection unit 501 collects driving data in real time according to the request and sends it to the vehicle-mounted PWA management unit 502. The vehicle-mounted PWA management unit 502 then sends the acquired driving data to the browser client. In this way, it is ensured that the display of the subsequent vehicle-mounted progressive web application display interface meets the needs of the current real-time driving environment.

As another example, as shown in FIG. 5 , the browser client in the vehicle-mounted terminal (eg, vehicle-mounted system) obtains the driving data sent by the vehicle-mounted PWA management unit 502 according to a preset cycle (eg, the second cycle). Afterwards, the browser client sends the collected driving data to the storage unit 505 for storage. After receiving the driving data, the storage unit 505 updates the historical driving data using the newly acquired driving data. In this way, when the browser client in the vehicle-mounted terminal subsequently determines that it needs to use the driving data, it can directly obtain the corresponding driving data from the storage unit 505.

As another example, as shown in Figure 5, the vehicle-mounted PWA management unit 502 in the vehicle-mounted terminal (such as a vehicle-mounted system) obtains the driving data collected by the driving data collection unit 501, determines that the driving data and historical driving data have changed, and changes the driving data to the historical driving data. The subsequent driving data is sent to the browser client. In this way, the browser client updates the historical driving data stored in the storage unit 505 based on the acquired driving data.

In some embodiments, the vehicle-mounted terminal determines that the running scenario of the browser application is the vehicle-mounted terminal scenario, and after enabling the intelligent experience, the first driving data is obtained.

As an example, configuration parameters are preset in the browser client. After the browser client detects the user's operation to launch the in-vehicle progressive web application, it determines whether the browser client runs the scenario according to the value of the preset configuration parameter. For the vehicle terminal scenario, and whether to start the intelligent experience. If both are yes, the browser client can obtain the driving data and adaptively adjust the running environment of the in-vehicle progressive web application based on the driving data.

S1002. Display the first interface according to the first driving data, and the display configuration of the first interface is the first vehicle configuration.

In some embodiments, if the vehicle-mounted terminal needs to display the first interface of the vehicle-mounted progressive web application, in addition to obtaining the first driving data, it also needs to obtain vehicle-mounted configuration data. Optionally, the vehicle-mounted terminal obtains the vehicle-mounted configuration data stored in the storage unit. Wherein, the storage unit updates the vehicle configuration data according to the first cycle. Or, in response to the operation of starting the vehicle-mounted progressive web application, the vehicle-mounted terminal requests the server to obtain vehicle-mounted configuration data.

It should be noted that the embodiment of the present application does not limit the order in which driving data and vehicle configurations are obtained. For example, the vehicle-mounted terminal can obtain driving data and vehicle-mounted data at the same time in response to the user's operation of starting the vehicle-mounted progressive web application; or, obtain the driving data first, and then obtain the vehicle configuration data; or, obtain the vehicle configuration data first, and then obtain the driving data. .

In some embodiments, the vehicle-mounted terminal matches the first vehicle-mounted configuration corresponding to the first driving data in the vehicle-mounted configuration data. And according to the first vehicle configuration, the first interface of the vehicle progressive web application is displayed.

For example, the vehicle-mounted terminal configures one or more of the volume, font size, and whether to support voice navigation during the process of displaying the first interface of the vehicle-mounted progressive web application based on the first vehicle configuration.

For example, the vehicle configuration data includes preset driving data and preset vehicle configuration corresponding to the preset driving data. The vehicle-mounted terminal matches the target preset driving data that is the same as the first driving data in the preset driving data, and determines the first vehicle configuration among the preset vehicle configurations corresponding to the target preset driving data.

In this way, the vehicle-mounted terminal can match the vehicle-mounted configuration corresponding to the preset vehicle-mounted configuration data that is the same as the current vehicle-mounted data in the preset vehicle-mounted configuration data based on the vehicle-mounted vehicle data. Afterwards, the vehicle-mounted terminal displays the interface of the vehicle-mounted progressive web application according to the vehicle-mounted configuration. This allows the display interface to match the current driving data to meet the user's needs and improve the user experience.

S1003. Obtain the second driving data. The first driving data is different from the second driving data.

In some embodiments, the second driving data includes one or more of the following: weather conditions, day and night conditions, road conditions, vehicle speed, call conditions, and light conditions.

Optionally, for other contents of step S1003, reference may be made to the relevant contents of step S1001, which will not be described again here.

S1004. Display the second interface according to the second driving data, and the display configuration of the second interface is the second vehicle configuration. Wherein, the first interface and the second interface are interfaces of the same vehicle-mounted progressive web application, and the first vehicle-mounted configuration is different from the second vehicle-mounted configuration.

In some embodiments, the first interface and the second interface are the same function page of the vehicle-mounted progressive web application, and the function page corresponds to the function of the vehicle-mounted progressive web application. For example, the vehicle-mounted progressive web application is a map application, and the first interface and the second interface are both navigation function pages in the map application. For another example, the vehicle-mounted progressive web application is a music application, and the first interface and the second interface are both music playback function pages in the music application, displaying lyrics.

For example, in the interface 801 shown in (a) of FIG. 8 , after detecting the user's click on the map application icon 81 , the vehicle-mounted terminal determines to start the map application corresponding to the map application icon 81 . The browser client in the vehicle-mounted terminal obtains the first driving data and the first vehicle-mounted configuration data, and matches the first vehicle-mounted configuration in the first vehicle-mounted configuration data according to the first driving data. After that, the browser client in the vehicle-mounted terminal displays as shown in the figure according to the first vehicle-mounted configuration. The map application interface 802 shown in (b) in 8.

For another example, in the interface 801 shown in (a) of FIG. 8 , after detecting the user's click on the map application icon 81 , the vehicle-mounted terminal determines to start the map application corresponding to the map application icon 81 . The browser client in the vehicle-mounted terminal obtains the second driving data and the second vehicle-mounted configuration data, and matches the second vehicle-mounted configuration in the second vehicle-mounted configuration data according to the second driving data. Afterwards, the browser client in the vehicle-mounted terminal displays the map application interface 803 as shown in (c) of Figure 8 according to the second vehicle-mounted configuration.

As another example, when the browser client displays the map application interface 802 as shown in (b) of FIG. 8 , it receives the driving data and determines that the driving data is different from the driving data obtained last time. Then, the browser client can match the vehicle configuration in the vehicle data based on the latest received driving data. According to the vehicle configuration determined this time, the browser client displays the map application interface 803 as shown in (c) of Figure 8 . The display font of interface 803 is larger than that of interface 802, and supports voice navigation, enabling the browser client to adaptively adjust the running environment of the map application based on driving data.

In this way, the browser client can adaptively display the in-vehicle progressive web application based on the latest acquired driving data and vehicle configuration data, which can further ensure that the displayed in-vehicle progressive web application meets the current driving data requirements, further ensuring that the driver's driving Safety. The above is a detailed description of the vehicle application adaptive configuration method provided by the embodiment of the present application in conjunction with Figures 4-10. The vehicle application adaptive configuration device provided by the embodiment of the present application will be described in detail below with reference to FIG. 11 .

In one possible design, FIG. 11 is a schematic structural diagram of a vehicle-mounted terminal provided by an embodiment of the present application. As shown in Figure 11, the vehicle-mounted terminal 1100 may include: a transceiver unit 1101, a processing unit 1102, and a display unit 1103. The vehicle-mounted terminal 1100 can be used as a vehicle-mounted application adaptive configuration device to implement the functions of the vehicle-mounted terminal involved in the above method embodiments.

Optionally, the transceiver unit 1101 is used to support the vehicle-mounted terminal 1100 in executing S1001 and S1003 in Figure 10 .

Optionally, the processing unit 1102 is used to support the vehicle-mounted terminal 1100 in executing S1002 and S1004 in FIG. 10 .

Optionally, the display unit 1103 is used to support the vehicle-mounted terminal 1100 to display interface content; and/or to support the vehicle-mounted terminal 1100 to execute S1002 and S1004 in FIG. 10 .

The transceiver unit may include a receiving unit and a transmitting unit, may be implemented by a transceiver or a transceiver-related circuit component, and may be a transceiver or a transceiver module. The operation and/or function of each unit in the vehicle-mounted terminal 1100 is to implement the corresponding process of the vehicle-mounted application adaptive configuration method described in the above-mentioned method embodiment. All relevant content of each step involved in the above-mentioned method embodiment can be quoted. The function description of the corresponding functional unit will not be repeated here for the sake of brevity.

Optionally, the vehicle-mounted terminal 1100 shown in Fig. 11 may also include a storage unit (not shown in Fig. 11), in which programs or instructions are stored. When the transceiver unit 1101, the processing unit 1102, and the display unit 1103 execute the program or instruction, the vehicle-mounted terminal 1100 shown in FIG. 11 can execute the vehicle-mounted application adaptive configuration method described in the above method embodiment.

For the technical effects of the vehicle-mounted terminal 1100 shown in FIG. 11 , reference can be made to the technical effects of the vehicle-mounted application adaptive configuration method described in the above method embodiment, and will not be described again here.

In addition to being in the form of the vehicle-mounted terminal 1100, the technical solution provided by this application can also be a functional unit or chip in the vehicle-mounted terminal, or a device used in conjunction with the vehicle-mounted terminal.

An embodiment of the present application also provides a chip system, including: a processor, the processor is coupled to a memory, The memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the chip system implements the method in any of the above method embodiments.

Optionally, there may be one or more processors in the chip system. The processor can be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in memory.

Optionally, there may be one or more memories in the chip system. The memory may be integrated with the processor or may be provided separately from the processor, which is not limited by the embodiments of the present application. For example, the memory may be a non-transient processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be separately provided on different chips. The embodiments of this application vary on the type of memory, and The arrangement of the memory and processor is not specifically limited.

For example, the chip system can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC). ), it can also be a central processor (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (micro controller unit, MCU), it can also be a programmable logic device (PLD) or other integrated chip.

It should be understood that each step in the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software. The method steps disclosed in conjunction with the embodiments of this application can be directly implemented by a hardware processor, or executed by a combination of hardware and software modules in the processor.

Embodiments of the present application also provide a computer-readable storage medium. A computer program is stored in the computer-readable storage medium. When the computer program is run on a computer, it causes the computer to perform the above related steps to implement the above embodiments. Adaptive configuration method for in-vehicle applications.

An embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, it causes the computer to perform the above-mentioned related steps to implement the vehicle-mounted application adaptive configuration method in the above-mentioned embodiment.

In addition, the embodiment of the present application also provides a device. The device may specifically be a component or module, and the device may include one or more connected processors and memories. Among them, memory is used to store computer programs. When the computer program is executed by one or more processors, the device is caused to execute the vehicle-mounted application adaptive configuration method in each of the above method embodiments.

Among them, the devices, computer-readable storage media, computer program products or chips provided by the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects it can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be described again here.

The steps of the methods or algorithms described in connection with the disclosure of the embodiments of this application can be implemented in hardware or by a processor executing software instructions. Software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read only memory (ROM), erasable programmable read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), register, hard disk, removable hard disk, compact disc (CD-ROM) or any other form of storage media well known in the art. An exemplary storage medium is coupled to the processor such that the processor can read from the storage medium Information can be retrieved and information can be written to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium may be located in an application specific integrated circuit (AP device application specific integrated circuit, ASIC).

Through the above description of the embodiments, those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In practical applications, the above function allocation can be completed by different functional modules according to needs; that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working processes of the systems, devices and units described above, reference can be made to the corresponding processes in the foregoing method embodiments, which will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed method can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components may be combined or integrated into another system, or some features may be ignored. or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of modules or units, and may be in electrical, mechanical or other forms.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

Computer-readable storage media includes but is not limited to any of the following: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, etc. Various media that can store program code.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be covered by the protection scope of the present application. . Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (12)

1. An adaptive configuration method for vehicle-mounted applications, characterized in that it is applied to vehicle-mounted terminals, and the method includes:

   Get the first driving data;

   Display a first interface according to the first driving data, and the display configuration of the first interface is a first vehicle configuration;

   Get the second driving data;

   According to the second driving data, a second interface is displayed, and the display configuration of the second interface is a second vehicle-mounted configuration; wherein the first driving data is different from the second driving data, and the first interface and The second interface is an interface of the same vehicle-mounted progressive web application, and the first vehicle-mounted configuration is different from the second vehicle-mounted configuration.
2. The method according to claim 1, characterized in that, before displaying the first interface according to the first driving data, the method further includes:

   Obtain vehicle configuration data;

   Displaying a first interface based on the first driving data includes:

   Match the first vehicle configuration corresponding to the first driving data according to the vehicle configuration data;

   According to the first vehicle configuration, the first interface of the vehicle-mounted progressive web application is displayed.
3. The method according to claim 2, characterized in that said obtaining vehicle configuration data includes:

   Obtain vehicle-mounted configuration data stored in the storage unit; wherein the storage unit updates the vehicle-mounted configuration data from the server according to the first cycle;

   or,

   In response to the operation of starting the vehicle-mounted progressive web application, a request is made to the server to obtain the vehicle-mounted configuration data.
4. The method according to claim 2 or 3, characterized in that the vehicle configuration data includes preset driving data and a preset vehicle configuration corresponding to the preset driving data, and the matching of the vehicle configuration data according to the vehicle configuration data The first vehicle configuration corresponding to the first driving data includes:

   In the preset driving data, match the target preset driving data that is the same as the first driving data;

   The first vehicle configuration among the preset vehicle configurations corresponding to the target preset driving data is determined.
5. The method according to any one of claims 1 to 4, characterized in that the first vehicle configuration includes one or more of the volume size, font size, and whether to support voice navigation during the display of the first interface. item.
6. The method according to any one of claims 1-5, characterized in that said obtaining the first driving data includes:

   Detecting the operation of starting the vehicle-mounted progressive web application and obtaining the first driving data;

   Or, obtain the first driving data according to the second cycle;

   Or, when the driving data changes, the first driving data is updated.
7. The method according to any one of claims 1 to 6, characterized in that, before displaying the first interface according to the first driving data, the method further includes:

   It is determined that the running scenario of the browser application is the vehicle terminal scenario, and the intelligent experience has been enabled.
8. The method according to any one of claims 1 to 7, characterized in that the first driving data or the second driving data include one or more of the following: weather conditions, day and night conditions, road conditions, vehicle speed, Call conditions and light conditions.
9. The method according to any one of claims 1 to 8, characterized in that the first interface and the second interface are the same functional pages of the vehicle-mounted progressive web application.
10. A vehicle-mounted terminal, characterized in that the vehicle-mounted terminal includes: a display screen, a processor and a memory, the display screen and the memory are coupled to the processor, and the memory is used to store computer readable instructions. The processor reads the computer-readable instructions from the memory, causing the vehicle-mounted terminal to execute the method according to any one of claims 1-9.
11. A computer-readable storage medium, characterized in that the computer-readable storage medium includes a computer program. When the computer program is run on a vehicle-mounted terminal, the vehicle-mounted terminal causes the vehicle-mounted terminal to execute any one of claims 1-9. method described in the item.
12. A computer program product, characterized in that, when the computer program product is run on a computer, it causes the computer to execute the method according to any one of claims 1-9.