Page generation system and page generation method

TW202638294AActive Publication Date: 2026-09-16DIGIWIN SOFTWARE CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
TW114113876
Authority / Receiving Office
TW · TW
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-03-13
Filing Date
2025-04-11
Publication Date
2026-09-16
Estimated Expiration
2045-04-10

AI Technical Summary

Technical Problem

The existing page design and development process for business management pages requires collaboration among multiple roles, leading to inefficiencies in manpower and time consumption, resulting in low development efficiency.

Method used

A page generation system and method that automatically generates pages using a scene analysis module, feature matching module, and element integration module, analyzing scene input data to determine page component elements and their spatial relationships, and assembling them based on user profile data.

Benefits of technology

The system effectively reduces development time and cost by automatically generating customized pages, eliminating the need for developers to understand complex configuration rules and allowing for minor user adjustments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure TWG2TA001076056_001
    Figure TWG2TA001076056_001
  • Figure TWG2TA001076056_002
    Figure TWG2TA001076056_002
  • Figure TWG2TA001076056_003
    Figure TWG2TA001076056_003
Patent Text Reader

Abstract

A page generation system and a page generation method are provided. The page generation system includes a storage device and a processor. The storage device stores a scene analysis module, a feature matching module and an element integration module. The processor is coupled to the storage device and executes the scene analysis module, the feature matching module and the element integration module. The scene analysis module generates scene feature data based on scene input data. The feature matching module generates page component element data according to the scene feature data. The element integration module organizes the page component data into a page according to an element spatial position relationship information and user portrait data.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] This invention relates to a data processing technology, and more particularly to a page generation system and a page generation method. [Previous Technology]

[0002] In the existing design process of business management pages, page design and development require collaboration from multiple roles, including the Product Owner (PO) and System Architect (SA). The PO and SA need to determine the page prototype based on the actual business scenario and deliver the prototype to the application developers for manual assembly on the development platform. Therefore, the existing page design and development process is lengthy and consumes a significant amount of manpower and time, resulting in low development efficiency. [Summary of the Invention]

[0003] This invention relates to a page generation system and a page generation method that can automatically generate pages.

[0004] According to an embodiment of the present invention, the page generation system of the present invention includes a storage device and a processor. The storage device stores a scene analysis module, a feature matching module, and an element integration module. The processor is coupled to the storage device and executes the scene analysis module, the feature matching module, and the element integration module. The scene analysis module generates scene feature data based on scene input data. The feature matching module generates page component element data based on the scene feature data and user profile data. The element integration module assembles the page component element data into a page based on the spatial positional relationship information of the elements.

[0005] According to an embodiment of the present invention, the page generation method of the present invention includes the following steps: generating scene feature data based on scene input data through a scene analysis module; generating page component data based on the scene feature data through a feature matching module; and assembling the page component data into a page through an element integration module based on element spatial location relationship information and user profile data.

[0006] Based on the above, the page generation system and page generation method of the present invention can automatically analyze the scene input data input by the user to generate scene feature data, and obtain the corresponding page component element data according to feature matching. Furthermore, the page generation system and page generation method of the present invention can automatically assemble the corresponding page based on the page component element data and the corresponding element spatial position relationship information.

[0007] In order to make the above features and advantages of the present invention more apparent and understandable, specific embodiments are described below, and detailed descriptions are given in conjunction with the accompanying drawings.

Implementation Method

[0008] Reference will now be made in detail to exemplary embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same element symbols are used in the drawings and description to denote the same or similar parts.

[0009] Figure 1 is a schematic diagram of a page generation system according to an embodiment of the present invention. Referring to Figure 1, the page generation system 100 includes a processor 110 and a storage device 120. The processor 110 is coupled to the storage device 120. The processor 110 and the storage device 120 can be implemented as a server. In this embodiment, the page generation system 100 may be set up in a cloud server, for example, so that page developers or users can connect to it via wired or wireless communication methods to operate it, but the present invention is not limited thereto. In one embodiment, the page generation system 100 may also be implemented by multiple processors and storage devices, and the multiple processors and the multiple storage devices may be separately set up in different cloud devices or computing devices.

