Page labeling method and device, vehicle, storage medium and product

Abstract

The invention relates to a page labeling method and device, a vehicle, a computer readable storage medium and a computer program product. The method comprises the following steps: determining an initial application; and according to a target page element, determining a target canvas from the associated canvas of the initial application, so as to label the target page element on the target canvas. According to the method, the page element labeling efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of display control technology, and in particular to a page marking method, device, vehicle, computer-readable storage medium, and computer program product. Background Art

[0002] In the smart cockpit, the driver and passengers can use voice to simulate clicking on page elements on the screen to perform voice operations (such as switching the currently playing song, increasing the volume, etc.).

[0003] In order to ensure that users can operate page elements by voice (such as clicking a "play" button), each page element needs to be semantically annotated in advance.

[0004] In related page element annotation technologies, it is generally necessary to create a new layer as a canvas to draw annotation patterns, and use the annotation patterns to annotate page elements. However, this annotation method of creating a new canvas leads to low efficiency in page element annotation. Summary of the invention

[0005] Embodiments of the present application provide a page annotation method, apparatus, vehicle, computer-readable storage medium, and computer program product, aiming to improve the efficiency of page element annotation.

[0006] In order to achieve the above object, according to a first aspect of the present application, a page marking method is provided, the method comprising:

[0007] Identify initial applications;

[0008] According to the target page element, a target canvas is determined from the associated canvases of the initial application, so as to mark the target page element on the target canvas.

[0009] Optionally, determining the target canvas from the associated canvases of the initial application includes:

[0010] Get the root view of the initial application;

[0011] Based on the root view, a target canvas is determined from canvases associated with the initial application.

[0012] Optionally, the determining the target canvas from the associated canvases of the initial application based on the root view includes:

[0013] If the target page element exists in the root view, a target canvas is determined from a plurality of canvases included in the root view.

[0014] Optionally, the determining the target canvas from the associated canvases of the initial application based on the root view includes:

[0015] If the target page element does not exist in the root view, the root canvas of the webpage of the initial application is obtained, and the root canvas of the webpage is determined as the target canvas of the target page element.

[0016] Optionally, determining the target canvas from a plurality of associated canvases included in the root view includes:

[0017] Determine an initial canvas where the target page element is located and size information of the initial canvas from a plurality of canvases included in the root view;

[0018] When the size information is greater than a preset size threshold, the initial canvas is determined as the target canvas.

[0019] Optionally, the method further comprises:

[0020] When the size information is less than or equal to a preset size threshold, determining a reference canvas of the initial canvas according to a hierarchical relationship between canvases included in the root view;

[0021] A target canvas is determined from the reference canvas based on size information of the reference canvas.

[0022] Optionally, determining the target canvas from the reference canvas based on the size information of the reference canvas includes:

[0023] A reference canvas whose size information is greater than a preset size threshold is determined as a target canvas.

[0024] Optionally, marking the target page element on the target canvas includes:

[0025] Determining second position information of a preset annotation in a corresponding direction according to first position information of the target page element in multiple directions of the target canvas;

[0026] According to the second position information, the preset annotation is drawn on the target canvas to annotate the target page element.

[0027] Optionally, marking the target page element on the target canvas includes:

[0028] Acquire the first screen coordinates of the target page element based on the display screen coordinate system, and acquire the second screen coordinates of the web page root canvas based on the display screen coordinate system;

[0029] Calculating preset marked screen coordinates according to the first screen coordinates and the second screen coordinates;

[0030] According to the screen coordinates, the preset annotation is drawn on the target canvas to annotate the target page element.

[0031] Optionally, obtaining the root view of the initial application includes:

[0032] Obtaining the window type of the initial application;

[0033] A preset interface corresponding to the window type is called according to the window type to obtain the root view of the initial application.

[0034] Optionally, the acquiring the root view of the initial application by calling a preset interface corresponding to the window type according to the window type includes:

[0035] In the case where the window type is a first window type, calling an application drawing interface to obtain a root view of the initial application; the first window type includes: an active window;

[0036] In the case where the window type is a second window type, the annotation drawing interface of the root view is called to obtain the root view of the initial application; the second window type includes: a pop-up window.

[0037] Optionally, the target page element is obtained by the following steps:

[0038] Get the user's application operation voice triggered by the voice application;

[0039] The application operation voice is processed to obtain a target page element.

[0040] Optionally, determining the initial application includes:

[0041] Determining a target display screen from a plurality of initial display screens according to voice positioning information in the voice operation information corresponding to the target page element;

[0042] An application corresponding to the application page displayed on the target display screen is determined as an initial application.

[0043] According to a second aspect of the present application, a page marking device is provided, comprising:

[0044] A first determination module, used to determine an initial application;

[0045] The second determination module is used to determine a target canvas from the associated canvases of the initial application according to the target page element, so as to mark the target page element on the target canvas.

[0046] According to a third aspect of the present application, a vehicle is provided, comprising a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the above-mentioned page marking method.

[0047] According to a fourth aspect of the present application, a computer-readable storage medium is provided, comprising a processor and a memory, wherein the memory stores a plurality of instructions; the processor loads instructions from the memory to execute the steps of the above-mentioned page marking method.

[0048] According to the fifth aspect of the present application, a computer program product is provided, comprising a computer program, wherein the computer program is stored in a computer-readable storage medium; when a processor of an electronic device reads the computer program from the computer-readable storage medium, the processor executes the computer program, so that the electronic device performs the steps of the above-mentioned page marking method.

[0049] In the page annotation method, device, vehicle, computer-readable storage medium and program product of the embodiment of the present application, by determining the initial application, according to the target page element, the target canvas is determined from the associated canvas of the initial application, so as to annotate the target page element on the target canvas. It can be seen that the present application can directly annotate the target page element on the existing canvas associated with the initial application without creating a new canvas, thereby improving the efficiency of page element annotation, effectively improving the efficiency of page display, allowing users to perform voice operations according to the annotated page elements, and also realizing more accurate voice operation control.

[0050] Other features and advantages of the present application will be described in detail in the subsequent detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application, and those skilled in the art can obtain other drawings based on these drawings without creative work.

