Page fusion method, device, equipment, storage medium and program product

Abstract

This application discloses a page fusion method, apparatus, device, storage medium, and program product, relating to the field of data processing technology. The method includes: obtaining page access information corresponding to a first page in a vehicle infotainment system, the page access information indicating at least one second page accessed by a user after accessing the first page within a preset time period; determining the page correlation degree between the first page and each second page based on the page access information; and fusion of the first page and a third page, wherein the third page is the page among at least one second page whose page correlation degree reaches a first threshold.

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of data processing technology, and in particular to a page merging method, apparatus, device, storage medium, and program product. Background Technology

[0002] With the widespread use of smart devices, users rely heavily on mobile applications in their daily lives. However, switching between applications after using one requires frequent page switching and complex workflows, negatively impacting the user experience. Summary of the Invention

[0003] One objective of this application is to provide a page fusion method. Its advantage lies in obtaining page access information corresponding to a first page in the vehicle infotainment system, determining the page relevance between the first page and each second page, and then fusion the first page with at least one third page whose page relevance reaches a first threshold. This reduces the frequency of user page switching and improves operational convenience. Furthermore, based on page access information of at least one second page accessed by the user after accessing the first page within a preset time period, two pages with high relevance can be merged. Thus, embodiments of this application can dynamically adjust the merged pages according to the user's access habits and preferences to provide a more personalized user experience.

[0004] Another objective of this application is to provide a page fusion method. Its advantage lies in that the in-vehicle device determines the access frequency of each second page based on page access information, and then determines the page relevance between the first page and each second page based on the access frequency. Therefore, by analyzing user behavior when jumping from the first page to the second page, the second page most frequently visited by the user after visiting the first page can be quickly identified. Moreover, a higher page relevance often means that the first and second pages are highly correlated. After merging pages with high relevance, users can directly operate on the merged page without frequently switching pages, thus improving the user experience.

[0005] Another objective of this application is to provide a page fusion method. Its advantage lies in that the in-vehicle device, through the obtained control operation information, merges the layout tree of the first page with the layout tree of the third page to obtain a merged page, and adjusts the display parameters of the controls on the merged page. Therefore, by merging the layout trees of different pages, the in-vehicle device can achieve cross-page resource integration and information sharing, improving the overall integrity and coherence of the page. Moreover, by adjusting the display parameters of the merged page, the layout and interaction methods of controls can be prioritized, making user operation more convenient and intuitive.

[0006] Another objective of this application is to provide a page fusion method. Its advantage lies in that the in-vehicle device determines the control association degree between each first control and each second control through control operation information. Then, based on the control association degree, the layout tree of the first page and the layout tree of the third page are merged to obtain the layout tree of the merged page. In this way, the layout tree of the merged page can be adjusted according to the association degree of the controls actually used by the user, making frequently used or related controls closer together, improving the convenience of user operation. Moreover, because related controls are located close to each other, users can more easily find and use the controls they need, enhancing page usability.

[0007] Another objective of this application is to provide a page fusion method. Its advantage lies in that the in-vehicle device adjusts the display parameters of each control on the fused page by acquiring the frequency of user operations on each control within a preset time period, making the fused page more tailored to the user's personalized needs. Frequently used controls can be made more prominent or easily accessible, improving operational efficiency. Furthermore, by optimizing the layout and display of controls, obstacles for users switching between different controls are reduced, making operation smoother and avoiding user confusion caused by too many controls or a cluttered layout. Additionally, if the transparency of a control falls below a certain threshold, that control is removed from the fused page. Removing controls with low transparency avoids visual interference between page elements, improving the overall page clarity and readability. Moreover, removing unnecessary controls with low transparency makes the page more concise and aesthetically pleasing, enhancing the user experience.

[0008] Another objective of this application is to provide a page merging method. Its advantage lies in that the in-vehicle device can acquire controls selected by the user on both the first and third pages, and merge these controls onto a single page. This allows users to select and combine controls from different pages according to their needs and preferences, achieving personalized customization. This personalization enhances user satisfaction and loyalty. Furthermore, merging controls reduces the resource consumption of the in-vehicle system across different pages, improving the system's response speed and stability.

[0009] To achieve the above objectives, the technical solution of this application embodiment is implemented as follows:

[0010] In a first aspect, embodiments of this application provide a page fusion method, the method comprising: obtaining page access information corresponding to a first page in a vehicle system, the page access information being used to indicate at least one second page accessed by a user after accessing the first page within a preset time period; determining the page correlation degree between the first page and each second page based on the page access information; and fusion of the first page and a third page, the third page being the page among at least one second page whose page correlation degree reaches a first threshold.

