Mobile phone software and hardware interaction scene control method and device for back screen pixelated display

Abstract

This invention discloses a method and apparatus for controlling pixelated display on the back screen in mobile phone hardware and software interaction scenarios, relating to the field of smart terminal technology. The method includes: comprehensively monitoring hardware and software events of the mobile terminal through system-level services; responding to events by matching corresponding graphic resources from a resource library; intelligently scheduling events based on preset priority rules to determine the current display content of the back dot matrix screen, with scheduling strategies including high-priority event preemption, merging of events of the same priority, or carousel display; converting the finally determined graphic resources into pixelated data adapted to the dot matrix screen for display; this invention also achieves environmentally adaptive display control by fusing sensor data; this invention solves the problems of limited usage scenarios, chaotic display when multiple events occur concurrently, and lack of environmental awareness in existing technologies for back dot matrix screens, achieving efficient, intuitive, intelligent, and low-power system status indication, improving user experience and device energy efficiency.

Description

Technical Field

[0001] This invention relates to the field of smart terminal technology, specifically to a control method, device, electronic device, and storage medium for pixelated display on the back screen in a mobile phone software / hardware interaction scenario. Background Technology

[0002] As the core terminal of modern life, smartphones integrate a wealth of software and hardware functional modules. In daily use, smartphones need to provide real-time feedback on a large amount of system status information, such as incoming calls, SMS notifications, Bluetooth / Wi-Fi connection status, charging progress, NFC card swipe feedback, and voice assistant wake-up status.

[0003] Traditional status indicators mainly rely on two methods: one is a monochrome LED breathing light at the top or front of the phone, which uses different colors and flashing frequencies to indicate a rough status (such as missed calls or charging); the other is to directly light up the main screen to display detailed notification content. However, both methods have obvious drawbacks. With the popularization of full-screen and under-display camera designs, the physical space on the front of the phone has been extremely compressed, leading to the gradual elimination of the top LED light. While viewing the status by lighting up the main screen presents complete information, it brings a series of problems: First, lighting up the main screen (especially on OLED screens) consumes a lot of power, and frequent screen lighting will significantly affect battery life; second, the act of lighting up the screen itself is intrusive, interrupting the user's current operation or the operation of other applications (such as games or video playback); third, in light-sensitive scenarios such as sleeping at night, meetings, or watching movies, the sudden lighting of the screen will cause light pollution and be disruptive.

[0004] Against this backdrop, some high-end mobile phones have begun to integrate low-power, low-resolution dot matrix screens (or "secondary screens" or "smart windows") on the back cover (back). These dot matrix screens are typically composed of hundreds of independent LEDs or micro-pixels, and have advantages such as low power consumption, always-on display, and customizable graphic expression, providing an ideal alternative for system status indication. Users expect to be able to intuitively and clearly understand the specific system status (e.g., distinguish between WeChat messages and SMS messages, fast charging and normal charging, Bluetooth connection and searching) simply by glancing at the back of the phone without turning on the main screen or interrupting the current operation, rather than the vague prompts provided by traditional LED lights.

[0005] However, current technologies for back-mounted dot matrix displays mostly limit themselves to simple clock displays, custom patterns, or static prompts for single events (such as flashing for incoming calls). They lack a systematic and intelligent solution to achieve the interactive goal of "zero disruption and high information density." Specific problems include: 1) Incomplete event capture: The system cannot deeply and comprehensively monitor the complex hardware and software events and associate them with the back display; 2) Chaotic display logic: When multiple events (such as incoming calls, messages, and charging) occur simultaneously or consecutively, the lack of an effective scheduling strategy may lead to display conflicts, information overlay, or omissions; 3) Stiff interactive experience: The display strategy is fixed and cannot adapt to the phone's environment (such as in a pocket, upside down, or at night), potentially causing unnecessary brightness in inappropriate scenarios.

[0006] Therefore, there is an urgent need for a display control algorithm for smartphone software / hardware interaction scenarios that can deeply monitor system software and hardware events, has intelligent priority scheduling, low latency response, and supports environmental adaptation, so as to fully tap the potential of the rear dot matrix screen and improve the intelligent experience and energy efficiency of smartphones. Summary of the Invention

