Page turning method, electronic device and storage medium

Abstract

The present application is used for providing a page turning method, an electronic device and a storage medium. The page turning method is used for an electronic device. The page turning method comprises: displaying an application interface of a first application, the application interface comprising a first display area and a second display area, and the first display area and the second display area partially overlapping or not overlapping at all; in response to determining that a gaze point of a user relative to the application interface moves from the first display area to the second display area, determining page turning waiting time of the application interface of the first application; and in response to determining that the gaze point of the user moves from the first display area to the second display area, after elapsing of the page turning waiting time, and in response to determining that the gaze point of the user moves from the second display area to the first display area, executing a page turning operation for the application interface of the first application. The present method enables accurate and automatic page turning, thereby improving the reading experience of users.

Description

A page-turning method, an electronic device, and a storage medium

[0001] This application claims priority to Chinese Patent Application No. 202410808296.3, filed on June 20, 2024, entitled "A Page Turning Method, Electronic Device and Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of software technology, and more particularly to a page-turning method, electronic device, and storage medium. Background Technology

[0003] With the rapid development of network technology, smart terminal devices such as smartphones and tablets are becoming increasingly popular, bringing great convenience to people's lives, studies, and work. In recent years, digital reading has become very widespread, and most reading software, such as reading applications (APPs), browser apps, and news feed apps, currently uses manual page-turning interaction methods, such as swiping or tapping to turn pages. This manual page-turning method requires users to use their hands frequently for extended periods, which can easily lead to fatigue and requires single-handed operation. When users find it inconvenient to use their hands or when the device screen is too large for convenient operation, the user experience is diminished.

[0004] In addition, some reading software offers automatic page-turning interaction methods, such as vertical scrolling. Vertical scrolling scrolls the page up or down at a uniform speed set by the user. However, since the scrolling speed is fixed, but the content density and difficulty of the page vary—meaning the user's reading speed varies—the page scrolling speed and the user's reading speed cannot be well matched, resulting in a poor reading experience with vertical scrolling. Summary of the Invention

[0005] Some embodiments of this application provide a page-turning method, an electronic device, and a storage medium. The following describes this application from multiple aspects, and the embodiments and beneficial effects of the following aspects can be referred to each other.

[0006] In a first aspect, embodiments of this application provide a page-turning method for an electronic device, the method comprising:

[0007] Display the application interface of the first application, which includes a first display area and a second display area, and the first display area and the second display area may partially overlap or not overlap at all.

[0008] In response to determining that the user's gaze point relative to the application interface moves from the first display area to the second display area, the page-turning wait time of the first application's application interface is determined;

[0009] In response to determining that the user's gaze has moved from the first display area to the second display area, after a page-turning waiting time, and in response to determining that the user's gaze has moved from the second display area to the first display area, a page-turning operation is performed on the application interface of the first application.

[0010] According to the embodiments of this application, the electronic device can divide the application interface into an upper area (as an example of a first display area) and a lower area (as an example of a second display area), and can detect changes in the user's gaze point based on eye-tracking technology. After determining that the user's gaze point has moved from the upper area to the lower area, the electronic device can estimate the remaining reading time required for the user to finish reading the page content in the lower area as a page-turning waiting time, and enter a waiting time window. After this waiting time window, when it is determined that the user's gaze point has moved from the lower area to the upper area, the electronic device can determine that it has detected the user's page-turning intention, and then execute an automatic page-turning operation. In this way, when the user decides to turn the page after reading the page content in the lower area, they only need to move their gaze point up to the upper area, and the page will turn automatically without any mechanical movement of the user's hand, greatly reducing fatigue and improving the user's reading experience. Furthermore, the electronic device identifies the user's reading progress and page-turning intention on the current page by detecting changes in the user's gaze point, with high accuracy, good fault tolerance, and strong applicability.

[0011] Furthermore, the electronic device defines the overlapping area between the upper and lower regions as a transition zone. When the user's gaze moves from the upper grid (as an example of the upper region excluding the transition zone) to the transition zone, no change in the user's gaze location is detected. Similarly, when the user's gaze moves from the lower grid (as an example of the lower region excluding the transition zone) to the transition zone, no change in the user's gaze location is detected. The size of this transition zone affects the sensitivity of the gaze switching between the upper and lower regions; a larger transition zone results in lower sensitivity, while a smaller transition zone results in higher sensitivity. Therefore, by setting an intermediate transition zone, the electronic device can adjust the sensitivity of the gaze switching between the upper and lower regions, avoiding frequent detection of gaze location changes when the user's gaze jumps in the middle region, thus preventing intention recognition errors.

[0012] In some embodiments, the method further includes:

[0013] In response to determining that the user's gaze point has moved from the first display area to the second display area, after a page-turning waiting time, a page-turning prompt message is displayed in the application interface of the first application.

[0014] The page-turning prompt is used to prompt the user to move their gaze from the second display area to the first display area in order to turn the page.

[0015] According to the embodiments of this application, after determining that the user's gaze has moved from the upper area to the lower area, and after the waiting time window, the electronic device can determine that the user has finished reading the content of the current page (i.e., read to the bottom of the page). At this time, the electronic device can provide a page-turning prompt, guiding the user to turn the page, thereby giving the user a clear psychological cue that their intention has been accurately recognized, further enhancing the user's reading experience.

[0016] In some implementations, determining that the user's gaze point relative to the application interface has moved from a first display area to a second display area includes:

[0017] The display area where the user's gaze point is currently located is determined as the second display area, and the display area where the user's gaze point was previously located is determined as the first display area;

[0018] The process of determining whether the user's gaze point has moved from the second display area to the first display area includes:

[0019] The display area where the user's gaze point is currently located is determined as the first display area, and the display area where the user's gaze point was previously located is determined as the second display area;

[0020] The display area where the user's gaze point is currently located and the display area where it was previously located are determined based on at least one frame of the user's facial image.

[0021] According to the embodiments of this application, an electronic device can use one or more frames of facial images to determine the coordinates of the user's gaze point, thereby determining the specific display area where the user's gaze point is concentrated on the application interface. This multi-frame smoothing processing method improves the accuracy of determining the display area where the user's gaze point is located, effectively suppresses gaze point jumps, and further improves the accuracy of reading progress and page-turning intention recognition.

[0022] In some implementations, determining the page-turning wait time for the application interface of the first application includes:

[0023] Determine the user's page reading speed within the first display area;

[0024] Estimate the user's remaining reading time in the second display area based on page reading speed;

[0025] The page-turning waiting time is determined based on the remaining reading time.

[0026] According to the embodiments of this application, the electronic device dynamically calculates the user's reading speed in the upper area and estimates the reading time in the lower area based on this speed, thereby transforming the judgment of reading progress into a judgment of reading time. In this way, the electronic device does not need to precisely identify which word or line the user's gaze falls on on the page, providing favorable conditions for using low-power cameras for eye tracking. This ensures that there is little or no impact on the battery life of the electronic device during long-term reading, encouraging users to use it for extended periods and reducing user stress, distraction, and anxiety during prolonged use.

[0027] In some implementations, determining the user's page reading speed within the first display area includes:

[0028] Obtain the first cumulative time that the user's gaze has lingered within the first display area;

[0029] The page reading speed is determined based on the first cumulative time and the amount of page information within the first display area.

[0030] In some implementations, the remaining reading time of the user in the second display area is estimated based on the page reading speed, including:

[0031] When the page reading speed is within the preset speed range, the estimated reading time for the user in the second display area is determined based on the amount of page information and the page reading speed in the second display area.

[0032] When the page reading speed is outside the preset speed range, the estimated reading time of the user in the second display area is determined based on the amount of page information in the second display area and the preset reading speed or the user's historical reading speed.

[0033] The remaining reading time is determined based on the estimated reading time and the second cumulative time that the user's gaze has lingered in the second display area.

[0034] According to the embodiments of this application, the electronic device dynamically calculates the user's reading speed in the upper region of the current page based on the amount of page information in the upper region and the cumulative time the user's gaze lingers in the upper region. Then, based on the calculated reading speed, it estimates the expected time for the user to finish reading the content in the lower region, as well as the remaining reading time. In this way, the electronic device can accurately determine the user's reading progress based on the user's reading time, solving the problem that the accuracy limitations of low-power camera technology prevent accurate identification of the user's gaze position and the inability to determine the user's reading progress based on the precise location of the user's gaze.

[0035] Meanwhile, by statistically analyzing the cumulative time users spend reading the upper half of the screen and the cumulative time users spend reading the lower half of the screen, the waiting time window for detecting users' page-turning intentions can be dynamically determined, which can further reduce the impact of the problem of users' gaze points changing in the middle area on the accuracy of page-turning intention recognition.

[0036] Furthermore, by determining whether the calculated reading speed is within the normal range, or by combining the user's historical reading speed to determine whether there is a large error, the electronic device discards data that does not fall within the normal range or has a large error, and uses the preset reading speed or the user's historical reading speed to estimate the reading time, which can further ensure the accuracy of identifying the user's reading progress.

[0037] In some implementations, the page-turning waiting time is determined based on the remaining reading time, including:

[0038] When the remaining reading time is within the preset time range, the page-turning waiting time is determined as the remaining reading time;

[0039] When the remaining reading time is less than the minimum of the preset time range, the page-turning waiting time is set as the first preset time.

[0040] When the remaining reading time is greater than the maximum value of the preset time range, the page-turning waiting time is set to the second preset time.

[0041] According to the embodiments of this application, the electronic device determines whether the estimated remaining reading time falls within a reasonable time range, discards data that does not fall within a reasonable time range, and uses a preset time as the page-turning waiting time. This can avoid turning pages too quickly (or prompting the user to turn pages too quickly, causing accidental page turning) or not turning pages for too long (or not prompting the user to turn pages for too long, causing the user to wait too long), so that the automatic page-turning time is within a reasonable time range, further improving the user's reading experience.

[0042] In some implementations, performing a page-turning operation on the application interface of the first application includes:

[0043] In response to determining that the user's gaze point has moved from the second display area to the first display area, after a third preset time, a page-turning operation is performed on the application interface of the first application.

[0044] In some embodiments, the method further includes:

[0045] Within a third preset time period, in response to determining that the user's gaze point has moved from the first display area to the second display area, the page-turning operation for the application interface of the first application is abandoned.

[0046] According to the embodiments of this application, after determining that the user's gaze point has moved from the lower area to the upper area, the electronic device enters a delayed execution time window. If no further switching of the user's gaze point between the upper and lower areas occurs within this delayed execution time window, the user's intention to turn the page by moving their gaze point upward is considered genuine, and the electronic device performs the page-turning operation. If the user's gaze point moves back to the lower area within this delayed execution time window, the previous upward movement of the user's gaze point is considered a mistake and is suppressed. This delayed execution time window avoids the problem of users mistakenly turning the page by looking at the upper area before finishing reading the content in the lower area, as well as preventing accidental page turning due to gaze point jumps caused by algorithm recognition errors.

[0047] Secondly, embodiments of this application provide a page-turning method for an electronic device, the method comprising:

[0048] The application interface of the second application is displayed. The application interface includes a first display area and a second display area, which may partially overlap or not overlap at all.

[0049] In response to determining that the user's gaze point relative to the application interface has moved from the first display area to the second display area, and after a fourth preset time, the page scrolling speed of the second application interface is adjusted from the first scrolling speed to the second scrolling speed.

[0050] According to the embodiments of this application, the electronic device can divide the application interface into an upper region and a lower region (as examples of a first display region and a second display region), and can detect changes in the user's gaze point based on eye-tracking technology. If the user habitually gazes at the upper half of the application interface, and it is determined that the user's gaze point moves from the upper region to the lower region, it can be determined that the page scrolling speed is slower than the user's reading speed, and the electronic device can increase the page scrolling speed. If the user habitually gazes at the lower half of the application interface, and it is determined that the user's gaze point moves from the lower region to the upper region, it can be determined that the page scrolling speed is faster than the user's reading speed, and the electronic device can decrease the page scrolling speed. In this way, the electronic device can dynamically adjust the page scrolling speed according to the user's reading speed, matching the page scrolling speed with the user's reading habits and reading speed, without requiring manual adjustment by the user, greatly improving the user's reading experience.

[0051] Furthermore, the electronic device defines the overlapping area between the upper and lower regions as a transition zone. When the user's gaze moves from the upper grid (as an example of the upper region excluding the transition zone) to the transition zone, no change in the user's gaze location is detected. Similarly, when the user's gaze moves from the lower grid (as an example of the lower region excluding the transition zone) to the transition zone, no change in the user's gaze location is detected. The size of this transition zone affects the sensitivity of the gaze switching between the upper and lower regions; a larger transition zone results in lower sensitivity, while a smaller transition zone results in higher sensitivity. Therefore, by setting an intermediate transition zone, the electronic device can adjust the sensitivity of the gaze switching between the upper and lower regions, avoiding frequent detection of gaze location changes when the user's gaze jumps in the middle region, thus preventing intention recognition errors.

[0052] In some embodiments, the method further includes:

[0053] Determine the adjustment coefficient for each user;

[0054] The second rolling speed is determined based on the adjustment factor.

[0055] In some embodiments, the method further includes:

[0056] In response to determining that the user's gaze point has moved from the second display area to the first display area, and after a fifth preset time, the page scrolling speed of the application interface of the second application is adjusted from the second scrolling speed to the first scrolling speed.

[0057] According to the embodiments of this application, if a user habitually focuses on the upper half of the application interface, and it is determined that the user's gaze point has moved from the lower area to the upper area, it can be determined that the page scrolling speed is faster than the user's reading speed. In this case, the electronic device can restore the default scrolling speed. Conversely, if a user habitually focuses on the lower half of the application interface, and it is determined that the user's gaze point has moved from the upper area to the lower area, it can be determined that the page scrolling speed is slower than the user's reading speed. In this case, the electronic device can also restore the default scrolling speed. In this way, the electronic device can dynamically adjust the page scrolling speed according to the user's reading speed, making the page scrolling speed match the user's reading habits and reading speed, without requiring manual adjustment by the user, greatly improving the user's reading experience.

[0058] Thirdly, embodiments of this application provide an electronic device, including: a memory for storing instructions executable by one or more processors of the electronic device; and a processor, which, when executing the instructions in the memory, causes the electronic device to perform the page-turning method provided in any embodiment of the first or second aspect of this application. The beneficial effects achievable through this third aspect can be referred to in the context of the beneficial effects of any embodiment of the first or second aspect of this application, and will not be repeated here.

[0059] Fourthly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the page-turning method provided by any embodiment of the first or second aspect of this application. The beneficial effects achievable through this fourth aspect can be found in the beneficial effects of any embodiment of the first or second aspect of this application, and will not be repeated here. Attached Figure Description

[0060] Figure 1 is a schematic diagram of an application scenario provided by an implementation example of this application;

[0061] Figure 2a is a schematic diagram of the settings interface for the air-sliding screen function provided in some embodiments;

[0062] Figure 2b is a schematic diagram of the interactive method of air gesture page turning provided in some embodiments;

[0063] Figures 2c and 2d are schematic diagrams of the settings interface for setting the scrolling speed provided in some embodiments;

