Methods and devices for enabling product capabilities in multi-level IoT platform scenarios

Abstract

This invention discloses a method and device for enabling product capabilities in a multi-level IoT platform scenario. The method includes automatically discovering and managing dependencies between three types of products: IoT platform services, IoT application services, and terminal product services. It identifies key fields in the applications and public products sold by lower-level nodes and accurately matches them with internal service fields. Dynamic interface registration and intelligent business logic orchestration are also included. Lower-level nodes dynamically register their provided services through a capability gateway, including interface services such as account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification. Business logic orchestration is then performed, and interface call strategies are dynamically adjusted to achieve optimal orchestration and call of business logic. This invention enables a series of processes such as activation, acceptance, installation, and maintenance of local products based on sub-nodes in a two-level IoT platform scenario. It allows for IT process tracking and is beneficial for product operation and maintenance.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) technology, and specifically to a method and device for enabling product capabilities in a multi-level architecture IoT platform scenario. Background Technology

[0002] Currently, the capability development and business encapsulation of IoT products are completed at centralized nodes. Each lower-level region can only accept IoT product orders based on a centralized and unified CRM system, and cannot develop and encapsulate localized IoT products. However, with the huge market demand and the formation of the "1+N" two-tier architecture, each lower-level region urgently needs to develop product capability encapsulation, activation, acceptance, installation and maintenance based on sub-nodes.

[0003] The existing technical solution mainly involves configuring and listing products at centralized nodes, with lower-level nodes ordering through the provincial CRM, calling the two-level service activation system, and realizing product acceptance and activation through the synchronization of centralized and sub-node orders.

[0004] (1) Centralized Node Configuration and Sub-Node Product Deployment: On the centralized platform, standardized product configurations are performed based on the characteristics and requirements of IoT products. These configurations include, but are not limited to, device type, communication protocol, data processing rules, and security policies. After configuration, the products are deployed to each sub-node, i.e., the local subordinate companies, in a standardized form.

[0005] (2) Subordinate nodes order through the provincial CRM: Subordinate nodes use the CRM to receive IoT product order requests from customers. The provincial CRM system will automatically match the product configuration on the centralized platform to ensure the automation and accuracy of the ordering process.

[0006] (3) Calling the two-level service activation system: After the order request is confirmed, the provincial CRM system will automatically call the service activation system of the centralized platform and the local service activation system.

[0007] (4) Synchronization of centralized and sub-node orders to achieve product acceptance and activation: In order to ensure service consistency and timeliness, a real-time order synchronization mechanism has been established between the centralized platform and each sub-node. Once an order request is processed by the provincial CRM system, the relevant information will be immediately synchronized to the centralized platform, triggering the subsequent product acceptance and activation process. At the same time, the sub-nodes will also receive corresponding notifications and prepare to perform local service activation operations.

[0008] The main technical problems existing in the current technical solutions include:

[0009] (1) Data synchronization delay: There may be a delay in order synchronization between the centralized platform and the sub-nodes, especially when the network conditions are poor or the system load is high, which will affect the timeliness of product acceptance and activation.

[0010] (2) High configuration complexity: With the diversification of IoT application scenarios, the complexity of product configuration is constantly increasing. It is difficult to simplify the configuration process and reduce the error rate while ensuring flexibility. The configuration of sub-node products through centralized nodes and the acceptance of products through sub-nodes involve many IT systems, which can easily lead to order blockage and make it difficult to locate the problem.

[0011] (3) Cross-regional consistency is difficult to guarantee: There is a lack of unified technical specifications and standards. Due to the differences in local policies, network environment and customer needs, it is difficult to fully achieve consistency in product configuration and user experience. If many sub-node platforms are involved in local product acceptance and activation, the workload of transformation is large and difficult to maintain.

[0012] Explanation of related terms:

[0013] The Internet of Things (IoT) uses various information sensing devices to collect real-time information about any object or process that needs to be monitored, connected, or interacted with, enabling interconnection between objects and between objects and people.

[0014] Multi-level IoT platform architecture: refers to an IoT platform architecture that includes an edge layer, access layer, core layer and application layer, where each layer communicates with each other through standardized interfaces to achieve efficient data flow and processing.

[0015] Product capability activation: The process of activating and configuring specific services or functions for specific users or applications on an IoT platform, such as device management, data stream analysis, and security policies.

