Method and device for opening product capability in multi-level architecture Internet of Things platform scene

Abstract

The invention discloses a method and equipment for opening product capability in a multi-level architecture Internet of Things platform scene, and the method comprises the steps: automatically discovering three types of products, namely Internet of Things platform service, Internet of Things application service and terminal product service, managing the dependency relationship among the services, recognizing key fields in selling applications and public products in subordinate nodes, performing accurate matching with an internal service field; dynamic interface registration and business logic intelligent arrangement are carried out, the services provided by a subordinate node are dynamically registered through a capability gateway, interface services such as account synchronization, product creation, application creation, business synchronization, equipment registration and equipment activation verification are included, business logic arrangement is carried out, and an interface calling strategy is dynamically adjusted; and optimal arrangement and calling of the service logic are realized. According to the method, a series of links such as opening, acceptance, installation and maintenance can be performed on the local product based on the partial nodes in a two-stage architecture Internet of Things platform scene, the IT process can be tracked, and operation and maintenance of the product are facilitated.

Description

Technical Field

[0001] The present invention relates to the technical field of Internet of Things, and in particular to a method and device for enabling product capabilities in a multi-level architecture Internet of Things platform scenario. Background Art

[0002] At present, the capability building and business packaging of IoT products are completed at the centralized nodes. Each subordinate region can only accept IoT product orders based on the centralized unified CRM system, and cannot build and package localized IoT products. However, with the huge market drive and the formation of the "1+N" two-level architecture, each subordinate region urgently needs to form product capability packaging, activation, acceptance, installation and maintenance based on sub-nodes.

[0003] The existing technical solution mainly configures the sub-node products through centralized node configuration, and the lower-level nodes order through the provincial CRM, call the two-level service activation system, and realize product acceptance and activation through centralized and sub-node orders:

[0004] (1) Centralized node configuration and product listing on sub-nodes: On the centralized platform, standardized product configuration is performed based on the characteristics and requirements of IoT products. These configurations include but are not limited to device types, communication protocols, data processing rules, security policies, etc. After configuration is completed, the products are listed in a standardized form on each sub-node, i.e., the subordinate companies in each location.

[0005] (2) Subordinate nodes order through provincial CRM: Subordinate nodes use CRM to receive IoT product ordering 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: When 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) Synchronize orders between centralized and distributed nodes to realize product acceptance and activation: In order to ensure the consistency and timeliness of services, a real-time order synchronization mechanism is established between the centralized platform and each distributed node. Once the 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 distributed node will also receive the corresponding notification and prepare to perform local service activation operations.

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

[0009] (1) Data synchronization delay: There may be delays 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 continues to increase. It is difficult to simplify the configuration process and reduce the error rate while ensuring flexibility. The centralized node configuration is used to put sub-node products on the shelves. The acceptance of products through sub-nodes involves many IT systems, which is prone to stuck orders and difficult to locate problems.

[0011] (3) Difficulty in ensuring consistency across regions: Due to the lack of unified technical specifications and standards, it is difficult to fully achieve consistency in product configuration and user experience due to differences in local policies, network environments, and customer needs. If many sub-node platforms are involved in the acceptance and activation of local products, the transformation workload will be large and difficult to maintain.

[0012] Related term explanation:

[0013] Internet of Things (IoT): Through various information sensing devices, various information of any object or process that needs to be monitored, connected, and interacted is collected in real time to achieve interconnection between objects and objects, and between objects and people.

[0014] Multi-level IoT platform: refers to the IoT platform architecture that includes edge layer, access layer, core layer and application layer, in which each layer communicates 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 the IoT platform, such as device management, data flow analysis, security policies, etc.

[0016] Capability Gateway: Capability Gateway is a key component in a microservice architecture. As a front-end entry, it is responsible for processing external requests and routing them to back-end services. Capability Gateway not only provides API routing, authentication and authorization, load balancing and other functions, but also can perform flow control, circuit breaking and degradation, and log auditing, thereby enhancing the stability and security of the system. In the IoT platform, the capability gateway plays an important role in service registration and discovery, dynamic interface management, and ensures high availability and efficient call of services.

