IPTV (Internet Protocol Television) set top box distribution network debugging and testing method, system, equipment and medium

Abstract

The invention discloses an IPTV (Internet Protocol Television) set top box distribution network commissioning and testing method, system and device and a medium, and relates to the technical field of set top box commissioning and testing. The invention provides an IPTV (Internet Protocol Television) set top box distribution network debugging and testing method, which comprises the following steps of: connecting target equipment with a set top box through a physical interface, acquiring equipment information of the target equipment, and judging whether the target equipment is authorized debugging equipment or not; if the target equipment is authorized debugging equipment, activating a debugging mode; reading a pre-generated readable debugging code through the target equipment, and converting the debugging code into a standard input event; a system input manager of the set top box monitors a standard input event in real time, and when the source of the standard input event is authorized debugging equipment, the standard input event is intercepted; and comparing the standard input event with a preset instruction, and outputting an execution operation strategy according to a comparison result.

Description

Technical Field

[0001] The present application relates to the technical field of set-top box commissioning, and in particular to an IPTV set-top box network configuration commissioning method, system, device, and medium. Background Art

[0002] An IPTV (interactive Internet Television) set-top box (STB) transmits television signals over a carrier's private network. During the commissioning and production stages, IPTV STBs require commissioning features. These features typically require the use of tools like adb, telnet, and ssh. These features open corresponding ports on the device to await connections from the console. However, opening these ports on all devices poses security risks and prevents them from passing port scan tests. Therefore, these features are always disabled by default.

[0003] At the same time, in the production process, some equipment needs to connect to Wi-Fi for function or throughput testing, which requires the equipment to have a convenient Wi-Fi connection function. Otherwise, Wi-Fi connection can only be performed through the remote control, which is too inefficient. Summary of the Invention

[0004] The main purpose of this application is to provide an IPTV set-top box network configuration and debugging method, system, equipment and medium, aiming to solve the technical problem in the existing technology that the IPTV set-top box operates the device through a special network method to open the device debugging port (such as a network backdoor), which poses a security risk.

[0005] To achieve the above objectives, in a first aspect, the present application provides an IPTV set-top box network configuration and commissioning method, comprising: The target device is connected to the set-top box through a physical interface, the device information of the target device is obtained, and whether the target device is an authorized debugging device is determined; If the target device is an authorized debugging device, activating the debugging mode; Reading pre-generated readable debugging code through the target device and converting the debugging code into a standard input event; The system input manager of the set-top box monitors standard input events in real time, and intercepts the standard input events when the source of the standard input events is an authorized debugging device; The standard input event is compared with the preset instruction, and an execution operation strategy is output based on the comparison result.

[0006] Optionally, the target device is connected to a set-top box via a physical interface, and the step of obtaining device information of the target device and determining whether the target device is an authorized debugging device includes: When the target device is connected to the set-top box through a physical interface, the set-top box obtains device information of the target device through a kernel driver, wherein the device information includes at least one of a manufacturer label, a product label, and a device serial number. Verify the device information by matching it with the preset authorized device whitelist to obtain the verification result; If the verification is successful, the target device is marked as an authorized debugging device; If the verification fails, the target device is prohibited from triggering the debugging mode.

[0007] Optionally, if the target device is an authorized debugging device, the step of activating the debugging mode includes: When detecting that the target device is marked as an authorized debugging device, activating a debugging instruction monitoring service of the set-top box; When the debugging instruction monitoring service is started, the debugging port is kept in a default closed state.

[0008] Optionally, the system input manager of the set-top box monitors standard input events in real time, and when the source of the standard input event is an authorized debugging device, the step of intercepting the standard input event includes: If the device information of the source of the standard input event is consistent with the device information of the authorized debugging device, intercepting the standard input event and preventing it from being passed to the upper layer application; If they are inconsistent, the standard input event is dispatched to the currently focused application.

[0009] Optionally, the step of comparing the standard input event with a preset instruction and outputting an execution operation strategy based on the comparison result includes: Reassemble the intercepted standard input events into character sequences to generate the original debugging instruction string; Parsing the original debugging instruction string according to preset instruction grammar rules to obtain a parsing result; Compare the parsing result with the preset instruction to determine whether the original debugging instruction string matches the preset instruction; If so, perform the preset operation type; If not, the original debugging instruction string is discarded and the parsing state is reset.

[0010] Optionally, if yes, then performing the steps of a preset operation type includes: When the network configuration command is recognized, the preset wireless network SSID and encryption key are automatically extracted, and the system network management interface is called to connect to the wireless network; When a debug port control instruction is recognized, the corresponding debug service process is dynamically started and the preset port is opened; When a test script calling instruction is recognized, the automated test script is called.