[0007] In view of this, the present invention provides a method, device, electronic device and storage medium for controlling pixelated display on the back screen in mobile phone software / hardware interaction scenarios, aiming to solve the problems of limited usage scenarios, chaotic information presentation and lack of intelligent scheduling and environmental adaptability of the back dot matrix screen in the prior art.

[0008] To achieve the above objectives, the present invention adopts the following technical solution: In a first aspect, the present invention provides a method for controlling pixelated display on a mobile phone software / hardware interaction scenario, comprising: Monitoring steps: Monitor at least one software or hardware event of the mobile terminal through system-level services; the software or hardware events include at least one of software notification events, system broadcast events, hardware interrupt events, and sensor events; Matching step: In response to the detection of a target software or hardware event, match the graphics resource corresponding to the target software or hardware event from the preset resource library; Scheduling steps: Based on preset priority rules, the target software and hardware events are scheduled and processed to determine the target events that should be displayed on the back dot matrix screen of the mobile terminal. Rendering step: Based on the processing result of the scheduling step, the graphic resources corresponding to the target event are converted into pixelated display data adapted to the resolution of the rear dot matrix screen; Execution steps: The pixelated display data is sent to the driver layer of the rear dot matrix screen for display.

[0009] In conjunction with the first aspect, in one possible implementation, the listening step includes: By inheriting NotificationListenerService and overriding the onNotificationPosted method, we can listen for and filter notification events from whitelisted applications, and extract the application package name, notification icon, and title. By registering a BroadcastReceiver and setting the corresponding IntentFilter, listen for system broadcast events, including power connection events, Bluetooth connection status change events, and airplane mode on / off events. By registering callbacks or listening to system services of the underlying Hardware Abstraction Layer (HAL), hardware interrupt events can be captured, including NFC tag sensing events, fingerprint recognition events, and physical button events. By registering a SensorEventListener, data from the proximity sensor, gyroscope sensor, and ambient light sensor can be listened to.

[0010] In conjunction with the first aspect, in one possible implementation, the scheduling step includes: Maintain an event queue sorted by priority; When a new event is detected, its priority is compared with that of the currently displayed event; If the priority of the new event is higher than the priority of the currently displayed event, then the current display is interrupted and the new event is set as the target event; If the priority of a new event is not higher than that of the currently displayed event, the new event will be added to the event queue for queuing.

[0011] In conjunction with the first aspect, in one possible implementation, the scheduling step further includes a conflict resolution strategy, which includes: For multiple concurrent events with the same priority, a time-slice carousel strategy is used to display them alternately on the rear dot matrix screen; Alternatively, the graphic resources corresponding to the multiple concurrent events with the same priority can be stitched together and displayed in the same frame.

[0012] In conjunction with the first aspect, in one possible implementation, the method further includes an environment adaptation step: Obtain environmental context information from the sensors; Based on the environmental context information, adjust the parameters of the rendering step or execution step; The environmental context information includes at least one of whether the mobile terminal is obstructed, the screen orientation, and the ambient brightness; the adjusted parameters include at least one of the display brightness, display color, and display content.

[0013] Secondly, the present invention provides a control device for pixelated display on a mobile phone software / hardware interaction scenario, comprising: The listening module is used to listen for at least one software or hardware event on the mobile terminal through system-level services. The matching module is used to match the graphics resources corresponding to the target software and hardware event from a preset resource library in response to the detection of the target software and hardware event. The scheduling module is used to schedule the target software and hardware events based on preset priority rules in order to determine the target events that should be displayed on the back dot matrix screen of the mobile terminal. The rendering module is used to convert the graphic resources corresponding to the target event into pixelated display data adapted to the resolution of the rear dot matrix screen, based on the processing result of the scheduling module. The execution module is used to send the pixelated display data to the driver layer of the rear dot matrix screen for display.

[0014] Thirdly, the present invention provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the method as described in the first aspect or any possible implementation thereof.

[0015] Fourthly, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method as described in the first aspect or any possible implementation thereof.

