Electronic specification generation method and system based on identification analysis

Abstract

The invention relates to the field of data processing, and particularly discloses an electronic specification generation method and system based on identification analysis, and the method comprises the steps: developing and deploying identification analysis middleware; designing an assembly and a template; identification generation and registration: generating an identification code, then obtaining an identification original data packet, associating and binding the identification code and the identification original data packet to generate identification data, registering the identification data to an identification analysis application platform through identification analysis middleware, generating a two-dimensional code image corresponding to the identification code, and associating and binding the two-dimensional code image with a product; a user scans the two-dimensional code on the product package to obtain an identification code, and the identification code is analyzed to obtain identification data; generating an electronic specification matched with the terminal according to the identification data obtained through analysis; the system comprises identification analysis middleware, a component and template design module, an identification registration module, an identification analysis module and a rendering generation module. According to the method, the effect that the product specification can be customized and dynamically generated is achieved through modularization and identification.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, specifically to the field of industrial Internet identity resolution technology, and in particular to a method and system for generating an electronic instruction manual based on identity resolution. Background Art

[0002] The product manual is a formal document provided with the product, which systematically explains the product's functions, structure, use and maintenance, technical parameters and other information. It serves as a bridge between the product and the user, helping users to correctly understand and use the product. Currently, product manuals come in many forms, including: 1. Package printing, where the manufacturer prints the manual on the product packaging, which is common for food products; 2. Paper manual, where the manufacturer prints the manual on paper media and delivers it to the user along with the product, which is common for pharmaceutical products; 3. Paper manual, where the manual is printed into a book, which is common for complex equipment such as automobiles and industrial equipment. 4. Electronic version, such as through a website page, users can view it online through electronic devices such as computers and mobile phones.

[0003] Traditional printed instructions (including packaging, paper, manuals, etc.) have the following problems: 1. The layout is simple and the content is fixed. The content cannot be changed or modified, and information can only be transmitted in one direction. Once the product is upgraded, the information recorded is outdated and users cannot view the latest instructions. 2. Basic electronic instructions have basic online query capabilities and solve the storage medium problem, but their content is usually the same as traditional paper instructions, and the problems of simple layout and fixed content are not solved.

[0004] Therefore, there is an urgent need for an electronic instruction manual generation method based on identifier resolution to solve the above problems. Summary of the Invention

[0005] The purpose of the present invention is to solve the shortcomings existing in the prior art, and to propose an electronic manual generation method and system based on identity resolution, which adopts identity resolution middleware to solve the problem of data processing. The content of the manual involves multiple business systems of the manufacturer. The introduction of identity resolution middleware collects and uniformly manages the content data, shielding the interaction details of multiple underlying business systems. For the composition of the manual, a componentized design is adopted. Each component can independently set its content and display form, and the components can be laid out by dragging and dropping, and finally the product manual is generated by filling in the content. Through componentization and identification, the product manual can be customized and dynamically generated.

[0006] In order to achieve the above object, the present invention adopts the following technical solutions: A method for generating an electronic instruction manual based on identifier resolution, comprising: Develop and deploy identity resolution middleware: As a data flow hub, the identity resolution middleware connects to the Industrial Internet identity resolution platform and various internal business systems. The identity resolution middleware can register the necessary information in the product manual to the Industrial Internet identity resolution platform, providing a convenient data acquisition channel for the subsequent generation of electronic manuals and shielding the complexity of connecting to business systems. a. Server environment preparation Hardware requirements: CPU: At least 4 cores to meet the needs of multi-threaded processing tasks such as data aggregation and identity generation; Memory: 16GB or more to ensure smooth operation of the middleware, especially sufficient memory space for caching and calculation when processing large amounts of data; Hard disk: Configure based on the company's product data volume and manual storage requirements. A 500GB initial configuration is generally recommended, which can be expanded later based on actual conditions. Software environment: Operating system: Linux (such as CentOS 7) is recommended, as its stability and multi-user environment support capabilities are suitable for running middleware; Java runtime environment: Install JDK 1.8 or later to support running Spring Boot applications; Database system: Install MySQL 5.7 or above to store middleware data; b. Middleware installation and configuration Install the middleware application: Package the developed identity resolution middleware Spring Boot project into a JAR file and start the middleware application on the server using the command "java -jar [middleware JAR file name].jar"; Set application startup parameters, such as specifying the log storage path and configuration file path. For example, use the "--spring.config.location= / etc / identifier / manual / config / application.yml" parameter to specify the configuration file location. Configure middleware parameters: Fill in the configuration file (application.yml) with the database connection parameters for each business system, the interface address of the Industrial Internet Identity Resolution Platform, the data polling cycle, and other parameters; For example, to configure the business system database connection information: spring: datasource: url:jdbc:mysql: / / [business system database address]:3306 / [database name]?useUnicode=true&characterEncoding=utf-8 username: [database username] password: [database password] Configure the Industrial Internet Identity Resolution Platform interface address: identifier: platform: register-url: http: / / [platform domain name] / api / register parse-url: http: / / [platform domain name] / api / parse Configure data polling period: data: polling: interval: 300 (unit: seconds).

[0007] Component and template design: Define manual components and templates. Each manual component describes a part of the manual content. The manual template is composed of a series of manual components combined in a certain order. Identification generation and registration: Generate an identification code, obtain the original identification data packet, associate and bind the identification code and the original identification data packet to generate identification data, and register it with the identification resolution application platform through the identification resolution middleware. Generate a QR code image (or other identifiable media such as an RFID tag) corresponding to the identification code and associate it with the product. Identification resolution: The user scans the QR code on the product packaging (or other identifiable media such as RFID tags) through a terminal device to obtain the identification code, calls the Industrial Internet Identification Resolution Platform interface to resolve the identification code, and obtains the identification data registered in the identification registration step; Generate rendering: The rendering generation module processes the identification data obtained by parsing and generates an electronic instruction manual that is compatible with the terminal; a. Receive identification data Get the parsing results: Algorithm description: The electronic manual rendering module receives the parsing result from the logo parsing module. The result is usually the logo content data encapsulated in JSON format. Expression: parseResult = identifierParseModule.getResult(); Parameter definition: parseResult: The parsing result returned by the identifier parsing module, which includes the identifier code and the identifier content (electronic instruction manual data) corresponding to the identifier code. For example, parseResult = {"identifierCode":"a5950f56c40c9d3a1580a97327e14f8_1", "content":{"drugName":"Aspirin tablets","adaptation":"For the relief of mild to moderate pain"}}.