[0016] Capability Gateway: A capability gateway is a key component in a microservice architecture. As the front-end entry point, it handles external requests and routes them to back-end services. Capability gateways not only provide API routing, authentication and authorization, and load balancing, but also perform traffic control, circuit breaking and degradation, and log auditing, thereby enhancing system stability and security. In IoT platforms, capability gateways play a crucial role in service registration and discovery, and dynamic interface management, ensuring high service availability and efficient invocation.

[0017] DICT refers to the convergence of digital information technology and communication technology. DICT applications encompass multiple fields such as cloud computing, big data, the Internet of Things (IoT), and artificial intelligence (AI), aiming to provide comprehensive IT solutions for businesses and individuals by integrating these technologies, thereby promoting industrial upgrading and digital transformation. In the context of IoT platforms, DICT applications emphasize achieving deep perception and efficient management of the physical world through data collection, analysis, and intelligent decision-making.

[0018] NLP (Natural Language Processing) is a branch of artificial intelligence that focuses on enabling computers to understand, interpret, and generate human language. NLP technology involves multiple aspects such as speech recognition, semantic analysis, sentiment analysis, and machine translation, helping computers parse the meaning of text, identify entities and relationships, thereby achieving automated processing and intelligent decision-making. In IoT platforms, NLP is used to automatically identify and map key fields in product information, improving the accuracy and efficiency of data processing.

[0019] Metadata: Metadata refers to data that describes data, providing detailed information about the data, such as its source, format, creation date, author, and copyright information. In IoT platforms, metadata is used to describe the attributes and relationships of entities such as sensors, devices, and applications, facilitating data organization, retrieval, and management. Through metadata management, dependencies between products can be automatically identified, enabling automated service configuration and optimization.

[0020] Service Registry: A service registry is a crucial component of a microservices architecture. It stores and manages information about service instances, such as service addresses, ports, and statuses. Service registries are typically used in conjunction with service discovery mechanisms, enabling service consumers to dynamically find and invoke service providers without hard-coding service addresses. In IoT platforms, service registries facilitate dynamic service registration and discovery, enhancing system scalability and robustness.

[0021] Event-Driven Architecture (EDA) is a distributed computing pattern where applications run in response to streams of events, rather than through a traditional request-response model. In EDA, events are generated by components in the system and then passed to interested subscribers for processing. This architectural pattern improves system responsiveness and flexibility, enabling real-time processing of large numbers of concurrent events. It is suitable for scenarios requiring high responsiveness and scalability, such as real-time data analysis and processing in IoT platforms. Summary of the Invention

[0022] The present invention proposes a method and device for enabling product capabilities in a multi-level architecture IoT platform scenario, which can at least solve one of the technical problems in the background art.

[0023] To achieve the above objectives, the present invention adopts the following technical solution:

[0024] A method for enabling product capabilities in a multi-level IoT platform scenario includes the following steps.

[0025] Product service configuration and intelligent dependency management include automatically discovering and managing the dependencies between three types of products: IoT platform services, IoT application services, and terminal product services. It identifies key fields in the applications sold and public products in lower-level nodes and accurately matches them with internal service fields to achieve high-efficiency and high-accuracy data synchronization.

[0026] Dynamic interface registration and intelligent business logic orchestration include lower-level nodes dynamically registering the services they provide through the capability gateway, including interface services such as account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification, and performing business logic orchestration, dynamically adjusting interface call strategies to achieve optimal orchestration and call of business logic.

[0027] Furthermore, product service configuration and intelligent dependency management include,

[0028] S2.1 Lower-level nodes apply for and create access-type products and functional products based on the product management platform, so that the acceptance personnel can process orders;

[0029] S2.2 Product Information Configuration: Terminal products that have completed docking and testing at the sub-nodes are applied to become public products, generating public product information pubProductId; at the same time, based on the sub-node application interface specifications, application products are created and developed, generating sales application information pubAppId, and configuring key application docking addresses, including business synchronization URL address, message push URL address, and single sign-on URL address, to ensure data synchronization, message push, and a seamless user login experience;

[0030] The business synchronization URL is used to synchronize the SaaS business information subscribed by customers to the SaaS platform;

[0031] The message push URL is used to push and synchronize uplink data from the terminal device of the SaaS application to the SaaS platform;

[0032] The single sign-on URL allows customers who subscribe to SaaS applications to directly access the SaaS platform without logging in, based on the sub-nodes, to use the applications and view and manage their data.

[0033] S2.3 Perform field mapping, using NLP technology algorithms to automatically identify and map key fields in product information.