[0011] Optionally, the step of comparing the standard input event with a preset instruction and outputting an execution operation strategy based on the comparison result includes: After completing the execution of the operation strategy, remove the target device, close the opened debugging port, and terminate the debugging service process; The original debug command string is cleared and the debug command listening service is disabled.

[0012] In a second aspect, the present application provides an IPTV set-top box network configuration and debugging system, comprising: A debugging device determination module is configured to connect a target device to a set-top box via a physical interface, obtain device information of the target device, and determine whether the target device is an authorized debugging device; a debugging mode activation module configured to activate the debugging mode if the target device is an authorized debugging device; a standard input event acquisition module configured to read pre-generated readable debugging codes through the target device and convert the debugging codes into standard input events; An event interception module is configured as a system input manager of the set-top box to monitor standard input events in real time, and intercept the standard input events when the source of the standard input events is an authorized debugging device; The execution module is configured to compare the standard input event with the preset instruction and output an execution operation strategy according to the comparison result.

[0013] In a third aspect, the present application provides a device comprising a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above method.

[0014] In a fourth aspect, the present application provides a storage medium having a computer program stored thereon, and a processor executes the computer program to implement the above-mentioned method.

[0015] Beneficial effects that this application can achieve: The embodiment of the present application proposes an IPTV set-top box network configuration and debugging method, system, device and medium, including: a target device is connected to the set-top box through a physical interface, the device information of the target device is obtained, and whether the target device is an authorized debugging device is determined; if the target device is an authorized debugging device, the debugging mode is activated; a pre-generated readable debugging code is read through the target device, and the debugging code is converted into a standard input event; the system input manager of the set-top box monitors the standard input event in real time, and when the source of the standard input event is an authorized debugging device, the standard input event is intercepted; the standard input event is compared with a preset instruction, and an execution operation strategy is output based on the comparison result. Verifying whether the target device is an authorized debugging device through a physical interface avoids the possibility of opening the debugging port on a large scale through the network, and prevents illegal devices from tampering with the network configuration or implanting malicious code. The double verification mechanism is triggered by physical device binding and instructions, which significantly reduces the risk of malicious code injection and enhances the system's anti-attack capability. The debugging mode is activated only when an authorized device is connected, ensuring that the debugging operation is in a controlled environment, preventing the debugging function from being accidentally triggered in the production environment and causing business interruption, and improving the stability of the system operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A flow chart of a distribution network commissioning method according to an embodiment of the present application; Figure 2 This is a flow chart of the input device identification part of an embodiment of the present application; Figure 3 This is a flowchart of the set-top box network configuration and commissioning function according to an embodiment of the present application.

[0017] The realization of the objectives, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0018] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0019] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative position relationship, movement status, etc. between the various components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0020] In the present invention, unless otherwise specified or limited, the terms "connection" and "fixation" should be understood in a broad sense. For example, "fixation" can mean fixed connection, detachable connection, or integration; mechanical connection or electrical connection; direct connection or indirect connection through an intermediate medium; internal communication between two elements or interaction between two elements, unless otherwise specified. Those skilled in the art will be able to understand the specific meanings of the above terms in the present invention based on specific circumstances.

[0021] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present invention, the descriptions of "first", "second", etc. are only for descriptive purposes and cannot be understood as indicating or suggesting their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of such features. In addition, the meaning of "and / or" appearing throughout the text includes three parallel schemes. Taking "A and / or B" as an example, it includes scheme A, or scheme B, or a scheme in which A and B are satisfied at the same time. In addition, the technical solutions between the various embodiments can be combined with each other, but it must be based on the ability of ordinary technicians in this field to implement. When the combination of technical solutions is mutually contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0022] In existing technology, an IPTV set-top box (STB) is a terminal device that receives and decodes audio and video streams over the Internet Protocol (IP) network, converting digital signals into content playable on a television. It supports interactive TV services such as live streaming, on-demand viewing, and playback. IPTV set-top boxes require commissioning features during the commissioning phase or production process. These features typically require the use of tools like ADB, Telnet, and SSH. These features open corresponding ports on the device to await connections from the console. However, directly opening these ports on all devices poses security risks and prevents port scanning tests. Therefore, these features are typically disabled by default. At the same time, during production, devices often connect to Wi-Fi for functional or throughput testing, requiring convenient Wi-Fi connectivity. Otherwise, Wi-Fi connection can only be performed using a remote control, which is inefficient.

[0023] The reasons for these issues are: some scenarios and personnel require open debugging ports, and production test environments require fast wireless network connections. However, it is impossible to directly open the debugging ports and quickly connect to Wi-Fi networks, creating a conflict between these requirements and security controls.