[0008] b. Data processing Data format conversion: Algorithm description: Convert the identification content data in the parsing result into a format suitable for rendering, such as HTML, XML, etc. Expression: renderableData = convertToRenderFormat(parseResult.content); Example: If the target rendering format is HTML, convert each component in the identified content into the corresponding HTML element; for example, convert the drug name component "Aspirin Tablets" into <h1>Aspirin tablets< / h1> The indication component "for the relief of mild to moderate pain" is converted to For relief of mild to moderate pain .

[0009] c. Rendering generation Select a rendering template based on the terminal device type: Algorithm description: According to the type of user terminal device (such as mobile phone, tablet, computer, etc.), select the corresponding rendering template from the rendering template library; Expression: renderTemplate=renderTemplateLibrary.getTemplateByDeviceType(deviceType); Parameter definition: deviceType: The type of the user's terminal device, which can be determined by the terminal device's User-Agent and other information; for example, deviceType = "mobile" (mobile phone), "tablet" (tablet), "desktop" (computer).

[0010] Fill data into the rendering template: Algorithm description: Fill the converted renderable data into the selected rendering template to generate the final electronic instruction manual; Expression: finalManual=renderTemplate.fillData(renderableData); Example: Assume that the selected mobile device rendering template is an HTML template, which contains layout structures such as title and content area; <h1> Aspirin tablets< / h1> Fill the title area of ​​the template with the HTML element For relief of mild to moderate pain Fill in the content area and finally generate a complete electronic manual in HTML format.

[0011] Generate a visual interface: Algorithm description: Convert the generated electronic manual data into a user-visible interface, usually involving calling the browser engine or other display components of the terminal device for rendering; Expression: displayResult = terminalDevice.render(finalManual); Parameter definition: finalManual: The final electronic manual data, in a format that can be displayed by terminal devices, such as HTML and XML; terminalDevice: The user's terminal device, which has a display interface and rendering engine (such as a browser engine).

[0012] As a further technical solution of the present invention, the identity resolution middleware is a software module responsible for processing requests such as identification data registration, update and resolution. Its functions mainly include: aggregating business data, generating identification codes, registering identifications and basic functions such as enterprises and prefixes; the identity resolution middleware provides a service interface for other modules to call.

[0013] As a further technical solution of the present invention, the instruction manual component describes a portion of the instruction manual content, and each component independently configures the data source of the instruction manual content, including static data, API interface and database query; Static data: fixed text specified when defining a component, which does not need to be obtained from the outside; API: Get data by calling other http interfaces, and perform interface call queries based on the configured API address and call parameters; Database: Get data by querying the database, and perform database query based on the configured database connection address, SQL query statement and other parameters.

[0014] As a further technical solution of the present invention, the specification component includes the following basic fields: component name, component content type, data source, and auxiliary configuration (such as font, color, etc.). Depending on the data source type, data source-specific fields such as API address, parameters, and data source connection parameters are configured. The specification component is described in JSON data. The basic fields are described as follows: title: title, describing the name of this part of the manual; contentType: content type, which describes the content type of this part and supports four types: text, image, video, and handle sub-identifier; dataSource: Data source, which describes the data source of this part of the content. It supports static, API interface and database. According to different data source types, necessary fields can also be set to support data acquisition according to the data source configuration; config: Configuration information fields, such as width (component width), style (inline style), defining font, color, size and other attributes.

[0015] As a further technical solution of the present invention, the instruction manual template is described in JSON data, and the main fields include template name, product number, version number and component list.

[0016] As a further technical solution of the present invention, the generating of the identification code includes: generating the identification code of the product through an identification resolution middleware when the product is completed and offline (or delivered).

[0017] As a further technical solution of the present invention, the obtaining of the original identified data packet includes: Obtain the corresponding electronic instruction manual template from the template library based on product information and category; Analyze the above template and parse out the list of components contained in the template; Process the component list in sequence and obtain the actual data from the configured data source according to the component configuration information; After obtaining the actual data corresponding to all components, the actual data is spliced ​​and filled into the template in the order of the component list to obtain the original data packet.

[0018] As a further technical solution of the present invention, the industrial Internet identification resolution platform interface is called to resolve the identification code and obtain the identification data registered in the identification registration step, including: the identification data supports multiple forms of presentation, supporting text, images, videos and sub-identifiers; for the three types of text, images and videos, the data obtained by the component is the actual data, and if the identification data contains sub-identifiers, the sub-identifier needs to be resolved before the actual identification data can be obtained.

[0019] As a further technical solution of the present invention, it also includes data update. When the product information changes due to upgrade, optimization, etc., the instruction manual is updated, the identification data of the corresponding product is parsed through the identification code, the old data in the identification data is replaced with the latest data, and the identification update is completed through the identification resolution middleware.

[0020] A system for generating electronic instructions based on identifier resolution is used to implement a method for generating electronic instructions based on identifier resolution, comprising: Identity resolution middleware: acts as a data flow hub, used for identity registration, resolution, and update; Component and template design module: used to create, store and manage manual component definitions and manual templates; Identity registration module: used for identity data generation, including template instantiation, data acquisition, identity generation and identity registration; Identification resolution module: used to obtain identification data based on the identification code; Rendering generation module: used to receive identification data, render the data, and generate an electronic instruction manual that is compatible with the terminal.