[0017] DICT: refers to the integration of digital information technology and communication technology. DICT applications cover multiple fields such as cloud computing, big data, the Internet of Things, and artificial intelligence. It aims to provide comprehensive information solutions for enterprises and individuals through the integration of these technologies, and promote industrial upgrading and digital transformation. In the context of the Internet of Things platform, DICT applications emphasize the deep perception and efficient management of the physical world through data collection, analysis, and intelligent decision-making.

[0018] NLP (Natural Language Processing): Natural language processing is a branch of artificial intelligence that focuses on enabling computers to understand, interpret, and generate human language. NLP technology involves speech recognition, semantic analysis, sentiment analysis, machine translation, and other aspects, which can help computers parse the meaning of text, identify entities and relationships, and thus achieve automated processing and intelligent decision-making. In the IoT platform, 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. It provides detailed information about the data, such as the source, format, creation date, author, copyright information, etc. In the IoT platform, metadata is used to describe the attributes and relationships of entities such as sensors, devices, and applications, which helps organize, retrieve, and manage data. Through metadata management, dependencies between products can be automatically identified, and automatic configuration and optimization of services can be achieved.

[0020] Service Registry: The service registry is an important part of the microservice architecture. It is responsible for storing and managing information about service instances, such as the service address, port, and status. The service registry is usually used in conjunction with the service discovery mechanism, allowing service consumers to dynamically find and call service providers without hard-coding the service address. In the IoT platform, the service registry helps realize dynamic registration and discovery of services, enhancing the scalability and robustness of the system.

[0021] Event-Driven Architecture (EDA): is a distributed computing model in which applications run by responding to event streams rather than through the traditional request-response approach. In EDA, events are generated by components in the system and then passed to interested subscribers for processing. This architectural model improves the responsiveness and flexibility of the system, can handle a large number of concurrent events in real time, and is suitable for scenarios that require 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 Internet of Things platform scenario, which can at least solve one of the technical problems in the background technology.

[0023] To achieve the above object, the present invention adopts the following technical solutions:

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

[0025] Product service configuration and intelligent dependency management, including automatic discovery and management of the dependencies between the three categories of IoT platform services, IoT application services, and terminal product services, identifying the key fields in the sales applications and public products in the lower-level nodes, and accurately matching them with the internal service fields to achieve efficient and high-precision data synchronization;

[0026] Dynamic interface registration and intelligent orchestration of business logic, including the dynamic registration of services provided by lower-level nodes through the capability gateway, including account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification. These interface services also perform business logic orchestration and dynamically adjust 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. Subordinate nodes apply for and create access products and functional products based on the product management platform for acceptance personnel to accept orders;

[0029] S2.2, product information configuration, apply for the terminal products that have completed docking and debugging of the sub-nodes to become public products, and generate public product information pubProductId; at the same time, based on the sub-node application interface specifications, realize the creation and development of application products, generate sales application information pubAppId, and configure 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 seamless user login experience;

[0030] The service synchronization URL address is used to synchronize the SaaS service information subscribed by the customer to the SaaS platform;

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

[0032] The single sign-on URL address is used for SaaS application subscription customers to directly jump to the SaaS platform based on the node without logging in to use their applications and view and manage their data;

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

[0034] Furthermore, the product in step S2.1 includes,

[0035] IoT platform service: As the basic 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 service: It relies on IoT platform services to provide further support at the application level. When activated, it generates application triple information: appId, appKey, secret, which is used to create applications under specific tenants to achieve application-level management and data processing;

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

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

[0039] Automatic identification and configuration of product dependencies: Automatically identify and configure dependencies between products using the service registry and metadata management;

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

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

[0042] Data preprocessing: Clean and standardize product information text to remove irrelevant characters and format differences;

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

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

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

[0046] Verification and correction: Set up a verification mechanism, manually review the automatic mapping results, correct incorrect mappings, and continuously optimize the model.

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

[0048] In the dependency chain, in order to quickly reflect changes in upstream product information to downstream products, the following technical methods are used:

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

[0050] Asynchronous message queue: Use message queue to asynchronously process product information change events to avoid blocking the main process;

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

[0052] Dependency monitoring: monitor the dependencies between products in real time and start the synchronization process immediately once upstream changes are detected;

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

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

[0055] S3.1, Dynamic registration of interfaces, the lower-level nodes adopt a dynamic registration mechanism to register 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 request to ensure the integrity and legitimacy of the service description information;