[0064] Figure 3a is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0065] Figure 3b is a software structure block diagram of an electronic device provided in an embodiment of this application;

[0066] Figure 3c is a schematic diagram of the system architecture of an electronic device provided in an embodiment of this application;

[0067] Figure 4 is a flowchart of a page-turning method provided in an embodiment of this application;

[0068] Figure 5a is a schematic diagram of the application interface of a reading APP provided in an embodiment of this application;

[0069] Figure 5b is a schematic diagram of a transition region provided in an embodiment of this application;

[0070] Figure 5c is a schematic diagram of the application interface of a reading app provided in another embodiment of this application;

[0071] Figure 5d is a schematic diagram of the application interface of a reading app provided in another embodiment of this application;

[0072] Figure 5e is a schematic diagram of the application interface of a reading app provided in another embodiment of this application;

[0073] Figure 6 is a flowchart of a page-turning method provided in a specific embodiment of this application;

[0074] Figure 7a is a schematic diagram of gaze jump provided in an embodiment of this application;

[0075] Figure 7b is a schematic diagram of gaze jump provided in another embodiment of this application;

[0076] Figure 8 is a flowchart of the process for triggering a fence event provided in a specific embodiment of this application;

[0077] Figure 9 is a schematic diagram showing the change of the display area where the user's gaze point is located according to an embodiment of this application;

[0078] Figure 10 is a flowchart of the process of opening a new page according to an embodiment of this application;

[0079] Figure 11 is a flowchart of the process when a user switches from gazing at the lower region to gazing at the upper region according to an embodiment of this application;

[0080] Figure 12 is a flowchart of the process when a user switches from gazing at the upper region to gazing at the lower region according to an embodiment of this application;

[0081] Figure 13 is a flowchart of a page-turning method provided in another embodiment of this application;

[0082] Figure 14a is a schematic diagram of a left-right page turning process provided in an embodiment of this application;

[0083] Figure 14b is a schematic diagram of the page turning process of the upper and lower half screens provided in an embodiment of this application;

[0084] Figure 15 is a schematic diagram of switching a mobile phone from portrait to landscape mode according to an embodiment of this application;

[0085] Figure 16 is a flowchart of a page-turning method provided in another specific embodiment of this application;

[0086] Figure 17 is a flowchart of a page-turning method provided in another embodiment of this application;

[0087] Figure 18 is a flowchart of a page-turning method provided in another specific embodiment of this application;

[0088] Figure 19 is a schematic diagram of accelerated scrolling page turning provided in an embodiment of this application;

[0089] Figure 20 is a flowchart of a page-turning method provided in another embodiment of this application;

[0090] Figure 21 is a flowchart of a page-turning method provided in another specific embodiment of this application;

[0091] Figure 22 is a schematic diagram of decelerated scrolling page turning provided in one embodiment of this application;

[0092] Figure 23 shows a block diagram of an electronic device provided in one embodiment of this application;

[0093] Figure 24 shows a block diagram of a System on Chip (SOC) provided in one embodiment of this application. Detailed Implementation

[0094] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0095] The page-turning method provided in this application embodiment can be applied to scenarios where users read page content in the application interface of reading software on electronic devices, controlling the page-turning process of the reading software application interface. This is especially useful in scenarios where it is inconvenient for users to operate the page-turning function with their hands, such as when the user is lying down, has dirty hands, or is wearing gloves.

[0096] Referring to Figure 1 in the specification, Figure 1 illustrates an application scenario provided by an embodiment of this application. As shown in Figure 1, in this scenario, user 101 can read the page content in the application interface 102 of the reading software on the electronic device at a certain speed. After the user finishes reading the current page, they need to perform a page-turning operation on the application interface 102 of the reading software. The reading software can be various types of apps that provide information to the user, such as including but not limited to reading apps, browser apps, and news feed apps. This embodiment of the application does not impose specific limitations on this.

[0097] In some embodiments, users can configure whether to enable the air swipe screen function in the settings interface of the electronic device. Referring to Figure 2a of the specification, Figure 2a shows a schematic diagram of the settings interface for the air swipe screen function provided in some embodiments. As shown in Figure 2a, the settings interface 201 for the air swipe screen function may include a control 202 for enabling the air swipe screen function. The electronic device can enable the air swipe screen function in response to a user's click operation on the control 202.

[0098] When the air swipe screen function is enabled, the electronic device can use air gestures to turn pages. Referring to Figure 2b of the specification, Figure 2b shows a schematic diagram of the air gesture page-turning interaction method provided in some embodiments. As shown in Figure 2b, when the air swipe screen function is enabled, the electronic device can recognize the user's gesture information based on machine vision technology. When a user gesture indicating page turning is detected (the downward waving gesture 203 shown in Figure 2b), the page-turning operation is executed on the application interface 204 of the reading software.

[0099] While this page-turning method eliminates the need for finger touches on the screen, solving the problem of inconvenient hand gestures, it still requires frequent and prolonged hand gestures, leading to fatigue and requiring one-handed operation. It doesn't truly liberate the user's hands. Furthermore, this method has relatively low recognition speed and accuracy, with occasional recognition failures, a complex interaction process, and high power consumption.

[0100] In some embodiments, the electronic device can use a scrolling page-turning interaction method to achieve automatic page turning. Specifically, the user can set the scrolling speed in the settings interface of the electronic device, and the electronic device can obtain the scrolling speed set by the user accordingly. Referring to Figures 2c and 2d of the specification, Figures 2c and 2d show schematic diagrams of the settings interface for setting the scrolling speed provided in some embodiments. As shown in Figure 2c, the electronic device can provide the user with a settings interface 205 for setting the scrolling speed and obtain the scrolling speed set by the user based on settings interface 205. Alternatively, as shown in Figure 2d, the electronic device can provide the user with a settings interface 206 for setting the scrolling speed and obtain the scrolling speed set by the user based on settings interface 206.

[0101] Subsequently, the electronic device can control the page to scroll down or up at a constant speed according to the user-set scrolling speed. Since the scrolling speed is fixed, but the content density and difficulty of the page vary, the user's reading speed also varies. Therefore, the page scrolling speed and the user's reading speed cannot be well matched, resulting in a poor reading experience under the scrolling page-turning method. Furthermore, the scrolling page-turning interaction method is mainly suitable for vertical scrolling page-turning modes. In simulated page-turning and horizontal covering page-turning modes, there are issues with premature or delayed page turning, leading to a poor user experience.

[0102] In some embodiments, the electronic device can collect user facial image information, determine the direction of the user's gaze based on the collected facial information, obtain the coordinates of the user's gaze falling on the display screen based on the direction of the user's gaze, and determine the display area where the user's gaze is located based on the coordinates of the user's gaze falling on the display screen. The electronic device can compare the display area where the user's current gaze is located with the display area where the user's previous gaze was located. If the display area where the user's current gaze is located is different from the display area where the user's previous gaze was located, the content displayed in the display area where the user's gaze was located is refreshed to be the next page of the page content displayed in the display area where the user's current gaze is located. This page includes the page displayed in the e-reader's display area, and the next page content includes the content of the next page displayed in the e-reader's display area. This page-turning method is mainly suitable for page-turning modes that divide the display screen into two parts and control the page-turning of the two parts of the display screen separately. It is not suitable for other page-turning modes, and there is a problem of gaze jump between the two display areas, which can easily lead to accidental page-turning and a poor user experience.

[0103] Therefore, this application provides a page-turning method to achieve automatic page turning and improve the user's reading experience.

[0104] According to one embodiment of this application, an electronic device can divide the application interface into an upper area (as an example of a first display area) and a lower area (as an example of a second display area), and can detect changes in the user's gaze point based on eye-tracking technology. After determining that the user's gaze point has moved from the upper area to the lower area, the electronic device can estimate the remaining reading time required for the user to finish reading the page content in the lower area as a page-turning waiting time, and enter a waiting time window. After this waiting time window, when it is determined that the user's gaze point has moved from the lower area to the upper area, the electronic device can determine that it has detected the user's page-turning intention, and then execute an automatic page-turning operation. In this way, when the user decides to turn the page after reading the page content in the lower area, they only need to move their gaze point up to the upper area, and the page will turn automatically without any mechanical movement of the user's hand, greatly reducing fatigue and improving the user's reading experience. Furthermore, the electronic device identifies the user's reading progress and page-turning intention on the current page by detecting changes in the user's gaze point, with high accuracy, good fault tolerance, and strong applicability.

[0105] Furthermore, the electronic device defines the overlapping area between the upper and lower regions as a transition zone. When the user's gaze moves from the upper grid (as an example of the upper region excluding the transition zone) to the transition zone, no change in the user's gaze location is detected. Similarly, when the user's gaze moves from the lower grid (as an example of the lower region excluding the transition zone) to the transition zone, no change in the user's gaze location is detected. The size of this transition zone affects the sensitivity of the gaze switching between the upper and lower regions; a larger transition zone results in lower sensitivity, while a smaller transition zone results in higher sensitivity. Therefore, by setting an intermediate transition zone, the electronic device can adjust the sensitivity of the gaze switching between the upper and lower regions, avoiding frequent detection of gaze location changes when the user's gaze jumps in the middle region, thus preventing intention recognition errors.

[0106] According to another embodiment of this application, after determining that the user's gaze has moved from the upper area to the lower area, and after the waiting time window, the electronic device can determine that the user has finished reading the content of the current page (i.e., read to the bottom of the page). At this time, the electronic device can provide a page-turning prompt, guiding the user to turn the page, thereby giving the user a clear psychological cue that their intention has been accurately recognized, further enhancing the user's reading experience.

[0107] According to another embodiment of this application, the electronic device can divide the application interface into an upper region and a lower region (as examples of a first display region and a second display region), and can detect changes in the user's gaze point based on eye-tracking technology. If the user habitually gazes at the upper half of the application interface, and it is determined that the user's gaze point moves from the upper region to the lower region, it can be determined that the page scrolling speed is slower than the user's reading speed, and the electronic device can increase the page scrolling speed. If the user habitually gazes at the lower half of the application interface, and it is determined that the user's gaze point moves from the lower region to the upper region, it can be determined that the page scrolling speed is faster than the user's reading speed, and the electronic device can decrease the page scrolling speed. In this way, the electronic device can dynamically adjust the page scrolling speed according to the user's reading speed, matching the page scrolling speed with the user's reading habits and reading speed, eliminating the need for manual adjustment by the user and greatly improving the user's reading experience.

[0108] In the embodiments described above, the electronic device can be a single screen, a foldable screen, a curved screen, etc. A foldable screen can have a structure with two physical screens or a structure with only one physical screen; this is not a limitation. In other embodiments of this application, the page-turning method can also be applied to electronic devices with three or more screens; this is not a limitation.

[0109] In the embodiments described above, the application interface is divided according to the vertical area division method in the portrait mode of the electronic device. In other embodiments of this application, it can also be divided into left and right areas in the landscape mode of the electronic device. In the left and right area division method in the landscape mode of the electronic device, the left part of the display interface is the first display area, and the right part of the display interface is the second display area.

[0110] The embodiments of this application do not limit the form of the electronic device. The electronic device can be a mobile phone, tablet, laptop, smart screen, vehicle equipment (e.g., car infotainment system, car navigation system) or other electronic devices with a display screen, and is not intended to be limited here.

[0111] The page-turning method of this application embodiment is described below in conjunction with the specific structure of the electronic device.

[0112] Figure 3a shows a schematic diagram of the structure of an electronic device 300 provided in one embodiment of this application. The electronic device 300 may include a processor 310, an external memory interface 320, an internal memory 321, a Universal Serial Bus (USB) interface 330, a charging management module 340, a power management module 341, a battery 342, antenna 1, antenna 2, a mobile communication module 350, a wireless communication module 360, an audio module 370, a speaker 370A, a receiver 370B, a microphone 370C, a headphone jack 370D, a sensor module 380, buttons 390, a motor 391, an indicator 392, a camera 393, a display screen 394, and a Subscriber Identification Module (SIM) card interface 395, etc. The sensor module 380 may include a pressure sensor 380A, a gyroscope sensor 380B, a barometric pressure sensor 380C, a magnetic sensor 380D, an accelerometer sensor 380E, a distance sensor 380F, a proximity light sensor 380G, a fingerprint sensor 380H, a temperature sensor 380J, a touch sensor 380K, an ambient light sensor 380L, a bone conduction sensor 380M, etc.

[0113] Processor 310 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processor (NPU). Different processing units may be independent devices or integrated into one or more processors. For example, processor 310 may be used to execute various steps of the page-turning method in the embodiments of this application.

[0114] The processor 310 can generate operation control signals based on the instruction opcode and timing signals to control the instruction fetching and execution.

[0115] The processor 310 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 310 is a cache memory. This memory can store instructions or data that the processor 310 has just used or that are used repeatedly. If the processor 310 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 310, and thus improves the efficiency of the system.

[0116] In some embodiments, the processor 310 can detect changes in the user's gaze point based on eye-tracking technology. After determining that the user's gaze point has moved from the upper region to the lower region, the remaining reading time required for the user to finish reading the page content in the lower region can be estimated as a page-turning waiting time, and a waiting time window is entered. After this waiting time window, when it is determined that the user's gaze point has moved from the lower region to the upper region again, the user's page-turning intention can be detected, and an automatic page-turning operation can be performed. In this way, when the user decides to turn the page after reading the page content in the lower region, they only need to move their gaze point up to the upper region, and the page will turn automatically without any mechanical movement of the user's hand, greatly reducing fatigue and improving the user's reading experience.

[0117] In some embodiments, the processor 310 can detect changes in the user's gaze point based on eye-tracking technology. If the user typically gazes at the upper half of the application interface, and it is determined that the user's gaze point has moved from the upper area to the lower area, it can be determined that the page scrolling speed is slower than the user's reading speed, and the page scrolling speed can be increased. Conversely, if the user typically gazes at the lower half of the application interface, and it is determined that the user's gaze point has moved from the lower area to the upper area, it can be determined that the page scrolling speed is faster than the user's reading speed, and the page scrolling speed can be decreased. In this way, the page scrolling speed can be dynamically adjusted according to the user's reading speed, matching the page scrolling speed with the user's reading habits and reading speed, eliminating the need for manual adjustment by the user and greatly improving the user's reading experience.

[0118] In some embodiments, the processor 310 may include one or more interfaces. These interfaces may include an Inter-Integrated Circuit (I2C) interface, an Inter-Integrated Circuit Sound (I2S) interface, a Pulse Code Modulation (PCM) interface, a Universal Asynchronous Receiver / Transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI) interface, a General-Purpose Input / Output (GPIO) interface, and a Subscriber Identity Module (SIM) interface.

[0119] The MIPI interface can be used to connect the processor 310 to peripheral devices such as the display screen 394 and the camera 393. The MIPI interface includes a Camera Serial Interface (CSI) and a Display Serial Interface (DSI). In some embodiments, the processor 310 and the camera 393 communicate via the CSI interface to enable the electronic device 300 to capture images. The processor 310 and the display screen 394 communicate via the DSI interface to enable the electronic device 300 to display images.