[0021] The beneficial effects of the present invention are: 1. It achieves the decoupling of content and carrier and supports dynamic updates. The QR code is only an identifier and does not contain the instruction manual. The specific content is stored in the Industrial Internet Identification Resolution Platform system. When the product is updated or optimized, only the original content related to the identifier needs to be modified. The user can automatically obtain the latest instruction manual the next time they scan the code without changing the physical QR code, simplifying the instruction manual management process.

[0022] 2. Provides flexibility and configurability. Through the design of components and templates, the same product can use the same template, achieving template reuse; at the same time, the diversified configuration of component data sources enhances the dynamics and manageability of content.

[0023] 3. Generate on demand, saving costs. Data acquisition and final rendering are only performed when the user actually scans the code, avoiding the overhead of pre-generating and maintaining massive static instruction manual files for all products (such as storage, management, and distribution costs).

[0024] 4. Strong adaptability: for the same product manual data package, the rendering module can generate the optimal display effect according to the terminal device type. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 This is a flow chart of a method for generating electronic instructions based on identifier resolution proposed by the present invention; Figure 2 This is a flowchart of the identifier registration step in the electronic instruction manual generation method based on identifier resolution proposed by the present invention; Figure 3 This is a flowchart of the identification data acquisition step in Example 1 of the electronic instruction manual generation method based on identification resolution proposed by the present invention; Figure 4 This is a flowchart of the identification resolution step in Example 1 of the method for generating an electronic instruction manual based on identification resolution proposed by the present invention; Figure 5 This is a module diagram of an electronic instruction manual generation system based on identity resolution proposed by the present invention. DETAILED DESCRIPTION

[0026] In order to make the technical means, creative features, objectives and effects achieved by the present invention easier to understand, the present invention is further described below in conjunction with specific implementation methods.

[0027] Please see the attached Figure 1-2 , a method for generating an electronic instruction manual based on identifier resolution, comprising: Develop and deploy identity resolution middleware: As a data flow hub, the identity resolution middleware connects to the Industrial Internet identity resolution platform and various internal business systems. The identity resolution middleware can register the necessary information in the product manual to the Industrial Internet identity resolution platform, providing a convenient data acquisition channel for the subsequent generation of electronic manuals and shielding the complexity of connecting to business systems. The identity resolution middleware is a software module responsible for processing requests such as identity data registration, update, and resolution. Its main functions include: aggregating business data, generating identity codes, registering identities, enterprises, prefixes, and other basic functions; the identity resolution middleware provides a service interface for other modules to call.

[0028] Develop and deploy identity resolution middleware specifically: a. Server environment preparation Hardware requirements: CPU: At least 4 cores to meet the needs of multi-threaded processing tasks such as data aggregation and identity generation; Memory: 16GB or more to ensure smooth operation of the middleware, especially sufficient memory space for caching and calculation when processing large amounts of data; Hard disk: Configure based on the company's product data volume and manual storage requirements. A 500GB initial configuration is generally recommended, which can be expanded later based on actual conditions. Software environment: Operating system: Linux (such as CentOS 7) is recommended, as its stability and multi-user environment support capabilities are suitable for running middleware; Java runtime environment: Install JDK 1.8 or later to support running Spring Boot applications; Database system: Install MySQL 5.7 or above to store middleware data; b. Middleware installation and configuration Install the middleware application: Package the developed identity resolution middleware Spring Boot project into a JAR file and start the middleware application on the server using the command "java -jar [middleware JAR file name].jar"; Set application startup parameters, such as specifying the log storage path and configuration file path. For example, use the "--spring.config.location= / etc / identifier / manual / config / application.yml" parameter to specify the configuration file location. Configure middleware parameters: Fill in the configuration file (application.yml) with the database connection parameters for each business system, the interface address of the Industrial Internet Identity Resolution Platform, the data polling cycle, and other parameters; For example, to configure the business system database connection information: spring: datasource: url:jdbc:mysql: / / [business system database address]:3306 / [database name]?useUnicode=true&characterEncoding=utf-8 username: [database username] password: [database password] Configure the Industrial Internet Identity Resolution Platform interface address: identifier: platform: register-url: http: / / [platform domain name] / api / register parse-url: http: / / [platform domain name] / api / parse Configure data polling period: data: polling: interval: 300 (unit: seconds).

[0029] Component and template design: Define manual components and templates. Each manual component describes a part of the manual content. The manual template is composed of a series of manual components combined in a certain order. The instruction manual component describes a part of the instruction manual. Each component independently configures the data source of the instruction manual content, including static data, API interfaces, and database queries. Static data: fixed text specified when defining a component, which does not need to be obtained from the outside; Algorithm description: Get the content directly from the value (fixed text) field of the component; Expression: content = component.dataSource.value; Example: For a drug name component, if component.dataSource.value = "Aspirin Tablets", then content = "Aspirin Tablets".

[0030] API: Get data by calling other http interfaces, and perform interface call queries based on the configured API address and call parameters; Algorithm description: According to the API address and parameters configured by the component, data is obtained through HTTP requests; expression: Construct an HTTP request: request=HTTPClient.constructRequest(component.dataSource.url, component.dataSource.param); Send a request and get a response: response = HTTPClient.sendRequest(request); Parse response data: content = parseResponse(response); Example: Assume component.dataSource.url = "http: / / api.pharmaceutical.com / adaptation?drugId=", component.dataSource.param = {"drugId": "123456"}; when a request is made to the API through an HTTP client, the response data obtained may be in JSON format, such as {"adaptation": "For relief of mild to moderate pain, such as headaches and toothaches"}, then content = "For relief of mild to moderate pain, such as headaches and toothaches".

[0031] Database: Get data by querying the database, and perform database query based on the configured database connection address, SQL query statement and other parameters; Algorithm description: Based on the database connection address and SQL query statement configured by the component, connect to the database and execute the query to obtain data; expression: Establish a database connection: connection = DBConnection.getConnection(component.dataSource.jdbcUrl); Execute the query: resultSet = connection.executeQuery(component.dataSource.sql); Parse the query results: content = parseResultSet(resultSet); Example: component.dataSource.jdbcUrl=jdbc:mysql: / / localhost:3306 / pharmaceutical_db?useUnicode=true&characterEncoding=utf-8, component.dataSource.sql=SELECT dosage FROM drug_usage WHERE drug_id='123456'; connect to the database and execute the query. Assuming the query result is "1 tablet at a time, 3 times a day", then content = "1 tablet at a time, 3 times a day".

