Display device, electronic device, and display method of functional money

Abstract

Some embodiments of the present application provide a display device, an electronic device and a display method of functional items. The method obtains a signaling file associated with a target channel and extracts functional items in response to a channel switching instruction. The method identifies private items in the functional items and displays a first target window including a management control. After the user triggers the management control, the method obtains historical selection information according to the category of the private items, determines the execution status of the private items according to the historical selection information, and displays the private items and the corresponding execution status in the management window. The embodiments of the present application can avoid the user from continuously switching channels of multiple unconfirmed private items, reduce the frequency of manual confirmation of the user, simplify the confirmation process of the private items of the user, and improve the confirmation efficiency of the private items.

Description

Technical Field

[0001] This application relates to the field of display device technology, and more particularly to a device, electronic device and a method for displaying functional items. Background Technology

[0002] Display devices are intelligent devices capable of presenting a user interface and supporting user interaction. Taking smart TVs as an example, smart TVs are television products based on Internet application technology, equipped with open operating systems and chips, possessing open application platforms, enabling two-way human-computer interaction, and integrating multiple functions such as audio-visual, entertainment, and data to meet diverse and personalized user needs.

[0003] Display devices integrate digital television applications, providing users with a live television viewing experience. Based on digital television broadcasting standards, digital television broadcasters need to collect users' personal data through display devices to personalize digital television content delivery. Display devices are required to present privacy requests from broadcasters to users in graphic and textual form, allowing users to choose whether to agree or decline.

[0004] Each channel on digital television has its own privacy policy. When a user switches to a new channel, the display device will pop up a window with the terms and conditions for that channel, requiring the user to manually confirm their agreement or rejection. When a user switches to multiple new channels without having confirmed their privacy policy, multiple policy windows will pop up sequentially, requiring the user to manually confirm frequently. This is cumbersome and negatively impacts the user experience. Summary of the Invention

[0005] This application provides a display device, an electronic device, and a method for selecting function options to solve the problem that users need to frequently manually confirm when switching to a new channel.

[0006] In a first aspect, some embodiments of this application provide a display device, including: monitor; The controller is configured as follows: In response to a channel switching command, obtain the signaling file associated with the target channel; wherein, the target channel is the channel corresponding to the channel switching command; Extract at least one functional payment from the signaling file; If at least one privacy payment is included in at least one functional payment, the display is controlled to show a first target window; wherein the first target window includes management controls; the privacy payment is a payment that requires user confirmation for execution, and the management controls are used to trigger the display to show a management window, which is a window related to the execution status of the privacy payment; If a triggering operation for triggering the management control is detected, historical selection information is obtained based on the payment type of at least one privacy payment; wherein, the historical selection information is used to characterize the user's preference for the execution status of at least one privacy payment; Determine the execution status of at least one privacy payment based on historical selection information; Based on the execution status of at least one privacy payment, the control monitor displays a management window; wherein the management window includes a text description of at least one privacy payment and the execution status of at least one privacy payment.

[0007] The above technical solutions have the following beneficial effects or advantages: The embodiments of this application can automatically pre-fill the execution status of privacy payments based on the user's historical preferences, reduce the frequency of manual confirmation, avoid the tedious operation of frequent pop-up confirmation when switching between multiple channels, and intuitively display the content and execution status of privacy payments through the management window, making it easy for users to intuitively view privacy payments and their corresponding execution status, thereby improving the user's viewing and interaction experience.

[0008] In some embodiments of this application, the controller is further configured to: If none of the aforementioned feature items include the privacy item, a second target window is displayed; wherein the second target window includes a confirmation control; If a triggering operation is detected that triggers the confirmation control, exit the second target window.

[0009] The above technical solution has the following beneficial effects or advantages: When the functional payment does not include privacy payment, a second target window with a confirmation control pops up. After the confirmation control is triggered, the second target window exits directly, thereby simplifying the processing flow and window interaction logic of functional payments without privacy confirmation requirements, reducing unnecessary interface windows and operation steps, and improving the smoothness of interface interaction during channel switching.

[0010] In some embodiments of this application, after the controller executes a channel switching command and obtains the signaling file associated with the target channel, it is further configured to: Locate historical versions of the signaling file in local storage; If a historical version of the signaling file is found in local storage, the difference in amount is determined by comparing the current version of the signaling file with the historical version. The difference in amount is the amount that differs between the historical version and the current version of the signaling file. If the difference in charges includes at least one privacy charge, display the first target window; If the difference in payment does not include privacy payments, a second target window will be displayed.

[0011] The above technical solutions have the following beneficial effects or advantages: By comparing the current version with historical versions to determine the difference in payments, the system determines whether to display the first or second target window based on whether the difference in payments includes privacy-related payments. Users do not need to repeatedly verify all functional payments in the signaling file; they only need to select and process the difference in payments due to version differences. This avoids repeatedly loading and verifying already confirmed functional payments and improves payment confirmation efficiency.

[0012] In some embodiments of this application, after the controller performs the search for historical versions of the signaling file in local storage, it is further configured to: If the corresponding historical version of the signaling file is not found in the local storage, then the step of extracting at least one function item from the signaling file is performed.

[0013] The above technical solutions have the following beneficial effects or advantages: When no historical version of the signaling file is found in local storage, the step of retrieving function funds is executed directly. For the first switch to the corresponding target channel, or in scenarios where the privacy funds for the target channel are different from the privacy funds of the historical version, the process of retrieving function funds and determining privacy funds is executed directly, simplifying the processing logic for the first channel switch.

[0014] In some embodiments of this application, the controller determines the execution status of at least one privacy payment based on historical selection information, specifically configured as follows: Extract the number of times a user consented to at least one privacy payment of the same type and the number of times a user refused to comply with at least one privacy payment of the same type from historical selection information; The total number of executions for the same type of payment corresponding to at least one privacy payment is determined based on the number of times the payment was agreed to and the number of times the payment was refused. The confidence level of consent to execute at least one privacy payment is determined based on the ratio of the number of consents to the total number of executions. The execution status of at least one privacy payment is determined based on the confidence level of consent to execute corresponding to at least one privacy payment.

[0015] The above technical solutions have the following beneficial effects or advantages: By extracting the number of times that privacy payments were agreed to or refused to be executed for the same type, calculating the total number of executions and the confidence level of the agreed execution, the execution status of privacy payments can be determined. This ensures that the execution status of privacy payments pre-filled is consistent with the user's long-term selection preferences, avoids the judgment bias caused by a single historical record, and improves the rationality and reliability of the automatic determination of the execution status of privacy payments.

[0016] In some embodiments of this application, after the controller executes based on at least one privacy payment and execution status display management window, it is further configured to: Upon detecting a selection operation for selecting a target privacy item, a function preview mapping table is obtained; wherein, the target privacy item is any privacy item in the management window; the function preview mapping table includes at least one function prompt message corresponding to a privacy item; Based on the feature preview mapping table, determine the feature prompt information corresponding to the target privacy payment; The function preview area is displayed based on the function prompt information corresponding to the target privacy payment; the function preview area does not obscure the content displayed in the management window.

[0017] The above technical solutions have the following beneficial effects or advantages: After displaying the management window, the system retrieves the function preview mapping table for the selected privacy fund, determines the function prompts corresponding to the target privacy fund, and displays unobstructed function preview areas. Users can view the function prompt details corresponding to the target privacy fund in real time without obscuring the content of the management window, without having to exit the management window or jump to an additional interface. This helps users quickly understand the actual functions of each privacy fund and improves the intuitiveness and completeness of information for users to understand privacy funds.