[0024] If the debugging port of the set-top box is opened by operating the device through special network methods (such as a network backdoor), there will be security risks (such as sending special data through Ethernet, Layer 2, etc.). Since the operation is performed over the network, this security risk cannot be controlled. When there are many set-top boxes in the same scenario, the impact is greater, and the danger level of the set-top box spreads faster through the network.

[0025] Therefore, the present application provides a method for control that is not based on the network, which has high security. The debugging equipment used is at the user end, and the impact will only be on a single set-top box at most, and will not spread through the network.

[0026] Furthermore, on Android, input characters are only delivered to the top-level active window. If the app is in the background, the app cannot receive the characters. Therefore, it is necessary to solve the problem of the program processing the received control characters, and thus solve the problem of the program being able to receive data in all circumstances.

[0027] Example 1 Reference Figure 1 The first embodiment of the present application provides an IPTV set-top box network configuration and debugging method, including the following steps: S10: The target device is connected to the set-top box via a physical interface, device information of the target device is obtained, and it is determined whether the target device is an authorized debugging device.

[0028] Optionally, the target device can establish a physical connection to the set-top box via a USB interface. The interface type is predefined in the system driver layer as a dedicated debugging port. Read the target device's hardware identifiers, such as the vendor table identifier, product identifier, and device name. Obtain the device descriptor (via libusb or the HID API) and extract the firmware version number and serial number. Match the collected device information with the list of authorized devices pre-set in the set-top box's secure storage area (such as / etc / debug_devices.conf). If a match is successful, a temporary session token is generated. The temporary session token can be set to a validity period, such as 30 minutes, marking the target device as an authorized debugging device. If the match is unsuccessful, a system log alarm is triggered (recording the device information and access time), and debugging function activation is prohibited. If an unauthorized device is accessed three times in a row, the debugging interface will be locked for one hour to prevent brute force attacks.

[0029] S20: If the target device is an authorized debugging device, activate the debugging mode.

[0030] Optionally, a background down payment process is started to listen for command input from authorized devices, keeping the adb / telnet / SSH ports closed by default. After activating debug mode, a preset command parsing library (such as a regular expression rule set) is loaded, and the WiFi connection manager and debug service controller are initialized. Privilege isolation is implemented, with debug mode running only at the system level, isolated from application-layer processes to prevent privilege escalation attacks.

[0031] S30: Read the pre-generated readable debugging code through the target device, and convert the debugging code into a standard input event.

[0032] Optionally, the readable debug code can be a one-dimensional barcode or a two-dimensional code. The target device can be a barcode scanner. The target device simulates HID keyboard input, converts the barcode content into a key event stream, and sets a debounce delay in the target device firmware, such as 100ms, to avoid character sticking caused by rapid barcode scanning. S40: The system input manager of the set-top box monitors standard input events in real time, and intercepts the standard input events when the source of the standard input events is an authorized debugging device.

[0033] Optionally, register an InputDeviceListener with the Input Manager (PhoneWindowManager) at the Android framework level to capture input device change events in real time. Create a hash table to record the identifiers of currently connected input devices, such as / dev / input / event3. Compare the device ID of the input event with the authorized device identifier mDeviceA. Allocate a separate memory buffer, mCtrlArray, to store intercepted keystrokes. Clear the buffer and generate an alarm if the limit is exceeded.

[0034] S50: Compare the standard input event with the preset instruction, and output an execution operation strategy based on the comparison result.

[0035] Optionally, the intercepted input event stream is ASCII-decoded to generate the original instruction string. This instruction string is then matched against the instruction template in the configuration file using a regular expression. Dynamic policies are executed based on the matching results. After the operation is completed, the security recovery process is executed.

