Telecommunication service information processing system and display equipment

Abstract

The embodiment of the invention provides a telecommunication service information processing system and display equipment, and the system comprises an identity information reading module which is used for reading the identity information of a customer; the keyword extraction module is connected with the package information arrangement module and used for extracting keywords from the package information, generating a package abstract, obtaining the metadata through a data change detector and creating a meta-label, and the meta-label records occurrence of a data change event related to the package information. Relates to the telecommunication service field. The package information arrangement module dynamically updates package information and generates metadata through the acquisition unit, the data lineage recording unit links new and old metadata to create a data lineage record, and on-demand display of detailed information is matched, so that a user and an operator can quickly grasp core contents of a package, and the information acquisition efficiency is remarkably improved.

Description

Technical Field

[0001] This invention relates to the field of telecommunications services, specifically to a telecommunications business information processing system and display equipment. Background Technology

[0002] With the rapid development of the telecommunications industry, customers' demands for telecommunications service information are becoming increasingly diversified and personalized. To meet customers' needs for quickly obtaining telecommunications package information tailored to their specific requirements in scenarios such as service centers, telecommunications service information processing systems have gradually become a key focus of the industry. Traditional methods of processing telecommunications service information typically rely on manual queries or simple database searches, which have the following problems: Low information acquisition efficiency: The process of matching customer identity information with service needs is cumbersome and lacks an automated prediction mechanism, resulting in inaccurate recommended package information and affecting customer experience.

[0003] Inadequate package information management: Package information is usually stored in a static form, lacking dynamic updates and metadata management mechanisms, making it impossible to effectively track data continuity or record data change events, and making it difficult to support complex data analysis and personalized push notifications.

[0004] Limited information display: Existing systems mostly display package information in list format, lacking a summary-first display method, making it difficult for operators and customers to quickly understand the core content of the package, resulting in low interaction efficiency.

[0005] Insufficient selection and interaction experience: Traditional systems lack convenient selection modules, requiring operators to manually query or switch package information, which is complex and prone to errors, making it difficult to meet the needs of high-frequency interaction scenarios in business halls.

[0006] To address the aforementioned issues, some telecommunications service information processing systems have introduced functions such as identity information reading, demand forecasting, and information push in recent years. For example, some systems make basic service recommendations by reading customer identity information (such as ID card data), but these systems are usually based on simple rule matching and lack in-depth demand forecasting and dynamic data management capabilities. Furthermore, existing methods of organizing package information largely rely on manual maintenance, with weak metadata generation and data inheritance recording functions, making it difficult to cope with rapidly changing telecommunications service needs. While keyword extraction and package summary generation technologies are used in some systems, they are often not deeply integrated with display and selection modules, resulting in a disconnect between information display and operational processes, affecting overall efficiency.

[0007] Therefore, there is an urgent need for an integrated telecommunications service information processing system that can efficiently acquire customer information through an identity information reading module, achieve accurate service recommendations by combining a demand prediction module, realize dynamic data management through a package information organization module and a data inheritance recording unit, generate package summaries through a keyword extraction module, and optimize information display and interactive experience with display and selection modules. Such a system can significantly improve the processing efficiency of telecommunications service information and customer satisfaction in the business hall scenario, providing telecommunications operators with more intelligent and convenient service support. Summary of the Invention

[0008] According to embodiments of the present invention, a telecommunications service information processing system and display device are provided to solve the technical problems existing in the background art described above.

[0009] In a first aspect of the present invention, a telecommunications service information processing system is provided.

[0010] The telecommunications service information processing system includes: The identity information reading module is used to read the customer's identity information; The demand estimation module is connected to the identity information reading module and is used to estimate the customer's service needs based on the identity information. An information push module, connected to the demand estimation module, is used to push relevant telecommunications service information to customers based on the estimated service demand. The package information processing module is used to obtain package information from the telecommunications business database through the acquisition unit, and generate or update metadata about the package information, the metadata including newly generated metadata and previously stored metadata; A data lineage recording unit is used to create or modify a data lineage record of the package information by linking the previously obtained metadata with the newly generated metadata; The keyword extraction module, connected to the package information processing module, is used to extract keywords from the package information and generate a package summary, and to obtain the metadata through a data change detector and create meta tags, wherein the meta tags record the occurrence of data change events involving the package information; The display module, connected to the keyword extraction module, is used to display a single package summary and corresponding package information, wherein the package summary is displayed first. The selection module, connected to the display module and the keyword extraction module, is used to allow operators to select the package summary and trigger the display of package information corresponding to the selected package summary.

[0011] Preferred options also include: A metadata storage module is used to store the metadata and meta tags, and associate the meta tags with the metadata; The demand forecasting module includes: The data analysis unit is used to analyze the customer's potential service needs based on the identity information and pre-stored user behavior data; The demand matching unit, connected to the data analysis unit, is used to match the potential service demands with telecommunications service packages and generate estimated demand results.

[0012] Preferably, the package information processing module includes: A data acquisition unit is used to obtain package information from a telecommunications service database through an acquisition unit, and to create and / or obtain metadata about the package information, wherein the metadata includes newly generated metadata and previously obtained metadata; An information classification unit, connected to the data acquisition unit, is used to classify and organize the package information according to the package type and service content.

[0013] Preferably, the keyword extraction module includes: The text analysis unit is used to perform natural language processing on the package information, extract keywords including data usage, call duration and price, and obtain the metadata through a data change detector to obtain information about data change events involving the package information; The data change detector is operable to examine two or more directly linked metadata fragments parsed from public records, and to calculate or determine based on this: How much data has been added to or removed from a record; Has the nature of the recorded content changed, and what type of change has occurred? Has sensitive data been added to or removed from the record? A summary generation unit, connected to the text analysis unit, is used to generate a package summary based on the keywords; The meta tag creation unit is used to create meta tags based on the acquisition of the metadata. The meta tags record the occurrence of the data change event and indicate the status of the package information when the package information is acquired.

[0014] Preferably, it further includes: a button control module for detecting and processing input signals from a control device having at least four buttons, wherein the at least four buttons include two toggle buttons and two browse buttons, wherein: The two toggle buttons are used to switch between different package summaries displayed in the module; Two browse buttons are used to trigger browsing of detailed information on the selected package summary; a key signal detection unit, connected to the key control module, is used to monitor the key events of the four buttons and generate corresponding operation instructions; a page switching unit, connected to the key signal detection unit and the display module, is used to switch the display of the package summary according to the operation instructions of the two switching buttons; a detailed information display unit, connected to the key signal detection unit and the display module, is used to display the detailed information of the selected package summary according to the operation instructions of the two browse buttons.

[0015] Preferably, the button control module further includes: a user preference analysis unit, used to record the operator's browsing behavior of the package summary through the two browsing buttons, and analyze the operator's preference pattern; and a dynamic push unit, connected to the user preference analysis unit and the information push module, used to adjust the pushed package summary according to the preference pattern.

[0016] Preferably, the button signal detection unit includes: an event capture subunit, used to capture the press and release events of the four buttons in real time and generate button signal data containing button type and time; and an instruction generation subunit, connected to the event capture subunit, used to generate corresponding page switching or detailed information display instructions based on the button signal data, and transmit the instructions to the page switching unit or detailed information display unit.