[0120] The GPIO interface can be configured via software. It can be configured as a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 310 to a camera 393, a display screen 394, a wireless communication module 360, an audio module 370, a sensor module 380, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0121] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the electronic device 300. In other embodiments of this application, the electronic device 300 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0122] Electronic device 300 implements display functions through a GPU, a display screen 394, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 394 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 310 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0123] Display screen 394 is used to display images, videos, etc. Display screen 394 includes a display panel. The display panel may be a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), an Active-Matrix Organic Light-Emitting Diode (AMOLED), a Flexible Light-Emitting Diode (FLED), a Minied, MicroLED, Micro-OLED, or Quantum Dot Light-Emitting Diode (QLED), etc. In some embodiments, electronic device 300 may include one or N displays 394, where N is a positive integer greater than 1.

[0124] Electronic device 300 can achieve shooting function through ISP, camera 393, video codec, GPU, display 394 and application processor.

[0125] The ISP (Image Signal Processor) is used to process data fed back from the camera 393. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's image sensor. The light signal is converted into an electrical signal, and the image sensor transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimizations on image noise, brightness, and skin tone. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be integrated into the camera 393.

[0126] Camera 393 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 300 may include one or N cameras 393, where N is a positive integer greater than 1.

[0127] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn. NPUs can enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0128] Internal memory 321 can be used to store executable program code, including instructions. Internal memory 321 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.). The data storage area may store data created during the use of electronic device 300 (such as audio data, phonebook, etc.). Furthermore, internal memory 321 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, Universal Flash Storage (UFS), etc. Processor 310 executes various functional applications and data processing of electronic device 300 by running instructions stored in internal memory 321 and / or instructions stored in memory located within the processor.

[0129] In some embodiments, the internal memory 321 may store instructions for a page-turning method. By executing these instructions, the processor 310 can detect changes in the user's gaze point based on eye-tracking technology. After determining that the user's gaze point has moved from the upper region to the lower region, the remaining reading time required for the user to finish reading the lower region's page content can be estimated as a page-turning waiting time, and a waiting time window is entered. After this waiting time window, when it is determined that the user's gaze point has moved from the lower region to the upper region again, the user's page-turning intention can be detected, and an automatic page-turning operation can be executed. In this way, when the user decides to turn the page after reading the lower region's page content, they only need to move their gaze point to the upper region, and the page will turn automatically without any mechanical movement of the user's hand, greatly reducing fatigue and improving the user's reading experience.

[0130] In some embodiments, the processor 310 executes page-turning method instructions, enabling it to detect changes in the user's gaze point based on eye-tracking technology. If the user typically gazes at the upper half of the application interface, and it is determined that the user's gaze point has moved from the upper area to the lower area, it can be determined that the page scrolling speed is slower than the user's reading speed, and the page scrolling speed can be increased. Conversely, if the user typically gazes at the lower half of the application interface, and it is determined that the user's gaze point has moved from the lower area to the upper area, it can be determined that the page scrolling speed is faster than the user's reading speed, and the page scrolling speed can be decreased. This allows for dynamic adjustment of the page scrolling speed based on the user's reading speed, matching the scrolling speed to the user's reading habits and speed, eliminating the need for manual adjustment and significantly improving the user's reading experience.

[0131] Pressure sensor 380A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 380A can be disposed on display screen 394. There are many types of pressure sensors 380A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 380A, the capacitance between the electrodes changes. Electronic device 300 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 394, electronic device 300 detects the touch operation intensity based on pressure sensor 380A. Electronic device 300 can also calculate the touch position based on the detection signal from pressure sensor 380A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example: when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

[0132] The gyroscope sensor 380B can be used to determine the motion attitude of the electronic device 300. In some embodiments, the gyroscope sensor 380B can determine the angular velocity of the electronic device 300 around three axes (i.e., the x, y, and z axes). The gyroscope sensor 380B can be used for image stabilization. For example, when the shutter is pressed, the gyroscope sensor 380B detects the angle of the electronic device 300's shake, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to counteract the shake of the electronic device 300 through reverse movement, thus achieving image stabilization. The gyroscope sensor 380B can also be used in navigation and motion-sensing game scenarios.

[0133] In some embodiments, when a user rotates the electronic device 300, the gyroscope sensor 380B can determine the motion posture of the electronic device 300. This allows the processor 310 to determine whether the electronic device 300 is in landscape or portrait mode based on the data provided by the gyroscope sensor 380B.

[0134] A distance sensor 380F is used to measure distance. Electronic device 300 can measure distance via infrared or laser. In some embodiments, during a shooting scene, electronic device 300 can utilize the distance sensor 380F to measure distance for rapid focusing.

[0135] The ambient light sensor 380L is used to sense the brightness of ambient light. The electronic device 300 can adaptively adjust the brightness of its display screen 394 based on the sensed ambient light level. The ambient light sensor 380L can also be used to automatically adjust the white balance when taking photos. The ambient light sensor 380L can also work in conjunction with the proximity sensor 380G to detect whether the electronic device 300 is in a pocket, preventing accidental touches.

[0136] Touch sensor 380K, also known as a "touch device," can be located on display screen 394. The touch sensor 380K and display screen 394 together form a touchscreen, also known as a "touchscreen." Touch sensor 380K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 394. In other embodiments, touch sensor 380K may also be located on the surface of electronic device 300, in a different position than display screen 394.

[0137] The software system of electronic device 300 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses the layered architecture Android system as an example to exemplify the software structure of electronic device 300. This application does not limit the type of operating system for the electronic device. For example, Android, Linux, Windows, iOS, Harmony Operating System (HarmonyOS), etc.

[0138] Figure 3b is a software structure block diagram of an electronic device 300 provided in one embodiment of this application.

[0139] As shown in Figure 3b, the layered architecture divides the software into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer (APP), the application framework layer (APP Framework), the Android Runtime and system libraries, and the kernel layer (Kernel).

[0140] The application layer can include a series of application packages.

[0141] As shown in Figure 3b, the application package may include apps such as gallery, map, navigation, music, video, games, chat, shopping, and reading. The application layer may also include other apps besides those shown in Figure 3b, such as camera, calendar, call, WLAN, Bluetooth, and SMS, which will not be elaborated upon in this embodiment.

[0142] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0143] As shown in Figure 3b, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0144] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0145] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0146] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0147] The phone manager is used to provide communication functions for electronic devices 300. For example, it manages call status (including connection and disconnection).

[0148] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0149] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0150] The Android Runtime consists of core libraries and a virtual machine. The Android Runtime is responsible for the scheduling and management of the Android system.

[0151] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0152] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0153] System libraries can include multiple functional modules. For example: Surface Manager, Media Libraries, 3D graphics processing libraries (e.g., OpenGLES), 2D graphics engines (e.g., SGL), foveated interaction engines, etc.

[0154] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0155] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0156] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0157] A 2D graphics engine is a graphics engine for 2D drawing.

[0158] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0159] The system architecture of the electronic device 300 according to an embodiment of this application is explained below with reference to FIG3c.

[0160] Referring to Figure 3c in the specification, Figure 3c shows a schematic diagram of the system architecture of an electronic device provided in an embodiment of this application. As shown in Figure 3c, the system architecture adopted by the electronic device 300 in this embodiment may include an image sensor 301, a gaze interaction engine 302, a gaze interaction algorithm module 303, an artificial intelligence (AI) chip 304, an application (APP) 305, a gaze intent processing module 306, and a reader module 307.

[0161] Image sensor 301 can be a front-facing low-power camera used to capture and output images of the user's face.

[0162] The gaze point interaction engine 302 is the execution software module for gaze point interaction. It is used to receive facial images collected by the image sensor 301 and input the facial images and related parameters into the gaze point interaction algorithm module 303 for inference to identify the user's gaze point.

[0163] The gaze point interaction algorithm module 303 may include a pre-trained inference model for recognizing gaze points. This model can run within the AI ​​chip 304 and the inference container, and consume system computing power to infer the input facial image in order to recognize the user's gaze points.

[0164] AI chip 304 can be integrated on the motherboard of electronic device 300 to provide AI computing power and operators.

[0165] Application APP 305 is an APP running on electronic device 300, which can mainly include reading APPs such as news and information, e-books, magazines and comics. The main characteristic of this type of APP is that it can use the entire screen area as a reading interface, and the text and images are arranged on the screen from top to bottom according to natural layout rules. The text and images outside the screen area support left and right or up and down page turning operations. It should be noted that in some possible embodiments, application APP can also include other types of APPs, such as browser APPs, information flow APPs, etc., and this application embodiment does not make specific limitations in this regard.

[0166] The gaze intent processing module 306 is a software module for gaze intent processing that runs in a reading app. This module can assist the gaze interaction engine 302 on the external operating system of the app in registering and listening for events; it can also assist the reader module 307 in the app in calculating the amount of information on the reading page, the reading speed, and executing page turning.

[0167] The reader module 307 runs within reading apps, providing layout and rendering of reading page content, as well as operations such as page turning. The reader module 307 can also expose APIs to external systems for querying reading page parameters, such as an interface for querying page information content and an interface for executing page turning operations with mixed page types.

[0168] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 300. In other embodiments of this application, the electronic device 300 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0169] The following details the specific process of the page-turning method provided in the embodiments of this application.

[0170] The page-turning method provided in this application can be applied to electronic devices with the hardware structure shown in FIG3a and the software structure shown in FIG3b. Alternatively, it can be applied to electronic devices with more or fewer components than shown, or combinations of certain components, or splitting of certain components, or different component arrangements, etc., with similar hardware and software structures.

[0171] The following describes in detail a page-turning method provided in one embodiment of this application, using a mobile phone as an example. The mobile phone can be in portrait mode and has multiple apps installed, some or all of which provide information to the user. Referring to Figure 4, which shows a flowchart of a page-turning method provided in one embodiment of this application, the method may include steps S401-S405.

[0172] S401: The mobile phone displays the application interface of a reading app (as an example of a first application), which includes an upper area (as an example of a first display area) and a lower area (as an example of a second display area), the upper area and the lower area partially overlap or do not overlap at all.

[0173] In this embodiment, the first application can be any application installed on the mobile phone that can provide information to the user. The first application can be of various types, including but not limited to reading apps, browser apps, and news feed apps. This embodiment uses a reading app as an example of the first application, but this application is not limited to this. The reading app can be an app with page-turning modes such as left and right page turning, simulated page turning, overlay page turning, or top and bottom half-screen page turning.

[0174] In this embodiment, the upper and lower regions together constitute the application interface of the reading app. The upper and lower regions may partially overlap or not overlap at all. The application interface of the reading app may display pages of the reading app, such as the homepage of the reading app, or the reading page of a book in the reading app; this application does not impose specific limitations on this.

[0175] In one possible embodiment, referring to Figure 5a of the specification, Figure 5a shows a schematic diagram of the application interface of a reading app provided in one embodiment of this application. As shown in Figure 5a, when the mobile phone is in portrait mode, the upper area of ​​the application interface 510 may include an upper grid 501 and a transition area 502, and the lower area of ​​the application interface 510 may include a transition area 502 and a lower grid 503. That is, the upper and lower areas of the application interface 510 may partially overlap, and this overlapping area is the transition area 502.

[0176] The transition region 502 can be positioned in the middle of the application interface, and its size can affect the sensitivity of the user's gaze when switching between the upper and lower regions. Specifically, a larger transition region 502 results in lower sensitivity, while a smaller transition region 502 results in higher sensitivity.

[0177] For example, referring to Figure 5b of the specification, Figure 5b shows a schematic diagram of a transition region 502 provided in one embodiment of this application. As shown in Figure 5b, the transition region 502 may include a region with a width of [Xa, X+b] in the middle of the application interface 510, where X represents the position of half the height of the application interface 510. The size of the transition region 502 can be determined based on the values ​​of a and b, which can be determined according to actual needs. For example, they can be passed in by a reading app when registering a gaze point switching fence event or preset by the system. This embodiment of the application does not impose specific limitations on this.

[0178] In another possible embodiment, referring to Figure 5c of the specification, Figure 5c shows a schematic diagram of the application interface of a reading app provided in another embodiment of this application. As shown in Figure 5c, the upper area of ​​the application interface 510 may consist only of the upper grid 501, and the lower area of ​​the application interface 510 may consist only of the lower grid 503. That is, the upper and lower areas of the application interface 510 may not overlap at all.

[0179] It should be noted that in the embodiments described above, the phone is displayed in portrait mode. In other embodiments of this application, it can also be displayed in landscape mode. When the phone is displayed in landscape mode, the area above the application interface is the first display area, and the area below the application interface is the second display area. Alternatively, when the phone is displayed in landscape mode, the area on the left side of the application interface is the first display area, and the area on the right side of the application interface is the second display area.

[0180] In one possible embodiment, Figure 5d shows a schematic diagram of the application interface of a reading app provided in another embodiment of this application. As shown in Figure 5d, when the mobile phone is in landscape mode, the positional relationship between the two areas of the application interface can remain unchanged, still being vertical. That is, the application interface 520 may include an upper area and a lower area. The upper area of ​​the application interface 520 may include an upper grid 504 and a transition area 505, and the lower area of ​​the application interface 520 may include a transition area 505 and a lower grid 506. In other words, the upper and lower areas of the application interface 520 may partially overlap, and this overlapping area is the transition area 505.

[0181] In another possible embodiment, when the phone is in landscape mode, the upper area of ​​the application interface 520 may consist only of the upper grid 504, and the lower area of ​​the application interface 520 may consist only of the right grid 506. That is, the upper and lower areas of the application interface 520 may not overlap at all.

[0182] In another possible embodiment, Figure 5e shows a schematic diagram of the application interface of a reading app provided in another embodiment of this application. As shown in Figure 5e, when the mobile phone is in landscape mode, the positional relationship between the two areas of the application interface can become a left-right relationship. That is, the application interface 520 may include a left area (as another example of a first display area) and a right area (as another example of a second display area). The left area of ​​the application interface 520 may include a left grid 507 and a transition area 508, and the right area of ​​the application interface 520 may include a transition area 508 and a right grid 509. In other words, the left and right areas of the application interface 520 may partially overlap, and this overlapping area is the transition area 508.

[0183] In another possible embodiment, when the phone is in landscape mode, the left area of ​​the application interface 520 may consist only of the left grid 507, and the right area of ​​the application interface 520 may consist only of the right grid 509. That is, the left and right areas of the application interface 520 may not overlap at all.

[0184] S402: The mobile phone determines that the user's gaze point relative to the application interface has moved from the upper area to the lower area.

[0185] In this embodiment, the mobile phone can acquire the user's facial image in real time and perform inference based on the user's facial image to identify the user's gaze point relative to the application interface and determine the display area where the gaze point is located, thereby determining whether the user's gaze point has moved from the upper area to the lower area. Specifically, if it is determined that the display area where the user's gaze point is currently located is the lower area, and it is determined that the display area where the user's gaze point was previously located is the upper area, it can be determined that the user's gaze point has moved from the upper area to the lower area.