[0036] Based on these operations, network attack surfaces exposed by default-open high-risk ports (such as port scanning and unauthorized access) are avoided. A dual authentication mechanism, through physical device binding and command triggering, significantly reduces the risk of malicious code injection. Complying with industry security testing standards (such as ISO 27001), ensures device compliance with port scanning penetration tests. Hardware-level authentication prevents pure software-based phishing attacks (such as forged input signals or remote commands), ensuring that debugging functions are triggered only by production-line-specific devices. The debug port is automatically closed and its status cleared upon device removal, eliminating the risk of residual debugging functionality. Pre-coded codes are automatically parsed and connected to Wi-Fi, replacing the traditional manual entry of SSID / password via a remote control. Complex parameter configuration can be completed with a single scan. Batch processing is supported (such as concurrently scanning multiple devices on a production line), preventing misconfiguration and data inconsistencies caused by manual input. The system input manager intercepts input events from authorized devices and prevents them from being passed to foreground applications. This prevents conflicts between debug commands and user operations (such as remote control button presses), preventing inadvertent application malfunctions. This ensures that foreground applications (such as IPTV players) are not disrupted by the debugging process. This system only responds to valid commands that conform to pre-set syntax (such as colon-delimited structures) and automatically discards invalid commands. This prevents invalid or malicious input from causing system crashes (such as buffer overflow attacks), improving robustness. Format verification reduces the probability of incorrect operations and ensures traceability of debugging operations. It reuses existing physical interfaces (USB) and barcode scanning devices (e.g., scanners already in production lines). This eliminates the need to develop dedicated debugging hardware, reducing production equipment procurement costs. Compatible with mainstream barcode scanning protocols (such as HID keyboard emulation), eliminating the need for custom driver development. Events are intercepted by the Android system input manager (PhoneWindowManager), eliminating the need to modify application code. It adapts to custom ROMs from different manufacturers, avoiding compatibility issues caused by system fragmentation. Debugging is decoupled from business logic, ensuring a seamless user experience. Network configuration and commissioning are independent of the application app and can be performed in the background using this method in any application without impacting existing services.

[0037] It should be noted that the set-top box can collaborate with the converged gateway to achieve intelligent device management, network optimization, or data interoperability. Optionally, connect the set-top box and the converged gateway to the same local area network (LAN), such as the same router. Ensure that the set-top box supports the IP protocol and discover and bind the converged gateway through the API or UPnP protocol. If the set-top box hardware supports protocol extensions, it is necessary to reduce the number of independent gateway devices. Connect a protocol converter, such as the Zigbee adapter ConBee II, via the USB interface and install the driver. At this time, the Linux system needs to load the kernel module and install an open source gateway service, such as Zigbee2MQTT, on the set-top box. Configure the MQTT protocol to forward device data to the set-top box or the cloud.

[0038] Example 2 Based on Example 1, this embodiment provides an IPTV set-top box network configuration and commissioning method, including the following steps: S10: The target device is connected to the set-top box via a physical interface, device information of the target device is obtained, and it is determined whether the target device is an authorized debugging device.

[0039] Optionally, the target device is connected to a set-top box via a physical interface, the device information of the target device is obtained, and the step of determining whether the target device is an authorized debugging device includes: S101: When the target device is connected to a set-top box via a physical interface, the set-top box obtains device information of the target device via a kernel driver, where the device information includes at least one of a manufacturer label, a product label, and a device serial number; Specifically, the physical interface is a USB 2.0 / 3.0 Type-A interface with a data transmission function, and a kernel-level usb_device_attach event is triggered when a target device is inserted.

[0040] The Linux kernel of the set-top box calls the libudev library to perform the following operations: (1) Get the device capability set through ioctl(USBDEVFS_GET_CAPABILITIES); (2) Parse the device descriptor and extract the following key fields: Manufacturer ID (VID): 16-bit hexadecimal value (e.g. 0x1234) Product ID (PID): 16-bit hexadecimal value (e.g. 0x5678) Device serial number: 64-bit ASCII string (stored in the iSerialNumber field) Interface protocol class (interface_class): distinguishes device types such as HID / Mass Storage; (3) Generate a device node with an encrypted signature under the / sys / bus / usb / devices / path.

[0041] S102: Verify the device information by matching it with a preset authorized device whitelist to obtain a verification result; Specifically, the authorized device whitelist is stored in a secure element or a trusted execution environment, using a tamper-resistant structure, and includes: A SHA-3 hash chain of the VID-PID combination of the pre-registered device; A list of legitimate device serial numbers signed with RSA-2048; Device authorization validity period timestamp (Unix epoch format).

[0042] A multi-level verification strategy is adopted; primary verification: calling the dm-verity module to verify whether the device basic identifier exists in the whitelist hash chain; deep verification: digital signature verification of the device serial number, using the public key certificate preset in the TEE to perform PKCS#1 v2.2 verification; time verification: comparing the current system time with the authorization validity period, and rejecting authentication requests from expired devices.

[0043] S103: If the verification is successful, the target device is marked as an authorized debugging device; Specifically, after verification, the kernel security subsystem performs: Create a character device node in / dev / debug_auth and set the access permission to 600; Write a timestamped authentication success record to the system log (syslog), including the HMAC-SHA256 value of the device fingerprint; Sends the USB_DEBUG_AUTH event to the user space daemon via the netlink socket to trigger the initialization of the debugging service.

[0044] S104: If the verification fails, prohibiting the target device from triggering the debugging mode.