[0052] In order to more completely understand the present application and its beneficial effects, the following description will be given in conjunction with the accompanying drawings, wherein the same figure numbers represent the same parts in the following description.

[0053] Figure 1 It is a schematic diagram of the overall architecture provided in an exemplary embodiment of the present application;

[0054] Figure 2 This is a schematic diagram of a first process of marking page elements provided in an exemplary embodiment of the present application;

[0055] Figure 3 This is a first schematic diagram of a page element annotation effect provided in an exemplary embodiment of the present application;

[0056] Figure 4 This is a schematic diagram of the HTML5 application window hierarchy provided in an exemplary embodiment of the present application;

[0057] Figure 5 is a schematic diagram of the canvas level provided in an exemplary embodiment of the present application;

[0058] Figure 6 This is a second schematic diagram of a page element annotation effect provided in an exemplary embodiment of the present application;

[0059] Figure 7 This is a third schematic diagram of a page element annotation effect provided in an exemplary embodiment of the present application;

[0060] Figure 8 This is a schematic diagram of a second process of marking page elements provided in an exemplary embodiment of the present application;

[0061] Fig. 9 is a schematic diagram of a page marking device provided in an exemplary embodiment of the present application;

[0062] Fig.10 It is a schematic diagram of the structure of a vehicle provided in one embodiment of the present application. DETAILED DESCRIPTION

[0063] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0064] According to the background technology description of this application, in a smart cockpit, the driver and passengers can use voice to simulate clicking on page elements on the screen to enhance the cockpit experience. However, most application page elements have no text information or contain multiple repeated page elements. Therefore, it is necessary to semantically annotate various types of page elements of the application to facilitate user voice control, such as adjusting the temperature of the car air conditioning, adjusting the Bluetooth connection status, etc.

[0065] In the current semantic annotation solution, it is common to integrate the voice software development kit (SDK) into the application, and then the voice controls the application through the SDK to perform self-annotation on the page, so that users can operate on the user interface of the application through voice commands, such as adding tags or annotations. However, the adaptation cost of this solution is high, and the application needs to dynamically adapt its own layout, and the promotion cost of third-party applications is high. If the third-party application does not integrate the above SDK, semantic annotation cannot be achieved, resulting in the inability to realize voice simulation clicks.

[0066] Therefore, in order to solve the above problems, the present application proposes a page annotation method, device, electronic device, computer-readable storage medium and computer program product. The present application aims to implement semantic annotation of any page element of any application on the Android Framework side, so that there is no need for application adaptation. Among them, the Android Framework is an important component of the Android system. It provides some core application programming interfaces (Application Programming Interface, API) and services, so that applications can interact with the system more easily.

[0067] However, if semantic annotation is performed on any page element of any application on the Android Framework side, there are at least the following problems that need to be overcome:

[0068] (1) Applications in the in-vehicle operating system have multiple window modes, such as full-screen mode, split-screen mode, small window mode, parallel window mode, and free window mode. Therefore, it is necessary to solve the problem of simultaneous voice annotation of application page elements in all window modes on the same screen. At the same time, applications will have many pop-up windows, including application pop-up windows and system pop-up windows. It is also necessary to solve the problem of how to semantically annotate page elements in pop-up windows.

[0069] (2) As more and more screens are installed in vehicle systems, the number of scenarios where a single system with multiple screens is applied is also increasing. The vehicle driver and each passenger are equipped with an operation screen. If voice operation is initiated at the same time to perform semantic annotation of page elements, the original semantic annotation solution can no longer meet the needs of this single system with multiple screens scenario;

[0070] (3) Currently, the technology for implementing third-party application pages is changing with each passing day. In addition to page layouts developed using native controls of the Android system, there are also a large number of application page layouts implemented using hybrid development technologies, such as HyperText Markup Language (HTML5) type page layouts. However, the Android Framework side cannot obtain HTML5 type page element information, which makes the existing annotation scheme invalid, so it is impossible to perform semantic annotation on this page element. Therefore, it is also an urgent problem to annotate page elements developed with non-native controls.

[0071] In order to overcome the above problems, the present application embodiment proposes the following Figure 1 The annotation architecture shown, such as Figure 1 As shown in the process ① in , some page elements are semantically annotated according to the page element information and business requirements to facilitate voice control. The voice application calls the system-side annotation interface provided by this application, such as Figure 1 As shown in the process ② in the above, this application adds a new extension module on the system process Framework side ( Figure 1 The blue module in the middle) enhances the functions of ATMS and WMS and provides annotation functions for application windows. The module first determines on which screens to annotate page elements, and then calls the application's annotation drawing interface to draw. Figure 1 As shown in process ③, this application adds a semantic annotation drawing module ( Figure 1 The yellow module in the middle is responsible for finding page elements, calculating the canvas level and position of annotations, and displaying semantic annotations by actively refreshing the page.

[0072] Through the above annotation architecture, this application can at least achieve the following effects:

[0073] (1) This application is implemented on the system framework side and does not require adaptation on the application side, saving the application adaptation cost. At the same time, this application supports any application to mark page elements, thereby improving the coverage of the solution.

[0074] (2) This application supports the annotation of application page elements in multiple window modes of the system, including full-screen mode, split-screen mode, and parallel window mode. This application can also be used to annotate application page elements. At the same time, it can also annotate page elements in the system pop-up box, thereby achieving compatible support for various types of application window modes in the system. New window modes that appear in the future can also be expanded to support;

[0075] (3) This application supports the application scenario of a single system with multiple screens in a vehicle system. The voice side can determine which vehicle screen the driver and passenger initiated the voice operation on based on the sound source positioning and mark the page elements, and then choose to mark the page elements on the corresponding screen;

[0076] (4) In addition to supporting annotation on application pages developed with Android native controls, this application also supports annotation on the newly popular pages developed using hybrid development technology, such as HTML5 type pages. Therefore, this application has a higher coverage of annotations on all page elements of the application than existing annotation solutions.

[0077] Specifically, for example, the page marking method in the embodiment of the present application is as follows: Figure 2 As shown, the following steps may be included:

[0078] S10, determining the initial application;

