Playback record display method and device

Abstract

The present application discloses a method and device for displaying playback records, and relates to the technical field of devices. The device can choose to display the historical playback records of a single account or the historical playback records of multiple users according to the number of viewing users in front of the screen. In this solution, the device displays a first interface, and the first interface includes a first control, and the first control is used to trigger the first device to display the historical playback records of the first account that has logged in; in response to the triggering operation on the first control, the device can display a second interface according to the number of viewing users in front of the screen of the first device; wherein, when the number of viewing users in front of the screen of the first device is one, the historical playback records of the first account are displayed in the second interface; when the number of viewing users in front of the screen of the first device is n, the historical playback records of the accounts of m users are displayed in the second interface, where n is an integer greater than 1, and m is an integer not greater than n, and the accounts of m users include the first account.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of device technology, and in particular to a method and device for displaying a playback record. Background Art

[0002] With the rapid development of multimedia technology and Internet technology, the massive growth of multimedia content such as audio and video is greatly filling the lives of modern people. Various devices that can present multimedia content are emerging in an endless stream, such as smart screens, smart TVs and other large-screen devices. At present, users usually play corresponding multimedia content through multimedia applications installed on their devices, such as video applications, music applications, etc.

[0003] When a user plays multimedia content through an application on a device, the device will save the historical playback record of the user's multimedia content in the application. However, a device can only log in to one user's account at a time. When different users need to view the content they have played before, they need to first scan the login QR code on the device, or manually switch to log in to their own account by entering the account password, and then enter the corresponding application and open the historical playback record to view the content they have played before. The whole operation process is relatively cumbersome. And if the current user's account is not logged out, and there are other users playing the same multimedia content through the application, the playback progress of other users will also be updated to the historical playback record of the application, resulting in the current user's real historical playback record in the application being overwritten, and the current user cannot retrieve his historical playback record, which brings inconvenience to the user. Summary of the invention

[0004] The present application provides a method and device for displaying playback records. The device can choose to display the historical playback records of a single account or the historical playback records of multiple users according to the number of viewing users in front of the screen, and intelligently display the historical playback records that are suitable for the user needs in the current viewing scene according to the current viewing scene, without the need for the user to manually log out of one account and then manually switch to log in to another account.

[0005] In order to achieve the above objectives, this application adopts the following technical solutions:

[0006] In a first aspect, a method for displaying a playback record is provided, which can be applied to a first device. In the method, the first device displays a first interface, the first interface includes a first control, and the first control is used to trigger the first device to display the historical playback record of the logged-in first account; in response to the triggering operation on the first control, a second interface is displayed according to the number of viewing users in front of the screen of the first device; wherein, the second interface is displayed according to the number of viewing users in front of the screen of the first device, including: when the number of viewing users in front of the screen of the first device is one, the historical playback record of the first account is displayed in the second interface; when the number of viewing users in front of the screen of the first device is n, the historical playback record of the accounts of m users is displayed in the second interface, where n is an integer greater than 1, m is an integer not greater than n, and the accounts of m users include the logged-in first account.

[0007] Optionally, the first device is a device with a display screen, such as a smart TV, smart screen or other large-screen devices.

[0008] Optionally, the first interface is the main interface of the first device. The main interface may include options such as input source options, video options, and music options. The second interface is an interface for displaying historical playback records. The second interface may only display the historical playback records of a single account, or may display the historical playback records of multiple accounts. As an example, the first control may be a control for the video option in the main interface, and correspondingly, the second interface is used to display the historical playback records of the video. As another example, the first control may be a control for the music option in the main interface, and correspondingly, the second interface is used to display the historical playback records of the music. In the solution provided in the first aspect above, the first device can identify the number of viewing users in front of the screen of the first device when the playback record needs to be displayed, so that when there is only one user watching in front of the screen of the first device, the first device can adaptively display the historical playback records of the logged-in single account, and when there are n users watching in front of the screen of the first device, the first device can adaptively display the historical playback records of m users, wherein the accounts of the m users include the currently logged-in account, and m is an integer not greater than n. In this way, the first device can intelligently display the historical playback records adapted to the user needs in the current viewing scene according to the current viewing scene. Furthermore, in a scenario where multiple users are watching, the first device can realize the sharing of historical playback records among multiple users by displaying the historical playback records of multiple users, thereby improving the interactive experience of multiple users watching.

[0009] Optionally, m may be equal to n. In this way, when n users are watching in front of the screen of the first device, the first device can adaptively display the historical playback records of the n users, thereby realizing the sharing of historical playback records of all users in the current viewing scene.

[0010] Optionally, m may be less than n. In this way, when n users are watching in front of the screen of the first device, the first device can adaptively display the historical playback records of some of the n users, thereby realizing the sharing of the historical playback records of all users in the current viewing scene. The selection of m is not limited. For example, the m users may be users among the n users who have used the first device in the current month, or the m users may be users among the n users who use the first device more frequently than a preset frequency.

[0011] In one possible implementation, the first device is controlled by the second device, the first account is the account of the first user, and the first user is the user who is in front of the screen of the first device and operates the second device. Optionally, the second device may be a device used to assist in realizing the relevant functions of the first device, such as a remote control. In this way, when the first device has logged in to the account of the first user who is currently operating the second device, if only the first user who is operating the second device is watching the screen of the first device, the first device can adaptively display only the historical playback records of the first user's account. If there are n users watching the screen of the first device, that is, not only the first user but also other users are watching, the first device can also adaptively display the historical playback records of the accounts of m users among the n users, where the accounts of the m users include the account of the currently logged in first user.

[0012] In one possible implementation, when the first account is not the account of the first user, a prompt message is displayed, and the prompt message is used to prompt whether to switch to the account of the first user; in response to the confirmation operation for the account of the first user in the prompt message, the first account is logged out, and the account of the first user is switched to log in. In this way, the first device can identify whether the currently logged in account is the account of the user currently operating the second device. When it is identified that the currently logged in account is not the account of the user currently operating the remote control, the account of the user currently operating the remote control can be quickly displayed, and the user can be prompted whether to switch accounts, so that the user currently operating the remote control can easily complete the account switch by simply confirming the operation, without the need for the user to manually log out of the account and then manually log in to his own account.

[0013] In one possible implementation, when the first device has switched to log in to the account of the first user, after displaying the historical playback records of the logged-in first account in the second interface, the method further includes: displaying the historical playback records of the first user's account in the second interface. In this way, after the user currently operating the remote control completes the account switching by simply confirming the operation, since the currently logged-in account has been changed to the account of the first user, the first device can adaptively display the historical playback records of the first user's account in the second interface. Optionally, the first device can switch the historical playback records of the first account displayed in the second interface to display the historical playback records of the first user's account.

[0014] Similarly, when the number of viewers in front of the screen of the first device is n, since the historical playback records of the accounts of m users displayed in the second interface include the historical playback records of the logged-in first account, after the user currently operating the remote control completes the account switching by simply confirming the operation, the first device can adaptively switch the historical playback records of the first account in the historical playback records of the accounts of m users displayed to the historical playback records of the first user's account.

[0015] In a possible implementation, when the number of users watching on the screen of the first device is n, the prompt information includes the account information of m users, wherein the account of the first user is highlighted in the account information. In this way, in a multi-user viewing scenario, when the first device recognizes that the currently logged-in account is not the account of the user currently operating the remote control, it can not only quickly display the account of the user currently operating the remote control, but also quickly display the account information of other users in the current viewing scenario. And because the user's own account is highlighted, the user currently operating the remote control can also quickly view his own account.

[0016] In one possible implementation, the method further includes: in response to a confirmation operation on a second account in the account information, logging out of the first account and switching to the second account, wherein the second account is an account other than the first account among the m users' accounts. In this way, after the first device quickly displays the account information of the m users, the user currently operating the remote control can conveniently switch between multiple user accounts in the current viewing scene by simply selecting and confirming. In this way, the user currently operating the remote control can choose to switch to his own account or to switch to the account of another user.

[0017] In one possible implementation, when the first device has switched to log in to the second account, after displaying the historical playback records of the logged-in first account in the second interface, the method further includes: displaying the historical playback records of the second account in the second interface. In this way, after the user currently operating the remote control switches to log in to the second account by simply selecting and confirming, since the currently logged-in account has been changed to the second account, the first device can adaptively display the historical playback records of the second account in the second interface. Optionally, the first device can switch the historical playback records of the first account displayed in the second interface to display the historical playback records of the second account.

[0018] Similarly, when the number of viewers in front of the screen of the first device is n, since the historical playback records of the accounts of m users displayed in the second interface include the historical playback records of the logged-in first account, after the user currently operating the remote control switches to log in to the second account by simply selecting and confirming, the first device can adaptively switch the historical playback records of the first account in the historical playback records of the accounts of m users displayed to the historical playback records of the second account.

[0019] In a possible implementation, displaying the historical playback records of the accounts of m users in the second interface includes: displaying the integrated historical playback records in the second interface, where the integrated historical playback records are playback records after the historical playback records of the accounts of m users are integrated. In this way, when there are n users watching in front of the screen of the first device, the first device can adaptively integrate and display the historical playback records of m users among the n users, realizing another kind of historical playback record display that is different from only displaying the historical playback records of a single logged-in account, that is, the integrated historical playback record display of multiple accounts.

[0020] In a possible implementation, displaying the historical playback records of m user accounts in the second interface includes: displaying the historical playback records of the first account in the second interface, and fusing the historical playback records, wherein the fused historical playback records are playback records after the historical playback records of the m user accounts are fused. In this way, when there are n users watching in front of the screen of the first device, the first device can not only display the historical playback records of the single account that has been logged in, but also can display the historical playback records of m users among the n users in a fused manner. In this way, the user can not only conveniently browse the historical playback records of the currently logged in account, but also browse the historical playback records of other users who are currently watching together.

[0021] Optionally, the historical play records of the first account and the fused historical play records are displayed side by side in the second interface. For example, the historical play records of the first account are displayed on the left side of the second interface, and the fused historical play records are displayed in the middle or on the right side.

[0022] In one possible implementation, displaying the integrated historical playback record includes: displaying the playback progress of the same file played by the accounts of m users in the same playback progress bar, wherein the display styles of the playback progress of different user accounts in the playback progress bar are different. In this way, the first device integrates the playback progress of the same multimedia file by different users into a playback progress bar for display, so that the user can intuitively understand the difference in playback progress between different users in the current viewing scene, or which users have watched the same multimedia file.

[0023] In one possible implementation, the method further includes: in response to a confirmation operation on a first playback progress in the playback progress bar, playing the file at the first playback progress, wherein the first playback progress is the playback progress of an account of any one of the m users. In this way, the user can conveniently select to play the multimedia file at the playback progress of any one of the m users by simply selecting and confirming the playback progress condition that integrates the playback information of multiple users.

[0024] In one possible implementation, the method further includes: displaying account information corresponding to the playback progress bar on the playback progress bar, the account information being account information of a user who has played the file among the m users; and in response to a confirmation operation on a third account in the account information, playing the file with the playback progress of the third account. In this way, the first device, by displaying the user account information corresponding to the playback progress bar, facilitates the user to directly select and confirm an account to conveniently select to play the multimedia file with the playback progress of any user in the current viewing scene.

[0025] In a possible implementation, when a first playback progress bar corresponding to a first file and a second playback progress bar corresponding to a second file are displayed in the second interface, the method further includes: when the number of users who play the first file is greater than the number of users who play the second file, arranging and displaying the first playback progress bar before the second playback progress bar, wherein the playing user is a user among the m users. In this way, when there are multiple playback progress bars of multimedia files in the fusion history playback record, the playback progress bars can be arranged from most to least according to the number of users who have played the file in the current scene.

[0026] In a possible implementation, when the number of users playing the first file is the same as the number of users playing the second file, the method further includes: when the difference between the various play progress of the first file is less than the difference between the various play progress of the second file, arranging and displaying the first play progress bar before the second play progress bar; and / or when the score value of the first file is greater than the score value of the second file, arranging and displaying the first play progress bar before the second play progress bar. In this way, when there are multiple play progress bars with the same number of play users, the first device can also arrange the play progress bars according to the play progress difference between users and / or the score of the multimedia file.

[0027] Optionally, the first device may further arrange the playback progress bar in combination with the currently logged-in account, so as to display the playback progress bar of the file played by the currently logged-in account in front.

[0028] Optionally, the first device may also construct the account of the user currently operating the second device and arrange the play progress bar so that the play progress bar of the file played by the user currently operating the second device is displayed in the front. This solution does not limit the arrangement of multiple play progress bars.

[0029] In one possible implementation, the historical playback records are historical playback records in multiple applications, and the method further includes: displaying a corresponding application icon on each historical playback record. In this way, the first device can display the historical playback records of the user in different applications together. In order to facilitate the user to understand the source of the historical playback record, the first device can also display the application icon corresponding to the source of the historical playback record when displaying the historical playback record.

[0030] In one possible implementation, before displaying the historical playback records of the accounts of m users in the second interface, the method further includes: acquiring an image in front of the screen of the first device; identifying the identities of n users watching in front of the screen of the first device based on the image, the identities including registered account users or unregistered account users; acquiring the historical playback records of the accounts of m users, where the m users are all registered users located in front of the screen of the first device. In this way, the first device can identify the identity information of the users watching in front of the screen by capturing the image in front of the screen to determine which user is a registered user and which user is an unregistered user. When there are m registered users in front of the screen, the first device can adaptively display the historical playback records of the accounts of the m registered users in front of the screen.

[0031] Optionally, a registered user can also perform privacy protection settings and choose not to share his / her historical play records. In this way, the fused historical play records displayed by the first device will not include the historical play records of the user set to privacy protection.

[0032] In one possible implementation, the first device is controlled by the second device, and the n users include the user operating the second device. The method further includes: performing human gesture recognition on the image to identify the user operating the second device in front of the screen of the first device; or identifying the user operating the second device in front of the screen of the first device based on the position and image of the user operating the second device determined by ultrasonic positioning. In this way, the first device can accurately identify the user operating the second device in the current viewing scene through human gesture recognition or ultrasonic positioning technology or other methods. Then, the identity information of the user operating the second device is identified.

[0033] In a second aspect, a method for displaying playback records is provided, which is applied to a first device, the method comprising: displaying a first interface, the first interface comprising a first control, the first control being used to trigger the first device to display historical playback records of a first account that has logged in; when n users are watching in front of the screen of the first device, in response to a trigger operation on the first control, a second interface is displayed, the second interface comprising a fused historical playback record, the fused historical playback record being a playback record obtained by merging historical playback records of accounts of m users, where n is an integer greater than 1, m is an integer not greater than n, and the accounts of the m users include the first account.

[0034] In the solution provided by the second aspect above, when there are n users watching in front of the screen of the first device, the first device can adaptively fuse and display the historical playback records of m users among the n users when it is necessary to display the playback records, wherein the accounts of the m users include the currently logged-in account, and m is an integer not greater than n. In this way, the first device can intelligently display the historical playback records adapted to the user needs in the current viewing scene according to the current viewing scene. In addition, in the scenario of multiple users watching, the first device can realize the sharing of historical playback records among multiple users by displaying the historical playback records after fusion of multiple users, thereby improving the interactive experience of multiple users watching.

[0035] In a possible implementation, a second interface is displayed, and the second interface includes a fusion of historical playback records, including: in the second interface, the playback progress of the same file played by the accounts of m users is displayed in the same playback progress bar, wherein the display styles of the playback progress of different user accounts in the playback progress bar are different. In this way, the first device integrates the playback progress of the same multimedia file by different users into a playback progress bar for display, so that the user can intuitively understand the difference in playback progress between different users in the current viewing scene, or which users have watched the same multimedia file.

[0036] In one possible implementation, the method further includes: in response to a confirmation operation on a first playback progress in the playback progress bar, playing the file at the first playback progress, wherein the first playback progress is the playback progress of an account of any one of the m users. In this way, the user can conveniently select to play the multimedia file at the playback progress of any one of the m users by simply selecting and confirming the playback progress condition that integrates the playback information of multiple users.

[0037] In one possible implementation, the method further includes: displaying account information corresponding to the playback progress bar on the playback progress bar, the account information being account information of a user who has played the file among the m users; and in response to a confirmation operation on a first account in the account information, playing the file with the playback progress of the first account. In this way, the first device, by displaying the user account information corresponding to the playback progress bar, facilitates the user to directly select and confirm an account to conveniently select to play the multimedia file with the playback progress of any user in the current viewing scene.