[0045] Specifically, a defensive sequence of actions is performed: (1) Forcefully uninstall the USB driver module of the target device (execute modprobe -r usbhid); (2) Record the abnormal device details in / var / log / usb_audit.log, including: The captured raw descriptor data; Failed verification stage indicator; The physical port location of the device; (3) Activate the port locking mechanism: Run the command echo 0> / sys / bus / usb / devices / portX / power / level to power off the USB port where the abnormal device is located. Set the port cooling period to prohibit re-enumeration of devices within 300 seconds; (4) When the cumulative number of failures exceeds the threshold (e.g. 5 times), a system-level security alarm is triggered: Send SNMP trap alarms to remote management platforms; Error code E19 is displayed on the device LED panel.

[0046] Based on the above technical solution, the USB Type-A interface type is limited to eliminate wireless connections. A kernel-level event triggering mechanism ensures real-time detection, and device node cryptographic signatures prevent forgery. Whitelists are stored in the secure TEE environment to defend against physical attacks, and a device authorization validity period mechanism is introduced to implement temporary permission management. Port-level power-off control ensures physical isolation, a cooldown period prevents brute force cracking attempts, and security logs contain device fingerprint HMAC values ​​to ensure log tamper-proofing. Trusted verification is implemented by integrating the Linux kernel module (dm-verity), using netlink for kernel-userspace communication, and hardware power management is controlled through the sysfs interface.

[0047] S20: If the target device is an authorized debugging device, activate the debugging mode.

[0048] If the target device is an authorized debugging device, the step of activating the debugging mode includes: S201: When detecting that the target device is marked as an authorized debugging device, activating a debugging instruction monitoring service of the set-top box; Specifically, after the system detects the authorized device tag, it performs an environmental safety check: confirming that the current operating mode is factory test mode or after-sales maintenance mode (not normal user mode). It also verifies that system resource utilization (CPU / memory) is below the safety threshold to avoid resource conflicts that may cause service instability.

[0049] Load the debug communication protocol driver module (e.g., debug_comm.ko) and create a virtual character device / dev / debug_channel for command transmission. Start the debug_listener daemon, bind it to the local loopback address (127.0.0.1), and listen on the internal command pipeline. Assign the debug_listener process a dedicated Linux user group (e.g., debuggrp) to restrict its access to only debugging-related resources. Generate a temporary session key pair (RSA 2048). The public key is pre-installed on the authorized device, and the private key is stored in the set-top box's secure element (SE / TEE). Enable an encrypted communication channel, and all command transmissions are encrypted using the TLS 1.3 protocol to prevent man-in-the-middle attacks.

[0050] S202: When the debugging instruction monitoring service is started, the debugging port is kept in a default closed state.

[0051] Specifically, during initialization, set the adb / telnet / SSH ports to DROP status through firewall rules (such as iptables / nftables), denying all external connection requests. Disable the debug service's automatic startup in the system service configuration (e.g., systemctl mask adbd.service). When the debug_listener receives a valid debug command (e.g., adb:open:5555), modify the firewall rules to allow only specific IP addresses (e.g., the production line control terminal) to access the designated port. Dynamically start the debug service process (e.g., adbd) and restrict its bound IP address to an intranet address (e.g., 192.168.0.100). Set a countdown timer (e.g., 30 minutes) for each enabled debug port; upon the timeout, automatically terminate the debug service process. Restore the default firewall rules (reset the port status to DROP). Force-close all debug ports when the device restarts to prevent residual status.

[0052] S30: Read the pre-generated readable debugging code through the target device, and convert the debugging code into a standard input event.

[0053] S40: The system input manager of the set-top box monitors standard input events in real time, and intercepts the standard input events when the source of the standard input events is an authorized debugging device.

[0054] Optionally, the system input manager of the set-top box monitors standard input events in real time, and when the source of the standard input event is an authorized debugging device, the step of intercepting the standard input event includes: S401: If the device information of the source of the standard input event is consistent with the device information of the authorized debugging device, intercept the standard input event and prevent it from being delivered to the upper layer application; Specifically, the system input manager maintains a dynamic device list, recording each input device's unique identifier (such as the / dev / input / eventX path, bus-id, and vendor-product combination). When an input event arrives, the device ID field in the event header is extracted and matched against the authorized debug device identifier (mDeviceA). The device's vendor ID (VID) and product ID (PID) are checked for consistency with whitelist entries. For high-security scenarios, the device firmware hash or digital certificate is verified (requires the device to support Secure Boot).

[0055] In the Android framework's InputManagerService, register an InputFilter callback function to intercept the raw input stream before event delivery. If the event originates from an authorized device, call the filterInputEvent() method to mark the event with FLAG_INTERCEPTED, preventing it from being passed to the application layer. Create a circular buffer, mEventBuffer, to store intercepted input events (such as key codes, scan codes, and timestamps). When the buffer is full, an overwrite warning is triggered and the oldest event is discarded (to prevent memory overflow attacks). Intercepted event data is stored in kernel memory (a kfifo structure) to prevent tampering by userspace processes. An incremental sequence number is added to each event to prevent duplicate or out-of-order events from being processed.