[0186] Specifically, the mobile phone can recognize faces and eyes based on inference from a gaze-point interaction algorithm model, determine the relationship between the user's gaze point and the display area, and detect the switching of the user's gaze point between the upper and lower areas by combining the display area where the user's gaze point was previously located. The gaze-point interaction algorithm model can be predetermined according to actual needs, and this application embodiment does not impose specific limitations on it.

[0187] S403: The phone responds to determining that the user's gaze point relative to the application interface has moved from the upper area to the lower area, and determines the page-turning wait time for the reading app's application interface.

[0188] In this embodiment, for reading scenarios, the main areas requiring intent identification include the top of the page (representing start) and the bottom of the page (representing completion); the middle area has no actual intent. Considering that users typically read the first half of the page before moving on to the second half, when the phone determines that the user is reading the second half, it can dynamically estimate the time required for the user to finish reading the second half based on the user's real-time reading speed, i.e., estimate the page-turning waiting time. The phone can determine the reading progress based on the reading time; once the page-turning waiting time is determined, it can be concluded that the user has finished reading the second half of the page (i.e., reached the bottom of the page).

[0189] Specifically, once the phone determines that the user's gaze has moved from the upper area to the lower area, it can determine that the user has switched from reading the page content in the upper area to reading the page content in the lower area. At this point, based on the user's page reading speed in the upper area, the remaining reading time required to read the page content in the lower area can be estimated, and thus the page-turning wait time can be determined. The specific process for determining the page-turning wait time will be described in detail later.

[0190] S404: The mobile phone responds to the determination that the user's gaze has moved from the upper area to the lower area, and after a page-turning waiting time, determines that the user's gaze has moved from the lower area to the upper area.

[0191] In this embodiment, in response to determining that the user's gaze has moved from the upper area to the lower area, the mobile phone can determine the reading progress to ascertain whether the user has finished reading all the content of the page (i.e., reached the bottom of the page). Specifically, the mobile phone can determine whether the current waiting time t has reached the page-turning waiting time T after determining that the user's gaze has moved from the upper area to the lower area. If yes, it can be determined that the user has finished reading all the content of the page. If no, it can be determined that the user has not yet finished reading all the content of the page, and the user continues to wait.

[0192] In this embodiment, after determining that the user has finished reading all the content on the page, the mobile phone can determine the user's intention to turn the page, and then automatically turn the page when the user's intention to turn the page is detected. Specifically, the mobile phone can determine whether the user's gaze has moved from the lower area to the upper area. If so, it can determine that the user's intention to turn the page has been detected. If not, it can continue to wait.

[0193] Specifically, the details of detecting the user's gaze point moving from the lower region to the upper region can be found in step S402, which describes the detection of the user's gaze point moving from the upper region to the lower region. This embodiment will not repeat the details here. Specifically, if it is determined that the current display area where the user's gaze point is located is the upper region, and it is determined that the display area where the user's gaze point was previously located was the lower region, then it can be determined that the user's gaze point has moved from the lower region to the upper region.

[0194] S405: The phone responds to the user's gaze shifting from the lower area to the upper area and performs a page-turning operation for the application interface of a reading app.

[0195] In this embodiment, when the mobile phone determines that the user's gaze has moved from the lower area to the upper area, it can identify the user's intention to turn the page, and then automatically turn the page. Specifically, the mobile phone can perform a page-turning operation to display the content of the next page in the reading app's interface.

[0196] It is understood that the page-turning method provided in this application embodiment can be used in reading apps with various page-turning modes, such as including but not limited to left and right page turning, simulated page turning, overlay page turning, and half-screen page turning. For reading apps with different page-turning modes, the page-turning operations performed may be different.

[0197] For example, for reading apps with a left-right page-turning mode, a left or right page-turning action can be performed to display the content of the next page on the app's interface. For reading apps with a simulated page-turning mode, a simulated page-turning action can be performed to display the content of the next page on the app's interface. For reading apps with an overlay page-turning mode, an overlay page-turning action can be performed to overlay the content of the current page with the content of the next page. For reading apps with a top-and-bottom half-screen page-turning mode, a half-screen flip page-turning action can be performed to display the top half of the next page's content on the top half and the bottom half of the next page's content on the bottom half.

[0198] It should be noted that the details of performing page-turning operations on the application interface of reading apps will not be elaborated here in the embodiments of this application.

[0199] In one possible embodiment, performing a page-turning operation on the application interface of a reading app may include: in response to determining that the user's gaze point has moved from the lower area to the upper area, performing a page-turning operation on the application interface of the reading app after 200ms (as an example of a third preset time).

[0200] In one possible embodiment, the page-turning method may further include: within 200ms, the mobile phone, in response to determining that the user's gaze point has moved from the upper area to the lower area, abandons the page-turning operation for the application interface of the reading app.

[0201] In this embodiment, the following scenario of abrupt change in recognition result exists: the user is looking at the lower area of ​​the application interface, and after determining that the user's gaze point has moved from the upper area to the lower area, the current waiting time t has reached the page-turning waiting time T. The user has not looked up, but the algorithm's recognition error causes a jump in the user's gaze point from bottom to top and then back down. In this scenario, page turning may be falsely triggered, affecting the user experience. Therefore, to avoid this scenario, a 200ms page-turning delay can be added.

[0202] If the user's gaze does not move from the upper area to the lower area within the delay time, the user's intention to turn the page is considered genuine, and the page-turning operation can be performed. If the user's gaze moves from the upper area to the lower area again within the delay time, the user's intention to turn the page is considered a misidentification, and the page-turning operation is not performed.

[0203] It should be noted that the example of using 200ms as the third preset time is only an exemplary implementation. In practical applications, the third preset time can also be set to other values, and this application embodiment does not impose specific limitations on this.

[0204] The page-turning method provided in this application embodiment will be further described below in conjunction with the system architecture of the mobile phone and its modules. Referring to Figure 6, Figure 6 shows a flowchart of a page-turning method provided in a specific embodiment of this application, which is a further explanation of the embodiment shown in Figure 4. The method may include steps S601-S621.

[0205] S601: The gaze intent processing module can register gaze point switching fence events with the gaze point interaction engine.

[0206] Specifically, when a user is using a reading app, the reader module can display the app's interface. At this time, the gaze intent processing module can register gaze fences for the two display areas of the app interface, as well as gaze point switching fence events. Specifically, it can register the upper area gaze fence and the lower area gaze fence, as well as fence events when the user's gaze point switches from the upper area gaze fence to the lower area gaze fence and vice versa.

[0207] S602: When the user is looking at the upper area of ​​the application interface, the image sensor can acquire and output images in real time to obtain the user's facial image.

[0208] Specifically, the image sensor can be a low-power front-facing camera for the phone, such as a low-power camera with frames per second (FPS) of 10 to 20. This low-power camera can run on a security chip to ensure user privacy and security.

[0209] Understandably, by using a low-power camera, the power consumption increase is no more than 5% compared to manual page turning, and the recognition accuracy of the area where the user's gaze is located is high (greater than 95%), which can effectively solve the power consumption problem based on image recognition technology. Even during long-term reading, the impact on the phone's battery life is minimal.

[0210] It should be noted that in practical applications, the page-turning method of this application embodiment can also be implemented by directly enabling the low-power mode of the front-facing camera of the mobile phone. This application embodiment does not impose specific limitations on this.

[0211] S603: The image sensor can input the acquired facial images into the gaze-point interaction engine.

[0212] Accordingly, the gaze-point interaction engine can receive the user's facial image sent by the image sensor.

[0213] S604: The gaze point interaction engine can input the user's facial image into the gaze point interaction algorithm module for processing.

[0214] Specifically, after receiving the user's facial image, the gaze point interaction engine can input the facial image and related parameters (such as the position and angle of the image sensor relative to the user's eyes) into the gaze point interaction algorithm module.

[0215] S605: The gaze point interaction algorithm module can perform gaze point recognition processing on facial images to obtain the user's gaze point coordinates relative to the application interface.

[0216] Specifically, the gaze-point interaction algorithm module can recognize faces and eyes based on inference from the gaze-point interaction algorithm model. The specific recognition method will be described in detail later.

[0217] S606: The gaze point interaction algorithm module can determine whether to trigger a fence entry / exit event by judging the gaze point coordinates to determine whether to trigger the fence event that the user's gaze point changes from the upper area to the lower area (i.e., determine whether the user's gaze point moves from the upper area to the lower area).

[0218] Specifically, the gaze point interaction algorithm module can determine the relationship between the identified user gaze point and the display area, and detect the switching of the user's gaze point between the upper and lower display areas based on the display area where the user's gaze point was previously located. Specifically, if it is determined that the current display area where the user's gaze point is located is the lower area, and the previous display area where the user's gaze point was located is the upper area, it can be determined that the user's gaze point has moved from the upper area to the lower area. Conversely, if it is determined that the current display area where the user's gaze point is located is the upper area, and the previous display area where the user's gaze point was located is the lower area, it can be determined that the user's gaze point has moved from the lower area to the upper area.

[0219] Specifically, when the gaze point interaction algorithm module determines that the current phone is in portrait mode, it can use a gaze point interaction algorithm with an upper and lower region recognition mode to identify the user's gaze point and determine the display area of ​​the application interface where the gaze point is located. In the upper and lower region recognition mode, the phone can directly determine whether the display area of ​​the application interface where the user's gaze point is located is the upper or lower region of the display interface using the gaze point interaction algorithm.

[0220] S607: If a fence event is determined to trigger a switch of the user's gaze point from the upper region gaze fence to the lower region gaze fence, the gaze point interaction algorithm module can also report the fence event to the gaze point interaction engine.

[0221] Accordingly, the gaze point interaction engine can receive fence events when the user's gaze point switches from the upper region gaze fence to the lower region gaze fence.

[0222] S608: The gaze point interaction engine can report the fence event when the user's gaze point switches from the upper area gaze fence to the lower area gaze fence to the gaze intent processing module.

[0223] Accordingly, the gaze intent processing module can receive fence events when the user's gaze point switches from the upper area gaze fence to the lower area gaze fence.

[0224] It should be noted that steps S602 to S608 correspond to step S402 in the embodiment shown in Figure 4.

[0225] S609: The gaze intent processing module can respond to the fence event when the user's gaze point switches from the upper area gaze fence to the lower area gaze fence, and calculate the page reading speed and page turning waiting time.

[0226] Specifically, the gaze intent processing module can estimate the remaining reading time required to read the content in the lower section of the page based on the user's page reading speed in the upper section, and then determine the page-turning wait time. The method for determining the page-turning wait time will be described in detail later.

[0227] It should be noted that step S609 corresponds to step S403 in the embodiment shown in Figure 4.

[0228] S610: The gaze intent processing module can respond to the fence event when the user's gaze point switches from the upper area gaze fence to the lower area gaze fence, and judge the reading progress.

[0229] Specifically, after receiving a fence event indicating that the user's gaze has switched from the upper area to the lower area, the gaze intent processing module can also determine the reading progress based on the calculated page-turning wait time, thereby determining whether the user has finished reading all the content on the page.

[0230] S611: When the user is looking at the lower area of ​​the application interface, the image sensor can acquire and output images in real time to obtain the user's facial image.

[0231] S612: The image sensor can input the acquired facial images into the gaze-point interaction engine.

[0232] Accordingly, the gaze-point interaction engine can receive the user's facial image sent by the image sensor.

[0233] S613: The gaze point interaction engine can input the user's facial image into the gaze point interaction algorithm module for processing.

[0234] S614: The gaze point interaction algorithm module can perform gaze point recognition processing on facial images to obtain the user's gaze point coordinates relative to the application interface.

[0235] S615: The gaze point interaction algorithm module can determine the fence entry and exit based on the gaze point coordinates to determine whether to trigger the fence event that the user's gaze point switches from the lower area to the upper area (i.e., determine that the user's gaze point moves from the lower area to the upper area).

[0236] S616: If a fence event is determined to trigger a switch of the user's gaze point from the lower region gaze fence to the upper region gaze fence, the gaze point interaction algorithm module can also report the fence event to the gaze point interaction engine.

[0237] Accordingly, the gaze point interaction engine can receive fence events when the user's gaze point switches from the lower region gaze fence to the upper region gaze fence.

[0238] It should be noted that the specific content of steps S611 to S616 can be referred to the relevant content of steps S602 to S607, and will not be repeated here in the embodiments of this application.

[0239] S617: The gaze point interaction engine can also report the fence event when the user's gaze point switches from the lower area gaze fence to the upper area gaze fence to the gaze intent processing module.

[0240] Accordingly, the gaze intent processing module can receive fence events when the user's gaze point switches from the lower area gaze fence to the upper area gaze fence.

[0241] S618: The gaze intent processing module can determine the page turning intent.

[0242] Specifically, after determining that the user has finished reading all the content on the page, and receiving a fence event indicating that the user's gaze has switched from the lower area gaze fence to the upper area gaze fence, the gaze intent processing module can determine and recognize the user's intention to turn the page.

[0243] In practical applications, the gaze intent processing module, during the page-turning intent determination process, can enter a waiting time window of duration T after receiving a fence event indicating that the user's gaze point has switched from the upper region's gaze fence to the lower region's gaze fence. Only after this waiting time window (i.e., after the current waiting time t reaches the page-turning waiting time T) does the page-turning intent determination begin, and the page-turning action is executed in response to the fence event indicating that the user's gaze point has switched from the lower region's gaze fence to the upper region's gaze fence, thus reducing the impact of gaze point jumps. Within this waiting time window (i.e., before the current waiting time t reaches the page-turning waiting time T), even if a fence event indicating that the user's gaze point has switched from the lower region's gaze fence to the upper region's gaze fence is received, page-turning is not executed.

[0244] It should be noted that steps S610 to S618 correspond to step S404 in the embodiment shown in Figure 4.

[0245] S619: When the gaze intent processing module receives a fence event indicating that the user's gaze point has switched from the lower area gaze fence to the upper area gaze fence, the event smoothing suppression can be performed.

[0246] Specifically, after receiving a fence event indicating that the user's gaze has switched from the lower area fence to the upper area fence, the gaze intent processing module can enter a 200ms delay execution window. If no further fence event indicating that the user's gaze has switched from the upper area fence to the lower area fence is received within this delay execution window, the module considers the user's intention to turn the page to be genuine.

[0247] Specifically, within the delayed execution window, if another fence event indicating a shift in the user's gaze from the upper to the lower fence area is received, the previously received fence event can be considered a misidentification and needs to be suppressed. In other words, the page-turning operation for reading apps can be abandoned, waiting for the next fence event indicating a shift in the user's gaze from the lower to the upper fence area.

[0248] S620: If it is determined that the user's intention to turn the page is genuine, the gaze intent processing module can send a page-turning instruction to the reader module.

[0249] Accordingly, the reader module can receive page-turning instructions sent by the gaze intent processing module.

[0250] S621: The reader module can respond to page-turning commands and perform page-turning operations for the application interface of reading apps.

[0251] It should be noted that steps S619 to S621 correspond to step S405 in the embodiment shown in FIG4. Other contents in steps S601 to S621 can be referred to the relevant contents in the embodiment shown in FIG4, and will not be repeated here.