[0038] In a possible implementation, when a first playback progress bar corresponding to a first file and a second playback progress bar corresponding to a second file are displayed in the second interface, the method further includes: when the number of users who play the first file is greater than the number of users who play the second file, arranging and displaying the first playback progress bar before the second playback progress bar, wherein the playing user is a user among the m users. In this way, when there are multiple playback progress bars of multimedia files in the fusion history playback record, the playback progress bars can be arranged from most to least according to the number of users who have played the file in the current scene.

[0039] In a possible implementation, when the number of users playing the first file is the same as the number of users playing the second file, the method further includes: when the difference between the various play progress of the first file is less than the difference between the various play progress of the second file, arranging and displaying the first play progress bar before the second play progress bar; and / or when the score value of the first file is greater than the score value of the second file, arranging and displaying the first play progress bar before the second play progress bar. In this way, when there are multiple play progress bars with the same number of play users, the first device can also arrange the play progress bars according to the play progress difference between users and / or the score of the multimedia file.

[0040] Optionally, the first device may further arrange the playback progress bar in combination with the currently logged-in account, so as to display the playback progress bar of the file played by the currently logged-in account in front.

[0041] Optionally, the first device may also construct the account of the user currently operating the second device and arrange the play progress bar so that the play progress bar of the file played by the user currently operating the second device is displayed in the front. This solution does not limit the arrangement of multiple play progress bars.

[0042] In one possible implementation, the historical playback records of the accounts of m users are historical playback records in multiple applications, and the method further includes: displaying a corresponding application icon on each fused historical playback record. In this way, the first device can display the historical playback records of users in different applications together. In order to facilitate the user to understand the source of the historical playback record, the first device can also display the application icon corresponding to the source of the historical playback record when displaying the historical playback record.

[0043] In a third aspect, a first device is provided, the first device comprising a display unit for displaying a first interface, the first interface comprising a first control, the first control being used to trigger the first device to display the historical playback record of the logged-in first account. The display unit is also used to: in response to a trigger operation on the first control, display a second interface according to the number of viewing users in front of the screen of the first device. The display unit is also used to: when the number of viewing users in front of the screen of the first device is one, display the historical playback record of the first account in the second interface. The display unit is also used to: when the number of viewing users in front of the screen of the first device is n, display the historical playback records of the accounts of m users in the second interface, where n is an integer greater than 1, m is an integer not greater than n, and the accounts of the m users include the logged-in first account.

[0044] In one possible implementation, the first device is controlled by the second device, the first account is an account of a first user, and the first user is a user who is in front of the screen of the first device and operates the second device.

[0045] In a possible implementation, the display unit is further used to: when the first account is not the account of the first user, display a prompt message, where the prompt message is used to prompt whether to switch to the account of the first user.

[0046] In one possible implementation, the first device further includes an account login service unit, which is configured to log out of the first account and switch to log in to the first user's account in response to a confirmation operation on the first user's account in the prompt information.

[0047] In one possible implementation, the display unit is further used to: after displaying the historical playback records of the logged-in first account in the second interface, display the historical playback records of the first user's account in the second interface.

[0048] In a possible implementation, the display unit is further used to: switch the historical playback records of the first account among the displayed historical playback records of the m user accounts to the historical playback records of the first user's account.

[0049] In one possible implementation, when the number of users viewing the screen of the first device is n, the prompt information includes account information of m users, wherein the account of the first user is highlighted in the account information.

[0050] In one possible implementation, the account login service unit is further used to log out of the first account and switch to log in to the second account in response to a confirmation operation on the second account in the account information, wherein the second account is an account other than the first account among the m users' accounts.

[0051] In a possible implementation, the display unit is further used to: after displaying the historical playback records of the logged-in first account in the second interface, display the historical playback records of the second account in the second interface.

[0052] In a possible implementation, the display unit is further used to: switch the historical playback records of a first account among the displayed historical playback records of the m user accounts to the historical playback records of a second account.

[0053] In a possible implementation, the display unit is further used to: display a fused historical playback record in the second interface, where the fused historical playback record is a playback record obtained by merging historical playback records of accounts of m users.

[0054] In one possible implementation, the display unit is also used to: display the historical playback records of the first account and the integrated historical playback records in the second interface, where the integrated historical playback records are playback records obtained by integrating the historical playback records of the accounts of m users.

[0055] In one possible implementation, the display unit is further used to display the playback progress of the same file played by m user accounts in the same playback progress bar, wherein the display styles of the playback progress of different user accounts in the playback progress bar are different.

[0056] In one possible implementation, the display unit is further used to: in response to a confirmation operation on a first playback progress in the playback progress bar, play the file at the first playback progress, wherein the first playback progress is the playback progress of an account of any one of the m users.

[0057] In one possible implementation, the display unit is further configured to: display account information corresponding to the play progress bar on the play progress bar, where the account information is the account information of the user who has played the file among the m users. The display unit is further configured to: respond to a confirmation operation for a third account in the account information, and play the file at the play progress of the third account.

[0058] In one possible implementation, when a first playback progress bar corresponding to a first file and a second playback progress bar corresponding to a second file are displayed in the second interface, the display unit is further used to: when the number of users playing the first file is greater than the number of users playing the second file, arrange the first playback progress bar to be displayed before the second playback progress bar, wherein the playing user is a user among the m users.

[0059] In one possible implementation, when the number of users who have played the first file is the same as the number of users who have played the second file, the display unit is further used to: when the difference between the various playback progress of the first file is smaller than the difference between the various playback progress of the second file, arrange and display the first playback progress bar before the second playback progress bar; and / or when the rating value of the first file is greater than the rating value of the second file, arrange and display the first playback progress bar before the second playback progress bar.

[0060] In a possible implementation, the historical playback records are historical playback records of multiple applications, and the display unit is further used to: display a corresponding application icon on each historical playback record.

[0061] In a possible implementation, the first device further includes an image acquisition unit, an identity recognition unit, and a record acquisition unit. The image acquisition unit is used to acquire an image in front of the screen of the first device; the identity recognition unit is used to identify the identities of n users watching in front of the screen of the first device based on the image, and the identities include registered account users or unregistered account users; the record acquisition unit is used to acquire historical playback records of m user accounts, and the m users are all registered users located in front of the screen of the first device.

[0062] In a possible implementation, the first device is controlled by the second device, and the n users include a user operating the second device. The first device also includes an operating user identification unit. The operating user identification unit is used to: perform human posture recognition on the image to identify the user operating the second device in front of the screen of the first device; or identify the user operating the second device in front of the screen of the first device based on the position and image of the user operating the second device determined by ultrasonic positioning.

[0063] In a fourth aspect, a first device is provided, the first device comprising a display unit, configured to display a first interface, the first interface comprising a first control, the first control being configured to trigger the first device to display a historical playback record of a first account that has logged in. The display unit is further configured to display a second interface in response to a trigger operation on the first control when n users are watching in front of a screen of the first device, the second interface comprising a fused historical playback record, the fused historical playback record being a playback record after the historical playback records of accounts of m users are fused, n being an integer greater than 1, m being an integer not greater than n, and the accounts of the m users including the first account.

[0064] In one possible implementation, the display unit is also used to: in the second interface, display the playback progress of the same file played by m user accounts in the same playback progress bar, wherein the display styles of the playback progress of different user accounts in the playback progress bar are different.

[0065] In one possible implementation, the display unit is further used to: in response to a confirmation operation on a first playback progress in the playback progress bar, play the file at the first playback progress, wherein the first playback progress is the playback progress of an account of any one of the m users.

[0066] In one possible implementation, the display unit is also used to: display account information corresponding to the playback progress bar on the playback progress bar, where the account information is the account information of the user who has played the file among the m users; and in response to a confirmation operation for the first account in the account information, play the file with the playback progress of the first account.

[0067] In one possible implementation, when a first playback progress bar corresponding to a first file and a second playback progress bar corresponding to a second file are displayed in the second interface, the display unit is further used to: when the number of users playing the first file is greater than the number of users playing the second file, arrange the first playback progress bar to be displayed before the second playback progress bar, wherein the playing user is a user among the m users.

[0068] In one possible implementation, when the number of users who have played the first file is the same as the number of users who have played the second file, the display unit is further used to: when the difference between the various playback progress of the first file is smaller than the difference between the various playback progress of the second file, arrange and display the first playback progress bar before the second playback progress bar; and / or when the rating value of the first file is greater than the rating value of the second file, arrange and display the first playback progress bar before the second playback progress bar.

[0069] In a possible implementation, the historical playback records of the accounts of m users are historical playback records in multiple applications, and the display unit is further used to: display a corresponding application icon on each fused historical playback record.

[0070] In a fifth aspect, a device is provided, comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories are used to store program codes, and the program codes include instructions, and when the one or more processors execute the instructions, the device executes the method for displaying playback records in any possible implementation of the first aspect, or the device executes the method for displaying playback records in any possible implementation of the second aspect.

[0071] In a sixth aspect, a chip system is provided, which is applied to a device. The chip system includes one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected by a line. The interface circuit is used to receive a signal from a memory of the device and send the signal to the processor, where the signal includes an instruction stored in the memory. When the processor executes the instruction, the device executes a display method for playing a record as in the first aspect and any possible design thereof, or the device executes a display method for playing a record as in the second aspect and any possible design thereof.

[0072] In the seventh aspect, a communication system is provided, comprising a second device and the first device provided in the third aspect, wherein the first device is controlled by the second device, and the first device executes a display method for playback records as in the first aspect and any possible design thereof.

[0073] In an eighth aspect, a communication system is provided, comprising a second device and the first device provided in the fourth aspect, wherein the first device is controlled by the second device, and the first device executes a display method for playback records as in the second aspect and any possible design thereof.

[0074] In a ninth aspect, a readable storage medium is provided, which includes instructions. When the instructions are executed on a device, the device executes a method for displaying playback records as in the first aspect and any possible design thereof.

[0075] In a tenth aspect, a program product is provided, which, when executed on a device, enables the device to execute a method for displaying playback records as in the first aspect and any possible design thereof.

[0076] It can be understood that the beneficial effects that can be achieved by the devices of the third and fourth aspects, the device of the fifth aspect, the chip system of the sixth aspect, the communication systems of the seventh and eighth aspects, the readable storage medium of the ninth aspect, and the program product of the tenth aspect provided above can be referred to the beneficial effects of the first aspect, the second aspect and any possible design methods thereof, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] Figure 1 Scenario diagram provided for the embodiment of this application Figure 1 ;

[0078] Figure 2 Scenario diagram provided for the embodiment of this application Figure 2 ;

[0079] Figure 3 Scenario diagram provided for the embodiment of this application Figure 3 ;

[0080] Figure 4 Schematic diagram of the user interface provided in the embodiment of the present application Figure 1 ;

[0081] Figure 5 Schematic diagram of the user interface provided in the embodiment of the present application Figure 2 ;

[0082] Figure 6 Scenario diagram provided for the embodiment of this application Figure 4 ;

[0083] Figure 7 Scenario diagram provided for the embodiment of this application Figure 5 ;

[0084] Figure 8 Scenario diagram provided for the embodiment of this application Figure 6 ;

[0085] Fig. 9 Schematic diagram of the user interface provided in the embodiment of the present application Figure 3 ;

[0086] Fig.10 Scenario diagram provided for the embodiment of this application Figure 7 ;

[0087] Fig.11 Scenario diagram provided for the embodiment of this application Figure 8 ;

[0088] Fig.12 A schematic diagram of a scene image provided in an embodiment of the present application;

[0089] Fig.13 A schematic diagram of the hardware structure of a device provided in an embodiment of the present application;

[0090] Fig.14 A schematic diagram of the software structure of a device provided in an embodiment of the present application;

[0091] Fig.15 Scenario diagram provided for the embodiment of this application Figure 9 ;

[0092] Fig.16Schematic diagram of the user interface provided in the embodiment of the present application Figure 4 ;

[0093] Fig.17 Schematic diagram of the user interface provided in the embodiment of the present application Figure 5 ;

[0094] Fig.18 Schematic diagram of the user interface provided in the embodiment of the present application Figure 6 ;

[0095] Fig.19 Schematic diagram of the user interface provided in the embodiment of the present application Figure 7 ;

[0096] Fig. 20 Scenario diagram provided for the embodiment of this application Figure 10 ;

[0097] Fig.21 Schematic diagram of the user interface provided in the embodiment of the present application Figure 8 ;

[0098] Fig. 22 Schematic diagram of the user interface provided in the embodiment of the present application Figure 9 ;

[0099] Fig.23 A flowchart of a method for displaying playback records provided in an embodiment of the present application. DETAILED DESCRIPTION

[0100] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0101] See also Figure 1 , shows an application scenario provided by an embodiment of the present application. The application scenario includes a large-screen device 100, a remote controller 200, and a user 300. The user 300 can control the large-screen device 100 to play corresponding multimedia content, such as TV series, movies, music, etc., through the remote controller 200.

[0102] Among them, the large-screen device 100 can provide an account login function. By logging in to the account on the large-screen device 100, the user 300 can enable the large-screen device 100 to provide the user 300 with business functions that match the login account, such as membership functions, history functions, personalized recommendation functions, etc. The large-screen device 100 can also be installed with at least one application, including applications for presenting multimedia content such as audio and video, such as "Video Application 1", "Video Application 2", "Music Application 1", "Music Application 2", etc. The user 300 can control the large-screen device 100 to enter the corresponding application and play the corresponding multimedia content through the remote control 200.

[0103] In some scenarios, the account of the large-screen device 100 can be bound to the platform accounts of multiple applications to enjoy the mutual access of membership rights. In this case, when the user 300 needs to view the content that he has played on the large-screen device 100 before, the user 300 can log in to his account on the large-screen device 100, enter the corresponding application, open the historical playback record, and view the content that he has played before. If the large-screen device 100 is currently logged in to the account of another user, the user 300 needs to log out of the other user's account first, then switch to log in to his own account, then enter the corresponding application, open the historical playback record, and then view the content that he has played before.

[0104] like Figure 2 As shown, a login control 101 for guiding a user to log in to an account may be displayed on the large-screen device 100. The user 300 may click the login control 101 by operating the remote controller 200. In response to the click operation, the large-screen device 100 displays a login window 102. The user 300 may enter his / her account information, such as an account name and password, in the login window 102 by operating the remote controller 200 to log in to the account on the large-screen device 100.

[0105] In some scenarios, users can also scan a code to log in. Figure 2 As shown, the user 300 can operate the remote controller 200 to click the scan code login control 103 in the login window 102 to prompt scanning code login. In response to the click operation, as shown in FIG. Figure 3 As shown, the large-screen device 100 can display a login QR code 104 in the login window 102. Then the user 300 can scan the login QR code 104 through the mobile phone 400 to log in to the account on the large-screen device 100.

[0106] After the user successfully logs in to his account on the large-screen device 100, Figure 4 As shown in (a) in FIG. 1 , the large-screen device 100 can display the logged-in account information 105 , such as displaying the logged-in account name “User A”. Then the user can open the corresponding application on the large-screen device 100 to view his / her historical playback records in the application.

[0107] For example, Figure 4 As shown in (a) of FIG. 1 , the user can continue to operate the remote control to click the icon 106 of the video application 1 displayed on the large-screen device 100. In response to the click operation, the large-screen device 100 opens the video application 1 and can display the video application 1 as shown in FIG. Figure 4 The application interface of the video application 1 shown in (b) of FIG. The application interface may include a history record control 107. After the user operates the remote control to click the history record control 107, the large screen device 100 may display the following: Figure 4The historical play record page 108 shown in (c) of FIG. 108 , through the historical play record page 108 , the user can browse the videos that he / she has played in the history on the video application 1 , as well as the corresponding play progress, play time and other information.

[0108] When a user wants to view videos that he has played on other applications, the user can first operate the remote control to make the large-screen device 100 exit the video application 1, and then operate the remote control to make the large-screen device 100 open other applications to view his historical playback records in other applications.

[0109] For example, Figure 5 As shown in (a) of FIG. 1 , after the large-screen device 100 exits the video application 1, the user can continue to operate the remote control to click the icon 109 of the video application 2. In response to the click operation, the large-screen device 100 opens the video application 2 and can display the following Figure 5 The application interface of the video application 2 shown in (b) of FIG. 1 may include a history playback control 110. After the user operates the remote control to click the history playback control 110, the large screen device 100 may display the following: Figure 5 The historical play record page 111 shown in (c) in FIG. 111 , through the historical play record page 111 , the user can browse the videos that he / she has played in the history on the video application 2 , as well as the corresponding play progress, play time and other information.

[0110] If there are other users besides user 300 in the current scenario, such as Figure 6 As shown in FIG. 4 , other users can also use the above method to control the large-screen device 100 to switch and log in to their own account by operating the remote control, and then enter the corresponding application, open the historical playback record, and view the content they have played before.