[0016] Compared with the prior art, the beneficial effects of the technical solution provided by the present invention include at least the following: 1. Precise and efficient information delivery: By deeply associating and mapping various abstract hardware and software events at the system's underlying level (such as specific APP notifications, fast charging protocols, and NFC card swiping) with concrete pixel graphics (such as APP icons, charging percentage animations, and successful card swiping animations), users can accurately and intuitively obtain rich and specific system status information without turning on the main screen, simply by glancing at the back of the phone. This greatly improves information acquisition efficiency and achieves true "zero-disturbance" interaction.

[0017] 2. Real-time response and intelligent scheduling: By constructing a system-level event monitoring framework with millisecond-level response, and combining it with a multi-level dynamic priority queue scheduling algorithm based on event type and urgency (e.g., incoming calls > messages > status indicators), it can intelligently handle concurrent multi-event scenarios; ensuring that high-priority and urgent information (e.g., incoming calls, alarms) can be displayed immediately and strongly, avoiding missing information; at the same time, ordinary information is queued or merged for display in an orderly manner, avoiding display conflicts and screen flickering, and achieving clear and orderly information flow management.

[0018] 3. Environmental Awareness and Intelligent Power Saving: By integrating data from sensors such as distance, gyroscope, and light sensor, the display behavior of the rear dot matrix screen becomes "environmentally aware." For example, it automatically turns off the screen or suppresses notification display when the phone is put in a pocket or turned upside down, and automatically reduces brightness and switches to a warm color tone in low-light environments. This not only makes the interaction more user-friendly and less abrupt, but also completely turns off the rear screen in scenarios where no display is needed, further reducing overall power consumption and improving the device's energy efficiency ratio and the "warmth" of the user experience. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating a method for controlling pixelated display of a mobile phone software / hardware interaction scenario on a back screen, according to an embodiment of the present invention. Figure 2 This is a system architecture block diagram provided in an embodiment of the present invention; Figure 3 This is a logical diagram of intelligent priority scheduling and conflict resolution provided in an embodiment of the present invention; Figure 4 This is a logical schematic diagram of an environment adaptive strategy provided in an embodiment of the present invention; Figure 5 This is a block diagram of a control device provided in an embodiment of the present invention; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention; Figure 7 This is a timing diagram example of a specific application scenario provided by an embodiment of the present invention. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be described in further detail below with reference to the accompanying drawings; obviously, the described embodiments are some embodiments of the present invention, but not all embodiments; generally, the components of the embodiments of the present invention described and shown in the accompanying drawings can be arranged and designed in various different configurations.

[0021] ( Example 1 )like Figure 1 As shown, Figure 1The flowchart of the control method for pixelated display on the back screen in a mobile phone software / hardware interaction scenario provided in this embodiment is illustrated. This method can be applied to mobile terminals such as smartphones and tablets with a back dot matrix screen. It is implemented by the processor in the terminal executing a stored computer program. The method includes the following steps: S101, Full-Dimensional Event Listening and Capture: The core of this step is to build a system-level, persistent guardian service, acting as the "sensory nerves" of the entire system, capturing all kinds of interactive events occurring inside and outside the phone without blind spots; combined with Figure 2 As shown, the event listener layer contains several sub-modules: 1) Notification Listener Module: This module inherits from the Android system's NotificationListenerService and overrides its onNotificationPosted(StatusBarNotification sbn) method. This method is called back when any application sends a notification. Internally, this module maintains a "whitelist" of applications (such as WeChat, QQ, DingTalk, SMS, phone, email clients, and other important applications that users care about). When a notification arrives, the module first checks if its package name (sbn.getPackageName()) is in the whitelist. If it is, it further parses the notification, extracting key information: the application package name (used for unique identification), the notification icon (sbn.getNotification().getSmallIcon()), and can selectively extract the notification title and content. For the "Phone" application, it can also mark it as an "important contact" by parsing additional information (such as contacts), giving it higher priority. Notifications from non-whitelisted applications can be selectively ignored or uniformly classified as "other notifications" to save resources.

