Terminal and viewing record processing method

Abstract

The application relates to a terminal and a viewing record processing method. The terminal comprises a display and a controller. The controller is configured to: in the case where the login state of a desktop application is changed from an anonymous state to a real-name state, copying the incremental viewing record under an anonymous account stored in a local database, modifying the user identifier in the incremental viewing record from the anonymous account identifier to a first account identifier, and modifying the index value of the joint index field in the incremental viewing record to obtain a first record, wherein the first account identifier is the identifier of a first account currently used for logging in the desktop application, and writing the first record into the local database, so as to realize that the media information corresponding to the incremental viewing record exists in the viewing records under the anonymous account and the first account at the same time. The above method can ensure the convenience of user viewing media.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a terminal and a method for processing viewing records. Background Technology

[0002] With the development of devices (such as smart TVs), in order to ensure the convenience of users watching media resources, corresponding viewing records are generated in the local database when users browse media resources provided by related applications integrated into the device. Since the viewing records of a user when not logged in are not shared with the viewing records of a user when logged in, in order to ensure the integrity of the user's viewing records, the viewing records of a user when not logged in will be imported into the user's account.

[0003] However, when this method is used to import a user's viewing history when they are not logged in into their account, the viewing history will disappear. When the user returns to a logged-out state, they will not be able to view the original viewing history, which will reduce the convenience of watching media assets. Summary of the Invention

[0004] This application provides a terminal and a method for processing viewing records, which can retain the viewing records of users who are not logged in after importing them into the user's account, thereby ensuring the convenience of users watching media assets.

[0005] In a first aspect, some embodiments provide a terminal, including:

[0006] Displays and controllers;

[0007] The controller is configured as follows:

[0008] If the login status of the desktop application is detected to change from anonymous to real-name, the incremental viewing records of the anonymous account stored in the local database are copied.

[0009] The user identifier in the incremental viewing record is changed from the anonymous account identifier to the first account identifier, and the index value of the composite index field in the incremental viewing record is modified to obtain the first record; where the first account identifier is the identifier of the first account used by the currently logged-in desktop application;

[0010] Write the first record to the local database so that the media asset information corresponding to the incremental viewing record exists simultaneously in the viewing records of the anonymous account and the first account.

[0011] The above technical solution copies the incremental viewing records under the anonymous account and modifies the index value of the composite index field in the copied viewing record to obtain the first record. This first record is then distinguished from the original incremental viewing records in the local database. This allows the local database to store both the incremental viewing records under the anonymous state and the first record under the user account. This ensures that the media asset information corresponding to the incremental viewing records exists in both the viewing records under the anonymous account and the user account, thereby guaranteeing the convenience of users watching media assets.

[0012] In some optional embodiments, the viewing records stored in the local database include user identifiers and synchronization identifiers; when the controller performs the copying of incremental records generated by desktop applications under anonymous accounts stored in the local database, it is configured to: filter incremental viewing records from the historical viewing records stored in the local database according to the anonymous account identifier and the first synchronization identifier value representing the record to be synchronized, and copy the incremental viewing records.

[0013] In this embodiment, a synchronization identifier is introduced. By using an anonymous account identifier and a first synchronization identifier value that represents the record to be synchronized, not only can incremental viewing records be quickly filtered from historical viewing records, but the reliability of the filtered incremental viewing records can also be guaranteed.

[0014] In some optional embodiments, when the controller modifies the index value of the composite index field in the incremental viewing record, it is configured to: concatenate the index value of the specified index field in the incremental viewing record with the first account identifier to obtain a new index value for the specified index field; wherein, the specified index field is any one or more index fields in the composite index field.

[0015] In this embodiment, by concatenating the index value of a specified index field in the incremental viewing record with the first account identifier, it is not only possible to distinguish it from the original index value in the incremental viewing record, but also to provide a simple way to modify the index value in the incremental viewing record. Furthermore, this embodiment can also use the first account identifier to concatenate the index values ​​of one or more index fields in the composite index field, not just the index value of the unique index field, which also provides flexibility for modifying the index value.

[0016] In some optional embodiments, when the controller executes the action of copying incremental viewing records generated by the desktop application under the anonymous account stored in the local database when it detects that the login status of the desktop application has changed from anonymous to real-name, it is configured to: obtain the current version information of the desktop application when it detects that the login status of the desktop application has changed from anonymous to real-name; and copy the incremental viewing records under the anonymous account stored in the local database when the current version information indicates that the desktop application is an upgraded version application.

[0017] The controller is also configured to: when the current version information indicates that the desktop application is the application before the version upgrade, change the user identifier in the incremental viewing records in the local database from the anonymous account identifier to the first account identifier, so that the media asset information corresponding to the incremental viewing records only exists under the first account.

[0018] In this embodiment, the current version information of the desktop application is introduced, providing a method for processing incremental viewing records under different application versions. This ensures the rationality of incremental viewing record processing and meets the viewing records of users with different versions under anonymous accounts.

[0019] In some alternative embodiments, when the controller executes the action of writing the first record to the local database, it is configured to: query the local database based on the modified index value; if the second record is not found, write the first record to the local database; wherein the index value of the second record is the same as the index value before modification; if the second record is found, overwrite the second record in the local database with the first record.

[0020] In this embodiment, by querying the local database for a second record corresponding to the same media asset as the first record based on the modified index value before writing the first record, and performing the corresponding operation based on the query result, the rationality of writing the first record can be guaranteed.

[0021] In some alternative embodiments, after the controller executes the writing of the first record to the local database, it is further configured to modify the synchronization identifier in the incremental viewing record to a second synchronization identifier value that indicates that synchronization has been achieved.

[0022] In this embodiment, after the first record is written to the local database, by modifying the synchronization identifier in the incremental viewing record to a second synchronization identifier value that indicates that it has been synchronized, the repeated synchronization of the viewing record can be avoided, thus avoiding the waste of resources.

[0023] In some optional embodiments, the controller is further configured to: receive a record search request for a first account; wherein the record search request includes media asset keywords; determine a first index value corresponding to a composite index field based on the media asset keywords; query from a local database based on a second index value obtained by concatenating the first account identifier and the first index value, and the first index value; remove the first account identifier from the index value of a third record; wherein the third record is a record in the query results that contains the second index value; the query results also include a fourth record that does not contain the second index value; and control the display to output the fourth record and the removed third record.