[0017] Preferably, the user preference analysis unit includes: a behavior data recording subunit, used to record the frequency, duration, and selected package type of the operator browsing detailed information through the two browsing buttons; and a preference model updating subunit, connected to the behavior data recording subunit, used to update the operator's preference model according to the behavior data, and transmit the updated preference model to the dynamic push unit to optimize the push order or content of the package summary.

[0018] In a second aspect of the invention, a telecommunications service information display device is provided, including a housing, a display screen, a control module, two switching buttons, and two browsing buttons; The casing is connected to the display screen, which is used to display a single package summary or corresponding package details, wherein the package summary is displayed first. The control module is connected to the display screen, the toggle button, and the browse button, and is used to process button input signals and control the content of the display screen. The control module includes: The microprocessor receives button signals, executes switching or browsing logic based on the display status, and generates display instructions. A button interface circuit is used to detect the physical contact between the switch button and the browse button and generate an electrical signal; The display driver circuit is used to convert microprocessor instructions into display screen signals and update the display content; The memory is used to store the current display status and package summary data; The browse button is used to trigger the display of package details or to browse the details page: When the browse button is first in the first position, the button interface circuit detects the electrical signal generated by physical contact, the microprocessor triggers the display of detailed information of the selected package summary, the display driver circuit updates the display screen content, enables the detailed information display function, and disables the display of the package summary; When the browse button is in the first position again in the details view, the microprocessor triggers the browsing details page, the display driving circuit updates the display screen content, and enables the page browsing function; When the browse button is in the second position, the microprocessor maintains the currently displayed content and disables the summary display function; The toggle button is used to switch between package summaries or jump from the details view to the package summary: When the switching button is in the first position, the button interface circuit detects the electrical signal generated by physical contact, the microprocessor triggers the display of the next or previous package summary, the display driving circuit updates the display screen content, enables the switching function, and turns off the display of the currently displayed content; When the switch button is in the second position, the microprocessor maintains the current display content and disables the switching function; After the browse button triggers the display of detailed information, the display screen only shows the package details, and the package summary is no longer displayed. The browse button is used to browse the detailed information page, and the user can only jump back to the package summary view and switch to the next or previous package summary by using the switch button.

[0019] Preferably, it also includes at least four triggering mechanisms and switching mechanisms; The switching mechanism includes a first outer frame, two first positioning holes, a second outer frame, two second positioning holes, a first rack, a gear, a second rack, a bracket, two limit rods, two stops, two magnetic blocks, a base, and two notches; Both first positioning holes are machined on the first outer frame. The first outer frame is connected to the first rack. The first rack meshes with the gear. The gear meshes with the second rack. The second rack is connected to the second outer frame. Both second positioning holes are machined on the second outer frame. The gear is rotatably connected to the bracket. The bracket is connected to the base. Both notches are machined on the base. The notches match the size of the magnetic blocks and can attract each other. Both magnetic blocks are connected to the first rack and the second rack respectively. Both magnetic blocks are connected to the two stops respectively. The bottom surface of the stops can contact the top surface of the base. Both limiting rods are connected to the first rack and the second rack respectively. Both limiting rods are slidably connected to the base. The triggering mechanism includes a trigger element, a protrusion, and a tension spring; The trigger is slidably connected to the first positioning hole or the second positioning hole, the protrusion is connected to the first outer frame or the second outer frame, and the tension spring is connected between the lower part of the trigger and the protrusion.

[0020] One or more technical solutions provided in this application have at least the following technical effects or advantages: This invention provides a telecommunications service information processing system and display device. Through a package information organization module, package information is dynamically updated and metadata is generated by an acquisition unit. A data inheritance record unit links new and old metadata to create data inheritance records, ensuring the traceability and integrity of package information and providing reliable support for subsequent data analysis and service optimization. A keyword extraction module extracts keywords from the package information to generate package summaries, which are then prioritized for display by a display module. Combined with the on-demand display of detailed information, this allows users and operators to quickly grasp the core content of the package, significantly improving information acquisition efficiency.

[0021] It should be understood that the description in the Summary of the Invention is not intended to limit the key or essential features of the embodiments of the present invention, nor is it intended to restrict the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0022] The above and other features, advantages, and aspects of the various embodiments of the present invention will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein: Figure 1 A flowchart of a telecommunications service information processing system according to an embodiment of the present invention is shown; Figure 2 A three-dimensional connection structure diagram of a telecommunications service information display device according to an embodiment of the present invention is shown; Figure 3 An exploded view of a telecommunications service information display device according to an embodiment of the present invention is shown; Figure 4 An exploded view of the housing of a telecommunications service information display device according to an embodiment of the present invention is shown; Figure 5 A schematic diagram of the connection structure of the triggering mechanism of a telecommunications service information display device according to an embodiment of the present invention is shown; Figure 6 A schematic diagram of the connection structure of the switching mechanism of a telecommunications service information display device according to an embodiment of the present invention is shown; Figure 7 A partially enlarged schematic diagram of the switching mechanism of a telecommunications service information display device according to an embodiment of the present invention is shown.

[0023] Tag name: 1-Casing, 2-Display screen, 3-Identification unit, 4-Housing, 5-Control module, 6-Browse button, 7-Switch button, 8-Switch mechanism, 801-First outer frame, 802-First positioning hole, 803-Second outer frame, 804-Second positioning hole, 805-First rack, 806-Gear, 807-Second rack, 808-Bracket, 809-Stop, 810-Magnetic block, 811-Base, 812-Notch, 813-Limit rod, 9-Trigger mechanism, 901-Trigger element, 902-Protrusion, 903-Tension spring. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0025] Furthermore, the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0026] like Figure 1As shown, this telecommunications service information processing system is used to estimate service needs based on customer identity information, organize and push telecommunications service package information, and present it to operators on a display device in an interactive manner with package summaries and detailed information. The implementation of the system is described in detail below with reference to preferred embodiments, enabling those skilled in the art to implement this invention.

[0027] This system includes an identity information reading module, a demand prediction module, an information push module, a package information organization module, a data lineage recording unit, a keyword extraction module, a display module, a selection module, a metadata storage module, a button control module, and a telecommunications service information display device. The system is deployed on a server (e.g., a cloud server based on a Linux operating system, equipped with an 8-core CPU and 16GB of memory) and interacts with the display device via a communication network (such as 4G / 5G or Wi-Fi). The display device is an embedded terminal equipped with a touchscreen or physical buttons for operator interaction.

[0028] The identity information reading module connects to external devices (such as ID card readers or mobile phone NFC modules) via hardware interfaces (such as USB or NFC) to read customer identity information, including name, ID number, and mobile phone number. For example, when an operator places a customer's ID card on the reader, the module parses the ID card chip data through the driver program, generates structured identity information (JSON format, such as {"name":"Zhang San","id":"123456789012345678"}), and stores it in system memory for use by subsequent modules.

[0029] The demand forecasting module receives identity information and, combined with pre-stored user behavior data (stored in a MySQL database, including historical call duration, data usage, etc.), analyzes the customer's potential service needs. The module includes a data analysis unit and a demand matching unit. Data Analysis Unit: Employing machine learning algorithms (such as decision trees) and based on identity information (such as age and occupation) and behavioral data (such as monthly average data usage of 5GB and 100 minutes of calls), predicts customer preferences (such as high data plans).