[0022] 2) Hardware and System Status Monitoring Module: This module listens for system broadcasts by registering a BroadcastReceiver and setting the corresponding IntentFilter. The main broadcasts it listens for include: a) Intent.ACTION_POWER_CONNECTED / DISCONNECTED: Power connection / disconnection event; when connected, additional information such as BatteryManager.EXTRA_PLUGGED can be used to call the relevant interfaces of BatteryManager to determine whether the current charging is normal charging, fast charging (such as QC, PD protocol) or wireless charging, and to obtain the current battery percentage. b) BluetoothAdapter.ACTION_CONNECTION_STATE_CHANGED: Bluetooth connection status change event; c) Intent.ACTION_HEADSET_PLUG: Wired headphone plug / unplug event; d) AudioManager.ACTION_SCO_AUDIO_STATE_UPDATED or listening to specific voice assistant broadcasts (such as "android.intent.action.VOICE_COMMAND"): used to capture the wake-up state of voice assistants (such as Xiao Ai, Bixby); e) Intent.ACTION_SCREEN_ON / OFF: Screen on / off event, which can be used to help determine the context.

[0023] 3) Sensor Fusion Module: This module registers and monitors multiple sensors; for example, Sensor.TYPE_PROXIMITY (proximity sensor) is used to determine whether the phone is held close to the ear for a call or placed in a pocket / bag; another example is that Sensor.TYPE_ACCELEROMETER and Sensor.TYPE_GYROSCOPE (accelerometer and gyroscope) are combined to determine whether the phone is facing up, down, or in portrait or landscape mode through attitude calculation; yet another example is Sensor.TYPE_LIGHT (ambient light sensor) used to sense the brightness of the surrounding environment.

[0024] S102, Resource Matching and Pixelation Conversion: This step is entered after a valid event is captured in step S101; The system has a pre-set "System Status Icon Resource Library", which contains two types of resources: Vector / Bitmap Resources: pre-stores vector graphics of commonly used system statuses (such as Bluetooth, Wi-Fi, battery icon, NFC symbol, volume icon), as well as icon caches of whitelisted applications (which can be extracted from APK); Animation Templates: defines a series of simple frame animation sequences, such as breathing animation, blinking animation, progress fill animation, checkmark diffusion animation, etc.

[0025] 1) Matching process: Search the resource library according to the event type and the parameters carried (such as package name); for example, if a WeChat notification is detected, match the WeChat icon; if a fast charging connection is detected, match the "lightning bolt + battery" icon and a progress bar animation template for battery increase.

[0026] 2) Pixelation Conversion: Since the resolution of the rear dot matrix screen is usually low (e.g., 16x16, 32x32 pixels), the matched graphic resources need to be converted into an appropriate pixel array. This invention adopts an optimized "image to pixel map" algorithm. For icons, they are first scaled to the size of the dot matrix screen, and then binarized (black and white) or quantized with limited colors (e.g., 4 colors, 8 colors) to generate a two-dimensional color index array. For animations, this conversion is performed for each frame. For numerical information (e.g., battery 78%), a lightweight graphics rendering engine is dynamically called to draw a bitmap containing the number "78" or a progress bar with a length of 78% in memory, and then pixelation conversion is performed to finally generate the byte stream format required to drive the dot matrix screen (e.g., each pixel uses 2 bits to represent 4 colors).

[0027] S103, Intelligent Priority Scheduling and Conflict Resolution: This is the "decision-making brain" of the present invention, and its logic is as follows: Figure 3 As shown, the system internally defines a multi-level priority enumeration, for example (from high to low): P0_Emergency Interruption: SOS distress call, fire alarm, high-priority system alarm; P1_Call: Incoming call, video call request; P2_Timer: Alarm clock, important countdown; P3_Notification: Messages from whitelisted applications, email notifications; P4_Status Indicator: Bluetooth connection / disconnection, charging status, NFC card swipe success, voice assistant wake-up; P5_Standby: Time, date, personalized slogans and other constantly displayed information.

[0028] Meanwhile, the system maintains a priority queue (PriorityQueue); when a new event (Event_new) is ready to display data after step S102, the scheduler compares it with the currently displayed event (Event_current) as follows: 1) Preemption mechanism: If Event_new.priority > Event_current.priority, the display of Event_current is immediately interrupted (its animation breakpoint is saved for later resumption), and Event_new is set as the current display target, and its display data is immediately sent into the rendering process; for example, when the WeChat icon (P3) is being displayed, a call suddenly comes in (P1), the display of the WeChat icon stops immediately, and the back dot matrix screen switches to a full-screen flashing phone icon.