[0024] In this embodiment, by querying media asset viewing records from the local database based on the first index value corresponding to the media asset keywords and the second index value obtained by concatenating the first account identifier and the first index value, the comprehensiveness of the media asset viewing record query can be guaranteed.

[0025] Secondly, some embodiments also provide a viewing recording processing method applied to a terminal, including:

[0026] If the login status of the desktop application is detected to change from anonymous to real-name, the incremental viewing records of the anonymous account stored in the local database are copied.

[0027] The user identifier in the incremental viewing record is changed from the anonymous account identifier to the first account identifier, and the index value of the composite index field in the incremental viewing record is modified to obtain the first record; wherein, the first account identifier is the identifier of the first account used to log in to the desktop application;

[0028] The first record is written to the local database so that the media asset information corresponding to the incremental viewing record exists simultaneously in the anonymous account and the viewing record under the first account.

[0029] In some optional embodiments, the viewing records stored in the local database include user identifiers and synchronization identifiers; copying incremental records generated by desktop applications under anonymous accounts stored in the local database includes: selecting incremental viewing records from the historical viewing records stored in the local database based on the anonymous account identifier and a first synchronization identifier value representing the record to be synchronized, and copying the incremental viewing records.

[0030] In some optional embodiments, modifying the index value of the composite index field in the incremental viewing record includes: concatenating the index value of the specified index field in the incremental viewing record with the first account identifier to obtain a new index value for the specified index field; wherein, the specified index field is any one or more index fields in the composite index field.

[0031] Thirdly, some embodiments also provide a viewing and recording processing device applied to a terminal, including:

[0032] The copy module is used to copy incremental viewing records stored in the local database for anonymous accounts when the login status of the desktop application is detected to change from anonymous to real-name.

[0033] The modification module is used to modify the user identifier in the incremental viewing record from the anonymous account identifier to the first account identifier, and to modify the index value of the composite index field in the incremental viewing record to obtain the first record; wherein, the first account identifier is the identifier of the first account used to log in to the desktop application;

[0034] The writing module is used to write the first record into the local database so that the media asset information corresponding to the incremental viewing record exists simultaneously in the anonymous account and the viewing records under the first account.

[0035] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a viewing and recording processing device, causes the viewing and recording processing device to perform a viewing and recording processing method according to the second aspect.

[0036] Fifthly, a computer program product is provided, comprising: a computer program that, when run by a viewing and recording processing device, causes the viewing and recording processing device to perform a viewing and recording processing method as described in the second aspect. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in some embodiments or related technologies, the accompanying drawings used in the description of some embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is a schematic diagram illustrating an operational scenario between a display device and a control device provided in some embodiments of this application;

[0039] Figure 2 This is a schematic diagram of the hardware configuration of a display device provided in some embodiments of this application;

[0040] Figure 3 This is a schematic diagram of the hardware configuration of the control device provided in some embodiments of this application;

[0041] Figure 4 This is a schematic diagram of the software configuration of a display device provided in some embodiments of this application;

[0042] Figure 5 A schematic flowchart illustrating a viewing record processing method provided in some embodiments of this application;

[0043] Figure 6 A flowchart illustrating the incremental record copying process provided for some embodiments of this application;

[0044] Figure 7 This is a schematic flowchart illustrating the synchronization identifier processing provided in some embodiments of this application;

[0045] Figure 8 A schematic diagram illustrating the process of modifying index values ​​provided in some embodiments of this application;

[0046] Figure 9 A flowchart illustrating the incremental record copying process provided for other embodiments of this application;

[0047] Figure 10 A flowchart illustrating the write operation provided in some embodiments of this application;

[0048] Figure 11 A schematic diagram illustrating the record search process provided for some embodiments of this application;

[0049] Figure 12 This application provides schematic diagrams illustrating the interactions between various devices during the viewing and recording process, as shown in some embodiments.

[0050] Figure 13 This is a structural block diagram of the viewing recording processing device in some embodiments;

[0051] Figure 14 This is a structural block diagram of the viewing recording processing device in some other embodiments;

[0052] Figure 15 This is a structural block diagram of the viewing recording processing device in some other embodiments. Detailed Implementation

[0053] The embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described below do not represent all embodiments consistent with this application. They are merely examples of systems and methods consistent with some aspects of this application as detailed in the claims.

[0054] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.

[0055] The terms "first," "second," "third," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar or related objects or entities, and do not necessarily imply a specific order or sequence, unless otherwise specified. It should be understood that such terms are interchangeable where appropriate.

[0056] The terms “include” and “have”, and any variations thereof, are intended to cover but not exclusively include, for example, a product or device that includes a range of components is not necessarily limited to all of the components that are clearly listed, but may include other components that are not clearly listed or that are inherent to such product or device.

[0057] The term "module" refers to any known or subsequently developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functions associated with that element.

[0058] In some embodiments, the display device 200 generally refers to a device with screen display and data processing capabilities. For example, the display device 200 includes, but is not limited to, smart TVs, mobile terminals, computers, monitors, advertising screens, wearable devices, virtual reality devices, augmented reality devices, etc.

[0059] Figure 1 This is a schematic diagram illustrating an operational scenario between a display device and a control device provided in some embodiments of this application. For example... Figure 1 As shown, users can operate the display device 200 via touch operation, mobile terminal 300, and control device 100. For example, control device 100 can be a remote control, stylus, gamepad, etc.

[0060] The mobile terminal 300 can serve as a control device for human-computer interaction between the user and the display device 200. The mobile terminal 300 can also serve as a communication device for establishing a communication connection with the display device 200 for data interaction. In some embodiments, the mobile terminal 300 can install software applications with the display device 200 to establish a connection and communication via network communication protocols, achieving one-to-one control operations and data communication. It can also transmit audio and video content displayed on the mobile terminal 300 to the display device 200 to achieve synchronous display.

[0061] like Figure 1 The diagram also shows that the display device 200 communicates with the server 400 via various communication methods. This allows the display device 200 to communicate via a local area network (LAN), a wireless local area network (WLAN), and other networks.

[0062] Display device 200 can provide broadcast television reception function, and can also be equipped with intelligent network television function that provides computer support, including but not limited to network television, smart television, Internet Protocol Television (IPTV), etc.

[0063] Figure 2 Provided for some embodiments of this application Figure 1 Hardware configuration block diagram of display device 200.

[0064] In some embodiments, the display device 200 may include at least one of a tuner 210, a communication device 220, a detector 230, a device interface 240, a controller 250, a display 260, an audio output device 270, a memory, a power supply, and a user input interface.