[0057] After verification, the service information is stored in the service directory, using a database or cache system for storage to enable fast query and update;

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

[0059] At the same time, the orchestration engine supports A / B testing and grayscale release of advanced features to ensure a smooth transition between new and old services and reduce the impact on existing businesses.

[0060] S3.3, interface calling process; this process 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 update of 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;

[0063] Service call and management: The client queries the service directory to obtain the interface information of the required service and then calls the service. The capability gateway is responsible for routing and authority verification to ensure the security and effectiveness of service calls.

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

[0065] (1) Customer account initialization: The processing staff creates customer information in the lower-level customer relationship management system and subscribes to the IoT platform service. The system automatically calls the account synchronization interface, generates 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 processing personnel call the application creation interface through the lower-level IT system to create an application instance under the tenant account; the system returns the application triple: appId, appKey, secret, which is used for identity authentication of subsequent service calls;

[0067] (3) Terminal product ordering and creation: The receiving personnel initiates the 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; it supports multiple product ordering and uses a list structure encapsulation;

[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 to achieve order information binding. The system returns the SaaS application platform account and password and notifies the customer via SMS, completing the product activation acceptance process.

[0069] (5) Device registration and management: After the terminal device is shipped out of 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;

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

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

[0072] On the other hand, the present invention further discloses a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, the processor executes the steps of the above method.

[0073] On the other hand, the present invention further 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 executes the steps of the above method.

[0074] It can be seen from the above technical solution that the method and device for product capability activation in the multi-level architecture Internet of Things platform scenario of the present invention can be used in the two-level architecture Internet of Things platform scenario to activate, accept, install and maintain local products based on sub-nodes, and a series of links can be performed. The IT process can be tracked, which is beneficial to the operation and maintenance of the product and effectively solves the above-mentioned problems.

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

[0076] The present invention realizes autonomous product creation and configuration of lower-level nodes through product service configuration and intelligent dependency management, and builds multi-level product dependency relationships, including IoT platform services, IoT application services, and terminal product services. This mechanism not only simplifies the product ordering process, but also improves operation and maintenance efficiency and the transparency of product management through means such as automatic identification and configuration of dependencies and visualization of dependency graphs. In addition, the application of NLP technology realizes the automatic mapping of product information fields, reduces human errors, and ensures the real-time update and consistency of product information.

[0077] The present invention realizes dynamic registration and management of interfaces through dynamic interface registration and intelligent orchestration of business logic, and lower-level nodes realize dynamic registration and management of interfaces through capability gateway, thus ensuring high availability and security of services. The introduction of business logic orchestration engine intelligently adjusts interface call strategy according to dynamic factors such as real-time network status and resource availability, supports A / B testing and grayscale release, ensures smooth transition of new and old services, and reduces the risk of business interruption. The optimization of interface call process, from customer account initialization to device activation verification, each step has been proven and designed to ensure service continuity and user experience.

[0078] The following remarkable effects are achieved by the above technical means of the present invention:

[0079] Improved 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] Optimized data synchronization and configuration efficiency: Through event-driven architecture, asynchronous message queue and other technologies, the data synchronization delay is significantly shortened, the configuration process is simplified, and the response speed and flexibility of the overall system are 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 in the event of network fluctuations or resource constraints.

[0082] It promotes the realization of cross-regional consistency: the automated management of dependencies and the real-time update mechanism effectively solve the complexity of cross-regional product configuration, ensuring the consistency and standardization of services across the country. It can be replicated in batch project construction to reduce the workload of transformation and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0084] Figure 2 This is an interface calling flow chart of an embodiment of the present invention. DETAILED DESCRIPTION

[0085] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments.

[0086] The embodiment of the present invention proposes a unified standard method for product capability activation in a two-level architecture IoT platform scenario, which can realize a series of IT processes such as activation, acceptance, installation and maintenance of localized IoT products based on sub-nodes while minimizing resource costs, and further efficiently support the development of local IoT services. Figure 1 As shown, specific objectives include:

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

[0088] The three types of products, namely IoT platform services, IoT application services and terminal product services, automatically discover and manage the dependencies between services, identify the key fields in the sales applications and public products in the lower-level nodes, and accurately match them with the internal service fields to achieve efficient and high-precision data synchronization.

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