[0111] In some scenarios, the account of the large-screen device 100 may not be bound to the platform accounts of multiple applications. In this case, the user needs to log in to the platform accounts of multiple applications respectively before he can view his historical playback records in the corresponding applications.

[0112] Take video application 1 as an example. Figure 6 As shown, the user 300 operates the remote control to click the icon 106 of the video application 1 displayed on the large screen device 100. In response to the click operation, the large screen device 100 opens the video application 1 and may display the video application 1 as shown in FIG. Figure 7The application interface of the video application 1 shown in the figure may include a login control 112 for guiding the user to log in to the platform account of the video application 1, and a history control 107. The user 300 needs to log in to his platform account in the video application 1 before he can view the videos he has played before in the video application 1.

[0113] For example, after the user 300 clicks the login control 112 by operating the remote control, the large screen device 100 may display the following Figure 8 The login window 113 of the video application 1 is shown. The user 300 can log in to his platform account by operating the remote control and entering the account password, or by scanning the code with the mobile phone. After the user successfully logs in to his platform account in the video application 1, Fig. 9 As shown in (a) of FIG. 1 , the application interface of the video application 1 can display the logged-in platform account information 114, such as displaying the logged-in platform account name "user a". After the user continues to operate the remote control to click the history control 107 in the application interface of the video application 1, the large-screen device 100 can display the following information: Fig. 9 The historical play record page 115 shown in (b) of FIG. 115 , through the historical play record page 115 , the user can browse the videos that he / she has played in the history on the video application 1 , as well as the corresponding play progress, play time and other information.

[0114] It can be seen that currently users view their historical playback records by manually logging into their accounts (such as scanning a code to log in, entering an account number and password to log in, etc.). If other users have logged in with their accounts before, they will need to manually log out of other users’ accounts before they can manually log in to their own accounts. The entire operation process is relatively cumbersome. And if other users use the current user’s account to play multimedia content, the playback progress of other users will also be updated to the current user’s historical playback records, causing the current user to be unable to retrieve their true historical playback records, causing inconvenience to the user. In addition, due to the different sources of multimedia content, users usually play multimedia content in different applications. This causes the user’s historical playback records of multimedia content to be scattered across various applications, and users still need to search for them in the corresponding applications themselves, causing inconvenience to users.

[0115] Based on the above problems, the embodiment of the present application provides a method for displaying playback records, and the device can automatically determine whether the currently logged-in account is the account of the user currently operating the remote control. When the device determines that the currently logged-in account is not the account of the user currently operating the remote control, it can quickly display the account of the user currently operating the remote control and prompt the user whether to switch accounts, so that the user currently operating the remote control can easily complete the account switch without the user having to manually log out of the account and then manually log in to his or her account. The subsequent device can also display the historical playback records of the currently logged-in account together when displaying the historical playback records, without the user having to search in the corresponding application by himself.

[0116] The display method of the playback record provided in the embodiment of the present application can be applied to various fields of user-sharable functions or user-sharable products, and the embodiment of the present application does not limit this. For example, multiple users can share a certain device, such as playing multimedia content such as video and audio on the same device. For another example, multiple users can share an application on a certain device, such as playing multimedia content such as video and audio in the same application on the same device.

[0117] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0118] Fig.10 The schematic diagram of the architecture of the communication system 1000 in the embodiment of the present application is a schematic diagram of the architecture of the communication system 1000 in the embodiment of the present application. The display method of the playback record provided in the embodiment of the present application can be applied to Figure 1 In the communication system 1000 shown in FIG. Fig.10 As shown, the communication system 1000 may include: a first device 1010 and a second device 1020 .

[0119] Among them, the first device 1010 can be a large-screen device (such as a smart TV, a smart screen), a smart projector, a car machine (such as a car computer), a mobile phone (vertical screen mobile phone, folding screen mobile phone, etc.), a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook, and a cellular phone, a personal digital assistant (personal digital assistant, PDA), an augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) device, etc. The specific form of the first device is not particularly limited in the embodiment of the present application.

[0120] The first device 1010 may further include a camera 1011 for collecting image information in the current environment. In the embodiment of the present application, the first device 1010 may identify the number of users in the current scene and the identity information of each user through the image information collected by the camera 1011.

[0121] It should be understood that the camera 1011 can be a built-in device or an external device; when the camera 1011 is an external device, it can be connected to the first device 1010.

[0122] The second device 1020 may be a device for assisting in implementing the related functions of the first device 1010. For example, the user may control the first device 1010 to turn on or off, play multimedia content, adjust the volume, set or modify the display parameters of the display screen, etc. through the second device 1020. As a method, the second device 1020 may be an auxiliary device such as a remote controller (such as an infrared remote controller, a Bluetooth remote controller, a UWB remote controller), a keyboard, a mouse, etc. The second device 1020 may have multiple physical buttons, such as an "up" button, a "down" button, a "left" button, a "right" button, a "confirm" button, a power on / off button, a voice input button, a "return" button, a "home" button, a "menu" button, a "volume +" button, a "volume -" button, etc. The second device 1020 may receive the user's input operation through these multiple physical buttons to control the first device 1010. For example, after the user presses the "home" button of the second device 1020, the first device 1010 may receive the corresponding control instruction and display a home page containing multiple application icons in response to the control instruction. For another example, the user can press the "volume +" button of the second device 1020, and the first device 1010 can receive the corresponding instruction and increase the volume of the speaker in response to the instruction. Optionally, the second device 1020 can be sold together with the first device 1010 when the first device 1010 leaves the factory, or it can be sold independently. This embodiment of the application is not limited to this.

[0123] As another way, the second device 1020 may be a terminal such as a mobile phone or a tablet computer equipped with a remote control application. When a terminal such as a mobile phone or a tablet computer is equipped with a remote control application, the terminal such as the mobile phone or the tablet computer may open the remote control application to display a remote control interface, which may include multiple virtual buttons. The terminal may receive user input operations through the multiple virtual buttons in the remote control interface to control the first device 1010. The specific form of the second device is not particularly limited in the embodiment of the present application.

[0124] The first device 1010 and the second device 1020 can communicate with each other in a wired manner, such as using a universal serial bus (USB) to establish a wired connection, or can communicate with each other in a wireless manner, such as establishing a wireless connection through infrared technology (IR), Bluetooth low energy (BLE), wireless fidelity (Wi-Fi), near field communication (NFC), ultra wideband (UWB), etc. The first device 1010 can receive a control instruction sent by the second device 1020 through the above-mentioned wired communication or wireless communication, and can respond to the control instruction.

[0125] In the embodiment of the present application, the first device 1010 can identify the identity information of the user operating the second device 1020 in the current scene through the image information collected by the camera 1011. Fig.10 As shown, when the current scene includes user A, user B, user C, and user D, the first device 100 can identify the identity information of user A who is currently operating the second device 1020.

[0126] In one scenario, after obtaining the image information captured by the camera 1011, the first device 1010 can identify the user who is operating the second device 1020 in the current scene by performing human posture recognition on the image information, and combine with face recognition technology to identify the identity information of the user operating the second device 1020.

[0127] In another scenario, the first device 1010 can also determine the position information of the user who is operating the second device 1020 in the current scene through ultrasonic positioning technology. Then, combined with the image information collected by the camera 1011, the identity information of the user corresponding to the position information can be identified through face recognition technology.

[0128] For example, Fig.11 As shown, the first device 1010 may include a microphone array 1012 composed of multiple microphones. The second device 1020 may include a sound unit 1021. When the user operates the second device 1020, the sound unit 1021 can emit ultrasonic waves, and the microphone array 1012 of the first device 1010 can receive the ultrasonic waves. The first device 1010 can calculate the approximate position of the current second device 1020 based on the time difference of the multiple microphones receiving the ultrasonic waves. Then, based on the image captured by the camera 1011, the first device 1010 can calculate the approximate position of the second device 1020. Fig.12The first device 1010 can determine the location information of the faces of each user in the scene image. The first device 1010 can determine the face image of the user corresponding to the approximate location of the second device 1020 through the approximate location of the second device 1020 and the location information of the faces of each user, which is the face image of user A.

[0129] Optionally, in general, when a user uses the second device 1020, such as a remote control, the user's hand is placed in front of the body, and the remote control is at a relative position below the user's face, such as within a 30° deflection range in the vertical direction, within a range of [20, 70] cm in the vertical direction, and within a range of [0, 50] cm in the horizontal direction. When the relative positions of the face and the remote control are within this constraint range, the first device 1010 can regard the user represented by the face as the user currently operating the remote control.

[0130] The embodiment of the present application does not limit the method for identifying the user currently operating the second device 1020. In some scenarios, other methods may also be used to implement the identification of the user currently operating the second device 1020. For example, an obvious mark is added to the second device 1020, so that the first device 1010 can perform a mark image recognition on the image information collected by the camera 1011 to locate the position information of the second device 1020, so that the face image of the user operating the second device 1020 can be located, and then the identity information of the user operating the second device 1020 can be identified. For another example, an identity authentication module, such as a fingerprint authentication module, may also be added to the second device 1020, so that the second device 1020 can send the fingerprint information of the current user of the second device 1020 to the first device 1010, and then the first device 1020 can quickly identify the identity information of the user currently operating the second device 1020.

[0131] Fig.13 A schematic diagram of the structure of a device provided in an embodiment of the present application. The device may be Figure 1 The large screen device 100 in the embodiment may also be Fig.10 The first device 1020 in FIG. Fig.13 As shown, the device may include: a processor 1301, a memory 1302, a display screen 1303, a camera 1304, etc.

[0132] The processor 1301 includes one or more processing units, for example, the processor 1301 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors. The controller may generate an operation control signal according to the instruction opcode and the timing signal to complete the control of fetching and executing instructions.

[0133] The processor 1301 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 1301 is a cache memory. The memory may store instructions or data that the processor 1301 has just used or cyclically used. If the processor 1301 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 1301, and thus improves the efficiency of the system.

[0134] In an embodiment of the present application, the memory may store registered user information, which includes the user's face information. In some embodiments, the user information may also include information such as the user's clothing, age, height, etc.

[0135] The memory 1302 can be used to store program codes, which include instructions. In an embodiment of the present application, the memory 1302 stores a program or instruction corresponding to the display method of the playback record provided in the embodiment of the present application. The memory 1302 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, at least one application required for a function (such as various video applications, audio applications), etc. The data storage area may store data created during the use of the device (such as scene images collected by the camera 1304), etc. In addition, the memory 1302 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (universal flash storage, UFS), etc. The processor 1301 executes various functional applications and data processing of the device by running instructions stored in the memory 1302, and / or instructions stored in a memory provided in the processor 1301.

[0136] The device implements the display function through a GPU, a display screen 1303, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 1303 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 1301 may include one or more GPUs, which execute program instructions to generate or change display information.

[0137] The display screen 1303 is used to display images, videos, etc. In the embodiment of the present application, the display screen 1303 can be used to display information input by the user or information provided to the user, as well as various menus of the device, various applications, etc. The display screen 1303 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light emitting diode or an active-matrix organic light emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light emitting diode (QLED), etc. In some embodiments, the device may include 1 or N display screens 1303, where N is a positive integer greater than 1.

[0138] The device can realize the shooting function through the ISP, the camera 1304, the display screen 1303 and the application processor.

[0139] Among them, ISP is used to process the data fed back by camera 1304. In some embodiments, ISP can be set in camera 1304. Camera 1304 is used to capture static images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element converts the light signal into an electrical signal and then transmits the electrical signal to ISP for conversion into a digital image signal. ISP outputs the digital image signal to DSP for processing. DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the device may include 1 or N cameras 1304, where N is a positive integer greater than 1.

[0140] In the embodiment of the present application, when the device is Figure 1When the remote control receives the user's operation, the device can be triggered to start collecting the scene image of the current scene through the camera 1304 to identify the identity information of the user who is operating the remote control in the current scene. When the device determines that the currently logged-in account is not the account of the user currently operating the remote control, the account of the user currently operating the remote control can be displayed on the display screen 1303, and the user is prompted whether to switch accounts. The display screen 1303 can also display the historical playback records of the currently logged-in account, and the historical playback records of various applications are displayed in the historical playback records.

[0141] It is to be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the device. In other embodiments, the device may include more or fewer components than shown, or combine certain components, or split certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware. For example, the device may also include a wireless communication module, a speaker, a microphone (or a microphone array), etc.

[0142] Among them, when the device is Figure 1 The large screen device 100 or Fig.10 When the first device 1010 is shown, the device can communicate with the remote controller 200 or the second device 1020 through the wireless communication module. The microphone can be used to implement ultrasonic positioning of the remote controller 200 or the second device 1020. In some embodiments, the above device is Figure 1 remote control 200, or Fig.10 When the second device 1020 in the embodiment of the present invention is used, the device may also include a sound generating unit for transmitting ultrasonic waves, which are Figure 1 The large screen device 100 or Fig.10 When the microphone in the first device 1010 shown receives the signal, it can be used to locate the device.

[0143] The software system of the above device can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the layered architecture as an example to illustrate the software structure of the device.

[0144] Fig.14 A software schematic diagram of a device provided in an embodiment of the present application. The device may be Figure 1 The large screen device 100 in the embodiment may also be Fig.10 The first device 1020 in the layered architecture divides the software into several layers, each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the software system is divided into four layers, from top to bottom, namely, the application layer, the application framework layer, the system library, and the kernel layer. The application layer can include a series of application packages.

[0145] like Fig.14 As shown, the application package may include video application 1, video application 2, music application, Bluetooth application, gallery application, etc. The application on the device may be a native application or a third-party application, which is not limited in the present application embodiment.

[0146] In some embodiments, the application layer may also include comprehensive applications that can integrate multimedia resources from different platforms. For example, the comprehensive application may be a video comprehensive application that can integrate video resources from video application 1 and video resources from video application 2. Users can browse video content from different application platforms only through the video comprehensive application.

[0147] In some embodiments, the account of the comprehensive application can be bound to the platform accounts of multiple applications, that is, when a certain account is logged in to the comprehensive application, multiple applications bound to the comprehensive application are logged in to the account simultaneously to enjoy the mutual access of member benefits. In this case, when the user logs in to his account in the comprehensive application, he can query his historical playback records, which may include multimedia content from different application platforms that he has played before.

[0148] In some embodiments, the account of the comprehensive application can also be bound to the account of the device, that is, when a certain account is logged in on the device, the comprehensive application bound to the device will simultaneously log in to the account.

[0149] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0150] like Figure 3 As shown, the application framework layer may include a window manager, a content provider, a notification manager, etc., which is not limited in the embodiments of the present application. Among them, the window manager is used to manage window programs. The content provider is used to store and obtain data, and make these data accessible to applications. The data may include video, images, audio, historical playback records, etc. The notification manager enables the application to display notification information in the status bar. For example, the notification manager is used for account switching reminders, etc. The notification manager can also be a notification that appears in the top status bar of the system in the form of a chart or scroll bar text, or a notification that appears on the screen in the form of a dialog window.

[0151] In some embodiments, the application framework layer may also include an account login service for registering an account of a device / application platform and logging into an account of a device / application platform. The account of the application platform may be the platform account of the video application 1, the platform account of the video application 2, the platform account of the music application, etc. Optionally, the account login service is also used to determine whether the currently logged-in account is the account of the user currently operating the remote control. When it is determined that the currently logged-in account is not the account of the user currently operating the remote control, the user is prompted whether to switch accounts.

[0152] Optionally, the account login service is also used to obtain the user's face, clothing, age, height and other user information when the user registers an account on the device / application platform, and associate the user information with the registered user and store it. This facilitates the subsequent verification of the currently logged-in account through the stored user information to see if it is the account of the user currently operating the remote control.

[0153] In some embodiments, the application framework layer may also include a history record service for recording the playback information of multimedia content played by the user in various applications, and the playback information may include the playback time, playback progress, etc. Optionally, the history record service is also used to obtain the recorded playback information matching the logged-in account when the device / application platform has logged in to the account, and display the obtained playback information on the historical playback record page. Among them, the historical playback record page can centrally display the playback information of the multimedia content played by the user in various applications.

[0154] The system library can include multiple functional modules. For example: surface manager, media library, 3D graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL), etc. The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications. The media library supports a variety of commonly used audio and video format playback and recording, as well as static image files, etc. The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis, and layer processing, etc. The 2D graphics engine is a drawing engine for 2D drawing.

[0155] The kernel layer is a layer between hardware and software. The kernel layer may include display drivers, camera drivers, input / output device drivers (such as touch screens), audio drivers, etc., which are not limited in the present application embodiment.