[0018] In some embodiments of this application, after the controller executes based on at least one privacy payment and execution status display management window, it is further configured to: If a change operation is detected that alters the execution status of the target privacy payment, obtain the feature preview mapping table; Based on the feature preview mapping table, determine the feature prompt information corresponding to the target privacy payment; The preview area displays function prompts based on the target privacy payment; In response to a confirmation operation used to confirm the execution status of the target privacy payment, the execution status of the target privacy payment is recorded; Exit the management window.

[0019] The above technical solutions have the following beneficial effects or advantages: When a change in the execution status of a target privacy payment is detected, the function preview mapping table is retrieved simultaneously to display the function preview area. After confirming the change, the corresponding execution status is recorded and the management window is exited. Users can view function prompts in real time through the function preview area when changing the execution status of privacy payments, which helps users adjust the execution status. At the same time, the changed execution status is recorded to complete the closed loop of this privacy payment configuration and improve the accuracy of users' decision-making when changing the execution status of target privacy payments.

[0020] In some embodiments of this application, after the controller records the execution status of the target privacy fund in response to a confirmation operation for confirming the execution status of the target privacy fund, it is further configured to: Adjust the number of consents and total executions, or the number of rejections and total executions, corresponding to the type of the target privacy payment, based on the execution status of the target privacy payment.

[0021] The above technical solutions have the following beneficial effects or advantages: After recording the execution status of the target privacy payment, the number of times the payment was agreed to, refused to be executed, and the total number of executions for the corresponding type of payment are adjusted simultaneously. The user's historical selection information is updated in real time, providing the latest historical selection information for the confidence calculation of the execution status of subsequent privacy payments and the pre-filling of the execution status, thereby improving the accuracy of pre-filling the execution status of privacy payments.

[0022] Secondly, some embodiments of this application provide an electronic device, including: monitor; The controller is configured as follows: In response to a channel switching command transmitted by the display, a signaling file associated with the target channel is obtained; wherein, the target channel is the channel corresponding to the channel switching command; Extract at least one functional payment from the signaling file; If at least one privacy payment is included in at least one functional payment, the display is controlled to show a first target window; wherein the first target window includes management controls; the privacy payment is the payment that requires user confirmation for execution, and the management controls are used to trigger the display to show a management window, which is a window related to the execution status of the privacy payment; Based on the operation events transmitted by the display, historical selection information is obtained according to the type of at least one privacy payment; wherein, the historical selection information is used to characterize the user's preference for the execution status of at least one privacy payment; the operation event is the event corresponding to the triggering operation of the management control; Determine the execution status of at least one privacy payment based on historical selection information; Based on the execution status of at least one privacy payment, the control monitor displays a management window; wherein the management window includes a text description of at least one privacy payment and the execution status of at least one privacy payment.

[0023] Thirdly, some embodiments of this application provide a method for displaying functional items, applied to the device provided in the first aspect, including: In response to a channel switching command, obtain the signaling file associated with the target channel; wherein, the target channel is the channel corresponding to the channel switching command; Extract at least one functional payment from the signaling file; If at least one privacy payment is included in at least one functional payment, the display is controlled to show a first target window; wherein the first target window includes management controls; the privacy payment is the payment that requires user confirmation for execution, and the management controls are used to trigger the display to show a management window, which is a management window related to the execution status of the privacy payment; If a triggering operation for triggering the management control is detected, historical selection information is obtained based on the payment type of at least one privacy payment; wherein, the historical selection information is used to characterize the user's preference for the execution status of at least one privacy payment; Determine the execution status of at least one privacy payment based on historical selection information; Based on the execution status of at least one privacy payment, the control monitor displays a management window; wherein the management window includes a text description of at least one privacy payment and the execution status of at least one privacy payment.

[0024] As can be seen from the above technical solutions, some embodiments of this application provide a display device, an electronic device, and a method for displaying functional funds. This method, after obtaining the signaling file associated with the target channel and extracting the functional funds in response to a channel switching command, identifies privacy funds within the functional funds and controls the display to show a first target window including management controls. After the user triggers the management controls, historical selection information is obtained according to the category of the privacy funds, and the execution status of the privacy funds is determined based on the historical selection information. The privacy funds and their corresponding execution status are then displayed in the management window. Embodiments of this application can avoid users manually confirming multiple channels with unconfirmed privacy funds when switching continuously, reducing the frequency of user confirmation, simplifying the user's confirmation process for privacy funds, and improving the efficiency of privacy fund confirmation. Attached Figure Description

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

[0026] 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; Figure 2 This is a schematic diagram of the hardware configuration of a display device provided in some embodiments of this application; Figure 3 This is a schematic diagram of the software configuration of a display device provided in some embodiments of this application; Figure 4 A flowchart illustrating the selection of a display device's function payment according to some embodiments of this application; Figure 5 Timing diagrams for selecting the function of a display device in some embodiments of this application; Figure 6 An interface diagram showing a first target window on a display device provided in some embodiments of this application; Figure 7 A flowchart illustrating the display of a second target window by a display device according to some embodiments of this application; Figure 8 An interface diagram showing a second target window on a display device provided in some embodiments of this application; Figure 9 A flowchart illustrating the display of differential payments is provided for some embodiments of this application. Figure 10 A flowchart illustrating the process of a display device determining the execution status of privacy payments based on historical selection information, as provided in this application embodiment. Figure 11 Flowcharts showing a preview of the display device performing functions provided in some embodiments of this application; Figure 12 This application provides a preview of the functional area interface of a display device in some embodiments. Figure 13 This is a flowchart illustrating the switching execution state of a display device as provided in some embodiments of this application. Detailed Implementation

[0027] 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.

[0028] 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.

[0029] 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.

[0030] The terms “comprising” and “having”, and any variations thereof, are intended to cover but not exclude inclusion, 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.

[0031] 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.

[0032] In this embodiment, 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.

[0033] 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, a user can operate the display device 200 via touch operation, a mobile terminal 300, and a control device 100. The control device 100 receives user input commands and converts them into control commands that the display device 200 can recognize and respond to. For example, the control device 100 can be a remote control, a stylus, a gamepad, etc.

[0034] The mobile terminal 300 can function as a control device for human-computer interaction between the user and the display device 200. It can also function as a communication device for establishing a communication connection with the display device 200 and exchanging data. In some embodiments, the mobile terminal 300 can have software applications installed on it and communicate with the display device 200 via network communication protocols to achieve one-to-one control and data communication. Furthermore, it can transmit audio and video content displayed on the mobile terminal 300 to the display device 200 for synchronized display.

[0035] In some embodiments, the mobile terminal 300 or other electronic devices may also simulate the functions of the control device 100 by running an application that controls the display device 200.

[0036] 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.

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

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

[0039] 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 280.

[0040] 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.

[0041] 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.

[0042] 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 with WiFi functionality. When the display device 200 supports Bluetooth connectivity, it needs to have a communication device 220 with Bluetooth functionality.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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).

[0047] 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.

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

[0049] To enable user interaction, in some embodiments, 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 to provide a user interface; for example, the operating system can directly control the display device to provide a user interface, or it can provide a user interface by running an application. The operating system also allows users to interact with the display device 200.

[0050] 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.

[0051] An operating system can be divided into different modules or levels based on the functions it implements, for example... Figure 3As 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.

[0052] 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.

[0053] 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.

[0054] like Figure 3 As shown, the application framework layer in this embodiment 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, and buttons. 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.

[0055] 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.

[0056] 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.

[0057] 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 3 As shown, hardware drivers can be configured in the kernel layer. The kernel layer can contain at least one of the following drivers: 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.

[0058] 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 this application embodiment. Depending on the function of the display device, the type of operating system, and other factors, the number of levels and the specific level type of the operating system may be expressed in other forms.