[0056] S402: If not consistent, the standard input event is distributed to the current focus application.

[0057] Specifically, the input manager calls the dispatchUnfilteredInputEvent() method if the device ID does not match an authorized identifier. The event is routed to the currently active application (such as the IPTV player or settings menu) based on system default policies (such as focus window priority). The input device VID / PID tampering is monitored (for example, by periodically scanning with the lsusb command). If an anomaly is detected, a security alert is triggered and the device is disconnected.

[0058] Through precise device identifier matching and kernel-mode buffer management, authorized debugging instructions are seamlessly isolated from user operations, preventing system malfunctions caused by misinterpretation. Unauthorized device events utilize a bypass mechanism, with distribution latency controlled to milliseconds (<5ms), ensuring seamless user interaction.

[0059] S50: Compare the standard input event with the preset instruction, and output an execution operation strategy based on the comparison result.

[0060] Optionally, the step of comparing the standard input event with a preset instruction and outputting an execution operation strategy based on the comparison result includes: S501, reorganizing the character sequence of the intercepted standard input event to generate an original debugging instruction string; Specifically, the intercepted raw input events are converted into ASCII character sequences. A sliding time window (200±50ms) is established based on the input event timestamps to dynamically splice continuously input character events. A 200ms timeout detection mechanism is set in PhoneWindowManager - if the interval between consecutive inputs exceeds 200ms, it is considered that a single command input has ended. The target device scans the readable debug code and converts the code into a virtual keyboard key sequence. For example: scan adb:open:5555 → output key stream: adb:open:55555 [Enter].

[0061] S502, parsing the original debugging instruction string according to preset instruction grammar rules to obtain a parsing result; Specifically, the command syntax format can be: operation type: parameter 1: parameter 2. For example, a valid command is: wifi:Lab_5G:Password123; an illegal command is: wifiLab_5G (missing separators). Commands are categorized by command type identifier (e.g., adb:, wifi:). Key-value pair parsing is used, with colons (:) used as separators to extract parameter segments (e.g., wifi:ssid:psk is split into {type:wifi, ssid:xxx, psk:yyy}).

[0062] Verify instruction integrity, including: The number of parameter segments must match (e.g., adb:open requires 2 segments, wifi:ssid:psk requires 3 segments); Parameter length limit (SSID ≤ 32 bytes, PSK ≥ 8 bytes); Reserved field compliance (disallow use of system reserved keywords).

[0063] S503, comparing the parsing result with the preset instruction to determine whether the original debugging instruction string matches the preset instruction; Specifically, the reconstructed string is matched against the pre-stored instruction library for full words (eg, adb:open corresponds to opening the ADB service).

[0064] For commands containing dynamic parameters (such as wifi:ssid:psk), execute: SSID validity check (compliant with IEEE 802.11 naming standards); PSK strength verification (contains at least a combination of numbers, letters, and special characters); Parameter whitelist filtering (disallowing the use of default factory credentials).

[0065] Add digital signature verification to sensitive instructions (such as port control) and use the RSA public key preset in the secure storage area to verify the legitimacy of the instruction source.

[0066] S504: If the original debugging instruction character string matches a preset instruction, then execute a preset operation type; Optionally, the steps of performing a preset operation type include: S5041. When a network configuration instruction is recognized, the preset wireless network SSID and encryption key are automatically extracted, and the system network management interface is called to connect to the wireless network; Specifically, the preset wireless network credentials are extracted from the encrypted security zone, and the wpa_supplicant service is called through the DBus interface; the 5GHz band is prioritized for connection establishment, and if the signal strength is lower than -70dBm, it automatically falls back to the 2.4GHz band; a three-level connectivity check (ARP detection → ICMP Ping → HTTP access test) is performed, and the system network status flag is updated after all passes.

[0067] S5042: When a debug port control instruction is identified, dynamically start the corresponding debug service process and open the preset port; Specifically, a socket activation mechanism is adopted to start the debugging service process (such as adbd) only when a legitimate connection request is detected; a source IP whitelist is bound in the firewall rules (only pre-registered debugging terminal IPs are allowed to access); a unique token is generated for each debugging session, and the session is terminated immediately if the token expires or an abnormal operation is performed.

[0068] S5043. When a test script calling instruction is identified, the automated test script is called.