[0079] It should be noted that, in this embodiment, the initial application can be the application corresponding to the application page currently displayed on the vehicle display screen, so that the user can select the target page elements in the initial application for annotation through the voice application, where the voice application refers to software or services that use voice recognition technology to allow users to interact with devices or applications through voice commands, such as a voice intelligent assistant.

[0080] In this embodiment, the Framework extension module (such as Figure 1 As shown), an initial application can be determined, wherein at least one target page element can be displayed in the page displayed by the initial application, and the target page element can be understood as a page element to be annotated specified by the user through a voice application.

[0081] In this embodiment, the voice application can use the system accessibility service (Accessibility ManagerService) and the OCR solution (OCR is usually used to recognize text in images or photos and convert them into editable text or for other purposes) to obtain the page element information displayed by the initial application, such as Figure 1 As shown in process ①, users can semantically annotate some page elements according to page element information and business needs for easy voice control. Users can select elements on the page by voice, triggering the corresponding application operation voice, so that the system auxiliary service can filter whether there are elements selected by the user on the page, and when there are corresponding page elements, the voice application can call the Framework extension module on the system side to annotate the page elements.

[0082] S20: Determine a target canvas from the associated canvases of the initial application according to the target page element, so as to mark the target page element on the target canvas.

[0083] In this embodiment, after obtaining the target page element in the initial application, the application main process of the initial application can determine the target canvas from the associated canvases of the initial application, and can mark the target page element on the target canvas using a preset mark.

[0084] Specifically, for example, in this embodiment, Figure 1 The semantic annotation drawing module in the View drawing framework in the main process of the application shown can execute the steps of determining the target canvas from the associated canvases of the initial application according to the target page element and annotating the target page element on the target canvas.

[0085] Among them, the associated canvas of the initial application can be understood as the canvas currently created by the initial application. That is, when annotating the target page elements, this embodiment does not need to add a new canvas, and can directly select a canvas of a suitable level from the currently created canvases as the target canvas, which significantly improves the annotation and drawing efficiency, and also significantly improves the display effect of the page elements and corresponding semantic identifiers. This embodiment does not limit the number of canvas levels.

[0086] For example, Figure 3 In the page element annotation effect diagram shown, there are multiple repeated page elements “Avatar”. In this embodiment, the corresponding preset annotation patterns 1, 2 and 3 can be respectively marked for the three page elements.

[0087] It should be noted that in this embodiment, according to the above description, the third-party application page implementation technology is changing with each passing day. In addition to the page layout developed using the native control of the Android system, a large number of application page layouts implemented using hybrid development technology have also appeared, such as HTML5 type page layouts. However, the Android Framework side cannot obtain HTML5 type page element information, which causes the existing annotation scheme to fail. In the embodiment of the present application, the target page element can be a page element developed by the native control of the Android system, or a page element developed by hybrid development, such as an HTML5 type page element. In this way, this embodiment can effectively improve the page element annotation coverage rate and is generally applicable to voice annotation of various types of page elements.

[0088] Therefore, in this embodiment, the Framework extension module on the system side can receive the application operation voice, determine the initial application, and determine the target canvas from the associated canvas of the initial application according to the target page element, and can mark the target page element on the target canvas. It can be seen that the embodiment of the present application can directly mark the target page element on the existing canvas associated with the initial application without creating a new canvas, which improves the efficiency of drawing the logo pattern, and then improves the efficiency of marking the page elements, which can effectively improve the page display efficiency, so that the user can perform voice operations according to the marked page elements, and realize more accurate voice operation control.

[0089] In one embodiment, in the above S20, “determining the target canvas from the associated canvases of the initial application” may include:

[0090] S201, obtaining the root view of the initial application;

[0091] S202: Determine a target canvas from associated canvases of the initial application based on the root view.

[0092] In this embodiment, the application main process of the initial application can obtain the root view of the initial application through the annotation drawing module, and determine the target canvas from the associated canvases of the initial application according to the root view.

[0093] Specifically, for example, the initial application may search for the root view of all current pages in its main process (each root view may include multiple canvases), and then determine the target canvas from the associated canvases of the initial application according to the root view.

[0094] Therefore, this embodiment can clearly determine the hierarchical relationship between associated canvases by searching for the canvas through the root view, and determine the target canvas from the constructed associated canvases without rebuilding the target canvas, thereby significantly improving the efficiency of page element annotation.

[0095] Furthermore, in the above S202, “determining the target canvas from the associated canvases of the initial application based on the root view” may include:

[0096] S2021: If the target page element exists in the root view, determine a target canvas from multiple canvases included in the root view.

[0097] S2022: If the target page element does not exist in the root view, obtain the webpage root canvas of the initial application, and determine the webpage root canvas as the target canvas of the target page element.