[0011] Secondly, embodiments of this application provide a page fusion device, the device comprising: an obtaining module, configured to obtain page access information corresponding to a first page in a vehicle system, the page access information being used to indicate at least one second page accessed by a user after accessing the first page within a preset time period; a determining module, configured to determine the page correlation degree between the first page and each second page based on the page access information; and a fusion module, configured to fuse the first page and a third page, the third page being the page among at least one second page whose page correlation degree reaches a first threshold.

[0012] Thirdly, embodiments of this application provide an in-vehicle device, including a memory and a processor. The memory stores a computer program that can run on the processor, and the processor executes the program to implement the steps in the above-described method.

[0013] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps in the above-described method.

[0014] Fifthly, embodiments of this application provide a computer program product, including a computer program or instructions, which, when executed by a processor, implement the steps in the method described above.

[0015] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and are not intended to limit the technical solutions of this application. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application.

[0017] Figure 1 This is an optional flowchart illustrating the page merging method provided in an embodiment of this application;

[0018] Figure 2 This is an optional flowchart illustrating the page merging method provided in an embodiment of this application;

[0019] Figure 3This is an optional flowchart illustrating the page merging method provided in an embodiment of this application;

[0020] Figure 4 This is an optional flowchart illustrating the page merging method provided in an embodiment of this application;

[0021] Figure 5 This is an optional flowchart illustrating the page merging method provided in an embodiment of this application;

[0022] Figure 6 This is an optional flowchart illustrating the page merging method provided in an embodiment of this application;

[0023] Figure 7 This is a schematic diagram of the composition structure of a page fusion device provided in an embodiment of this application;

[0024] Figure 8 This is a schematic diagram of the hardware entity of an in-vehicle device provided in an embodiment of this application. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application are further described in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0026] In the following description, references to "some embodiments" refer to a subset of all possible embodiments. It is understood that "some embodiments" may be the same or different subsets of all possible embodiments and may be combined with each other without conflict. The terms "first / second / third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first / second / third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0027] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used herein is for descriptive purposes only and is not intended to limit the scope of this application.

[0028] With the widespread adoption of smart devices, users are increasingly reliant on applications in their daily lives. After using one application, users typically use another to perform subsequent actions. Take taking and sharing photos as an example: after capturing an image through the camera app, users may want to immediately share their joy with family and friends. However, the reality is often that they need to exit the camera app, open a social media page, and then go through several clicks and wait before the image can be uploaded and shared. This process is not only time-consuming and laborious but can also lead to frustration due to operational errors or network latency, significantly reducing the user experience.

[0029] To address the aforementioned issues, this application provides a page fusion method that can merge frequently used pages based on user browsing habits. This reduces the need for users to frequently switch pages, improves operational convenience, and ultimately enhances the user experience.

[0030] Figure 1 This is an optional flowchart illustrating the page merging method provided in an embodiment of this application. For example, this method is executed by an in-vehicle device. Figure 1 As shown, the method includes steps S101 to S103.

[0031] In step S101, the page access information corresponding to the first page in the vehicle system is obtained.

[0032] In some embodiments, page access information is used to indicate at least one second page accessed by a user after accessing a first page within a preset time period.

[0033] In some embodiments, the in-vehicle infotainment system may also be referred to as the operating system of an in-vehicle device, or an in-vehicle operating system. It is the operating system installed and running on the in-vehicle device. The in-vehicle infotainment system is system software that manages and controls in-vehicle hardware and software resources.

[0034] In some embodiments, the vehicle infotainment system may be an operating system such as Android, Linux, Windows, Apple, or Harmony. This application does not limit this.

[0035] In some embodiments of the Android system, the in-vehicle device can query all pages (Activities) in the vehicle's infotainment system through the package manager. In some embodiments, the in-vehicle system may have a log function that records user page visits. This log may include information such as the page identifier (ID), access time, and user identifier of the pages visited. Based on the log, the in-vehicle device can determine other pages visited by the user after visiting one page in the in-vehicle system.

[0036] In some embodiments, the vehicle infotainment system includes multiple pages, where the first page is any one of the multiple pages, and the second page is all the other pages except the first page. When a user accesses the first page, the vehicle infotainment system can record the page access information corresponding to the first page in the operation log, that is, record at least one second page accessed by the user after accessing the first page within a preset time period. In this way, the in-vehicle device can obtain the page access information recorded by the vehicle infotainment system and determine other pages accessed by the user within the preset time period after accessing the first page based on this information. The preset time period is used to analyze the user's behavior over a period of time after accessing the first page. This preset time period can be preset, such as ten minutes, one hour, etc., and this embodiment does not limit this.