[0034] Furthermore, the products in step S2.1 include,

[0035] IoT Platform Service: As the foundational layer, it provides core functional services, including terminal access, terminal management, and application enablement. The activation of this service will generate sub-node accounts and tenants, providing infrastructure support for subsequent services.

[0036] IoT Application Services: Relying on IoT platform services, it further provides application-level support. When activated, it generates application triple information: appId, appKey, and secret, which are used to create applications under specific tenants and realize application-level management and data processing.

[0037] xx terminal product: As a functional layer product, it relies on IoT application services. After activation, it generates product information, allows the creation of terminal products based on sub-nodes, and can be attached to application products to realize the management and data interaction of terminal devices.

[0038] Furthermore, product service configuration and intelligent dependency management involve the following steps in building dependencies:

[0039] Automated identification and configuration of product dependencies: Utilizes a service registry and metadata management to automatically identify and configure dependencies between products;

[0040] Dependency graph visualization: Construct a dependency graph to intuitively display the hierarchical dependencies between products, making it easier for operations and maintenance personnel to understand and maintain.

[0041] Furthermore, step S2.3 specifically includes,

[0042] Data preprocessing: Cleaning and standardizing product information text, removing irrelevant characters and formatting differences;

[0043] Feature extraction: Using NLP techniques to extract keywords and phrases from text;

[0044] Model training: Based on historical datasets, train machine learning models to identify and classify key fields;

[0045] Automatic mapping: Matches and maps extracted key fields with fields in the database to automatically update product information;

[0046] Validation and Correction: Set up a validation mechanism, manually review the automatic mapping results, correct erroneous mappings, and continuously optimize the model.

[0047] Furthermore, step S2.3 specifically also includes,

[0048] In dependency chains, to ensure that changes in upstream product information are quickly reflected in downstream products, the following technical methods are employed:

[0049] Event-driven architecture (EDA): When upstream product information changes, an event is triggered to notify downstream products to update.

[0050] Asynchronous message queues: Use message queues to process product information change events asynchronously, avoiding blocking the main process;

[0051] Version control: Add version numbers to product information, track every change, and ensure data consistency;

[0052] Dependency monitoring: Monitor the dependencies between products in real time, and immediately initiate the synchronization process once an upstream change is detected;

[0053] Data verification and rollback: During the synchronization process, data verification is performed to ensure the integrity and correctness of information; if errors are found, a rollback operation is performed to restore the state to that before the change.

[0054] Furthermore, dynamic interface registration and intelligent orchestration of business logic include,

[0055] S3.1 Dynamic Interface Registration: Lower-level nodes adopt a dynamic registration mechanism, registering interface services such as account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification through the capability gateway.

[0056] The capability gateway verifies the received registration requests to ensure the completeness and legality of the service description information;

[0057] Once verified, the service information is stored in the service directory, using a database or caching system for quick querying and updating.

[0058] S3.2 Business Logic Orchestration; The capability gateway has a built-in business logic orchestration engine that can dynamically adjust interface call strategies based on current network status, resource availability, and historical call success rates.

[0059] Meanwhile, the orchestration engine supports advanced features such as A / B testing and canary releases to ensure a smooth transition between old and new services and reduce the impact on existing business.

[0060] S3.3 Interface Call Flow; This flow involves key interfaces including account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification.

[0061] Furthermore, step S3.1 also includes,

[0062] Dynamic service catalog updates: The capability gateway maintains a dynamic service catalog, which is automatically updated whenever a new service is registered or an existing service is updated.

[0063] Service Invocation and Management: Clients obtain the interface information of the required services by querying the service catalog, and then invoke the services. The capability gateway is responsible for routing and authorization verification to ensure the security and validity of service invocation.

[0064] Furthermore, step S3.3 specifically includes,

[0065] (1) Customer account initialization: The customer service personnel create customer information and order IoT platform services in the lower-level customer relationship management system; the system automatically calls the account synchronization interface to generate a tenant ID and notifies the customer of the login credentials via SMS. This step ensures that the customer can access the sub-node platform.

[0066] (2) Application service configuration: Based on the tenant created in the first step, the personnel in charge call the application creation interface through the lower-level IT system to create an application instance under the tenant account; the system returns an application triple: appId, appKey, and secret, which are used for authentication of subsequent service calls;

[0067] (3) Terminal product ordering and creation: The receiving personnel initiates the ordering of terminal products, and the lower-level IT system calls the product creation interface to create a terminal product instance under the specified tenant and return the product ID and master key; multiple product orders are supported and encapsulated in a list structure.