[0029] 2) Queuing mechanism: If Event_new.priority <= Event_current.priority, then Event_new is placed in the priority queue to wait; when Event_current has finished displaying (such as when a call is hung up) or its display time limit is reached, the scheduler takes the next event with the highest priority from the queue for display.

[0030] 3) Conflict resolution: a) Merged display: For multiple notifications of the same priority (such as WeChat group messages) that flood in within a short period of time (e.g., within 2 seconds), the scheduler merges them into a "message set" event and displays the application icons in turn on the dot matrix screen, or displays 2-3 small icons side by side when space allows; b) Carousel display: For multiple continuous states with the same priority (such as when Bluetooth headphones and smartwatches are connected at the same time), a time-sharing carousel method can be used to switch and display a status icon every few seconds.

[0031] S104, Environmental Adaptive Strategy Adjustment; such as Figure 4 As shown, before and after the decision in step S103, the system will refer to the environmental context provided by the sensor fusion module and make the following fine-tuning to the display strategy to make the interaction more intelligent and more power-efficient: 1) Anti-accidental touch / power saving strategy: If the proximity sensor detects that the phone is blocked (isInPocket = true), it will suppress the display of all notifications with a priority of P3 and below (the event will still be recorded, but the back dot matrix screen will not light up), and only P2 and above events (such as alarm clock, incoming call) will be allowed to be forcibly lit up; if the gyroscope detects that the phone screen is placed face down (isFaceDown = true), it can also suppress the display of most notifications to avoid light interference on the conference table.

[0032] 2) Visual comfort strategy: If the ambient light sensor detects that the ambient brightness is very low (isDark = true), the system will automatically adjust the display brightness to the lowest level and adjust the color mode to warm color (such as dark orange) during the rendering process of S105 to reduce the stimulation to the user's eyes.

[0033] 3) Interaction enhancement strategy: When the voice assistant is activated, in conjunction with gyroscope data, if the phone is picked up, a more vivid "sound wave" animation can be played; if the phone is laid flat, a simple microphone icon will be played.

[0034] S105, Pixelated Rendering and Driver Execution: Locate the local icon library based on packageName; if missing, call the system API to extract the APP icon and perform real-time pixelation; for numerical statuses (battery, volume), dynamically draw a progress bar; this step receives the final display instruction determined by the scheduler and parameters adjusted by the environment, and executes the specific graphics rendering; the rendering engine generates the final pixel data frame (Frame Buffer) based on the type of graphics resource (static icon, dynamic progress bar, frame animation) and the dot matrix screen's driver protocol; for example, for a 16x16 monochrome dot matrix screen, the rendering engine will generate an array of 32 bytes (16... 16 / 8); Subsequently, the execution module writes the pixel data frame to the frame buffer device node (such as / sys / class / backlight / back_pixel / fb) corresponding to the back dot matrix screen through the operating system kernel; at the same time, a timer is started for this display. If no higher priority event interrupts the display before the timeout (for example, notification display for 5 seconds, status display for 3 seconds), the dot matrix screen will be turned off or switched back to the P5 level standby animation (such as display time) after the timer expires.

[0035] Specific application scenario examples: For a better understanding of the above process, please refer to... Figure 7 Suppose a user's phone is placed on a table and they are listening to music through Bluetooth headphones. The dot matrix screen on the back of the phone displays the time (P5, standby mode).

[0036] At time T1: The user inserts a fast-charging charger; the hardware monitoring module captures the ACTION_POWER_CONNECTED broadcast and identifies it as a fast-charging protocol; the matching module finds the "lightning bolt + battery" icon and progress animation; this event is P4 (status indicator), with a priority no higher than the currently displayed P5; however, since P5 is a constantly displayed state, the scheduler decides to briefly display the charging status for 3 seconds in an "interrupted" manner; the dot matrix screen switches to the charging icon and the increasing battery bar animation, and automatically resumes the display time after 3 seconds.

[0037] At time T2 (charging in progress): A WeChat message is received; the notification listening module captures the WeChat notification, extracts the icon, and this event is designated as P3. Since P3 has a lower priority than the currently displayed P4, the scheduler puts the WeChat notification event into the priority queue to wait.