[0037] Understandably, in-vehicle devices can extract page access information after a user visits the first page from the vehicle's system operation logs. Then, based on a preset time period, they can filter out all the second pages accessed by the user after visiting the first page, aggregate the results, and obtain detailed information about the second pages accessed by the user within the preset time period, such as the page identifier and access time of each second page accessed by the user.

[0038] For example, the in-vehicle system includes five pages: Page 1, Pages 2, 3, 4, and 5. The preset time period is 5 minutes. If the page access information includes the pages visited by the user and the access time, the page access information could be: (Page 2, 7:00:01), (Page 3, 7:02:30), (Page 2, 7:03:00), (Page 4, 7:03:20), (Page 2, 7:04:00), (Page 5, 7:04:10), (Page 2, 7:04:30), (Page 3, 7:05:00). Here, 7:00:01 represents the hour:minute:second of the access time. Based on this example, the in-vehicle device can determine each page visited by the user after visiting Page 1 and the access time of each page, thereby determining the user's page browsing habits.

[0039] In step S102, the page association degree between the first page and each second page is determined based on the page access information.

[0040] As is understandable, page relevance is used to indicate the degree of connection between different pages. Here, page relevance can be the probability or frequency of a user visiting a certain second page after visiting the first page.

[0041] In some embodiments, after obtaining page access information, the in-vehicle device can determine the number of times a user accesses each of the other second pages after accessing the first page, and then determine the page relevance between each second page and the first page based on the number of visits to each second page. For example, the in-vehicle device can use the quotient of the number of visits to each page and the total number of user visits as the page relevance between each second page and the first page. A higher page relevance indicates a stronger connection between the two pages.

[0042] In step S103, the first page and the third page are merged.

[0043] In some embodiments, the third page is a page whose page relevance reaches a first threshold among at least one second page.

[0044] Understandably, the first threshold is used to filter second pages that are highly relevant to the first page. The first threshold can be preset, for example, the first threshold is 0.8, but this embodiment does not limit this.

[0045] Understandably, after obtaining the page relevance between the first page and each second page, the in-vehicle device can identify the second page (also known as the third page) whose page relevance reaches a first threshold from among multiple second pages, and then merge the third page with the first page. Since the third page is a page that users frequently visit after accessing the first page, merging these two pages allows users to directly operate on both the first and third pages on the merged page without frequently switching pages, thus improving the user experience.

[0046] In some embodiments, after obtaining the page relevance between the first page and each second page, the in-vehicle device can sort the multiple second pages according to the page relevance. For example, the second pages can be sorted in descending order of page relevance, and then the second page with the highest relevance (i.e., the highest relevance to the first page) can be merged with the first page to obtain the merged page.

[0047] In some embodiments, the two pages are merged. The in-vehicle device can integrate the content of the two pages and then adjust the structure of the merged page based on the integrated content. For example, the core content, key information, or functions of one page can be extracted and integrated with the content of another page. Then, the structure of the merged page can be adjusted and optimized based on the integrated content.

[0048] In some embodiments, during the fusion process, the in-vehicle device can maintain consistency between the two pages in terms of style, color, font, etc.

[0049] In some embodiments, the in-vehicle device can back up the content of the pages to be merged before performing page merging. This allows for timely recovery should problems occur during the merging process or a rollback to the original state is required.

[0050] In this embodiment, by obtaining page access information corresponding to the first page in the vehicle system, the page relevance between the first page and each second page is determined. Then, the first page is merged with at least one third page whose page relevance reaches a first threshold. This reduces the frequency of page switching for users and improves operational convenience. Furthermore, based on page access information of at least one second page accessed by the user after accessing the first page within a preset time period, pages with high relevance can be merged. Thus, this embodiment can dynamically adjust the merged pages according to the user's access habits and preferences to provide a more personalized user experience.

[0051] Figure 2 This is an optional flowchart illustrating the page merging method provided in this application embodiment. Based on Figure 1 , Figure 1 Step S102 can be updated to steps S201 to S202, combining Figure 2 The steps shown are explained.

[0052] In step S201, the access frequency of each second page is determined based on the page access information.

[0053] Understandably, access frequency refers to the total number of times a user visits a particular second page, reflecting the page's popularity or user attention. After obtaining page access information, the in-vehicle device can determine the frequency of a user's visits to each subsequent second page after visiting the first page, thus obtaining the access frequency of each second page.

[0054] In step S202, the page relevance between the first page and each second page is determined based on the access frequency.

[0055] In some embodiments, after obtaining the access frequency of each second page, the in-vehicle device can divide the access frequency of each second page by the total number of pages accessed by the user after accessing the first page, and use this quotient as the page relevance between each second page and the first page. In some embodiments, the higher the access frequency, the higher the page relevance.