[0059] In some embodiments, the display device 200 may include digital television services. Digital television is a type of broadcast television that, based on digital encoding, digital modulation, and digital transmission technologies, transmits and plays audio and video media assets, service signaling, privacy control signaling, and other information in the form of digital streams. The display device 200 can receive digital signals from broadcast providers by implementing signal reception methods such as satellite signals, terrestrial signals, cable closed-circuit signals, or IP network streaming media signals at its hardware level. The tuner / demodulator 210 can lock onto the digital signals, select channels, amplify, frequency convert, and demodulate them, restoring the high-frequency digital signals to a digital broadcast stream, and parsing the audio and video data streams, signaling files, and other service data from the digital broadcast stream.

[0060] In some embodiments, digital television may include multiple different channels, each corresponding to a different digital broadcast stream, thereby playing different channel content. For example, different channels may transmit television programs, interactive service content, or value-added service information from different television stations. Users can switch between different channels and select the content they want to watch using the control device 100.

[0061] In some embodiments, digital television may comply with digital television broadcasting standards (such as ATSC 3.0, TV 3.0). These standards define a Privacy Record Request Description (PRRD), which indicates that the broadcaster needs to collect personally identifiable information from users through the display device 200 to perform certain functionalities. For example, the broadcaster may collect personally identifiable information such as user viewing behavior data, device identification, geographic information, and usage habits, and use this information to perform personalized content recommendations, advertising, service optimization, and other functionalities.

[0062] In some embodiments, the display device 200 may include a privacy manager, which is a system functional component of the display device 200 and can perform functions such as parsing privacy signaling, user authorization interaction, and storing privacy records.

[0063] Display device 200 can receive privacy requests from broadcast providers based on the current channel through a privacy manager, and receive the privacy signaling file corresponding to that channel, i.e., the signaling file corresponding to the privacy record request description. The privacy signaling file includes multiple functional items. Among these, multiple functional items may include consent-based functional items (hereinafter referred to as privacy items).

[0064] The privacy manager can present the privacy terms obtained from parsing the privacy signaling file to the user via a graphical interface on the display 260, allowing the user to choose to agree or refuse based on the privacy terms. The display device 200 can determine the execution status of the privacy terms based on the user's input, thereby responding to privacy requests from broadcast providers. When the user has chosen to agree to the privacy terms, the display device 200 allows the transmission of personally identifiable information to the broadcast provider; when the user has chosen to refuse the privacy terms, the display device 200 prevents the collection and transmission of personally identifiable information, protecting the user's right to privacy control.

[0065] Each channel on a digital television network has its own privacy policy. When display device 200 switches to a channel with an unconfirmed privacy policy, it will display a terms and conditions window for that channel, requiring the user to confirm the policy. After confirmation, display device 200 will close the terms and conditions window, and no further confirmation will be required when switching to the same channel again.

[0066] However, digital television typically includes dozens or even hundreds of channels. Every time a user switches to a new, unconfirmed channel, they need to confirm the privacy terms. When switching between multiple channels, the terms window will pop up repeatedly, interrupting the user's viewing process and affecting the viewing experience. Furthermore, there are often duplicate privacy terms across different channels. Users need to repeatedly select the same privacy terms, which is cumbersome and affects the user experience.

[0067] Based on the above technical problems, some embodiments of this application provide a display device 200 that can pre-fill the execution status of privacy payments based on the user's historical selection information when the display device 200 continuously switches multiple channels, thereby reducing the user's selection operations for privacy payments on each channel and improving the user experience.

[0068] In some embodiments, the display device 200 includes at least a display 260 and a controller 250, wherein the display 260 is configured to display a user interface.

[0069] Figure 4 A flowchart illustrating the selection of a function payment for a display device according to some embodiments of this application. Figure 5 Timing diagrams for selecting the function items of a display device provided in some embodiments of this application.

[0070] See Figure 4 and Figure 5 The controller 250 is configured to perform the following steps, including: S410: In response to a channel switching command, obtain the signaling file associated with the target channel.

[0071] In some embodiments, the user can input a channel switching command via the button component of the control device 100 (such as a remote control), or via voice command or touch operation. Upon receiving the channel switching command, the controller 250 determines the target channel. The target channel is the channel corresponding to the channel switching command. After the broadcast provider detects that the display device 200 has switched channels, it can send the digital broadcast stream corresponding to the target channel to the display device 200.

[0072] After receiving the digital broadcast stream corresponding to the target channel, the controller 250 demodulates the digital broadcast stream through the tuner 210 and detects and obtains the signaling file associated with the target channel from the Service Layer Signaling (SLS).

[0073] In some embodiments, the signaling file is based on a privacy record request description file defined by next-generation digital television broadcasting standards (such as ATSC 3.0, TV 3.0, etc.) and uses a structured format (such as XML). After obtaining the signaling file, the controller 250 obtains the root node attribute (schemaVersion attribute) of the signaling file. The root node attribute is used to identify the version of the file format specification followed by the privacy record request description file. The controller 250 performs a format validity check on the signaling file according to the root node attribute, and proceeds to the subsequent processing flow after confirming that the file format is valid.

[0074] S420: Extract at least one function payment from the signaling file.

[0075] In some embodiments, the controller 250 can parse the XML structure of the privacy record request description in the signaling file and extract at least one functional item.

[0076] The content extracted for each feature payment may include: a lawfulbasis attribute value, which is used to determine the confirmation type and window type of the feature payment; a type identifier attribute value, which is used to indicate the processing purpose type of the feature terms and the classification key for subsequent determination of historical selection information; and text content describing personal information, which serves as a description of the personally identifiable information to be collected by the feature terms.

[0077] For example, the attribute values ​​for the legality basis can include consent attribute values ​​and non-consent attribute values. The consent attribute value is used to indicate that the functional terms require user confirmation; the non-consent attribute value is used to indicate that the functional terms do not require user confirmation. For example, the attribute of the functional terms is "LegalObligation", which means that the necessary information processing to meet legal compliance requirements does not require user authorization or confirmation. Or, the attribute of the functional terms is "LegitimateInterest", which means that the legitimate interests of the broadcaster require no user authorization or confirmation.

[0078] S430: If at least one privacy policy is included in at least one feature policy, control the display to show the first target window.

[0079] In some embodiments, privacy payments refer to payment items that require user confirmation before execution, i.e., payment items with the lawfulBasis attribute value of consent. After retrieving all payment items in step S200, controller 250 can determine the lawfulBasis attribute value for each payment item to detect whether there is at least one payment item with the lawfulBasis attribute value of consent.

[0080] For payments with the lawfulBasis attribute value of consent, the corresponding window type is the first target window. If at least one privacy payment is detected among the functional payments, the controller 250 invokes the rendering logic of the first target window and controls the display 260 to display the first target window at a preset position on the user interface.

[0081] Figure 6 This is an interface diagram showing a first target window displayed on a display device provided in some embodiments of this application.

[0082] like Figure 6 As shown, the first target window 41 is displayed overlaid on top of the currently playing content. While the first target window 41 is displayed, the controller 250 does not interrupt the current playback content of the target channel. The first target window 41 includes management controls for triggering the display 260 to display a management window, guiding the user to the management window 42. The management window 42 is a window related to the execution status of privacy funds, allowing the user to view privacy funds in the management interface.

[0083] S440: If a triggering operation for triggering the management control is detected, obtain historical selection information based on at least one privacy payment type.