[0010] In this embodiment, the processor 110 may be a system on a chip (SOC), or may include, for example, a central processing unit (CPU) or other programmable general-purpose or special-purpose microprocessors, digital signal processors (DSPs), programmable controllers, application-specific integrated circuits (ASICs), programmable logic devices (PLDs), other similar processing devices, or combinations thereof. The storage device 120 may include, for example, dynamic random access memory (DRAM), flash memory, or non-volatile random access memory (NVRAM).

[0011] Figure 2 is a schematic diagram of the modules of the page generation system according to an embodiment of the present invention. Referring to Figures 1 and 2, in this embodiment, the storage device 120 can store the scene analysis module 111, the feature matching module 112, and the element integration module 113 shown in Figure 2. In this embodiment, the scene analysis module 111, the feature matching module 112, and the element integration module 113 can be implemented using programming languages ​​such as JSON (JavaScript Object Notation), Extensible Markup Language (XML), or YAML. Furthermore, in this embodiment, the page generation system 100 may further include a scene feature database 211, an element feature database 212, a spatial location relationship database 213, and a user profile (or user image) database 214. The scene feature database 211, the element feature database 212, the spatial location relationship database 213, and the user profile database 214 can be stored in the storage device 120 or in other external storage devices.

[0012] Figure 3 is a flowchart of a page generation method according to an embodiment of the present invention. Referring to Figures 1 to 3, the page generation system 100 can perform the following steps S310 to S330. In this embodiment, the user (or developer) can provide scene input data 201 through an input device. The input device may be, for example, a keyboard, mouse, and / or microphone, etc., and the present invention is not limited thereto. In this embodiment, the processor 110 can obtain the scene input data 201. In step S310, the scene analysis module 111 generates scene feature data 202 based on the scene input data 201. In step S320, the feature matching module 112 generates page component element data 204 based on the scene feature data 202. In step S330, the element integration module 113 assembles the page component element data 204 into a page 207 based on the element spatial position relationship information 205 and the user profile data 206. The user profile data 206 may include, for example, information such as role, age, gender, or position. The element integration module 113 can combine relevant scenario data with user profile data 206 to combine the overall page. For example, user profile data 206 can be used to determine information for a specific region or industry, where the background color of the page corresponding to different regions or industries may be different.

[0013] Specifically, in this embodiment, the scene analysis module 111 can analyze the scene input data 201 to determine the corresponding scene data. Then, the scene analysis module 111 can determine the scene category based on the corresponding scene data and read the scene feature data 202 corresponding to the scene category from the scene feature database 211. The scene data may include multiple data corresponding to different data dimensions. In this embodiment, the scene data may include at least one of user profile data, time information data, event information data, geographic information data, and terminal information data.

[0014] In this embodiment, the scene analysis module 111 provides scene feature data 202 to the feature matching module 112. In this embodiment, the feature matching module 112 can perform feature vector similarity calculation between the scene feature data 202 and the element feature data 203 provided by the element feature database 212 to determine the generation of page composition element data 204, wherein the feature vector similarity calculation is implemented based on an improved version of cosine similarity calculation.

[0015] In this embodiment, the improvement of the cosine similarity calculation is achieved by using an improved Term Frequency-Inverse Document Frequency (TF-IDF) algorithm based on the following formula (1). In formula (1), the symbol “i” represents the feature vector value of the scene feature. The symbol “i” represents the feature vector value of the element feature. The symbol “i” represents the weight coefficient of the scene as a degree. The symbol “i” represents the scene dimension (i is a positive integer). In this embodiment, the feature matching module 112 can perform weighted processing on the similarity of the feature vectors of each dimension to improve the accuracy of the algorithm. In this regard, the weight coefficient “i” can be adjusted according to the initial value and range of the weight coefficient set by the design expert, or according to the historical data of the dimension input by the user. ………Formula (1)