[0032] The instruction manual component contains the following basic fields: component name, component content type, data source, and auxiliary configuration (such as font and color). Depending on the data source type, configure data source-specific fields such as API address, parameters, and data source connection parameters. The instruction manual component is described in JSON data. The basic fields are described as follows: Title: Title, describing the name of this part of the instructions; for example, "Drug Name", "Indications", etc. Parameter type: string Example: title="Drug Name".

[0033] contentType: content type, which describes the content type of this part and supports four types: text, image, video, and handle sub-identifier; Parameter type: string, value range is enumeration type (text, image, video, handle); Example: contentType="text" (indicates that the content of this component is in text form).

[0034] dataSource: Data source, which describes the data source of this part of the content. It supports static, API interface and database. According to different data source types, necessary fields can also be set to support data acquisition according to the data source configuration; Parameter type: string, value range is enumeration type (static, API, database); Unique field configuration: For static types: value: fixed text content; for example, when the component content is a fixed generic name of a drug, value = "aspirin tablets"; For API type: url: API interface address; for example, the interface address for obtaining drug indication information is "http: / / api.pharmaceutical.com / adaptation?drugId="; param: interface call parameter; for example, param = {"drugId":"123456"}, where "123456" is the specific drug ID; For database type: jdbcUrl: database connection address; for example, jdbc:mysql: / / localhost:3306 / pharmaceutical_db?useUnicode=true&characterEncoding=utf-8; sql: SQL query statement; for example, SELECT dosage FROM drug_usage WHERE drug_id='123456' (used to query drug usage and dosage information).

[0035] config: configuration information fields, such as width (component width), style (inline style), defining font, color, size and other attributes; Parameter type: JSON format object; Example: config = {"width": "300px", "style": {"fontFamily": "Arial", "color": "#333333", "fontSize": "14px"}}.

[0036] The instruction manual template is described in JSON data. The main fields include template name, product number, version number, and component list. Template field definition Template Name (templateName): used to distinguish different instruction sheet templates; for example, "Drug Instruction Sheet Template V1"; Parameter type: string Example: templateName="Drug Instructions Template V1".

[0037] Product Code: This is the product code associated with the template, used to accurately obtain the instruction manual template for the corresponding product when registering the logo; Parameter type: string Example: productCode="YP001" (indicates that the template is applicable to the drug with product number YP001).

[0038] Version number (version): records the version information of the template to facilitate version updates and management; Parameter type: string, format such as "1.0" and "2.0"; Example: version="1.0".

[0039] Component List (componentList): An array of manual components arranged in a certain order. The order in which each component is displayed in the manual is determined by its position in the list; Parameter type: Array, where the array elements are the instruction manual components defined above; Example: componentList=[drug name component, indication component, usage and dosage component, adverse reaction component].

[0040] Template generation algorithm a. Template initialization Algorithm description: Based on product category and other information, obtain the corresponding electronic instruction manual template from the template library; Expression: template=templateLibrary.getTemplateByProductCategory(productCategory); Example: If productCategory = "drugs", obtain the instruction sheet template applicable to the drug from the template library.

[0041] b. Component list parsing Algorithm description: Parse the component list in the template and determine the configuration information of each component; Expression: componentConfigs = template.componentList.parseConfigs(); Example: For the above drug insert template, componentConfigs obtained through parsing contains configuration information of the drug name component, indication component, etc., such as component name, content type, data source, etc.

[0042] c. Data acquisition and filling Algorithm description: Process the component list in sequence, obtain data according to the data source information configured by the component, and fill it into the template; expression: Traverse the component list: for component in template.componentList: Get component data: componentData = getDataByComponent(component) (call the corresponding data acquisition algorithm based on the component data source type, such as static data acquisition, API data acquisition, or database data acquisition); Fill data into the template: filledTemplate.addComponentData(componentData); For example: For the drug name component, the static data acquisition algorithm obtains the content "aspirin tablets" and fills it into the corresponding position in the template; for the indication component, the API data acquisition algorithm obtains the content "used to relieve mild to moderate pain, such as headaches, toothaches, etc." and fills it into the position of the indication component in the template. And so on, complete the filling of all component data.

[0043] Identification generation and registration: When the product is completed and offline (or delivered), the identification code of the product is generated through the identification resolution middleware, and then the corresponding electronic instruction manual template is obtained from the template library based on the product information and category; the above template is analyzed to parse out the component list contained in the template; the component list is processed in sequence, and the actual data is obtained from the configured data source according to the component configuration information; after obtaining the actual data corresponding to all components, the actual data is spliced ​​and filled into the template in the order of the component list, and the original identification data packet is obtained. The identification code and the original identification data packet are associated and bound to generate identification data, and then registered with the identification resolution application platform through the identification resolution middleware, and a QR code image (or other identifiable media such as RFID tags) corresponding to the identification code is generated and associated and bound to the product; Specifically: a. Logo generation Identification code generation algorithm: hash operation and serial number splicing; Algorithm description: First, a hash operation is performed on the key information of the product (such as product number, production date, etc.) to obtain a hash value of fixed length. This hash value is then concatenated with an increasing serial number to form the final identification code. Expression: identifierCode=hash / ProductKeyInfo / +sequenceNumber; Parameter definition: Product Key Information (ProductKeyInfo): Select a combination of information that can uniquely identify the product, such as product ID (productId) and production date (productionDate). For example, ProductKeyInfo = productId + "_" + productionDate. Hash algorithm: Use the MD5 hash algorithm to convert ProductKeyInfo into a 128-bit (16-byte) hash value, usually represented as a 32-character hexadecimal string. For example, if ProductKeyInfo = "YP001_2025-10-01", after the MD5 hash operation, the resulting hashValue may be "a5950f56c40c9d3a1580a97327e14f8"; Sequence Number (sequenceNumber): used to distinguish different products with the same product key information. The initial value (seqInitial) of the sequence number is set to 1, and the step size (seqStep) is set to 1. The sequence number increases by one step each time an identification code is generated. For example, the sequenceNumber of the first identification code is 1, the second is 2, and so on. Example calculation: Assume that the product number is "YP001" and the production date is "2025-10-01", then ProductKeyInfo = "YP001_2025-10-01"; After MD5 hash operation, we get hashValue = "a5950f56c40c9d3a1580a97327e14f8"; The initial serial number is 1, so the first identification code is "a5950f56c40c9d3a1580a97327e14f8_1".