[0056] For example, based on the page access information example in step S101 above, after a user accesses page 1, the in-vehicle device can obtain the access frequency of pages 2, 3, 4, and 5. Based on the above example, the access frequency of page 2 is 4 times, the access frequency of page 3 is 2 times, the access frequency of page 4 is 1 time, and the access frequency of page 5 is 1 time. Thus, the in-vehicle device can determine that the total user access frequency is 4 + 2 + 1 + 1 = 8 times, the page correlation degree between page 2 and page 1 is 4 / 8 = 0.5, the page correlation degree between page 3 and page 1 is 2 / 8 = 0.25, the page correlation degree between page 4 and page 1 is 1 / 8 = 0.125, and the page correlation degree between page 5 and page 1 is 1 / 8 = 0.125. In this way, the in-vehicle device can obtain the page correlation degree between each page and page 1.

[0057] In some embodiments, by calculating the frequency of each subsequent page accessed by the user after accessing the first page, the page relevance between each page and the first page is determined, and pages with a page relevance higher than a first threshold are merged. In this way, multiple pages frequently used by the user can be intelligently integrated, enabling the user to perform multitasking more efficiently and improve overall operational efficiency.

[0058] In this embodiment, the in-vehicle device determines the access frequency of each second page based on page access information, and then determines the page relevance between the first page and each second page based on the access frequency. Therefore, by analyzing the user's behavior of jumping from the first page to the second page, the second page most frequently visited by the user after visiting the first page can be quickly identified. Moreover, a higher page relevance often means that the first page and the second page are highly correlated. By merging pages with high page relevance, users can directly operate on the merged page without frequently switching pages, thus improving the user experience.

[0059] Figure 3 This is an optional flowchart illustrating the page merging method provided in this application embodiment. Based on Figure 2 , Figure 2 Step S103 can be updated to steps S301 to S303, which will be discussed below. Figure 3 The steps shown are explained.

[0060] In step S301, control operation information is obtained.

[0061] In some embodiments, the control operation status is used to indicate to the user that after operating the controls on the first page within a preset time period, the user will then operate the controls on the third page.

[0062] As is understandable, each page includes multiple controls (also called components or page elements). These controls are graphical elements that users interact with to perform specific tasks or retrieve information. For example, multiple controls may include buttons, text boxes, drop-down menus, labels, etc. Buttons may include submit buttons, regular buttons, icon buttons, etc. Submit buttons are used to submit form data, while regular buttons perform general operations such as opening dialog boxes or navigating to another page. Icon buttons typically have icons for quick access to frequently used functions. Text boxes are used to enter text, such as usernames or passwords. Drop-down menus provide a series of options for users to choose from, typically to save space and reduce the number of clicks. Labels are used to describe the purpose or content of the space.

[0063] In some embodiments, when a user visits a page, they typically interact with multiple controls on that page. Therefore, the vehicle infotainment system can also record the user's interaction information with the controls on that page, including the control identifier, control attributes, and other information. The control attributes can include the control's style, value, and other properties.

[0064] In some embodiments, when the correlation between the first page and the third page exceeds a certain threshold, the in-vehicle device can obtain control operation information of the first page and the third page recorded by the vehicle system. In this way, the in-vehicle device can determine the controls operated by the user when accessing the first page and the controls operated by the user when accessing the third page based on the control operation information.

[0065] In step S302, based on the control operation information, the layout tree of the first page and the layout tree of the third page are merged to obtain the merged page.

[0066] In some embodiments, the in-vehicle device may also obtain the layout tree of the first page and the layout tree of the third page, the layout tree being used to indicate the hierarchy and position of multiple controls on the page.

[0067] Understandably, the in-vehicle device first creates a new layout tree, which represents the merged page. Then, based on the hierarchy and position of controls in the layout trees of the two pages, it adds controls to the new layout tree. If controls in the two pages conflict in the same position, the in-vehicle device can resolve the conflict according to preset priority rules.

[0068] For example, the priority rule could be that the page where the user interacts with the controls is displayed first, or, if the user interacts with controls on both pages or not interacts with controls on either page, the controls on the first page are displayed first. In this way, the in-vehicle device can first determine, based on control interaction information, whether controls on the two pages located at the same position (e.g., the first control on the first page and the second control on the third page) have been interacted with by the user. If the first control on the first page has been interacted with by the user and the second control on the second page has not been interacted with by the user, then the control at the conflicting position in the new layout tree is determined to be the first control.

[0069] In some embodiments, the in-vehicle device can also determine which controls on the first and third pages can be retained and which can be removed by analyzing the control operation information of the pages. For example, if a control on the two pages is exactly the same or only slightly different, the in-vehicle device can retain that control. Alternatively, if the controls on the two pages have similar functions but different behaviors, the in-vehicle device can merge their characteristics into a new control.