[0016] Furthermore, the feature matching module 112 can record the scene dimensions input by the user and classify them into a database. The feature matching module 112 can use the following formula (2) to calculate the proportion of each dimension to the total number of dimensions based on the number of individual dimensions and the total number of dimensions in the database (the higher the number of individual dimensions, the more important the dimension). The feature matching module 112 can use the following formula (3) to multiply the initial weight value of each dimension by the proportion of each dimension, and normalize the result to obtain the optimized weight coefficient of each dimension. In the following formula (2), the symbol “” represents the number of each dimension in the database. The symbol “” represents the total number of all dimensions in the database. The symbol “” represents the optimized dimension weight coefficient. ………Formula (2)………Formula (3)

[0017] In this embodiment, the scene analysis module 111 can also analyze the scene input data 201 to obtain user profile data 206, and store the user profile data 206 in the user profile database 214. The user profile data 206 may include information such as role, age, gender, and position. In this embodiment, the element integration module 113 can read the corresponding element spatial location relationship information 205 from the spatial location relationship database 213. The element integration module 113 can read the corresponding user profile data 206 from the user profile database 214. The element integration module 113 can generate a page (page data) 207 based on the page composition element data 204, the element spatial location relationship information 205, and the user profile data 206. Therefore, the page generation system 100 and its method in this embodiment can effectively and automatically generate the page 207 required by the user. It should be noted that the page 207 may refer to a customized page of a specific application program or webpage used by a specific user for business management.

[0018] In addition, the page generation system 100 can further receive adjustment instructions input by the user to adjust the content of the page 207 generated by the element integration module 113. Furthermore, the page generation system 100 can also record the user's adjustment history of the page 207 to update the scene feature database 211, the element feature database 212, and the spatial location relationship database 213, so as to effectively optimize the scene feature data, element feature data, and spatial location relationship data.

[0019] Figure 4 is a flowchart of scene analysis according to an embodiment of the present invention. Referring to Figures 2 and 4, the following steps S401-S412 further illustrate the implementation details. In step S401, the processor 110 can obtain scene input data 201. In step S402, the scene analysis module 111 can determine whether the scene input data 201 is voice data or text data. In this embodiment, when the scene input data 201 is voice data, in step S403, the scene analysis module 111 inputs the voice data to a natural language processing model to convert the scene input data 201 into text data format. In step S404, the scene analysis module 111 can input the scene input data 201 in text data format to a machine learning model (a large model with a large number of parameters). Then, in step S406, the scene analysis module 111 can generate scene data through the machine learning model.

[0020] In this embodiment, when the scene input data 201 is text data, the scene analysis module 111 determines whether the text data conforms to the data specifications. When the text data conforms to the data specifications, in step S406, the scene analysis module 111 can directly generate scene data based on the text data. When the text data does not conform to the data specifications, in step S404, the scene analysis module 111 can input the text data into a machine learning model (a large model with a large number of parameters) to generate the scene data.

[0021] In step S407, the scene analysis module 111 can determine whether the scene dimension of the scene data is greater than or equal to the dimension threshold. When the scene dimension of the scene data is less than the dimension threshold (the dimension threshold may be, for example, 2), in step S408, the scene analysis module 111 outputs input prompt information. The page generation system 100 can display the input prompt through the display interface to request the user to supplement the scene information. When the scene dimension of the scene data is greater than or equal to the dimension threshold, in step S409, the feature matching module 112 performs scene category analysis based on the scene data to determine the scene category. In this embodiment, the feature matching module 112 can perform feature vector similarity calculation between the scene feature data and the element feature data 203 provided by the element feature database 212 to determine the element data 204 to be generated as page components. Alternatively, the feature matching module 112 can read the element feature database 212 based on the user selection and scene category recommendation information to obtain the element feature data 203.

[0022] In step S410, the feature matching module 112 determines whether a scene category has been identified. In step S411, if the scene category analysis fails to identify the scene category, the feature matching module 112 outputs input prompts. The page generation system 100 can display these prompts via a display interface to request the user to supplement the scene information. The feature matching module 112 can directly calculate the similarity between the scene category and the categories in the database based on the user's supplemented scene information. Furthermore, if no matching scene category exists, the feature matching module 112 can also directly request the user to input the scene category information. In step S412, the feature matching module 112 can generate scene category recommendation information. The feature matching module 112 can read the feature database 212 based on the scene category recommendation information with the highest similarity after similarity comparison to obtain page component element data 204. Therefore, the element integration module 113 can obtain appropriate page component element data 204 to combine with the corresponding scene for subsequent page generation processing.