[0252] In practical applications, because the embodiments of this application use low-power cameras, the accuracy of gaze point recognition cannot be achieved at the pixel level due to limitations in sampling rate, image clarity, camera position, the angle between the camera and the user's eyes, user's eye characteristics, lighting conditions, and the power consumption of the gaze point interaction algorithm. Furthermore, the accuracy deviation is relatively large for certain areas of the screen. In areas with large deviations, the gaze point recognition algorithm may exhibit abrupt changes in recognition coordinates, and these abnormal changes can interfere with the recognition of the user's intended intent.

[0253] For example, referring to Figure 7a of the specification, Figure 7a illustrates a gaze jump diagram provided in one embodiment of this application. As shown in Figure 7a, when a user gazes at the upper region, a partial gaze jump problem may occur (i.e., within a time window, the user's gaze may be identified as mainly concentrated in the upper region, but some gaze points may also be identified as being in the lower region). Referring to Figure 7b of the specification, Figure 7b illustrates a gaze jump diagram provided in another embodiment of this application. As shown in Figure 7b, similar to the upper region, when a user gazes at the lower region, due to the constraint of recognition accuracy, a partial gaze jump problem may still occur (i.e., within a time window, the user's gaze may be identified as mainly concentrated in the lower region, but some gaze points may also be identified as being in the upper region).

[0254] To address the gaze point transition issue, in one possible embodiment, a transition area can be set in the middle of the application interface, and this transition area can be included in both the upper and lower areas of the application interface. When the user's gaze point falls within the middle transition area, the gaze point interaction algorithm module and the gaze point interaction engine will suppress the triggering of the gaze point switching fence event. That is, as shown in Figure 5a, when it is determined that the user's gaze point falls within the middle transition area 502, regardless of whether the user's gaze point previously fell within the upper grid 501 or the lower grid 503 (or the left or right grid in landscape mode), the gaze point switching fence event will not be triggered.

[0255] In addition to setting a transition region, in one possible embodiment, multi-frame smoothing can also be performed when determining the coordinates of the gaze point. That is, the display area where the user's gaze point is currently located and the display area where it was previously located can both be determined based on at least one frame of the user's facial image. Specifically, as shown in Figure 6, before step S606, step S605' (shown as a dashed line in Figure 6) can be executed first, and / or, before step S615, step S614' (shown as a dashed line in Figure 6) can be executed first. That is, the gaze point interaction algorithm module can weight the identified gaze point coordinates together with at least one historical gaze point coordinate to obtain the final gaze point coordinates. Among them, the historical gaze point coordinates can be the coordinates of the gaze point identified based on historical frame data, and the historical frame data can be facial images acquired before the current frame data.

[0256] In one possible embodiment, when identifying the user's gaze point, the gaze point interaction algorithm module can also directly use the continuously acquired multi-frame images to identify multiple gaze point coordinates, and then perform weighted summation to obtain the final gaze point coordinates.

[0257] The following is a more detailed description of the gaze point recognition and fence entry / exit judgment process in steps S602 to S607 of the embodiment shown in Figure 6. Referring to Figure 8, Figure 8 shows a flowchart of the fence triggering event processing provided in a specific embodiment of this application. The processing flow may include steps S801-S821.

[0258] As shown in Figure 8, in step S801, it can be first determined whether the phone screen is off. In step S802, if it is determined that the screen is not off, it can be determined whether the current light intensity is higher than a preset light intensity threshold. If it is determined that the screen is off, the entire process ends. In step S803, if it is determined that the light intensity is higher than the preset light threshold, the image sensor collects the current frame data and inputs it into the gaze point interaction engine. If it is determined that the light intensity is not higher than the preset light threshold, the entire process ends. The preset light intensity threshold can be preset according to actual conditions, for example, it can be set to 5 lux, etc., and this embodiment does not impose specific limitations on this. Steps S801 to S802 correspond to steps S602 to S603 in the embodiment shown in Figure 6.

[0259] In step S804, the gaze point interaction engine can input the received current frame data into the gaze point interaction algorithm module for pre-face recognition image processing. In step S805, the gaze point interaction algorithm module can perform face recognition on the pre-face recognition image. In step S806, the gaze point interaction algorithm module can determine whether the face is valid based on the recognized face recognition result. If it is determined to be invalid, the current frame data can be determined to be an invalid frame, and the entire process ends. In step S807, if it is determined to be valid, the gaze point interaction algorithm module can perform pre-face orientation detection image processing on the face recognition result. In step S808, the gaze point interaction algorithm module can perform face orientation detection on the pre-face orientation detection image. In step S809, the gaze point interaction algorithm module can determine whether the face is facing the screen based on the detected face orientation detection result. If it is determined that the face is not facing the screen, the current frame data can be determined to be an invalid frame, and the entire process ends.

[0260] In step S810, if it is determined that the face is facing the screen, the gaze point interaction algorithm module can perform pre-visual detection image processing on the face recognition result. In step S811, the gaze point interaction algorithm module can perform visual detection on the image after pre-visual detection image processing. In step S812, the gaze point interaction algorithm module can determine whether the user is looking at the screen based on the detected visual detection result. If it is determined that the user is not looking at the screen, the current frame data can be determined as an invalid frame, and the entire process ends. In step S813, if it is determined that the user is looking at the screen, the gaze point interaction algorithm module can perform pre-facial keypoint detection image processing on the face recognition result. In step S814, the gaze point interaction algorithm module can perform facial keypoint detection on the image after pre-facial keypoint detection image processing. In step S815, the gaze point interaction algorithm module can determine whether the facial keypoints are valid based on the detected facial keypoint detection result. If it is determined to be invalid, the current frame data can be determined as an invalid frame, and the entire process ends. In step S816, if the determination is valid, the gaze point interaction algorithm module can perform pre-gaze prediction image processing on the face recognition result. In step S817, the gaze point interaction algorithm module can perform gaze point prediction on the image after pre-gaze prediction image processing.

[0261] In step S818, the gaze point interaction algorithm module can also determine whether the distance between the user and the mobile phone screen is less than a preset distance threshold. If the distance is greater than or equal to the preset distance threshold, the current frame data can be determined to be an invalid frame, and the entire process ends. In step S819, if the distance is less than the preset distance threshold, the gaze point interaction algorithm module can obtain the final gaze point coordinates by weighting the predicted gaze point coordinates with the historical gaze point coordinates corresponding to the historical frame data. The preset distance threshold can be preset according to actual needs, for example, it can be set to 50cm, etc., and this application embodiment does not impose specific limitations on it. Steps S804 to S819 correspond to steps S604 to S605' in the embodiment shown in Figure 6.

[0262] It should be noted that in this embodiment of the application, the distance between the user and the mobile phone screen can be 0 to 50 cm, with the optimal distance being 35 cm, but it is not limited to this.

[0263] In step S820, the gaze point interaction algorithm module can also determine the relationship between the final gaze point coordinates and the upper and lower regions, that is, determine whether the user's gaze point is currently located in the upper or lower display area. Then, it can combine the display area where the user's gaze point was previously located to determine whether reporting is required. In step S821, if it is determined that the user's gaze point is currently located in the lower display area and that the user's gaze point was previously located in the upper display area, the gaze point interaction algorithm module can determine the fence event that triggered the user's gaze point to switch from the upper region gaze fence to the lower region gaze fence, that is, it needs to be reported. At this time, the fence event can be reported to the context-aware software development kit (SDK) of the gaze point interaction engine. Otherwise, it can be determined that no reporting is required, and the entire process ends. Steps S820 to S821 correspond to steps S606 and S607 in the embodiment shown in Figure 6. Afterwards, the context-aware software development kit can inform the gaze intent processing module of the reading app of the fence event.

[0264] It should be noted that other aspects of each step in the embodiment shown in Figure 8 will not be repeated here.

[0265] In one possible embodiment, if no face is detected in step S805 (i.e., the number of faces is 0), it can be determined that the user has left. If it is determined in step S809 that the face is not facing the screen, it can be determined that the user is not reading. At this time, page turning can be automatically paused, and the screen can be dimmed or turned off to save the phone's battery. If multiple faces are detected in step S805, one of the faces can be selected as the target face for subsequent operations. The target face can be the face closest to the camera or the face with the highest usage frequency. This application embodiment does not impose specific limitations on the face selection method.

[0266] The following is a more detailed explanation of the calculation process for page reading speed and page turning waiting time in step S609 of the embodiment shown in Figure 6.

[0267] In one possible embodiment, step S609 may include: determining the user's page reading speed in the upper area; estimating the user's remaining reading time in the lower area based on the page reading speed; and determining the page-turning waiting time based on the remaining reading time.

[0268] In one specific embodiment, the gaze intent processing module can calculate the user's page reading speed in the upper region in real time based on the amount of page information in the upper region and the time the user spends reading the page content in the upper region. That is, determining the user's page reading speed in the upper region can include: obtaining the cumulative time the user's gaze has lingered in the upper half of the screen (as an example of a first cumulative time); and determining the page reading speed based on the cumulative time of reading the upper half of the screen and the amount of page information in the upper region. The amount of page information may include, but is not limited to, the amount of text, white space, and the proportion of illustrations, etc., and this embodiment does not impose specific limitations on this.

[0269] In this embodiment, when a user opens a reading app and displays the corresponding application interface, or after performing operations such as page turning or chapter switching, the information content of the page above half the height of the application interface can be calculated based on the current page content, and this information content is used as the page information content in the upper region. The information content of the page below half the height of the application interface is also calculated, and this information content is used as the page information content in the lower region. For example, if the current page is a text page, the coordinates of each character on the current page can be obtained, and the text content above half the height of the application interface can be calculated as the page information content in the upper region. The text content below half the height of the application interface can also be calculated as the page information content in the lower region.

[0270] In one possible embodiment, the amount of information of the page located in the upper region can be calculated based on the page content of the current page, and used as the amount of information of the page in the upper region, while the amount of information of the remaining page is used as the amount of information of the page in the lower region.

[0271] In this embodiment of the application, in order to obtain the cumulative time of the user reading the upper half of the screen and the cumulative time of reading the lower half of the screen, when the user opens the reading APP and displays the corresponding application interface, or after performing operations such as page turning or chapter switching, the gaze intent processing module can record the current time as the time of reading the upper area or the time of reading the lower area according to the display area where the user's gaze point is located.

[0272] Specifically, when a user opens a reading app and displays the corresponding application interface, or after performing operations such as turning pages or switching chapters, if the user's gaze is on the upper area of ​​the display, the gaze intent processing module can record the current time as the time spent reading the upper area; if the user's gaze is on the lower area of ​​the display, the gaze intent processing module can record the current time as the time spent reading the lower area.

[0273] In this embodiment, when a user is looking at the middle area of ​​the display interface, there may be issues with inaccurate algorithm recognition leading to gaze point shifts, and / or, the user may scan up and down, or read the lower half of the page content and then reread the upper half. Therefore, to obtain the cumulative time for the user to read the upper half of the screen and the cumulative time to read the lower half, the time it takes for the user's gaze point to move from the upper area to the lower area can be recorded as the time for reading the lower area. Similarly, the time it takes for the user's gaze point to move from the lower area to the upper area can be recorded as the time for reading the upper area. Furthermore, the time difference between the most recent time of reading the lower area and the most recent time of reading the upper area can be added to the cumulative time for reading the upper half of the screen or the cumulative time for reading the lower half of the screen.

[0274] As the above analysis shows, during the process of a user reading a new page, the gaze intent processing module can obtain an event sequence representing the changes in the display area where the user's gaze point is located. Based on this event sequence, and according to the time difference between the recorded time for reading the upper area and the time for reading the lower area, the cumulative reading time of the user's gaze point in the upper half of the screen and the cumulative reading time in the lower half of the screen can be calculated.

[0275] For example, referring to Figure 9 of the specification, Figure 9 shows a schematic diagram of the changes in the display area where the user's gaze point is located according to an embodiment of this application. As shown in Figure 9, A→B→C→D→E→F represents the changes in the display area where the user's gaze point is located, and the time for each change can be recorded as t1, t2, t3, t4, t5, and t6. Then, the total time from point A to point B, point C to point D, and point E to point F, T1 = (t2-t1) + (t4-t3) + (t6-t5), can be determined as the cumulative reading time of the upper half of the screen where the user's gaze point has stayed in the upper area, and the total time from point B to point C, and point D to point E, T2 = (t3-t2) + (t5-t4), is the cumulative reading time of the lower half of the screen where the user's gaze point has stayed in the lower area.

[0276] In this embodiment, the user's page reading speed can be estimated based on the cumulative reading time of the upper half of the screen and the amount of page information in the upper area. The specific calculation formula is as follows:

[0277] V1 represents the page reading speed, X1 represents the amount of page information in the upper area, and T1 represents the cumulative time spent reading the upper half of the screen.

[0278] In one specific embodiment, estimating the user's remaining reading time in the lower area based on page reading speed may include: when the page reading speed is within a preset speed range, determining the user's estimated reading time in the lower area based on the amount of page information in the lower area and the page reading speed; when the page reading speed is outside the preset speed range, determining the user's estimated reading time in the lower area based on the amount of page information in the lower area and the preset reading speed or the user's historical reading speed; and determining the remaining reading time based on the estimated reading time and the cumulative reading time of the user's gaze point in the lower area (as an example of a second cumulative time).

[0279] The preset speed range can be pre-set according to actual conditions. For example, it can be determined based on the average reading speed range of a certain user group, or it can be determined based on the user's historical reading speed. This application embodiment does not impose specific limitations on this. For example, the preset speed range can be set to a speed range greater than or equal to 5 words / second and less than or equal to 15 words / second.

[0280] The preset reading speed can be set according to actual conditions, such as a default reading speed of 10 words per second. This embodiment does not impose specific limitations on this. The historical reading speed can also be determined according to actual conditions. For example, it can be the average reading speed of all pages in the previous page, or it can be the page reading speed of the user in the upper area estimated when reading the previous page. This embodiment does not impose specific limitations on this either.

[0281] In this embodiment, after determining the page reading speed, it can be further determined whether the page reading speed falls within the normal range, or whether there is a significant error by combining the user's historical reading speed. Page reading speeds that do not fall within the normal range or have significant errors can be discarded, and a preset reading speed or the user's historical reading speed can be used to estimate the user's estimated reading time in the lower area, and then estimate the user's remaining reading time in the lower area. The specific estimation methods for the estimated reading time and the remaining reading time will be described in detail later.

[0282] In one specific embodiment, determining the page-turning waiting time based on the remaining reading time may include: when the remaining reading time is within a preset time range, determining the page-turning waiting time as the remaining reading time; when the remaining reading time is less than the minimum value of the preset time range, determining the page-turning waiting time as 2 seconds (as an example of a first preset time); when the remaining reading time is greater than the maximum value of the preset time range, determining the page-turning waiting time as 9 seconds (as an example of a second preset time).

[0283] The preset time range can be preset according to the actual situation. For example, it can be set to a time range of greater than or equal to 3 seconds and less than or equal to 9 seconds. This application embodiment does not impose specific restrictions on this.