[0070] In step S303, the display parameters of the controls on the merged page are adjusted.

[0071] Understandably, after receiving the merged page, the in-vehicle device can adjust the display parameters of the controls on the merged page to ensure that the merged page is both aesthetically pleasing and practical.

[0072] In some embodiments, display parameters include the position and transparency of the control within the merged interface. The transparency of a control refers to the visibility of the control itself or the area containing the control to the page background or underlying content. Adjusting the transparency of a control can significantly affect the appearance of the user page and the user experience. The transparency of a control is typically represented by a value between 0 (completely transparent) and 1 (completely opaque).

[0073] For example, the in-vehicle device can traverse the layout tree of the merged page, starting from the root node and going through all the controls on the child nodes to determine whether each control needs to adjust its display parameters.

[0074] In some embodiments, the in-vehicle device can acquire user operation information for each control within a preset time period before page merging, and adjust the display parameters of the controls based on this information. When the user operation information includes the frequency of user operations on a control, if a user's operation on a certain control reaches a certain threshold, the in-vehicle device can consider that control to be frequently used by the user. In this case, the in-vehicle device can place frequently used controls in the most prominent area of ​​the merged page and increase the transparency of the most frequently used controls so that the user can more easily notice them.

[0075] In this embodiment, the in-vehicle device merges the layout trees of the first and third pages using the obtained control operation information to obtain a merged page, and then adjusts the display parameters of the controls on the merged page. Therefore, by merging the layout trees of different pages, this embodiment enables cross-page resource integration and information sharing, improving the overall integrity and coherence of the page. Furthermore, by adjusting the display parameters of the merged page, the layout and interaction methods of the controls can be prioritized, making user operation more convenient and intuitive.

[0076] Figure 4 This is an optional flowchart illustrating the page merging method provided in this application embodiment. Based on Figure 3 , Figure 3 Step S302 in the process can be updated to steps S401 to S402, which will combine Figure 4 The steps shown are explained.

[0077] In step S401, the control association degree between each first control and each second control is determined based on the control operation information.

[0078] In some embodiments, the first control is a control on a first page, and the second control is a control on a third page.

[0079] Understandably, in-vehicle devices can determine a user's actions on a first control on a first page when accessing the first page, and actions on a second control on a third page when accessing the third page, based on control operation information. For example, the user's actions on the first control on the first page when accessing the first page may include the control identifier of the first control operated by the user, and the user's operation time, among other information.

[0080] In some embodiments, the in-vehicle device can determine the control association degree between a first control on a first page and a second control on a third page based on the control identifier of a first control operated by the user and the user's operation time, and the control identifier of a second control operated by the user and the user's operation time. For example, the closer the time interval between the user's operation time on a first control on the first page and the user's operation time on a second control on the third page, the higher the control association degree between the two controls.

[0081] In step S402, based on the control association degree, the layout tree of the first page and the layout tree of the third page are merged to obtain the layout tree of the merged page.

[0082] Understandably, a layout tree is a tree-like data structure that describes the page structure and the hierarchical relationship between controls. Each node represents a control or layout container, and the connection relationship between nodes represents the parent-child relationship between controls.

[0083] In some embodiments, the in-vehicle device can determine the arrangement order, positional relationship, and attribute settings of each control on each page based on the layout tree of the first page and the layout tree of the third page. Then, based on the control relevance, it determines the arrangement order, positional relationship, and attribute settings of each control in the merged layout tree, i.e., arranging the position and hierarchy of each control in the merged page. For example, controls with high relevance can be placed in close proximity in the merged layout tree so that users can easily find and use them. Afterwards, the in-vehicle device can adjust the attribute settings of the controls, such as size, color, and font, to ensure consistency and coordination in the layout tree of the merged page.

[0084] In addition, during the integration process, issues such as control position conflicts and inconsistent attribute settings may be encountered. In such cases, the vehicle-mounted device can adjust and process the issues according to the pre-set priority rules to ensure that the layout tree of the integrated page can work normally.

[0085] In this embodiment, the in-vehicle device determines the control association degree between each first control and each second control through control operation information. Then, based on the control association degree, the layout tree of the first page and the layout tree of the third page are merged to obtain the layout tree of the merged page. In this way, the layout tree of the merged page can be adjusted according to the association degree of the controls actually used by the user, making frequently used or related controls closer together, improving the convenience of user operation. Moreover, because related controls are located close to each other, users can more easily find and use the required controls, enhancing the usability of the page.

[0086] Figure 5This is an optional flowchart illustrating the page merging method provided in this application embodiment. Based on Figure 3 , Figure 3 Step S303 can be updated to steps S501 to S502, combining Figure 5 The steps shown are explained.