[0084] In some embodiments, the controller 250 detects a user's trigger operation on the management control in the first target window 41. This trigger operation can be triggered by the user clicking a management button via a remote control or other means. In response to the trigger operation, the controller 250 sends an information retrieval request to the storage based on the type of each privacy payment. The storage responds to the information retrieval request by querying historical selection information in its local storage and sending the historical information to the controller 250. The payment type can be determined based on the attribute value of the type identifier extracted by the controller 250 during step S200. Based on different payment functions, the attribute value of the type identifier can include "Marketing" (for marketing), "Analytics" (for analytics), "Personalisation" (for personalized push notifications), etc.

[0085] In some embodiments, the controller 250 can obtain historical selection information based on the type of privacy payment. This historical selection information characterizes the user's preference for the execution status of at least one privacy payment. The historical selection information is an external representation of the privacy preference model of the display device 200. The privacy preference model can be stored in the memory of the display device 200, with the attribute value of the type identifier as the classification key. The privacy preference model can use multiple counters to record the user's selection results for each type of privacy payment, thereby maintaining a set of historical selection information for each type of privacy payment.

[0086] For example, if the privacy payment type of target channel A is "marketing", and the user has made selections for "marketing" privacy payments for channels B-D in the past, the controller 250 can call the privacy preference model in the memory and obtain the user's historical selection information for "marketing" privacy payments for channels B-D within a preset time period from the privacy preference model. This historical selection information includes selection information for privacy terms that have been confirmed and are of the same payment type as the privacy payment, so that the controller 250 can pre-fill the execution status of the privacy payment for target channel A with reference to the historical selection information.

[0087] S450: Determine the execution status of at least one privacy payment based on historical selection information.

[0088] In some embodiments, the controller 250 parses the historical selection information obtained in step S400 to obtain the user's selection information for the payment type within a preset time period. The controller 250 determines the execution status of at least one privacy payment by referring to this selection information. The preset time period can be set according to actual application conditions, such as the past 30 days, the past six months, or the past year. For example, taking a preset time period of 30 days, if the user's selection results for privacy payments related to "personalized push notifications" in the past 30 days are all "agree to execution," then the controller 250, by referring to the historical selection information, sets the execution status of the pre-filled privacy payment for the target channel to "agree to execution." Conversely, if the user's selection results for privacy payments related to "personalized push notifications" in the past 30 days are all "reject execution," then the controller 250, by referring to the historical selection information, sets the execution status of the pre-filled privacy payment for the target channel to "reject execution."

[0089] S460: Controls the display to show the management window based on the execution status of at least one privacy payment.

[0090] The management window 42 is an interactive interface that displays all privacy funds and their execution status in detail. Users can manually adjust the execution status of each privacy fund in the management window 42. The management window 42 only displays privacy funds; other functional funds that do not require user confirmation can be directly displayed in the first target window 41 (not shown in the figure) and do not need to be displayed in the management window 42.

[0091] After determining the execution status of each privacy fund in step S500, controller 250 invokes the rendering logic of management window 42 and displays management window 42 in the user interface via display 260. Management window 42 includes a text description of at least one privacy fund and an execution status control, wherein the execution status control is used to display the execution status of at least one privacy fund.

[0092] In some embodiments, the execution status control can display each privacy payment in a list format, forming a privacy payment list. The controller 250 can combine the privacy payment list with the corresponding execution status and display it in the management window 42. The privacy payment list includes multiple entries, each corresponding to a privacy payment for a target channel. Each entry can include a payment title, text content describing personal information, and an execution status control. The payment title displays the descriptive text corresponding to the privacy payment, such as "Privacy Payment 1," "Privacy Payment 2," "Privacy Payment 3," etc. The text content describing personal information helps users understand what personally identifiable information the broadcaster will specifically collect. The execution status control indicates the execution status of the privacy payment and is presented as a Toggle. It shows the user the pre-filled execution status of each privacy payment, and the user can manually adjust the execution status of the privacy payment. The initial execution status of the Toggle is the execution status determined in step S500. For example, as shown... Figure 6 In the management window 42 shown, the execution status of "Privacy Payment 1" is "Rejected", the execution status of "Privacy Payment 2" is "Rejected", and the execution status of "Privacy Payment 3" is "Agreed to execute".

[0093] In some embodiments, the management window 42 is overlaid on the currently playing content in an overlay form, presenting a complete privacy payment management interface without interrupting channel playback, ensuring that users can still perceive the current channel content while completing the privacy confirmation operation.

[0094] In some embodiments, when the execution status of a privacy payment is a pre-populated execution status based on historical selection information, rather than the standard default value corresponding to that privacy payment, the controller 250 can display a visual identifier, such as "Based on your preferences," in the area where the entry is located to indicate to the user that the execution status comes from historical selection information. Users can view the visual identifier and choose to retain the intelligently pre-populated execution status or manually modify the execution status, ensuring the user's right to know and right to choose. This also allows users to perceive that the display device 200 can remember and apply historical preferences, enhancing the user's trust in and willingness to use the intelligent privacy management function.

[0095] Based on the above technical solutions, the embodiments of this application can automatically pre-fill the execution status of privacy funds based on the user's historical selection information, reduce the frequency of manual confirmation, avoid the tedious operation of frequent pop-up confirmation when switching between multiple channels, and intuitively display the content and execution status of privacy funds through the management window 42, so that users can intuitively view privacy funds and their corresponding execution status, thereby improving the user's viewing and interaction experience.

[0096] Figure 7 A flowchart illustrating the display of a second target window by a display device provided in some embodiments of this application.

[0097] like Figure 7 As shown, in some embodiments, after executing step S420, the controller 250 may also execute the following steps: S710: Display a second target window if all features do not include privacy features.

[0098] In some embodiments, when the lawfulBasis of all functional items in the signaling file is of the non-consent type, it indicates that there are no privacy clauses in the signaling file that require user confirmation. The controller 250 can call the rendering logic of the second target window and control the display 260 to display the second target window at a preset position in the user interface.

[0099] Figure 8 This is an interface diagram showing a second target window displayed on a display device provided in some embodiments of this application.

[0100] See Figure 8 The second target window 81 includes a confirmation control and text content corresponding to each function / item. The confirmation control is used to prompt the user that there are no privacy-related items requiring confirmation in the current target channel, and allows the user to confirm and close the prompt window. The text content corresponding to each function / item is used to display each function / item to the user, thus achieving the purpose of prompting.

[0101] In some embodiments, the second target window 81 is displayed over the currently playing content in an overlay form, and the controller 250 does not interrupt the current playback content of the target channel while the second target window 81 is displayed.

[0102] S720: If a trigger operation for triggering the confirmation control is detected, close the second target window.

[0103] In some embodiments, the controller 250 detects a user's trigger operation on the confirmation control in the second target window 81. The triggering method can refer to the method described in the previous embodiments, and will not be repeated here. After detecting the trigger operation on the confirmation control, the controller 250 can determine that the user is aware of the functions displayed in the second target window 81. At this time, the controller can directly exit the second target window 81 and continue to display the currently playing content.

[0104] Since there are no privacy-related items, the second target window 81 is only used to display functional items to the user. The user does not need to enter the management interface to perform operations one by one. They only need to browse each functional item through the second target window 81. Compared with the first target window, the operation path of the second target window 81 is shorter and the window layout is simpler, reducing the interaction steps in non-consent functional item scenarios, thereby improving interaction efficiency.

[0105] Based on the above technical solution, when the functional payment does not include privacy payment, a second target window 81 with a confirmation control pops up. After the confirmation control is triggered, the second target window 81 exits directly, thereby simplifying the processing flow and window interaction logic of functional payments without privacy confirmation requirements, reducing unnecessary interface windows and operation steps, and improving the smoothness of interface interaction during channel switching.