[0090] The lower-level nodes dynamically register the services they provide through the capability gateway, including account synchronization, product creation, application creation, business synchronization, device registration, device activation verification and other interface services, and perform business logic orchestration, dynamically adjust the interface call strategy, and achieve the optimal orchestration and call of business logic.

[0091] The following are specific instructions:

[0092] 1. Background and demand analysis,

[0093] With the development of industrial digitalization, DICT applications emerge in an endless stream, and the demand for IoT platforms in various regions is becoming increasingly urgent. IoT platforms have gradually formed a "1+N" two-level architecture, that is, one centralized node and N sub-nodes, which jointly carry the access and data import of internal and external perception terminals, efficient management of all categories and scenarios of equipment, and multi-dimensional integrated perception data standards, enabling the digital transformation of thousands of industries. At present, the capability building and business packaging of IoT products are completed in the centralized nodes. Each subordinate region can only accept IoT product orders based on the centralized unified CRM system, and cannot build and package localized IoT products. At the same time, there are a series of problems such as data synchronization delay, configuration complexity, and cross-regional consistency.

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

[0095] 2.1. The lower-level nodes apply for and create access products and functional products based on the product management platform for acceptance personnel to accept orders, as shown in the following table:

[0096] Product Name Product Type Dependencies IoT Platform Services Access products none IoT Application Services Access products Reliance on IoT platform services xxTerminal product service Functional products Reliance on IoT application services

[0097] IoT platform service: As the basic layer, it provides core functional services, including but not limited to terminal access, terminal management, application enablement, etc. The activation of this service will generate sub-node accounts and tenants, providing infrastructure support for subsequent services.

[0098] IoT application service: Relying on IoT platform services, it further provides support at the application level. When activated, it generates application triplet information (appId, appKey, secret) to create applications under specific tenants and implement application-level management and data processing.

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

[0100] Building dependencies mainly includes the following steps:

[0101] Automatic identification and configuration of product dependencies: Use service registries (such as Consul, Eureka) and metadata management to automatically identify and configure dependencies between products. For example, the IoT platform service, as the base layer, does not need to rely on other services; the IoT application service depends on the IoT platform service, and the xx terminal product depends on the IoT application service.

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

[0103] 2.2. Product information configuration: apply for the terminal products that have completed docking and debugging at the sub-nodes to become public products and generate public product information (pubProductId). At the same time, based on the sub-node application interface specifications, create and develop application products, generate sales application information (pubAppId), and configure key application docking addresses, including business synchronization URL addresses, message push URL addresses, and single sign-on URL addresses to ensure data synchronization, message push, and seamless user login experience;

[0104] The service synchronization URL address is used to synchronize the SaaS service information subscribed by the customer to the SaaS platform;

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

[0106] The single sign-on URL address is used for SaaS application subscription customers to directly jump to the SaaS platform based on the node without logging in to use their applications and view and manage their information.

[0107] 2.3. Map the fields as shown in the following table:

[0108] Product Name Product Type Node Mapping IoT Application Services Access products pubAppId xx terminal products Functional products pubProductId

[0109] Using NLP technology algorithms, key fields in product information, such as pubAppId and pubProductId, are automatically identified and mapped to reduce manual configuration errors and automate field mapping, including the following steps:

[0110] Data preprocessing: Clean and standardize product information text to remove irrelevant characters and format differences.

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

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

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

[0114] Verification and correction: Set up a verification mechanism, manually review the automatic mapping results, correct incorrect mappings, and continuously optimize the model.

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

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

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

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

[0119] Dependency monitoring: Monitor the dependencies between products in real time and start the synchronization process immediately once upstream changes are detected.

[0120] 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 is performed to restore to the state before the change.

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

[0122] 3.1、Dynamic registration of interfaces

[0123] The lower-level nodes adopt a dynamic registration mechanism to register 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 request to ensure the integrity and legitimacy of the service description information. After verification, the service information is stored in the service directory, which may be stored in a database or cache system to achieve fast query and update.

[0124] Dynamic update of 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.

[0125] Service call and management: The client queries the service directory to obtain the interface information of the required service and then calls the service. The capability gateway is responsible for routing and authority verification to ensure the security and effectiveness of service calls.

[0126] 3.2 Business Logic Orchestration