[0098] It should be noted that, in this embodiment, according to the above description, the source information of the target page element may include: the target page element may be a page element developed by the native control of the Android system, or a page element developed by a hybrid development, such as an HTML5 type page element. However, it is worth noting that if the page element is developed using a new hybrid development architecture, such as an HTML5 type page element, then for this type of page element, the View drawing framework on the AndroidFramework side (such as Figure 1 As shown in the figure, it cannot be perceived, which makes it impossible to allocate a canvas for annotation drawing. However, for page elements developed by native controls of the Android system, the View drawing framework on the Android Framework side can perceive them.

[0099] Moreover, in this embodiment, no matter what kind of page element, the determined canvas is the canvas that has been constructed by the initial application, and the refresh drawing process of the existing page element is followed as a whole. There is no need to add a new canvas, but the annotation becomes part of the application page element, which significantly improves the annotation drawing efficiency and the display effect. The subsequent embodiments will elaborate on the canvas determination method and annotation drawing method of each type of page element, and will not be repeated here.

[0100] On this basis, after obtaining the root view of the initial application, it can be determined in advance whether the target page element can be found in the root view.

[0101] If the target page element is found in the root view, it means that the target page element is developed by the system native control, and the target canvas can be determined from the multiple canvases included in the root view.

[0102] If the target page element cannot be found in the root view, it means that the target page element is not developed by the system native control, that is, the target page element is developed by hybrid technology. For example, the target page element is an HTML5 type page element. In this case, the root canvas of the web page of the initial application can be obtained, and the root canvas of the web page can be determined as the target canvas of the target page element.

[0103] It is worth noting that even if the page is not developed by native controls, for example, HTML5 type pages, HTML5 type pages must also follow the Android application Activity layout to build the hierarchy when loaded into the Android system, such as Figure 4 As shown, Figure 4In the Activity window layout hierarchy, the first data structure is Activity, the second data structure is PhoneWindow, the third data structure is DecorView, and the fourth data structure is a root view added in DecorView. All HTML5 page layouts are drawn on this root view. Therefore, in this embodiment, if the target page element cannot be found in the root view, the annotation drawing module in the main application process can search the above window layout hierarchy, search for the root view in the window layout hierarchy, and use the root canvas of the web page under the root view as the target canvas to draw the preset annotation on the target canvas.

[0104] Therefore, in this embodiment, when drawing preset annotations, the annotation drawing module in the main process of the application needs to adopt different canvas determination methods for different types of page elements, so that the preset annotations can be completely drawn on the corresponding canvas, thereby realizing the annotation of any page element, significantly improving the annotation coverage rate of the page elements, and allowing users to perform precise voice control of the application.

[0105] Furthermore, in the above S2021, “determining a target canvas from multiple canvases included in the root view” may include:

[0106] Step a, determining the initial canvas where the target page element is located, and size information of the initial canvas from the multiple canvases included in the root view;

[0107] Step b: when the size information is greater than a preset size threshold, determining the initial canvas as the target canvas.

[0108] In this embodiment, if the target page element is developed by the system native control, the View drawing framework on the AndroidFramework side can perceive the page element. At this time, the main application process of the initial application can obtain the initial canvas where the target page element is located from the multiple canvases included in the root view, and obtain the size information of the initial canvas.

[0109] Then, it is determined whether the size information is greater than a preset size threshold, wherein the preset size threshold may be the size of a preset annotation, to ensure that the canvas is large enough to draw the preset annotation and avoid missing of the drawn annotation.

[0110] If it is determined that the size information of the initial canvas is greater than a preset size threshold, the initial canvas may be directly determined as the target canvas, and the preset annotation may be drawn on the canvas.

[0111] Therefore, in this embodiment, when the canvas size of the initial canvas is appropriate, the initial canvas is preferentially used as the target canvas, which can not only ensure the integrity of the drawn preset annotations, avoid the impact of missing annotations on the annotation display effect, but also improve the annotation drawing efficiency.

[0112] In one embodiment, the page marking method in the present application may further include:

[0113] Step c, when the size information is less than or equal to a preset size threshold, determining a reference canvas of the initial canvas according to the hierarchical relationship between the canvases included in the root view;

[0114] Step d: determining a target canvas from the reference canvas based on the size information of the reference canvas.

[0115] In this embodiment, if it is determined that the size information of the initial canvas is less than or equal to the preset size threshold, which means that the canvas size of the initial canvas is insufficient to draw the preset annotation, the reference canvas of the initial canvas can be determined according to the hierarchical relationship between the canvases included in the root view.

[0116] It should be noted that, in this embodiment, the hierarchical relationship between the canvases contained in the root view can be understood as the initial application has constructed canvases containing different levels, for example, Figure 5 As shown, there are currently four levels of associated canvases of the initial application, and the canvas sizes of the canvases at each level are different. If the canvas size of the initial canvas is not enough to draw the preset annotation, then the canvases of other levels other than the initial canvas can be used as reference canvases based on the hierarchical relationship between the canvases.

[0117] Furthermore, the application main process of the initial application may determine the target canvas from the reference canvas based on the size information of the reference canvas, so as to select the reference canvas that can completely draw the preset annotation as the target canvas.

[0118] Therefore, when the size of the initial canvas is not sufficient to draw the preset annotation, this embodiment can find a suitable reference canvas to draw the annotation, thereby ensuring the integrity of the drawn preset annotation and effectively improving the annotation display effect.

[0119] Furthermore, in the above step d, “determining the target canvas from the reference canvas based on the size information of the reference canvas” may include:

[0120] d10, determining a reference canvas whose size information is larger than a preset size threshold as a target canvas.

[0121] In this embodiment, the main application process of the initial application can select a reference canvas whose size information is greater than a preset size threshold from multiple reference canvases as the target canvas, so that the preset annotation can be fully displayed on the target canvas, wherein, according to the above description, the preset size threshold can be the size of the preset annotation.

[0122] Specifically, for example, the annotation drawing module in the main application process of the initial application can use a recursive algorithm to compare and calculate the size of the reference canvases at each level and a preset size threshold, and find a reference canvas at a suitable level as the target canvas.

[0123] In this way, this embodiment can traverse and search for reference canvases until a canvas that can fully display the preset annotation is found, thereby ensuring the integrity of drawing the preset annotation.

[0124] In one embodiment, in the above S20, “marking the target page element on the target canvas” may include:

[0125] S203, determining second position information of a preset annotation in a corresponding direction according to first position information of the target page element in multiple directions of the target canvas;

[0126] S204: Draw the preset annotation on the target canvas according to the second position information, and mark the target page element.

[0127] In this embodiment, if the target page element is developed by the system native control, the View drawing framework on the Android Framework side can perceive the page element (that is, the target page element exists in the root view). After determining the target canvas, Figure 6 As shown, the first position information of the target page element in multiple directions (such as up, down, left, and right) relative to the canvas boundary can be obtained, the second position information of the preset annotation in the corresponding direction can be calculated, and the preset annotation can be drawn on the target canvas at the second position information.

[0128] Therefore, in this embodiment, if the target page element can be found in the root view, the preset annotation can be drawn directly according to the calculated position between the target page element and the preset annotation, so that the preset annotation is displayed adjacent to the target page element, guiding the user to perform relevant voice control on the vehicle.

[0129] Furthermore, in the above S20, “marking the target page elements on the target canvas” may also include:

[0130] S205, obtaining a first screen coordinate of the target page element based on a display screen coordinate system, and obtaining a second screen coordinate of the web page root canvas based on a display screen coordinate system;

[0131] S206, calculating a preset marked screen coordinate according to the first screen coordinate and the second screen coordinate;

[0132] S207: Draw the preset annotation on the target canvas according to the screen coordinates, and annotate the target page element.

[0133] It should be noted that, in this embodiment, if the target page element is not developed by the system native control, the View drawing framework on the Android Framework side cannot perceive the page element. For example, if the target page element is an HTML5 type page element, the View drawing framework on the Android Framework side cannot perceive this type of page element, and therefore it is impossible to use the canvas determination method and logo drawing method of the page element developed by the native control.

[0134] Thus, in this embodiment, if the target page element is not developed by a native system control, the annotation drawing module in the main application process can obtain the first screen coordinates of the target page element on the target display screen.

[0135] It is worth noting that in this embodiment, the screen coordinates of the target page element can be obtained by the voice application and passed to the annotation drawing module of the application main process through the corresponding interface, so that the application main process can obtain the first screen coordinates of the target page element on the target display screen.

[0136] In addition, the screen coordinates of the root view of the web page (i.e., the second screen coordinates) can also be obtained, where it can be understood that the screen coordinates of the root view of the web page can refer to the absolute position of the view on the screen or window, usually with the upper left corner of the screen as the origin (0,0), the right as the positive direction of the x-axis, and the downward as the positive direction of the y-axis.

[0137] Furthermore, if Figure 7 As shown, the screen coordinates of the preset annotation can be calculated according to the first screen coordinates and the second screen coordinates, and the preset annotation can be drawn at the screen coordinates of the target canvas.

[0138] This embodiment ensures that even if the target page element is not developed by native controls, it can be annotated using preset annotations, which effectively adapts to the application page layout developed using hybrid development technology and is generally applicable to various types of page element annotation scenarios.

[0139] Therefore, in general, this embodiment is actually executed on the system framework side and does not require adaptation on the application side, which effectively saves the adaptation cost of the application, supports any initial application to perform page element annotation, and improves the coverage of the solution. In addition, this embodiment can support annotation on application pages developed with native controls, and also supports annotation on pages developed using hybrid development technology, such as HTML5 type pages. The coverage rate of annotation of all page elements of the application is significantly improved. In addition, this embodiment is drawn on the existing canvas of the application page element, and overall follows the refresh drawing process of the existing page element. There is no need to add a new layer as a canvas, but instead makes the annotation a part of the application page element, which not only improves the drawing efficiency, but also improves the display effect.

[0140] In one embodiment, in the above S201, “obtaining the root view of the initial application” may include:

[0141] S2011, obtaining the window type of the initial application;

[0142] S2012: Call a preset interface corresponding to the window type according to the window type to obtain the root view of the initial application.

[0143] After determining the current initial application, the Framework extension module in this embodiment can identify the window type of the initial application, and based on the window type, call a preset interface corresponding to the window type to obtain the root view of the initial application.

[0144] It should be noted that this embodiment does not limit the window type of the application, nor does it limit the window display mode of the application. For example, the target window can be a system pop-up window or a non-system pop-up window (such as an Activity type window), and the window display mode can be full-screen mode, split-screen mode, or parallel window mode.

[0145] It is understandable that a system pop-up window usually refers to an interface element provided by the operating system, which is used to display information, warnings, or request user input, such as error prompts, confirmation dialog boxes, etc. In Android development, an Activity window is a component used to represent a single screen with a user interface. Each Activity is an independent window that can contain user interaction elements.

[0146] Therefore, this embodiment can achieve compatible support for various types of application window modes in the system, and can also provide extended support for new window modes that appear later, so that each window can call the corresponding preset interface to obtain the root view of the initial application for voice annotation.

[0147] Furthermore, in the above S2012, “calling a preset interface corresponding to the window type according to the window type to obtain the root view of the initial application” may include:

[0148] Step e: when the window type is a first window type, calling an application drawing interface to obtain a root view of the initial application; the first window type includes: an active window;

[0149] Step f, when the window type is a second window type, calling the annotation drawing interface of the root view to obtain the root view of the initial application; the second window type includes: a pop-up window.

[0150] It should be noted that, in this embodiment, according to the above description, the window type may include an active window, such as an Activity window, and may also include a pop-up window, such as a WindowState window.

[0151] When the window type is an Activity type window, due to the rapid development of window types in the Android system, many different types of window structures have emerged, and different window structures have different data structures and display effects. Therefore, this embodiment can identify various types of windows, and obtain all Activity windows in the application main process (i.e., the active window in this embodiment) through their different data structures, so that each Activity window sequentially calls the application annotation drawing interface in the application main process to find all current root views in the application main process, and then the target canvas can be found in each root view.

[0152] If the window type is a system pop-up window, such as a WindowState window, you can call the annotation drawing interface of its root view in the pop-up WindowState window to get the root view of the initial application, and then you can find the target canvas in the root view.

[0153] Similarly, according to the above description, if the target page element is found in the root view, it means that the page element is developed using the system native control. If the target page element is not found, it means that the page element is not developed using the system native control. I will not go into details here.

[0154] Therefore, this embodiment supports the annotation of application page elements in multiple window modes of the system. Application page elements can be annotated in full-screen mode, split-screen mode, parallel window mode, etc. At the same time, page elements in the system pop-up box can also be annotated, thereby achieving compatible support for various types of application window modes in the system, and new window modes that appear in the future can also be expanded to support.

[0155] In one embodiment, the step of obtaining the target page element may include:

[0156] Step A, obtaining the application operation voice triggered by the user based on the voice application;

[0157] Step B: Process the application operation voice to obtain the target page element.

[0158] In this embodiment, according to the above description, the voice application can use the system auxiliary service and the OCR solution to obtain the page element information displayed on the application page of the initial application, such as Figure 1 As shown in process ①, users can semantically annotate some page elements according to page element information and business needs to facilitate voice control. Users can select elements on the page by voice to trigger the corresponding application operation voice.

[0159] The Framework extension module on the system side can receive the above application operation voice, parse the application operation voice, and obtain the target page element in the initial application specified by the user to be annotated.

[0160] Therefore, this embodiment supports users to select page elements to be marked in the target application through voice application. Regardless of whether the page elements are developed by native controls and the window type of the application, they can be marked through voice, so that users can control vehicle functions through voice.

[0161] Furthermore, in the above S10, “determining the initial application” may include:

[0162] S101, determining a target display screen from a plurality of initial display screens according to voice positioning information in voice operation information corresponding to a target page element;

[0163] S102: Determine the application corresponding to the application page displayed on the target display screen as the initial application.

[0164] It should be noted that in this embodiment, according to the above description, there are more and more scenarios of multi-screen display of a single system for in-vehicle applications, and multiple users can initiate voice operations on multiple display screens at the same time to perform semantic annotation of page elements. Therefore, in this embodiment, there can be at least one target display screen.

[0165] On this basis, after the application operation voice is parsed to obtain the target page element, the voice positioning information in the application operation voice can be extracted, and at least two target display screens can be determined according to the voice positioning information.

[0166] Then, the application corresponding to the application page displayed on the target display screen is determined as the initial application.

[0167] In this way, this embodiment can support the single-system multi-screen application scenario of the vehicle-mounted system. The voice side determines which display screen of the vehicle the driver and passengers have initiated voice operations on based on voice positioning for page element annotation, and can choose to annotate the page elements on the corresponding screen based on the voice positioning information.

[0168] In a specific embodiment, Figure 8 As shown, the marking method in this embodiment may specifically include:

[0169] First, the Framework extension module in this embodiment ( Figure 8 The process part shown in blue), this module runs on the system process system_server side. After receiving the interface call request from the voice application side, the module determines which screens of the system to annotate page elements based on the voice positioning information of the voice, and then determines whether the current screen focus is a system pop-up box on the corresponding screen. If it is not a system pop-up box, it means that it is an Activity type window. This embodiment will identify various types of windows, obtain all Activity windows through their different data structures, and finally all Activity windows call the annotation drawing interface in the main thread of the initial application in turn for drawing. If the current window type is a system pop-up box, directly find the WindowState window of the pop-up box type, call the annotation drawing interface of its root view in the pop-up box WindowState window, and enter the initial application side for annotation drawing.

[0170] After the system Framework side annotation process is completed, the main process of the initial application is entered to perform semantic annotation drawing. In this embodiment, a semantic annotation drawing module is added to the View drawing framework in the main process of the initial application. Figure 8 In the yellow part of the process, the module first finds the root view of all pages in the initial application main thread (i.e. Figure 8 ), and then find the page element to be annotated in all the root views in turn. If the element can be found, it means that the page element is developed using native controls. Then calculate the size of the canvas where the element is located, and use a recursive algorithm to compare and calculate the canvas size and the size of the semantic annotation pattern, find a canvas of the appropriate level for annotation drawing, and after finding the canvas, actively refresh the page layout to start the annotation pattern drawing process, draw the annotation pattern at the corresponding position, and finally display the corresponding annotation pattern in the application page.

[0171] If the semantic annotation module initially applied in the above process does not find the page element to be annotated by the voice in all the root views, it means that the page element is not developed using native controls, but is developed using a new hybrid development architecture, and the page element is of HTML5 type. This embodiment directly draws the semantic annotation on the canvas of this root view, calculates the coordinate position of the semantic annotation through the screen coordinates of the page element and the screen coordinates of this root view, and then draws the annotation pattern at the corresponding position of the page root view canvas according to this coordinate position.

[0172] In general, this embodiment is implemented on the system framework side, and does not require adaptation on the application side, saving the adaptation cost of the application. At the same time, this application supports any initial application to perform page element annotation, thereby improving the coverage of the solution; this embodiment supports application page element annotation in multiple window modes of the system, including full-screen mode, split-screen mode, and parallel window mode, all of which can use this application to annotate application page elements. At the same time, page elements in the system pop-up box can also be annotated to achieve compatible support for various types of application window modes in the system, and new window modes that appear later can also be expanded and supported; this embodiment supports single-system multi-screen application scenarios for vehicle-mounted systems, and the voice side can determine which vehicle-mounted screen the driver and passengers have initiated voice operations on for page element annotation based on sound source positioning, and then can choose to annotate page elements on the corresponding screen; in addition to supporting annotation on application pages developed with Android native controls, this embodiment also supports annotation of new popular pages developed using hybrid development technology, such as HTML5 type pages, so the coverage of all page element annotations of the application in this application is higher than that of existing annotation solutions.

[0173] Accordingly, the present application also provides a page marking device, such as Fig. 9 As shown,

[0174] A determination module 1001, used to determine an initial application;

[0175] The marking module 1002 is used to determine a target canvas from the associated canvases of the initial application according to the target page element, so as to mark the target page element on the target canvas.

[0176] Optionally, the second determining module 1002 is further configured to:

[0177] Get the root view of the initial application;

[0178] Based on the root view, a target canvas is determined from canvases associated with the initial application.

[0179] Optionally, the second determining module 1002 is further configured to:

[0180] If the target page element exists in the root view, a target canvas is determined from a plurality of canvases included in the root view.

[0181] Optionally, the second determining module 1002 is further configured to:

[0182] If the target page element does not exist in the root view, the root canvas of the webpage of the initial application is obtained, and the root canvas of the webpage is determined as the target canvas of the target page element.

[0183] Optionally, the second determining module 1002 is further configured to:

[0184] Determine an initial canvas where the target page element is located and size information of the initial canvas from a plurality of canvases included in the root view;

[0185] When the size information is greater than a preset size threshold, the initial canvas is determined as the target canvas.

[0186] Optionally, the second determining module 1002 is further configured to:

[0187] When the size information is less than or equal to a preset size threshold, determining a reference canvas of the initial canvas according to a hierarchical relationship between canvases included in the root view;

[0188] A target canvas is determined from the reference canvas based on size information of the reference canvas.

[0189] Optionally, the second determining module 1002 is further configured to:

[0190] A reference canvas whose size information is greater than a preset size threshold is determined as a target canvas.

[0191] Optionally, the second determining module 1002 is further configured to:

[0192] Determining second position information of a preset annotation in a corresponding direction according to first position information of the target page element in multiple directions of the target canvas;

[0193] According to the second position information, the preset annotation is drawn on the target canvas to annotate the target page element.

[0194] Optionally, the second determining module 1002 is further configured to:

[0195] Acquire the first screen coordinates of the target page element based on the display screen coordinate system, and acquire the second screen coordinates of the web page root canvas based on the display screen coordinate system;

[0196] Calculating preset marked screen coordinates according to the first screen coordinates and the second screen coordinates;

[0197] According to the screen coordinates, the preset annotation is drawn on the target canvas to annotate the target page element.

[0198] Optionally, the second determining module 1002 is further configured to:

[0199] Obtaining the window type of the initial application;

[0200] A preset interface corresponding to the window type is called according to the window type to obtain the root view of the initial application.

[0201] Optionally, the second determining module 1002 is further configured to:

[0202] In the case where the window type is a first window type, calling an application drawing interface to obtain a root view of the initial application; the first window type includes: an active window;

[0203] In the case where the window type is a second window type, the annotation drawing interface of the root view is called to obtain the root view of the initial application; the second window type includes: a pop-up window.

[0204] Optionally, the step of acquiring the target page element includes:

[0205] Get the user's application operation voice triggered by the voice application;

[0206] The application operation voice is processed to obtain a target page element.

[0207] Optionally, the first determining module 1001 is further configured to:

[0208] Determining a target display screen from a plurality of initial display screens according to voice positioning information in the voice operation information corresponding to the target page element;

[0209] An application corresponding to the application page displayed on the target display screen is determined as an initial application.

[0210] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.

[0211] Accordingly, the embodiment of the present application also provides a vehicle, which may be a fuel vehicle, a plug-in hybrid vehicle, or a new energy vehicle, etc., and the present application does not make specific limitations on this. Fig.10 As shown, Fig.10A schematic diagram of the structure of a vehicle provided in an embodiment of the present application. The vehicle 1100 includes a processor 1101 having one or more processing cores, a memory 1102 having one or more computer-readable storage media, and a computer program stored in the memory 1102 and executable on the processor. The processor 1101 is electrically connected to the memory 1102. It will be understood by those skilled in the art that the vehicle structure shown in the figure does not constitute a limitation on the vehicle, and may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0212] The processor 1101 is the control center of the vehicle 1100, and uses various interfaces and lines to connect various parts of the entire vehicle 1100. By running or loading software programs and / or units stored in the memory 1102, and calling data stored in the memory 1102, it executes various functions of the vehicle 1100 and processes data, thereby monitoring the vehicle 1100 as a whole. The processor 1101 can be a processor (Central Processing Unit, CPU), a graphics processing unit (graphics processing unit, GPU), a network processor (Network Processor, NP), etc., and can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application.