[0156] Understandably, Fig.14The layers in the software structure shown and the components contained in each layer do not constitute a specific limitation on the device. In other embodiments of the present application, the device may include more or fewer layers than shown in the figure, and each layer may include more or fewer components, which is not limited in the present application.

[0157] The methods in the following embodiments can all be implemented in a device having the above hardware structure and software structure.

[0158] The following takes a large-screen device as an example to specifically introduce the method for displaying playback records provided in an embodiment of the present application.

[0159] For ease of understanding, the method for displaying playback records provided in an embodiment of the present application is first introduced through two specific scenarios.

[0160] Scenario 1: A single user watches a large-screen device.

[0161] like Fig.15 As shown in (a), in the current scene, only a single user 300 is watching the large-screen device 100. The large-screen device 100 can collect the scene image of the current scene through the camera. Then the large-screen device 100 can identify the identity information of the user 300 in the current scene by performing face recognition on the scene image, so as to determine whether the user 300 is a registered user (a user who has registered an account with the large-screen device 100). If the user 300 has registered his own account on the large-screen device 100 and the account name is "User A", the large-screen device 100 can identify the user 300 as a registered user by performing face recognition on the face image of the user 300 in the scene image.

[0162] The large-screen device 100 may pre-store facial information of all registered users, and the large-screen device 100 may determine whether the user 300 is a registered user by comparing the facial image of the user 300 in the scene image with the pre-stored facial information of the registered users. Optionally, when there is a facial information of a person in the pre-stored facial information of the registered users that matches the facial image of the user 300, the user 300 may be confirmed to be a registered user.

[0163] In the embodiment of the present application, in addition to identifying registered users in the current scene, the large-screen device 100 can also identify the user who is operating the remote control 200 in the current scene.

[0164] As a method, the large screen device 100 can identify the user 300 who is currently holding the remote controller 200, that is, the user who is operating the remote controller 200, by performing human gesture recognition on the scene image. Human gesture recognition may include recognition of a person's hand gesture. The hand gesture may be a gesture of the person holding the remote controller.

[0165] As another way, the large-screen device 100 can also determine the approximate position of the remote control 200 through ultrasonic positioning technology, and then combine it with the scene image to identify the user 300 corresponding to the position, that is, the user who is operating the remote control 200.

[0166] After the large-screen device 100 recognizes that the user operating the remote controller 200 in the current scene is the user 300 , it can determine whether the account currently logged into the large-screen device 100 is the account of the user 300 currently operating the remote controller.

[0167] like Fig.15 As shown in (a) in the figure, if the large-screen device 100 displays the account information 116 of the currently logged-in account as the account name "User B", the large-screen device 100 can determine that the account currently logged in to the large-screen device 100 is not the account of the user 300 currently operating the remote control based on the pre-stored account information of the user 300 (including the account name "User A"). Therefore, when the user 300 starts to operate the remote control 200, the large-screen device 100 can prompt the user whether to switch accounts.

[0168] As a way, Fig.15 As shown in (b) in the figure, the large-screen device 100 may pop up a prompt window 117. The prompt window 117 may include an inquiry message "! The current login account does not match! Do you want to switch accounts?" and a "Confirm" button and a "Cancel" button. The user 300 may operate the remote control 200 to click the "Confirm" button 118 in the prompt window 117 to instruct the large-screen device 100 to switch to the account of the user 300. In this way, the user 300 can choose to switch the current login account or choose not to switch the current login account through the content in the prompt window 117.

[0169] Optionally, the prompt window 117 may also include the account information of the currently logged-in account and the account information of the registered user identified in the current scene, so that the user can make an accurate choice after understanding the current account switching scene. Since the user 300 currently operating the remote controller 200 is a registered user, the prompt window 117 may include the account information of the user 300. Fig.15 As shown in (b), the prompt window 117 can display the account name "User B" of the currently logged-in account and the account avatar 119 corresponding to "User B", as well as the account name "User A" of the user 300 currently operating the remote control and the account avatar 120 corresponding to "User A".

[0170] After the user 300 selects to switch the current login account through the prompt window 117, Fig.15As shown in (c) in the figure, the large-screen device 100 can display the account information 121 of the user 300 after switching login, such as displaying the account name "User A" after switching login.

[0171] In one scenario, after the user 300 quickly selects to switch the current login account through the prompt window 117, the user can open the corresponding application on the large-screen device 100 to view the historical playback records of the multimedia content in the application. Figure 4 As shown in (a) to (c) in FIG. 1 , the user can open the video application 1 on the large-screen device 100 to view the historical video playback records in the video application 1. For another example, Figure 5 As shown in (a) to (c) in FIG. 1 , the user can open the video application 2 on the large-screen device 100 to view the historical video playback records in the video application 2. For another example, the user can open the music application 1 on the large-screen device 100 to view the historical music playback records in the video application 1.

[0172] In one scenario, the large-screen device 100 can also centrally display the historical playback records of the user on each application, without the user having to open the corresponding application to search. As a method, the large-screen device 100 can obtain the historical playback records in each application that match the account of the user 300 through the account of the currently switched logged-in user 300. Then the large-screen device 100 can merge the historical playback records of each application obtained to display the merged historical playback records of multiple applications on the main interface of the large-screen device 100.

[0173] Among them, each historical playback record displayed on the main interface may include information such as the name of the multimedia content, content cover, playback time, and playback progress. The embodiments of the present application are not limited to this. For example, since different devices can share multimedia resources by logging into the same account, a user can use the same account to play multimedia content on different devices. Therefore, each historical playback record may also include the name of the device that plays the multimedia content, the device ID, etc.

[0174] like Fig.15 As shown in (d) in the figure, the large-screen device 100 displays a main interface, which includes multiple options, such as input source options, video options, music options, gallery options, etc. When the user 300 selects the video option in the main interface by operating the remote control 200 (the video option can be highlighted at this time), the large-screen device 100 can display the historical playback records 122 of each video application under the current login account. Since the current login account is the account "User A" of the user 300 after the aforementioned switch, the historical playback records 122 display the historical playback records in each video application that match the account "User A" of the user 300.

[0175] Similarly, when the user 300 selects the music option in the main interface by operating the remote controller 200 (the music option can be highlighted at this time), the large-screen device 100 can display the historical play records of each music application under the currently logged-in account. Since the currently logged-in account is the account "User A" of the user 300 after the aforementioned switch, the historical play records display the historical play records in each music application that match the account "User A" of the user 300.

[0176] In one scenario, the large-screen device 100 may also trigger the above-mentioned account quick switching process when it is necessary to display historical playback records.

[0177] For example, Fig.15 As shown in (e) in FIG. 1 , when the user 300 selects the video option in the main interface of the large-screen device 100 (the video option can be highlighted at this time) by operating the remote control 200, the large-screen device 100 displays the historical playback records 122 of each video application under the current login account by default in the main interface. Since the current login account of the large-screen device 100 is "User B", the historical playback records 122 display the historical playback records in each video application that match the account "User B".

[0178] Since the current login account of the large-screen device 100 may not match the user 300 in the current scene, the historical play record 122 displayed on the main interface of the large-screen device 100 may not meet the needs of the user 300. Therefore, in the embodiment of the present application, when the large-screen device 100 displays the historical play record 122 on the main interface, the large-screen device 100 can identify the registered users in the current scene and the user who is operating the remote control 200 in the current scene. When the user 300 in the current scene is identified as a registered user and the user who is operating the remote control 200, the large-screen device 100 can determine whether the current login account matches the account "User A" of the user 300 who is currently operating the remote control.

[0179] When a mismatch is detected, Fig.15 As shown in (e) in FIG. 1 , the large screen device 100 may display a prompt window 117 to prompt whether to switch to the account "User A". After the user confirms the switch through the remote control 200, as shown in FIG. Fig.15 As shown in (d), the large-screen device 100 can display the account information 121 of the user 300 after the switch login in the main interface, such as displaying the account name "User A" after the switch login, and correspondingly switch to display the historical playback records matching the account "User A" in each video application in the historical playback record 122 of the main interface.

[0180] Optionally, when a mismatch is determined, the large-screen device 100 may also prompt the user to switch accounts by popping up an account list. The account list includes account floating bars of all registered users in the current scene, and the top of the account floating bar corresponds to the account avatar. Since there is only user 300 in the current scene and user 300 is a registered user, if Fig.15 As shown in (f) in the figure, the large-screen device 100 can pop up a floating bar on the main interface that includes the account name "User A" of the user 300 and the account avatar 120 corresponding to "User A".

[0181] At this time, the user can press the "Confirm" button on the remote control 200 to instruct the large-screen device 100 to quickly switch to his account "User A". Fig.15 As shown in (d) in the figure, the account information 121 "User A" of the user 300 after the switch login is displayed in the main interface, and the historical playback records 122 in the main interface are correspondingly switched to display the historical playback records matching the account "User A" in each video application. The user can cancel the account switch by pressing the "Return" button on the remote control 200, so that the current login account of the large-screen device 100 is still "User B", and the historical playback records 122 in the main interface still display the historical playback records matching the account "User B" in each video application.

[0182] Optionally, if the large-screen device 100 is not currently logged in to an account, the large-screen device 100 may not display historical playback records in the main interface. At this time, the large-screen device 100 can identify the registered users in the current scene and identify the user who is operating the remote control 200 in the current scene. When the user 300 in the current scene is identified as a registered user and the user who is operating the remote control 200, the large-screen device 100 may prompt whether to log in to the account of user 300. The large-screen device 100 may pop up a prompt window, which may include the inquiry information "Identify the account of the user in front of the device! Do you want to log in to the account?" and a "Confirm" button and a "Cancel" button. User 300 can operate the remote control to click the "Confirm" button in the prompt window to instruct the large-screen device 100 to automatically log in to the account "User A" of user 300. In this way, user 300 can conveniently choose to log in to his own account, or choose not to log in to his own account. Optionally, when the user 300 chooses to log in to his own account, the large-screen device 100 can display the historical playback records 122 of each video application under the currently logged-in account in the main interface, that is, the historical playback records in each video application that match the currently logged-in account "User A".

[0183] Among them, there can be multiple ways to display the historical playback records of each video application under the current login account, which is not limited in this embodiment of the present application.

[0184] As one approach, the historical playback records may be displayed in the order of playback time in each playback record in all applications.

[0185] For example, Figure 4 As shown in (c) of FIG. 1 , it is assumed that the historical playback records matching the account "User A" of user 300 in video application 1 include: "Video 1", 2023-08-03, 60% played; "Video 2", 2023-08-01, 1% played; "Video 3", 2023-07-15, 30% played. Figure 5 As shown in (c), it is assumed that the historical playback records matching the account "User A" of user 300 in video application 2 include: "Video 4", 2023-08-05, 60% played; "Video 5", 2023-07-11, 50% played; "Video 6", 2023-07-01, 10% played; "Video 7", 2023-06-25, 90% played.

[0186] When the user 300 selects the video option in the main interface by operating the remote controller 200 (the video option can be highlighted at this time), the large-screen device 100 can display the following Fig.16 The historical play record list 123 shown in (a) in FIG. The historical play record list 123 includes historical play records matching the account "User A" of the currently logged-in user 300 in different video applications, and is displayed in the order of play time: "Video 4", 2023-08-05, 60% played -> "Video 1", 2023-08-03, 60% played -> "Video 2", 2023-08-01, 1% played -> "Video 3", 2023-07-15, 30% played.

[0187] The user 300 can realize quick playback of the played videos through the historical playback record list 123. Optionally, after the user 300 operates the remote control 200 to select the video playback record to be played in the historical playback record list 123, the large-screen device 100 can respond to the selection operation and continue to play the video in the video playback record based on the saved playback progress.

[0188] The selected video playback record can be highlighted. Fig.16As shown in (a), the selected record "Video 4, 2023-08-05, 60% played" is highlighted. When the user presses the "Confirm" button on the remote control 200, the large-screen device 100 can confirm that the user has performed a selection operation on the selected record "Video 4, 2023-08-05, 60% played", so that the large-screen device 100 can respond to the selection operation, quickly enter the playback interface of "Video 4", and start playing "Video 4" at 60% of the playback progress (i.e., playback duration).

[0189] As a method, the user can also switch the selected video playback record in the historical playback record list 123 by using the direction keys such as the “up” key and the “down” key on the remote control 200 .

[0190] Optionally, if there are many historical playback records to be displayed, they can also be displayed in pages. As a way, when the user presses the "down" button on the remote control 200 to switch the selected video playback record in the historical playback record list 123 to the last video playback record "Video 3, 2023-07-15, 30% played", if the user continues to press the "down" button on the remote control 200, the large-screen device 100 can display the following: Fig.16 The historical playback record list 124 on the next page shown in (b) is still displayed in chronological order of playback time: "Video 5", 2023-07-11, 50% played -> "Video 6", 2023-07-01, 10% played -> "Video 7", 2023-06-25, 90% played.

[0191] Optionally, since there are historical playback records of different applications in the historical playback record list, the large-screen device 100 may also identify the source of each playback record when displaying the historical playback record list. Fig.16 The historical play record list 125 shown in (c) in FIG. 1 may display an application identifier 126 corresponding to each play record to prompt the user which application platform the video in each play record comes from. Optionally, the application identifier may also be displayed on the video cover in each play record.

[0192] As another method, the historical playback records of each application may be displayed separately according to different applications.

[0193] Exemplarily, the large screen device 100 may display: Fig.17 The historical play record list 127 shown in (a) of FIG. The historical play record list 127 may include an application selection list on the left and a play record display list on the right. Fig.17 As shown in (a) of FIG. 1 , the application selection list on the left may include a video application 1 option 128 and a video application 2 option 129. When the user 300 selects the video application 1 option 128 in the historical play record list 127 by using the direction button on the remote control 200, the play record display list on the right is as shown in FIG. Fig.17 As shown in (a), the historical playback records matching the account "user A" of the currently logged-in user 300 in the video application 1 are displayed. The historical playback records can also be displayed in the order of playback time.

[0194] When the user 300 switches to and selects the video application 2 option 129 in the historical play record list 127 by using the direction button on the remote control 200, the play record display list on the right is as follows: Fig.17 As shown in (b) in FIG. 1 , the historical playback records matching the account “User A” of the currently logged-in user 300 in the video application 2 are displayed accordingly.

[0195] Alternatively, if Fig.17 As shown in (b) in the figure, the historical playback record list displayed by the large-screen device 100 may also display the matching account information 130 , such as the account name and account avatar of the currently logged-in user 300 .

[0196] As a method, each historical playback record can also be displayed in the form of a progress bar. Fig.17 As shown in (c) of FIG. 1 , the play progress bar of each historical play record includes a black area 131 and a white area 132. The black area 131 is the part that has been played, i.e., the play progress, and the white area 132 is the part that has not been played. The name, play progress, and other information of the multimedia content corresponding to each historical play record can be displayed on the progress bar, or on the top side or the bottom side of the progress bar.

[0197] In one scenario, the large-screen device 100 may also trigger the above-mentioned account quick switching process when entering a certain application or opening a historical playback record in a certain application.

[0198] For example, Fig.18 As shown in (a) of FIG. 1 , the user 300 operates the remote controller 200 to click the icon 106 of the video application 1 displayed on the large-screen device 100. In response to the click operation, the large-screen device 100 opens the video application 1 and may display the video application 1 as shown in FIG. Fig.18 The application interface of the video application 1 shown in (b) in FIG. 1 . If the video application 1 is currently logged into a platform account, the application interface of the video application 1 may display the logged-in platform account information 114 , such as displaying the logged-in platform account name “user b”.

[0199] Since the platform account currently logged in by the video application 1 may not match the user 300 in the current scene, in the embodiment of the present application, when the large-screen device 100 enters the video application 1, the large-screen device 100 can identify the registered user in the current scene (the user who has registered the platform account of the video application 1), and identify the user who is operating the remote control 200 in the current scene. It can be understood that if the user 300 has registered his own platform account on the video application 1 and the account name is "user a", the large-screen device 100 can identify the user 300 as a registered user.

[0200] When the user 300 in the current scene is identified as a registered user and the user who is operating the remote controller 200, the large screen device 100 can determine whether the platform account currently logged in by the video application 1 matches the platform account "user a" of the user 300 currently operating the remote controller. Fig.18 As shown in (c) in the figure, the large-screen device 100 may display a prompt window 117 to prompt the user 300 whether to switch to his or her account "user a".