[0038] At time T3 (after charging ends and recovery time is displayed): The scheduler checks the queue and finds a WeChat notification event at the head of the queue, so the dot matrix screen switches to display the WeChat icon for 5 seconds.

[0039] At time T4 (2 seconds after the WeChat icon is displayed): A call suddenly comes in. The system captures the call broadcast with a priority of P1. The scheduler immediately executes the preemption mechanism, interrupts the display of the WeChat icon, and forces the dot matrix screen to flash the phone icon in full-screen mode with high brightness and high frequency to ensure that the user can notice it with their peripheral vision even when they are not near the phone.

[0040] At time T5: The user does not answer the call, the call is disconnected, the phone icon stops flashing, and the scheduler processes the interrupted WeChat event. Since the WeChat notification display is interrupted and its preset duration has not been completed, the scheduler can choose to continue displaying the remaining 3 seconds, then check the queue. If the queue is empty, the dot matrix screen returns the display time.

[0041] T6 moment: When the user places the phone face down on the table, the gyroscope data changes, and the environment adaptation module sets the isFaceDown flag to True. After that, all new P3 (notification) events will be suppressed (but the phone will still record the notifications) until the user picks up the phone again and the screen faces up, at which point the display will return to normal.

[0042] Through the above process, the entire system achieves a closed loop from event perception and intelligent decision-making to adaptive execution, and the rear dot matrix screen becomes an efficient, quiet, and intelligent secondary information screen.

[0043] ( Example 2 Based on the above method, this embodiment also discloses a modified scheme for biometric linkage. This embodiment expands the functionality of the sensor fusion module based on the architecture of Embodiment 1. In addition to basic sensors, this scheme can also connect to a heart rate sensor (such as PPG) or utilize the contact signal from a fingerprint reader. 1) Stress Detection and Emotional Soothing: When the system roughly determines that a user may be in a state of tension or stress by continuously monitoring heart rate variability (HRV) or combining it with accelerometer data (e.g., a persistently high heart rate accompanied by slight tremors), it can generate a special P4-level "emotional soothing" event. The rendering engine will match a soothing, slow breathing rhythm light effect animation (such as soft ripples spreading outward from the center) and display it on the back dot matrix screen. This provides the user with an unconscious, low-intrusion emotional care and enhances the device's emotional interaction experience.

[0044] 2) Personalized fingerprint unlock feedback: When a user successfully unlocks the phone using the rear or side fingerprint recognition module, this is a hardware interruption event. In this solution, it can be associated with the user's account. The rendering engine not only displays a simple "unlock successful" checkmark animation, but can also retrieve a personalized welcome message or pattern customized for the user (such as an animation of the first letter of the user's nickname) from the cloud or local storage and display it briefly on the dot matrix screen. This enhances the sense of ritual and personalized experience of the unlocking process.

[0045] ( Example 3 This embodiment discloses a variant scheme that links with automated workflows; modern mobile operating systems (such as iOS Shortcuts and Android Tasker) support automation scenarios. This embodiment uses the rear dot matrix screen as the visual execution feedback terminal for these automated tasks, mainly including: 1) Linkage Mechanism: The system's broadcast monitoring module can listen to specific custom broadcasts issued by automation applications; for example, a user sets up an automation scenario of "automatically turning on the lights when arriving home," triggered by the mobile phone connecting to the home's Wi-Fi. 2) Visual Feedback: When the mobile phone connects to the home Wi-Fi, in addition to the normal Wi-Fi connection status indication (P4), the automation application will also send a custom broadcast, such as "com.example.automation.HOME_MODE_ON". After the event listening layer of this invention captures the broadcast, it matches a special "house + light" icon animation and displays it on the dot matrix screen with P4 priority for 2-3 seconds. The text prompt can be simplified to "Home". This provides users with clear and visual confirmation that the preset automation task has been successfully triggered and executed, enhancing the user's confidence in the control of smart home.

[0046] ( Example 4 This embodiment discloses a variation of a cross-device state synchronization scheme. This embodiment expands the scope of event listening, making it not limited to local events, for example: 1) Cloud / LAN synchronization channel: Add a network synchronization module to the control device on the mobile phone (local device). This module establishes a low-power status synchronization channel with the user's smartwatch, tablet, personal computer and other certified devices through Bluetooth, Wi-Fi LAN or cloud server.