[0087] In step S501, the frequency of user operations on each first control and the frequency of user operations on each second control within a preset time period are obtained.

[0088] In some embodiments, the in-vehicle device can acquire user operation information on each control on the first and third pages within a preset time period before page merging. This operation information may include control identifiers, operation types (such as click, input, selection), and operation times. After acquiring the user's operation information on each control within the preset time period, the in-vehicle device can count the operation frequency of each control within the preset time period, thus obtaining the user's operation frequency on each first control on the first page and the user's operation frequency on each second control on the third page.

[0089] In some embodiments, this step can be accomplished using a Structured Query Language (SQL) query tool.

[0090] In step S502, the display parameters of each third control on the merged page are adjusted based on the operation frequency.

[0091] Understandably, once the in-vehicle device obtains the operation frequency of each control, it can optimize the integrated page design based on the operation frequency of each control.

[0092] In some embodiments, the in-vehicle device can sort each third control in descending order of user interaction frequency to identify the most frequently and least frequently used controls, as well as their relative importance. The layout of the controls is then adjusted based on their relative importance. For example, the most frequently used controls can be placed in prominent positions on the page, such as at the top or center, so that users can quickly find and use them. Less frequently used controls can be placed in less prominent positions on the page or in a collapsed menu to reduce page clutter and improve the user experience.

[0093] In some embodiments, the in-vehicle device can also set a transparency gradient for the third control based on the frequency of its operation. The higher the operation frequency, the higher the transparency. For example, for controls that are most frequently used by the user, their transparency can be set to a higher level (i.e., less transparent) so that the user can see them clearly. For controls that are used less frequently, their transparency can be set to a lower level to reduce visual clutter on the page. After setting the transparency of the controls, the in-vehicle device can also ensure that the transparency settings are coordinated with the layout adjustments of the controls to achieve optimal visual effects and user experience.

[0094] In some embodiments, if the transparency of the third control is below a second threshold, the third control is removed from the merged page.

[0095] Understandably, in-vehicle devices can pre-set a reasonable second threshold based on page design and user experience requirements. This second threshold is used to distinguish which controls might cause visual interference to the user due to excessively low transparency. For example, the second threshold could be 0.1, but this application does not limit it to this.

[0096] In some embodiments, the in-vehicle device can iterate through all third-party controls on the merged page and obtain the current transparency of each third-party control. Then, it compares the transparency of each third-party control with a preset second threshold to identify third-party controls whose transparency is below the second threshold. If the transparency of each third-party control is above the second threshold, then each third-party control is retained in the merged page. If the transparency of any third-party control is below the second threshold, then that third-party control is removed from the merged page. This reduces visual clutter and improves page cleanliness and user experience.

[0097] In this embodiment, the in-vehicle device adjusts the display parameters of each control on the merged page by acquiring the frequency of user operations on each control within a preset time period, making the merged page more in line with the user's personalized needs. Frequently used controls can be made more prominent or easier to access, improving operational efficiency. Moreover, by optimizing the layout and display of controls, obstacles for users switching between different controls are reduced, making the operation smoother and avoiding user confusion caused by too many controls or a cluttered layout. In addition, if the transparency of a certain control is below a certain threshold, that control is removed from the merged page. By removing controls with low transparency, visual interference between page elements can be avoided, improving the overall clarity and readability of the page. Furthermore, removing unnecessary controls with low transparency can make the page more concise and aesthetically pleasing, improving the user experience.

[0098] Figure 6 This is an optional flowchart illustrating the page merging method provided in this application embodiment. Based on Figure 1 , Figure 1 The method may further include steps S601 to S602, combining Figure 6 The steps shown are explained.

[0099] In step S601, the controls on the first page and the controls on the third page selected by the user are obtained.

[0100] In some embodiments, users can select certain controls on the page they want to integrate. The in-vehicle device obtains the user's selection and records the user's selection in a data structure (e.g., an array, an object, or a database record). The data structure may include control information such as the control's identifier, control type, control position, and control size.

[0101] In some embodiments, after the user selects the controls they wish to integrate, the in-vehicle device can extract the corresponding control information from the layout or data structure of the first and third pages based on the user's selection.

[0102] In step S602, the controls selected by the user on the first page and the controls on the third page are merged into one page.

[0103] In some embodiments, after obtaining control information for multiple controls selected by the user, the in-vehicle device can integrate the obtained control information to ensure that they can be correctly displayed and function properly on a new page. Then, the in-vehicle device can create a new page based on the integrated control information. This new page includes the multiple controls selected by the user, as well as the layout and interaction relationships between the controls.