[0284] In this embodiment, to avoid page turning too quickly or not turning a page for too long, the gaze intent processing module can also verify the estimated remaining reading time to determine whether it falls within a reasonable time range. The gaze intent processing module can discard remaining reading time that does not fall within a reasonable time range and use a preset page-turning waiting time.

[0285] It should be noted that the above examples of using 2s as the first preset time and 9s as the second preset time are merely exemplary implementations. In practical applications, the first and second preset times can also be set to other values, and this application embodiment does not impose specific limitations on this.

[0286] The following is a detailed description of the process for opening a new page on a mobile phone. Referring to Figure 10, which shows a flowchart of the process for opening a new page according to an embodiment of this application, the process may include steps S1001-S1011.

[0287] As shown in Figure 10, in step S1001, when the user opens a reading app and displays the corresponding application interface, or after triggering operations such as page turning or chapter switching, the gaze intent processing module can first remove all delay methods, that is, reset all delay times. In step S1002, the gaze intent processing module can determine the amount of page information in the upper region and the lower region. In step S1003, the gaze intent processing module can also determine the display area where the user's gaze point is located, and determine whether the display area where the user's gaze point is located is the upper region. In step S1004, if it is determined that the display area where the user's gaze point is located is the upper region, the current time can be recorded as the time of the most recent reading of the upper region. And in step S1005, the gaze intent processing module can clear the cumulative time of reading the upper half of the screen and the cumulative time of reading the lower half of the screen, and reset the time of the most recent reading of the lower region.

[0288] In step S1006, the gaze intent processing module can further determine whether the amount of page information in the lower region is less than a preset information threshold. The preset information threshold can be pre-set according to actual needs, for example, it can be set to 30 characters, etc., and this embodiment does not impose specific limitations on this. In step S1007, if it is determined that the amount of page information in the lower region is less than the preset information threshold, the page-turning waiting time for this page can be directly estimated, and subsequent steps can be executed. For example, the page-turning waiting time can be directly calculated based on the total amount of page information and the preset reading speed or the user's historical reading speed. Specifically, if it is determined that the amount of page information in the lower region is greater than or equal to the preset information threshold, no operation is required.

[0289] In step S1008, if it is determined that the display area where the user's gaze point is located is not the upper area, then it can be determined whether the display area where the user's gaze point is located is the lower area. In step S1009, if it is determined that the display area where the user's gaze point is located is the lower area, then the current time can be recorded as the time of the most recent reading of the lower area. Furthermore, in step S1010, the gaze intent processing module can clear the cumulative time for reading the upper half of the screen and the cumulative time for reading the lower half of the screen, and reset the time of the most recent reading of the upper area. In step S1011, the gaze intent processing module can also directly estimate the page-turning waiting time for this page and execute subsequent steps. The estimation method is similar to that in step S1007, and will not be repeated here. Specifically, if it is determined that the display area where the user's gaze point is located is not the lower area, then it can be determined that the user is gazing at an area outside the application interface, and no operation is required in this case.

[0290] It should be noted that other aspects of each step in the embodiment shown in Figure 10 will not be repeated here.

[0291] The following is a detailed description of the process when a user switches from gazing at the lower region to gazing at the upper region. Referring to Figure 11, Figure 11 shows a flowchart of the process when a user switches from gazing at the lower region to gazing at the upper region according to an embodiment of this application. The process may include steps S1101-S1106.

[0292] As shown in Figure 11, in step S1101, when the user switches from gazing at the lower area to gazing at the upper area, all delay methods can be removed, i.e., all delay times can be reset. In step S1102, the gaze intent processing module can record the current time as the time of the most recent reading of the upper area. In step S1103, the gaze intent processing module can also determine whether the user has finished reading all the content of the page. For example, without prompting the user to turn the page, it can determine whether the previously calculated page-turning waiting time has elapsed since the user's gaze point was last determined to have moved from the upper area to the lower area. Alternatively, when prompting the user to turn the page, it can directly determine whether the user has been prompted to turn the page. In step S1104, if it is determined that the user has not finished reading all the content of the page, it can determine whether the time of the most recent reading of the lower area is 0. In step S1105, if it is determined that the time of the most recent reading of the lower area is not 0, it can calculate the time difference between the time of the most recent reading of the lower area and the time of the most recent reading of the upper area, and add it to the user's cumulative reading time of the lower half of the screen. If the time of the most recent reading of the lower area is 0, no operation is required. In step S1106, if it is determined that the user has finished reading all the content of the page, a page-turning command can be sent to the reader module after a delay of 200ms to execute the page-turning operation for the application interface of the reading app.

[0293] The following is a detailed description of the process when a user switches from gazing at the upper region to gazing at the lower region. Referring to Figure 12, which shows a flowchart of the process when a user switches from gazing at the upper region to gazing at the lower region according to an embodiment of this application, the process may include steps S1201-S1212.

[0294] As shown in Figure 12, in step S1201, when the user switches from gazing at the upper area to gazing at the lower area of ​​the display interface, the gaze intent processing module can first remove all delay methods, that is, reset all delay times. In step S1202, the gaze intent processing module can record the current time as the time of the most recent reading of the lower area. In step S1203, the gaze intent processing module can also determine whether the time of the most recent reading of the upper area is 0. In step S1204, if it is determined that the time of the most recent reading of the upper area is 0, it can be determined that the user will directly look at the lower area. At this time, the page turning waiting time of this page can be directly estimated, and subsequent steps can be executed. The estimation method is similar to the estimation method in step S1007 of the embodiment shown in Figure 10, and will not be described again in this embodiment.

[0295] In step S1205, if the time of the most recent reading of the upper region is not 0, the time difference between the time of the most recent reading of the lower region and the time of the most recent reading of the upper region can be calculated and added to the user's cumulative reading time of the upper half of the screen. In step S1206, the gaze intent processing module can also estimate the user's page reading speed based on the cumulative reading time of the upper half of the screen and the amount of page information in the upper region.

[0296] In step S1207, the gaze intent processing module can determine whether the page reading speed is within a preset speed range. If yes, it can be determined that the page reading speed is within the normal range or does not have a large error; if no, it can be determined that the page reading speed does not fall within the normal range or has a large error.

[0297] In step S1208, when it is determined that the page reading speed is within the preset speed range (i.e., the page reading speed is within the normal range or there is no large error), the gaze intent processing module can estimate the user's estimated reading time in the lower area based on the amount of page information and the page reading speed in the lower area, and then estimate the user's remaining reading time in the lower area. The specific calculation formula is as follows:

[0298] Where T′ represents the remaining reading time, X2 represents the amount of page information in the lower area, and T2 represents the cumulative reading time of the lower half of the screen.

[0299] Optionally, in step S1209, when it is determined that the page reading speed is outside the preset speed range (i.e., the page reading speed does not conform to the normal range or has a large error), the gaze intent processing module can discard the calculated page reading speed, estimate the user's estimated reading time in the lower area based on the amount of page information in the lower area and the preset reading speed, and then estimate the user's remaining reading time in the lower area. The specific calculation formula is as follows:

[0300] V2 represents the preset reading speed.

[0301] Optionally, in step S1209, when it is determined that the page reading speed is outside the preset speed range (i.e., the page reading speed does not conform to the normal range or has a large error), the gaze intent processing module can also discard the calculated page reading speed, estimate the user's estimated reading time in the lower area based on the amount of page information in the lower area and the user's historical reading speed, and then estimate the user's remaining reading time in the lower area. The specific calculation formula is as follows:

[0302] V3 represents the user's historical reading speed.

[0303] In step S1210, the gaze intent processing module can also calculate whether the remaining reading time is within a preset time range. In step S1211, when the remaining reading time is within the preset time range, the gaze intent processing module can determine that the remaining reading time conforms to a reasonable duration range. This can then be directly used as the page-turning waiting time for the reading app's interface. In step S1212, when the remaining reading time is outside the preset time range, the gaze intent processing module can determine that the remaining reading time does not conform to a reasonable duration range. If the remaining reading time is less than the minimum value of the preset time range, the page-turning waiting time for the reading app's interface can be determined to be 2 seconds. If the remaining reading time is greater than the maximum value of the preset time range, the page-turning waiting time for the reading app's interface can be determined to be 9 seconds. That is, if the remaining reading time is less than the minimum value of the preset time range, at the earliest, it will take at least 2 seconds before proceeding to the next step. If the remaining reading time is greater than the maximum value of the preset time range, the next step will be executed no later than 9 seconds.

[0304] The following describes in detail the page-turning method provided in this application embodiment, taking the scenario of prompting the user to turn the page as an example. In this scenario, when it is determined that the user has finished reading all the content of the page, the mobile phone can prompt the user to turn the page, giving the user a clear psychological cue that their intention has been accurately identified.

[0305] Referring to Figure 13, which shows a flowchart of a page-turning method provided in another embodiment of this application, the method may include steps S1301-S1306.

[0306] S1301: The mobile phone displays the application interface of a reading app (as an example of a first application), which includes an upper area (as an example of a first display area) and a lower area (as an example of a second display area), the upper area and the lower area partially overlap or do not overlap at all.

[0307] S1302: The mobile phone determines that the user's gaze point relative to the application interface has moved from the upper area to the lower area.

[0308] S1303: The mobile phone responds to determining that the user's gaze point relative to the application interface has moved from the upper area to the lower area, and determines the page-turning waiting time for the reading app's application interface.

[0309] In this embodiment, to avoid triggering accidental page turning due to prompting the user to turn the page too quickly, or causing excessive waiting time due to not prompting the user to turn the page for too long, the estimated remaining reading time can be verified to determine whether it falls within a reasonable time range, and the page turning waiting time can be determined based on the verification result. Specific verification methods can be found in the relevant content of the embodiment shown in Figure 4, and will not be repeated here.

[0310] S1304: The phone responds to the user's gaze shifting from the upper area to the lower area, and after a page-turning wait time, displays a page-turning prompt in the application interface of the reading app.

[0311] In this embodiment, in response to determining that the user's gaze has moved from the upper area to the lower area, and after the current waiting time t reaches the page-turning waiting time T (i.e., determining that the user has finished reading all the content of the page), the mobile phone can also provide a page-turning prompt to guide the user to turn the page. Specifically, page-turning prompt information can be displayed in the application interface of a reading app. This prompt information can be used to remind the user to move their gaze from the lower area to the upper area for automatic page turning.

[0312] It should be noted that the content and display position of the page turning prompt can be preset according to the actual situation. For example, the page turning prompt can be set to "Look up, turn one page", and the display position of the page turning prompt can be set to the bottom of the page. This application embodiment does not impose specific restrictions on this.

[0313] S1305: The mobile phone determines that the user's gaze point has moved from the lower area to the upper area.

[0314] In this embodiment, the mobile phone can determine the page-turning intention while displaying the page-turning prompt information. The specific determination method can be found in the relevant content of the embodiment shown in Figure 4, and will not be repeated here.

[0315] S1306: The phone responds to the user's gaze shifting from the lower area to the upper area and performs a page-turning operation for the application interface of a reading app.

[0316] In this embodiment, the following scenario of abrupt change in recognition result exists: the user is looking at the lower area of ​​the application interface, and the user has been prompted to look up to turn the page, but the user does not look up, yet the algorithm makes a recognition error, resulting in a jump in the user's gaze point from bottom to top and then back down. In this scenario, page turning may be triggered erroneously, affecting the user experience. Therefore, to avoid this scenario, a 200ms page turning delay can be added. The specific delayed page turning method can be found in the relevant content of the embodiment shown in Figure 4, and will not be repeated here.

[0317] For example, referring to Figure 14a of the specification, Figure 14a illustrates a schematic diagram of a left-right page-turning process provided in one embodiment of this application. As shown in Figure 14a, when the user moves their gaze from position 1401 in the upper region to position 1402 in the lower region, the mobile phone can determine that the user's gaze has moved from the upper region to the lower region. In response to determining that the user's gaze has moved from the upper region to the lower region, and after a page-turning waiting time, the mobile phone can display a page-turning prompt message "Look up, turn a page" in the application interface 1410 of the reading app. Subsequently, when the user moves their gaze from position 1403 in the lower region to position 1404 in the upper region, the mobile phone can determine that the user's gaze has moved from the lower region to the upper region. In response to determining that the user's gaze has moved from the lower region to the upper region, the mobile phone can perform a left-right page-turning action for the application interface of the reading app after a delay of 200ms.

[0318] For example, referring to Figure 14b of the specification, Figure 14b illustrates a schematic diagram of a half-screen page-turning process provided in one embodiment of this application. As shown in Figure 14b, when the user moves their gaze from position 1405 in the upper region to position 1406 in the lower region, the mobile phone can determine that the user's gaze has moved from the upper region to the lower region. In response to determining that the user's gaze has moved from the upper region to the lower region, and after a page-turning waiting time, the mobile phone can display a page-turning prompt message "Look up, turn the page" in the application interface 1420 of the reading app. Subsequently, when the user moves their gaze from position 1407 in the lower region to position 1408 in the upper region, the mobile phone can determine that the user's gaze has moved from the lower region to the upper region. In response to determining that the user's gaze has moved from the lower region to the upper region, the mobile phone can perform a half-screen flip page-turning action for the application interface of the reading app after a delay of 200ms.

[0319] It should be noted that other contents in steps S1301 to S1306 in the embodiments of this application can be referred to the relevant contents in the embodiments shown in Figures 4 to 12, and will not be repeated here.

[0320] In one possible embodiment, when a user rotates the phone to switch from portrait to landscape mode, the phone can obtain the corresponding rotation direction, which can include rotating left or right. When rotating left, the phone's camera (i.e., image sensor) is rotated to the left; when rotating right, the camera is rotated to the right. The phone can also obtain the current interface following mode, which can include both following and non-following modes. In following mode, the application interface layout can change with the phone's rotation (i.e., from a top-bottom layout to a left-right layout); in non-following mode, the application interface layout may not change with the phone's rotation. The phone can switch the display interface and adjust the division of the two display areas based on the rotation direction and the current interface following mode.

[0321] The following detailed explanation uses the example of rotating the phone to the left and setting the interface to not follow.

[0322] For example, referring to Figure 15 of the specification, Figure 15 shows a schematic diagram of switching a mobile phone from portrait to landscape mode according to an embodiment of this application. When the user rotates the phone to the left, assuming the current interface follow mode is not followed, the positional relationship between the two display areas of the user interface does not change with the rotation of the phone and remains vertical. That is, after the phone is switched from portrait to landscape mode, the reading page remains upward. As shown in Figure 15, when the phone is in portrait display mode, the portrait application interface 1510 of the reading app can include an upper area and a lower area. The upper area of ​​the portrait application interface 1510 can include an upper grid 1501 and a transition area 1502, and the lower area of ​​the portrait application interface 1510 can include a transition area 1502 and a lower grid 1503. When the user rotates the phone to the left, the phone enters landscape mode. At this time, the application interface of the reading app switches to landscape application interface 1520. Landscape application interface 1520 can still include an upper area and a lower area. The upper area of ​​landscape application interface 1520 can include the upper grid 1504 and the transition area 1505, and the lower area of ​​landscape application interface 1520 can include the transition area 1505 and the lower grid 1506.