[0065] In some embodiments, detector 230 is used to acquire signals from the external environment or to interact with the outside world. For example, detector 230 includes a light receiver, a sensor for acquiring ambient light intensity; or, detector 230 includes an image acquisition device, such as a camera, which can be used to acquire external environmental scenes, user attributes, or user interaction gestures; or, detector 230 includes a sound acquisition device, such as a microphone, for receiving external sounds.

[0066] In some embodiments, the display 260 includes display function components for presenting images and driving components for driving image display. The display 260 is used to receive and display image signals output from the controller 250. For example, the display 260 can be used to display video content, image content, menu control interface components, and user control UI interfaces, etc.

[0067] In some embodiments, the communication device 220 is a component used to communicate with external devices or the server 400 according to various communication protocol types. The display device 200 may have multiple communication devices 220 depending on the supported communication methods. For example, when the display device 200 supports wireless network communication, it may have a communication device 220 that includes the international wireless Fidelity (WiFi) standard. When the display device 200 supports Bluetooth connectivity, it needs to have a communication device 220 that includes Bluetooth functionality.

[0068] The communication device 220 enables the display device 200 to communicate with external devices or the server 400 via wireless or wired connections. Wired connections utilize data cables, interfaces, or other components to connect the display device 200 to external devices. Wireless connections utilize wireless signals or wireless networks. The display device 200 can directly establish a connection with external devices or indirectly through gateways, routers, or other connection devices.

[0069] In some embodiments, the controller 250 may include at least one of a central processing unit, a video processor, an audio processor, a graphics processor, and a power processor, and a first to an nth interface for input / output. The controller 250 controls the operation of the display device and responds to user operations through various software control programs stored in memory. The controller 250 controls the overall operation of the display device 200.

[0070] In some embodiments, the controller 250 and the tuner 210 may be located in different separate devices, that is, the tuner 210 may also be located in an external device of the main device where the controller 250 is located, such as an external set-top box.

[0071] In some embodiments, a user can input user commands through a graphical user interface (GUI) displayed on a display 260, and the user input interface receives user input commands through the graphical user interface (GUI).

[0072] In some embodiments, the audio output device 270 can be a built-in speaker of the display device 200 or an external audio output device connected to the display device 200. For the external audio output device connected to the display device 200, the display device 200 may also be provided with an external audio output terminal, through which the audio output device can be connected to the display device 200 to output sound from the display device 200.

[0073] In some embodiments, the user input interface 280 can be used to receive instructions from user input.

[0074] Figure 3 Provided for some embodiments of this application Figure 1 Hardware configuration block diagram of the central control device. (Example) Figure 3 As shown, the control device 100 may include: a controller 110, a communication interface 130, a user input / output interface, a memory, and a power supply.

[0075] The control device 100 is configured to control the display device 200, and to receive user input operation commands and convert the operation commands into commands that the display device 200 can recognize and respond to, thus acting as an intermediary for interaction between the user and the display device 200.

[0076] In some embodiments, the control device 100 may be an intelligent device. For example, the control device 100 may be equipped with various applications for controlling the display device 200 according to user needs.

[0077] In some embodiments, such as Figure 1As shown, the mobile terminal 300 or other smart electronic devices can perform similar functions to the control device 100 after installing the application of the control display device 200.

[0078] The controller 110 includes a processor 112, RAM 113, ROM 114, a communication interface 130, and a communication bus. The controller 110 is used to control the operation of the control device 100, as well as the communication and cooperation between internal components and the external and internal data processing functions.

[0079] Under the control of the controller 110, the communication interface 130 enables communication of control signals and data signals with the display device 200. The communication interface 130 may include at least one of other near-field communication modules such as WiFi chip 131, Bluetooth module 132, and NFC module 133.

[0080] User input / output interface 140, wherein the input interface includes at least one of other input interfaces such as microphone 141, touchpad 142, sensor 143, and button 144.

[0081] In some embodiments, the control device 100 includes at least one of a communication interface 130 and an input / output interface 140. The control device 100 is configured with the communication interface 130, such as a WiFi, Bluetooth, or NFC module, which can encode user input commands via WiFi, Bluetooth, or NFC protocols and send them to the display device 200.

[0082] The memory 190 is used to store various operating programs, data, and applications for driving and controlling the control device 100 under the control of the controller. The memory 190 can also store various control signal instructions input by the user.

[0083] The power supply 180 is used to provide operating power support for the various components of the control device 100 under the control of the controller.

[0084] In some embodiments, to enable user interaction, the display device 200 may run an operating system. The operating system is a computer program used to manage and control the hardware and software resources of the display device 200. The operating system can (control the display device) provide a user interface, allowing users to interact with the display device 200 and supporting the running of various applications.

[0085] It should be noted that the operating system can be a native operating system based on a specific operating platform, a third-party operating system that is deeply customized based on a specific operating platform, or an independent operating system specifically developed for display devices.

[0086] An operating system can be divided into different modules or levels based on the functions it implements, for example... Figure 4 As shown, in some embodiments, the system is divided into four layers, from top to bottom: the Applications layer (referred to as the "Application Layer"), the Application Framework layer (referred to as the "Framework Layer"), the System Library layer, and the Kernel layer.

[0087] In some embodiments, the application layer provides services and interfaces for applications, enabling the display device 200 to run applications and interact with the user based on the applications. The application layer may contain at least one application, which may be a built-in Windows program, system settings program, or clock program of the operating system; or it may be an application developed by a third-party developer. In specific implementations, the application packages in the application layer are not limited to the examples above.

[0088] The framework layer provides application programming interfaces (APIs) and a programming framework for applications. The application framework layer includes predefined functions. It acts as a central processing unit, determining the actions taken by applications within the application layer. Through the API, applications can access system resources and obtain system services during execution.

[0089] like Figure 4 As shown, in some embodiments, the application framework layer includes a view system, managers, and content providers. The view system designs and implements the application's interface and interactions, and includes lists, grids, text boxes, buttons, etc. The managers include at least one of the following modules: an activity manager for interacting with all running activities in the system; a location manager for providing system services or applications with access to system location services; a package manager for retrieving various information related to application packages currently installed on the device; a notification manager for controlling the display and clearing of notification messages; and a window manager for managing icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0090] In some embodiments, the Activity Manager manages the lifecycle of individual applications and common navigation and back functions, such as controlling application exit, opening, and back actions. The Window Manager manages all window programs, such as obtaining the screen size, determining if a status bar is present, locking the screen, capturing the screen, and controlling changes to the display window, such as shrinking the display window, shaking the display, or distorting the display.