[0030] Demand matching unit: Matches the prediction results with the telecom service package library (including package ID, name, data allowance, call duration, etc.) to generate estimated demand results (e.g., recommending a package with a monthly fee of 50 yuan, 10GB of data allowance, and 100 minutes of call time). The results are output to the information push module in JSON format ({"customer_id":"123","recommended_plan":"plan_001"}).

[0031] The information push module receives the estimated demand results and pushes relevant package information to customers via a communication interface (such as a REST API). The push method is display on the display device. For example, the module sends a message via SMS gateway: "Dear customer, based on your needs, we recommend a monthly package of 50 yuan, including 10GB of data." At the same time, the push result is transmitted to the control module of the display device for operators to view.

[0032] The package information processing module processes telecommunications service package information through a data collection unit and an information classification unit: Data Acquisition Unit: Retrieves package information from the telecommunications business database (PostgreSQL, which stores package IDs, names, prices, etc.) through database queries (SQL statements, such as SELECT * FROM plans), and generates metadata (including newly generated metadata such as creation time and package version number, and previously stored metadata such as historical prices). The metadata format is {"plan_id":"plan_001","create_time":"2025-07-04","version":"1.0"}.

[0033] Information classification unit: Organized according to package type (such as data package, voice package) and service content (such as preferential policies, applicable groups). For example, packages are divided into "high data package" (>5GB) and "low data package" (≤5GB) and stored in the metadata storage module.

[0034] The data continuity record unit records the update history of metadata and generates data continuity records for package information. The unit creates a record (format: {"plan_id":"plan_001","change_time":"2025-07-04","old_price": 50,"new_price": 60}) by comparing old and new metadata. The record is stored in the metadata storage module, supporting the tracing of package information changes.

[0035] The keyword extraction module processes package information, generates summaries, and records change events. It includes a text analysis unit, a data change detector, and a summary generation unit. Text Analysis Unit: Uses Natural Language Processing (NLP) techniques (such as the TF-IDF algorithm) to extract keywords (such as "50 yuan", "10GB", and "100 minutes") from package information (text description, such as "monthly fee of 50 yuan, 10GB of data, and 100 minutes of talk time").

[0036] Data Change Detector: Compares old and new metadata, detects change events (such as price changes, traffic adjustments), and generates meta tags (format: {"plan_id":"plan_001","change_event":"price_increase","timestamp":"2025-07-04"}).

[0037] Summary generation unit: Generates a package summary based on keywords (e.g., "50 yuan / month, 10GB data, 100 minutes of calls"), and stores it in the metadata storage module for use by the display module.

[0038] The metadata storage module is based on a NoSQL database (such as MongoDB) and stores metadata, meta tags, and package summaries. Meta tags are associated with metadata via package IDs (e.g., {"plan_id":"plan_001","metadata": {...},"tags": [...]}). The module supports fast queries and responds to requests to display and select modules.

[0039] The display module is deployed on the display device and displays a package summary and detailed information on a screen (e.g., a 7-inch LCD screen with a resolution of 1024x600). Initially, a single package summary (e.g., "50 yuan / month, 10GB data") is displayed, with the summary shown first. The selection module receives operator input (e.g., pressing a selection button or clicking on a touchscreen) through the control module of the display device, triggering the display of the corresponding package details (e.g., "Special Offer: First Month Free").

[0040] The button control module is integrated into the display device, including a user preference analysis unit and a dynamic push unit: User Preference Analysis Unit: Records the operator's interaction behavior through the browse button and switch button (e.g., browsing frequency, selected package type), and stores it as behavioral data (format: {"operator_id":"op_001","action":"view_plan_001","duration": 30s}).

[0041] Dynamic push unit: Adjust push priority based on behavioral data, for example, prioritize pushes of high-data packages that operators frequently view.

[0042] In actual use, when a customer visits a telecom service center, operators use a demonstration device (embedded terminal) to process customer requests: The operator scans the customer's ID card using an identity information reading module to obtain identity information (name: Zhang San, ID number: 123456789012345678). The demand estimation module analyzes the customer's historical data (average monthly data usage 6GB, call minutes 80 minutes) and recommends a package "50 yuan / month, 10GB data, 100 minutes of call time". The information push module sends the recommended package information via SMS and simultaneously transmits it to the demonstration device. The package information organization module retrieves the latest package information from the database, generates metadata ({"plan_id":"plan_001","price": 50}), and categorizes it as a "high data package". The data inheritance recording unit records metadata changes (e.g., price adjusted from 48 yuan to 50 yuan). The keyword extraction module generates a package summary ("50 yuan / month, 10GB data, 100 minutes of call time") and stores it in the metadata storage module. This system provides personalized package recommendations through identity information analysis and package information organization; the display device supports interactive display of summary and detailed information for easy operation; data inheritance and meta tag recording ensure information traceability; and user preference analysis optimizes push notification effects. The system is suitable for scenarios such as telecom service halls and online service platforms, improving customer experience and operational efficiency.