[0201] Optionally, after the user confirms the switch via the remote controller 200, Fig.18 As shown in (d) in FIG. 1 , the logged-in platform account information 114 displayed in the application interface of the video application 1 is updated to the platform account name "user a" after the switch login. After the user continues to operate the remote control to click the history control 107 in the application interface of the video application 1, the large-screen device 100 may display the following information: Fig.18 The historical play record page 115 shown in (e) in FIG. 1 shows the historical play record in the video application 1 that matches the currently logged-in platform account “user a”.

[0202] Optionally, after the user cancels the switch through the remote controller 200, the platform account currently logged in by the video application 1 is still "user b". Fig.18 As shown in (b) of FIG. 1 , after the user clicks the history control 107 in the application interface of the video application 1 through the remote control, the large screen device 100 may display the following Fig.18 The historical play record page 115 shown in (f) in FIG. 1 shows the historical play record in the video application 1 that matches the currently logged-in platform account "user b".

[0203] For example, the large screen device 100 may also trigger the above account switching process when opening the historical playback record page 115 in the video application 1 to display the historical playback record adapted to the user in the current scene. Fig.18As shown in (f) in FIG. 1 , when the large-screen device 100 enters the historical playback record page 115 of the video application 1, the large-screen device 100 can identify the registered users in the current scene and the user who is operating the remote control 200 in the current scene. When the user 300 in the current scene is identified as a registered user and the user who is operating the remote control 200, the large-screen device 100 can determine whether the platform account currently logged in to the video application 1 matches the platform account "user a" of the user 300 currently operating the remote control. When it is determined that there is no match, such as Fig.18 As shown in (g) in FIG. 1 , the large screen device 100 may display a prompt window 117 on the historical playback record page 115 to prompt the user 300 whether to switch to his account "user a". After the user confirms the switch through the remote control 200, as shown in FIG. Fig.18 As shown in (e), the historical playback record page 115 of the video application 1 can display the platform account name "user a" after switching login, and display the historical playback records in the video application 1 that match the currently logged in platform account "user a".

[0204] Optionally, each historical playback record in the historical playback record page 115 can also be displayed in the form of a progress bar. Fig.18 As shown in (h) in FIG. 1 , the playback progress bar of each historical playback record includes a black area and a white area. The black area is the part that has been played, i.e., the playback progress, and the white area is the part that has not been played. The name, playback progress, playback time, and other information of the multimedia content corresponding to each historical playback record can be displayed on the progress bar or near the progress bar.

[0205] Scenario 2: Multiple users viewing a large-screen device.

[0206] like Fig.19 As shown in (a), in the current scene, there are multiple users (such as user 300, user 400, and user 500) watching the large-screen device 100, wherein user 300 is operating the remote control 200. After the large-screen device 100 collects the scene image of the current scene through the camera, it can perform face recognition on the scene image to identify all registered users in the current scene. The large-screen device 100 can obtain the historical playback records of registered users in various applications.

[0207] Assume that user 300, user 400, and user 500 have registered their own accounts on the large-screen device 100, and the account names are "User A", "User B", and "User C", respectively. Since the large-screen device 100 pre-stores the facial information of all registered users, including the facial information of user 300, user 400, and user 500. Therefore, the large-screen device 100 can identify the identity information of user 300, user 400, and user 500 by comparing the facial images of user 300, user 400, and user 500 in the real-time collected scene image with the pre-stored facial information of the registered users. User 300, user 400, and user 500 are all registered users.

[0208] If there are other users in the current scene, and the other users have not registered accounts with the large-screen device 100, the large-screen device 100 can identify the other users as unregistered users by comparing the pre-stored facial information of registered users with the facial images of the other users in the scene image collected in real time. When no facial information of a registered user can be found in the pre-stored facial information of the registered user that matches the facial image of the other user, the other user can be confirmed to be an unregistered user.

[0209] In the embodiment of the present application, in addition to identifying all registered users in the current scene, the large-screen device 100 can also identify the user who is operating the remote control 200 in the current scene.

[0210] As one way, the large-screen device 100 can identify the user 300 who is currently holding the remote controller 200, that is, the user who is operating the remote controller 200, by performing body posture recognition on all users in the scene image. As another way, the large-screen device 100 can also use ultrasonic positioning technology to determine the approximate position of the remote controller 200, and then identify the user 300 corresponding to the position, that is, the user who is operating the remote controller 200, in combination with the positions of each user in the scene image.

[0211] After the large-screen device 100 recognizes that the user operating the remote controller 200 in the current scene is the user 300 , it can determine whether the account currently logged into the large-screen device 100 is the account of the user 300 currently operating the remote controller.

[0212] like Fig.19 As shown in (a) in the figure, if the large-screen device 100 displays the account information 133 of the currently logged-in account as the account name "User E", the large-screen device 100 can determine that the account currently logged in to the large-screen device 100 is not the account of the user 300 currently operating the remote control based on the pre-stored account information of the user 300 (including the account name "User A"). Therefore, when the user 300 starts to operate the remote control 200, the large-screen device 100 can prompt the user whether to switch accounts.

[0213] As a way, Fig.19 As shown in (b) of the figure, the large-screen device 100 may pop up a prompt window 134. The prompt window 134 may include an inquiry message "! The current logged-in account does not match! Do you want to switch accounts?" and a "Confirm" button and a "Cancel" button. Optionally, the prompt window 134 may also include the account information of the currently logged-in account and the account information of the registered user identified in the current scenario, so that the user can make an accurate choice after understanding the current account switching scenario.

[0214] Since the user 300 currently operating the remote controller 200 is a registered user, the account information of the registered users identified in the current scene may include the account information of the user 300 currently operating the remote controller 200. The prompt window 134 may preferentially recommend the account information of the user 300 currently operating the remote controller 200 to the user.

[0215] like Fig.19 As shown in (b) of FIG. 1 , the prompt window 134 may display the account name "User E" of the currently logged-in account and the account avatar 135 corresponding to "User E", as well as the account name "User A" of the user 300 currently operating the remote controller and the account avatar 136 corresponding to "User A". Thus, the user 300 may operate the remote controller 200 to click the "Confirm" button in the prompt window 134 to instruct the large-screen device 100 to switch to the account of the user 300.

[0216] Since the current scene also includes other registered users, the prompt window can also display the account switching list of all registered users in the current scene. Optionally, in the account list of all registered users in the current scene, the account name and account avatar of each registered user can be displayed so that the user can intuitively understand the account information that can be quickly switched.

[0217] Exemplarily, the large screen device 100 may pop up a Fig.19 The prompt window 137 shown in (c) in FIG. The prompt window 137 displays the account name "User E" of the currently logged-in account and the account avatar corresponding to "User E", as well as the account names and corresponding account avatars of all registered users identified in the current scene, namely, the account name "User A" of user 300 and the account avatar 138 corresponding to "User A", the account name "User B" of user 400 and the account avatar 139 corresponding to "User B", and the account name "User C" of user 500 and the account avatar 140 corresponding to "User C".

[0218] It can be understood that the large-screen device 100 can give priority to recommending switching to the account information of the user 300 currently operating the remote control. Therefore, the account information of the user 300 currently operating the remote control can be highlighted. Fig.19 As shown in (c) in FIG. 1 , the account name “User A” of the user 300 and the account avatar 138 corresponding to “User A” are highlighted.

[0219] At this time, the user 300 can operate the remote controller 200 to click the "Confirm" button in the prompt window 137 to instruct the large-screen device 100 to switch to log in to his account. The user 300 can also operate the direction button on the remote controller 200 to switch to the selected account of another registered user, and then operate the remote controller 200 to click the "Confirm" button in the prompt window 137 to complete the switch to log in to the account of another registered user.

[0220] Optionally, the large screen device 100 may also pop up Fig.19 The account list shown in (d) in the figure is used to prompt the user to switch accounts. The account list includes account floating bars of all registered users in the current scene, and the top of the account floating bar corresponds to the account avatar. Fig.19 As shown in (d) in the figure, the large-screen device 100 may pop up a floating bar 141 containing the account avatar of user 300, a floating bar 142 containing the account avatar of user 400, and a floating bar 143 containing the account avatar of user 500. Among them, the floating bar 141 of the account avatar of user 300 who is currently operating the remote control is highlighted. At this time, when the user presses the "confirm" button on the remote control 200, the large-screen device 100 can be instructed to quickly switch to his account. Optionally, the user can switch to the floating bar of the account avatar of other registered users (such as the floating bar 143 containing the account avatar of user 500) by operating the direction button on the remote control 200, and then press the "confirm" button on the remote control 200 to instruct the large-screen device 100 to quickly switch to the account of other registered users (such as the account "user C" of user 500). Optionally, the user can also cancel the account switching by pressing the "return" button on the remote control 200, and the current login account of the large-screen device 100 is still "user E".

[0221] It can be understood that after the user 300 completes the account switching action, the user 300 will no longer be prompted to switch accounts until the user 300 puts down the remote control 200.

[0222] In one scenario, after user 300 quickly chooses to switch to his own account, Fig. 20 As shown in (a), the large-screen device 100 can display the account information 144 of the user 300 after switching login, such as displaying the account name "User A" after switching login.

[0223] In one scenario, after the user 300 switches to his own account through the quick selection, the user can open the corresponding application on the large-screen device 100 to view the historical playback records of the multimedia content under the application.

[0224] In one scenario, after the user 300 quickly chooses to switch to his own account, the user can view the historical playback records of his multimedia content under various applications on the main interface of the large-screen device 100. Optionally, the large-screen device 100 can also display the historical playback records of other registered users in the current scenario on the main interface.

[0225] As a method, after the large-screen device 100 recognizes all registered users in the current scene, it can obtain the historical playback records of each registered user's account in each application through the account information of each registered user. Then the large-screen device 100 can generate the historical playback records corresponding to each registered user's account and display them on the main interface. Among them, the historical playback records corresponding to each account merge the historical playback records of the account in each application.

[0226] like Fig. 20 As shown in (b) of the diagram, the large-screen device 100 displays a main interface, which includes multiple options, such as input source options, video options, music options, gallery options, etc. When the user 300 selects the video option in the main interface by operating the remote control 200 (the video option can be highlighted at this time), the large-screen device 100 can display two columns of historical playback records. One column is the historical playback records 145 of each video application under the account of the currently logged-in user 300, and the other column is the historical playback records 146 of each video application under the account of other registered users in the current scene.

[0227] The historical play records 145 of each video application under the account of the currently logged-in user 300 may be as described in Scenario 1, and will not be described again.

[0228] As a method, in the historical playback record 146, the historical playback records of various video applications under the accounts of other registered users in the current scene can be displayed in pages according to different accounts.

[0229] For example, Fig. 20As shown in (b) in FIG. 1 , the historical play record 146 may include a user avatar selection list on the upper side and a play record display list on the lower side. The user avatar selection list on the upper side may include an account avatar 147 of user 400 and an account avatar 148 of user 500. When user 300 selects the account avatar 147 of user 400 in the historical play record list 146 by using the direction button on the remote control 200, the play record display list on the lower side will display the historical play records of the account "User B" of user 400 in each application. The historical play records may be displayed in the order of play time.

[0230] When user 300 switches to select the account avatar 148 of user 500 in the historical playback record list 146 through the direction buttons on the remote control 200, the playback record display list on the lower side correspondingly displays the historical playback records of user 500's account "User C" in various applications.

[0231] As another way, in the main interface, the historical play records of user 400 and user 500 in each application can also be displayed separately, without being displayed together in the historical play record 146. In this way, three columns of historical play records can be displayed in the main interface, namely, the historical play records of user 300, the historical play records of user 400, and the historical play records of user 500.

[0232] Optionally, each historical playback record can also be displayed in the form of a progress bar. Fig.21 As shown in (a) in the figure, the large screen device 100 displays two columns of historical playback records on the main interface, one of which is a progress bar 149 of the historical playback records under the account of the currently logged-in user 300, and the other is a progress bar 150 of the historical playback records under the accounts of other registered users in the current scene. The playback progress bar of each historical playback record includes a black area and a white area. The black area is the part that has been played, that is, the playback progress, and the white area is the part that has not been played.

[0233] As a method, in the main interface, in addition to displaying the historical playback records of each video application under the account of the currently logged-in user 300, the historical playback records of all registered users in the current scene can also be integrated and displayed.

[0234] For example, Fig.21 As shown in (b), the large-screen device 100 can display two columns of historical playback records in the main interface, one column is a progress bar 149 of the historical playback records under the account of the currently logged-in user 300, and the other column is the integrated historical playback records 151 of all registered users in the current scene.

[0235] There are many ways to display the integrated historical playback record 151, which is not limited in the embodiment of the present application.

[0236] As a method, the large-screen device 100 can assign a theme color to each user account for display, so as to distinguish and display the information such as the avatar frame and the playback progress with the theme color. Optionally, the large-screen device 100 can also integrate the information of multiple users watching the same video and display it in the same progress bar. Among them, although multiple users watch the same video, it is likely that their respective playback progress is different. Therefore, by displaying their respective playback progress in the theme color in the same progress bar, even if they are integrated and displayed in the same progress bar, the playback progress of each user can be intuitively understood.

[0237] For example, Fig.21 As shown in (b), it is assumed that the theme color of user 300's account "User A" is represented by black, the theme color of user 400's account "User B" is represented by white, and the theme color of user 500's account "User C" is represented by stripes. Since in the historical playback records of user 300's account "User A", "Video 7" has been played 50% and "Video 3" has been played 30%, in the historical playback records of user 400's account "User B", "Video 7" has been played 80% and "Video 4" has been played 70%, in the historical playback records of user 500's account "User C", "Video 7" has been played 93%, "Video 3" has been played 80%, and "Video 4" has been played 90%. Therefore, the large-screen device 100 can display the following. Fig.21 The fused historical playback record 151 shown in (b).

[0238] Among them, in the integrated historical playback record 151, the playback progress of the three users, user 300, user 400, and user 500, watching the same video "Video 7" are integrated and displayed in the same progress bar, forming a fusion progress bar of "Video 7" adapted to the users in the current scene; the playback progress of the two users, user 300 and user 500, watching the same video "Video 3" are integrated and displayed in the same progress bar, forming a fusion progress bar of "Video 3" adapted to the users in the current scene; the playback progress of the two users, user 400 and user 500, watching the same video "Video 4" are integrated and displayed in the same progress bar, forming a fusion progress bar of "Video 4" adapted to the users in the current scene. And the playback progress of different users in the same progress bar is displayed with the corresponding theme color. Fig.21As shown in (b) of FIG. 1 , in the fusion progress bar of "Video 7", the playback progress of the account "User A" of user 300 is displayed in black, the playback progress of the account "User B" of user 400 is displayed in white, and the playback progress of the account "User C" of user 500 is displayed in stripes. Optionally, the user can directly select the playback progress in the fusion progress bar to quickly play the video to be played, and the video starts playing based on the selected playback progress.

[0239] Optionally, the fusion progress bar of each video can display the user account information that has played the video in the current scene. Fig.21 As shown in (b) in the figure, the fusion progress bar of "Video 4" displays the account information of user 400 and user 500 who have played "Video 4" in the current scene, namely, the account name "User B" and the corresponding account avatar, and the account name "User C" and the corresponding account avatar. Optionally, user 300 can directly select the user avatar to quickly play the video to be played, and the video starts playing based on the playback progress corresponding to the selected user avatar.

[0240] Optionally, other information of the video, such as ratings, number of views, etc., may also be displayed on one side of the integrated progress bar so that the user can understand the details of the historically played videos.

[0241] As a method, the fusion progress bar can be arranged in descending order according to the number of users who have played the video in the current scene. For example, in the current scene, 3 users have played "Video 7", 2 users have played "Video 3", and 2 users have played "Video 4". Since the number of users who have played "Video 7" in the current scene is the largest, Fig.21 As shown in (b), in the fusion history playback record 151, the fusion progress bar of "Video 7" is displayed at a more forward position.

[0242] If there are different videos that have been played by the same number of users in the current scene, such as "Video 3" and "Video 4" have both been played by two users in the current scene, then as a way, the order of the fusion progress bars of the different videos can be determined randomly or according to the initial alphabetical order of the video names. This is not limited in the embodiments of the present application. For example, it can also be determined according to the size of the sum of the playback progress.

[0243] If there are different videos that have been played by the same number of users in the current scene, then as another method, the arrangement of the fusion progress bars of the different videos can be arranged using the following formula:

[0244] F(V x )=(w x P y +(1-wx )(100-(max(L p )-min(L p ))))×S / 1000,L u ;

[0245] Among them, V x Indicates the videos played by the user in the current scene, such as V1 for "Video 3" and V2 for "Video 4". F represents the sorting calculation formula of the video fusion progress bar, F(V x ) indicates that the video V is calculated using the sorting calculation formula x , and get the result value. The arrangement of the fusion progress bars of different videos can be installed with the result value, and arranged from large to small. That is, the larger the result value, the higher the fusion progress bar of the corresponding video is.