[0068] (4) Business relationship synchronization: After completing the first three steps, the lower-level IT system calls the business synchronization interface to synchronize the product relationship to the SaaS platform, realize the binding of order information, and the system returns the SaaS application platform account and password, and notifies the customer via SMS to complete the product activation and acceptance process.

[0069] (5) Device registration and management: After the terminal device is shipped out, the lower-level IT system calls the device registration interface to register the device in the specified product instance and returns the device ID as a unique identifier.

[0070] (6) Equipment activation verification: After the installation and maintenance personnel complete the equipment installation, they can scan the equipment label, call the equipment activation verification interface, query the online status of the equipment, and confirm that the installation is complete.

[0071] After completing (1)-(6), the order is reported as completed, realizing product ordering, acceptance, installation and maintenance.

[0072] In another aspect, the present invention also discloses a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform the steps of the method described above.

[0073] In another aspect, the present invention also discloses a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the method described above.

[0074] As can be seen from the above technical solutions, the method and apparatus for enabling product capabilities in a multi-level architecture IoT platform scenario of the present invention can perform a series of steps such as enabling, accepting, installing and maintaining local products based on sub-nodes in a two-level architecture IoT platform scenario. It can track IT processes, which is beneficial to product operation and maintenance and effectively solves the above problems.

[0075] The method proposed in this invention can perform a series of processes such as activation, acceptance, installation and maintenance of local products based on sub-nodes in a two-level IoT platform scenario. It can track IT processes and is beneficial to product operation and maintenance.

[0076] This invention enables lower-level nodes to autonomously create and configure products through product service configuration and intelligent dependency management, constructing a multi-layered product dependency relationship, including IoT platform services, IoT application services, and terminal product services. This mechanism not only simplifies the product ordering process but also improves operational efficiency and product management transparency through automated dependency identification and configuration, and dependency graph visualization. Furthermore, the application of NLP technology enables automatic mapping of product information fields, reducing human error and ensuring real-time updates and consistency of product information.

[0077] This invention utilizes dynamic interface registration and intelligent business logic orchestration. Lower-level nodes achieve dynamic registration and management of interfaces through a capability gateway, ensuring high service availability and security. The introduction of a business logic orchestration engine intelligently adjusts interface call strategies based on dynamic factors such as real-time network status and resource availability, supporting A / B testing and canary releases, ensuring a smooth transition between old and new services and reducing the risk of business interruption. The optimized interface call process, from customer account initialization to device activation verification, has been rigorously designed and validated at every step, ensuring service continuity and user experience.

[0078] The above-mentioned technical means of the present invention achieve the following significant effects:

[0079] It enhances product customization and localization capabilities: lower-level nodes can independently create and manage localized IoT products, meeting the specific needs of different regions and enhancing market competitiveness.

[0080] Data synchronization and configuration efficiency have been optimized: Through event-driven architecture, asynchronous message queues and other technologies, data synchronization latency has been significantly shortened, configuration processes have been simplified, and the overall system response speed and flexibility have been improved.

[0081] Enhanced service reliability and user experience: Dynamic interface registration and intelligent orchestration mechanisms ensure high service availability, maintaining service continuity and high quality even under network fluctuations or resource constraints.

[0082] It facilitates cross-regional consistency: the automated management and real-time update mechanism of dependencies effectively solves the complexity of cross-regional product configuration, ensures the consistency and standardization of services nationwide, can be promoted and replicated in batch project construction, and reduces the workload of transformation and maintenance. Attached Figure Description

[0083] Figure 1 This is a flowchart of an embodiment of the present invention;

[0084] Figure 2 This is a flowchart of the interface call process in an embodiment of the present invention. Detailed Implementation

[0085] 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 some embodiments of the present invention, but not all embodiments.

[0086] This invention proposes a unified standard method for product capability activation in a two-tier IoT platform scenario. This method, while minimizing resource costs, enables localized IT processes such as activation, acceptance, installation, and maintenance of IoT products based on distributed nodes, further efficiently supporting the development of local IoT businesses. The method flow is as follows: Figure 1 As shown, the specific objectives include:

[0087] 1. Product service configuration and intelligent dependency management

[0088] The system automatically discovers and manages the dependencies between three types of products: IoT platform services, IoT application services, and terminal product services. It identifies key fields in the applications sold and public products in lower-level nodes and accurately matches them with internal service fields to achieve highly efficient and accurate data synchronization.