[0091] In some embodiments, the system runtime library layer can provide support for the framework layer. When the framework layer is used, the operating system runs the instruction library contained in the system runtime library layer, such as the C / C++ instruction library, to implement the functions to be performed by the framework layer.

[0092] In some embodiments, the kernel layer is a functional layer situated between the hardware and software of the display device 200. The kernel layer can implement functions such as hardware abstraction, multitasking, and memory management. For example, ... Figure 4 As shown, hardware drivers can be configured in the kernel layer. The drivers included in the kernel layer can be at least one of the following: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor driver (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver, etc.

[0093] It should be noted that the above examples are merely a simple division of operating system functions and do not limit the specific form of the operating system of the display device 200 in some embodiments. Depending on the function of the display device, the type of operating system, and other factors, the number of layers and the specific type of the operating system may take other forms.

[0094] With the development of devices (such as smart TVs), in order to ensure the convenience of users watching media resources, corresponding viewing records are generated in the local database when users browse media resources provided by related applications integrated into the device. Since the viewing records of a user when not logged in are not shared with the viewing records of a user when logged in, in order to ensure the integrity of the user's viewing records, the viewing records of a user when not logged in will be imported into the user's account.

[0095] However, when this method is used to import a user's viewing history when they are not logged in into their account, the viewing history will disappear. When the user returns to a logged-out state, they will not be able to view the original viewing history, which will reduce the convenience of watching media assets.

[0096] Based on this, in some embodiments, a viewing recording processing method is provided. In one optional embodiment, the viewing recording processing method is applied to a controller in a terminal as an example. The terminal includes a display and a controller; the communication connection between the display and the controller can be a wired communication connection or a wireless communication connection. Figure 5 As shown, the specific steps include:

[0097] S 510, upon detecting that the login status of the desktop application has changed from anonymous to real-name, the incremental viewing records under the anonymous account stored in the local database are copied.

[0098] In this context, a desktop application can be an application that starts by default when the terminal is launched and can be used to support the playback of media data on the terminal. For example, when the terminal is a display device, the desktop application is a pre-installed application that can serve as a signal source for the display device. Login status refers to whether the user is logged into the desktop application, and can include anonymous status and real-name status.

[0099] Anonymous status means not logged in, that is, the user is not logged into the desktop application using a pre-registered account; correspondingly, the so-called anonymous account is the account information configured for the user in anonymous status, usually the default characters. Real-name status means logged in, that is, the user is logged into the desktop application using a pre-registered account.

[0100] The local database refers to data located on the terminal itself, which can be used to store user operation records on the terminal. Furthermore, in this embodiment, the local database can be used to store relevant operation data generated by the user using the desktop application on the terminal, such as media viewing records. Incremental viewing records refer to viewing records generated by the user using the desktop application in an anonymous state, without synchronization. Synchronization here includes synchronizing records generated under anonymous accounts to records under real-name accounts.

[0101] In one alternative implementation, a detection control can be used to monitor the login status of the desktop application. Then, when the login status of the desktop application is detected to change from anonymous to real-name, incremental viewing records can be obtained based on the changes in viewing records generated by the user using the desktop application in the anonymous state in the local database, and the incremental viewing records can be copied.

[0102] For example, after retrieving candidate viewing records generated by using the desktop application in anonymous mode from the local database, candidate viewing records without synchronization processing markers can be used as incremental viewing records. Alternatively, based on the target time when the desktop application last changed from real-name to anonymous mode, candidate viewing records generated after the target time can be selected as incremental viewing records.

[0103] S520 modifies the user identifier in the incremental viewing record from the anonymous account identifier to the first account identifier, and modifies the index value of the composite index field in the incremental viewing record to obtain the first record.

[0104] The user identifier is the identifier field representing user information in the viewing history, such as the "customer ld" field. The anonymous account identifier is the preset account identifier in the anonymous state, which is the field value of the "customer ld" field in the anonymous state, for example, "0". The first account identifier is the identifier of the first account used to log in to the desktop application, which is the field value of the "customer ld" field in the current real-name state. Furthermore, the first account is the user's login account in the desktop application.

[0105] A composite index field is an index field that is unique when queried in the local database (i.e., the index value of the composite index field is different for each viewing record in the local database). It can contain only one field or consist of multiple fields. For example, in the media asset playback records of a user in a desktop application stored in the local database, the composite index field can consist of a media asset field and a viewing device field, or it can consist of only the media asset field. Optionally, the composite index field can be configured when building the local database based on the functions of the desktop application (such as media asset playback function) and the index fields of other existing databases on the terminal.

[0106] The so-called first record refers to the record after the incremental viewing record has been modified. That is, the user identifier in the first record is the first account identifier, and the index value of the composite index field is the modified index value.

[0107] In one alternative implementation, in order to import incremental viewing records from anonymous accounts to real-name accounts, the user identifier in the incremental viewing records can be modified, that is, the user identifier can be changed from the original anonymous account identifier to the first account identifier corresponding to the user's login account.

[0108] Understandably, since the index values ​​of the composite index fields in the local database cannot be the same across different viewing records, but in this case, it's necessary for the index values ​​of the composite index fields in the incremental viewing records written to the verified account to be consistent with those in the original incremental viewing records written to the anonymous account. Therefore, to avoid conflicts in the composite index fields in the local database, the index values ​​of the composite index fields in the incremental viewing records written to the verified account can be modified to distinguish them from the incremental viewing records written to the verified account. In other words, the index values ​​of the composite index fields in the incremental viewing records need to be modified.

[0109] For example, the index value can be modified by changing the original index value of the composite index field, such as by performing hash processing. Alternatively, the original index value of the composite index field can be concatenated with a preset field.

[0110] S530 writes the first record to the local database to ensure that the media asset information corresponding to the incremental viewing record exists simultaneously in the viewing records of the anonymous account and the first account.

[0111] The so-called media asset information refers to the media asset viewing information corresponding to the incremental viewing record, which may include, but is not limited to, the specific media asset being viewed, the viewing progress of the media asset, and the viewing time of the media asset.

[0112] Optionally, since the index value of the composite index field in the first record is different from that in the incremental viewing record under the anonymous state, the first record can be written to the local database. At this time, the media asset information corresponding to the incremental viewing record can exist in both the anonymous account and the viewing record under the first account.

[0113] For example, after a user watches media asset B under an anonymous account, an incremental viewing record B1 corresponding to media asset B is generated in the local database. After the user logs in with account C, the incremental viewing record B1 can be copied, and the index value of the composite index field in the copied viewing record can be modified. After changing the user identifier in B1 to account C, the first record B2 corresponding to media asset B can be obtained. At this time, the first record B2 is written to the local database. The local database will simultaneously contain the incremental viewing record B1 generated by the user watching media asset B anonymously, and the first record B2 corresponding to the incremental viewing record B1 under account C. That is, both the anonymous account and account C contain media asset information of media asset B.

[0114] By employing the above technical solution, upon detecting a change in login status from anonymous to real-name in the desktop application, the incremental viewing records stored in the local database under the anonymous account are copied. The user identifier in the incremental viewing record is modified from the anonymous account identifier to the first account identifier of the first account currently logged into the desktop application. The index value of the composite index field in the incremental viewing record is also modified to obtain a first record. This first record is then written to the local database, ensuring that the media asset information corresponding to the incremental viewing records exists simultaneously in both the anonymous account and the first account's viewing records. Compared to related technologies that directly import viewing records from a user's offline state into the user account, this method, by copying the incremental viewing records under the anonymous account and modifying the index value of the composite index field in the copied viewing record to obtain the first record, distinguishes the first record from the original incremental viewing records in the local database. This allows the local database to simultaneously store incremental viewing records under the anonymous state and the first record under the user account, ensuring the media asset information corresponding to the incremental viewing records exists simultaneously in both the anonymous account and the user account's viewing records, thus guaranteeing the convenience of users watching media assets.

[0115] Based on the above embodiments, in some embodiments, the viewing records stored in the local database include user identifiers and synchronization identifiers. The user identifier is an identifier field in the viewing record that represents user information; for example, it could be the "customer ld" field in the viewing record. The synchronization identifier is an identifier field that indicates whether the viewing record has undergone synchronization processing; for example, it could be the "ls_syns" field in the viewing record. Based on this, the incremental record copying process is refined, such as... Figure 6 As shown, the specific steps include:

[0116] S610, based on the anonymous account identifier and the first synchronization identifier value representing the data to be synchronized, filters out incremental viewing records from the historical viewing records stored in the local database and copies the incremental viewing records.

[0117] The so-called first synchronization identifier value is the identifier information that indicates that the viewing record is in a state of waiting to be synchronized. For example, it can be the character "0". The so-called historical viewing record is the viewing record generated within a historical period stored in the local database.

[0118] In one alternative implementation, when the login status of the desktop application is detected to change from anonymous to real-name, the anonymous account identifier and the first synchronization identifier value representing the one to be synchronized can be used as indexes to query the historical viewing records in the local database, thereby obtaining the historical viewing records to be synchronized in the anonymous state, i.e., the incremental viewing records.

[0119] For example, the synchronization flag value corresponding to the "ls_syns" field in the historical viewing records can be used to indicate whether the historical viewing records have been synchronized. If ls_syns = 0, it is determined that the historical viewing records have not been synchronized. Based on this, "customer_ld = 0" and "ls_syns = 0" can be used as indexes to query the local database and obtain the incremental viewing records. Here, customer_ld = 0 is used to represent the anonymous account identifier.

[0120] In another alternative implementation, viewing records under anonymous accounts can be first filtered from the historical viewing records stored in the local database based on the anonymous account identifier; then, the first synchronization identifier value is used as an index to query the filtered viewing records, so that the synchronization identifier in the filtered viewing records represents the records to be synchronized, and these are used as incremental viewing records.

[0121] Furthermore, a preset copying method can be used to copy incremental viewing records.

[0122] In this embodiment, a synchronization identifier is introduced. By using an anonymous account identifier and a first synchronization identifier value representing the one to be synchronized, not only can incremental viewing records be quickly filtered from historical viewing records, but the reliability of the filtered incremental viewing records can also be guaranteed.

[0123] Furthermore, based on the above embodiments, in some embodiments, after writing the first record to the local database, an optional method for synchronizing the identifier processing is provided, such as... Figure 7 As shown, the specific steps include:

[0124] S710 modifies the synchronization identifier in the incremental viewing record to a second synchronization identifier value that indicates that synchronization has been achieved.

[0125] The second synchronization identifier value is the identifier information that indicates that the viewing record has been synchronized. For example, it can be the character "1".

[0126] Understandably, in order to avoid repeated synchronization of historical viewing records in anonymous mode, after writing the first record to the local database, a synchronization completion instruction for the incremental viewing record corresponding to the first record can be generated; then, after detecting the synchronization completion instruction for the incremental viewing record, the synchronization identifier in the incremental viewing record can be modified from the first synchronization identifier value to the second synchronization identifier value.

[0127] For example, for an incremental viewing record D containing "customer_ld=0" and "ls_syns=0", after the incremental viewing record D has been synchronized, it can be modified into a historical viewing record D′ containing "ls_syns=1".

[0128] In this embodiment, after the first record is written to the local database, by modifying the synchronization identifier in the incremental viewing record to a second synchronization identifier value that indicates that it has been synchronized, the repeated synchronization of the viewing record can be avoided, thus avoiding the waste of resources.

[0129] Based on the above embodiments, in some embodiments, the process of modifying the index value of the composite index field is refined, such as... Figure 8 As shown, the specific steps include:

[0130] S810: Concatenate the index value of the specified index field in the incremental viewing record with the first account identifier to obtain a new index value for the specified index field.

[0131] The specified index field can be any one or more index fields from a composite index. For example, the specified index field can be an index field from a composite index that is distinct from index fields in other databases already existing on the terminal. For instance, the specified index field could be the media asset identifier field "program_Id".

[0132] In one optional implementation, the index value of a specified index field in the incremental viewing record can be concatenated with the first account identifier based on a preset concatenation order to obtain a new index value for the specified index field. For example, after a user logs in with account X, for an incremental viewing record E containing "customer_ld=0" and "program_ld=1569085", customer_ld can be modified to "customer_ld=X", and program_ld can be modified to "program_ld=1569085+customer_ld_X", thereby obtaining the first record E′.

[0133] In this embodiment, by concatenating the index value of a specified index field in the incremental viewing record with the first account identifier, it is not only possible to distinguish it from the original index value in the incremental viewing record, but also to provide a simple way to modify the index value in the incremental viewing record. Furthermore, this embodiment can also use the first account identifier to concatenate the index values ​​of one or more index fields in the composite index field, not just the index value of the unique index field, which also provides flexibility for modifying the index value.

[0134] Based on the above embodiments, in some embodiments, the process of copying incremental viewing records is refined, such as... Figure 9 As shown, the specific steps include:

[0135] S910, upon detecting that the login status of the desktop application has changed from anonymous to real-name, obtains the current version information of the desktop application.

[0136] The so-called current version information refers to the version information of the desktop application at the current moment.

[0137] It is understandable that different versions of the desktop application support different data processing functions. In this embodiment, only the upgraded version of the desktop application supports the above-mentioned processing operations for incremental viewing records. Based on this, in order to ensure the reliability of viewing record processing, when the login status of the desktop application is detected to change from anonymous to real-name, the attribute information of the desktop application can be obtained from the local database of the terminal, and the current version information of the desktop application can be obtained from the attribute information.

[0138] S920: Determine whether the current version information indicates that the desktop application is an upgraded version. If yes, execute S930; otherwise, execute S940.

[0139] Optionally, the consistency comparison between the current version information and the standard version information representing the version upgrade can be performed. If the comparison result is consistent, the current version information represents the desktop application as the upgraded application, and step S930 is executed. If the comparison result is inconsistent, the current version information represents the desktop application as the application before the version upgrade, and step S940 is executed.

[0140] For example, if the version of a desktop application is identified as "5.1" after the version upgrade, desktop applications identified as "5.1" and other versions higher than "5.1" (e.g., "5.2") can be regarded as upgraded desktop applications, while desktop applications with other versions lower than "5.1" (e.g., "5.0") can be regarded as pre-upgrade desktop applications.

[0141] S930 copies incremental viewing records from anonymous accounts stored in the local database.

[0142] Optionally, when the desktop application is an upgraded version, the desktop application supports the function of processing incremental viewing records in steps S510-S530 above. Therefore, it is necessary to copy the incremental viewing records under the anonymous account stored in the local database.

[0143] That is, the user identifier in the incremental viewing record can be changed from the anonymous account identifier to the first account identifier, and the index value of the composite index field in the incremental viewing record can be modified to obtain the first record. The first record is then written to the local database so that the media asset information corresponding to the incremental viewing record can exist in both the viewing records under the anonymous account and the first account.

[0144] S940 modifies the user identifier in the incremental viewing records in the local database from the anonymous account identifier to the first account identifier, so that the media asset information corresponding to the incremental viewing records only exists under the first account.

[0145] Optionally, if the desktop application is the version prior to the upgrade, the desktop application does not support the incremental viewing record processing function in steps S510-S530 above. It only supports directly importing incremental viewing records into the real-name account. In this case, incremental viewing records can be filtered from the historical viewing records stored in the local database based on the anonymous account identifier and the first synchronization identifier value representing the record to be synchronized. Then, the user identifier in the incremental viewing record is changed from the anonymous account identifier to the first account identifier. In this case, the media asset information corresponding to the incremental viewing record only exists under the first account.

[0146] In this embodiment, the current version information of the desktop application is introduced, providing a method for processing incremental viewing records under different application versions. This ensures the rationality of incremental viewing record processing and meets the viewing records of users with different versions under anonymous accounts.

[0147] Based on the above embodiments, in some embodiments, the write operation of the first record is refined, such as... Figure 10 As shown, the specific steps include:

[0148] S1010, based on the modified index value, performs a query from the local database.

[0149] In this embodiment, to ensure the standardization of media asset viewing records in a user's account, each media asset can only correspond to one latest media asset viewing record. For example, if a user watches media asset F on both August 28th and August 29th while logged in, then the user's account will only contain the media asset viewing record F′ corresponding to the viewing of media asset F on August 29th.

[0150] Optionally, before writing the first record to the database, it is necessary to query the local database to see if there are any media viewing records under the first account that match the media asset corresponding to the first record. In this case, the query can be performed in the local database based on the modified index value. For example, the modified index value in the composite index field can be directly used to perform the query in the local database. Furthermore, to ensure the comprehensiveness of the query, both the original and modified index values ​​of the composite index field can be used simultaneously to perform the query in the local database.

[0151] S1020: Determine if a second record is found. If not, execute S1030; if yes, execute S1040.

[0152] The so-called second record refers to the viewing record under the first account that contains the same media asset as the first record; the index value of the second record is the same as the index value before the modification.

[0153] In an optional embodiment, when the index value of the second record is the same as the index value before modification, the retrieved second record is the media viewing record generated when the user is watching media assets under real-name status.

[0154] In another alternative embodiment, the index value of the second record can also be the same as the modified index value. In this case, the second record retrieved is a media asset viewing record imported from the viewing record in anonymous mode.

[0155] S1030, write the first record to the local database.

[0156] Optionally, if no second record is found, it proves that there is no second record generated when the first account viewed the first record containing media assets. In this case, the first record can be directly written into the local database.

[0157] S1040, the first record is used to overwrite the second record in the local database.

[0158] Optionally, if a second record is found, it proves that a second record already exists under the first account when the first record contains media assets. In this case, the first record may be used to overwrite the second record in the local database, thereby avoiding the existence of two viewing records for the same media asset in the first account.

[0159] In this embodiment, by querying the local database for a second record corresponding to the same media asset as the first record based on the modified index value before writing the first record, and performing the corresponding operation based on the query result, the rationality of writing the first record can be guaranteed.

[0160] Based on the above embodiments, in some of these embodiments, an optional method for record searching is provided, such as... Figure 11 As shown, the specific steps include:

[0161] S1110 receives a record search request for the first account.

[0162] In this context, a record search request refers to a request initiated when querying media asset viewing records. Furthermore, the record search request includes media asset keywords. In this embodiment, the record search request may contain only one media asset keyword, or it may contain multiple media asset keywords simultaneously. Media asset keywords are the keywords corresponding to the media asset, and can be the media asset name, the abbreviation of the media asset, or other media asset-related terms.

[0163] Optionally, after logging into the desktop application with the first account, the user can control the pointer on the remote control to select / enter the keywords to search for in the record search interface displayed on the screen and click the search control. This will generate a record search request containing media asset keywords. Correspondingly, the terminal can also receive record search requests for the first account.

[0164] S1120, Determine the first index value corresponding to the composite index field based on the media asset keywords.

[0165] The so-called first index value is the index value of the composite index field determined based on the media asset keywords, which is used to query media asset viewing records under real-name status.

[0166] Optionally, a search can be performed using media asset keywords to obtain the media asset identifier corresponding to the keywords, and then use the media asset identifier as the index value for the media asset field in the composite index. Afterwards, based on the field types of the other index fields in the composite index, the index values ​​for the other index fields are obtained. For example, if another index field is a playback terminal type, the terminal identifier is used as the index value for that index field.

[0167] Furthermore, by concatenating the index value corresponding to the media asset field with the index values ​​corresponding to other index fields, the first index value corresponding to the composite index field can be obtained.

[0168] S1130, Query from the local database based on the second index value obtained by concatenating the first account identifier and the first index value, and the first index value.

[0169] The so-called second index value is the index value obtained by concatenating the first account identifier and the first index value, which is used to query the media viewing records of the imported real-name status.

[0170] Optionally, to ensure comprehensive record retrieval, the first account identifier and the first index value can be concatenated to obtain the second index value. Then, the first account identifier and the first index value can be used as the first query condition, and the first account identifier and the second index value as the second query condition. Both the first and second query conditions can be used simultaneously to query the local database and obtain the query results. Alternatively, the first account identifier can be used to retrieve the user's historical viewing records under the first account from the local database. Then, both the first and second index values ​​can be used simultaneously to query the historical viewing records under the first account and obtain the query results.

[0171] S1140, Remove the first account identifier from the index value in the third record.

[0172] The third record is the record in the query results that contains the second index value; furthermore, the query results also include the fourth record that does not contain the second index value.

[0173] Optionally, in order to obtain specific information about media assets, such as media asset images, from the system later, de-identification processing is required to meet the system's query requirements. Furthermore, when the query results include a third record with a second index value, the first account identifier in the index value of the third record can be removed to restore the third record to its standard media asset viewing record format.

[0174] S1150 controls the display to output the fourth record and the third record after removal processing.

[0175] Optionally, after processing the third record, the display can show a result feedback interface containing the fourth record and the processed third record. Each record can be displayed as a preview image using a corresponding media asset poster.

[0176] Furthermore, since media viewing records also include viewing times, another optional method for searching records is for users, after logging into the desktop application with their primary account, to control the cursor on the remote control to trigger a shortcut control created based on the historical viewing order within the record search interface displayed on the screen. This allows the screen to display the media viewing records under the primary account, generated in reverse chronological order based on the primary account identifier and the viewing time. For example, the shortcut control's search logic could be to search for the 10 most recently viewed media viewing records, or to search for the 20 most recently viewed media viewing records.

[0177] In this embodiment, by querying media asset viewing records from the local database based on the first index value corresponding to the media asset keywords and the second index value obtained by concatenating the first account identifier and the first index value, the comprehensiveness of the media asset viewing record query can be guaranteed.

[0178] Based on the technical solutions of the above embodiments, taking a terminal as a display device as an example, the following description is provided. The display device includes a desktop application and a controller. Further, an optional embodiment is provided. See also... Figure 12 The diagram shown illustrates the interactions between devices during the viewing and recording process, including:

[0179] S1201, the desktop application performs a login operation based on the login information, including the first account, entered by the user.

[0180] S1202, when the controller detects that the login status of the desktop application has changed from anonymous to real-name, it obtains the current version information of the desktop application.

[0181] S1203, when the current version information indicates that the desktop application is an upgraded version application, the controller selects incremental viewing records from the historical viewing records stored in the local database based on the anonymous account identifier and the first synchronization identifier value indicating that it is to be synchronized, and then copies the incremental viewing records.

[0182] In some embodiments, the first synchronization identifier value is added to the viewing record when a new viewing record is generated in anonymous state.

[0183] S1204, the controller modifies the user identifier in the incremental viewing record from the anonymous account identifier to the first account identifier of the first account used by the currently logged-in desktop application, and concatenates the index value of the specified index field in the composite index field of the incremental viewing record with the first account identifier to obtain a new index value of the specified index field, so as to obtain the first record.

[0184] S1205, the controller writes the first record to the local database so that the media asset information corresponding to the incremental viewing record exists simultaneously in the viewing records under the anonymous account and the first account.

[0185] S1206, the controller modifies the synchronization flag in the incremental viewing record to a second synchronization flag value that indicates that synchronization has been achieved.

[0186] S1207, the remote control device sends a record search request to the controller for the first account, which includes media asset keywords.

[0187] S1208, the controller determines the first index value corresponding to the composite index field based on the media asset keywords, and performs a query from the local database based on the second index value obtained by concatenating the first account identifier and the first index value, as well as the first index value.

[0188] S1209, the controller removes the first account identifier from the index value of the third record containing the second index value in the query result, and controls the display to output the fourth record and the third record after removal.

[0189] Furthermore, the specific processes of S1201-S1209 described above can be found in the description of the above method embodiments, and their implementation principles and technical effects are similar, so they will not be repeated here.

[0190] Based on the same inventive concept, some embodiments also provide a viewing recording processing apparatus for implementing the viewing recording processing method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more viewing recording processing apparatus embodiments provided below can be found in the limitations of the viewing recording processing method described above, and will not be repeated here.

[0191] In one exemplary embodiment, such as Figure 13 As shown, a viewing and recording processing device 1 is provided, configured in a display device, including: a copying module 10, an editing module 20, and a writing module 30, wherein:

[0192] The copying module 10 is used to copy the incremental viewing records of the anonymous account stored in the local database when the login status of the desktop application is detected to change from anonymous to real-name.

[0193] Modification module 20 is used to modify the user identifier in the incremental viewing record from the anonymous account identifier to the first account identifier, and to modify the index value of the composite index field in the incremental viewing record to obtain the first record; wherein, the first account identifier is the identifier of the first account used to log in to the desktop application;

[0194] The writing module 30 is used to write the first record into the local database so that the media asset information corresponding to the incremental viewing record exists simultaneously in the anonymous account and the viewing record under the first account.

[0195] In some optional embodiments, the viewing records stored in the local database include user identifiers and synchronization identifiers; the copy module 10 is specifically used for:

[0196] Based on the anonymous account identifier and the first synchronization identifier value representing the data to be synchronized, incremental viewing records are selected from the historical viewing records stored in the local database, and then the incremental viewing records are copied.

[0197] In some alternative embodiments, the modification module 20 is specifically used for:

[0198] The index value of the specified index field in the incremental viewing record is concatenated with the first account identifier to obtain a new index value for the specified index field; wherein, the specified index field can be any one or more index fields in the composite index field.

[0199] In some alternative embodiments, such as Figure 14 As shown, the copy module 10 includes:

[0200] The detection unit 11 is used to obtain the current version information of the desktop application when it detects that the login status of the desktop application has changed from anonymous to real-name.

[0201] The copying unit 12 is used to copy the incremental viewing records of anonymous accounts stored in the local database when the current version information indicates that the desktop application is an upgraded version application.

[0202] Furthermore, the write module 30 is specifically used for:

[0203] If the current version of the information represents the desktop application as it was before the version upgrade, the user identifier in the incremental viewing records in the local database will be changed from the anonymous account identifier to the first account identifier, so that the media asset information corresponding to the incremental viewing records only exists under the first account.

[0204] In some alternative embodiments, such as Figure 15 As shown, the writing module 30 includes:

[0205] Query unit 31 is used to perform a query from the local database based on the modified index value;

[0206] The writing unit 32 is used to write the first record to the local database if the second record is not found; wherein the index value of the second record is the same as the index value before modification.

[0207] The overlay unit 33 is used to overwrite the second record in the local database with the first record when the second record is found.

[0208] In some optional embodiments, after the controller executes the writing of the first record to the local database, the viewing record processing device 1 further includes an identifier modification module, wherein the identifier modification module is specifically used for:

[0209] Modify the synchronization identifier in the incremental viewing record to a second synchronization identifier value that indicates that synchronization has been achieved.

[0210] In some optional embodiments, the viewing recording processing device 1 further includes a recording query module, wherein the recording query module is specifically used for:

[0211] Receive a record search request for the first account; the record search request contains media asset keywords; determine the first index value corresponding to the composite index field based on the media asset keywords; query from the local database based on the second index value obtained by concatenating the first account identifier and the first index value, and the first index value; remove the first account identifier from the index value of the third record; the third record is the record in the query result that contains the second index value; the query result also includes a fourth record that does not contain the second index value; control the display to output the fourth record and the removed third record.

[0212] Each module in the aforementioned viewing and recording processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the computer as software.

[0213] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0214] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0215] It should be noted that the data involved in this application (including but not limited to media viewing records) is all data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0216] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0217] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0218] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A terminal, characterized in that, include: Displays and controllers; The controller is configured as follows: If the login status of the desktop application is detected to change from anonymous to real-name, the incremental viewing records of the anonymous account stored in the local database are copied. The user identifier in the incremental viewing record is changed from the anonymous account identifier to the first account identifier, and the index value of the composite index field in the incremental viewing record is modified to obtain the first record; wherein, the first account identifier is the identifier of the first account used to log in to the desktop application; Write the first record into the local database to ensure that the media asset information corresponding to the incremental viewing record exists simultaneously in the anonymous account and the viewing record under the first account. When the controller modifies the index value of the composite index field in the incremental viewing record, it is configured as follows: The index value of the specified index field in the incremental viewing record is concatenated with the first account identifier to obtain a new index value for the specified index field; wherein, the specified index field is any one or more index fields in the composite index field.