[0044] b. Logo registration Registration Process: When a product is completed and offline (or delivered), the identity resolution middleware generates an identification code for the product; Generate a unique identification code for each product according to the above identification code generation algorithm; Obtain the corresponding electronic instruction manual template from the template library according to the product category; Algorithm description: Use product category keywords to search and match in the template library to obtain the corresponding instruction manual template; Expression: template=templateLibrary.getTemplateByProductCategory(productCategory); Parameter definition: Product Category (productCategory): Keywords used to distinguish different categories of products, such as "pharmaceuticals" and "electronic equipment". Template Library: A database or file system that stores instruction manual templates for various product categories.

[0045] Analyze the above template and parse out the list of components contained in the template; Algorithm description: Parse the obtained template and extract the component list information; Expression: componentList = template.parseComponentList(); Example: If the template is a drug insert template, the parsed componentList contains the drug name component, indication component, usage and dosage component, adverse reaction component, etc.

[0046] Process the component list in sequence and obtain data from the configured data source according to the component configuration information; Algorithm description: Traverse the component list and call the corresponding data acquisition algorithm for each component based on its data source type (static, API, database); expression: for component in componentList: if component.dataSource.type=="static": data = component.dataSource.value elif component.dataSource.type=="API": data = getDataFromAPI(component.dataSource.url,component.dataSource.param) elif component.dataSource.type=="database": data=getDataFromDatabase(component.dataSource.jdbcUrl,component.dataSource.sql); Example: For the drug name component, if its data source type is static and component.dataSource.value = "Aspirin Tablets", then the obtained data = "Aspirin Tablets".

[0047] After obtaining the actual data corresponding to all components, the actual data is spliced ​​and filled into the template in the order of the component list to obtain the original data packet of the identification; Algorithm description: After obtaining the actual data corresponding to all components, the actual data is spliced ​​and filled into the template in the order of the component list to obtain the original data packet; Expression: identifierContent = "" + componentData1 + "" + componentData2 + "" + ... + "_" + componentDatann; Example: If the drug name component data is "Aspirin Tablets", the indication component data is "For the relief of mild to moderate pain", and the usage and dosage component data is "1 tablet at a time, 3 times a day", then identifierContent = "Aspirin Tablets_For the relief of mild to moderate pain_1 tablet at a time, 3 times a day".

[0048] The identification code and the original identification data packet are associated and bound by the identification resolution middleware to generate identification data, and the identification data is registered to the identification resolution application platform through the identification resolution middleware; Algorithm description: Use HTTP POST request method to encapsulate the identification code and identification content in the JSON format required by the platform, and send the registration request to the specified platform interface; expression: registerJson={"identifierCode":identifierCode, "identifierContent":identifierContent} response=sendHttpPostRequest(platformRegisterUrl, registerJson) Parameter definition: Platform registration interface address (platformRegisterUrl): the identifier registration interface address provided by the Industrial Internet Identifier Resolution Platform, for example, "http: / / [platform domain name] / api / register"; Registration request timeout: Set the time to wait for the platform to respond after sending the request, such as 60 seconds.