[0213] In the embodiment of the present application, the processor 1101 in the vehicle 1100 will load instructions corresponding to the processes of one or more application programs into the memory 1102 according to the following steps, and the processor 1101 will run the application programs stored in the memory 1102 to implement various functions, such as:

[0214] Identify initial applications;

[0215] According to the target page element, a target canvas is determined from the associated canvases of the initial application, so as to mark the target page element on the target canvas.

[0216] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.

[0217] Optional, such as Fig.10 As shown, the vehicle 1100 further includes: a touch screen 1103, a radio frequency circuit 1104, an audio circuit 1105, an input unit 1106, and a power supply 1107. The processor 1101 is electrically connected to the touch screen 1103, the radio frequency circuit 1104, the audio circuit 1105, the input unit 1106, and the power supply 1107, respectively. Those skilled in the art will appreciate that Fig.10The vehicle structure shown in the figure does not constitute a limitation on the vehicle, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0218] The touch display screen 1103 can be used to display a graphical user interface and receive operation instructions generated by the user acting on the graphical user interface. The touch display screen 1103 may include a display panel and a touch panel. Among them, the display panel can be used to display information input by the user or information provided to the user and various graphical user interfaces of the vehicle, which can be composed of graphics, text, icons, videos and any combination thereof. Optionally, the display panel can be configured in the form of a liquid crystal display (LCD, Liquid Crystal Display), an organic light-emitting diode (OLED, Organic Light-Emitting Diode) and the like. The touch panel can be used to collect the user's touch operation on or near it (such as the user uses any suitable object or accessory such as a finger, a stylus, etc. on the touch panel or near the touch panel), and generate corresponding operation instructions, and the operation instructions execute the corresponding program. Optionally, the touch panel may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the touch point coordinates, and then sends it to the processor 1101, and can receive the command sent by the processor 1101 and execute it. The touch panel can cover the display panel. When the touch panel detects a touch operation on or near it, it is transmitted to the processor 1101 to determine the type of touch event, and then the processor 1101 provides a corresponding visual output on the display panel according to the type of touch event. In an embodiment of the present application, the touch panel and the display panel can be integrated into the touch display screen 1103 to realize the input and output functions. However, in some embodiments, the touch panel and the touch panel can be used as two independent components to realize the input and output functions. That is, the touch display screen 1103 can also be used as a part of the input unit 1106 to realize the input function.