[0047] 2) Remote event forwarding and display: When a user's smartwatch receives an important message (such as a message from a designated contact), or when a user's computer email client receives an email marked "urgent", the device will encapsulate this event into a standard remote event message through a synchronization channel and send it to the user's mobile phone.

[0048] 3) Local processing and display: After receiving this remote event, the network synchronization module on the mobile phone parses it into an event format that the local scheduler can recognize (e.g., event type: remote notification, source: PC email, priority: P3). The subsequent matching, scheduling, and rendering processes are exactly the same as those for processing local events. For example, a flashing animation of a computer or email icon will be displayed on the dot matrix screen. In this way, no matter which device the user is using, as long as the mobile phone is nearby, the key status of all devices can be uniformly perceived through the dot matrix screen on the back of the phone, thus building a seamless cross-device status awareness network.

[0049] It should be noted that the above embodiments can be implemented individually or in combination without conflict, and those skilled in the art can choose according to actual needs.

[0050] ( Example 5 )like Figure 5 As shown, Figure 5 This illustration shows a block diagram of a control device 500 for a pixelated display of a mobile phone's software / hardware interaction scenario on a rear screen, as provided in this embodiment. This device can be a software function module within a mobile terminal such as a mobile phone, or it can be implemented through hardware or a combination of hardware and software. The device 500 includes: The listening module 501 is used to perform the event listening and capturing function as described in step S101; Matching module 502 is used to perform the resource matching and pixelation conversion functions as described in step S102; The scheduling module 503 is used to perform the intelligent priority scheduling and conflict resolution functions as described in step S103; Rendering module 504 is used to perform the pixelation rendering function as described in step S105; Execution module 505 is used to perform the drive execution function as described in step S105; An environment adaptation module 506 (optional) is used to perform the environment adaptation strategy adjustment function as described in S104.

[0051] The specific working principles and interaction processes of each module in the device 500 have been described in detail in the above method embodiments, and will not be repeated here.

[0052] ( Example 6 )like Figure 6 As shown, Figure 6This diagram illustrates the structure of an electronic device 600 provided in this embodiment. The electronic device 600 can be a smartphone, tablet computer, etc. The electronic device 600 includes at least one processor 601, a memory 602, and a computer program 603 stored in the memory 602 and executable on at least one processor 601. When the processor 601 executes the computer program 603, it implements the steps in any of the above method embodiments. The electronic device 600 may also include a rear dot matrix screen 604, various sensors 605, a communication interface 606, etc. The memory 602 can be used to store the computer program 603, an icon resource library, priority configuration, etc. The memory 602 can be an internal storage unit of the device, such as a hard disk or memory, or it can be an external storage device of the device, such as a plug-in hard disk, a smart memory card, a secure digital card, etc.

[0053] It will be understood by those skilled in the art that Figure 6 This is merely an example of electronic device 600 and does not constitute a limitation on electronic device 600. Electronic device 600 may include more or fewer components than shown, or combine certain components, or use different components.

[0054] It should be noted that the above-described embodiments of the apparatus and equipment correspond to the method embodiments, and their specific implementation details and beneficial effects are similar to those of the method embodiments, and will not be repeated here.

[0055] It should be understood that the above description is only a preferred embodiment of the present invention and is not sufficient to limit the technical solution of the present invention. For those skilled in the art, within the spirit and principles of the present invention, additions, subtractions, substitutions, transformations or improvements can be made based on the above description, and all such additions, subtractions, substitutions or improvements should fall within the protection scope of the appended claims of the present invention.

Claims

1. A method for controlling pixelated display on a mobile phone software / hardware interaction scenario, characterized in that, include: Monitoring steps: Monitor at least one software or hardware event on the mobile terminal through system-level services; The software and hardware events include at least one of software notification events, system broadcast events, hardware interrupt events, and sensor events; Matching step: In response to the detection of a target software or hardware event, match the graphics resource corresponding to the target software or hardware event from the preset resource library; Scheduling steps: Based on preset priority rules, the target software and hardware events are scheduled and processed to determine the target events that should be displayed on the back dot matrix screen of the mobile terminal. Rendering step: Based on the processing result of the scheduling step, the graphic resources corresponding to the target event are converted into pixelated display data adapted to the resolution of the rear dot matrix screen; Execution steps: The pixelated display data is sent to the driver layer of the rear dot matrix screen for display.