[0127] The capability gateway has a built-in business logic orchestration engine that can dynamically adjust the interface call strategy based on factors such as the current network status, resource availability, and historical call success rate. At the same time, the orchestration engine supports advanced functions such as A / B testing and grayscale release to ensure a smooth transition between new and old services and reduce the impact on existing businesses.

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

[0129] 3.3 Interface Calling Process

[0130] The key interfaces involved in this process include account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification. Figure 2 As shown, the specific steps are as follows:

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

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

[0133] (3) Terminal product ordering and creation: The receiving personnel initiates the terminal product ordering, and 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). It supports multi-product ordering and uses a list structure encapsulation.

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

[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 to achieve order information binding. The system returns the SaaS application platform account and password and notifies the customer via SMS to complete the product activation acceptance process.

[0137] (5) Device registration and management: After the terminal device is shipped out of 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) Device activation verification: After the installation is complete, the maintenance personnel scan the device label (QR code / barcode), call the device activation verification interface, query the device online status, and confirm that the installation is complete. This step ensures that the device can access the network normally.

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

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

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

[0142] By utilizing the service registration center and metadata management, we have achieved automatic identification and configuration of product dependencies, which not only greatly improved configuration efficiency, but also ensured configuration accuracy and reduced the need for manual intervention. By introducing NLP technology algorithms, we have achieved automation of field mapping, effectively reduced manual configuration errors, and improved the accuracy and efficiency of data processing. We have adopted event-driven architecture, asynchronous message queues, version control and other technologies to ensure real-time updates of dependency chains, achieve real-time synchronization of product information, and ensure consistency of upstream and downstream products, thereby accelerating business response speed and improving the stability and reliability of the overall system.

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

[0144] The lower-level nodes use 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 be able to 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, improving service response speed and stability.

[0145] In summary, the embodiments of the present invention realize autonomous product creation and configuration of lower-level nodes through product service configuration and intelligent dependency management, and build multi-level product dependency relationships, including IoT platform services, IoT application services, and terminal product services. This mechanism not only simplifies the product ordering process, but also improves operation and maintenance efficiency and the transparency of product management through automated identification and configuration of dependencies, visualization of dependency graphs, and other means. In addition, the application of NLP technology realizes the automatic mapping of product information fields, reduces human errors, and ensures real-time updating and consistency of product information.

[0146] On the other hand, the present invention further discloses a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, the processor executes the steps of the above method.

[0147] On the other hand, the present invention further 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 executes the steps of the above method.

[0148] In another embodiment provided in the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute the method for enabling product capabilities in any multi-level architecture IoT platform scenario in the above embodiments.

[0149] It is understandable that the system, device and storage medium provided in the embodiments of the present invention correspond to the method provided in the embodiments of the present invention, and the explanation, examples and beneficial effects of the relevant contents can refer to the corresponding parts in the above methods.

[0150] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part 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, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive Solid State Disk (SSD)), etc.

[0151] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0152] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0153] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions 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: The following steps are included: Product service configuration and intelligent dependency management, including automatic discovery and management of the dependencies between the three categories of IoT platform services, IoT application services, and terminal product services, identifying the key fields in the sales applications and public products in the lower-level nodes, and accurately matching them with the internal service fields to achieve efficient and high-precision data synchronization; Dynamic interface registration and intelligent orchestration of business logic, including the dynamic registration of services provided by lower-level nodes through the capability gateway, including account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification. These interface services also perform business logic orchestration and dynamically adjust interface call strategies to achieve optimal orchestration and call of business logic.

2. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 1, characterized in that: Product service configuration and intelligent dependency management include: S2.

1. Subordinate nodes apply for and create access products and functional products based on the product management platform for acceptance personnel to accept orders; S2.2, product information configuration, apply for the terminal products that have completed docking and debugging of the sub-nodes to become public products, and generate public product information pubProductId; at the same time, based on the sub-node application interface specifications, realize the creation and development of application products, generate sales application information pubAppId, and configure 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 seamless user login experience; The service synchronization URL address is used to synchronize the SaaS service information subscribed by the customer to the SaaS platform; The message push URL address is used to push and synchronize the upstream data of the terminal device of the SaaS application to the SaaS platform; The single sign-on URL address is used for SaaS application subscription customers to directly jump to the SaaS platform based on the node without logging in to use their applications and view and manage their data; S2.