[0219] The RF circuit 1104 may be used to send and receive RF signals to establish wireless communication with network devices or other vehicles through wireless communication, and to send and receive signals with network devices or other vehicles.

[0220] The audio circuit 1105 can be used to provide an audio interface between the user and the vehicle through a speaker and a microphone. The audio circuit 1105 can transmit the electrical signal converted from the received audio data to the speaker, which is converted into a sound signal for output; on the other hand, the microphone converts the collected sound signal into an electrical signal, which is received by the audio circuit 1105 and converted into audio data, and then the audio data is output to the processor 1101 for processing, and then sent to another vehicle through the radio frequency circuit 1104, or the audio data is output to the memory 1102 for further processing. The audio circuit 1105 may also include an earplug jack to provide communication between an external headset and the vehicle.

[0221] The input unit 1106 may be used to receive input numbers, character information or user feature information (such as fingerprint, iris, facial information, etc.), and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0222] The power supply 1107 is used to supply power to various components of the vehicle 1100. Optionally, the power supply 1107 can be logically connected to the processor 1101 through a power management device, so that the power management device can manage charging, discharging, power consumption and other functions. The power supply 1107 can also include one or more DC or AC power supplies, recharging devices, power failure detection circuits, power converters or inverters, power status indicators and other arbitrary components.