[0246] Among them, L in the above formula u Indicates that the video V has been played in the current scene x For example, V x When it is V1, i.e., Video 3, L u For [account "user A", "user C"]. x When it is V2 (Video 4), L u is ["User B", "User C"].

[0247] L p Indicates that the video V has been played in the current scene x The user's playback progress list, where the progress value range is [0,100]. For example, V x When it is V1, i.e., Video 3, L p =[“User A”’s playback progress 30, “User C”’s playback progress 80]. x When it is V2 (Video 4), L u It is [“User B”’s playback progress 70, “User C”’s playback progress 90].

[0248] max(L p ) is L p The maximum value among the videos V played in the current scene x The highest playback progress among users. x When it is V1 (Video 3), max(L p ) is 80.

[0249] min(L p ) is L p The minimum value among the values ​​indicates that the video V has been played in the current scene. x The lowest playback progress among users. xWhen it is V1 (Video 3), min(L p ) is 30.

[0250] max(L p )-min(L p ) represents the difference between the highest playback progress and the lowest playback progress, which can be understood as the difference in playback progress between multiple users when multiple users play the same video. p )-min(L p ) is larger, the greater the difference in playback progress between users.

[0251] S is for video V x The score of , where the score range is [1,10]. 1000 is the normalization parameter.

[0252] w x Indicates the weight of the historical playback records under the current login account. y Indicates the playback progress of the currently logged-in account. The user of the currently logged-in account can configure the weight to choose whether to prioritize the videos he has played. For example, V1, i.e., "Video 3", has been played by the currently logged-in account "User A", while V2, i.e., "Video 3", has not been played by the currently logged-in account "User A". Therefore, the weight of V1 can be configured so that the result value of F(V1) is greater than F(V2). In this way, although "Video 3" and "Video 4" have been played by 2 users in the current scene, since "Video 3" has been played by the currently logged-in account "User A", Fig.21 As shown in (b) in FIG. 1 , in the fusion history playback record 151, "Video 3" can be displayed before "Video 4". In this way, the history playback records under the current login account can be ranked higher than other users in the current scene. Optionally, if video V x If it has not been played by the currently logged-in account "User A", then w x Can be 0 or the default value.

[0253] It can be understood that if there are different videos that have been played by the same number of users in the current scene, then the above formula F(V x ), after calculating the result values ​​of the different videos, the video with the smallest difference in user playback progress and a higher user score can be ranked relatively higher.

[0254] In one scenario, the large-screen device 100 may also trigger the above-mentioned account quick switching process when it is necessary to display historical playback records.

[0255] For example, when the user 300 selects the video option in the main interface of the large-screen device 100 by operating the remote control, the large-screen device 100 displays the historical playback records of each video application under the current login account by default in the main interface. Since the current login account of the large-screen device 100 is "User E", the historical playback records displayed are the historical playback records of each video application that match the account "User E".

[0256] Since the current login account of the large-screen device 100 may not match the user in the current scene, the historical playback records displayed on the main interface of the large-screen device 100 may not meet the user's needs. Therefore, in the embodiment of the present application, when the large-screen device 100 displays the historical playback records on the main interface, the large-screen device 100 can identify the registered users in the current scene, such as user 300, user 400, and user 500, and identify the user who is operating the remote control 200 in the current scene as user 300. When identifying that the user 300 in the current scene is a registered user and is the user who is operating the remote control, the large-screen device 100 can determine whether the current login account "User E" matches the account "User A" of the user 300 currently operating the remote control.

[0257] When it is determined that there is no match, the large-screen device 100 can display a prompt window to prompt whether to switch to your own account. After the user confirms the switch through the remote control, the large-screen device 100 can display the account name "User A" of the user 300 after the switch login in the main interface, and the historical playback records of the main interface are switched to display the historical playback records matching the account "User A" in each video application. And because there are other registered users in the current scene, the large-screen device 100 can also add the historical playback records of other registered users (i.e., user 400 and user 500) in the current scene in the main interface, or add the fusion historical playback records of all registered users (i.e., user 300, user 400 and user 500) in the current scene. In this way, in the scene where multiple people watch the large-screen device, when displaying the historical playback records, the large-screen device can display the historical playback records of a single user corresponding to the current login account, or display or fuse the historical playback records of multiple users watching the large-screen device in the current scene.

[0258] In one scenario, if user 300 quickly chooses to cancel switching to his own account, the current login account of the large-screen device 100 is still "User E", and the large-screen device 100 still displays the historical playback records matching the account "User E" in each video application in the historical playback records on the main interface. Optionally, the large-screen device 100 can also display the historical playback records of all registered users in the current scene in the main interface. As an example, the large-screen device 100 can display two columns of historical playback records on the main interface. One column is the historical playback records of each video application under the current login account "User E", and the other column is the fusion historical playback records of each video application under the accounts of all registered users in the current scene, that is, the account "User A" of user 300, the account "User B" of user 400, and the account "User C" of user 500. Among them, the fusion historical playback records can be as described above, and will not be repeated here.

[0259] In one scenario, the large-screen device 100 may also trigger the above-mentioned account quick switching process when entering a certain application or opening a historical playback record in a certain application.

[0260] For example, Fig. 22 As shown in (a) of FIG. 1 , in the current scene, there are multiple users (such as user 300, user 400, and user 500) watching the large-screen device 100, wherein user 300 is operating the remote controller 200. When user 300 clicks the icon 106 of the video application 1 displayed on the large-screen device 100 through the remote controller 200, in response to the click operation, the large-screen device 100 opens the video application 1 and may display the video application 1 as shown in FIG. Fig. 22 The application interface of the video application 1 shown in (b) of FIG. 1 . If the video application 1 is currently logged into a platform account, the application interface of the video application 1 may display the logged-in platform account information 114 , such as displaying the logged-in platform account name “user e”.

[0261] Since the platform account currently logged in to the video application 1 may not match the user 300 who is operating the remote control 200 in the current scene, in an embodiment of the present application, when the large-screen device 100 enters the video application 1, the large-screen device 100 can use face recognition technology to identify the registered users in the current scene (users who have registered a platform account for the video application 1), and identify the user who is operating the remote control 200 in the current scene through human posture recognition or ultrasonic positioning technology.

[0262] It can be understood that if user 300, user 400, and user 500 have registered their own platform accounts on video application 1, and the account names are "user a", "user b", and "user c", respectively, the large-screen device 100 can recognize that user 300, user 400, and user 500 are all registered users. If there are other users in the current scene, and the other users have not registered accounts on video application 1, the large-screen device 100 can recognize that the other users are unregistered users.

[0263] In the embodiment of the present application, when the user 300 in the current scene is identified as a registered user and the user who is operating the remote controller 200, the large-screen device 100 can determine whether the platform account "user e" currently logged in by the video application 1 matches the platform account "user a" of the user 300 currently operating the remote controller. If it is determined that there is no match, the large-screen device 100 can prompt the user whether to switch accounts.

[0264] As a method, the large-screen device 100 may pop up a prompt window. The prompt window may include the account information of the currently logged-in platform account and the account information of the registered user identified in the current scene, so that the user can make an accurate choice after understanding the current account switching scene.

[0265] Optionally, since the user 300 who is currently operating the remote controller 200 is a registered user, the prompt window may preferentially recommend the account information of the user 300 who is currently operating the remote controller 200 to the user.

[0266] Optionally, since the current scene also includes other registered users, the prompt window may also display an account switching list of all registered users in the current scene. In the account list of all registered users in the current scene, the account name and account avatar of each registered user may be displayed so that the user can intuitively understand the account information that can be quickly switched.

[0267] For example, Fig. 22 As shown in (c) in the figure, the large-screen device 100 can display a prompt window 153 on the application interface of the video application 1, and the prompt window 153 displays the account name "user e" of the currently logged-in platform account and the corresponding account avatar, as well as the account names and corresponding account avatars of all registered users identified in the current scene, that is, the account names and corresponding account avatars of user 300, user 400, and user 500. Among them, the account name "user a" and the corresponding account avatar of user 300 who is currently operating the remote control can be highlighted.

[0268] At this time, the user can operate the remote control to click the "Confirm" button in the prompt window 153 to instruct the large-screen device 100 to switch to log in to his own platform account. The user can also operate the direction buttons on the remote control to switch to the platform account of other registered users, and then click the "Confirm" button in the prompt window 153 to complete the switch to log in to the platform account of other registered users.

[0269] Optionally, after the user quickly switches to his platform account through the remote control, such as Fig. 22 As shown in (d) in FIG. 1 , the logged-in platform account information 114 displayed in the application interface of the video application 1 is updated to the platform account name “user a” after the login is switched.

[0270] In one scenario, after the user quickly switches to his / her platform account through the remote control, the user continues to operate the remote control to click the history control 107 in the application interface of the video application 1. Fig. 22 As shown in (e) in the figure, the large screen device 100 can display a historical play record page 115. The historical play record page 115 includes two columns of historical play records, one of which is a progress bar 154 of historical play records under the currently logged-in platform account, and the other is a progress bar 155 of historical play records under the platform accounts of other registered users in the current scene.

[0271] Optionally, after the user cancels the switch to his own platform account through the remote controller 200, the platform account currently logged in by the video application 1 is still "user e". Fig. 22 As shown in (b) of FIG. 1 , after the user clicks the history control 107 in the application interface of the video application 1 through the remote control, the large screen device 100 may display the following Fig. 22 The historical play record page 115 shown in (f) in FIG. The historical play record page 115 includes two columns of historical play records, one of which is a progress bar 156 of the historical play records under the currently logged-in platform account "user e", and the other is a progress bar 157 of the combined historical play records under the platform accounts of all registered users in the current scene, that is, the platform accounts "user a", "user b", and "user c" of user 300, user 400, and user 500. In this way, the historical play records of a single user corresponding to the currently logged-in platform account can be displayed, and the historical play records of multiple users watching the large-screen device in the current scene can also be displayed.

[0272] Optionally, when displaying the historical playback records under the platform accounts of all registered users in the current scene, the historical playback records of each platform account in each application can also be displayed separately and independently, without having to display them in a centralized list.

[0273] In one scenario, the large-screen device 100 may also trigger the above-mentioned account switching process when opening the historical playback record page 115 in the video application 1 to display the historical playback record adapted to the user in the current scenario.

[0274] Exemplarily, the large screen device 100 enters the Fig. 22 When the historical playback record page 115 of the video application 1 shown in (f) of FIG. 1 is displayed, the large-screen device 100 displays the progress bar 156 of the historical playback record of "user e" under the currently logged-in platform account by default. At this time, the large-screen device 100 can identify the registered users in the current scene, such as user 300, user 400, and user 500, and identify the user who is operating the remote controller 200 in the current scene.

[0275] Optionally, after identifying the registered users in the current scene, the large-screen device 100 can add a new historical playback record 157 of all registered users in the current scene in the historical playback record page 115. The historical playback record display adapted to the users in the current scene is realized. Optionally, the historical playback record 157 can also include the historical playback record of "user e" under the currently logged-in platform account. In this way, the historical playback record of the currently logged-in account can be displayed independently, or the historical playback record of the currently logged-in account can be displayed together with other registered users in the current scene.

[0276] Optionally, when the user 300 in the current scene is identified as a registered user and the user who is operating the remote controller 200, the large screen device 100 can determine whether the platform account "user e" currently logged in by the video application 1 matches the platform account "user a" of the user 300 currently operating the remote controller. Fig. 22 As shown in (g) in FIG. 1 , the large screen device 100 may display a prompt window 153 on the historical playback record page 115 to prompt the user 300 whether to switch to his account "user a". After the user 300 confirms the switch through the remote control 200, as shown in FIG. Fig. 22 As shown in (e), the platform account name "User a" after the switch login can be displayed in the historical playback record page 115 of the video application 1, and the progress bar 154 of the historical playback record of the platform account "User a" after the switch login can be displayed in the historical playback record page 115.

[0277] As a method, in the historical playback record page 115, in addition to displaying the progress bar 154 of the historical playback record of the platform account "user a" after switching login, the progress bar 155 of the historical playback record of other registered users in the current scene can also be displayed.

[0278] As a method, in the historical playback record page 115, in addition to displaying the progress bar 154 of the historical playback record of the platform account "user a" after switching login, the progress bars of the historical playback records of all registered users in the current scene can also be integrated and displayed.

[0279] For example, Fig. 22 As shown in (h) in the figure, the large-screen device 100 can display two columns of historical playback records in the main interface, one of which is a progress bar 154 of the historical playback records under the currently logged-in platform account "user a", and the other is a fusion progress bar 158 of the historical playback records of all registered users in the current scene. The fusion progress bar can refer to the above description and will not be repeated here.

[0280] Based on the above introduction to the overall process of the method for displaying playback records provided in the embodiment of the present application, the method for displaying playback records provided in the embodiment of the present application is described in detail below. The method for displaying playback records can be applied to a first device (such as the large-screen device 100 described above), and the user can control the first device by operating a second device (such as a remote controller).

[0281] Fig.23 A flowchart of a method for displaying playback records provided in an embodiment of the present application is shown in FIG. Fig.23 As shown, the specific process of the method for displaying the playback record may include:

[0282] S2301, the first device obtains a scene image.

[0283] The first device may be configured with N cameras, which may be built into the first device or disposed outside the first device. The N cameras may capture the scene in front of the screen of the first device to obtain an image of the scene in front of the screen of the first device. The first device may then read the image of the scene captured by the camera. Wherein, N is an integer greater than or equal to 1. When the value of N is greater than 1, the shooting directions of different cameras may not overlap or may partially overlap.

[0284] As a method, the first device may also record the scene in front of the screen of the first device through a camera to obtain video data in front of the screen of the first device. Through the video data, an image of the scene in front of the screen of the first device may be obtained. Optionally, the first device includes multiple video frames (i.e., images), and the first device may perform a video frame extraction operation on the video data to obtain an image of the scene in front of the screen of the first device.

[0285] It is understandable that when multimedia content is played on the screen of the first device, there may be one user or multiple users watching in front of the screen of the first device. Therefore, by acquiring the scene image in front of the screen of the first device, the first device can timely sense the number of users watching in front of the current screen, the identity of the users, and other information.

[0286] Optionally, the first device shoots the scene in front of the first device screen at a preset frequency to obtain the scene image in front of the first device screen at a regular interval, so as to timely sense whether the scene in front of the current first device screen changes.

[0287] In one case, when the first device is turned on, the camera on the first device may be triggered to automatically start to continuously or periodically shoot the scene in front of the screen of the first device, so as to obtain the scene image in front of the current screen of the first device as soon as possible after the power is turned on, so as to facilitate the identification of the number of users watching in front of the current screen, the identity of the users and other information. The power-on of the first device may be automatic power-on of the first device, or the user may control the power-on through the second device. The second device may be an auxiliary device such as a remote control (such as an infrared remote control, a Bluetooth remote control), a keyboard, a mouse, etc. For example, taking the second device as a remote control, the user may press the power button on the remote control to control the power-on of the first device. The scene image may also help to identify the user currently operating the second device.

[0288] In one case, when the second device begins to be operated, the first device may trigger the camera on the first device to automatically start continuously or periodically photographing the scene in front of the screen of the first device, so as to obtain the current scene image in front of the screen of the first device when a user operates the second device, thereby facilitating identification of the user currently operating the second device.

[0289] In one case, when the first device opens the first application, the first device may trigger the camera on the first device to automatically and continuously or periodically capture the scene in front of the screen of the first device, so as to obtain the scene image in front of the current screen of the first device after entering the first application, so as to facilitate identification of the number of users watching in front of the current screen, the identity of the users, the user currently operating the second device, and other information. The first application may be an application for presenting multimedia content such as audio and video, such as Fig.18 The “video application 1”, “video application 2”, “music application 1”, “music application 2”, etc. shown in (a) are not limited in this application.

[0290] In one case, when the first device displays the first interface, the camera on the first device can be triggered to automatically start continuously or periodically photographing the scene in front of the screen of the first device, so as to obtain the scene image in front of the current screen of the first device when entering the first interface.

[0291] Optionally, the first interface is a startup interface of the first device, and the startup interface is an interface displayed after the first device is started. Fig.15 The interface including multiple application icons as shown in (a) in FIG. 1 . For another example, the first interface may also be as follows Fig.15 The main interface shown in (d) includes input source options, video options, music options, etc.