3. Perform field mapping and use NLP technology algorithms to automatically identify and map key fields in product information.

3. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 2, characterized in that: The products in step S2.1 include, IoT platform service: As the basic 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 service: It relies on IoT platform services to provide further support at the application level. When activated, it generates application triple information: appId, appKey, secret, which is used to create applications under specific tenants to achieve application-level management and data processing; xx terminal product: As a functional layer product, it relies on the Internet of Things application service. After activation, it generates product information, allows the creation of terminal products based on sub-nodes, and can be mounted under the application product to realize the management of terminal devices and data interaction.

4. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 3, characterized in that: Product service configuration and intelligent dependency management include the following steps in building dependencies: Automatic identification and configuration of product dependencies: Automatically identify and configure dependencies between products using the service registry and metadata management; Dependency graph visualization: Build a dependency graph to intuitively display the hierarchical dependencies between products, making it easier for operation and maintenance personnel to understand and maintain.

5. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 2, characterized in that: Step S2.3 specifically includes: Data preprocessing: Clean and standardize product information text to remove irrelevant characters and format differences; Feature extraction: Use NLP techniques to extract keywords and phrases from text; Model training: Based on historical data sets, train machine learning models to identify and classify key fields; Automatic mapping: Match and map the extracted key fields with the fields in the database to automatically update product information; Verification and correction: Set up a verification mechanism, manually review the automatic mapping results, correct incorrect mappings, and continuously optimize the model.

6. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 5, characterized in that: Step S2.3 specifically also includes: In the dependency chain, in order to quickly reflect changes in upstream product information to downstream products, the following technical methods are used: Event-driven EDA: When upstream product information changes, an event is triggered to notify downstream products to update; Asynchronous message queue: Use message queue to asynchronously process product information change events to avoid blocking the main process; Version control: Add version numbers to product information, track each change, and ensure data consistency; Dependency monitoring: monitor the dependencies between products in real time and start the synchronization process immediately once upstream changes are detected; Data verification and rollback: During the synchronization process, data verification is implemented to ensure the integrity and correctness of information; If an error is found, perform a rollback operation to restore to the state before the change.

7. 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 registration of interfaces, the lower-level nodes adopt a dynamic registration mechanism to register 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 request to ensure the integrity and legitimacy of the service description information; After verification, the service information is stored in the service directory, using a database or cache system for storage to enable fast query and update; S3.2, Business logic orchestration: The capability gateway has a built-in business logic orchestration engine that can dynamically adjust the interface call strategy based on the current network status, resource availability, and historical call success rate factors; At the same time, the orchestration engine supports A / B testing and grayscale release of advanced features to ensure a smooth transition between new and old services and reduce the impact on existing businesses. S3.3, interface calling process; The key interfaces involved in this process include account synchronization, product creation, application creation, business synchronization, device registration, and device activation verification.

8. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 7, characterized in that: Step S3.1 also includes,dynamic update of 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 call and management: The client queries the service directory to obtain the interface information of the required service and then calls the service. The capability gateway is responsible for routing and authority verification to ensure the security and effectiveness of service calls.

9. The method for enabling product capabilities in a multi-level architecture IoT platform scenario according to claim 7, characterized in that: Step S3.3 specifically includes: (1) Customer account initialization: The processing staff creates customer information in the lower-level customer relationship management system and subscribes to the IoT platform service. The system automatically calls the account synchronization interface, generates 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 processing personnel call the application creation interface through the lower-level IT system to create an application instance under the tenant account; the system returns the application triple: appId, appKey, secret, which is used for identity authentication of subsequent service calls; (3) Terminal product ordering and creation: The receiving personnel initiates the 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; it supports multiple product ordering and uses a list structure encapsulation; (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 to achieve order information binding. The system returns the SaaS application platform account and password and notifies the customer via SMS, completing the product activation acceptance process. (5) Device registration and management: After the terminal device is shipped out of 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 tag, call the equipment activation verification interface, query the equipment online status, and confirm that the installation is complete; After completing (1)-(6), the order is reported complete, and product ordering, acceptance, installation and maintenance are completed.

10. 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, the processor is caused to perform the steps of the method according to any one of claims 1 to 9.

Images