[0223] although Fig.10 Not shown, the vehicle 1100 may also include a camera, a sensor, a wireless fidelity module, a Bluetooth module, etc., which will not be described in detail here.

[0224] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0225] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0226] To this end, an embodiment of the present application provides a computer-readable storage medium, in which a plurality of computer programs are stored. The computer program can be loaded by a processor to execute any one of the page marking methods provided in the embodiments of the present application. The computer program can execute the steps of the following page marking method:

[0227] Identify initial applications;

[0228] According to the target page element, a target canvas is determined from the associated canvases of the initial application, so as to mark the target page element on the target canvas.

[0229] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.

[0230] The computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0231] Since the computer program stored in the computer-readable storage medium can execute any of the page marking methods provided in the embodiments of the present application, the beneficial effects that can be achieved by any of the page marking methods provided in the embodiments of the present application can be achieved. Please refer to the previous embodiments for details and will not be repeated here.

[0232] In the above-mentioned page annotation device, vehicle, computer-readable storage medium and computer program product, the description of each embodiment has its own emphasis. For the part not described in detail in a certain embodiment, reference can be made to the relevant description of other embodiments. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process and beneficial effects of the above-mentioned page annotation device, vehicle, computer-readable storage medium, computer program product and its corresponding units can refer to the description of the page annotation method in the above embodiment, and will not be repeated here.