[0106] Figure 9 This application provides a flowchart for displaying the difference in payment using a display device according to some embodiments.

[0107] In some embodiments, after the controller 250 executes step S410, the following steps may also be included: S910: Locate historical versions of signaling files in local storage.

[0108] In some embodiments, after obtaining the signaling file from the service layer signaling, the controller 250 first checks in local storage whether a historical version corresponding to the signaling file exists. The controller 250 can use a combination of the root node attribute (schemaVersion attribute) of the signaling file and the identifier corresponding to the target channel as a lookup key to search in the privacy record database locally stored by the display device 200 for a matching historical version.

[0109] S920: If a historical version of the signaling file is found in local storage, the difference in payment is determined by comparing the current version of the signaling file with the historical version.

[0110] If a historical version is found, it means that the current version of the signaling file is based on an updated version of the signaling file stored on display device 200. Controller 250 compares the current version and historical versions of the signaling file line by line to determine the difference items. Difference items are items that differ between historical and current versions of the signaling file. These difference items include the following three categories: The first category is newly added items, which refer to functional items that exist in the current version but not in historical versions. The second category is modified items, which refer to functional items whose key attributes, such as the attribute values ​​of the legal basis, type identifiers, and the text content of personal information descriptions, have changed between the current and historical versions. The third category is deleted items, which refer to functional items that existed in historical versions but not in the current version.

[0111] S930: In cases where the differential payment includes at least one privacy payment, control the display to show the first target window.

[0112] After completing the differential payment detection, the controller 250 checks whether the differential payment includes privacy clauses (i.e., clauses with a lawfulbasis of Consent). If the differential payment includes at least one privacy clause, the control display 260 displays the changed terms to the user in a first target window on the user interface, and allows the user to reconfirm the execution status through the management controls in the first target window.

[0113] In some embodiments, when the first target window displays the difference payment, a "Confirm Difference Update" control can be added. After the user triggers an operation based on the input of this control, the controller 250 can record the final execution status of all privacy payments in this difference payment and save the updated complete privacy payment record to the local database, overwriting historical versions. The controller 250 can also send the user's privacy confirmation result back to the broadcast provider through the interface specified by deliveryUrl in the signaling file.

[0114] In some embodiments, after performing the confirmation differential update, the controller 250 can update the counter data of various types of items in the privacy preference model according to the final execution status of all privacy items, thereby updating the historical selection information.

[0115] S940: When the difference payment does not include the privacy payment, control the display to show a second target window.

[0116] If the difference in payments does not include privacy payments (such as only adding or modifying non-consent payments), the control display 260 will notify the user in a second target window on the user interface that the signaling file has been updated, and the user only needs to click the confirmation control.

[0117] In some embodiments, the controller 250 can employ differentiated visual identifiers for different types of changes. For example, newly added payments are marked with a green "New" label to highlight the user's awareness of a new data collection intent; modified payments are marked with an orange "Modified" label, and the differences before and after the change are displayed in a comparative format to help users quickly identify the terms and conditions changes; deleted payments are marked with a gray "Removed" label to inform the user that the processing of this payment has stopped and no further action is required. Historical payments that have not undergone changes are displayed in a collapsed manner at the bottom of the window, collapsed by default, and users can manually expand them to view the complete history.

[0118] Based on the above technical solution, the difference in payment is determined by comparing the current version with the historical version. Depending on whether the difference in payment includes privacy payment, the first target window or the second target window is displayed. Users do not need to repeatedly verify all the payment functions in the signaling file. They only need to select and process the difference in payment due to version differences, avoiding repeated display and verification of already confirmed payment functions and improving payment confirmation efficiency.

[0119] In some embodiments, after the controller 250 executes step S610, if the historical version corresponding to the signaling file is not found in the local storage, the controller 250 executes the step of extracting at least one function item from the signaling file.

[0120] For example, when a user switches to a channel for the first time, there is no historical version of the signaling file for the target channel in the local storage, indicating that the user is confirming the signaling file for that channel for the first time. Since there is no comparable historical version, the controller 250 skips the differential detection process, directly extracts all functional items from the signaling file, and decides whether to display the first target window or the second target window based on whether privacy items are included.