[0089] 2. Dynamic interface registration and intelligent orchestration of business logic

[0090] Lower-level nodes dynamically register the services they provide through the capability gateway, including interface services such as account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification. They also perform business logic orchestration, dynamically adjust interface call strategies, and achieve optimal orchestration and call of business logic.

[0091] The following is a detailed explanation:

[0092] 1. Background and Requirements Analysis

[0093] With the development of industrial digitalization, DICT applications are emerging in an endless stream, and the demand for IoT platforms in various regions is becoming increasingly urgent. IoT platforms are gradually forming a "1+N" two-tier architecture, namely one centralized node and N sub-nodes, jointly supporting the access and data import of internal and external sensing terminals, efficient management of all types and scenarios of devices, and multi-dimensional fusion of sensing data standards, empowering the digital transformation of various industries. Currently, the capability building and business encapsulation of IoT products are completed at the centralized node. Each lower-level region can only process IoT product orders based on a unified centralized CRM system, making it impossible to build and encapsulate localized IoT products. This also results in a series of problems such as data synchronization delays, configuration complexity, and cross-regional consistency.

[0094] 2. Product service configuration and intelligent dependency management.

[0095] 2.1 Lower-level nodes apply for and create access-type and functional products based on the product management platform, which are then used by the processing personnel to process orders, as shown in the table below:

[0096] Product Name Product Type Dependency IoT platform services Access products none Internet of Things (IoT) application services Access products Relying on IoT platform services xx terminal product service Functional products Relying on IoT application services

[0097] IoT Platform Services: As the foundational layer, this service provides core functionalities, including but not limited to terminal access, terminal management, and application enablement. Activation of this service will generate sub-node accounts and tenants, providing infrastructure support for subsequent services.

[0098] IoT Application Services: Relying on IoT platform services, these services further provide application-level support. Upon activation, an application triplet (appId, appKey, secret) is generated to create applications under a specific tenant, enabling application-level management and data processing.

[0099] xx terminal product: As a functional layer product, it relies on IoT application services. After activation, it generates product information (productId, masterKey), allows the creation of terminal products based on sub-nodes, and can be attached to application products to realize the management and data interaction of terminal devices;

[0100] The main steps involved in building dependencies are as follows:

[0101] Automated identification and configuration of product dependencies: Utilizing service registries (such as Consul and Eureka) and metadata management, dependencies between products are automatically identified and configured. For example, the IoT platform service, as the foundational layer, does not depend on other services; the IoT application service depends on the IoT platform service, while the xx terminal product depends on the IoT application service.

[0102] Dependency graph visualization: Construct a dependency graph to intuitively display the hierarchical dependencies between products, making it easier for operations and maintenance personnel to understand and maintain.

[0103] 2.2 Product Information Configuration: Terminal products that have completed integration and testing at each node will be designated as public products, generating public product information (pubProductId). Simultaneously, based on the node's application interface specifications, application products will be created and developed, generating sales application information (pubAppId), and configuring key application integration addresses, including business synchronization URLs, message push URLs, and single sign-on URLs, to ensure data synchronization, message push functionality, and a seamless user login experience.

[0104] The business synchronization URL is used to synchronize the SaaS business information subscribed by customers to the SaaS platform;

[0105] The message push URL is used to push and synchronize uplink data from the terminal device of the SaaS application to the SaaS platform;

[0106] The single sign-on URL allows customers who subscribe to SaaS applications to directly access the SaaS platform without logging in, enabling them to use the applications and view and manage their data.

[0107] 2.3 Perform field mapping as shown in the table below:

[0108] Product Name Product Type Sub-node mapping Internet of Things (IoT) application services Access products pubAppId xx terminal products Functional products pubProductId

[0109] By leveraging NLP algorithms, key fields in product information, such as pubAppId and pubProductId, are automatically identified and mapped, reducing manual configuration errors and automating field mapping. This includes the following steps:

[0110] Data preprocessing: Clean and standardize product information text, removing irrelevant characters and formatting differences.

[0111] Feature extraction: Use NLP techniques to extract keywords and phrases from the text, such as product names, types, dependencies, etc.

[0112] Model training: Based on historical datasets, train machine learning models to identify and classify key fields such as pubAppId and pubProductId.

[0113] Automatic mapping: Matches and maps extracted key fields with fields in the database to automatically update product information.

[0114] Validation and Correction: Set up a validation mechanism, manually review the automatic mapping results, correct erroneous mappings, and continuously optimize the model.