[0233] The above are only preferred embodiments of the present application and do not constitute any form of limitation to the present application. However, any simple modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of the present application without departing from the content of the technical solution of the present application are still within the scope of the technical solution of the present application.

Claims

1. A page marking method, characterized in that: The method comprises: Identify initial applications; According to the target page element, a target canvas is determined from the associated canvases of the initial application, so as to mark the target page element on the target canvas.

2. The page marking method according to claim 1, characterized in that: The determining of the target canvas from the associated canvases of the initial application includes: Get the root view of the initial application; Based on the root view, a target canvas is determined from canvases associated with the initial application.

3. The page marking method according to claim 2, characterized in that: The step of determining the target canvas from the associated canvases of the initial application based on the root view includes: If the target page element exists in the root view, a target canvas is determined from a plurality of canvases included in the root view.

4. The page marking method according to claim 2, characterized in that: The step of determining the target canvas from the associated canvases of the initial application based on the root view includes: If the target page element does not exist in the root view, the root canvas of the webpage of the initial application is obtained, and the root canvas of the webpage is determined as the target canvas of the target page element.

5. The page marking method according to claim 3, characterized in that: The determining of the target canvas from the multiple associated canvases included in the root view comprises: Determine an initial canvas where the target page element is located and size information of the initial canvas from a plurality of canvases included in the root view; When the size information is greater than a preset size threshold, the initial canvas is determined as the target canvas.

6. The page marking method according to claim 5, characterized in that: The method further comprises: When the size information is less than or equal to a preset size threshold, determining a reference canvas of the initial canvas according to a hierarchical relationship between canvases included in the root view; A target canvas is determined from the reference canvas based on size information of the reference canvas.

7. The page marking method according to claim 6, characterized in that: The determining the target canvas from the reference canvas based on the size information of the reference canvas includes: A reference canvas whose size information is greater than a preset size threshold is determined as a target canvas.

8. The page marking method according to claim 3, characterized in that: The marking of the target page elements on the target canvas includes: Determining second position information of a preset annotation in a corresponding direction according to first position information of the target page element in multiple directions of the target canvas; According to the second position information, the preset annotation is drawn on the target canvas to annotate the target page element.

9. The page marking method according to claim 4, characterized in that: The marking of the target page element on the target canvas includes: Acquire the first screen coordinates of the target page element based on the display screen coordinate system, and acquire the second screen coordinates of the web page root canvas based on the display screen coordinate system; Calculating preset marked screen coordinates according to the first screen coordinates and the second screen coordinates; According to the screen coordinates, the preset annotation is drawn on the target canvas to annotate the target page element.

10. The page marking method according to claim 2, characterized in that: The obtaining the root view of the initial application includes: Obtaining the window type of the initial application; A preset interface corresponding to the window type is called according to the window type to obtain the root view of the initial application.

11. The page marking method according to claim 10, characterized in that: The step of calling a preset interface corresponding to the window type according to the window type to obtain the root view of the initial application includes: In the case where the window type is a first window type, calling an application drawing interface to obtain a root view of the initial application; the first window type includes: an active window; In the case where the window type is a second window type, the annotation drawing interface of the root view is called to obtain the root view of the initial application; the second window type includes: a pop-up window.

12. The page marking method according to claim 1, characterized in that: The target page element is obtained by the following steps: Get the user's application operation voice triggered by the voice application; The application operation voice is processed to obtain a target page element.

13. The page marking method according to any one of claims 1 to 12, characterized in that: Determining the initial application includes: Determining a target display screen from a plurality of initial display screens according to voice positioning information in the voice operation information corresponding to the target page element; An application corresponding to the application page displayed on the target display screen is determined as an initial application.

14. A page marking device, characterized in that: The page marking device comprises: A first determination module, used to determine an initial application; The second determination module is used to determine a target canvas from the associated canvases of the initial application according to the target page element, so as to mark the target page element on the target canvas.

15. A vehicle, characterized in that: The method comprises a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the method according to any one of claims 1 to 13.

16. A computer-readable storage medium, characterized in that: It comprises a computer program, which, when running on a vehicle, is used to cause the vehicle to execute the steps of the method according to any one of claims 1 to 13.

17. A computer program product, characterized in that It includes a computer program, which is stored in a computer-readable storage medium; when a processor of an electronic device reads the computer program from the computer-readable storage medium, the processor executes the computer program, so that the electronic device performs the steps of any method described in claims 1 to 13.

Images