Method and equipment for pushing key business to smart watch
By encrypting and transmitting streamlined card data from BI tools to a smartwatch for parsing and display, the problem of inefficient acquisition of critical business data during mobile and field work is solved, achieving efficient and secure data transmission and real-time insights.
Patent Information
- Application Number
- CN202511743467.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-25
- Publication Date
- 2026-03-03
AI Technical Summary
Traditional methods are inefficient in obtaining key business metrics in a timely manner when working on the go, during meeting breaks, or on-site.
By obtaining streamlined card data from BI tools, encrypting and transmitting it to the smartwatch using an intermediary service, and then parsing and displaying streamlined key business metrics or status icons on the smartwatch, including mini bar charts or line charts.
It enables efficient, secure, and streamlined data transmission from BI tools to smartwatches, improving work efficiency and meeting the needs of instant decision-making.
Smart Images
Figure CN121603555A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of business push, specifically to a method, apparatus, device, and computer-readable storage medium for pushing key business information to a smartwatch. Background Technology
[0002] In today's fast-paced business environment, managers need to stay informed about market dynamics and revenue data to adjust strategies. Frontline employees, such as sales staff, need to quickly access customer orders and product inventory information, while maintenance personnel need to check equipment operating parameters promptly. "Decision-making anytime, anywhere" has become a core requirement for business advancement. However, the inefficiencies of traditional work methods in mobile, meeting breaks, and field scenarios severely hinder the immediate acquisition of key business indicators and the implementation of decisions. From a mobile perspective, the traditional model relies on fixed terminals and intranet environments, making it difficult for managers to quickly access business systems while traveling or for frontline employees to access them while on the field. For example, when sales staff visit clients, they need to log in to the backend via computer to check the latest product pricing and inventory. If the network is unstable or there is no computer available, they cannot provide timely feedback to clients, delaying the closing process. Managers cannot view real-time revenue data while commuting, potentially missing the best opportunities for market adjustments. Meeting breaks are crucial for decision-making. In the traditional approach, key business indicators need to be compiled into documents and distributed by designated personnel. If attendees have not prepared relevant materials in advance, they cannot quickly verify data and align their decision-making direction. For example, after a cross-departmental meeting, operations managers need to understand user growth metrics to formulate promotional strategies, but because they lack data storage devices, they can only rely on memory or retrieve the data after the meeting, leading to stalled decision-making discussions. In on-site work scenarios, when maintenance personnel troubleshoot equipment malfunctions, the traditional method requires manually recording equipment parameters and then returning to the office to enter them into the system to query historical data. This method cannot retrieve equipment operating metrics and fault cases in real time, prolonging troubleshooting time. Researchers cannot access market share, competitor dynamics, and other metrics in real time on-site, affecting the accuracy and timeliness of research conclusions. While existing basic office tools can provide some data query functions, most are not optimized for key business metrics, resulting in slow data loading, unintuitive metric display, and inability to access data offline, making it difficult to meet the needs of immediate decision-making. Therefore, building a technical solution that supports access to key business metrics anytime, anywhere has become a core direction for breaking through traditional efficiency bottlenecks. Summary of the Invention
[0003] This application provides a method, apparatus, device, and computer-readable storage medium for pushing critical business information to a smartwatch, which can solve the technical problem in the prior art where critical business information cannot be obtained in a timely manner while on the move, during meeting breaks, or while working on-site, resulting in low efficiency.
[0004] In a first aspect, embodiments of this application provide a method for pushing critical business data to a smartwatch, including: Obtain card data of key business metrics subscribed to or triggered by users from BI tools, wherein the card data of key business metrics is card data formed after simplification. The card data is encrypted and transmitted to the push service of the smartwatch operating system via an intermediary service, and then transmitted to the smartwatch. The smartwatch then parses the card data to display a simplified set of key business indicators or status icons.
[0005] In conjunction with the first aspect, in one implementation, obtaining card data of key business metrics subscribed to or triggered by users from the BI tool includes: The JSON format data containing the user's metrics values, status, and timestamps is obtained through the RESTful API of the BI tool. The JSON format data is generated based on the user's preset subscription rules or alarm triggering conditions. By aggregating and formatting the JSON format data, card data containing core numbers and status identifiers is generated; Based on the display limitation information of the smartwatch screen, optimize the size and structure of the card data card; Obtain optimized card data based on key business metrics obtained through user subscriptions or triggers.
[0006] In conjunction with the first aspect, in one implementation, the step of encrypting and transmitting the card data to the push service of the smartwatch operating system via an intermediary service for transmission to the smartwatch terminal includes: The data card is encrypted using an end-to-end encryption method in the intermediate service; The encrypted card data is routed to the corresponding smartwatch push service for transmission to the smartwatch.
[0007] In conjunction with the first aspect, in one implementation, the step of parsing the card data on the smartwatch to display a simplified set of key business metrics or status icons includes: The application on the smartwatch receives and parses the card data, extracting the core numbers and status identifiers; The notification center on the smartwatch displays the status identifier as a status icon and the core number as a core number, wherein the status icon represents different business statuses; Alternatively, based on the chart data in the data card, a mini bar chart or line chart can be rendered, and the display range of the mini chart or line chart can be limited to fit the smartwatch screen.
[0008] In conjunction with the first aspect, in one implementation, after parsing the card data on the smartwatch and displaying simplified key business indicators or status icons, the method further includes: Click on the card data to display expanded details, including a timestamp or a brief description; The card data is marked as read or processed by swiping. The card data marked as read or processed is synchronized to the BI tool via the intermediate service.
[0009] In conjunction with the first aspect, in one implementation, obtaining JSON-formatted data containing user metrics, status, and timestamps via the RESTful API of the BI tool includes: Based on the subscription rules configured by the user in the BI tool, determine the key business metrics that need to be pushed. If the value of the key business indicator exceeds the preset threshold, an alarm data generation will be triggered. Extract the JSON format data of the alert data or subscription data through the RESTful API to obtain the JSON format data of the user's included metric values, status, and timestamps.
[0010] In conjunction with the first aspect, in one implementation, rendering the chart data from the data card into a mini bar chart or line chart includes: Extract key trend data points from the data cards; The key trend data points are processed based on the pixel density of the smartwatch screen to generate adapted chart data. The chart data is rendered using a preset color scheme, resulting in a mini bar chart or line chart, wherein the color scheme is consistent with the status icon.
[0011] Secondly, embodiments of this application provide a device for pushing critical business information to a smartwatch, the device comprising: The acquisition module is used to acquire card data of key business indicators subscribed to or triggered by users from BI tools, wherein the card data of key business indicators is card data formed after simplification. The push module is used to encrypt and transmit the card data to the push service of the smartwatch operating system through an intermediate service, so as to transmit it to the smartwatch. The smartwatch then parses the card data to display a simplified set of key business indicators or status icons.
[0012] Thirdly, embodiments of this application provide a device for pushing critical services to a smartwatch. The device for pushing critical services to a smartwatch includes a processor, a memory, and a program for pushing critical services to a smartwatch stored in the memory and executable by the processor. When the program for pushing critical services to a smartwatch is executed by the processor, it implements the steps of the method for pushing critical services to a smartwatch as described above.
[0013] Fourthly, embodiments of this application provide a computer-readable storage medium storing a program for pushing critical business data to a smartwatch. When the program for pushing critical business data to a smartwatch is executed by a processor, it implements the steps of the method for pushing critical business data to a smartwatch as described above.
[0014] The beneficial effects of the technical solutions provided in this application include: By acquiring card data of key business metrics subscribed to or triggered by users from BI tools, wherein the card data of key business metrics is simplified and processed, and transmitting the card data encrypted through an intermediary service to the push service of the smartwatch operating system, the simplified key business metrics or status icons are displayed on the smartwatch. This solves the technical problem of inefficiency caused by the inability to obtain key business data in a timely manner while on the move, during meeting breaks, or in the field. It realizes an efficient, secure, and simplified data transmission pipeline from BI tools to smartwatches, focusing on real-time insights on the wrist rather than viewing complete reports, thereby improving work efficiency. Attached Figure Description
[0015] Figure 1 This is a flowchart illustrating the first embodiment of the method for pushing critical business data to a smartwatch according to this application; Figure 2 This is a flowchart illustrating a second embodiment of the method for pushing critical business data to a smartwatch according to this application. Figure 3 This is a schematic diagram of the functional modules of an embodiment of the device for pushing key business information to a smartwatch according to this application; Figure 4 This is a schematic diagram of the hardware structure of a device that pushes critical business data to a smartwatch, as described in the embodiments of this application. Detailed Implementation
[0016] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.
[0017] First, some of the technical terms used in this application will be explained to help those skilled in the art understand this application.
[0018] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.
[0019] In a first aspect, embodiments of this application provide a method for pushing critical business data to a smartwatch.
[0020] In one embodiment, reference is made to Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the method for pushing critical business data to a smartwatch according to this application. Figure 1 As shown, methods for pushing critical business data to smartwatches include: Step S10: Obtain card data of key business metrics subscribed to or triggered by users from the BI tool, wherein the card data of the key business metrics is card data formed after simplification. As an example, this involves retrieving JSON-formatted data containing metric values, statuses, and timestamps from a user via a BI tool's RESTful API. This JSON data is generated based on user-preset subscription rules or alert triggering conditions. The JSON data is then aggregated and formatted to generate card data containing core numbers and status identifiers. The size and structure of the card data are optimized based on display limitations of the smartwatch screen. Finally, the optimized card data is retrieved based on key business metrics subscribed to or triggered by the user. For example, at the API layer: Utilizing the rich APIs (RESTful APIs are most common) provided by BI tools (such as Power BI, Tableau, Qlik, Looker, FineBI, etc.). This forms the basis of the link. Data Subscription and Triggering: Define the "data cards" or "alert rules" to be pushed. Subscription-based: Users pre-subscribe to specific streamlined views (such as "Sales Director Key Dashboard Summary") on the BI platform or accompanying management terminal. Trigger-based: Set thresholds for key metrics (such as inventory below safety level, server CPU > 90%), and automatically generate push notifications when the threshold is triggered. Data formatting: BI tools output the required data in a pre-defined, highly concise format (such as JSON) via API, including metric values, status, timestamps, and possibly small chart data points or image URLs.
[0021] Step S20: The card data is encrypted and transmitted to the push service of the smartwatch operating system through an intermediate service to be transmitted to the smartwatch. The card data is then parsed on the smartwatch to display simplified key business indicators or status icons. As an example, data cards are encrypted using end-to-end encryption in the intermediate service; the encrypted card data is then routed to the corresponding smartwatch push service for transmission to the smartwatch. The smartwatch application receives and parses the card data, extracting core numbers and status identifiers; the status identifiers are displayed as status icons and the core numbers as core numbers in the smartwatch's notification center, where the status icons represent different business states; alternatively, based on the chart data in the data cards, miniature bar charts or line charts are rendered, and the display range of the miniature charts or line charts is limited to adapt to the smartwatch screen. Key trend data points are extracted from the data cards, processed according to the pixel density of the smartwatch screen, and adapted chart data is generated. The chart data is rendered using a preset color scheme, resulting in miniature bar charts or line charts, where the color scheme is consistent with the status icons. For example, the intermediate service includes a connection hub. Connection Hub: Builds a secure middleware service (cloud service or enterprise on-premises deployment). It is responsible for: authenticating (OAuth, API Key, etc.) and interacting with the BI tool's API to obtain data. User Management: Link BI user accounts with smartwatch user / device identifiers. Data Processing and Optimization: Perform necessary processing, aggregation, and formatting on data obtained from BI, transforming it into a structure suitable for smartwatch display (extremely simplified). Push Routing: Determine which users / devices need to receive a push notification based on subscription relationships or trigger rules. Integrate with smartwatch platform push services. Security: Implement strict authentication, authorization, and data encryption (in transit and at rest) to ensure the security of sensitive business data. Smartwatch Side: Push Service Integration: Utilize the official push notification services provided by smartwatch operating systems (watchOS, Wear OS, HarmonyOS, etc.) (such as Apple Push Notification Service - APNs, Firebase Cloud Messaging - FCM for Wear OS). Smartwatch Application: Lite App / Complex Functionality: Develop a companion smartwatch app (complex functionality or a standalone app) whose main function is to receive push notifications from the intermediary service. Parse push content (text, values, status, micro-chart data). Render and display in notifications or within the app: Display key metrics, status icons, and micro-visual charts in a clear and easy-to-read layout. Offer simple interactions: tap the notification / card to expand and view a little more detail (but still very limited), or mark it as read / processed. Avoid complex operations.
[0022] The notification center displays: The most important scenario is that push cards are displayed directly in the watch's notification center, which users can see by simply raising their wrist.
[0023] In this embodiment, key business metrics card data subscribed to or triggered by users are obtained from BI tools. This key business metrics card data is simplified and processed. The card data is encrypted and transmitted to the push service of the smartwatch operating system via an intermediary service, and then transmitted to the smartwatch. The smartwatch parses the card data to display simplified key business metrics or status icons. This solves the technical problem in related technologies where key business metrics cannot be obtained in a timely manner while on the move, during meeting breaks, or in the field, leading to low efficiency. It achieves an efficient, secure, and simplified data transmission pipeline from BI tools to smartwatches, focusing on real-time insights on the wrist rather than viewing complete reports, thereby improving work efficiency.
[0024] In one embodiment, reference is made to Figure 2 , Figure 2 This is a flowchart illustrating a second embodiment of the method for pushing critical business data to a smartwatch according to this application. Figure 2 As shown, methods for pushing critical business data to smartwatches include: Step S100: Obtain card data of key business metrics subscribed to or triggered by users from the BI tool, wherein the card data of the key business metrics is card data formed after simplification. As an example, this involves retrieving JSON-formatted data containing metric values, statuses, and timestamps from a user via a BI tool's RESTful API. This JSON data is generated based on user-preset subscription rules or alert triggering conditions. The JSON data is then aggregated and formatted to generate card data containing core numbers and status identifiers. The size and structure of the card data are optimized based on display limitations of the smartwatch screen. Finally, the optimized card data is retrieved based on key business metrics subscribed to or triggered by the user. For example, at the API layer: Utilizing the rich APIs (RESTful APIs are most common) provided by BI tools (such as Power BI, Tableau, Qlik, Looker, FineBI, etc.). This forms the basis of the link. Data Subscription and Triggering: Define the "data cards" or "alert rules" to be pushed. Subscription-based: Users pre-subscribe to specific streamlined views (such as "Sales Director Key Dashboard Summary") on the BI platform or accompanying management terminal. Trigger-based: Set thresholds for key metrics (such as inventory below safety level, server CPU > 90%), and automatically generate push notifications when the threshold is triggered. Data formatting: BI tools output the required data in a pre-defined, highly concise format (such as JSON) via API, including metric values, status, timestamps, and possibly small chart data points or image URLs.
[0025] Step S200: The card data is encrypted and transmitted to the push service of the smartwatch operating system through an intermediate service, so as to be transmitted to the smartwatch. The card data is then parsed on the smartwatch to display simplified key business indicators or status icons. As an example, data cards are encrypted using end-to-end encryption in the intermediate service; the encrypted card data is then routed to the corresponding smartwatch push service for transmission to the smartwatch. The smartwatch application receives and parses the card data, extracting core numbers and status identifiers; the status identifiers are displayed as status icons and the core numbers as core numbers in the smartwatch's notification center, where the status icons represent different business states; alternatively, based on the chart data in the data cards, miniature bar charts or line charts are rendered, and the display range of the miniature charts or line charts is limited to adapt to the smartwatch screen. Key trend data points are extracted from the data cards, processed according to the pixel density of the smartwatch screen, and adapted chart data is generated. The chart data is rendered using a preset color scheme, resulting in miniature bar charts or line charts, where the color scheme is consistent with the status icons. For example, the intermediate service includes a connection hub. Connection Hub: Builds a secure middleware service (cloud service or enterprise on-premises deployment). It is responsible for: authenticating (OAuth, API Key, etc.) and interacting with the BI tool's API to obtain data. User Management: Link BI user accounts with smartwatch user / device identifiers. Data Processing and Optimization: Perform necessary processing, aggregation, and formatting on data obtained from BI, transforming it into a structure suitable for smartwatch display (extremely simplified). Push Routing: Determine which users / devices need to receive a push notification based on subscription relationships or trigger rules. Integrate with smartwatch platform push services. Security: Implement strict authentication, authorization, and data encryption (in transit and at rest) to ensure the security of sensitive business data. Smartwatch Side: Push Service Integration: Utilize the official push notification services provided by smartwatch operating systems (watchOS, Wear OS, HarmonyOS, etc.) (such as Apple Push Notification Service - APNs, Firebase Cloud Messaging - FCM for Wear OS). Smartwatch Application: Lite App / Complex Functionality: Develop a companion smartwatch app (complex functionality or a standalone app) whose main function is to receive push notifications from the intermediary service. Parse push content (text, values, status, micro-chart data). Render and display in notifications or within the app: Display key metrics, status icons, and micro-visual charts in a clear and easy-to-read layout. Offer simple interactions: tap the notification / card to expand and view a little more detail (but still very limited), or mark it as read / processed. Avoid complex operations.
[0026] The notification center displays: The most important scenario is that push cards are displayed directly in the watch's notification center, which users can see by simply raising their wrist.
[0027] Step S300: Click on the card data to display extended details including a timestamp or brief description; Step S400: Mark the card data as read or processed by swiping. Step S500: Synchronize the card data marked as read or processed to the BI tool via an intermediate service.
[0028] Demonstratingly, users can tap on card data to display expanded details including timestamps or brief descriptions; swipe to mark card data as read or processed; and synchronize the marked read or processed card data to the BI tool via an intermediary service. Through an extremely streamlined data card format and micro-visualization technology, adapted to the small screen of smartwatches, it enables "instant" business insights via push notifications and simple interactions, solving the access efficiency problem of traditional BI dashboards in mobile scenarios, and providing feedback to the BI tool by marking card data as read or processed via swipe.
[0029] In this embodiment, key business metrics card data subscribed to or triggered by users are obtained from BI tools. This key business metrics card data is simplified and processed. The card data is encrypted and transmitted to the push service of the smartwatch operating system via an intermediary service, and then transmitted to the smartwatch. The smartwatch parses the card data to display simplified key business metrics or status icons. This solves the technical problem in related technologies where key business metrics cannot be obtained in a timely manner while on the move, during meeting breaks, or in the field, leading to low efficiency. It achieves an efficient, secure, and simplified data transmission pipeline from BI tools to smartwatches, focusing on real-time insights on the wrist rather than viewing complete reports, thereby improving work efficiency.
[0030] Secondly, embodiments of this application also provide a device for pushing critical business information to a smartwatch.
[0031] In one embodiment, reference is made to Figure 3 , Figure 3 This is a functional module diagram of an embodiment of the device for pushing key business information to a smartwatch, as described in this application. Figure 3 As shown, devices that push critical business data to smartwatches include: The acquisition module 10 is used to acquire card data of key business indicators subscribed or triggered by users from BI tools, wherein the card data of key business indicators is card data formed after simplification. The push module 20 is used to encrypt and transmit the card data to the push service of the smartwatch operating system through an intermediate service, so as to transmit it to the smartwatch. The push module 20 is used to parse the card data on the smartwatch to display simplified key business indicators or status icons.
[0032] Furthermore, in one embodiment, the acquisition module 10 is used for: The JSON format data containing the user's metrics values, status, and timestamps is obtained through the RESTful API of the BI tool. The JSON format data is generated based on the user's preset subscription rules or alarm triggering conditions. By aggregating and formatting the JSON format data, card data containing core numbers and status identifiers is generated; Based on the display limitation information of the smartwatch screen, optimize the size and structure of the card data card; Obtain optimized card data based on key business metrics obtained through user subscriptions or triggers.
[0033] Furthermore, in one embodiment, the push module 20 is used for: The data card is encrypted using an end-to-end encryption method in the intermediate service; The encrypted card data is routed to the corresponding smartwatch push service for transmission to the smartwatch.
[0034] Furthermore, in one embodiment, the device for pushing critical business information to the smartwatch further includes a new module for: The application on the smartwatch receives and parses the card data, extracting the core numbers and status identifiers; The notification center on the smartwatch displays the status identifier as a status icon and the core number as a core number, wherein the status icon represents different business statuses; Alternatively, based on the chart data in the data card, a mini bar chart or line chart can be rendered, and the display range of the mini chart or line chart can be limited to fit the smartwatch screen.
[0035] Furthermore, in one embodiment, the device for pushing critical business information to the smartwatch further includes a new module for: Click on the card data to display expanded details, including a timestamp or a brief description; The card data is marked as read or processed by swiping. The card data marked as read or processed is synchronized to the BI tool via an intermediary service.
[0036] Furthermore, in one embodiment, the device for pushing critical business information to the smartwatch further includes a new module for: Based on the subscription rules configured by the user in the BI tool, determine the key business metrics that need to be pushed. If the value of the key business indicator exceeds a preset threshold, an alarm data generation will be triggered. Extract the JSON format data of the alert data or subscription data through the RESTful API to obtain the JSON format data of the user's included metric values, status, and timestamps.
[0037] Furthermore, in one embodiment, the device for pushing critical business information to the smartwatch further includes a new module for: Extract key trend data points from the data cards. The key trend data points are processed based on the pixel density of the smartwatch screen to generate adapted chart data. The chart data is rendered using a preset color scheme, resulting in a mini bar chart or line chart, wherein the color scheme is consistent with the status icon.
[0038] The functions of each module in the device that pushes key business information to the smartwatch correspond to the steps in the method embodiment that pushes key business information to the smartwatch. Their functions and implementation processes will not be described in detail here.
[0039] Thirdly, embodiments of this application provide a device for pushing critical business data to a smartwatch. The device for pushing critical business data to a smartwatch can be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.
[0040] Reference Figure 4 , Figure 4 This is a schematic diagram of the hardware structure of a device for pushing critical services to a smartwatch, as described in an embodiment of this application. In this embodiment, the device for pushing critical services to a smartwatch may include a processor, memory, a communication interface, and a communication bus.
[0041] The communication bus can be of any type and is used to interconnect the processor, memory, and communication interface.
[0042] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces. These interfaces enable interconnection of internal devices within the smartwatch to push critical business data to it, and also enable interconnection between the smartwatch and other devices (such as other computing devices or user devices). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user devices can be displays, keyboards, etc.
[0043] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.
[0044] The processor can be a general-purpose processor, which can call a program stored in memory to push critical services to the smartwatch and execute the method for pushing critical services to the smartwatch provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the program for pushing critical services to the smartwatch is called can refer to the various embodiments of the method for pushing critical services to the smartwatch in this application, and will not be repeated here.
[0045] Those skilled in the art will understand that Figure 4 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0046] Fourthly, embodiments of this application also provide a computer-readable storage medium.
[0047] The present application stores a program on a computer-readable storage medium for pushing critical business information to a smartwatch, wherein when the program for pushing critical business information to a smartwatch is executed by a processor, it implements the steps of the method for pushing critical business information to a smartwatch as described above.
[0048] The method implemented when the program for pushing critical business data to a smartwatch is executed can be found in various embodiments of the method for pushing critical business data to a smartwatch in this application, and will not be repeated here.
[0049] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0050] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.
[0051] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.
[0052] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.
[0053] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.
[0054] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.
[0055] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.
Claims
1. A method for pushing key business information to a smartwatch, characterized in that, include: Obtain card data of key business metrics subscribed to or triggered by users from BI tools, wherein the card data of key business metrics is card data formed after simplification. The card data is encrypted and transmitted to the push service of the smartwatch operating system via an intermediary service, and then transmitted to the smartwatch. The smartwatch then parses the card data to display a simplified set of key business indicators or status icons.
2. The method for pushing critical business data to a smartwatch as described in claim 1, characterized in that, The card data obtained from the BI tool for key business metrics subscribed to or triggered by users includes: The JSON format data containing the user's metrics values, status, and timestamps is obtained through the RESTful API of the BI tool. The JSON format data is generated based on the user's preset subscription rules or alarm triggering conditions. By aggregating and formatting the JSON format data, card data containing core numbers and status identifiers is generated; Based on the display limitation information of the smartwatch screen, optimize the size and structure of the card data card; Obtain optimized card data based on key business metrics obtained through user subscriptions or triggers.
3. The method for pushing critical business data to a smartwatch as described in claim 1, characterized in that, The step of encrypting and transmitting the card data to the push service of the smartwatch operating system via an intermediary service for transmission to the smartwatch terminal includes: The data card is encrypted using an end-to-end encryption method in the intermediate service; The encrypted card data is routed to the corresponding smartwatch push service for transmission to the smartwatch.
4. The method for pushing critical business data to a smartwatch as described in claim 1, characterized in that, The step of parsing the card data on the smartwatch to display concise key business metrics or status icons includes: The application on the smartwatch receives and parses the card data, extracting the core numbers and status identifiers; The notification center on the smartwatch displays the status identifier as a status icon and the core number as a core number, wherein the status icon represents different business statuses; Alternatively, based on the chart data in the data card, a mini bar chart or line chart can be rendered, and the display range of the mini chart or line chart can be limited to fit the smartwatch screen.
5. The method for pushing critical business data to a smartwatch as described in claim 1, characterized in that, After parsing the card data on the smartwatch and displaying simplified key business metrics or status icons, the process also includes: Click on the card data to display expanded details, including a timestamp or a brief description; The card data is marked as read or processed by swiping. The card data marked as read or processed is synchronized to the BI tool via the intermediate service.
6. The method for pushing critical business data to a smartwatch as described in claim 2, characterized in that, The process of retrieving user-defined JSON data, including metrics, status, and timestamps, via the BI tool's RESTful API includes: Based on the subscription rules configured by the user in the BI tool, determine the key business metrics that need to be pushed. If the value of the key business indicator exceeds a preset threshold, an alarm data generation will be triggered. Extract the JSON format data of the alert data or subscription data through the RESTful API to obtain the JSON format data of the user's included metric values, status, and timestamps.
7. The method for pushing critical business data to a smartwatch as described in claim 4, characterized in that, The step of rendering a mini bar chart or line chart based on the chart data in the data card includes: Extract key trend data points from the data cards; The key trend data points are processed based on the pixel density of the smartwatch screen to generate adapted chart data. The chart data is rendered using a preset color scheme, resulting in a mini bar chart or line chart, wherein the color scheme is consistent with the status icon.
8. A device for pushing critical business information to a smartwatch, characterized in that, The device for pushing critical business information to a smartwatch includes: The acquisition module is used to acquire card data of key business indicators subscribed to or triggered by users from BI tools, wherein the card data of key business indicators is card data formed after simplification. The push module is used to encrypt and transmit the card data to the push service of the smartwatch operating system through an intermediate service, so as to transmit it to the smartwatch. The smartwatch then parses the card data to display a simplified set of key business indicators or status icons.
9. A device for pushing critical business data to a smartwatch, characterized in that, The device for pushing critical business data to a smartwatch includes a processor, a memory, and a program stored in the memory and executable by the processor for pushing critical business data to a smartwatch. When the program for pushing critical business data to a smartwatch is executed by the processor, it implements the steps of the method for pushing critical business data to a smartwatch as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program for pushing critical services to a smartwatch, wherein when the program for pushing critical services to a smartwatch is executed by a processor, it implements the steps of the method for pushing critical services to a smartwatch as described in any one of claims 1 to 7.