2. The terminal according to claim 1, characterized in that, The viewing records stored in the local database include user identifiers and synchronization identifiers; when the controller performs the copying of incremental records generated by the desktop application under anonymous accounts stored in the local database, it is configured as follows: Based on the anonymous account identifier and the first synchronization identifier value representing the data to be synchronized, incremental viewing records are selected from the historical viewing records stored in the local database, and the incremental viewing records are copied.

3. The terminal according to any one of claims 1-2, characterized in that, When the controller detects a change in the login status of the desktop application from anonymous to real-name, and copies the incremental viewing records generated by the desktop application under the anonymous account stored in the local database, it is configured as follows: If the login status of the desktop application is detected to change from anonymous to real-name, obtain the current version information of the desktop application; If the current version information indicates that the desktop application is an upgraded version, the incremental viewing records of the anonymous account stored in the local database are copied. The controller is also configured to: If the current version information indicates that the desktop application is an application from before the version upgrade, the user identifier in the incremental viewing record in the local database is changed from the anonymous account identifier to the first account identifier, so that the media asset information corresponding to the incremental viewing record exists only under the first account.

4. The terminal according to any one of claims 1-3, characterized in that, When the controller executes the action of writing the first record to the local database, it is configured as follows: Based on the modified index value, a query is performed from the local database; If the second record is not found, the first record is written to the local database; wherein the index value of the second record is the same as the index value before modification. If the second record is found, the first record is used to overwrite the second record in the local database.