[0104] In some embodiments, by merging controls, users can complete operations on a single page that would otherwise require multiple pages, thus simplifying the workflow and improving efficiency. Furthermore, users can customize the selection and layout of controls to achieve a personalized page design.

[0105] In this embodiment, the in-vehicle device can acquire controls selected by the user on a first page and controls on a third page, and merge these controls onto a single page. This allows users to select and combine controls from different pages according to their needs and preferences, achieving personalized customization. This personalization improves user satisfaction and loyalty. Furthermore, merging controls reduces the resource consumption of the in-vehicle system across different pages, improving the system's response speed and stability.

[0106] Based on the foregoing embodiments, this application provides a page fusion device. The modules and units included in the device can be implemented by a processor in an in-vehicle device; of course, they can also be implemented by specific logic circuits. In the implementation process, the processor can be a central processing unit (CPU), a microprocessor unit (MPU), a digital signal processor (DSP), or a field programmable gate array (FPGA), etc.

[0107] Reference Figure 7 , Figure 7 This is a schematic diagram of the structural composition of a page merging device provided in an embodiment of this application. The page merging device 7 includes: an obtaining module 701, a determining module 702, and a merging module 703, wherein...

[0108] The obtaining module 701 is used to obtain page access information corresponding to the first page in the vehicle system. The page access information is used to indicate at least one second page accessed by the user after accessing the first page within a preset time period. The determining module 702 is used to determine the page correlation degree between the first page and each second page based on the page access information. The fusion module 703 is used to fuse the first page and the third page, where the third page is the page among at least one second page whose page correlation degree reaches a first threshold.

[0109] In some embodiments, the determining module 702 is further configured to: determine the access frequency of each second page based on page access information; and determine the page relevance between the first page and each second page based on the access frequency, wherein the higher the access frequency, the higher the page relevance.

[0110] In some embodiments, the fusion module 703 includes: an obtaining unit, configured to obtain control operation information, wherein the control operation information is used to indicate that the user operates on the controls on the first page and then operates on the controls on the third page within a preset time period; a fusion unit, configured to merge the layout tree of the first page and the layout tree of the third page based on the control operation information to obtain a fused page, wherein the layout tree is used to indicate the hierarchical structure and position of multiple controls on the page; and an adjusting unit, configured to adjust the display parameters of the controls on the fused page, wherein the display parameters include the position and transparency of the controls in the fused interface.

[0111] In some embodiments, the fusion unit is further configured to: determine the control association degree between each first control and each second control based on control operation information, wherein the first control is a control on a first page and the second control is a control on a third page; and merge the layout tree of the first page and the layout tree of the third page based on the control association degree to obtain the layout tree of the merged page.

[0112] In some embodiments, the adjustment unit is further configured to: obtain the frequency of user operations on each first control and the frequency of user operations on each second control within a preset time period, wherein the first control is a control on a first page and the second control is a control on a third page; and adjust the display parameters of each third control on the merged page based on the operation frequency, wherein the higher the operation frequency, the higher the transparency.

[0113] In some embodiments, the adjustment unit is further configured to: remove the third control from the merged page when the transparency of the third control is lower than a second threshold.

[0114] In some embodiments, the fusion module is further configured to: obtain the controls selected by the user on the first page and the controls on the third page; and merge the controls selected by the user on the first page and the controls on the third page onto one page.

[0115] The descriptions of the apparatus embodiments above are similar to those of the method embodiments above, and have similar beneficial effects. In some embodiments, the functions or modules included in the apparatus provided in this application can be used to perform the methods described in the method embodiments above. For technical details not disclosed in the apparatus embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0116] It should be noted that, in the embodiments of this application, if the above-described page fusion method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware, software, or firmware, or any combination of hardware, software, and firmware.

[0117] This application provides an in-vehicle device, including a memory and a processor. The memory stores a computer program that can run on the processor, and the processor executes the program to implement the steps in the above-described method.

[0118] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps in the above-described method. The computer-readable storage medium can be transient or non-transient.

[0119] This application provides a computer program including computer-readable code, wherein when the computer-readable code is executed in a computer device, a processor in the computer device performs steps for implementing the method described above.

[0120] This application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, it implements the steps in the above-described method. This computer program product can be implemented specifically through hardware, software, or a combination thereof. In some embodiments, the computer program product is specifically embodied as a computer storage medium; in other embodiments, the computer program product is specifically embodied as a software product, such as a software development kit (SDK), etc.