[0323] In this embodiment, when the interface following mode is not followed, although the layout of the application interface does not change after the phone switches from portrait to landscape mode, the position and angle of the phone's camera (i.e., image sensor) relative to the user's eyes will change under different display states (including portrait and landscape display states). Therefore, the phone can use different modes of gaze point interaction algorithms to identify the user's gaze point and determine the display area where the gaze point is located under different display states. For example, in the portrait display state, a gaze point interaction algorithm with a top-bottom area recognition mode can be used to identify the user's gaze point and determine the display area where the gaze point is located. In the landscape display state, a gaze point interaction algorithm with a left-right area recognition mode can be used to identify the user's gaze point and determine the display area where the gaze point is located. Different modes of gaze point interaction algorithms can correspond to different camera position parameters and angle parameters, etc.

[0324] Specifically, in left / right region recognition mode, the phone uses a gaze point interaction algorithm to determine whether the user's gaze point is located in the left or right region of the physical screen. Based on the phone's rotation direction, it maps the left and right regions of the physical screen to the top and bottom regions of the display interface, respectively, thus determining whether the application interface display area where the user's gaze point is located is the top or bottom region. Specifically, when rotating to the left, the left region of the physical screen is automatically mapped to the bottom region of the display interface, and the right region is mapped to the top region. When rotating to the right, the left region of the physical screen is automatically mapped to the top region of the display interface, and the right region is mapped to the bottom region.

[0325] In one specific embodiment, referring to Figure 16 of the specification, Figure 16 shows a flowchart of a page-turning method provided in another specific embodiment of this application, which further illustrates an embodiment of a mobile phone switching from portrait to landscape mode. The content of steps S1601 and S1604 to S1623 in the embodiment shown in Figure 16 is similar to the content of steps S601 to S621 in the embodiment shown in Figure 6. The same content will not be repeated here; only the differences will be described in detail.

[0326] As shown in Figure 16, in step S1602, when the user performs a rotation operation on the phone to switch the phone from portrait to landscape mode, the reader module can respond to the rotation operation, determine the phone's rotation direction and interface following mode, and switch the application interface of the reading app displayed on the phone based on the interface following mode. In step S1603, the reader module can notify the gaze point interaction engine of the rotation operation that switches the phone from portrait to landscape mode, and send the rotation direction and interface following mode of the rotation operation.

[0327] In step S1606, after receiving the user's facial image, the gaze point interaction engine can input the user's facial image into the gaze point interaction algorithm module for processing. Specifically, the gaze point interaction engine can determine relevant parameters (such as the position and angle of the image sensor relative to the user's eyes) based on the rotation direction, and input the facial image, relevant parameters, and interface following mode together into the gaze point interaction algorithm module. In step S1607, the gaze point interaction algorithm module can perform gaze point recognition processing on the facial image to obtain the user's gaze point coordinates relative to the application interface. In step S1608, the gaze point interaction algorithm module can also perform fence entry / exit judgment based on the gaze point coordinates to determine whether to trigger a fence event that switches the user's gaze point from the upper area to the lower area. Specifically, when the interface following mode is determined to be non-following, the gaze point interaction algorithm module can use a gaze point interaction algorithm with left and right area recognition mode to identify the user's gaze point and determine the area of ​​the physical screen where the gaze point is located. The gaze point interaction algorithm module can also determine the rotation direction of the rotation operation, and based on the rotation direction, map the left and right areas of the physical screen to the upper and lower areas of the display interface, respectively, thereby determining the display area of ​​the application interface where the gaze point is located, and then determining whether to trigger the fence event that switches the user's gaze point from the upper area gaze fence to the lower area gaze fence.

[0328] In step S1615, after receiving the user's facial image, the gaze point interaction engine can input the user's facial image into the gaze point interaction algorithm module for processing. The specific implementation process is similar to step S1606, and will not be repeated here. In step S1616, the gaze point interaction algorithm module can perform gaze point recognition processing on the facial image to obtain the user's gaze point coordinates relative to the application interface. In step S1617, the gaze point interaction algorithm module can also perform fence entry / exit judgment based on the gaze point coordinates to determine whether to trigger a fence event that triggers the user's gaze point to switch from the lower area to the upper area (i.e., determine that the user's gaze point has moved from the lower area to the upper area). The specific judgment method is similar to steps S1607 and S1608, and will not be repeated here.

[0329] It should be noted that other contents in steps S1601 to S1623 of the embodiment shown in Figure 16 can be referred to the relevant contents of the embodiment shown in Figure 6, and will not be repeated here in the embodiments of this application.

[0330] The following describes in detail another embodiment of the page-turning method provided in this application, using a mobile phone as an example. The mobile phone can be in portrait mode and has multiple apps installed, some or all of which provide information to the user. In the initial state, the user can choose whether they prefer to focus on the upper or lower half of the application interface, and the corresponding page-turning method is determined based on the user's selection.

[0331] The following section will first describe in detail the page-turning method provided in this application embodiment, assuming that the user habitually focuses on the upper half of the application interface. Referring to Figure 17, which shows a flowchart of another page-turning method provided in this application, the method may include steps S1701-S1705.

[0332] S1701: The mobile phone displays the application interface of a reading app (as an example of a second application), which includes an upper area (as an example of a first display area) and a lower area (as an example of a second display area), the upper area and the lower area partially overlap or do not overlap at all.

[0333] In this embodiment, the second application can be any application installed on the mobile phone that can provide information to the user. The second application can be of various types, including but not limited to reading apps, browser apps, and news feed apps. In this embodiment, a reading app is used as an example of the first application, but this application is not limited to this. The reading app can be an app with a scrolling page-turning mode or a swipe page-turning mode.

[0334] S1702: The mobile phone determines that the user's gaze point relative to the application interface has moved from the upper area to the lower area.

[0335] S1703: The mobile phone responds to determining that the user's gaze point relative to the application interface has moved from the upper area to the lower area, and after 1 second (as an example of the fourth preset time), adjusts the page scrolling speed of the reading app's application interface from the default scrolling speed (as an example of the first scrolling speed) to an accelerated scrolling speed (as an example of the second scrolling speed).

[0336] In this embodiment, since the reading app uses a scrolling or swiping page-turning mode, and the user typically focuses on the upper half of the application interface, when the phone determines that the user's gaze has moved from the upper area to the lower area, it can determine that the page scrolling speed is slower than the user's reading speed and needs to be increased. The phone can respond to this by determining that the user's gaze relative to the application interface has moved from the upper area to the lower area, and after 1 second, adjust the page scrolling speed of the reading app's interface from the default scrolling speed to an accelerated scrolling speed, thereby accelerating the page scrolling.

[0337] Both the default scrolling speed and the accelerated scrolling speed can be preset according to actual conditions. For example, the default scrolling speed can be set by the user, and the accelerated scrolling speed can be calculated based on the user-set default scrolling speed. For different users, the corresponding default scrolling speed and accelerated scrolling speed can be the same or different, and this application embodiment does not impose specific restrictions on this.

[0338] It should be noted that the above example of using 1s as the fourth preset time is only an exemplary implementation. In practical applications, the fourth preset time can also be set to other values, and this application embodiment does not impose specific limitations on this.

[0339] In one possible embodiment, the page-turning method may further include: the mobile phone determining an adjustment coefficient corresponding to the user, and determining an acceleration scrolling speed based on the adjustment coefficient. The adjustment coefficient corresponding to the user can be greater than 1 (i.e., the acceleration coefficient). The adjustment coefficient corresponding to the user can be preset according to actual conditions, for example, it can be set to 1.5. Different users can be set with the same adjustment coefficient or different adjustment coefficients; this application embodiment does not impose specific limitations in this regard.

[0340] Specifically, the accelerated scrolling speed can be obtained by multiplying the default scrolling speed by the user's corresponding adjustment factor. Since the adjustment factor is greater than 1, the calculated accelerated scrolling speed is greater than the default scrolling speed.

[0341] S1704: The mobile phone determines that the user's gaze point has moved from the lower area to the upper area.

[0342] S1705: The phone responds to the user's gaze point moving from the lower area to the upper area, and after 1 second (as an example of the fifth preset time), adjusts the page scrolling speed of the reading app's interface from the accelerated scrolling speed to the default scrolling speed.

[0343] In this embodiment, when the mobile phone determines that the user's gaze has moved from the lower area to the upper area, it can determine that the page scrolling speed is faster than the user's reading speed, and therefore the scrolling speed needs to be reduced. In response to determining that the user's gaze has moved from the lower area to the upper area, and after 1 second, the mobile phone adjusts the page scrolling speed of the reading app's interface from the accelerated scrolling speed back to the default scrolling speed, thereby restoring the page to its default speed.

[0344] It should be noted that the example of using 1s as the fifth preset time is only an exemplary implementation. In practical applications, the fifth preset time can also be set to other values, and this application embodiment does not impose specific limitations on this.

[0345] It should be noted that other contents in steps S1701 to S1705 in the embodiments of this application can be referred to the relevant contents in the embodiments shown in Figures 4 to 12, and will not be repeated here.

[0346] In one specific embodiment, referring to Figure 18 of the specification, Figure 18 shows a flowchart of a page-turning method provided by another specific embodiment of this application, which is a further illustration of the embodiment shown in Figure 17. The contents of steps S1801 to S1808 and S1811 to S1817 in the embodiment shown in Figure 18 are similar to the contents of steps S601 to S608 and S611 to S617 in the embodiment shown in Figure 6, respectively. Therefore, the embodiments of this application will not repeat the details here; only the contents different from those in the embodiment shown in Figure 6 will be described in detail.

[0347] As shown in Figure 18, in step S1809, the gaze intent processing module can respond to the fence event where the user's gaze point switches from the upper area gaze fence to the lower area gaze fence, and after 1 second, send an accelerated scrolling command to the reader module. In step S1810, the reader module can respond to the accelerated scrolling command and execute accelerated scrolling operation for the application interface of the reading app.

[0348] It should be noted that steps S1809 to S1810 correspond to step S1703 in the embodiment shown in Figure 17.

[0349] As shown in Figure 18, in step S1818, the gaze intent processing module can respond to the fence event where the user's gaze point switches from the lower area gaze fence to the upper area gaze fence, and after 1 second, send a scroll speed recovery command to the reader module. In step S1819, the reader module can respond to the scroll speed recovery command and perform a scroll speed recovery operation for the application interface of the reading app.

[0350] It should be noted that steps S1818 to S1819 correspond to step S1705 in the embodiment shown in Figure 17.

[0351] It should be noted that other contents in steps S1801 to S1819 of the embodiment shown in Figure 18 can refer to the relevant contents of the embodiment shown in Figure 6, and will not be repeated here in the embodiments of this application.

[0352] By way of example, referring to Figure 19 of the specification, Figure 19 shows a schematic diagram of accelerated scrolling page turning provided in one embodiment of this application. As shown in Figure 19, when the user moves their gaze from position 1901 in the upper region to position 1902 in the lower region, the mobile phone can determine that the user's gaze has moved from the upper region to the lower region. In response to determining that the user's gaze has moved from the upper region to the lower region, and after 1 second, the mobile phone adjusts the page scrolling speed of the application interface 1910 from the default scrolling speed to an accelerated scrolling speed, thereby accelerating the scrolling of the page of the application interface 1910.

[0353] As shown in Figure 19, when the user moves their gaze from position 1903 in the lower region to position 1904 in the upper region, the mobile phone can determine that the user's gaze has moved from the lower region to the upper region. In response to determining that the user's gaze has moved from the lower region to the upper region, the mobile phone can, after 1 second, adjust the page scrolling speed of the application interface 1910 from the accelerated scrolling speed back to the default scrolling speed, thereby restoring the page scrolling speed of the application interface 1910.

[0354] The following describes in detail the page-turning method provided in this application embodiment, assuming the user habitually focuses on the lower half of the application interface. Referring to Figure 20, which shows a flowchart of another embodiment of the page-turning method provided in this application, the method may include steps S2001-S2005.

[0355] S2001: The mobile phone displays the application interface of a reading app (as an example of a second application), which includes an upper area (as an example of a first display area) and a lower area (as an example of a second display area), the upper area and the lower area partially overlap or do not overlap at all.

[0356] S2002: The mobile phone determines that the user's gaze point relative to the application interface has moved from the lower area to the upper area.

[0357] S2003: The mobile phone responds to determining that the user's gaze point relative to the application interface has moved from the lower area to the upper area, and after 1 second (as an example of the fourth preset time), adjusts the page scrolling speed of the reading app's application interface from the default scrolling speed (as an example of the first scrolling speed) to a decelerated scrolling speed (as an example of the second scrolling speed).

[0358] In this embodiment, since the reading app uses a scrolling or swiping page-turning mode, and the user typically focuses on the lower half of the application interface, when the phone determines that the user's gaze has moved from the lower area to the upper area, it can determine that the page scrolling speed is faster than the user's reading speed and therefore needs to be reduced. The phone can respond to this determination by shifting the user's gaze relative to the application interface from the lower to the upper area, and after 1 second, adjust the page scrolling speed of the reading app's interface from the default speed to a decelerated scrolling speed, thereby slowing down the page scrolling.

[0359] Both the default scrolling speed and the deceleration scrolling speed can be preset according to actual conditions. For example, the default scrolling speed can be set by the user, and the deceleration scrolling speed can be calculated based on the user-set default scrolling speed. For different users, the corresponding default scrolling speed and deceleration scrolling speed can be the same or different, and this embodiment does not impose specific restrictions on this.

[0360] It should be noted that the above example of using 1s as the fourth preset time is only an exemplary implementation. In practical applications, the fourth preset time can also be set to other values, and this application embodiment does not impose specific limitations on this.

[0361] In one possible embodiment, the page-turning method may further include: the mobile phone determining an adjustment coefficient corresponding to the user, and determining a deceleration scrolling speed based on the adjustment coefficient. The adjustment coefficient corresponding to the user may be less than 1 (i.e., a deceleration coefficient). The adjustment coefficient corresponding to the user can be preset according to actual conditions, for example, it can be set to 0.5. Different users may be set with the same adjustment coefficient or different adjustment coefficients; this application embodiment does not impose specific limitations on this.

[0362] Specifically, the decelerated scrolling speed can be obtained by multiplying the default scrolling speed by the user's corresponding adjustment factor. Since the adjustment factor is less than 1, the calculated decelerated scrolling speed is less than the default scrolling speed.

[0363] S2004: The mobile phone determines that the user's gaze point has moved from the upper area to the lower area.

[0364] S2005: The mobile phone responds to the determination that the user's gaze point has moved from the upper area to the lower area, and after 1 second (as an example of the fifth preset time), adjusts the page scrolling speed of the reading app's application interface from the decelerated scrolling speed to the default scrolling speed.

[0365] In this embodiment, when the mobile phone determines that the user's gaze has moved from the upper area to the lower area, it can determine that the page scrolling speed is slower than the user's reading speed, and the scrolling speed needs to be increased. In response to determining that the user's gaze has moved from the upper area to the lower area, and after 1 second, the mobile phone adjusts the page scrolling speed of the reading app's interface from the decelerated scrolling speed back to the default scrolling speed, thereby restoring the page to its default speed.

[0366] It should be noted that the example of using 1s as the fifth preset time is only an exemplary implementation. In practical applications, the fifth preset time can also be set to other values, and this application embodiment does not impose specific limitations on this.

[0367] It should be noted that other contents in steps S2001 to S2005 in the embodiments of this application can be referred to the relevant contents in the embodiments shown in Figures 4 to 12 and Figures 17 to 19, and will not be repeated here.

[0368] In one specific embodiment, referring to Figure 21 of the specification, Figure 21 shows a flowchart of a page-turning method provided by another specific embodiment of this application, which is a further illustration of the embodiment shown in Figure 20. The contents of steps S2101 to S2108 and steps S2111 to S2117 in the embodiment shown in Figure 21 are similar to the contents of steps S601 to S608 and S611 to S617 in the embodiment shown in Figure 6, respectively. Therefore, the embodiments of this application will not repeat the details here; only the contents different from those in the embodiment shown in Figure 6 will be described in detail.

[0369] As shown in Figure 21, in step S2109, the gaze intent processing module can respond to the fence event where the user's gaze point switches from the lower area gaze fence to the upper area gaze fence, and after 1 second, send a deceleration scrolling command to the reader module. In step S2110, the reader module can respond to the deceleration scrolling command and perform a deceleration scrolling operation on the application interface of the reading app.

[0370] It should be noted that steps S2109 to S2110 correspond to step S2003 in the embodiment shown in FIG20.

[0371] As shown in Figure 21, in step S2118, the gaze intent processing module can respond to the fence event where the user's gaze point switches from the upper area gaze fence to the lower area gaze fence, and after 1 second, send a scroll speed recovery command to the reader module. In step S2119, the reader module can respond to the scroll speed recovery command and perform a scroll speed recovery operation for the application interface of the reading app.

[0372] It should be noted that steps S2118 to S2119 correspond to step S2005 in the embodiment shown in FIG20.

[0373] It should be noted that other contents in steps S2101 to S2119 of the embodiment shown in Figure 21 can refer to the relevant contents in the embodiment shown in Figure 6, and will not be repeated here in the embodiments of this application.

[0374] By way of example, referring to Figure 22 of the specification, Figure 22 shows a schematic diagram of a decelerated scrolling page turning method provided in one embodiment of this application. As shown in Figure 22, when the user moves their gaze point from position 2201 in the lower region to position 2202 in the upper region, the mobile phone can determine that the user's gaze point has moved from the lower region to the upper region. In response to determining that the user's gaze point has moved from the lower region to the upper region, and after 1 second, the mobile phone adjusts the page scrolling speed of the application interface 2210 from the default scrolling speed to a decelerated scrolling speed, thereby causing the page of the application interface 2210 to scroll at a decelerated speed.

[0375] As shown in Figure 22, when the user moves their gaze from position 2203 in the upper region to position 2204 in the lower region, the mobile phone can determine that the user's gaze has moved from the upper region to the lower region. In response to determining that the user's gaze has moved from the upper region to the lower region, and after 1 second, the mobile phone adjusts the page scrolling speed of the application interface 2210 from a decelerated scrolling speed to the default scrolling speed, thereby restoring the page scrolling speed of the application interface 2210.

[0376] Furthermore, in the above embodiments, only the portrait mode was described. The page turning method in the landscape mode can be the same as the page turning method in the portrait mode. For details, please refer to the page turning process in the portrait mode, which will not be repeated here.

[0377] This application also provides an electronic device, including:

[0378] Memory, used to store instructions executed by one or more processors of an electronic device, and

[0379] When the processor executes instructions in the memory, it causes the electronic device to perform the page-turning method shown in Figures 4 to 22 of the above embodiments.

[0380] This application also provides a computer-readable storage medium storing instructions that, when executed by a processor, cause the processor to perform the page-turning method shown in Figures 4 to 22 of the above embodiments.

[0381] This application also provides a computer program product containing instructions that, when the computer program product is run on an electronic device, cause the processor to execute the page-turning method shown in Figures 4 to 22 of the above embodiments.

[0382] Referring now to FIG. 23, a block diagram of an electronic device 2300 according to an embodiment of the present application is shown. The electronic device 2300 may include one or more processors 2301 coupled to a controller hub 2303. In at least one embodiment, the controller hub 2303 communicates with the processor 2301 via a multi-branch bus such as a Front Side Bus (FSB), a point-to-point interface such as a Quick Path Interconnect (QPI), or a similar connection 2306. The processor 2301 executes instructions controlling general-type data processing operations. In one embodiment, the controller hub 2303 includes, but is not limited to, a Graphics Memory Controller Hub (GMCH) (not shown) and an Input / Output Hub (IOH) (which may be on a separate chip) (not shown), wherein the GMCH includes memory and a graphics controller and is coupled to the IOH.

[0383] Electronic device 2300 may also include a coprocessor 2302 and a memory 2304 coupled to a controller hub 2303. Alternatively, one or both of the memory and GMCH may be integrated within the processor (as described in this application), with memory 2304 and coprocessor 2302 directly coupled to processor 2301 and controller hub 2303, which is on a single chip with IOH.

[0384] Memory 2304 may be, for example, Dynamic Random Access Memory (DRAM), Phase Change Memory (PCM), or a combination of both. As a computer-readable storage medium, memory 2304 may include one or more tangible, non-transitory computer-readable media for storing data and / or instructions. For example, memory 2304 may include any suitable non-volatile memory such as flash memory and / or any suitable non-volatile storage device, such as one or more hard-disk drives (HDD(s)), one or more compact disc (CD) drives, and / or one or more digital versatile disc (DVD) drives.

[0385] According to some embodiments of this application, the memory 2304, which is a computer-readable storage medium, stores instructions that, when executed on a computer, cause the system 2300 to execute the display method of the floating ball control according to the above embodiments. Specifically, refer to the page-turning method shown in Figures 4 to 22 in the above embodiments, which will not be described again here.

[0386] In one embodiment, the coprocessor 2302 is a dedicated processor, such as, for example, a high-throughput many-integrated-core (MIC) processor, a network or communication processor, a compression engine, a graphics processor, a general-purpose graphics processor (GPGPU), or an embedded processor, etc. Optional properties of the coprocessor 2302 are indicated by dashed lines in Figure 23.

[0387] In one embodiment, electronic device 2300 may further include a Network Interface Controller (NIC) 2306. The network interface 2306 may include a transceiver for providing a radio interface for electronic device 2300 to communicate with any other suitable device (such as a front-end module, antenna, etc.). In various embodiments, the network interface 2306 may be integrated with other components of electronic device 2300. The network interface 2306 can implement the functions of the communication unit in the above embodiments.

[0388] Electronic device 2300 may further include input / output (I / O) devices 2305. I / O 2305 may include: a user interface designed to enable a user to interact with electronic device 2300; a peripheral component interface designed to enable peripheral components to also interact with electronic device 2300; and / or sensors designed to determine environmental conditions and / or location information related to electronic device 2300.

[0389] It is worth noting that Figure 23 is merely exemplary. That is, although Figure 23 shows that the electronic device 2300 includes multiple devices such as a processor 2301, a controller hub 2303, and a memory 2304, in actual applications, devices using the methods of this application may include only a subset of the devices in the electronic device 2300; for example, it may only include the processor 2301 and the network interface 2306. The nature of the optional devices in Figure 23 is shown with dashed lines.

[0390] Referring now to FIG. 24, a block diagram of a SoC (System on Chip) 2400 according to an embodiment of this application is shown. In FIG. 24, similar components have the same reference numerals. Additionally, dashed boxes represent optional features of more advanced SoCs. In FIG. 24, the SoC 2400 includes: an interconnect unit 2450 coupled to a processor 2410; a system proxy unit 2470; a bus controller unit 2480; an integrated memory controller unit 2440; a group or one or more coprocessors 2420, which may include integrated graphics logic, an image processor, an audio processor, and a video processor; a static random access memory (SRAM) unit 2430; and a direct memory access (DMA) unit 2460. In one embodiment, the coprocessor 2420 includes a dedicated processor, such as, for example, a network or communication processor, a compression engine, a GPGPU, a high-throughput MIC processor, or an embedded processor.

[0391] The static random access memory (SRAM) cell 2430 may include one or more tangible, non-transitory computer-readable storage media for storing data and / or instructions. The computer-readable storage medium may store instructions, specifically temporary and permanent copies of those instructions. These instructions may include, when executed by at least one unit in the processor, causing the SoC 2400 to perform the display method of the floating ball control according to the above embodiments, specifically referring to the page-turning methods shown in Figures 4 to 22 of the above embodiments, which will not be repeated here.

[0392] The various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. Embodiments of this application can be implemented as computer programs or program code executable on a programmable system, the programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0393] Program code can be applied to input instructions to execute the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, the processing system includes any system having a processor such as, for example, a Digital Signal Processor (DSP), a microcontroller, an Application Specific Integrated Circuit (ASIC), or a microprocessor.

[0394] The program code can be implemented using a high-level procedural language or an object-oriented programming language to communicate with the processing system. Assembly language or machine language can also be used when needed. In fact, the mechanisms described in this application are not limited to any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0395] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored thereon on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or through other computer-readable media. Therefore, machine-readable media may include any mechanism for storing or transmitting information in a machine-readable (e.g., computer-readable) form, including but not limited to floppy disks, optical disks, CD-ROMs, compact disc read-only memory (CD-ROMs), magneto-optical disks, read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic cards or optical cards, flash memory, or tangible machine-readable storage for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in the form of electrical, optical, acoustic, or other forms of propagated signals. Therefore, machine-readable media includes any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a machine-readable (e.g., computer-readable) form.