5. The terminal according to claim 2, characterized in that, After the controller executes the action of writing the first record to the local database, it is further configured to: Modify the synchronization identifier in the incremental viewing record to a second synchronization identifier value that indicates that synchronization has been achieved.

6. The terminal according to claim 1, characterized in that, The controller is also configured to: Receive a record search request for the first account; wherein the record search request contains media asset keywords; Based on the media asset keywords, determine the first index value corresponding to the composite index field; A query is performed from the local database based on the second index value obtained by concatenating the first account identifier and the first index value, and the first index value. The first account identifier in the index value of the third record is removed; wherein, the third record is the record in the query result that contains the second index value; the query result also includes a fourth record that does not contain the second index value; Control the display to output the fourth record and the third record after the removal process.

7. A method for processing viewing records, characterized in that, The method includes: If the login status of the desktop application is detected to change from anonymous to real-name, the incremental viewing records of the anonymous account stored in the local database are copied. The user identifier in the incremental viewing record is changed from the anonymous account identifier to the first account identifier, and the index value of the composite index field in the incremental viewing record is modified to obtain the first record; wherein, the first account identifier is the identifier of the first account used to log in to the desktop application; Write the first record into the local database to ensure that the media asset information corresponding to the incremental viewing record exists simultaneously in the anonymous account and the viewing record under the first account. The modification of the index value of the composite index field in the incremental viewing record includes: The index value of the specified index field in the incremental viewing record is concatenated with the first account identifier to obtain a new index value for the specified index field; wherein, the specified index field is any one or more index fields in the composite index field.

8. The method according to claim 7, characterized in that, The viewing records stored in the local database include user identifiers and synchronization identifiers; the copying of incremental records generated by the desktop application under anonymous accounts stored in the local database includes: Based on the anonymous account identifier and the first synchronization identifier value representing the data to be synchronized, incremental viewing records are selected from the historical viewing records stored in the local database, and the incremental viewing records are copied.

Images