2. The method for controlling pixelated display on the back screen in a mobile phone software / hardware interaction scenario according to claim 1, characterized in that, The monitoring steps specifically include: By inheriting the notification listening service and overriding the notification publishing callback method, we can listen for and filter notification events of a specified application to extract the application identifier and icon. By registering a broadcast receiver and setting an intent filter, the system broadcast events are monitored, including at least power connection events and Bluetooth connection status change events. By registering a sensor listener, you can monitor sensor data from at least one of the following: a distance sensor, a gyroscope sensor, and an ambient light sensor.

3. The method for controlling pixelated display on the back screen in a mobile phone software / hardware interaction scenario according to claim 1 or 2, characterized in that, The scheduling steps include: Maintain a queue sorted by event priority; When a new event is detected, its priority is compared with the priority of the currently displayed event; If the priority of the new event is higher than the priority of the currently displayed event, then the current display is interrupted, and the new event is identified as the target event; If the priority of the new event is not higher than the priority of the currently displayed event, then the new event is added to the queue for waiting.

4. The method for controlling pixelated display on the back screen in a mobile phone software / hardware interaction scenario according to claim 3, characterized in that, The scheduling steps also include conflict resolution strategies: When there are multiple events with the same priority to be displayed, a carousel strategy is adopted to alternately display the graphics corresponding to each event on the rear dot matrix screen in a time-sharing manner; or, The graphic resources corresponding to the multiple events to be displayed with the same priority are combined to generate a composite graphic for display in the same frame.

5. The method for controlling pixelated display on the back screen in a mobile phone software / hardware interaction scenario according to claim 1, characterized in that, It also includes environmental adaptation steps: The current environmental context information of the mobile terminal is obtained, and the environmental context information is determined based on data from at least one of the distance sensor, gyroscope sensor, and ambient light sensor. Based on the environmental context information, adjust the display parameters of the pixelated display data generated in the rendering step, or control whether the execution step performs the display. The display parameters include at least one of brightness, color, and display duration.

6. The method for controlling pixelated display on the back screen in a mobile phone software / hardware interaction scenario according to claim 5, characterized in that, The step of controlling whether to execute the display based on environmental context information includes: When it is determined based on distance sensor data that the mobile terminal is in an obstructed state, and / or When the screen orientation of the mobile terminal is determined to be downward based on gyroscope data, the display of events with a priority lower than a preset threshold on the rear dot matrix screen is suppressed.

7. The method for controlling pixelated display on the back screen in a mobile phone software / hardware interaction scenario according to claim 1, characterized in that, The hardware and software events monitored in the monitoring step also include remote status events from other smart devices connected to the mobile terminal via a network; in the matching step, corresponding graphic resources are matched for the remote status events.

8. The method for controlling pixelated display on the back screen in a mobile phone software / hardware interaction scenario according to claim 1, characterized in that, The software and hardware events include automation task triggering events associated with automation task applications running on the mobile terminal; In the matching step, different identifier graphic resources are matched for different automated task trigger events.

9. A control device for pixelated display of a mobile phone software / hardware interaction scenario on the back screen, characterized in that, include: The listening module is used to listen for at least one software or hardware event on the mobile terminal through system-level services. The matching module is used to match the graphics resources corresponding to the target software and hardware event from a preset resource library in response to the detection of the target software and hardware event. The scheduling module is used to schedule the target software and hardware events based on preset priority rules in order to determine the target events that should be displayed on the dot matrix screen on the back of the mobile terminal. The rendering module is used to convert the graphic resources corresponding to the target event into pixelated display data adapted to the resolution of the rear dot matrix screen, based on the processing result of the scheduling module. The execution module is used to send the pixelated display data to the driver layer of the rear dot matrix screen for display.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the control method for pixelated display of mobile phone software / hardware interaction scenarios on the back screen as described in any one of claims 1 to 8.

Images