[0396] In the accompanying drawings, some structural or methodological features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be necessary. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the accompanying drawings. Furthermore, including structural or methodological features in a particular figure does not imply that such features are required in all embodiments, and in some embodiments, these features may be omitted or may be combined with other features.

[0397] It should be noted that all units / modules mentioned in the device embodiments of this application are logical units / modules. Physically, a logical unit / module can be a physical unit / module, a part of a physical unit / module, or a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important factor; the combination of functions implemented by these logical units / modules is the key to solving the technical problems proposed in this application. Furthermore, to highlight the innovative aspects of this application, the above-described device embodiments of this application have not introduced units / modules that are not closely related to solving the technical problems proposed in this application. This does not mean that the above-described device embodiments do not contain other units / modules.

[0398] It should be noted that in the examples and description of this application, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, 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. Without further limitations, 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 said element.

[0399] Although this application has been illustrated and described with reference to certain preferred embodiments thereof, those skilled in the art should understand that various changes in form and detail may be made thereto without departing from the spirit and scope of this application.

Claims

1. A page-turning method for an electronic device, characterized in that, The method includes: Display the application interface of the first application, the application interface including a first display area and a second display area, the first display area and the second display area partially overlap or do not overlap at all; In response to determining that the user's gaze point relative to the application interface moves from the first display area to the second display area, the page-turning wait time of the application interface of the first application is determined; In response to determining that the user's gaze point has moved from the first display area to the second display area, after the page-turning waiting time has elapsed, and in response to determining that the user's gaze point has moved from the second display area to the first display area, a page-turning operation for the application interface of the first application is performed.

2. The method according to claim 1, characterized in that, The method further includes: In response to determining that the user's gaze point has moved from the first display area to the second display area, after the page-turning waiting time, a page-turning prompt message is displayed in the application interface of the first application; The page-turning prompt information is used to prompt the user to move their gaze from the second display area to the first display area in order to turn the page.

3. The method according to claim 1, characterized in that, The step of determining that the user's gaze point relative to the application interface has moved from the first display area to the second display area includes: The display area where the user's gaze point is currently located is determined as the second display area, and the display area where the user's gaze point was previously located is determined as the first display area; Wherein, determining that the user's gaze point moves from the second display area to the first display area includes: The display area where the user's gaze point is currently located is determined as the first display area, and the display area where the user's gaze point was previously located is determined as the second display area; The display area where the user's gaze point is currently located and the display area where it was previously located are determined based on at least one frame of the user's facial image.

4. The method according to claim 1, characterized in that, Determining the page-turning wait time of the application interface of the first application includes: Determine the user's page reading speed within the first display area; The remaining reading time of the user in the second display area is estimated based on the page reading speed; The page-turning waiting time is determined based on the remaining reading time.

5. The method according to claim 4, characterized in that, Determining the user's page reading speed within the first display area includes: Obtain the first cumulative time that the user's gaze has lingered within the first display area; The page reading speed is determined based on the first cumulative time and the amount of page information within the first display area.

6. The method according to claim 4, characterized in that, The step of estimating the user's remaining reading time in the second display area based on the page reading speed includes: When the page reading speed is within a preset speed range, the estimated reading time of the user in the second display area is determined based on the amount of page information in the second display area and the page reading speed. When the page reading speed is outside the preset speed range, the estimated reading time of the user in the second display area is determined based on the amount of page information in the second display area and the preset reading speed or the user's historical reading speed. The remaining reading time is determined based on the estimated reading time and the second cumulative time that the user's gaze has lingered in the second display area.

7. The method according to claim 4, characterized in that, Determining the page-turning waiting time based on the remaining reading time includes: When the remaining reading time is within a preset time range, the page-turning waiting time is determined as the remaining reading time; When the remaining reading time is less than the minimum value of the preset time range, the page-turning waiting time is determined to be the first preset time; When the remaining reading time is greater than the maximum value of the preset time range, the page-turning waiting time is determined to be the second preset time.

8. The method according to claim 1, characterized in that, The step of performing a page-turning operation on the application interface of the first application includes: In response to determining that the user's gaze point has moved from the second display area to the first display area, after a third preset time, a page-turning operation is performed on the application interface of the first application.

9. The method according to claim 8, characterized in that, The method further includes: Within the third preset time period, in response to determining that the user's gaze point has moved from the first display area to the second display area, the page-turning operation for the application interface of the first application is abandoned.

10. A page-turning method for an electronic device, characterized in that, The method includes: The application interface of the second application is displayed. The application interface includes a first display area and a second display area, and the first display area and the second display area may partially overlap or not overlap at all. In response to determining that the user's gaze point relative to the application interface has moved from the first display area to the second display area, and after a fourth preset time, the page scrolling speed of the application interface of the second application is adjusted from the first scrolling speed to the second scrolling speed.

11. The method according to claim 10, characterized in that, The method further includes: Determine the adjustment coefficient corresponding to the user; The second rolling speed is determined based on the adjustment coefficient.

12. The method according to claim 10, characterized in that, The method further includes: In response to determining that the user's gaze point has moved from the second display area to the first display area, and after a fifth preset time, the page scrolling speed of the application interface of the second application is adjusted from the second scrolling speed to the first scrolling speed.

13. An electronic device, characterized in that, include: A memory for storing instructions executed by one or more processors of the electronic device; The processor, when executing the instructions in the memory, causes the electronic device to perform the page-turning method according to any one of claims 1 to 12.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the page-turning method according to any one of claims 1 to 12.

Images