[0023] Figure 5 is a data structure diagram of scene feature data according to an embodiment of the present invention. Referring to Figure 5, for example, the data structure of scene feature data can be as shown in Figure 5. In this embodiment, the page generation system can analyze scene input data to obtain scene category 511 and scene story 521. In this example, scene category 511 may correspond to project management scene and deliverable management (subcategory) for example. Scene story 521 may correspond to "XX scene story" for example. Scene category 511 may correspond to multiple dimensions 531 to 535, wherein the multiple dimensions 531 to 535 may correspond to "person", "event", "time", "place" and "terminal" for example. An instance of dimension 531 ("person") may be "responsible person" for example. An instance of dimension 532 ("event") may be "file management" for example. The multiple dimensions 531 to 535 each have corresponding features 541 to 545, and features 541 to 545 may correspond to different instances respectively. An instance of feature 541 may be "view" and "high privileges" for example. Examples of feature 542 could be "download", "upload", and "large data volume". Examples of feature 543 could be "time type". Furthermore, the features corresponding to the instances "view", "high privilege", "download", and "upload" can be further converted into corresponding feature vector values ​​551~554.

[0024] Figure 6 is a data structure diagram of the element feature data according to an embodiment of the present invention. Referring to Figure 6, for example, the data structure of the element feature data can be as shown in Figure 6. The element feature database can store element feature data corresponding to different scene categories. Taking a certain scene category as an example, the page composition element data 611 can correspond to multiple dimensions 621-624, such as "control", "operation", "operation" and "layout". An example of dimension 621 can be "table". An example of dimension 622 can be "batch download". Dimensions 621-624 can correspond to different features 631-634 respectively. An example of feature 631 can be "large data volume" and "view". An example of feature 632 can be "download" and "batch operation". Furthermore, the features corresponding to the instances "large data volume", "view", "download" and "batch operation" can be further converted into corresponding feature vector values ​​641-644. In this regard, the page generation system can determine, for example, that the feature vector values ​​551~554 of Figure 5 and the feature vector values ​​641~644 of Figure 6 have the highest feature vector similarity through the similarity calculation of the above embodiments.

[0025] Figure 7 is a data structure diagram of spatial location relationship data according to an embodiment of the present invention. Referring to Figure 7, for example, the spatial location relationship data can be as shown in Figure 7. The page generation system reads the database according to the user profile data and scene category to obtain the corresponding spatial location relationship data. The spatial location relationship data may, for example, have controls 711, capabilities 721, and locations 731. The page generation system can fill the corresponding instances "table", "batch download", and "upper right corner" into the corresponding spatial locations on the page according to the content of the above-mentioned page component data 611 to effectively generate the page.

[0026] In summary, the page generation system and method of the present invention can automatically generate design pages based on scenario input data corresponding to specific business scenarios input by users, and can be published after minor adjustments, thereby effectively reducing the time required for page development and effectively reducing development costs. Furthermore, the page generation system of the present invention allows developers to avoid understanding the complex configuration rules of the development platform, effectively reducing learning and setup costs.

[0027] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention. [Simplified Explanation of the Diagram]

[0028] Figure 1 is a system schematic diagram of the page generation system according to an embodiment of the present invention. Figure 2 is a module schematic diagram of the page generation system according to an embodiment of the present invention. Figure 3 is a flowchart of the page generation method according to an embodiment of the present invention. Figure 4 is a flowchart of scene analysis according to an embodiment of the present invention. Figure 5 is a data structure diagram of scene feature data according to an embodiment of the present invention. Figure 6 is a data structure diagram of element feature data according to an embodiment of the present invention. Figure 7 is a data structure diagram of spatial position relationship data according to an embodiment of the present invention.

Claims