[0069] Specifically, the test script is loaded in a temporary namespace to isolate the impact on the main system configuration; CPU / memory usage thresholds are set (such as CPU ≤ 80%, memory ≤ 512MB), and script termination is triggered when the limit is exceeded; temporary files and memory cache in the / tmp partition are automatically cleared after the script is completed.

[0070] S505: If the original debugging instruction string does not match the preset instruction, discard the original debugging instruction string and reset the parsing state.

[0071] Specifically, a cooling lock is activated for three consecutive invalid command inputs (new commands are prohibited from being received within 300 seconds); the hash fingerprint and source device information of the invalid command are recorded in the system audit log; the device identity review process is triggered, requiring the authorized device to be re-plugged to verify its legitimacy.

[0072] Optionally, the step of comparing the standard input event with a preset instruction and outputting an execution operation strategy based on the comparison result includes: S510: After the execution of the operation strategy is completed, the target device is removed, the opened debugging port is closed, and the debugging service process is terminated; Specifically, a state rollback mechanism is used to restore the firewall rule snapshot before debugging. A TCP RST packet is sent to active debugging connections to forcibly terminate the session. Kernel modules related to the debugging service are uninstalled and occupied resources are released. A SIGTERM signal is sent to the debugging service process to initiate a graceful exit. The process tree is monitored to ensure that all child processes are terminated synchronously.

[0073] S520: Clear the original debugging instruction character string and disable the debugging instruction monitoring service.

[0074] Specifically, the system performs a physical memory overwrite of the instruction buffer (filling it with random data at least three times); clears sensitive operation records from the system log, retaining only the audit hash value; deletes the debug mode identification file and temporarily generated configuration files; resets the input device status flag, and unbinds the authorized device from debug mode; generates an operation summary report (including timestamp, execution results, and resource change list); transmits the audit log encrypted via a secure channel to a remote management platform; and writes a tamper-proof event watermark to the local storage device.

[0075] Optional, for input device (i.e. target device) identification part: By registering an input device change monitoring function in PhoneWindowManager init, the id function of the agreed device mDeviceA recorded in PhoneWindowManager (telephone window manager) can be changed when adding or removing input devices.

[0076] This method records the value of the mDeviceA variable in the current set-top box when device A is inserted. If the inserted device fails device information verification (device name, manufacturer, and other information), the value of mDeviceA remains unchanged. This method allows you to determine whether the device is the intended debug device upon insertion. Only devices that pass device information verification can trigger subsequent actions.

[0077] When a device is removed, the system checks whether the device being removed is mDeviceA. If so, the mDeviceA flag is set to -Integer.MAX_VALUE, indicating that the debug device has been removed. Subsequent operations will not trigger network configuration and debugging functions.

[0078] Optional, the process for configuring the network and enabling the commissioning function is as follows: The target device is a barcode scanner. Configure the control commands required by the set-top box as barcodes and then enter them through the scanner. For example, "wifi:aaaa:bbbbbbbb" indicates connecting to a Wi-Fi network with the Wi-Fi name aaaa and the password bbbbbbbb. "adb:open" opens the ADB port for debugging.

[0079] Since IPTV key processing can only be thrown to the current display application, the key input by us cannot be processed by the current application, so we need to intercept and process the key before it is handed over to the application, and discard the key after processing.

[0080] (1) In interceptKeyBeforeDispatching, determine the source of the current input key. If the current input key source device is mDeivceA, intercept the key. Otherwise, proceed to the next step.

[0081] (2) Add the intercepted keystrokes to the character array mCtrlArray.

[0082] (3) After receiving enter, determine the current character array content.

[0083] (4) If the current character array content is "adb:open", it means that the adb debugging port of the device is opened and the device is controlled to start the adbd debugging program.

[0084] (5) If the current character array is "wifi:aaaa:bbbbbbbb", then use WifiManager to operate the device to connect to wifi using wifi name aaaa and password bbbbbbbb.

[0085] (6) If it is any other string, discard it.

[0086] (7) Clear the contents of the character array.

[0087] Example 3 Based on Example 1, this embodiment provides an IPTV set-top box network configuration and commissioning system, including: A debugging device determination module is configured to connect a target device to a set-top box via a physical interface, obtain device information of the target device, and determine whether the target device is an authorized debugging device; a debugging mode activation module configured to activate the debugging mode if the target device is an authorized debugging device; a standard input event acquisition module configured to read pre-generated readable debugging codes through the target device and convert the debugging codes into standard input events; An event interception module is configured as a system input manager of the set-top box to monitor standard input events in real time, and intercept the standard input events when the source of the standard input events is an authorized debugging device; The execution module is configured to compare the standard input event with the preset instruction and output an execution operation strategy according to the comparison result.

[0088] Example 4 This embodiment provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement any of the above methods.