[0121] It should be noted that the descriptions of the various embodiments above tend to emphasize the differences between them, while their similarities or commonalities can be referred to interchangeably. The descriptions of the above embodiments of the device, storage medium, computer program, and computer program product are similar to the descriptions of the above method embodiments and have similar beneficial effects. For technical details not disclosed in the embodiments of the vehicle-mounted device, storage medium, computer program, and computer program product of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0122] Figure 8 This is a schematic diagram of the hardware entity of an in-vehicle device provided in an embodiment of this application, such as... Figure 8 As shown, the hardware entity of the vehicle-mounted device 8 includes a processor 801 and a memory 802, wherein the memory 802 stores a computer program that can run on the processor 801, and the processor 801 executes the program to implement the steps in the method of any of the above embodiments.

[0123] The memory 802 stores computer programs that can run on the processor. The memory 802 is configured to store instructions and applications that can be executed by the processor 801. It can also cache data to be processed or already processed by the processor 801 and the various modules in the vehicle device 8 (e.g., image data, audio data, voice communication data and video communication data). It can be implemented by flash memory or random access memory (RAM).

[0124] When the processor 801 executes the program, it implements the steps of the page blending method described above. The processor 801 typically controls the overall operation of the vehicle-mounted device 8.

[0125] This application provides a computer storage medium storing one or more programs that can be executed by one or more processors to implement the steps of the page merging method as described in any of the above embodiments.

[0126] It should be noted that the descriptions of the storage medium and device embodiments above are similar to those of the method embodiments above, and have similar beneficial effects. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0127] The aforementioned processor can be at least one of the following: Application Specific Integrated Circuit (ASIC), DSP, Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), FPGA, CPU, controller, microcontroller, and microprocessor. It is understood that other electronic devices can also implement the functions of the aforementioned processor, and this application does not specifically limit the specific implementation.

[0128] The aforementioned computer storage media / memory can be ROM, Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Ferromagnetic Random Access Memory (FRAM), Flash Memory, Magnetic Surface Memory, Optical Disc, or Compact Disc Read-Only Memory (CD-ROM), etc.; or it can be various terminals that include one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0129] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above steps / processes do not imply a sequential order of execution; the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0130] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

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

[0132] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected based on actual needs to achieve the purpose of this embodiment.

[0133] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0134] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0135] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence or the part that contributes to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, magnetic disks, or optical disks.

[0136] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A page merging method, characterized in that, The method includes: Obtain page access information corresponding to the first page in the vehicle system. The page access information is used to indicate at least one second page accessed by the user after accessing the first page within a preset time period. Based on the page access information, determine the page association degree between the first page and each second page; The first page and the third page are merged, wherein the third page is the page whose page relevance reaches a first threshold among the at least one second page.

2. The method according to claim 1, characterized in that, Determining the page relevance between the first page and each second page based on the page access information includes: Based on the page access information, the access frequency of each second page is determined; Based on the access frequency, the page relevance between the first page and each of the second pages is determined; the higher the access frequency, the higher the page relevance.

3. The method according to claim 1, characterized in that, The merging of the first page and the third page includes: Obtain control operation information, which is used to indicate that the user operates on the controls on the first page and then operates on the controls on the third page within a preset time period; Based on the control operation information, the layout tree of the first page and the layout tree of the third page are merged to obtain a merged page. The layout tree is used to indicate the hierarchical structure and position of multiple controls on the page. Adjust the display parameters of controls on the merged page, including the position and transparency of the controls in the merged interface.

4. The method according to claim 3, characterized in that, The step of merging the layout tree of the first page and the layout tree of the third page based on the control operation information to obtain a merged page includes: Based on the control operation information, the control association degree between each first control and each second control is determined, wherein the first control is a control on the first page and the second control is a control on the third page; Based on the control association, the layout tree of the first page and the layout tree of the third page are merged to obtain the layout tree of the merged page.

5. The method according to claim 3, characterized in that, The adjustment of the display parameters of controls on the merged page includes: The frequency of user operations on each first control and the frequency of user operations on each second control within a preset time period are obtained. The first control is the control on the first page, and the second control is the control on the third page. Based on the operation frequency, the display parameters of each third control on the merged page are adjusted; the higher the operation frequency, the higher the transparency.

6. The method according to claim 5, characterized in that, The method further includes: If the transparency of the third control is lower than the second threshold, the third control is removed from the merged page.

7. The method according to claim 1, characterized in that, The merging of the first page and the third page includes: Obtain the controls selected by the user on the first page and the controls on the third page; The controls selected by the user on the first page and the controls on the third page are combined into one page.

8. A page blending device, characterized in that, The device includes: The acquisition module is used to acquire page access information corresponding to the first page in the vehicle system. The page access information is used to indicate at least one second page accessed by the user after accessing the first page within a preset time period. The determination module is used to determine the page association degree between the first page and each second page based on the page access information; The fusion module is used to merge the first page and the third page, wherein the third page is the page whose page relevance reaches a first threshold among the at least one second page.

9. An in-vehicle device, comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

Images