[0043] In this implementation, the metadata storage module stores metadata and meta tags, and associates meta tags with metadata via a package identifier (ID). The module uses a MongoDB database (version 4.4, deployed on a Linux server with an 8-core CPU and 16GB of memory) and stores data in JSON document format. Metadata includes newly generated metadata (such as package creation time and price) and previously stored metadata (such as historical version information). Meta tags record change events to package information (such as price adjustments). Example storage structure: { "plan_id":"plan_003", "metadata": { "name":"Value Data Plan", "price": 70, "traffic":"20GB", "create_time":"2025-07-04T16:00:00Z", "version":"1.1" }, "tags": [ { "change_event":"price_increase", "timestamp":"2025-07-04T10:00:00Z", "old_price": 65, "new_price": 70 } } Meta tags are associated with metadata through the plan_id field, supporting fast querying (e.g., db.plans.find({"plan_id":"plan_003"}), response time <30ms). The module responds to data requests from the demand estimation module, package information collation module, etc. through the REST API (based on the HTTPS protocol), providing package information and change records.

[0044] The demand estimation module includes a data analysis unit and a demand matching unit, which are used to analyze customers' potential service demands and match telecom service packages.

[0045] Data analysis unit: Obtain pre-stored user behavior data from the MySQL database, including historical call duration, traffic usage, and package preferences (e.g., average monthly traffic 10GB, calls 150 minutes). The unit receives the input from the identity information reading module (in JSON format, such as {"name":"王五","id":"123456789012345678","age": 30}), and uses the K-Nearest Neighbor (KNN) algorithm (k = 5, Euclidean distance) to analyze customers' demands. The algorithm generates a demand vector ({"traffic_demand":"high","call_demand":"medium","price_sensitivity":"low"}) based on identity information (such as age, occupation) and behavior data.

[0046] ​Demand Matching Unit: Receives a demand vector and matches packages using a weighted scoring algorithm. The unit queries package information from the metadata storage module (e.g., [{"plan_id":"plan_003","price": 70,"traffic":"20GB"}]), assigns weights based on the demand vector (data 0.6, price 0.3, call 0.1), and calculates a package score (e.g., score = 0.6*traffic_match + 0.3*price_match + 0.1*call_match). The highest-scoring package is selected as the recommendation result and output in JSON format ([{"plan_id":"plan_003","name":"Value Data Package","score": 0.92}]), which is then transmitted to the information push module.

[0047] In actual use, customer Wang Wu provides his ID card, which is scanned by the operator using the display device, and the identity information reading module obtains the data. The data analysis unit queries the behavioral data (10GB / month traffic) from the MySQL database to generate a high traffic demand vector. The demand matching unit queries the metadata storage module to match "plan_003" (70 yuan, 20GB traffic) and generates a recommendation result. The metadata storage module provides the latest package information and meta tags (recording the price adjustment from 65 yuan to 70 yuan). The display device displays a summary ("70 yuan / month, 20GB traffic"). The operator presses the first browse button to display detailed information; pressing it again scrolls to the discount details; pressing the first switch button jumps to the next package summary. The button control module records the operation behavior to optimize subsequent push notifications. The metadata storage module efficiently stores and queries metadata and meta tags through MongoDB, supporting package information traceability; the demand prediction module uses the KNN algorithm and weighted scoring to accurately recommend packages; combined with the display device, it provides interactive package displays, improving customer experience and operational efficiency.

[0048] In this embodiment, the package information processing module of the telecommunications service information processing system is used to obtain package information from the telecommunications service database, generate metadata, and classify and organize it to support subsequent package recommendations and displays. The implementation method and actual usage process of the package information processing module are described in detail below to enable those skilled in the art to implement this invention.

[0049] The package information processing module includes a data collection unit and an information classification unit, which is deployed on a cloud server (a server based on Ubuntu 20.04, equipped with an 8-core CPU and 16GB of memory) and interacts with the telecommunications business database through a database interface.

[0050] Data Acquisition Unit: The data acquisition unit retrieves plan information from a PostgreSQL database (version 15) via a database interface (JDBC, Java 17 environment). The unit executes SQL queries (e.g., SELECT id, name, price, traffic, call_duration, description FROM plans WHERE active = true) to obtain plan data (e.g., plan ID, name, price, data usage, call duration). After acquisition, the unit generates metadata, including newly generated metadata (generated in real-time, such as acquisition time and plan version) and previous metadata (historical data, such as last month's price). The metadata is in JSON format, for example: { "plan_id":"plan_004", "name":"Family Sharing Package", "price": 100, "traffic":"30GB", "call_duration":"300min", "collect_time":"2025-07-04T14:00:00Z", "version":"1.2", "previous_price": 95 } The newly generated metadata is derived from the collection time and current package information, while previous metadata is retrieved from the database's history table (plan_history). The metadata data is transferred to the metadata storage module (MongoDB) for storage and then passed to the information classification unit.

[0051] The information classification unit receives package information and metadata from the data collection unit and organizes the packages based on a rule-based classification algorithm. Classification criteria include package type (data package, voice package, comprehensive package) and service content (applicable users, preferential policies). For example: Data package: Monthly data allowance ≥ 10GB, suitable for high-data users. Voice package: Talk time ≥ 200 minutes, suitable for frequent call users. Comprehensive package: Balanced data and voice allowance, suitable for families or multi-device users. Algorithm flow: Parses the traffic and call_duration fields in the metadata. Apply rules (e.g., if traffic >= 10GB then type = 'traffic_plan').

[0052] Extract service content keywords (e.g., "family" and "first month discount") using Python's re regular expression library. The categorization results are package tags ({"plan_id":"plan_004","type":"comprehensive_plan","target":"family"}), stored in the metadata storage module for use by the keyword extraction module and the demand forecasting module.

[0053] In practical use, the package information processing module collects and categorizes package information through the following steps: The data collection unit queries the latest package information from the PostgreSQL database via a scheduled task (e.g., executed daily at 00:00, based on Spring Boot scheduling) (SELECT * FROM plans). For new packages (e.g., "Family Shared Package, 100 RMB, 30GB Data, 300 Minutes of Talk Time"), newly generated metadata is generated ({"plan_id":"plan_004","collect_time":"2025-07-04"}). For existing packages, previous metadata is retrieved (e.g., historical price 95 RMB), merged into complete metadata, and stored in MongoDB. The information classification unit parses the metadata and applies classification rules (e.g., 30GB data > 10GB, marked as a comprehensive package). Keywords are extracted from the description field ("Applicable to family users, first month waived") to generate tags ({"type":"comprehensive_plan","target":"family"}). The classification results are stored in MongoDB for use by subsequent modules. The categorized package information is transmitted to the keyword extraction module, generating a package summary ("100 yuan / month, 30GB data, 300 minutes of calls"). The summary is displayed on screen 2 of the display device. The package information organization module generates structured metadata and category tags through efficient data collection and rule-based classification, supporting accurate package recommendations and displays; combined with the metadata storage module and display device, it enhances the system's data processing capabilities and user interaction experience.

[0054] In this embodiment, the keyword extraction module of the telecommunications service information processing system is used to extract key information from the package information, generate a package summary, and record data change events to support the display and traceability of package information.

[0055] The keyword extraction module includes a text analysis unit, a data change detector, a summary generation unit, and a meta tag creation unit. It is deployed on a cloud server and interacts with a MongoDB database through a Python 3.9 environment to process package information and metadata.

[0056] Text Analysis Unit: The text analysis unit receives package information (text description, e.g., "Monthly fee 80 yuan, 20GB data, 200 minutes of talk time, first month waived") from the package information processing module and extracts keywords using Natural Language Processing (NLP) technology. The unit uses Python's NLTK library and analyzes the text based on the TF-IDF (Term Frequency-Inverse Document Frequency) algorithm to extract key fields, including data allowance (e.g., "20GB"), talk time (e.g., "200 minutes"), price (e.g., "80 yuan"), and other features (such as "first month waived"). Processing Flow: Word segmentation: Breaks text into words or phrases (e.g., “monthly fee / 80 yuan / 20GB / data traffic”).

[0057] Feature extraction: Use regular expressions to match numbers and units (e.g., r'\d+\s*(GB|minutes|yuan)').

[0058] TF-IDF scoring prioritizes extracting high-frequency and unique fields (e.g., "20GB" is more critical than "monthly fee"). The output is a keyword list (["80 yuan", "20GB", "200 minutes", "first month discount"]), which is then sent to the abstract generation unit.

[0059] Data Change Detector: The data change detector retrieves new and old metadata from the metadata storage module (MongoDB), compares two or more metadata records, and detects change events in package information. The comparison objects are metadata fields (e.g., price, data usage), not "common records." Detection logic: Read metadata (e.g., {"plan_id":"plan_005","price": 80,"traffic":"20GB"} and {"plan_id":"plan_005","price": 75,"traffic":"20GB"}).

[0060] Field comparison: Field-by-field comparison (Python's dictionary comparison), calculate the change (e.g., price increases by 5 yuan).

[0061] Determine the change type: It is divided into addition (new field, such as adding "discount"), deletion (removal of field) and modification (value change, such as price adjustment).

[0062] Sensitive Data Check: Define sensitive data as price, data usage, and call duration, and check for changes to these sensitive fields. The output is a change event description ({"plan_id":"plan_005","event":"price_increase","change_amount": 5,"sensitive": true}), which is transmitted to the meta tag creation unit.

[0063] Summary Generation Unit: This unit receives a keyword list from the text analysis unit and generates a package summary based on a predefined template. The template is "{price} / month, {data}data, {call duration}call". After filling in the keywords, a string is generated (e.g., "80 yuan / month, 20GB data, 200 minutes of calls"). If other features are included (such as "first month discount"), a description is added (e.g., "80 yuan / month, 20GB data, 200 minutes of calls, first month discount"). The summary is stored as a string in the metadata storage module for use by the display module.

[0064] Meta Tag Creation Unit: This unit receives change event descriptions from the data change detector, generates meta tags, and records the change events and package information status. Meta tags are in JSON format, for example: { "plan_id":"plan_005", "change_event":"price_increase", "timestamp":"2025-07-04T15:00:00Z", "details": {"old_price": 75,"new_price": 80}, "status":"updated", "version":"1.3" } The `status` field in the meta tag indicates the plan status (e.g., "updated" means updated, "active" means active), and the `version` field records the plan version. Meta tags are stored in the metadata storage module and associated with metadata via `plan_id`.

[0065] In practical use, the keyword extraction module generates package summaries and records changes through the following steps: The package information organization module provides package information (e.g., "Monthly fee 80 yuan, 20GB data, 200 minutes of talk time, first month free"), storing it as metadata ({"plan_id":"plan_005","price": 80,"traffic":"20GB"}) in MongoDB. The text analysis unit uses the TF-IDF algorithm and regular expressions to extract keywords (["80 yuan","20GB","200 minutes","first month free"]). The summary generation unit fills the template, generates a summary ("80 yuan / month, 20GB data, 200 minutes of talk time, first month free"), and stores it in MongoDB. The data change detector compares the old and new metadata (old: {"price": 75}, new: {"price": 80}) and generates a change event ({"event":"price_increase","change_amount": 5}). The meta tag creation unit generates meta tags ({"change_event":"price_increase","status":"updated"}) and stores them in MongoDB. Display screen 2 shows "80 yuan / month, 20GB data, 200 minutes of calls". The operator presses the first browse button to view detailed information ("Monthly fee 80 yuan, first month waived"); presses it again to scroll to "Applicable age group: 18-40 years old"; presses the first switch button to jump to the next package summary ("90 yuan / month, 30GB data"). The keyword extraction module efficiently extracts keywords using the TF-IDF algorithm to generate a concise package summary; the data change detector and meta tag creation unit record change events, supporting information traceability; combined with the display device, it provides interactive package display, improving user experience.

[0066] In this embodiment, the key control module (control module 5) of the telecommunications service information processing system is used to detect and process button input signals from the control device, supporting the switching of package summaries and browsing of detailed information. The key control module (control module 5) is the input processing component of the system, deployed on a server (based on Ubuntu 20.04, equipped with an 8-core CPU and 16GB of memory) or an embedded device, and processes signals through a software module developed in Python 3.9. The module interacts with the control device, which is equipped with at least four buttons: two switching buttons (switching buttons 7-1 and 7-2) and two browsing buttons (browsing buttons 6-1 and 6-2). The buttons are general-purpose digital input interfaces (e.g., GPIO pins), generating a low-level signal (0V) when pressed and a high-level signal (3.3V) when released. The module interacts with the display module and the metadata storage module through a software interface (e.g., REST API).

[0067] Button Signal Detection Unit: This unit monitors the input signals from four buttons using an event-driven mechanism (based on Python's select library, polling GPIO status). When a button is pressed, a low-level signal is generated. The unit filters noise using a debouncing algorithm (10ms delay) to ensure signal stability. The unit generates operation instructions in JSON object format, for example: { "button_id":"switch_1", "action":"next_summary", "timestamp":"2025-07-04T15:30:00Z" } The instructions are categorized according to button function: Toggle button 7-1 (next_summary), Toggle button 7-2 (previous_summary), Browse button 6-1 (show_details), and Browse button 6-2 (scroll_details). The instructions are transmitted to the page switching unit or the detailed information display unit.

[0068] Page Switching Unit: The page switching unit receives commands from the switching button and controls the display module to switch package summaries. Switching Logic: Read the current summary index (stored in memory, for example, index: 2 corresponds to package plan_005).

[0069] Update the index according to the instructions: Toggle button 7-1 increases the index (index += 1), toggle button 7-2 decreases the index (index -= 1).

[0070] Query the metadata storage module (MongoDB) via the REST API to get a new summary (e.g., {"plan_id":"plan_006","summary":"90 yuan / month, 30GB data, 200 minutes of calls"}).

[0071] Call the display module's interface (e.g., POST / display / update) to update the displayed content. Switching response time is <100ms, and the summary is presented in text format.

[0072] Detailed Information Display Unit: This unit receives instructions from the browse button and controls the display module to show the detailed information of the selected package summary. Display Logic: Read the package ID of the current summary (e.g., plan_005).

[0073] Query the metadata storage module to obtain detailed information (e.g., {"plan_id":"plan_005","details":"Monthly fee of 80 yuan, 20GB of data, 200 minutes of calls, first month free, applicable to people aged 18-40"}).

[0074] Call the display module interface to switch to the details view.

[0075] If the command (scroll_details) from the browse button 6-2 is received, content scrolling is triggered (e.g., scrolling down 100 characters). Display switching and scrolling response time is <50ms, and detailed information is presented in multi-line text format.

[0076] In actual use, the button control module achieves switching of package summaries and browsing of detailed information through the following steps: Upon system startup, the display module shows the initial package summary (e.g., "80 yuan / month, 20GB data, 200 minutes of talk time", package plan_005, index 2). The button control module initializes the GPIO interface and starts signal polling. When the operator presses the switch button 7-1 (the first switch button), the button signal detection unit captures a low-level signal and generates an instruction ({"button_id":"switch_1","action":"next_summary"}). The page switching unit increases the index to 3, queries the metadata storage module, retrieves the summary of package plan_006 ("90 yuan / month, 30GB data, 200 minutes of talk time"), and the display module updates the displayed content. When the operator presses the browse button 6-1 (the first browse button), the button signal detection unit generates an instruction ({"button_id":"browse_1","action":"show_details"}). The detailed information display unit queries the detailed information of plan_005 ("Monthly fee 80 yuan, 20GB data, 200 minutes of calls, first month free"), and the display module switches to the detailed information view. The operator presses the browse button 6-2 (the second browse button), and the key signal detection unit generates an instruction ({"button_id":"browse_2","action":"scroll_details"}). The detailed information display unit triggers scrolling down to display the subsequent content ("Applicable to: 18-40 years old"). The operator presses the switch button 7-1 again, and the page switching unit jumps back to the summary view, displaying the summary of plan_006 ("90 yuan / month, 30GB data"). The key signal detection unit transmits the operation record ({"operator_id":"op_003","action":"browse_plan_005","duration": 20s}) to the user preference analysis unit for dynamic push optimization. The button control module enables rapid switching of package summaries and smooth browsing of detailed information through efficient signal detection and command processing; it collaborates with the metadata storage and display modules to provide accurate data display; and operation logs support user preference analysis, enhancing the personalization of package recommendations.

[0077] In this embodiment, the user preference analysis unit includes a behavior data recording subunit and a preference model updating subunit, which analyzes the browsing behavior of operators and generates a preference model.

[0078] Behavior data recording subunit: This subunit monitors the key signal data of browsing buttons 6-1 and 6-2, recording the operator's browsing behavior, including: Frequency: The number of times the browse button (to display details) is pressed each time.

[0079] Duration: The time spent viewing detailed information (from show_details to the next button event).

[0080] Package type: The type of package viewed (e.g., data plan, comprehensive plan, retrieved from the metadata storage module). Data is stored as a JSON log in MongoDB (database user_behavior), for example: { "operator_id":"op_004", "kit_id":"plan_005", "type":"traffic_plan", "frequency": 3, "duration": 25, "timestamp":"2025-07-04T16:00:05Z" } Logs are written in batches every minute with a recording latency of <10ms.

[0081] The preference model update subunit updates the operator's preference model based on behavioral data. The model is a statistical weighted model, recording the preference score (range 0-1) for each meal type. Update algorithm: Calculate the frequency weight: frequency_score = min(frequency / 5, 1) (maximum of 5 times).

[0082] Calculate duration weight: duration_score = min(duration / 60, 1) (maximum 60 seconds).

[0083] Update the preference score: preference_score = 0.6 * frequency_score + 0.4 * duration_score.

[0084] Smooth the score using an exponential moving average (EMA, α=0.3): new_score = α * preference_score + (1-α) * old_score. The model is stored as JSON, for example: { "operator_id":"op_004", "preferences": { "traffic_plan": 0.75, "call_plan": 0.20, "comprehensive_plan": 0.45 }, "update_time":"2025-07-04T16:01:00Z" } The updated model is transmitted to the dynamic push unit and updated every 5 minutes.

[0085] The dynamic push unit receives a preference model that collaborates with the information push module to adjust the package summary of the push notifications. Adjustment logic: Reading preference model (e.g., traffic_plan: 0.75).

[0086] Query the metadata storage module to retrieve summaries of all plans (e.g., [{"plan_id":"plan_005","summary":"80 yuan / month, 20GB traffic"}]).

[0087] Sort by preference score: Plan types with higher preference scores are given priority (e.g., data plans are ranked first).

[0088] The sorted summary list is transmitted to the information push module via the REST API (POST / push / update). The push list is in JSON format, for example: [ {"plan_id":"plan_005","summary":"80 yuan / month, 20GB data","type":"traffic_plan"}, {"plan_id":"plan_006","summary":"90 yuan / month, 30GB data","type":"traffic_plan"}, {"plan_id":"plan_004","summary":"70 yuan / month, 150 minutes of talk time","type":"call_plan"} ] The push update interval is 5 minutes, and the response time is less than 200ms.

[0089] In practical use, the button signal detection unit processes button input through the following steps: Upon system startup, the event capture subunit initializes GPIO polling, listening for the switching buttons 7-1 and 7-2, and the browse buttons 6-1 and 6-2. When the operator presses the browse button 6-1, the event capture subunit detects a low-level signal and generates signal data ({"button_id":"browse_1","event":"press"}). The instruction generation subunit parses the signal data and generates an instruction ({"action":"show_details","kit_id":"plan_005"}), which is transmitted to the detailed information display unit via a message queue. When the operator presses the switching button 7-1, an instruction ({"action":"next_summary"}) is generated and transmitted to the page switching unit, updating the display module to a summary of plan_006 ("90 yuan / month, 30GB data traffic"). The user preference analysis unit analyzes user behavior through the following steps: The user presses the browse button 6-1 to view the details of plan_005 ("Monthly fee 80 yuan, 20GB data, first month free"), and stays for 25 seconds. The behavior data recording sub-unit generates a log ({"kit_id":"plan_005","type":"traffic_plan","frequency": 1,"duration": 25}) and stores it in MongoDB. The preference model update sub-unit calculates the preference score (frequency_score = 1 / 5 = 0.2, duration_score = 25 / 60 ≈ 0.417, preference_score = 0.6*0.2 + 0.4*0.417 ≈ 0.287), updates the data plan score using EMA (new_score = 0.3*0.287 + 0.7*0.5 = 0.436), and stores the model ({"preferences": {"traffic_plan": 0.436}}). The dynamic push unit optimizes push notifications through the following steps: The dynamic push unit reads the preference model (traffic_plan: 0.436). It queries the metadata storage module to obtain the package summary, prioritizes data packages, and generates a push list ([{"plan_id":"plan_005","summary":"80 yuan / month, 20GB data"}]). The list is transmitted to the information push module via REST API, and the display module prioritizes displaying the data package summary ("80 yuan / month, 20GB data").The button control module enables precise summary switching and detailed information browsing through efficient event capture and command generation; the user preference analysis unit provides personalized preference data through behavior recording and model updates; and the dynamic push unit optimizes package summary push, improving recommendation accuracy and user experience.

[0090] In addition, such as Figures 2 to 7As shown, another embodiment of the present invention provides a telecommunications service information display device for displaying telecommunications service package information, supporting switching of package summaries and interactive browsing of detailed information. The device includes a housing 1, a display screen 2, a control module 5, two switching buttons 7 (switching buttons 7-1 and 7-2), and two browsing buttons 6 (browsing buttons 6-1 and 6-2). The display device is an independent terminal, deployed in telecommunications business halls or self-service points, and communicates with the telecommunications service information processing system via Wi-Fi or 5G networks to obtain package data. The device runs an embedded Linux system (version 5.10) and uses firmware developed in Python 3.9 and C language to handle interactive logic. The housing 1 is made of ABS plastic and has dustproof and shockproof functions. The housing secures the display screen 2 with bolts and clips and contains an internal circuit board slot to accommodate the control module 5 and button circuits. The housing and display screen are connected via FPC (flexible printed circuit) to ensure stable signal transmission. The display screen 2 is a TFT-LCD with a resolution of 1024x600, a refresh rate of 60Hz, and supports 16-bit RGB color. The display initially shows a summary of a single plan (e.g., "80 yuan / month, 20GB data, 200 minutes of calls"), prioritizing the summary view. Upon triggering the browse button, it switches to a detailed information view (e.g., "Monthly fee 80 yuan, 20GB data, first month free"). The displayed content is received from the control module via an I2C interface, with an update latency of <50ms. Control module 5 is an embedded control unit containing the following components: Microprocessor: ARM Cortex-M4, 120MHz, running FreeRTOS firmware, handling button signals and display logic based on a state machine. The state machine maintains two display states: summary view (state: summary) and detailed information view (state: details). The microprocessor receives button commands, executes switching or browsing logic, and generates display commands (JSON format, e.g., {"action":"display_summary","kit_id":"plan_006"}). Button interface circuit: detects the physical contact between the switching button 7 and the browsing button 6 via GPIO pins. The buttons are mechanical microswitches, generating a low level (0V) when pressed and a high level (3.3V) when released. The circuit uses a 10ms debouncing delay and is interrupt-driven (rising / falling edge triggered) to generate electrical signals (e.g., {button:"browse_1", level: 0}). The signal is transmitted to the microprocessor with a detection delay of <5ms. The display driver circuit converts the microprocessor's display instructions into RGB signals via an SPI interface (10MHz) to update the display content. The instructions include the view type (summary or details) and content data (e.g., summary text or details paragraph). The refresh time is <50ms.Storage: 4MB flash memory, storing the current display state ({state:"summary", index: 2}) and package summary data (JSON array, e.g., [{"plan_id":"plan_005","summary":"80 yuan / month, 20GB data"}]). Data is retrieved from the metadata storage module via REST API, with a cache size supporting 50 packages. Toggle button 7 is used to switch package summaries or jump back from the details view to the summary view: First position (pressed): The button interface circuit detects a low-level signal, the microprocessor updates the summary index (7-1 increases index += 1, 7-2 decreases index -= 1), queries the metadata storage module (MongoDB, e.g., db.plans.find({"plan_id":"plan_006"})), and retrieves the next or previous summary (e.g., "90 yuan / month, 30GB data"). The display driver circuit updates the display, enabling the switching function and closing the current display (summary or details). Switching time <100ms. Second position (release): The microprocessor maintains the currently displayed content (summary or details) and disables the toggle function. Logic: In the details view, pressing any toggle button jumps back to the summary view, displaying a new summary. Browse button 6 is used to trigger the details display or browse the details page: First press (first position): The button interface circuit detects a low-level signal, the microprocessor switches to the details state, queries the metadata storage module, and retrieves the details (e.g., {"plan_id":"plan_005","details":"Monthly fee 80 yuan, 20GB traffic, first month free"}). The display driver circuit updates the display screen, enables the details display function, and disables the summary display. Switching time <50ms. Press again (first position): In the details view, the microprocessor triggers page browsing (6-1 scrolls down 100 pixels, 6-2 scrolls up), the display driver circuit updates the content (e.g., scrolls to "Applicable audience: 18-40 years old"), and enables the page browsing function. Scrolling response <30ms. Second position (release): The microprocessor maintains the currently displayed content (details or scroll position) and disables the summary display function. Logic: After the detailed information is displayed, the summary is no longer displayed. You can only return to the summary view by toggling button 7.

[0091] In actual use, the device displays package information interactively through the following steps: The device starts up, and display screen 2 shows the initial package summary ("80 yuan / month, 20GB data, 200 minutes of talk time", package plan_005, index 2). Control module 5 initializes GPIO interrupts, loads cached data (50 package summaries), and the microprocessor is set to summary mode. The operator presses switch button 7-1, the button interface circuit generates a low-level signal, the microprocessor increments the index to 3, queries the metadata storage module, and retrieves the summary of plan_006 ("90 yuan / month, 30GB data, 200 minutes of talk time"). The display driver circuit updates the display screen via SPI, showing the new summary. The operator presses browse button 6-1, the button interface circuit triggers an interrupt, the microprocessor switches to details mode, and queries the detailed information for plan_005 ("Monthly fee 80 yuan, 20GB data, first month free"). The display driver circuit updates the display screen, showing the detailed information, and closes the summary view. The operator presses browse button 6-1 again, the microprocessor triggers scrolling down, displaying "Suitable for: 18-40 years old". Press the browse button 6-2 to scroll up to the initial content. The display driver circuit updates in real time, ensuring smooth scrolling. In the details view, the operator presses the switch button 7-2, the microprocessor switches to summary mode, reduces the index to 1, and queries the summary of plan_004 ("70 yuan / month, 15GB data, 150 minutes of calls"). The display driver circuit updates the display screen, showing the new summary. The control module transmits the operation record ({"operator_id":"op_005","action":"browse_plan_005","duration": 30}) to the user preference analysis unit to optimize push priority. The display device provides stable package information interaction through a robust casing and efficient control module; the microprocessor and state machine logic ensure accurate summary switching and details browsing; it collaborates with the metadata storage module to support real-time data display; user behavior records optimize personalized push notifications, improving business hall efficiency and customer experience.

[0092] In this embodiment, the device also includes a housing 4, an identification unit 3, a triggering mechanism 9, and a switching mechanism 8. The housing 4 is made of ABS plastic and has an IP54 dust and water resistance rating. The housing 4 is connected to the casing 1, forming the outer protective layer of the device and housing the triggering mechanism 9 and the switching mechanism 8. The identification unit 3 uses a 13.56MHz NFC module (e.g., NXP PN532), supports the ISO / IEC 14443 standard, and identifies identification documents (e.g., second-generation ID cards). The unit connects to the control module 5 via an I2C interface (400kHz), scans the ID card, parses the chip data, and outputs identity information in JSON format. The switching mechanism 8 is a mechanical transmission system. Specifically, the mechanism consists of: a first outer frame 801 with two first positioning holes 802 for fixing two switching buttons 7 (7-1 and 7-2); a second outer frame 803 with two second positioning holes 804 for fixing two browsing buttons 6 (6-1 and 6-2); and a first rack 805 fixed to the first outer frame 801 with bolts. The second rack 807 is fixed to the second outer frame 803. The gear 806 meshes with the first rack 805 and the second rack 807. The bracket 808 supports the gear 806 and is rotatably connected via bearings. Two notches 812 are machined on the base 811. Magnetic blocks 810 are aligned with the notches 812 and fixed to the first rack 805 and the second rack 807 respectively. A stop block 809 is fixed to the magnetic block 810, with its bottom end contacting the base 811, limiting the maximum stroke of the first rack 805 and the second rack 807. A limiting rod 813 is fixed to the first rack 805 and the second rack 807, connected to the sliding groove of the base 811, constraining the linear movement of the racks. At least four trigger mechanisms 9 (corresponding to two switching buttons 7 and two browsing buttons 6) serve as the mechanical input interface for the buttons, enhancing tactile feedback. Each mechanism specifically includes: a trigger element 901 slidably connected to the first positioning hole 802 or the second positioning hole 804. The protrusion 902 is fixed to the first outer frame 801 or the second outer frame 803 by adhesive, limiting the travel of the trigger 901. When the trigger 901 is pressed, it stretches the tension spring 903, contacting the microswitch (rated 3.3V, 10mA), generating an electrical signal that is transmitted to the control module 5, simulating the signal of the browsing button 6 or the toggle button 7. The elastic deformation of the tension spring 903 can reset the browsing button 6 or the toggle button 7. After the tension spring 903 resets, the trigger 901 remains attached to the surface of the browsing button 6 or the toggle button 7 and will not trigger its activation. The gear 806 is located between the first rack 805 and the second rack 807, ensuring that when the first rack 805 moves upward, the second rack 807 moves downward, and vice versa. This design makes the movement directions of the first outer frame 801 and the second outer frame 803 opposite, reducing the possibility of accidentally triggering other buttons when the browsing button 6 is pressed.

[0093] In actual use, when the user needs to use the browsing button 6, pressing the corresponding trigger 901 will cause the tension spring 903 to deform during the downward movement of the trigger 901. Instead, it will cause the second rack 807 to indirectly mesh with the first rack 805 through the gear 806. At this time, the first rack 805 and the second rack 807 move in opposite directions. When the stop block 809 is attached to the top of the base 811, the bottom of the trigger 901 is just attached to the browsing button 6. Only by continuing to press the trigger 901 can the browsing button 6 be triggered to move. By setting the switching mechanism 8 and the trigger mechanism 9, the user can prevent accidental operation due to accidental touch, reduce the probability of pressing the wrong button, and improve the accuracy of the information pushed by the entire system.

[0094] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A telecommunications service information processing system, characterized in that, include: The identity information reading module is used to read the customer's identity information; The demand estimation module is connected to the identity information reading module and is used to estimate the customer's service needs based on the identity information. An information push module, connected to the demand estimation module, is used to push relevant telecommunications service information to customers based on the estimated service demand. The package information processing module is used to obtain package information from the telecommunications business database through the acquisition unit, and generate or update metadata about the package information, the metadata including newly generated metadata and previously stored metadata; A data lineage recording unit is used to create or modify a data lineage record of the package information by linking the previously obtained metadata with the newly generated metadata; The keyword extraction module, connected to the package information processing module, is used to extract keywords from the package information and generate a package summary, and to obtain the metadata through a data change detector and create meta tags, wherein the meta tags record the occurrence of data change events involving the package information; The display module, connected to the keyword extraction module, is used to display a single package summary and corresponding package information, wherein the package summary is displayed first. The selection module, connected to the display module and the keyword extraction module, is used to allow operators to select the package summary and trigger the display of package information corresponding to the selected package summary.

2. The telecommunications service information processing system according to claim 1, characterized in that, Also includes: A metadata storage module is used to store the metadata and meta tags, and associate the meta tags with the metadata; The demand forecasting module includes: The data analysis unit is used to analyze the customer's potential service needs based on the identity information and pre-stored user behavior data; The demand matching unit, connected to the data analysis unit, is used to match the potential service demands with telecommunications service packages and generate estimated demand results.

3. The telecommunications service information processing system according to claim 1, characterized in that, The package information processing module includes: A data acquisition unit is used to obtain package information from a telecommunications service database through an acquisition unit, and to create and / or obtain metadata about the package information, wherein the metadata includes newly generated metadata and previously obtained metadata; An information classification unit, connected to the data acquisition unit, is used to classify and organize the package information according to the package type and service content.

4. The telecommunications service information processing system according to claim 1, characterized in that, The keyword extraction module includes: The text analysis unit is used to perform natural language processing on the package information, extract keywords including data usage, call duration and price, and obtain the metadata through a data change detector to obtain information about data change events involving the package information; The data change detector is operable to examine two or more directly linked metadata fragments parsed from public records, and to calculate or determine based on this: How much data has been added to or removed from a record; Has the nature of the recorded content changed, and what type of change has occurred? Has sensitive data been added to or removed from the record? A summary generation unit, connected to the text analysis unit, is used to generate a package summary based on the keywords; The meta tag creation unit is used to create meta tags based on the acquisition of the metadata. The meta tags record the occurrence of the data change event and indicate the status of the package information when the package information is acquired.

5. The telecommunications service information processing system according to claim 1, characterized in that, Also includes: A button control module (5) is used to detect and process input signals from a control device having at least four buttons, the at least four buttons including two toggle buttons (7) and two browse buttons (6), wherein: Two toggle buttons (7) are used to switch between different package summaries displayed in the display module; Two browsing buttons (6) are used to trigger browsing of detailed information on the selected package summary; a key signal detection unit, connected to the key control module (5), is used to monitor the key events of the four buttons and generate corresponding operation instructions; a page switching unit, connected to the key signal detection unit and the display module, is used to switch the display of the package summary according to the operation instructions of the two switching buttons (7); a detailed information display unit, connected to the key signal detection unit and the display module, is used to display the detailed information of the selected package summary according to the operation instructions of the two browsing buttons (6).

6. The telecommunications service information processing system according to claim 5, characterized in that, The button control module (5) further includes: a user preference analysis unit, used to record the operator's browsing behavior of the package summary through the two browsing buttons (6) and analyze the operator's preference pattern; and a dynamic push unit, connected to the user preference analysis unit and the information push module, used to adjust the pushed package summary according to the preference pattern.

7. The telecommunications service information processing system according to claim 6, characterized in that, The button signal detection unit includes: an event capture subunit, used to capture the press and release events of the four buttons in real time and generate button signal data containing button type and time; and an instruction generation subunit, connected to the event capture subunit, used to generate corresponding page switching or detailed information display instructions based on the button signal data, and transmit the instructions to the page switching unit or detailed information display unit.

8. The telecommunications service information processing system according to claim 7, characterized in that, The user preference analysis unit includes: a behavior data recording subunit, used to record the frequency, duration and selected package type of the operator browsing detailed information through the two browsing buttons (6); and a preference model updating subunit, connected to the behavior data recording subunit, used to update the operator's preference model according to the behavior data, and transmit the updated preference model to the dynamic push unit to optimize the push order or content of the package summary.

9. A telecommunications service information display device, characterized in that, The device is applied to the telecommunications service information processing system according to any one of claims 1 to 8, and includes a housing (1), a display screen (2), a control module (5), two switching buttons (7) and two browsing buttons (6). The casing (1) is connected to the display screen (2), which is used to display a single package summary or corresponding package details, wherein the package summary is displayed first; The control module (5) is connected to the display screen (2), the switch button (7), and the browse button (6), and is used to process button input signals and control the content of the display screen. The control module (5) includes: The microprocessor receives button signals, executes switching or browsing logic based on the display status, and generates display instructions. A button interface circuit is used to detect the physical contact between the switch button (7) and the browse button (6) and generate an electrical signal; The display driver circuit is used to convert microprocessor instructions into display screen signals and update the display content. The memory is used to store the current display status and package summary data; The browse button (6) is used to trigger the display of package details or browse the details page: When the browsing button (6) is in the first position for the first time, the button interface circuit detects the electrical signal generated by physical contact, the microprocessor triggers the display of detailed information of the selected package summary, the display driving circuit updates the display screen content, enables the detailed information display function, and disables the display of the package summary; When the browse button (6) is in the first position again in the details view, the microprocessor triggers the browsing details page, the display driving circuit updates the content of the display screen (2), and enables the page browsing function; When the browse button (6) is in the second position, the microprocessor maintains the current display content and turns off the summary display function; The toggle button (7) is used to switch the package summary or jump from the details view to the package summary: When the switching button (7) is in the first position, the button interface circuit detects the electrical signal generated by physical contact, the microprocessor triggers the display of the next or previous package summary, the display driving circuit updates the display screen content, enables the switching function, and turns off the display of the current content; When the switching button (7) is in the second position, the microprocessor maintains the current display content and disables the switching function; When the browsing button (6) triggers the display of detailed information, the display screen (2) only displays the package details and the package summary is no longer displayed. The browsing button (6) is used to browse the detailed information page. The package summary view can only be accessed by switching the switch button (7) to jump back to the package summary view and switch to the next or previous package summary.

10. The telecommunications service information display device according to claim 9, characterized in that: It also includes at least four triggering mechanisms (9) and a switching mechanism (8); The switching mechanism (8) includes a first outer frame (801), two first positioning holes (802), a second outer frame (803), two second positioning holes (804), a first rack (805), a gear (806), a second rack (807), a bracket (808), two limit rods (813), two stops (809), two magnetic blocks (810), a base (811), and two notches (812). Both first positioning holes (802) are machined on the first outer frame (801). The first outer frame (801) is connected to the first rack (805). The first rack (805) meshes with the gear (806). The gear (806) meshes with the second rack (807). The second rack (807) is connected to the second outer frame (803). Both second positioning holes (804) are machined on the second outer frame (803). The gear (806) is rotatably connected to the bracket (808). The bracket (808) is connected to the base (811). The two notches... (812) is machined on the base (811), the notch (812) is matched with the size of the magnetic block (810) and can attract each other, the two magnetic blocks (810) are respectively connected to the first rack (805) and the second rack (807), the two magnetic blocks (810) are respectively connected to the two stops (809), the bottom end face of the stop (809) can contact the top end face of the base (811), the two limiting rods (813) are respectively connected to the first rack (805) and the second rack (807), and the two limiting rods (813) are slidably connected to the base (811); The triggering mechanism (9) includes a trigger (901), a protrusion (902), and a tension spring (903); The trigger (901) is slidably connected to the first positioning hole (802) or the second positioning hole (804), the protrusion (902) is connected to the first outer frame (801) or the second outer frame (803), and the tension spring (903) is connected between the lower part of the trigger (901) and the protrusion (902).

Images