[0049] Generate a QR code image (or RFID tag) corresponding to the identification code and associate it with the product; Algorithm description: Use a QR code generation library (such as Python's qrcode library) to convert the identification code into a QR code image; for RFID tags, use the corresponding tag writing device to write the identification code into the tag; expression: For QR code generation: qrCodeImage = qrcode.make(identifierCode) qrCodeImage.save("qrCodePath / "+identifierCode+".png") Parameter definition: QR code storage path (qrCodePath): the folder path used to store the generated QR code image, such as " / data / qrCodes / "; RFID tag writing parameters: including tag type, frequency, etc., are configured according to the specific RFID device and tag specifications.

[0050] Identification resolution: The user scans the QR code on the product packaging (or other identifiable media such as RFID tags) through a terminal device to obtain the identification code, calls the Industrial Internet Identification Resolution Platform interface to resolve the identification code, and obtains the identification data registered in the identification registration step; Identification data supports multiple forms of presentation, including text, images, videos, and sub-identifications. For text, images, and videos, the data obtained by the component is the actual data. If the identification data contains sub-identifications, the sub-identifications must be parsed to obtain the actual identification data.

[0051] Specifically: a. User request processing Scan the QR code to obtain the identification code: Algorithm description: The user scans the QR code on the product packaging with a terminal device (such as a mobile phone). The terminal device's scanning application decodes the QR code image and obtains the identification code stored in it; Expression: identifierCode=qrCodeScanner.decode(qrCodeImage); Parameter definition: qrCodeImage: QR code image data, generated by the QR code generation device based on the identification code and printed on the product packaging; qrCodeScanner: A QR code scanning application or software development kit (SDK) on a terminal device that can decode a QR code image into an identification code.

[0052] Send a parsing request: Algorithm description: The application on the terminal device encapsulates the obtained identification code into a resolution request and sends it to the Industrial Internet identification resolution platform via an HTTP GET request; Expression: parseRequestUrl=platformParseUrl+“?identifierCode=”+identifierCode; Example: If platformParseUrl="http: / / [platform domain name] / api / parse", identifierCode="a5950f56c40c9d3a1580a97327e14f8_1", then parseRequestUrl="http: / / [platform domain name] / api / parse?identifierCode=a5950f56c40c9d3a1580a97327e14f8_1".

[0053] b. Platform analysis and processing Receive parsing request: Algorithm description: The interface service of the Industrial Internet Identity Resolution Platform receives a resolution request sent by a terminal device and resolves the identification code parameters in the resolution request; Expression: identifierCode = parseRequest.getParameter("identifierCode"); Parameter definition: parseRequest: The received HTTP GET request object, including request parameters and header information.

[0054] Query identification content: Algorithm description: The platform searches the database for the corresponding identification content based on the identification code. The identification content is the electronic instruction manual data associated with the identification code stored during the identification registration phase. Expression: identifierContent=database.query("SELECT content FROMidentifier_table WHERE code='"+identifierCode+ "'"); Parameter definition: identifier_table: The database table used by the Industrial Internet Identifier Resolution Platform to store the correspondence between identification codes and identification content; code: A field in a database table used to store identification codes; content: A field in the database table used to store the identification content (i.e., electronic instruction manual data) corresponding to the identification code.

[0055] Process sub-ID (if present): Algorithm description: If the identifier content contains sub-identifiers (i.e., components whose contentType is handle), the sub-identifiers need to be recursively parsed until all the actual data content is obtained; expression: for component in identifierContent.components: if component.contentType=="handle": subIdentifierCode=component.subIdentifierCode subIdentifierContent=database.query("SELECT content FROM identifier_table WHERE code = '" + subIdentifierCode + "'") Replace component.subIdentifierContent with subIdentifierContent; Example: Assume that a component in the identifier content has a contentType of handle and its subIdentifierCode = "sub_code_001". The platform queries the database to obtain subIdentifierContent = "actual sub-identifier data content" and then replaces the content of the sub-identifier component with the actual data content.

[0056] c. Return the parsing results Assembly analysis results: Algorithm description: The parsed identification content (including processed sub-identification content) is assembled according to a certain data format (such as JSON) and prepared to be returned to the terminal device; Expression: parseResult={"identifierCode":identifierCode, "content":identifierContent}; Example: If identifierCode = "a5950f56c40c9d3a1580a97327e14f8_1", and identifierContent contains information such as the drug name and indications, then parseResult = {"identifierCode": "a5950f56c40c9d3a1580a97327e14f8_1", "content": {"drugName": "Aspirin tablets", "adaptation": "For the relief of mild to moderate pain"}}.

[0057] d. Send analysis results Algorithm description: The platform returns the assembled parsing results to the terminal device via HTTP response. After receiving the parsing results, the terminal device can pass them to the electronic manual rendering module for further processing; Expression: sendHttpServletResponse(parseResult).

[0058] Generate rendering: The rendering generation module processes the identification data obtained by parsing and generates an electronic instruction manual that is compatible with the terminal; Specifically: a. Receive identification data Get the parsing results: Algorithm description: The electronic manual rendering module receives the parsing result from the logo parsing module. The result is usually the logo content data encapsulated in JSON format. Expression: parseResult = identifierParseModule.getResult(); Parameter definition: parseResult: The parsing result returned by the identifier parsing module, which includes the identifier code and the identifier content (electronic instruction manual data) corresponding to the identifier code. For example, parseResult = {"identifierCode":"a5950f56c40c9d3a1580a97327e14f8_1", "content":{"drugName":"Aspirin tablets","adaptation":"For the relief of mild to moderate pain"}}.

[0059] b. Data processing Data format conversion: Algorithm description: Convert the identification content data in the parsing result into a format suitable for rendering, such as HTML, XML, etc. Expression: renderableData = convertToRenderFormat(parseResult.content); Example: If the target rendering format is HTML, convert each component in the identified content into the corresponding HTML element; for example, convert the drug name component "Aspirin Tablets" into <h1> Aspirin tablets< / h1> , the indication component "for the relief of mild to moderate pain" is converted to For relief of mild to moderate pain .

[0060] c. Rendering generation Select a rendering template based on the terminal device type: Algorithm description: According to the type of user terminal device (such as mobile phone, tablet, computer, etc.), select the corresponding rendering template from the rendering template library; Expression: renderTemplate=renderTemplateLibrary.getTemplateByDeviceType(deviceType); Parameter definition: deviceType: The type of the user's terminal device, which can be determined by the terminal device's User-Agent and other information; for example, deviceType = "mobile" (mobile phone), "tablet" (tablet), "desktop" (computer).

[0061] Fill data into the rendering template: Algorithm description: Fill the converted renderable data into the selected rendering template to generate the final electronic instruction manual; Expression: finalManual=renderTemplate.fillData(renderableData); Example: Assume that the selected mobile device rendering template is an HTML template, which contains layout structures such as title and content area; <h1> Aspirin tablets< / h1> Fill the title area of ​​the template with the HTML element For relief of mild to moderate pain Fill in the content area and finally generate a complete electronic manual in HTML format.

[0062] Generate a visual interface: Algorithm description: Convert the generated electronic manual data into a user-visible interface, usually involving calling the browser engine or other display components of the terminal device for rendering; Expression: displayResult = terminalDevice.render(finalManual); Parameter definition: finalManual: The final electronic manual data, in a format that can be displayed by terminal devices, such as HTML and XML; terminalDevice: The user's terminal device, which has a display interface and rendering engine (such as a browser engine).

[0063] Data update: When product information changes due to upgrades, optimizations, etc., the manual is updated. The identification code is parsed to the identification data of the corresponding product, and the old data in the identification data is replaced with the latest data. The identification update is completed through the identification resolution middleware; Specifically: a. Receive update request Get update parameters: Algorithm description: The identity resolution middleware receives an update request from the product management system or other authorized system. The request contains information such as the product identification code to be updated and the updated instruction manual content. Expression: updateRequest={"identifierCode":identifierCode, "newContent":newContent}; Parameter definition: identifierCode: the identification code of the product to be updated; for example, "a5950f56c40c9d3a1580a97327e14f8_1"; newContent: The updated content of the electronic instruction manual, which is usually new component data encapsulated in JSON format; for example, newContent={"drugName":"Aspirin Tablets (New Edition)","adaptation":"For the relief of mild to moderate pain, with new indications"}.

[0064] b. Parsing update request Verify the legitimacy of the request: Algorithm description: Checks whether the update request comes from an authorized system or user, and verifies whether the request contains valid authorization information (such as API keys, tokens, etc.); Expression: isValidRequest=verifyAuthorization(updateRequest.authorizationInfo); Parameter definition: authorizationInfo: updates the authorization information in the request, for example, "Bearer token12345"; verifyAuthorization: Authorization verification function, used to check whether the authorization information is valid.

[0065] Extract updated data: Algorithm description: Extract the identification code and new specification content from the update request; Expression: identifierCode=updateRequest[“identifierCode”], newContent=updateRequest[“newContent”].

[0066] c. Update identification data Query old identification data: Algorithm description: Query old identification data from the database of the Industrial Internet identification resolution platform based on the identification code; Expression: oldData=database.query("SELECT content FROM identifier_tableWHERE code='"+ identifierCode+"'"); Parameter definition: identifier_table: a database table that stores the correspondence between identification codes and identification contents; code: the identification code field in the database table; content: identifies the content field in the database table.

[0067] Merge old and new data: Algorithm description: Merge the new instruction manual content with the old identification data, usually by overwriting the corresponding part of the old data with the new data; Expression: updatedData=mergeData(oldData, newContent); Example: Assume that the old data is {"drugName":"Aspirin Tablets","adaptation":"For the relief of mild to moderate pain"}, and the new content is {"drugName":"Aspirin Tablets (New Edition)","adaptation":"For the relief of mild to moderate pain, new indications"}, after merging, updatedData = {"drugName":"Aspirin Tablets (New Edition)","adaptation":"For the relief of mild to moderate pain, new indications"}.

[0068] Update the database: Algorithm description: Update the merged data into the database; Expression: database.update("UPDATE identifier_table SET content='"+updatedData+"'WHERE code='"+identifierCode +"'").

[0069] d. Complete logo update Send update notifications: Algorithm description: Send an update notification to the identity resolution platform to ensure that the platform knows that the identity data has been updated; Expression: sendUpdateNotification(platformUrl, identifierCode); Parameter definition: platformUrl: identifies the notification interface address of the resolution platform, for example, "http: / / [platform domain name] / api / notifyUpdate"; identifierCode: The updated identifier code.

[0070] Return the updated result: Algorithm description: Return the update result to the requester, informing whether the update is successful; Expression: returnResult = {"success": True, "message": "Update successful"} or returnResult = {"success": False, "message": "Update failed, reason..."}.

[0071] Please see the attached Figure 5 , an electronic instruction manual generation system based on identifier resolution, used to implement an electronic instruction manual generation method based on identifier resolution, comprising: Identity resolution middleware: acts as a data flow hub, used for identity registration, resolution, and update; Component and template design module: used to create, store and manage manual component definitions and manual templates; Identity generation and registration module: used for identity data generation, including template instantiation, data acquisition, identity generation and identity registration; Identification resolution module: used to obtain identification data based on the identification code; Rendering generation module: used to receive identification data, render the data, and generate an electronic instruction manual that is compatible with the terminal.

[0072] Example 1 Taking medicine as an example, components and templates are defined. Four examples of components are as follows: Example 1: {『title』:『Drug name』, / / title 〝contentType":〝text", / / The content is a text string 〝dataSource":〝static", / / The data source is static data and does not need to be obtained from other sources 〝value":〝Xiao Chaihu Granules" / / Content data "config":{"style": "color: blue; font-size: 16px;", width: 100% Example 2: {〝title":〝ingredients", / / title 〝contentType":〝image", / / The content is an image 〝dataSource":〝API", / / The data source is dynamic data, obtained through API interface query "ur1":"http: / / 127.0.0.1 / query", / / http address 〝param〞:〝id=´1´" / / parameter} Example 3: {〝title":〝Characteristics", / / title 〝contentType":〝video", / / The content is video 〝dataSource":〝API", / / The data source is dynamic data, obtained through API interface query "ur1":"http: / / 127.0.0.1 / query", / / http address 〝param":〝id=´1´" / / parameter} Example 4: {〝title":〝Functions and indications", / / title 〝contentType":〝handle", / / The content is a sub-identifier 〝dataSource", / / 〝database" / / The data source is dynamic data, obtained by querying the database "jdbcUrl" :"jdbc:mysql: / / 127.0.0.1:3306 / test" 〝username":〝admin", / / username 〝password":〝password", / / password 〝sq1":〝select desc from table where id=´1´" / / Executed SQL} In the above manner, other necessary components can be defined, such as contraindications, usage and dosage, adverse reactions, etc.

[0073] Taking medicine as an example, the template JSON data description example is as follows: Example 5: {〝name":〝Xiao Chaihu Granule Instructions", / / Model name 〝productCode":〝123456", / / product number 〝version":〝v1.0", / / version number 〝1ist":[{}, / / Component configuration 1, field reference example 1 {}, / / Component configuration 2, field reference example 2 {}, / / Component configuration 3, field reference example 3 {}, / / Component configuration 4, field reference example 4]} As attached Figure 3 As shown, taking the template shown in Example 5 as an example, the detailed process of obtaining identification data is explained: a. Query the template library based on product code, batch number and other information to obtain template JSON data; b. Parse the template JSON and get the component list; c. Traverse the component list and obtain content data in sequence; dataSource=static, static content parses the value field to obtain data dataSource=API, data comes from the API interface ① Parse JSON information and obtain field parameters such as url and param; ②Build an HttpClient object and initiate an http request; ③Wait for http response and parse the returned data; dataSource=database, data comes from the database ① Parse JSON information and obtain field parameters such as jdbcUrl and sql; ②Establish a database connection and initiate a query request; ③Wait for the database to respond and parse the returned data; d. Replace the above-obtained content data into the template to obtain the complete original data e. Assemble the identification codes to obtain complete identification data and register it to the identification resolution platform.

[0074] As attached Figure 4 As shown, for the type of handle in the contentType field of the component, the content of the identifier resolution is the sub-identifier, and the sub-identifier needs to be resolved to obtain the actual data content.

[0075] From the above description, it can be seen that the above-mentioned embodiments of the present invention achieve the following technical effects: decoupling of content and carrier is achieved, and dynamic updates are supported. The QR code is only an identifier and does not contain the content of the instruction manual. Its specific content is stored in the industrial Internet identification resolution platform system; when the product is updated or optimized, it is only necessary to modify the original content related to the identifier. The user can automatically obtain the latest instruction manual when scanning the code next time without changing the physical QR code, thereby simplifying the instruction manual management process.

[0076] It provides flexibility and configurability. Through the design of components and templates, the same product can use the same template to achieve template reuse; at the same time, the diversified configuration of component data sources enhances the dynamics and manageability of content.

[0077] Generate on demand, saving costs. Data acquisition and final rendering are only performed when the user actually scans the code, avoiding the overhead of pre-generating and maintaining massive static instruction manual files for all products (such as storage, management, and distribution costs).

[0078] It has strong adaptability. For the same product manual data package, the rendering module can generate the optimal display effect according to the terminal device type.

[0079] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present invention is limited to these examples. Within the scope of the present invention, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the present invention as described above, which are not provided in detail for the sake of simplicity.

[0080] The present invention is intended to cover all such substitutions, modifications and variations that fall within the broad scope of the specification. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for generating an electronic instruction manual based on identifier resolution, characterized in that: include: Develop and deploy identity resolution middleware: The identity resolution middleware acts as a data flow hub, connecting to the Industrial Internet identity resolution platform and connecting to various business systems within the enterprise. Component and template design: Define manual components and templates. Each manual component describes a part of the manual content. The manual template is composed of a series of manual components combined in a certain order. Identification generation and registration: Generate an identification code, obtain the original identification data packet, associate and bind the identification code and the original identification data packet to generate identification data, and register it with the identification resolution application platform through the identification resolution middleware, generate a QR code image corresponding to the identification code, and associate and bind it with the product; Identification resolution: The user scans the QR code on the product packaging through a terminal device to obtain the identification code, calls the Industrial Internet Identification Resolution Platform interface to resolve the identification code, and obtains the identification data registered in the identification registration step; Generate rendering: The rendering generation module processes the identification data obtained by parsing and generates an electronic instruction manual that is compatible with the terminal.

2. The method for generating an electronic instruction manual based on identifier resolution according to claim 1, wherein: The identity resolution middleware is a software module responsible for processing identity data registration, update and resolution requests. Its functions include: aggregating business data, generating identity codes, registering identities, enterprises and prefixes; the identity resolution middleware provides a service interface for other modules to call.

3. The method for generating an electronic instruction manual based on identifier resolution according to claim 1, wherein: The instruction manual component describes a portion of the instruction manual content. Each component independently configures the data source of the instruction manual content, including static data, API interfaces, and database queries. Static data: fixed text specified when defining a component, which does not need to be obtained from the outside; API: Get data by calling other http interfaces, and perform interface call queries based on the configured API address and call parameters; Database: Get data by querying the database, and perform database query based on the configured database connection address, SQL query statement and other parameters.

4. The method for generating an electronic instruction manual based on identifier resolution according to claim 2, wherein: The instruction manual component contains the following basic fields: component name, component content type, data source, and auxiliary configuration. Depending on the type of data source, data source-specific fields are configured. The instruction manual component is described in JSON data.

5. The method for generating an electronic instruction manual based on identifier resolution according to claim 3, wherein: The instruction manual template is described in JSON data, and the main fields include template name, product number, version number and component list.

6. The method for generating an electronic instruction manual based on identification resolution according to claim 1, characterized in that: The generating of the identification code includes: generating the identification code of the product through the identification resolution middleware when the product is completed and offline or delivered.

7. The method for generating an electronic instruction manual based on identification resolution according to claim 6, characterized in that: The obtaining of the original data packet includes: Obtain the corresponding electronic instruction manual template from the template library based on product information and category; Analyze the above template and parse out the list of components contained in the template; Process the component list in sequence and obtain the actual data from the configured data source according to the component configuration information; After obtaining the actual data corresponding to all components, the actual data is spliced ​​and filled into the template in the order of the component list to obtain the original data packet.

8. The method for generating electronic instructions based on identifier resolution according to claim 1, characterized in that: The industrial Internet identification resolution platform interface is called to resolve the identification code and obtain the identification data registered in the identification registration step, including: the identification data supports multiple forms of presentation, supporting text, images, videos and sub-identifiers; for the three types of text, images and videos, the data obtained by the component is the actual data, and if the identification data contains a sub-identifier, the sub-identifier needs to be resolved before the actual identification data can be obtained.

9. The method for generating an electronic instruction manual based on identifier resolution according to claim 1, wherein: It also includes data updates. When product information changes due to upgrades or optimizations, the instructions are updated, the identification code is parsed to the identification data of the corresponding product, the old data in the identification data is replaced with the latest data, and the identification update is completed through the identification resolution middleware.

10. An electronic instruction manual generation system based on identifier resolution, characterized in that: A method for generating an electronic instruction manual based on identifier resolution, for implementing any one of claims 1 to 9, comprising: Identity resolution middleware: acts as a data flow hub, used for identity registration, resolution, and update; Component and template design module: used to create, store and manage manual component definitions and manual templates; Identity registration module: used for identity data generation, including template instantiation, data acquisition, identity generation and identity registration; Identification resolution module: used to obtain identification data based on the identification code; Rendering generation module: used to receive identification data, render the data, and generate an electronic instruction manual that is compatible with the terminal.

Images