[0292] Optionally, the startup interface includes a first control for triggering the display of historical playback records of multimedia content matching the current login account of the first device. Fig.15 As shown in (d) in the figure, the first control may be a control for a video option in the main interface. When the user selects the control for the video option by operating the second device, the first device may display the historical playback records of each video application under the current login account in the main interface. For another example, the first control may be a control for a music option in the main interface. When the user selects the control for the music option by operating the second device, the first device may display the historical playback records of each music application under the current login account in the main interface.

[0293] The first interface may be an interface for displaying historical playback records after the first control in the startup interface is triggered. Fig.15 After selecting the control of the video option as shown in (d), the interface of the historical playback record of the videos under the currently logged-in account is displayed in the main interface.

[0294] Optionally, the first interface is a home page interface of the first application, and the home page interface is an application interface displayed when the first device opens the first application. Fig.18 The application interface of the video application 1 shown in (a).

[0295] Optionally, the home page interface of the first application includes a first control, which is used to trigger the display of historical playback records in the first application that match the current login account. Fig.18 As shown in (d) in FIG. 1 , the first control may be a history record control 107 in the application interface of the video application 1. When the user selects the history record control 107 by operating the second device, the first device may display the following information: Fig.18 The historical play record page 115 of the first application shown in (e).

[0296] The first interface may be an interface for displaying historical playback records in the first application. Fig.18 The historical play record page 115 of the first application shown in (e).

[0297] It is understood that the first device may acquire the scene image by using other image acquisition devices in addition to the camera, and this application does not limit this. For example, the first device may also be configured with an infrared sensor, and the first device may acquire the image sensed by the infrared sensor as the scene image.

[0298] S2302, the first device determines whether there is a registered user in the current scene according to the scene image. If yes, execute S2303, if not, end the process.

[0299] The first device can identify the identity information of each user in the current scene through face recognition to determine which is a registered user and which is an unregistered user.

[0300] There are many methods for face recognition. Such as face recognition methods based on geometric features, face recognition methods based on feature faces, face recognition methods based on neural networks, etc., which are not limited in the embodiments of the present application. As one method, the open source face recognition algorithm library CompareFace can be used for face recognition. The algorithm library has the characteristics of easy deployment, high recognition accuracy, and the ability to recognize multiple faces at the same time. The use of this algorithm library can meet the face recognition task in the multi-person viewing scenario in this application. Thereby, the identity information of multiple users in the current scene can be confirmed, and which users are registered users and which users are unregistered users can be confirmed.

[0301] In one scenario, the first device can establish a facial information library of registered users. For example, when a user registers an account of the first device, or when a user registers a platform account of the first application, the user's facial image can be captured by an image capture device such as a camera, so that the captured facial image is associated with the user's registered account and stored. Subsequently, when the first device captures the scene image of the current scene in real time, the facial image in the current scene image can be extracted and compared with the facial information library of registered users. If there is a facial image in the current scene image that matches the facial image in the facial information library, it can be confirmed that the user corresponding to the facial image in the scene image is a registered user.

[0302] Optionally, if the first device obtains a facial image of a single user contained in the scene image, the first recognition is performed through facial recognition. If the single user is identified as a registered user, the first device can determine that there is a registered user in the current scene. At this time, the first device can obtain the account information of the single user, such as the account name, account avatar, etc., and can also obtain the historical playback record information of the single user. Conversely, if the single user is identified as an unregistered user, the first device can determine that there is no registered user in the current scene, and the first device may not execute the playback record display method provided in this application. At this time, the first device may only obtain the historical playback record information of the currently logged-in account for display. If the account is not currently logged in, the first device may not display the historical playback record information, or display the historical playback record information of the visitor user.

[0303] Optionally, if the first device obtains facial images of multiple users in the scene image, the first recognition is performed through facial recognition. If it is identified that at least one user among the multiple users is a registered user, the first device can determine that there is a registered user in the current scene. At this time, the first device can obtain the account information of the at least one user, such as the account name, account avatar, etc., and can also obtain the historical playback record information of the at least one user. On the contrary, if it is identified that the multiple users are all unregistered users. The first device can determine that there is no registered user in the current scene. At this time, the first device may not execute the display method of the playback record provided in this application.

[0304] S2303, the first device determines whether the current login account is the account of the user operating the second device. If so, execute S2305, if not, execute S2304 first, and then execute S2305.

[0305] Since the user generally controls the first device by operating the second device, in the scene where a single user is watching the first device, the single user is usually the user operating the second device. Correspondingly, the facial image of the single user contained in the above scene image is usually the facial image of the user operating the second device in the current scene. In other words, the first device can determine whether the user operating the second device in the current scene is a registered user. If so, the first device can obtain the account information of the user operating the second device, such as the account name, account avatar, account unique identifier, etc., and can also obtain the historical playback record information of the user operating the second device.

[0306] In a scenario where a single user is viewing the first device, if the first device recognizes that the user operating the second device in the current scenario is a registered user, the first device may execute S2303 to determine whether the current login account is the account of the user operating the second device by obtaining the account information of the user operating the second device and the account information of the current login account. As a method, whether the current login account is the account of the user operating the second device may be determined by comparing whether at least one of the account name, account avatar, account-associated facial image, and account unique identifier is consistent.

[0307] Optionally, when the first device triggers scene image acquisition when it is turned on, or when the first device triggers scene image acquisition when it displays the startup interface, or when the first device triggers scene image acquisition when it displays the interface of historical playback records corresponding to the first control in the startup interface, the current login account may refer to the account currently logged in to the first device, and the account of the first device may be bound to the platform accounts of multiple applications to enjoy the interoperability of member benefits. In this case, the first device can obtain the historical playback records that match the login account in the bound multiple applications through the account logged in by the user. Optionally, in order to protect user privacy, the user is required to authorize before obtaining the historical playback records in the bound multiple applications.

[0308] Optionally, when the first device triggers scene image acquisition when opening the first application, or when the first device triggers scene image acquisition when displaying the home page interface of the first application, or when the first device triggers scene image acquisition when displaying the interface of the historical playback record corresponding to the first control in the first application, the current login account may refer to the platform account currently logged in to the first application. The platform account of the first application may not be bound to the account of the first device, or may be bound to the account of the first device.

[0309] Generally, in a scene where multiple users are watching a first device, in addition to the user who is operating the second device, other users who are watching together are also included. For ease of understanding, the user who is operating the second device among the multiple users can be defined as the first user, and the other users who are watching together but not operating the second device are defined as the second user. Correspondingly, the facial images of the multiple users included in the above scene image include the facial image of the first user and the facial image of the second user in the current scene.

[0310] That is to say, the first device can determine whether the first user in the current scene is a registered user, and can also determine whether the second user in the current scene is a registered user. If the first user is a registered user, the first device can obtain the first user's account information, such as account name, account avatar, etc., and can also obtain the first user's historical playback record information. Similarly, if the second user is a registered user, the first device can obtain the second user's account information, such as account name, account avatar, account unique identifier, etc., and can also obtain the second user's historical playback record information.

[0311] In a scenario where multiple users watch the first device, if the first device recognizes that the first user in the current scene is a registered user, the first device can execute S2303 to determine whether the current login account is the account of the first user by obtaining the account information of the first user and the account information of the current login account.

[0312] In some embodiments, in a scene where multiple users are watching the first device, if the first device recognizes that the first user in the current scene is an unregistered user, but the second user in the current scene is a registered user, the first device may also determine whether the current login account is the second user's account. If the current login account is the second user's account, the first device may execute S2305 to continue to determine whether there are multiple registered users in the current scene. If the current login account is not the second user's account, the first device may first execute S2304 to prompt the user whether to switch to the second user's account. Then the first device executes S2305 again to continue to determine whether there are multiple registered users in the current scene.

[0313] In one scenario, after the first device obtains the scene image captured by the camera, it can identify the user who is operating the second device in the current scene by performing human posture recognition on the scene image, and combine with face recognition technology to identify the identity information of the user operating the second device to determine whether the user operating the second device is a registered user.

[0314] There are many methods for human posture recognition, such as PoseNet, AlphaPose and other posture estimation methods based on deep learning, which are not limited in the embodiments of the present application. As a method, the open source human posture recognition algorithm library OpenPose can be used. The algorithm library has the function of recognizing human posture and hand gestures, which can meet the recognition of the posture of a person holding a second device (such as a remote control) in the embodiments of the present application. In this way, based on the judgment of the posture of the user holding the second device, the identity information of the user operating the second device in the current scene can be identified, and then the historical playback record information of the user in each application can be obtained through the identity information for display.

[0315] In another scenario, the first device can also determine the position information of the user who is operating the second device in the current scene through ultrasonic positioning technology. Then, combined with the scene image captured by the camera, the identity information of the user corresponding to the position information can be identified through face recognition technology. It can be understood that the user identification of the second device based on ultrasonic technology has the characteristics of fast speed, short time consumption, and low hardware performance requirements. The embodiment of the present application does not limit the method of how to identify the user operating the second device.

[0316] S2304: The first device displays a prompt message to prompt the user to switch accounts.

[0317] When the user operating the second device (ie, the first user) is a registered user, after the first device identifies that the current login account is not the account of the user operating the second device, the first device may display a prompt message to prompt the user whether to switch accounts.

[0318] The prompt information may include account information of a candidate account to be switched to login, and the candidate account is the account of the user in the current scenario. That is, at different times, when the user in front of the screen of the first device is different, the candidate account in the prompt information is also different. Thus, the user can directly switch to login to an account that meets the needs of the current scenario through the prompt information.

[0319] As a method, the candidate account includes the account of the user operating the second device in the current scene. In this way, when the user operating the second device is watching the first device, he can choose whether to quickly switch to log in to his own account through the prompt information. It can be understood that in the scene where a single user is watching the first device, the candidate account may only include the account of the user operating the second device, such as Fig.15 As shown in (e) in .

[0320] As another way, in a scenario where multiple users are viewing the first device, the candidate accounts include both the account of the user operating the second device in the current scenario and the accounts of other registered users identified in the current scenario, such as Fig.19 In this way, when the user operating the second device is watching the first device, he can quickly choose whether to switch to log in to his own account or to switch to log in to the account of another user in the current scene by operating the second device in the prompt information.

[0321] Optionally, there are many ways to display the prompt information, which are not limited in this application. Fig.19 The pop-up window display method shown in (c) in FIG. Fig.19 The list display method shown in (d) in the figure.

[0322] Optionally, the account of the user operating the second device in the current scenario can be highlighted in the prompt information. There are many ways to highlight, which are not limited in this application. Fig.19 As shown in (c) of FIG. 1 , the account name “User A” of the user 300 currently operating the remote control and the account avatar 138 corresponding to “User A” are highlighted. Fig.19 As shown in (d) in FIG. 1 , the floating bar 141 of the account avatar of the user 300 currently operating the remote control is longer than the floating bars of other account avatars.

[0323] In some embodiments, in a scene where multiple users are watching the first device, if the first device recognizes that the first user in the current scene is an unregistered user, but the second user in the current scene is a registered user, the first device may also determine whether the current login account is the account of the second user. If the current login account is not the account of the second user, the first device displays a prompt message to prompt the account to switch. The prompt message may include the account information of the candidate account to be switched. As a method, the candidate account includes the account of the second user in the current scene. In this way, when the user operating the second device is watching the first device, although he has not registered an account, he can still quickly choose whether to switch to log in to the account of other registered users in the current scene in the prompt message by operating the second device.

[0324] Optionally, after the user operating the second device in the current scene chooses to switch to his own account, the first device can respond to the selection operation, automatically log out of the current login account, and automatically log in to the account of the user operating the second device in the current scene. At this time, the first device can display the account information of the user operating the second device after the switch login.

[0325] In one scenario, when the current login account refers to the account currently logged in to the first device, the first device can display the account information of the user who operates the second device after switching login on the boot interface of the first device. In another scenario, when the current login account refers to the account currently logged in to the first application, the first device can display the account information of the user who operates the second device after switching login in the application interface of the first application.

[0326] Optionally, after the user operating the second device in the current scene chooses to switch to the account of another registered user in the current scene, the first device may also respond to the selection operation, automatically log out of the current login account, and automatically log in to the account of the other registered user. At this time, the first device may display the account information of the other registered user after the switch login.

[0327] Optionally, the user operating the second device in the current scenario may also choose not to make any account switches, and the current login account remains unchanged.

[0328] S2305, the first device determines whether there are multiple registered users in the current scene. If yes, execute S2306, if not, execute S2307.

[0329] In the embodiment of the present application, when the first device needs to display the historical playback records of the currently logged-in account, the first device can choose whether to display the historical playback records of a single registered user or the integrated historical playback records of multiple registered users according to the number of registered users in the current scene. Thus, the first device can display the historical playback records adapted to the needs of the user in the current scene.

[0330] In some embodiments, when the first device displays the second interface, it may trigger the first device to determine whether there are multiple registered users in the current scene, so that the first device may choose whether to display the historical playback record of a single registered user or the integrated historical playback record of multiple registered users in the second interface according to the number of registered users in the current scene. The second interface may be an interface for displaying historical playback records.

[0331] Optionally, when the first interface is a startup interface of the first device, when the first device detects a trigger operation for a first control in the startup interface, in response to the trigger operation, the first device may display a second interface. Fig.15 As shown in (d), the first control is the control of the video option at the bottom of the main interface. When the user selects the control of the video option by operating the second device, the first device can display the second interface in the upper area of ​​the main interface. The second interface contains the historical playback records of each video application under the current login account.

[0332] Optionally, when the first interface is the home page interface of the first application, when the first device detects a trigger operation for a first control in the home page interface of the first application, in response to the trigger operation, the first device may display the second interface of the first application. Fig.18 As shown in (d) in FIG. 1 , the first control may be a history control 107 in the application interface of the video application 1. When the user selects the history control 107 by operating the second device, the first device may display the second interface of the first application, that is, Fig.18 The historical play record page 115 of the first application shown in (e).

[0333] In the case where the user operating the second device (i.e., the first user) is a registered user, after the first device recognizes that the current login account is the account of the first user, the first device can determine whether there are multiple registered users in the current scene. That is, in addition to the first user being a registered user, whether there are other registered users. If there are multiple registered users in the current scene, the first device can obtain the historical playback records of each registered user to display the historical playback records of each registered user in the current scene. If the first user is the only registered user in the current scene, the first device can obtain the historical playback records of the first user to display the single historical playback record of the first user.

[0334] In the scenario where a single user watches the first device, even if the single user (usually also the user operating the second device) is a registered user, there will not be multiple registered users in the current scenario. Therefore, in the scenario where a single user watches the first device, if the current login account is the account of the single user, the first device can only display the historical playback records of the single user, that is, execute S2307, and the first device can only display the historical playback records of the current login account. Optionally, if the current login account is not the account of the single user, and the single user does not choose to switch to his own account through the prompt information of S2304, the first device can only display the historical playback records of the current login account, or it can display the historical playback records of the account of the single user in the current scenario while displaying the historical playback records of the current login account. Among them, the historical playback records of the current login account and the historical playback records of the account of the single user in the current scenario can be displayed in different areas, such as one displayed on the far left and the other displayed on the far right. For example, one is displayed on the far left and the other is displayed in the middle.

[0335] In a scenario where multiple users are watching the first device, after the first device recognizes that the first user is a registered user and the current login account is the account of the first user, if the first user is the only registered user in the current scenario, the first device may only display the single historical playback record of the first user, that is, execute S2307, and the first device may only display the historical playback record of the current login account. If in addition to the first user being a registered user in the current scenario, other users watching together (i.e., the second user) are also registered users, that is, there are multiple registered users, the first device may display the historical playback records of each registered user in the current scenario.

[0336] As a method, the single historical play record of the first user can be displayed, that is, S2307 is executed, and the integrated historical play records of multiple registered users in the current scene can also be displayed, that is, S2306 is executed. Among them, the single historical play record and the integrated historical play records of multiple registered users can be displayed in different areas, such as one is displayed on the far left and the other is displayed on the far right. For another example, one is displayed on the far left and the other is displayed in the middle.

[0337] Optionally, after the first device identifies that the first user is a registered user, if the current login account is not the account of the first user, and the first user does not choose to switch to his own account through the prompt information of S2304, the first device can display the historical playback records of the registered users (such as the first user) in the current scene while displaying the historical playback records of the current login account. If the current scene is a registered user in addition to the first user, the second user is also a registered user, that is, there are multiple registered users, the first device can display the historical playback records of multiple registered users (such as the first user and the second user) in the current scene while displaying the historical playback records of the current login account, that is, execute S2306 to display the integrated historical playback records of multiple registered users.