1. A page generation system, comprising: Storage device, including storage scene analysis module, feature matching module, and element integration module; The system includes a processor, coupled to the storage device, and executes the scene analysis module, the feature matching module, and the element integration module. The scene analysis module generates scene feature data based on scene input data, and the feature matching module generates page component data based on the scene feature data. The element integration module assembles the page component data into a page based on element spatial relationship information and user profile data. When the scene input data is text data, the scene analysis module determines whether the text data conforms to data specifications. If the text data conforms to the data specifications, the scene analysis module directly generates scene data based on the text data. If the text data does not conform to the data specifications, the scene analysis module inputs the text data into a machine learning model to generate the scene data. When the scene input data is speech data, the scene analysis module inputs the speech data into a natural language processing model to convert the scene input data into text data format and inputs it into the machine learning model to generate the scene data. The scene analysis module determines whether the scene dimension of the scene data is greater than or equal to a dimension threshold. When the scene dimension of the scene data is less than the dimension threshold, the scene analysis module outputs input prompts. When the scene dimension of the scene data is greater than or equal to the dimension threshold, the feature matching module performs scene category analysis based on the scene data to determine the scene category.

2. The page generation system as described in request item 1, wherein when the scene category analysis fails to determine the scene category, the feature matching module outputs another prompt input information; and when the scene category analysis determines the scene category, the feature matching module outputs scene category recommendation information corresponding to the scene category.

3. The page generation system as described in request item 2, wherein the feature matching module performs feature vector similarity calculation between the scene feature data and the feature feature data provided by the feature feature database to determine the component element data of the generated page.

4. The page generation system as described in request item 3, wherein the feature matching module reads the feature database based on user selection and the scene category recommendation information to obtain feature data.

5. The page generation system as described in request item 3, wherein the feature matching module reads the feature database based on the highest similarity among the scene category recommendation information to obtain the page component element data.

6. The page generation system as described in claim 3, wherein the feature vector similarity calculation is implemented based on an improved version of cosine similarity calculation.

7. The page generation system as described in Request 1, wherein the scene data includes at least one of the user profile data, time information data, event information data, geographic information data, and terminal information data.

8. A page generation method, comprising: The scene analysis module generates scene feature data based on the scene input data; The feature matching module generates page component data based on the scene feature data; The page is composed of element data using an element integration module based on element spatial location relationship information and user profile data. The step of generating the scene feature data includes: when the scene input data is text data, the scene analysis module determines whether the text data conforms to data specifications; when the text data conforms to the data specifications, the scene analysis module directly generates scene data based on the text data; when the text data does not conform to the data specifications, the scene analysis module inputs the text data into a machine learning model to generate the scene data; and when the scene input data is voice data, the scene analysis module inputs the voice data into a natural language processing model to convert the scene input data into text data format, and inputs it into the machine learning model to generate the scene data. The step of generating the page component element data includes: determining whether the scene dimension of the scene data is greater than or equal to a dimension threshold using the scene analysis module. When the scene dimension of the scene data is less than the dimension threshold, the scene analysis module outputs input prompts; and when the scene dimension of the scene data is greater than or equal to the dimension threshold, the feature matching module performs scene category analysis based on the scene data to determine the scene category.

9. The page generation method as described in claim 11, wherein the step of generating the page component data further includes: When the scene category analysis fails to determine the scene category, the feature matching module outputs another prompt input information; And when the scene category analysis determines the scene category, the feature matching module outputs scene category recommendation information corresponding to the scene category.

10. The page generation method as described in claim 9, wherein the step of generating the page component data further includes: The feature matching module calculates the feature vector similarity between the scene feature data and the feature feature data provided by the feature feature database to determine the element data that make up the generated page.

11. The page generation method as described in claim 10, wherein the step of generating the page component data further includes: The feature matching module reads the feature database based on user selection and scene category recommendation information to obtain feature data.

12. The page generation method as described in claim 10, wherein the step of generating the page component data further includes: The feature matching module reads the feature database based on the highest similarity among the scene category recommendation information to obtain the page component element data.

13. The page generation method as described in request item 10, wherein the feature vector similarity calculation is implemented based on an improved version of cosine similarity calculation.

14. The page generation method as described in request item 8, wherein the scene information includes at least one of the user profile information, time information information, event information information, geographic information information, and terminal information information.