[0121] In some embodiments, after the controller 250 processes the signaling file completely for the first time and the user confirms the privacy payment, it stores the complete content of the current signaling file (including the file version identifier, details of all functional payments, and the user's execution status selection) in the local database as a historical version for the next time the channel is switched. This allows the controller 250 to gradually accumulate selection information for each channel and each type of payment during the user's use, forming a complete historical dataset that can be used for subsequent differential comparison and preference analysis.

[0122] Based on the above technical solutions, this application embodiment directly executes the step of extracting functional funds when no historical version of the signaling file is found in local storage. For scenarios where the target channel is switched for the first time, or where the privacy funds corresponding to the target channel are different from the privacy funds of the historical version, the process of extracting functional funds and determining privacy funds is directly executed, simplifying the processing logic of the first channel switch and improving the execution efficiency of confirming funds.

[0123] Figure 10 This is a flowchart illustrating the process by which a display device, as provided in an embodiment of this application, determines the execution status of privacy payments based on historical selection information.

[0124] like Figure 10 As shown, in some embodiments, the controller 250 performing step S450 may include the following steps: S451: Extract from historical selection information the number of times a user consented to at least one privacy payment of the same type and the number of times a user refused to comply with at least one privacy payment of the same type.

[0125] In some embodiments, the controller 250 uses the type identifier of the privacy payment for the target channel as the key to query the historical selection records corresponding to the type identifier in the privacy preference model, thereby extracting two counter values: allowCount and denyCount. allowCount represents the number of times the user has agreed to the privacy payment for this type within a preset period of time, and denyCount represents the number of times the user has refused to accept the privacy payment for this type within a preset period of time.

[0126] In some embodiments, if the privacy payment corresponding to the type identifier has never been confirmed by the user in the history (e.g., the user encounters the Personalisation type payment for the first time), then allowCount and denyCount are both 0, there is no corresponding record in the preference model, and the controller 250 will enter the processing branch for insufficient historical selection information.

[0127] S452: Determine the total number of executions of the same type of payment corresponding to at least one privacy payment based on the number of times of consent to execution and the number of times of refusal to execution corresponding to at least one privacy payment.

[0128] In some embodiments, the controller 250 can calculate the sum of the number of times a user agrees to execute the privacy payment for this type and the number of times a user refuses to execute the privacy payment for this type, to obtain the total execution count. The total execution count represents the total number of interactions a user has with this type of payment within a preset time period, and is an important basis for assessing whether historical selection information is sufficient.

[0129] If the total number of executions is too small (e.g., less than the preset minimum number threshold, such as 3 times), the historical selection information is insufficient to reliably reflect user preferences. The controller 250 will not determine the execution status of the privacy payment for the target channel based on the historical selection information, but will instead execute the processing branch where the historical selection information is insufficient, i.e., return to the standard default value of the privacy payment. For consent-type payments, the standard default value is to refuse execution.

[0130] S453: Determine the confidence level of consent execution for at least one privacy payment based on the ratio of the number of consent executions to the total number of executions.

[0131] In some embodiments, the controller 250 can calculate the ratio of the number of consent executions to the total number of executions to obtain the confidence of consent execution for at least one privacy payment. The confidence of consent execution is a core indicator for quantifying users' historical preferences. The higher the confidence of consent execution, the higher the probability that the user has consented to this type of privacy payment in the past, and the more obvious the user's preference tendency.

[0132] In another implementation, controller 250 may also choose to calculate the ratio of the number of rejections to the total number of executions to obtain the rejection confidence of at least one privacy payment. The higher the rejection confidence, the lower the probability that the user has agreed to the execution of this type of privacy payment in the past, and the less bias the user has towards this type of privacy payment.

[0133] S454: Determine the execution status of at least one privacy payment based on the confidence level of consent execution corresponding to at least one privacy payment.

[0134] In some embodiments, the controller 250 may determine the range of values ​​for the confidence level of agreeing to execute based on at least two confidence thresholds, namely a first confidence threshold and a second confidence threshold greater than the first confidence threshold. Furthermore, considering that insufficient historical selection information may lead to randomness in the determination of the execution state, the controller 250 may combine the total number of executions in the process of determining the execution state.

[0135] Taking a first confidence threshold of 0.3 and a second confidence threshold of 0.7 as an example, when confidence is greater than or equal to 0.7 and totalCount is greater than or equal to 3, controller 250 determines the execution status of pre-filling privacy funds as "agree to execute"; when confidence is less than or equal to 0.3 and totalCount is greater than or equal to 3, controller 250 determines the execution status of pre-filling privacy funds as "reject execute"; in other cases (the middle range of 0.3-0.7 or totalCount less than 3), controller 250 enters the processing branch for insufficient historical selection information and reverts the execution status to the standard default value, that is, the default execution status of privacy funds is "reject execute".

[0136] Based on the above technical solutions, by extracting the number of times that privacy payments were agreed to or refused to be executed for the same type, calculating the total number of executions and the confidence level of the agreed execution, the execution status of privacy payments can be determined. This ensures that the execution status of privacy payments pre-filled is consistent with the user's long-term selection preferences, avoids the judgment bias caused by a single historical record, and improves the rationality and reliability of the automatic determination of the execution status of privacy payments.

[0137] Figure 11 A flowchart showing a preview of the functions performed by a display device according to some embodiments of this application.

[0138] In some embodiments, after executing step S460, the controller 250 is further configured to perform the following steps: S1110: If a selection action is detected to select a target privacy payment, obtain the feature preview mapping table.

[0139] In some embodiments, in the management window, the controller 250 can detect the selection operation of the target privacy fund in the management window and trigger the function preview process when the selection operation is detected, wherein the target privacy fund is any privacy fund in the management window.

[0140] For example, whenever a user moves the focus to a privacy item using the directional keys on the remote control (i.e., selects it), the controller 250 triggers the feature preview process and retrieves the feature preview mapping table.

[0141] The feature preview mapping table includes at least one feature prompt message corresponding to a privacy payment. The feature prompt message includes a description of the impact of the privacy payment. The following is an example of a feature preview mapping table: Marketing: When agreeing to the privacy payment - the feature prompt message is "You can receive personalized ads and promotional recommendations". When refusing - the feature prompt message is "You will only receive general ads and will not be able to receive exclusive offers based on your viewing habits". Analytics: When agreeing to the privacy payment - the feature prompt message is "The system will analyze your viewing behavior to optimize the content recommendation algorithm". When refusing - the feature prompt message is "Content recommendations will be based on general popular content and cannot be personalized according to your preferences".

[0142] S1120: Based on the feature preview mapping table, determine the feature prompt information corresponding to the target privacy payment.

[0143] In some embodiments, the controller 250 can look up the corresponding function prompt information in the function preview mapping table according to the type identifier corresponding to the target privacy payment. For example, if the target privacy payment is "marketing", the controller 250 can look up the function prompt information corresponding to the privacy payment being "marketing" in the function preview mapping table.

[0144] S1130: Based on the function prompt information corresponding to the target privacy payment, control the display to show the function preview area.

[0145] In some embodiments, the controller 250 may invoke the rendering logic of the function preview area to display the function preview area in the management window according to the function prompt information corresponding to the target privacy amount.

[0146] Figure 12 This is a preview area interface diagram of the display device provided in some embodiments of this application.

[0147] like Figure 12 In the management window shown, Privacy Item 3 is the selected privacy item. The function preview area of ​​Privacy Item 3 is displayed in an animated manner below the item containing Privacy Item 3. The function preview area 121 does not obstruct the content displayed in the management window and does not affect the normal display and interaction of other items in the management window, ensuring that the user can always see the complete list of terms and conditions and the function prompt information of the currently selected item at the same time.

[0148] In one implementation, the feature preview area 121 adopts a visual style that differs from the terms and conditions description text (e.g., a light yellow background with information icons), enabling users to quickly distinguish between the terms and conditions description and the feature impact prompts, thus avoiding visual confusion.

[0149] In one implementation, when the user moves the focus to another privacy item, i.e., switches from selecting the target privacy item to selecting another privacy item, the controller 250 can close the preview area 121 of the target privacy item in an animated manner (i.e., Figure 12 (in the opposite direction of the arrow shown), and at the same time expand the preview area 121 of the newly selected privacy payment function to achieve a smooth focus-following preview effect.

[0150] Based on the above technical solutions, after displaying the management window, this application embodiment retrieves the function preview mapping table for the selected target privacy fund, determines the function prompt information corresponding to the target privacy fund, and displays an unobstructed function preview area 121. Users can view the function prompt details corresponding to the target privacy fund in real time without obstructing the content of the management window, without exiting the management window or jumping to an additional interface. This helps users quickly understand the actual function of each privacy fund and improves the intuitiveness and readability of users' understanding of privacy funds.

[0151] In some embodiments, when the controller 250 detects a change operation for changing the execution status of the target privacy fund, it will perform a switching operation on the selected target privacy fund Toggle, thereby triggering the feature preview process. The controller 250 obtains the feature preview mapping table and looks up the corresponding feature prompt information from the feature preview mapping table according to the new execution status (agree / reject) after the Toggle is switched.

[0152] Figure 13 This is a flowchart illustrating the switching execution state of a display device as provided in some embodiments of this application.

[0153] See Figure 13 Unlike the preview triggered by the selected operation, the function prompt information triggered by the change operation will be dynamically updated according to the new status of Toggle. For example, when the user changes the "Analytics" type item from "Refuse to execute" to "Agree to execute", the controller 250 will retrieve the function prompt information corresponding to "Agree to execute" in the function preview mapping table: "The system will analyze your viewing behavior to optimize the content recommendation algorithm".

[0154] After receiving the function prompt information, the controller 250 controls the display 260 to remove the original function prompt information corresponding to "Refuse to execute" ("Content recommendations will be based on general popular content and cannot be personalized according to your preferences") from the function preview area 121, and instead displays the function prompt information corresponding to "Agree to execute" ("The system will analyze your viewing behavior to optimize the content recommendation algorithm"). This updates and changes the function prompt information in the function preview area 121, allowing the user to obtain a description of the impact of agreeing to execute the target privacy payment based on the changed function prompt information. Through this preview update mechanism, the display device 200 enables the user to immediately know the functional impact of each Toggle change operation, assisting the user in making privacy choices that align with their wishes and avoiding choices made against their will due to misunderstandings of the terms.

[0155] In some embodiments, after the user completes the adjustment of the execution status of all privacy funds, they can click the "Confirm" control at the bottom of the management window to enter a confirmation operation. In response to the confirmation operation for confirming the execution status of the target privacy fund, the controller 250 records the changed execution status of the target privacy fund and exits the management window and the first target window (or the second target window) to avoid multiple windows obstructing the playback content of the target channel and improve the user's viewing experience.

[0156] Based on the above technical solution, when the controller 250 detects a change in the execution status of the target privacy payment, it simultaneously retrieves the function preview mapping table to display the function preview area 121. After confirming the change, it records the corresponding execution status and exits the management window. When changing the execution status of the privacy payment, the user can view the function prompt information in real time through the function preview area 121 to assist the user in adjusting the execution status. At the same time, it records the changed execution status, completing the closed loop of this privacy payment configuration and improving the accuracy of the user's decision when changing the execution status of the target privacy payment.

[0157] In some embodiments, after a user clicks the "Confirm" control in the management window to complete the confirmation of this privacy payment, the controller 250 can update the counter value of the privacy preference model, thereby updating the number of times the payment was agreed to, the number of times it was rejected, and the total number of times it was executed for this type of payment, thus updating the historical selection information. For example, if the user confirms the execution status of the target privacy payment as "Agree to Execute", the controller 250 will increment the value of the counter used to record allowCount by 1 in the privacy preference model, and increment totalCount by 1. At the same time, the controller 250 will also update the last selection result (lastChoice) to "Agree to Execute" and recalculate the confidence level of agreeing to execute.

[0158] If the user confirms the execution status of the target privacy payment as "deny execution", the controller 250 increments the value of the counter used to record denyCount by 1 in the privacy preference model, increments totalCount by 1, updates lastChoice to "deny execution", and recalculates the confidence level of consent execution.

[0159] Based on the above technical solution, after recording the execution status of the target privacy payment, the controller 250 synchronously adjusts the number of times the corresponding type of payment is agreed to, rejected, and the total number of executions, and updates the user's historical selection information in real time. This provides the latest historical selection information for the calculation of the confidence level of the execution status of subsequent privacy payments and the pre-filling of the execution status, thereby improving the accuracy of pre-filling the execution status of privacy payments.

[0160] In some embodiments, after executing step S410, the controller 250 may further parse the XML structure corresponding to the signaling file to extract the preset display data for each function item. The preset display data includes the title text of the function item, an identification code for instructing the terminal device to receive the function item, a language identifier, and a declaration text for the function item.

[0161] In some embodiments, the title text of a function payment can be a combination of the function payment and the target channel name, such as “Payment 1-TV1”. The controller 250 can extract the channel name from the root node attribute of the signaling file or the metadata of the target channel and concatenate it with the fixed prefix of the function payment (such as payment 1) to form the title text, so that the user can determine the channel source to which the first target window belongs from the title text.

[0162] In some embodiments, the controller 250 can generate an identification code based on the privacy notification URL stored in the privacy statement link attribute field of the signaling text. This identification code can be recognized by various terminal devices, including the display device 200, through image scanning. For example, the identification code can be a QR code. After parsing the privacy notification URL, the controller 250 can encode the URI into a QR code using a QR code generation module. Users can scan the QR code using a mobile terminal (such as a smartphone or tablet) to be redirected to the full privacy payment page.

[0163] In some embodiments, the controller 250 may extract a statement text from the initial disclaimer field in the signaling text, the statement text including information such as the overall purpose of data collection, the data retention period, and the user's basic rights.

[0164] In some embodiments, the controller 250 can extract language identifiers from the language field in the signaling text. For example, "pt-BR" represents Brazilian Portuguese and "en" represents English. The controller 250 can match the corresponding language identifiers to the function items according to the system language currently set by the display device 200, ensuring that the language of the content displayed to the user conforms to the user's usage habits.

[0165] Based on the above extraction process, when the controller 250 executes step S430, it can display the title text in the first display area, the identification code in the second display area, and the declaration text in the third display area based on the language corresponding to the language identifier.

[0166] In some embodiments, the controller 250 may divide the first target window into a first display area, a second display area, and a third display area based on the extracted preset display data, wherein the first display area, the second display area, and the third display area do not overlap with each other to ensure the integrity of the information displayed in each area.

[0167] The controller 250 can display title text in the first display area, identification code in the second display area, and declaration text in the third display area based on the language corresponding to the language identifier.

[0168] In some embodiments, the first display area, the second display area, and the third display area may be arranged vertically from top to bottom, so that users can first intuitively view the title text of the feature item in the first display area, then view the identification code in the second display area, and finally view the declaration text in the third display area.

[0169] In one implementation, the controller 250 can adjust the display area and layout of the title text, identification code, and declaration text of the feature item based on the user's personalized settings.

[0170] It should be noted that the above embodiments are described in detail with reference to the layout of the first target window. The layout of the second target window can be referred to the layout of the above embodiments, and will not be repeated here.

[0171] Based on the above technical solutions, this embodiment extracts the preset display data of functional payments from the signaling file, and displays the title text, identification code and declaration text in the first, second and third display areas in layers according to the language identifier, thereby improving the rationality of the interface layout of the first target window, making privacy payment and functional payment information reasonably arranged in the first target window, and improving the readability of window information.

[0172] In some embodiments, the controller 250 can obtain a broadcast provider mapping table in response to a user's activation command based on the "Privacy Management" function in the settings menu. The broadcast provider mapping table includes the correspondence between broadcast providers and feature payments. This correspondence can be displayed in the user interface using a two-layer navigation structure: a list view and a terms and conditions view. The list view includes broadcast providers whose privacy payment records have been stored on the display device 200, with each entry in the list view corresponding to one broadcast provider. The terms and conditions view includes a complete list of privacy payments corresponding to each broadcast provider, with each entry in the terms and conditions view corresponding to the last confirmed execution status of the corresponding privacy payment. The user can input modification commands based on the broadcast provider mapping table to modify the execution status of the privacy payment at the function menu level, and click the "Confirm" control to save and update the execution status.

[0173] It should be noted that the process of the controller 250 providing the mapping table to modify the execution state via broadcast can also trigger the update of the number of times each counter in the privacy preference model is recorded.

[0174] Some embodiments of this application also provide an electronic device 500, which can be a mobile terminal, tablet computer, or other device with touch functionality. The electronic device 500 may include a controller 510 and a display 520. The display 520 can receive user input commands or operations through its own touch functionality. Based on this, the controller 510 is configured as follows: In response to a channel switching command transmitted by the display 520, a signaling file associated with a target channel is obtained; wherein the target channel is the channel corresponding to the channel switching command; at least one functional item is extracted from the signaling file; if at least one privacy item is included in the at least one functional item, the display is controlled to display a first target window; wherein the first target window includes management controls; privacy items are items that require user confirmation for execution, and the management controls are used to trigger the display to show a management window, which is a window related to the execution status of the privacy item; based on the operation event transmitted by the display, historical selection information is obtained according to the item type of at least one privacy item; wherein the historical selection information is used to characterize the user's preference for the execution status of at least one privacy item; the operation event is an event corresponding to the triggering operation of the management controls; the execution status of at least one privacy item is determined based on the historical selection information; based on the execution status of at least one privacy item, the display is controlled to display a management window; wherein the management window includes a text description of at least one privacy item and the execution status of at least one privacy item.

[0175] Based on the above display device 200 and / or electronic device 500, some embodiments of this application also provide a function selection method that can be applied to the above display device 200, including steps S410-S460 shown in the above embodiments: S410: In response to a channel switching command, obtain the signaling file associated with the target channel.

[0176] The target channel is the channel corresponding to the channel switching instruction.

[0177] S420: Extract at least one function payment from the signaling file.

[0178] S430: If at least one privacy policy is included in at least one feature policy, control the display to show the first target window.

[0179] The first target window includes management controls; privacy payments are payments that require user confirmation before execution; the management controls are used to trigger the display of the management window, which is a window related to the execution status of privacy payments.

[0180] S440: If a triggering operation for triggering the management control is detected, obtain historical selection information based on at least one privacy payment type.

[0181] Among them, historical selection information is used to characterize a user's preference for the execution status of at least one privacy payment.

[0182] S450: Determine the execution status of the at least one privacy payment based on historical selection information.

[0183] S460: Controls the display to show the management window based on the execution status of at least one privacy payment.

[0184] The management window includes a text description of at least one privacy payment and the execution status of at least one privacy payment.

[0185] The implementation methods and beneficial effects of the embodiments provided in this application can be found in the foregoing embodiments, and will not be repeated here.

[0186] As can be seen from the above technical solutions, some embodiments of this application provide a display device, an electronic device, and a method for selecting function payments. This method, after obtaining the signaling file associated with the target channel and extracting function payments in response to a channel switching command, identifies privacy payments within the function payments and displays a first target window including management controls. After the user triggers the management controls, historical selection information is obtained according to the category of the privacy payment, and the execution status of the privacy payment is determined based on the historical selection information. The privacy payment and its corresponding execution status are then displayed in the management window. Embodiments of this application can avoid users manually confirming payments when continuously switching between multiple channels with unconfirmed privacy payments, reducing the frequency of manual confirmation, simplifying the confirmation process for privacy payments, and improving the efficiency of privacy payment confirmation.

[0187] The same or similar parts among the various embodiments in this specification can be referred to mutually, and will not be repeated here.

[0188] Those skilled in the art will clearly understand that the techniques in the embodiments of the present invention can be implemented using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solutions in the embodiments of the present invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of various embodiments or certain parts of the embodiments of the present invention.

[0189] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0190] For ease of explanation, the above description has been provided in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Various modifications and variations can be obtained based on the above teachings. The selection and description of the above embodiments are for the purpose of better explaining the principles and practical applications, thereby enabling those skilled in the art to better utilize the described embodiments and various different variations of embodiments suitable for specific use considerations.

Claims

1. A display device, characterized in that, include: monitor; The controller is configured as follows: In response to a channel switching command, a signaling file associated with a target channel is obtained; wherein, the target channel is the channel corresponding to the channel switching command; Extract at least one functional item from the signaling file; If at least one privacy payment is included in the at least one functional payment, the display is controlled to show a first target window; wherein the first target window includes management controls; the privacy payment is a payment that requires user confirmation for execution, the management controls are used to trigger the display to show a management window, and the management window is a window related to the execution status of the privacy payment; If a triggering operation for triggering the management control is detected, historical selection information is obtained according to the payment type of the at least one privacy payment; wherein, the historical selection information is used to characterize the user's preference for the execution status of the at least one privacy payment; The execution status of the at least one privacy payment is determined based on the historical selection information. Based on the execution status of the at least one privacy payment, the display is controlled to show a management window; wherein the management window includes a text description of the at least one privacy payment and the execution status of the at least one privacy payment.

2. The display device according to claim 1, characterized in that, The controller is also configured to: If none of the aforementioned features include the privacy feature, the display is controlled to show a second target window; wherein the second target window includes a confirmation control; If a triggering operation is detected that triggers the confirmation control, the second target window is closed.

3. The display device according to claim 2, characterized in that, After the controller executes the channel switching command and obtains the signaling file associated with the target channel, it is further configured to: Locate historical versions of the signaling file in local storage; If a historical version of the signaling file is found in the local storage, the difference amount is determined by comparing the current version and the historical version of the signaling file. The difference amount is the amount that differs between the historical version and the current version of the signaling file. If the difference payment includes at least one privacy payment, control the display to show the first target window; If the difference in payment does not include the privacy payment, control the display to show the second target window.

4. The display device according to claim 3, characterized in that, After the controller performs the operation of searching for historical versions of the signaling file in local storage, it is further configured to: If no historical version of the signaling file is found in the local storage, then the step of extracting at least one function item from the signaling file is performed.

5. The display device according to claim 1, characterized in that, The controller determines the execution status of the at least one privacy payment based on the historical selection information, and is specifically configured as follows: Extract from the historical selection information the number of times the user agreed to execute the same type of payment for the at least one privacy payment and the number of times the user refused to execute the same type of payment for the at least one privacy payment; The total number of executions of the same type of payment corresponding to the at least one privacy payment is determined based on the number of times the payment was agreed to and the number of times the payment was refused. The confidence level of consent execution corresponding to the at least one privacy payment is determined based on the ratio of the number of consent executions to the total number of executions. The execution status of the at least one privacy payment is determined based on the confidence level of consent to execute corresponding to the at least one privacy payment.

6. The display device according to claim 1, characterized in that, After the controller executes the execution status based on the at least one privacy payment and controls the display to show the management window, it is further configured to: Upon detecting an operation to select a target privacy item, a function preview mapping table is obtained; wherein, the target privacy item is any privacy item in the management window; the function preview mapping table includes function prompt information corresponding to at least one privacy item; Based on the function preview mapping table, determine the function prompt information corresponding to the target privacy payment; Based on the function prompt information corresponding to the target privacy payment, the display is controlled to show a function preview area; wherein, the function preview area and the content displayed in the management window do not obstruct each other.

7. The display device according to claim 6, characterized in that, After the controller executes the execution status based on the at least one privacy payment and controls the display to show the management window, it is further configured to: Upon detecting an operation used to change the execution status corresponding to the target privacy payment, the function preview mapping table is obtained; Based on the function preview mapping table, determine the function prompt information corresponding to the target privacy payment; Based on the function prompt information corresponding to the target privacy amount, control the display to show the function preview area; In response to an operation used to confirm the execution status of the target privacy fund, the execution status of the target privacy fund is recorded.

8. The display device according to claim 7, characterized in that, In response to a confirmation operation used to confirm the execution status of the target privacy fund, the controller, after recording the execution status of the target privacy fund, is further configured to: Adjust the number of times to agree to execute and the total number of times to execute, or the number of times to refuse to execute and the total number of times to execute, according to the execution status of the target privacy fund and the type to which the target privacy fund belongs.

9. An electronic device, characterized in that, include: monitor; The controller is configured as follows: In response to the channel switching instruction transmitted by the display, a signaling file associated with the target channel is obtained; wherein the target channel is the channel corresponding to the channel switching instruction; Extract at least one functional item from the signaling file; If at least one privacy payment is included in the at least one functional payment, the display is controlled to show a first target window; wherein the first target window includes management controls; the privacy payment is a payment that requires user confirmation for execution, the management controls are used to trigger the display to show a management window, and the management window is a window related to the execution status of the privacy payment; Based on the operation events transmitted by the display, historical selection information is obtained according to the type of the at least one privacy payment; wherein, the historical selection information is used to characterize the user's preference for the execution status of the at least one privacy payment; the operation event is an event corresponding to the triggering operation of the management control; The execution status of the at least one privacy payment is determined based on the historical selection information. Based on the execution status of the at least one privacy payment, the display is controlled to show a management window; wherein the management window includes a text description of the at least one privacy payment and the execution status of the at least one privacy payment.

10. A method for displaying functional payments, characterized in that, include: In response to a channel switching command, a signaling file associated with a target channel is obtained; wherein, the target channel is the channel corresponding to the channel switching command; Extract at least one functional item from the signaling file; If at least one privacy payment is included in the at least one functional payment, the display is controlled to show a first target window; wherein the first target window includes management controls; the privacy payment is a payment that requires user confirmation for execution, the management controls are used to trigger the display to show a management window, and the management window is a management window related to the execution status of the privacy payment; If a triggering operation for triggering the management control is detected, historical selection information is obtained according to the payment type of the at least one privacy payment; wherein, the historical selection information is used to characterize the user's preference for the execution status of the at least one privacy payment; The execution status of the at least one privacy payment is determined based on the historical selection information. The display is controlled based on the execution status of the at least one privacy payment. The management window includes a text description of the at least one privacy payment and the execution status of the at least one privacy payment.

Images