[0089] Example 5 This embodiment provides a computer-readable storage medium, on which a computer program is stored. A processor executes the computer program to implement any of the above methods.

[0090] In some embodiments, the computer-readable storage medium may be a memory device such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface mount memory, optical disk, or CD-ROM; or various devices including any one or any combination of the above memories. The computer may be various computing devices including smart terminals and servers.

[0091] In the above embodiments of the present disclosure, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0092] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0093] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected to achieve the purpose of the present embodiment according to actual needs.

[0094] In addition, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0095] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable non-volatile storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a non-volatile storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the various embodiments of the present invention. The aforementioned non-volatile storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program code.

[0096] The above are only preferred embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method for debugging an IPTV set-top box network configuration, characterized in that: include: The target device is connected to the set-top box through a physical interface, the device information of the target device is obtained, and it is determined whether the target device is an authorized debugging device; If the target device is an authorized debugging device, activating the debugging mode; Reading pre-generated readable debugging code through the target device and converting the debugging code into a standard input event; The system input manager of the set-top box monitors standard input events in real time, and intercepts the standard input events when the source of the standard input events is an authorized debugging device; The standard input event is compared with the preset instruction, and an execution operation strategy is output based on the comparison result.

2. The IPTV set-top box network configuration and debugging method according to claim 1, wherein: The target device is connected to the set-top box via a physical interface, the device information of the target device is obtained, and the step of determining whether the target device is an authorized debugging device includes: When the target device is connected to the set-top box through a physical interface, the set-top box obtains device information of the target device through a kernel driver, where the device information includes at least one of a manufacturer label, a product label, and a device serial number; Match and verify the device information with the preset authorized device whitelist to obtain the verification result; If the verification is successful, the target device is marked as an authorized debugging device; If the verification fails, the target device is prohibited from triggering the debugging mode.

3. The IPTV set-top box network configuration and debugging method according to claim 1, wherein: If the target device is an authorized debugging device, the step of activating the debugging mode includes: When detecting that the target device is marked as an authorized debugging device, activating a debugging instruction monitoring service of the set-top box; When the debugging instruction monitoring service is started, the debugging port is kept in a default closed state.

4. The IPTV set-top box network configuration and debugging method according to claim 1, wherein: The system input manager of the set-top box monitors standard input events in real time. When the source of the standard input event is an authorized debugging device, the step of intercepting the standard input event includes: If the device information of the source of the standard input event is consistent with the device information of the authorized debugging device, intercepting the standard input event and preventing it from being passed to the upper layer application; If they are inconsistent, the standard input event is dispatched to the currently focused application.

5. The IPTV set-top box network configuration and debugging method according to claim 1, wherein: The step of comparing the standard input event with the preset instruction and outputting an execution operation strategy according to the comparison result includes: Reassemble the intercepted standard input events into character sequences to generate the original debugging instruction string; Parsing the original debugging instruction string according to preset instruction grammar rules to obtain a parsing result; Compare the parsing result with the preset instruction to determine whether the original debugging instruction string matches the preset instruction; If so, perform the preset operation type; If not, the original debugging instruction string is discarded and the parsing state is reset.

6. The IPTV set-top box network configuration and debugging method according to claim 5, wherein: If yes, then the steps of performing the preset operation type include: When the network configuration command is recognized, the preset wireless network SSID and encryption key are automatically extracted, and the system network management interface is called to connect to the wireless network; When a debug port control instruction is recognized, the corresponding debug service process is dynamically started and the preset port is opened; When a test script calling instruction is recognized, the automated test script is called.

7. The IPTV set-top box network configuration and debugging method according to claim 1, wherein: The step of comparing the standard input event with the preset instruction and outputting an execution operation strategy according to the comparison result includes: After completing the execution of the operation strategy, remove the target device, close the opened debugging port, and terminate the debugging service process; The original debug command string is cleared and the debug command listening service is disabled.

8. An IPTV set-top box network configuration and debugging system, characterized in that: include: A debugging device determination module is configured to connect a target device to a set-top box via a physical interface, obtain device information of the target device, and determine whether the target device is an authorized debugging device; a debugging mode activation module configured to activate the debugging mode if the target device is an authorized debugging device; a standard input event acquisition module configured to read pre-generated readable debugging codes through the target device and convert the debugging codes into standard input events; An event interception module is configured as a system input manager of the set-top box to monitor standard input events in real time, and intercept the standard input events when the source of the standard input events is an authorized debugging device; The execution module is configured to compare the standard input event with the preset instruction and output an execution operation strategy according to the comparison result.

9. A device, characterized in that The device includes a memory and a processor, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium stores a computer program, and the processor executes the computer program to implement the method according to any one of claims 1 to 7.

Images