[0115] To ensure real-time updates and consistency of product information, changes in upstream product information can be quickly reflected in downstream products within the dependency chain. The following technical methods are primarily employed:

[0116] Event-driven architecture (EDA): When upstream product information changes, an event is triggered to notify downstream products to update.

[0117] Asynchronous message queues: Use message queues such as Kafka to process product information change events asynchronously, avoiding blocking the main process.

[0118] Version control: Add version numbers to product information, track each change, and ensure data consistency.

[0119] Dependency monitoring: Monitor product dependencies in real time, and immediately initiate the synchronization process once an upstream change is detected.

[0120] Data validation and rollback: During synchronization, data validation is performed to ensure the integrity and accuracy of information. If errors are found, a rollback operation is performed to restore the system to its state before the change.

[0121] 3. Dynamic interface registration and intelligent orchestration of business logic

[0122] 3.1 Dynamic Registration of Interfaces

[0123] Lower-level nodes employ a dynamic registration mechanism, registering interface services such as account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification through a capability gateway. The capability gateway verifies received registration requests to ensure the completeness and legitimacy of service description information. Upon successful verification, the service information is stored in a service directory, potentially using a database or caching system for rapid querying and updates.

[0124] Dynamic service catalog updates: The capability gateway maintains a dynamic service catalog, which is automatically updated whenever a new service is registered or an existing service is updated.

[0125] Service Invocation and Management: Clients retrieve the interface information of the required services by querying the service catalog, and then invoke the services. The capability gateway is responsible for routing and authorization verification, ensuring the security and validity of service invocations.

[0126] 3.2 Business Logic Orchestration

[0127] The capability gateway has a built-in business logic orchestration engine that can dynamically adjust interface call strategies based on factors such as current network status, resource availability, and historical call success rates. The orchestration engine also supports advanced features such as A / B testing and canary deployments, ensuring a smooth transition between old and new services and minimizing the impact on existing business operations.

[0128] Based on the business logic orchestration results, the capability gateway can intelligently select the optimal interface call path, prioritize the use of service instances with short response times and high stability, and support load balancing and failover. When a service instance becomes unavailable, it automatically switches to other healthy instances to ensure service continuity and user experience.

[0129] 3.3 Interface Call Flow

[0130] This process involves key interfaces including account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification, such as... Figure 2 As shown, the specific steps are as follows:

[0131] (1) Customer Account Initialization: The sales representative creates customer information and subscribes to IoT platform services in the lower-level customer relationship management system (CRM). The system automatically calls the account synchronization interface to generate a tenant ID (e.g., tenantId_A) and notifies the customer of their login credentials via SMS. This step ensures that the customer can access the sub-node platform.

[0132] (2) Application service configuration: Based on the tenant created in the first step, the personnel in charge call the application creation interface through the lower-level IT system to create an application instance (e.g., appInst_A) under the tenant account (e.g., tenantId_A). The system returns an application triple: appId, appKey, and secret, which are used for authentication of subsequent service calls.

[0133] (3) Terminal Product Ordering and Creation: When the receiving personnel initiate a terminal product order, the lower-level IT system calls the product creation interface to create a terminal product instance (such as productInst_A) under the specified tenant and returns the product ID (productId) and master key (masterKey). Multiple product orders are supported and encapsulated in a list structure.

[0134] (1)-(3) Create product relationships as shown in the table below:

[0135]

[0136] (4) Business Relationship Synchronization: After completing the first three steps, the lower-level IT system calls the business synchronization interface to synchronize the product relationship to the SaaS platform, thereby binding the order information. The system returns the SaaS application platform account and password, notifies the customer via SMS, and completes the product activation and acceptance process.

[0137] (5) Device Registration and Management: After the terminal device leaves the warehouse, the lower-level IT system calls the device registration interface to register the device in the specified product instance and returns the device ID as a unique identifier. This step ensures the association between the device and the platform.

[0138] (6) Equipment Activation Verification: After completing the equipment installation, the installation and maintenance personnel scan the equipment label (QR code / barcode) to call the equipment activation verification interface, check the equipment's online status, and confirm that the installation is complete. This step ensures that the equipment can connect to the network normally.

[0139] After completing (1)-(6), the order is reported as completed, realizing product ordering, acceptance, installation and maintenance.

[0140] In summary, the method for enabling product capabilities in a multi-level IoT platform scenario according to the present invention has the following specific advantages:

[0141] 1. Configuration and intelligent dependency management of lower-level node product services

[0142] By leveraging a service registry and metadata management, automated identification and configuration of product dependencies were achieved, significantly improving configuration efficiency, ensuring accuracy, and reducing the need for manual intervention. The introduction of NLP algorithms automated field mapping, effectively reducing manual configuration errors and improving data processing accuracy and efficiency. The adoption of event-driven architecture, asynchronous message queues, and version control ensured real-time updates to the dependency chain, enabling real-time synchronization of product information and guaranteeing consistency between upstream and downstream products. This accelerated business response time and enhanced the overall system stability and reliability.

[0143] 2. Dynamic interface registration and intelligent orchestration of business logic

[0144] The lower-level nodes adopt a dynamic registration mechanism to register various interface services through the capability gateway, maintain a dynamic service catalog, improve the flexibility of service management, and can quickly adapt to business changes; the overall built-in business logic orchestration engine dynamically adjusts the interface call strategy according to network status and resource availability, and intelligently selects the optimal interface call path, thereby improving service response speed and stability.

[0145] In summary, this invention, through product service configuration and intelligent dependency management, enables lower-level nodes to autonomously create and configure products, constructing a multi-layered product dependency relationship, including IoT platform services, IoT application services, and terminal product services. This mechanism not only simplifies the product ordering process but also improves operational efficiency and product management transparency through automated dependency identification and configuration, and dependency graph visualization. Furthermore, the application of NLP technology enables automatic mapping of product information fields, reducing human error and ensuring real-time updates and consistency of product information.

[0146] In another aspect, the present invention also discloses a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform the steps of the method described above.

[0147] In another aspect, the present invention also discloses a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the method described above.

[0148] In another embodiment provided in this application, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute the method for enabling product capabilities in any of the multi-level architecture IoT platform scenarios described above.

[0149] It is understood that the systems, devices, and storage media provided in the embodiments of the present invention correspond to the methods provided in the embodiments of the present invention, and the explanations, examples, and beneficial effects of the relevant content can be referred to the corresponding parts of the above methods.

[0150] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0151] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0152] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

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

Claims

1. A method for enabling product capabilities in a multi-level architecture IoT platform scenario, characterized in that, Includes the following steps, Product service configuration and intelligent dependency management include automatically discovering and managing the dependencies between three types of products: IoT platform services, IoT application services, and terminal product services. It identifies key fields in the applications sold and public products in lower-level nodes and accurately matches them with internal service fields to achieve high-efficiency and high-accuracy data synchronization. Dynamic interface registration and intelligent business logic orchestration include lower-level nodes dynamically registering the services they provide through the capability gateway, including interface services such as account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification, and performing business logic orchestration, dynamically adjusting interface call strategies to achieve optimal orchestration and call of business logic; Product service configuration and intelligent dependency management include, S2.1 Lower-level nodes apply for and create access-type products and functional products based on the product management platform, so that the acceptance personnel can process orders; S2.2 Product Information Configuration: Terminal products that have completed docking and testing at the sub-nodes are applied to become public products, generating public product information pubProductId; at the same time, based on the sub-node application interface specifications, application products are created and developed, generating sales application information pubAppId, and configuring key application docking addresses, including business synchronization URL address, message push URL address, and single sign-on URL address, to ensure data synchronization, message push, and a seamless user login experience; The business synchronization URL is used to synchronize the SaaS business information subscribed by customers to the SaaS platform; The message push URL is used to push and synchronize uplink data from the terminal device of the SaaS application to the SaaS platform; The single sign-on URL allows customers who subscribe to SaaS applications to directly access the SaaS platform without logging in, based on the sub-nodes, to use the applications and view and manage their data. S2.3 Perform field mapping, using NLP technology algorithms to automatically identify and map key fields in product information.

2. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 1, characterized in that: The products in step S2.1 include, IoT Platform Service: As the foundational layer, it provides core functional services, including terminal access, terminal management, and application enablement. The activation of this service will generate sub-node accounts and tenants, providing infrastructure support for subsequent services. IoT Application Services: Relying on IoT platform services, it further provides application-level support. When activated, it generates application triple information: appId, appKey, and secret, which are used to create applications under specific tenants and realize application-level management and data processing. xx terminal product: As a functional layer product, it relies on IoT application services. After activation, it generates product information, allows the creation of terminal products based on sub-nodes, and can be attached to application products to realize the management and data interaction of terminal devices.

3. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 2, characterized in that: Product service configuration and intelligent dependency management involve the following steps in building dependency relationships: Automated identification and configuration of product dependencies: Utilizes a service registry and metadata management to automatically identify and configure dependencies between products; Dependency graph visualization: Construct a dependency graph to intuitively display the hierarchical dependencies between products, making it easier for operations and maintenance personnel to understand and maintain.

4. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 1, characterized in that: Step S2.3 specifically includes, Data preprocessing: Cleaning and standardizing product information text, removing irrelevant characters and formatting differences; Feature extraction: Using NLP techniques to extract keywords and phrases from text; Model training: Based on historical datasets, train machine learning models to identify and classify key fields; Automatic mapping: Matches and maps extracted key fields with fields in the database to automatically update product information; Validation and Correction: Set up a validation mechanism, manually review the automatic mapping results, correct erroneous mappings, and continuously optimize the model.

5. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 4, characterized in that: Step S2.3 specifically also includes, In dependency chains, to ensure that changes in upstream product information are quickly reflected in downstream products, the following technical methods are employed: Event-driven architecture (EDA): When upstream product information changes, an event is triggered to notify downstream products to update. Asynchronous message queues: Use message queues to process product information change events asynchronously, avoiding blocking the main process; Version control: Add version numbers to product information, track every change, and ensure data consistency; Dependency monitoring: Monitor the dependencies between products in real time, and immediately initiate the synchronization process once an upstream change is detected; Data verification and rollback: During the synchronization process, data verification is performed to ensure the integrity and correctness of the information; If an error is found, a rollback operation will be performed to restore the state to its previous state.

6. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 1, characterized in that: Dynamic interface registration and intelligent orchestration of business logic include, S3.1 Dynamic Interface Registration: Lower-level nodes adopt a dynamic registration mechanism, registering interface services such as account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification through the capability gateway; The capability gateway verifies the received registration requests to ensure the completeness and legality of the service description information; Once verified, the service information is stored in the service directory, using a database or caching system for quick querying and updating. S3.2 Business Logic Orchestration; The capability gateway has a built-in business logic orchestration engine that can dynamically adjust interface call strategies based on current network status, resource availability, and historical call success rates. Meanwhile, the orchestration engine supports advanced features such as A / B testing and canary releases to ensure a smooth transition between old and new services and reduce the impact on existing business. S3.3, Interface call process; This process involves key interfaces including account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification.

7. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 6, characterized in that: Step S3.1 also includes dynamic updating of the service catalog: the capability gateway maintains a dynamic service catalog, which is automatically updated whenever a new service is registered or an existing service is updated; Service Invocation and Management: Clients obtain the interface information of the required services by querying the service catalog, and then invoke the services. The capability gateway is responsible for routing and authorization verification to ensure the security and validity of service invocation.

8. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 6, characterized in that: Step S3.3 specifically includes, (1) Customer account initialization: The staff creates customer information and subscribes to IoT platform services in the lower-level customer relationship management system; the system automatically calls the account synchronization interface to generate a tenant ID and notifies the customer of the login credentials via SMS. This step ensures that the customer can access the sub-node platform. (2) Application service configuration: Based on the tenant created in the first step, the personnel in charge call the application creation interface through the lower-level IT system to create an application instance under the tenant account; the system returns an application triple: appId, appKey, and secret, which are used for authentication of subsequent service calls; (3) Terminal product ordering and creation: The receiving personnel initiates terminal product ordering, and the lower-level IT system calls the product creation interface to create a terminal product instance under the specified tenant and return the product ID and master key; multiple product orders are supported and encapsulated in a list structure; (4) Business relationship synchronization: After completing the first three steps, the lower-level IT system calls the business synchronization interface to synchronize the product relationship to the SaaS platform, realize the binding of order information, and the system returns the SaaS application platform account and password, and notifies the customer via SMS to complete the product activation and acceptance process; (5) Device registration and management: After the terminal device leaves the warehouse, the lower-level IT system calls the device registration interface to register the device in the specified product instance and returns the device ID as a unique identifier; (6) Equipment activation verification: After the installation and maintenance personnel complete the equipment installation, they scan the equipment label, call the equipment activation verification interface, query the online status of the equipment, and confirm that the installation is complete. After completing (1)-(6), the order is reported as completed, realizing product ordering, acceptance, installation and maintenance.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the computer program is executed by the processor, it causes the processor to perform the steps of the method as described in any one of claims 1 to 8.

Images