[0338] Optionally, after the first device identifies that the first user is an unregistered user but the second user is a registered user, if the current login account is not the second user's account and the user has not chosen to switch to the second user's account, the first device may display the historical playback records of the registered user (such as the second user) in the current scene while displaying the historical playback records of the current login account. If there are other second users in the current scene who are registered users, that is, there are multiple registered users, the first device may also display the historical playback records of multiple registered users (such as multiple second users) in the current scene in a fused manner while displaying the historical playback records of the current login account, that is, execute S2306 to display the fused historical playback records of multiple registered users.

[0339] Optionally, after the first device recognizes that the first user is an unregistered user but the second user is a registered user, if the current login account is the account of the second user, and if there is only a single second user who is a registered user in the current scene, the first device may only display the single historical playback record of the second user, that is, execute S2307, and the first device may only display the historical playback record of the current login account. If there are other second users who are registered users in the current scene, that is, there are multiple registered users, the first device may execute S2306 while executing S2307. That is, while displaying the historical playback record of the current login account, the historical playback records of multiple registered users in the current scene are also displayed, such as executing S2306 to display the integrated historical playback records of multiple registered users.

[0340] S2306: The first device displays integrated historical playback records of multiple registered users.

[0341] It is understandable that there are multiple display formats for each historical playback record, which is not limited in the embodiments of the present application.

[0342] For example, each historical playback record is displayed in the form of a progress bar, such as Fig.21 The progress bar 150 of the historical playback record shown in (a) in FIG.

[0343] For another example, each historical playback record is displayed in the form of a playback information list, such as Fig. 20 The play information list in the historical play record 146 shown in (b) includes play information such as play time, play progress, and play video information.

[0344] As a way to integrate the display of historical playback records, the historical playback records of multiple registered users in the current scene can be displayed in pages according to different accounts. Fig. 20 The historical playback record 146 shown in (b) of FIG. Fig.21 In the progress bar 150 of the historical playback record shown in (a), the user can view the historical playback record under the selected account avatar by clicking the account avatar.

[0345] As another way, the display mode of integrating the historical playback records can also be to display the historical playback records of multiple registered users separately, without having to display them together in the historical playback record 146. For example, the first device can display multiple columns of historical playback records, and the multiple columns of historical playback records respectively display the historical playback records of multiple registered users. Through the multiple columns of historical playback records, the user can view the historical playback records of multiple users at the same time.

[0346] As another way, the display mode of integrating the historical playback records can also be to integrate the information of multiple registered users watching the same video and display it in the same progress bar. Fig.21 The first device may assign a theme color to each registered user account for display, so as to distinguish and display the respective avatar frames, playback progress and other information with the theme color. For example, the theme color of the account "User A" of the registered user 300 is represented by black, the theme color of the account "User B" of the registered user 400 is represented by white, and the theme color of the account "User C" of the registered user 500 is represented by stripes.

[0347] like Fig.21 As shown in (b), in the fusion history playback record 151, the playback progress of the same video "Video 7" watched by users 300, 400, and 500 is fused and displayed in the same progress bar, forming a fusion progress bar of "Video 7" adapted to the users in the current scene. The playback progress of different users in the same progress bar is displayed with corresponding theme colors.

[0348] Optionally, the user can quickly play the multimedia content to be played by directly selecting the play progress in the integrated progress bar, and the multimedia content starts playing based on the selected play progress.

[0349] Optionally, the fusion progress bar of each video can display the user account information that has played the video in the current scene. Fig.21 As shown in (b), the fusion progress bar of "Video 4" displays the account information of user 400 and user 500 who have played "Video 4" in the current scene, that is, the account name "User B" and the corresponding account avatar, and the account name "User C" and the corresponding account avatar.

[0350] Optionally, the user 300 can quickly play the multimedia content to be played by directly selecting the user avatar, and when playing the multimedia content, the playback starts based on the playback progress corresponding to the selected user avatar.

[0351] Optionally, other information of the multimedia content, such as ratings, viewing times, comments, etc., may also be displayed on one side of the fusion progress bar, so that the user can understand the details of the multimedia content played historically.

[0352] As a method, the arrangement of the fusion progress bar can be arranged from most to least according to the number of users who have played the multimedia content in the current scene. For example, in the current scene, there are 3 registered users who have played "Video 7", 2 registered users who have played "Video 3", and 2 registered users who have played "Video 4". Since the number of users who have played "Video 7" in the current scene is the largest, Fig.21 As shown in (b), in the fusion history playback record 151, the fusion progress bar of "Video 7" is displayed at a more forward position.

[0353] If there are different videos that have been played by the same number of users in the current scene, such as "Video 3" and "Video 4" have both been played by two registered users in the current scene, then as a way, the arrangement of the fusion progress bars of the different videos can be based on the aforementioned formula F(V x ) to arrange them. Thus, among the different multimedia contents, the multimedia contents with the smallest difference in user playing progress and with higher user ratings can be relatively arranged in a higher position.

[0354] S2307: The first device displays the historical playback records of the currently logged-in account.

[0355] It can be understood that when the first device needs to display the historical playback record of multimedia content, if there is an account currently logged in, the historical playback record of the multimedia content of the currently logged in account is obtained for display. If there is no account currently logged in, the first device can prompt the user to log in to the account, or through S2301 and S2302, when it is recognized that there is a registered user in the current scene, the account information that can be logged in is recommended to the user to log in to the account of the registered user in the current scene. If the user confirms to log in to the recommended account, the first device can display the historical playback record of the currently logged in account.

[0356] In one scenario, when the current login account refers to the account currently logged in to the first device, the first device may execute S2305 to S2307 when it is necessary to display the historical playback records of the multimedia content matching the current login account of the first device. The historical playback records of the multimedia content may come from multiple applications bound to the account of the first device.

[0357] As a method, when the first device detects that the user clicks the first control in the startup interface, it considers that it is necessary to display the historical playback records of the multimedia content matching the current login account of the first device. Fig.15 In the case of a main interface including input source options, video options, music options, etc. as shown in (d), the first control may be a control for the video option in the main interface. When the user selects the control for the video option by operating the second device, the first device needs to display the historical playback records of each video application under the current login account in the main interface. For another example, the first control is a control for the music option in the main interface. When the user selects the control for the music option by operating the second device, the first device needs to display the historical playback records of each music application under the current login account in the main interface.

[0358] As another way, when the multiple applications bound to the account of the first device include the first application, the first application can synchronously log in the account of the first device as the platform account. When the first device detects that the user performs a click operation on the first control in the first application, it may consider that it is necessary to display the historical playback records of the multimedia content in the first application that matches the current login account of the first device. For example, the first application may be Figure 4 In the case of the video application 1 shown in (a), the first control may be as follows Figure 4 The history record control 107 in the application interface of the video application 1 shown in (b) of FIG. 1 . When the user selects the history record control 107 by operating the second device, the first device needs to display the history play record page of the video application 1.

[0359] In one scenario, when the multiple applications bound to the account of the first device do not include the first application, the currently logged-in account may also refer to the platform account currently logged in to the first application, and the first device may execute S2305 to S2307 when it is necessary to display the historical playback records of the multimedia content that matches the currently logged-in platform account of the first application. As a method, the first device may consider that it is necessary to display the historical playback records of the multimedia content that matches the currently logged-in platform account in the first application when detecting that the user performs a click operation on the first control in the first application. Since the first device has currently entered the first application, the historical playback records of the multimedia content only come from the first application, and there is no need to display the historical playback records of other applications.

[0360] In some embodiments, the user can choose to turn on or off the historical play record sharing function in his account settings. For users who choose to turn off the sharing function, their historical play records will not be displayed in the fusion historical play records. Optionally, in the scenario of quick account switching login, the user's account information may not be displayed in the prompt information displayed in S2304.

[0361] An embodiment of the present application provides a method for displaying playback records. When a user can control a first device through a second device, the first device can automatically determine whether the currently logged-in account is the account of the user currently operating the second device. When the first device determines that the currently logged-in account is not the account of the user currently operating the second device, it can quickly display the account of the user currently operating the second device and prompt the user whether to switch accounts, so that the user currently operating the second device can easily complete the account switch without the user having to manually log out of the account and then manually log in to his or her account. Subsequently, the first device can also display the historical playback records of each application together when displaying the historical playback records of the currently logged-in account, without the user having to search in the corresponding application by themselves. In addition, when there are multiple users watching in the current scene, the first device can also display the historical playback records of multiple users together.

[0362] It is understandable that, in order to implement the above functions, the first device includes hardware and / or software modules corresponding to the execution of each function. In combination with the steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and software. Whether a function is executed in the form of hardware or software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of the present application. In this embodiment, the functional modules of the first device can be divided according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated in one processing module. The above integrated module can be implemented in the form of hardware. It should be noted that the division of modules in this embodiment is schematic, which is only a logical function division, and there may be other division methods in actual implementation.

[0363] The embodiment of the present application also provides a display device for playing records, which can be applied to the above-mentioned first device. The device is used to execute each function or step executed by the first device in the above-mentioned method embodiment.

[0364] The embodiment of the present application also provides a chip system, which includes at least one processor and at least one interface circuit. The processor and the interface circuit can be interconnected through a line. The interface circuit can read the instruction stored in the memory and send the instruction to the processor. When the instruction is executed by the processor, the first device can perform the various functions or steps performed by the first device in the above method embodiment. Of course, the chip system can also include other discrete devices, which are not specifically limited in the embodiment of the present application.

[0365] The embodiment of the present application further provides a first device, the first device including a second device. The first device is used to execute each function or step executed by the first device in the above method embodiment.

[0366] An embodiment of the present application also provides a readable storage medium, which includes instructions. When the instructions are executed on the above-mentioned first device, the first device executes each function or step executed by the first device in the above-mentioned method embodiment.

[0367] The embodiment of the present application also provides a program product. When the program product is run on a first device, the first device is enabled to perform each function or step performed by the first device in the above method embodiment.

[0368] Among them, the equipment, devices, readable storage media, program products or chips provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0369] In the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can be represented by: a, b, c, a and b, a and c, b and c, a and b and c, wherein a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the technical scheme of the embodiment of the present application, in the embodiment of the present application, the words "first", "second" and the like are used to distinguish the same items or similar items with basically the same functions and effects. It can be understood by those skilled in the art that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not limit necessarily different. In the embodiment of the present application, the words "exemplarily" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design scheme described as "exemplarily" or "for example" in the embodiment of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a specific way for easy understanding. Some optional features in the embodiments of the present application may be implemented independently in some scenarios without relying on other features to solve corresponding technical problems and achieve corresponding effects. They may also be combined with other features in some scenarios as needed. In the present application, unless otherwise specified, the same or similar parts between the various embodiments may refer to each other. In the various embodiments of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships. The implementation methods of the present application do not constitute a limitation on the scope of protection of the present application.

[0370] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for displaying a playback record, characterized in that: Applied to a first device, the method includes: Displaying a first interface, where the first interface includes a first control, and the first control is used to trigger the first device to display the historical playback record of the logged-in first account; In response to a trigger operation on the first control, displaying a second interface according to the number of viewing users in front of the screen of the first device; The step of displaying the second interface according to the number of viewing users in front of the screen of the first device includes: When there is only one user watching the video on the screen of the first device, displaying the historical playback records of the first account in the second interface; When the number of users watching in front of the screen of the first device is n, the historical playback records of the accounts of m users are displayed in the second interface, where n is an integer greater than 1, and m is an integer not greater than n, and the accounts of the m users include the first account.

2. The method according to claim 1, characterized in that The first device is controlled by the second device, the first account is an account of a first user, and the first user is a user who is located in front of the screen of the first device and operates the second device.

3. The method according to claim 1, characterized in that The first device is controlled by the second device, the first account is not an account of the first user, the first user is a user who is in front of the screen of the first device and operates the second device, and the method further includes: Displaying prompt information, wherein the prompt information is used to prompt whether to switch to the account of the first user; In response to a confirmation operation on the account of the first user in the prompt information, the first account is logged out, and a switch is made to log in to the account of the first user.

4. The method according to claim 3, characterized in that When the number of users watching in front of the screen of the first device is n, the prompt information includes the account information of the m users, wherein the account of the first user is highlighted in the account information.

5. The method according to claim 1 or 2, characterized in that: The historical playback records of the accounts of m users are displayed in the second interface, including: Displaying the merged historical playback record in the second interface, where the merged historical playback record is the playback record obtained by merging the historical playback records of the accounts of the m users; or The second interface displays the historical playback records of the first account and the integrated historical playback records, where the integrated historical playback records are playback records obtained by integrating the historical playback records of the accounts of the m users.

6. The method according to claim 5, characterized in that The display fusion historical playback record includes: The playback progress of the same file played by the accounts of the m users is displayed in the same playback progress bar, wherein the display styles of the playback progress of the accounts of different users in the playback progress bar are different.

7. The method according to claim 6, characterized in that The method further comprises: In response to a confirmation operation on a first playback progress in the playback progress bar, the file is played at the first playback progress, wherein the first playback progress is the playback progress of an account of any one of the m users.

8. The method according to claim 6 or 7, characterized in that: The method further comprises: On the play progress bar, displaying account information corresponding to the play progress bar, the account information being account information of a user among the m users who has played the file; In response to a confirmation operation on a third account in the account information, the file is played at a playback progress of the third account.

9. The method according to any one of claims 6 to 8, characterized in that: When a first playback progress bar corresponding to the first file and a second playback progress bar corresponding to the second file are displayed in the second interface, the method further includes: When the number of users playing the first file is greater than the number of users playing the second file, the first playing progress bar is arranged and displayed before the second playing progress bar, wherein the playing user is a user among the m users.

10. The method according to claim 9, characterized in that When the number of users playing the first file is the same as the number of users playing the second file, the method further includes: When the difference between the respective playback progress of the first file is smaller than the difference between the respective playback progress of the second file, the first playback progress bar is arranged and displayed before the second playback progress bar; and / or When the score value of the first file is greater than the score value of the second file, the first play progress bar is arranged and displayed before the second play progress bar.

11. The method according to any one of claims 1 to 10, characterized in that: The historical playback records are historical playback records in multiple applications, and the method further includes: The corresponding application icon is displayed on each historical playback record.

12. The method according to any one of claims 1 to 11, characterized in that: Before displaying the historical playback records of the accounts of m users in the second interface, the method further includes: Acquire an image in front of a screen of the first device; According to the image, identifying the identities of n users who are viewing the image on the screen of the first device, wherein the identities include registered account users or unregistered account users; The historical playback records of the accounts of m users are obtained, where the m users are all registered users located in front of the screen of the first device.

13. The method according to claim 12, characterized in that The first device is controlled by a second device, the n users include a user operating the second device, and the method further includes: Performing human gesture recognition on the image to identify a user operating the second device in front of the screen of the first device; or Based on the position of the user operating the second device determined by ultrasonic positioning and the image, a user operating the second device in front of the screen of the first device is identified.

14. A method for displaying a playback record, characterized in that: Applied to a first device, the method includes: Displaying a first interface, where the first interface includes a first control, and the first control is used to trigger the first device to display the historical playback record of the logged-in first account; When n users are watching in front of the screen of the first device, in response to a trigger operation on the first control, a second interface is displayed, wherein the second interface includes a fused historical playback record, wherein the fused historical playback record is a playback record obtained by merging the historical playback records of the accounts of m users, where n is an integer greater than 1, and m is an integer not greater than n, and the accounts of the m users include the first account.

15. The method according to claim 14, characterized in that The display of the second interface, wherein the second interface includes a fusion history playback record, includes: In the second interface, the play progress of the same file played by the accounts of the m users is displayed in the same play progress bar, wherein the display styles of the play progress of different user accounts in the play progress bar are different.

16. The method according to claim 15, characterized in that The method further comprises: In response to a confirmation operation on a first playback progress in the playback progress bar, the file is played at the first playback progress, wherein the first playback progress is the playback progress of an account of any one of the m users.

17. The method according to claim 15 or 16, characterized in that The method further comprises: On the play progress bar, displaying account information corresponding to the play progress bar, the account information being account information of a user among the m users who has played the file; In response to a confirmation operation on the first account in the account information, the file is played at a playback progress of the first account.

18. The method according to any one of claims 15 to 17, characterized in that: When a first playback progress bar corresponding to the first file and a second playback progress bar corresponding to the second file are displayed in the second interface, the method further includes: When the number of users playing the first file is greater than the number of users playing the second file, the first playing progress bar is arranged and displayed before the second playing progress bar, wherein the playing user is a user among the m users.

19. A device, characterized in that The device comprises a memory and one or more processors; the memory is used to store a program, and when the processor executes the program, the device executes the method according to any one of claims 1 to 18.

20. A readable storage medium, characterized in that: The device comprises a program, which, when executed on a device, causes the device to execute the method according to any one of claims 1 to 18.

Images