Demand information management method, electronic device, and computer program product

Abstract

The present disclosure provides a demand information management method, an electronic device and a computer program product. The demand information management method comprises: in response to a first function module of an application software being triggered to collect demand information, the first function module collects user demand information, and the collected user demand information is stored in a third function module and configured as at least one demand card by the third function module; in response to a second function module of the application software being triggered to execute a module-specific function, the second function module calls at least one demand card in the third function module to execute the module-specific function of the second function module; wherein the first function module and the third function module are the same function module or different function modules; and the first function module and the second function module are the same function module or different function modules.

Description

Technical Field

[0001] This disclosure relates to a demand information management method, an electronic device, a readable storage medium, and a computer program product. Background Technology

[0002] In related technologies, application software collects user demand information in real time and responds instantly based on this information to achieve the corresponding functions. However, this means the application software needs to re-collect user demand information before each function is implemented, which reduces its response efficiency. Summary of the Invention

[0003] This disclosure provides a demand information management method, an electronic device, a readable storage medium, and a computer program product.

[0004] According to one aspect of this disclosure, a demand information management method is provided, the method comprising: responding to a first functional module of application software being triggered to perform a demand information collection function, wherein the first functional module collects user demand information, the collected user demand information is stored in a third functional module and configured by the third functional module as at least one demand card; responding to a second functional module of the application software being triggered to perform a module-specific function, the second functional module invokes the at least one demand card in the third functional module to execute the module-specific function of the second functional module; wherein the first functional module and the third functional module are the same functional module or different functional modules; the first functional module and the second functional module are the same functional module or different functional modules.

[0005] According to at least one embodiment of the demand information management method of this disclosure, in response to the triggering of a demand information collection function of a first functional module of application software, the first functional module collects user demand information, including: the application software providing an entry control for the first functional module; in response to the triggering of the entry control, an electronic device on which the application software is installed provides a demand card management interface, and the first functional module collects user demand information input by the user through the demand card management interface.

[0006] According to at least one embodiment of the demand information management method of this disclosure, in response to a first functional module of application software being triggered to collect demand information, the first functional module collects user demand information, including: the first functional module collects user demand information through an automatic triggering mechanism of the application software; the automatic triggering mechanism of the application software includes an intelligent agent interaction module of the application software automatically acquiring user demand information based on the interaction content between the user and the intelligent agent.

[0007] According to at least one embodiment of the requirement information management method of this disclosure, the collected user requirement information is stored in a third functional module and configured by the third functional module as at least one requirement card, including: performing semantic parsing on the collected user requirement information to extract multiple different requirement items; performing association analysis and priority determination processing on the multiple different requirement items to determine the priority and association relationship between the different requirement items; and filling the multiple different requirement items into a requirement card template based on the priority and association relationship between the different requirement items to obtain a requirement card containing multiple structured requirement items.

[0008] According to at least one embodiment of the demand information management method of this disclosure, the step of performing correlation analysis and priority determination processing on the plurality of different demand items to determine the priority and correlation relationship between different demand items includes: identifying the inclusion relationship between different demand items, identifying the mutual exclusion relationship between different demand items, and identifying the primary and secondary order between different demand items; determining the correlation relationship based on the inclusion relationship and mutual exclusion relationship, and determining the priority based on the primary and secondary order; wherein, if the satisfaction condition of the first demand item is a sub-condition of the satisfaction condition of the second demand item, then the first demand item and the second demand item have an inclusion relationship; wherein, if the satisfaction condition of the first demand item and the satisfaction condition of the second demand item cannot be met simultaneously, then the first demand item and the second demand item have a mutual exclusion relationship; wherein, the primary and secondary order between different demand items is determined according to a preset demand decision rule or the conditional dependency relationship between demand items.

[0009] According to at least one embodiment of the requirement information management method of this disclosure, the step of filling the multiple different requirement items into a requirement card template based on the priority and correlation between the different requirement items includes: classifying, combining, and arranging the multiple different requirement items according to the priority and correlation, wherein requirement items with correlation are combined into requirement item groups, the requirement items within the requirement item groups are arranged according to the priority, and the requirement item groups and requirement items not combined into requirement item groups are arranged according to the priority; and the classified, combined, and sequentially arranged requirement item groups and / or requirement items are filled into the corresponding positions of the requirement card template.

[0010] According to at least one embodiment of the demand information management method of this disclosure, the demand card management interface displays a demand card addition control; the first functional module collects user demand information input by the user through the demand card management interface, including: in response to the demand card addition control being triggered, a new demand card configuration interface is displayed on the demand card management interface for the user to input user demand information.

[0011] According to at least one embodiment of the demand information management method of this disclosure, the demand card management interface displays existing demand cards, and the existing demand cards display demand card editing controls; the first functional module collects user demand information input by the user through the demand card management interface, including: in response to the demand card editing controls of the existing demand cards being triggered, the demand card management interface displays the demand card configuration interface of the existing demand cards for the user to edit the user demand information of the existing demand cards.

[0012] According to at least one embodiment of the demand information management method of this disclosure, after the first functional module collects user demand information through the automatic triggering mechanism of the application software, the method further includes: in response to the intelligent agent interaction module obtaining user demand information from the interaction content, displaying a new demand card configuration interface, and filling the obtained user demand information into the new demand card configuration interface for the user to edit or confirm.

[0013] According to at least one embodiment of the demand information management method of this disclosure, the second functional module calls at least one demand card in the third functional module to execute the module-specific function of the second functional module, including: the at least one demand card being called is configured as a demand module and displayed on the execution interface of the second functional module; the second functional module executes the module-specific function based on the demand module and displays the execution result on the execution interface.

[0014] According to another aspect of this disclosure, an electronic device is provided, comprising: a memory storing execution instructions; and a processor executing the execution instructions stored in the memory, causing the processor to perform a demand information management method according to any embodiment of this disclosure.

[0015] According to another aspect of this disclosure, a readable storage medium is provided, wherein executable instructions are stored therein, which, when executed by a processor, are used to implement a requirement information management method according to any embodiment of this disclosure.

[0016] According to another aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements a requirement information management method according to any embodiment of this disclosure. Attached Figure Description

[0017] The accompanying drawings illustrate exemplary embodiments of the present disclosure and, together with the description thereof, serve to explain the principles of the present disclosure. These drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this specification.

[0018] Figure 1This is a flowchart illustrating a requirement information management method according to one embodiment of this disclosure.

[0019] Figure 2 This is a schematic diagram illustrating the process of providing a demand card management interface according to one embodiment of this disclosure.

[0020] Figure 3 This is an example diagram of a display interface including an entry control, according to one embodiment of this disclosure.

[0021] Figure 4 This is an example diagram of a display interface including an entry control, according to another embodiment of this disclosure.

[0022] Figure 5 This is an example diagram of the demand card management interface when no demand card exists, according to one embodiment of this disclosure.

[0023] Figure 6 This is an example diagram of the demand card management interface when a demand card exists, according to one embodiment of this disclosure.

[0024] Figure 7 This is an example diagram of a requirement card configuration interface according to one embodiment of this disclosure.

[0025] Figure 8 This is an example diagram of the requirement card configuration interface of an existing requirement card according to one embodiment of this disclosure.

[0026] Figure 9 This is an example diagram of an implementation of the present disclosure where a new requirement card configuration interface is embedded in the interactive interface.

[0027] Figure 10 This is an example diagram of an interactive interface in which a new requirement card configuration interface is embedded in another embodiment of this disclosure.

[0028] Figure 11 This is a schematic diagram of the configuration requirements card process of one embodiment of this disclosure.

[0029] Figure 12 This is a schematic diagram illustrating the process of determining relationships and priorities in one embodiment of this disclosure.

[0030] Figure 13 This is a schematic diagram illustrating the process of filling in a requirement card template according to one embodiment of this disclosure.

[0031] Figure 14 This is an example diagram of an information confirmation interface according to one embodiment of this disclosure.

[0032] Figure 15 This is a schematic diagram illustrating the process of the proprietary function of the execution module in one embodiment of this disclosure.

[0033] Figure 16 This is a visual example of the execution result of one embodiment of this disclosure.

[0034] Figure 17 This is a visual example of the execution result of another embodiment of this disclosure.

[0035] Figure 18 This is a flowchart illustrating a demand information management method according to another embodiment of this disclosure.

[0036] Figure 19 include Figure 19 a, Figure 19 b、 Figure 19 c.

[0037] Figure 20 include Figure 20 a, Figure 20 b、 Figure 20 c.

[0038] Figure 21 include Figure 21 a, Figure 21 b、 Figure 21 c.

[0039] Figure 22 include Figure 22 a, Figure 22 b、 Figure 22 c.

[0040] Figure 23 include Figure 23 a, Figure 23 b、 Figure 23 c.

[0041] Figure 24 include Figure 24 a, Figure 24 b、 Figure 24 c.

[0042] Figure 25 include Figure 25 a, Figure 25 b、 Figure 25 c. Figure 25 d.

[0043] Figure 19 a to Figure 19 c is a schematic diagram of a user interface for yet another embodiment of this disclosure.

[0044] Figure 20 a to Figure 22 b is an interface diagram illustrating how, after the user triggers the entry control in one embodiment of this disclosure, the requirement information collection function of the first functional module is triggered, thereby entering the requirement information collection process.

[0045] Figure 22 c is a schematic diagram of the interface after triggering "My Needs" in one embodiment of this disclosure.

[0046] Figure 23 a is a schematic diagram of the interface following the triggering of the demand information viewing / modification control (i.e., the demand card editing control described above) in one embodiment of this disclosure.

[0047] Figure 23 b shows a diagram illustrating how the requirement information viewing / modification control is triggered, leading to a re-entry into the requirement information collection process.

[0048] Figure 23 c is a schematic diagram of a functional interface of an application software according to one embodiment of this disclosure.

[0049] Figure 24 a to Figure 25 a is a schematic diagram of the interface in some other embodiments of this disclosure, showing the user entering the demand information collection process after triggering the entry control.

[0050] Figure 25 b to Figure 25 d is a schematic diagram illustrating the collection of user demand information in some other embodiments of this disclosure.

[0051] Figure 26 This is a schematic block diagram of an electronic device according to one embodiment of the present disclosure. Detailed Implementation

[0052] The present disclosure will now be described in further detail with reference to the accompanying drawings and examples. It should be understood that the specific examples described herein are for illustrative purposes only and are not intended to limit the scope of the disclosure. Furthermore, it should be noted that, for ease of description, only the parts relevant to the present disclosure are shown in the accompanying drawings.

[0053] It should be noted that, where there is no conflict, the embodiments and features described in this disclosure can be combined with each other. The technical solutions of this disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0054] The process of users searching for their ideal property is continuous and dynamically adjusted, while user demand information (such as location, price, and apartment type) has a certain degree of stability. In real estate transaction applications, if user demand information is re-collected through real-time interaction before each core function is implemented—for example, requiring users to re-enter their property search requirements every time they enter the application—it will significantly reduce the application's response efficiency and increase the user's operational burden. Furthermore, in this model, user demand information is fragmented, unchangeable by the user, and difficult to reuse.

[0055] To address this, the present disclosure proposes the following technical solution: In this solution, user demand information collected by the first functional module of the application software is stored in the third functional module of the application software and configured as at least one demand card by the third functional module. The second functional module of the application software can then call the demand cards in the third functional module to execute its module-specific functions. Thus, by using demand cards, user demand information can be reused and shared, eliminating the need to re-collect user demand information before each implementation of a module-specific function, thereby improving the utilization rate of user demand information and enhancing the response efficiency of the application software. Furthermore, since user demand information is stored in the form of demand cards, it allows for a more comprehensive accumulation of user demand information, helping to reach the user's true intentions and facilitating the updating or modification of user demand information. In addition, the second functional module's ability to call the stored demand cards to execute its module-specific functions helps provide users with more accurate, matching, unified, or consistent services, while reducing the user's operational burden.

[0056] In this disclosure, electronic devices include, but are not limited to, mobile phones, tablets, laptops, personal computers, wearable devices, ATMs, etc.

[0057] Figure 1 A schematic diagram of the overall flow of a demand information management method M100 according to one embodiment of this disclosure is shown. Figure 1 The method shown includes steps S110 and S120. This method can be executed by electronic devices such as mobile phones and computers.

[0058] In step S110, in response to the first functional module of the application software being triggered to collect user demand information, the first functional module collects user demand information, which is then stored in the third functional module and configured by the third functional module as at least one demand card. The first functional module and the third functional module may be the same functional module or different functional modules.

[0059] The first functional module is a module in the application software that can collect user demand information. In addition to collecting user demand information, the functions that the first functional module can perform may include other functions. For example, when the first functional module and the third functional module are the same functional module, the first functional module can also perform functions such as storing user demand information and demand cards; when the first functional module and the second functional module are the same functional module, the first functional module can also perform functions such as calling demand cards and executing module-specific functions.

[0060] The third functional module is a module in the application software that can store user requirement information and requirement cards. The functions that the third functional module can perform include, but are not limited to, storing user requirement information and requirement cards.

[0061] In the real estate sector, user demand information may include one or more of the following: property location requirements, property price requirements, property orientation requirements, property layout requirements, and transportation requirements.

[0062] Requirement cards are data units that provide a structured expression and encapsulation of user requirement information. They make the management process of user requirement information visible and facilitate user adjustments. The third functional module can map user requirement information to requirement card templates based on preset rules, thereby generating requirement cards.

[0063] The first functional module can collect user demand information by providing input interfaces such as text input boxes or voice input controls, or it can automatically collect user demand information from the interaction process between the user and the application software.

[0064] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0065] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0066] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0067] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0068] At the same time, it is understood that the data involved in this disclosed technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0069] In step S120, in response to the second functional module of the application software being triggered with its module-specific function, the second functional module calls at least one requirement card from the third functional module to execute its module-specific function. The first functional module and the second functional module may be the same functional module or different functional modules.

[0070] The second functional module is a module within the application software that provides module-specific functions using user demand information from the demand card. The functions that the second functional module can implement include, but are not limited to, module-specific functions. Module-specific functions can be specific functions that the second functional module can perform, such as calculating the matching degree between housing options and user needs, and recommending housing options based on the matching degree.

[0071] Upon detecting a click on the module-specific function execution control or receiving a system event instructing the execution of the module-specific function, it can be determined that the second functional module has been triggered to perform its module-specific function. The second functional module can then obtain the corresponding requirement card from the third functional module via an API interface and execute its module-specific function based on the obtained requirement card.

[0072] In one example, the second functional module is different from the third functional module, meaning that the first functional module is not the same as both the second and third functional modules. For instance, if the second functional module is an agent interaction module and the third functional module is a demand management module, then when the first functional module is an agent interaction module, it is not a demand management module; and when the first functional module is a demand management module, it is not an agent interaction module.

[0073] There can be one third functional module, and multiple second functional modules, each with distinct module-specific functions. There can also be one or more first functional modules. When multiple second functional modules exist, they can share the requirement cards stored in the third functional module, thereby avoiding redundant collection of user requirement information and improving the overall execution efficiency and consistency of the module-specific functions.

[0074] It is understandable that when one of the second or third functional modules is the same as the first functional module, data flow can be simplified and communication overhead between functional modules can be reduced; when both the second and third functional modules are different from the first functional module, the independence of the functional modules can be improved and maintenance and expansion can be facilitated.

[0075] The requirement information management method of this disclosure involves storing user requirement information collected by a first functional module of the application software in a third functional module. This third functional module then configures the user requirement information as at least one requirement card. A second functional module of the application software can then invoke the requirement cards in the third functional module to execute its module-specific functions. This method reuses and shares user requirement information through requirement cards, eliminating the need to re-collect user requirement information before each module-specific function is implemented, thus improving the utilization rate of user requirement information and consequently increasing the response efficiency of the application software. Furthermore, the first functional module can be the same as or different from the third and second functional modules. That is, user requirement information can be collected through the second functional module, the third functional module, or other functional modules different from the second and third functional modules, enhancing the flexibility of user requirement information collection.

[0076] Regarding step S110, as one possible implementation, it may include, for example... Figure 2 Steps S111 and S112 are shown.

[0077] In step S111, the application software provides an entry control for the first functional module.

[0078] In step S112, in response to the entry control being triggered, the electronic device with the application software installed provides a demand card management interface, and the first functional module collects user demand information input by the user through the demand card management interface.

[0079] The demand information management method described above allows users to input their demand information through a demand card management interface provided by an electronic device with installed application software. This enables users to actively participate in the demand information collection process, thereby improving the accuracy of the collected demand information and enhancing users' sense of control over demand information management.

[0080] For example, an entry control can be one of the interactive elements used to view the requirement card management interface. The entry control can take the form of one or more of a button, link, pop-up, and label. The shape, size, and position of the entry control can be configured according to requirements. Figure 3 and Figure 4 As shown, the entry control is located in the upper right corner of the electronic device's display interface, thus meeting the user's need to quickly access the demand card management interface without obscuring other display content. The entry control can be triggered when it is clicked, long-pressed, or selected by voice.

[0081] The requirement card management interface displays and manages requirement cards. Multiple requirement cards can be arranged in a list, tiled, or other formats. Users can input their requirement information through text boxes or voice input within the requirement card management interface.

[0082] It is worth noting that, in this disclosure, various “interfaces” can be generated by an electronic device with application software installed, based on data provided by the application software, and the data provided by the application software may include one or more of the following: application software configuration data, data acquired from the network, and user input data.

[0083] Regarding step S112, as one possible implementation, the demand card management interface displays a demand card addition control. Accordingly, step S112 may include: in response to the demand card addition control being triggered, a new demand card configuration interface is displayed on the demand card management interface for the user to input user demand information.

[0084] The demand information management method described above displays a demand card addition control on the demand card management interface, and displays a demand card configuration interface for users to input user demand information when the demand card addition control is triggered. This enables flexible addition of demand cards and can meet users' needs for dynamically supplementing user demand information.

[0085] The request card addition control is an interactive element used by users to manually add new request cards. This control can take the form of one or more buttons, links, pop-ups, and labels. The shape, size, and position of the request card addition control can be configured according to requirements. The addition control can be triggered when it is clicked, long-pressed, or voice-selected.

[0086] Figure 5 The example diagram shows the demand card management interface when no demand card exists. The demand card addition control is displayed in the upper right corner and the middle area of ​​the demand card management interface, which prompts the user to manually add a new demand card.

[0087] Figure 6 An example diagram of the demand card management interface is shown when demand cards exist. In this interface, a demand card addition control is displayed in the upper right corner, thereby reducing the obstruction of existing demand cards by the addition control and improving the readability of existing demand cards.

[0088] The requirement card configuration interface serves as a platform for users to input their requirements. This interface can float above the requirement card management interface as a pop-up. A pop-up can be understood as a semi-modal window, a window type between modal and non-modal windows, characterized by blocking some operations when it pops up but allowing other windows to continue running.

[0089] The requirements card configuration interface provides text input boxes and / or voice input controls, and can prompt users to input and / or modify dimensions of their user requirements information, such as budget, location preference, and property preference. Figure 7 As shown, this allows users to easily input their own user needs information.

[0090] In this disclosure, different interfaces can be obtained by rendering corresponding templates and loading corresponding elements. Specifically, the demand card management interface can construct its overall layout by rendering a preset demand card management interface template, and then load demand card elements (such as demand card addition controls, demand card editing controls, and existing demand cards), thereby facilitating users to manage user demand information through the content displayed on the demand card management interface; the demand card configuration interface can support users to input user demand information by dynamically rendering a preset demand card configuration interface template and loading input elements (such as text input boxes and / or voice input controls).

[0091] Regarding step S112, as another possible implementation, the demand card management interface displays existing demand cards, and the existing demand cards display demand card editing controls. Accordingly, step S112 may include: in response to the demand card editing controls of existing demand cards being triggered, the demand card management interface displays the demand card configuration interface of existing demand cards for users to edit the user demand information of existing demand cards.

[0092] The demand information management method described above, by displaying a demand card editing control in the existing demand cards displayed on the demand card management interface, and displaying the demand card configuration interface of the existing demand cards when the demand card editing control is triggered, allows users to edit the existing user demand information, thereby meeting users' needs to modify the content of existing demand cards and improving the accuracy of user demand information.

[0093] Existing requirement cards are those that have already been stored. Existing requirement cards can be obtained by rendering a preset requirement card template and loading the user requirement information that has already been acquired.

[0094] The requirement card editing control is an interactive element used to add, modify, or delete content in existing requirement cards. The requirement card editing control can take the form of one or more of the following: buttons, links, pop-ups, and labels. The shape, size, and position of the requirement card editing control can be configured according to requirements. The triggering of a requirement card editing control can be determined by detecting a click, long press, or voice selection. Users can also delete entire requirement cards.

[0095] exist Figure 6In the example, the requirement card editing control is located in the lower right corner of the existing requirement card, thus providing users with a quick editing service without obscuring the content of the existing requirement card. The requirement card configuration interface of the existing requirement card displays the user requirement information corresponding to the existing requirement card, such as... Figure 8 As shown.

[0096] Regarding step S110, as another possible implementation, it may include: step S111', whereby the first functional module collects user demand information through the application software's automatic triggering mechanism. The application software's automatic triggering mechanism includes the application software's intelligent agent interaction module automatically acquiring user demand information based on the interaction content between the user and the intelligent agent.

[0097] In the above-described method for managing demand information, the intelligent agent interaction module serves as the first functional module. During the interaction between the user and the intelligent agent, it automatically obtains user demand information from the interaction content, thereby achieving passive capture of user demand information, reducing the user's manual input burden, and improving the timeliness and comprehensiveness of user demand information collection.

[0098] The automatic triggering mechanism is a mechanism for the intelligent agent interaction module to automatically initiate the collection of user demand information based on the interaction events between the user and the intelligent agent.

[0099] An intelligent agent can be understood as an artificial intelligence model, and its structure can adopt the structure of various existing neural network models, such as deep learning-based neural network models, shallow neural network models, large language models, etc., all of which fall within the protection scope of this disclosure.

[0100] The intelligent agent can be deployed in the cloud, while the intelligent agent interaction module can be a module deployed on the application software side. The intelligent agent interaction module can be used as a bridge for interaction between the user and the intelligent agent.

[0101] In some embodiments of this disclosure, after step S111', the following steps may be included: step S112', in response to the intelligent agent interaction module obtaining user demand information from the interaction content, displaying a new demand card configuration interface, and filling the obtained user demand information into the new demand card configuration interface for the user to edit or confirm.

[0102] The demand information management method described above automatically fills the demand card configuration interface with the acquired user demand information by the intelligent agent interaction module for user editing or confirmation. This achieves a combination of automatic collection of user demand information and user verification, thereby improving the reliability of user demand information and user participation, and solving the problem of inaccurate identification of user demand information.

[0103] When the intelligent agent interaction module obtains user demand information from the interaction content, a new demand card configuration interface can be displayed in an embedded form in a certain area of ​​the user-intelligent agent interaction interface (e.g., Figure 9 and Figure 10 As shown in the figure, or a new requirement card configuration interface can be displayed as a floating layer on the interactive interface, so as to ensure that users can understand the collected user requirement information in real time during the interaction.

[0104] The newly displayed requirement card configuration interface dynamically renders a preset requirement card configuration interface template and loads multiple elements, including user requirement information, user requirement information editing controls, user requirement information addition controls, and user requirement information confirmation controls. This facilitates user management of automatically collected user requirement information. The user requirement information in the newly displayed requirement card configuration interface can be in the form of requirement cards, or in the form of structured or unstructured text.

[0105] In some embodiments of this disclosure, the step S110, "the collected user demand information is stored in the third functional module and configured by the third functional module as at least one demand card," can be achieved through methods such as... Figure 11 Steps S130 to S150 shown are implemented.

[0106] In step S130, semantic parsing is performed on the collected user demand information to extract multiple different demand items.

[0107] In step S140, correlation analysis and priority determination are performed on multiple different requirement items to determine the priority and correlation between different requirement items.

[0108] In step S150, based on the priority and relationship between different requirement items, multiple different requirement items are filled into the requirement card template to obtain a requirement card containing multiple structured requirement items.

[0109] The above-described requirement information management method parses different requirement items in user requirement information and accurately fills them into the requirement card template based on the priority and correlation between them. As a result, the requirement items in the requirement card are of standard terminology and the structure between different requirement items is clear, which facilitates the second functional module to accurately understand the information in the requirement card and improves the efficiency and accuracy of the second functional module in implementing its proprietary functions.

[0110] For example, semantic parsing of the collected user demand information can be performed based on natural language understanding algorithms or artificial intelligence models to extract multiple different demand items.

[0111] A single requirement can be a specific user need within a specific dimension, such as a budget of less than 5 million, a preference for the city center, a preference for secondhand homes, or a preference for fully furnished homes. Multiple different requirement items can have different specific dimensions and / or different specific user needs.

[0112] Different requirement items may or may not be related (e.g., belonging to the same dimension). Correlation analysis helps to integrate related requirement items, thereby improving the readability of requirement cards. Correlation analysis can be achieved through rule engines or artificial intelligence models.

[0113] Prioritization can be achieved through weight calculation or user feedback sorting. Prioritization determines the order of requirements within the requirement card, thereby improving readability.

[0114] The requirement card template can be configured according to requirements and is not limited here. Multiple requirement items can be organized in key-value pairs or lists in the requirement card to form structured information that is easy to read and understand.

[0115] Regarding step S140, in one embodiment of this disclosure, it may include, as follows: Figure 12 Steps S141 and S142 are shown.

[0116] In step S141, the inclusion relationship between different requirements is identified, the mutual exclusion relationship between different requirements is identified, and the primary and secondary order between different requirements is identified.

[0117] In step S142, the association relationship is determined based on the inclusion relationship and the mutual exclusion relationship, and the priority is determined based on the primary and secondary order.

[0118] If the condition for satisfying the first requirement is a subcondition of the condition for satisfying the second requirement, then there is an inclusion relationship between the first requirement and the second requirement.

[0119] If the conditions for satisfying the first requirement and the conditions for satisfying the second requirement cannot be met simultaneously, then there is a mutual exclusion relationship between the first requirement and the second requirement.

[0120] In this process, the order of importance among different demand items is determined based on the preset demand decision rules or the conditional dependencies between demand items.

[0121] The demand information management method described above determines the relationship between different demand items based on the inclusion and mutual exclusion relationships between them, and determines the priority between different demand items based on their primary and secondary order. This enables accurate analysis of the relationship and priority between different demand items, thereby providing reliable data support for the generation of demand cards and improving the logic of demand information management.

[0122] For example, semantic recognition algorithms can be used to identify whether there is an inclusion relationship or a mutual exclusion relationship between different requirement items, and requirement items with inclusion and / or mutual exclusion relationships can be identified as requirement items with an association relationship. For instance, if requirement item A and requirement item B have an inclusion relationship, and requirement item A and requirement item C have a mutual exclusion relationship, then it can be determined that there is an association relationship between requirement items A, B, and C.

[0123] Pre-defined demand decision rules can be stored in the application software's rule base. This rule base may include a predefined priority mapping table based on domain knowledge (such as real estate user demand management). For example, demand items in the "budget" dimension can be set as primary demand items, and demand items in the "location" dimension as secondary demand items, because in the home purchase decision-making process, budget may be considered as a hard constraint and given priority, while location may be considered as a secondary selection factor. By traversing the extracted demand items and querying the priority mapping in the rule base, the demand items are assigned to the corresponding levels, thereby determining the primary and secondary order, and using this primary and secondary order as the priority order. For example, primary demand items have the highest priority, and secondary demand items have the lowest priority.

[0124] The conditional dependencies between demand items can be represented as a dependency graph, where each demand item is a node. If one demand item depends on another, a directed edge is added to the graph. For example, a demand item in the "apartment type" dimension might depend on a demand item in the "number of family members" dimension; therefore, the node corresponding to the demand item in the "apartment type" dimension and the node corresponding to the demand item in the "number of family members" dimension are connected by a directed edge. The dependency graph is processed using a topological sorting algorithm. The in-degree of each demand item is calculated, and demand items with an in-degree of 0 are identified as primary demand items (i.e., no dependencies), while those with higher in-degrees are identified as secondary demand items, thus establishing a primary-secondary order. This primary-secondary order serves as the priority order; for example, primary demand items have the highest priority, and secondary demand items have the lowest priority.

[0125] In addition, the reverse order of primary and secondary can also be used as the priority order, which is not limited here.

[0126] Regarding step S150, in one embodiment of this disclosure, it may include, as follows: Figure 13 Steps S151 and S152 are shown.

[0127] In step S151, multiple different requirement items are classified, combined, and arranged in order according to priority and relationship. Requirement items with relationship are combined into requirement item groups, and the requirement items within the requirement item groups are arranged according to priority. Requirement item groups and requirement items not combined into requirement item groups are also arranged based on priority.

[0128] In step S152, the classified and ordered requirement groups and / or requirement items are filled into the corresponding positions of the requirement card template.

[0129] The demand information management method described above accurately groups multiple different demand items based on association relationships and positions different demand items within the demand item group based on priority, thereby achieving orderly grouping and positioning of different demand items, optimizing the presentation of information in the demand card, improving the readability of the demand card, and increasing the efficiency of the second functional module in implementing the module's proprietary functions.

[0130] Multiple requirement items grouped into the same requirement item group belong to the same category of requirement items; for example, they all correspond to the same dimension. Different requirement item groups correspond to different categories. Multiple requirement items not grouped into requirement item groups are different categories of requirement items, and these requirement items are also not of the same category as the requirement items in the requirement item group.

[0131] A requirement card template may contain only one type of requirement group or requirement item, or multiple types of requirement group and / or requirement items; there is no limitation on this.

[0132] In some implementations, after step S151, the method further includes: an electronic device with application software installed providing an information confirmation interface; displaying categorized and sequentially arranged groups and / or items of requirements on the information confirmation interface, and providing checkboxes and confirmation controls for each group and / or item of requirements, such as... Figure 14 As shown. Step S152 may then include, in response to the triggering of the check confirmation control, filling the corresponding positions in the requirement card template with the category combinations and sequentially arranged requirement item groups and / or requirement items corresponding to the triggered check controls. This allows the user to verify relevant information before generating the requirement card, thus ensuring the accuracy of the generated requirement card. Category combinations and sequentially arranged requirement item groups and / or requirement items corresponding to untriggered check controls are not filled with the corresponding positions in the requirement card template. The triggering of a check control can be determined upon detecting actions such as clicking, long-pressing, or voice selection of the check control. The same applies to check confirmation controls.

[0133] The information confirmation interface also provides user requirement information editing controls, allowing users to re-edit their user requirement information when triggered. Additionally, it can detect whether the user has adjusted the order of requirement item groups and / or requirement items. If such adjustment is detected, the adjusted requirement item groups and / or requirement items can be filled into the corresponding positions in the requirement card template, ensuring that the generated requirement card meets the user's needs.

[0134] Regarding step S120, in one embodiment of this disclosure, it may include, as follows: Figure 15 Steps S121 and S122 are shown.

[0135] In step S121, at least one of the invoked requirement cards is configured as a requirement module and displayed on the execution interface of the second functional module.

[0136] In step S122, the second functional module executes the module-specific function based on the requirement module and displays the execution result on the execution interface.

[0137] The demand information management method described above improves the transparency of function execution by displaying the demand modules configured with demand cards and the function execution results based on the demand cards together in the execution interface of the second function module. This allows users to directly compare the differences between the function execution results and their needs through the content displayed on the execution interface.

[0138] A requirement module can be a collection of multiple requirement cards, such as a list or panel. Requirement modules can be rendered using UI components. The position of a requirement module in the execution interface can be configured according to requirements; for example, it can be configured to be at the top of the execution interface, making it convenient for users to observe the specific content of the requirement module first.

[0139] The position of the execution result in the execution interface can be configured according to requirements.

[0140] In one example, the module's proprietary function is to recommend highly matched properties to the user, and the execution result may include information on the most matched properties (such as...). Figure 16 (as shown) and / or match analysis report (such as) Figure 17 (As shown). The requirement module can be... Figure 17 The blue pentagonal pattern in the middle.

[0141] Please combine Figure 18 In one example, the demand information management method may include the following steps S201 to S217. The content related to steps S201 to S217 can be referred to the description of the above implementation method. For the sake of brevity, it will not be repeated here.

[0142] In step S201, the application software provides an entry control for the first functional module.

[0143] In step S202, it is determined whether the entry control is triggered. If so, proceed to step S203; otherwise, proceed to step S214.

[0144] In step S203, the electronic device with the application software installed provides a demand card management interface, which displays the newly added demand card control.

[0145] In step S204, it is determined whether there is an existing demand card. If so, proceed to step S205; otherwise, proceed to step S206.

[0146] In step S205, the demand card management interface displays existing demand cards, and the demand card editing control is displayed on the existing demand cards.

[0147] In step S206, it is determined whether the requirement card editing control of the existing requirement card has been triggered. If so, proceed to step S207; otherwise, proceed to step S209.

[0148] In step S207, the demand card management interface displays the demand card configuration interface for existing demand cards, allowing users to edit the user demand information of existing demand cards.

[0149] In step S208, the user-edited requirement card is displayed in the requirement card management interface.

[0150] In step S209, it is determined whether the new control of the demand card has been triggered. If so, proceed to step S210; otherwise, proceed to step S203.

[0151] In step S210, a new demand card configuration interface is displayed on the demand card management interface for users to input user demand information.

[0152] In step S211, the obtained user demand information is semantically parsed to extract multiple different demand items.

[0153] In step S212, correlation analysis and priority determination are performed on multiple different requirement items to determine the priority and correlation between different requirement items.

[0154] In step S213, based on the priority and relationship between different requirement items, multiple different requirement items are filled into the requirement card template to obtain a requirement card containing multiple structured requirement items, and the obtained requirement card is displayed in the requirement card management interface.

[0155] In step S214, it is determined whether the user is interacting with the intelligent agent. If yes, proceed to step S215; otherwise, proceed to step S217.

[0156] In step S215, a new requirement card configuration interface is displayed, and user requirement information obtained from the interaction between the user and the intelligent agent is filled into the new requirement card configuration interface for the user to edit or confirm. Specifically, after generating a requirement card based on the user requirement information obtained from the interaction between the user and the intelligent agent, the requirement card is displayed in the new requirement card configuration interface. The process of generating the requirement card based on the user requirement information obtained from the interaction between the user and the intelligent agent can be the same as steps S211 to S213.

[0157] In step S216, the user-edited or confirmed requirement card is displayed in the requirement card management interface.

[0158] In step S217, in response to the second functional module of the application software being triggered with a module-specific function, the second functional module calls at least one requirement card in the third functional module to execute the module-specific function of the second functional module.

[0159] Figure 19 a to Figure 19 c is a schematic diagram of a user interface for yet another embodiment of this disclosure.

[0160] refer to Figure 19 a to Figure 19 c shows the user's status after logging into the application software. The application software provides an entry control for the first functional module. Users can trigger the entry control to view the stored requirement cards in the third functional module, or trigger the requirement information collection function of the first functional module.

[0161] Figure 19 a and Figure 19 b shows a schematic diagram of the entry control under different implementations when the logged-in user has not yet filled in the required information. Figure 19 c is a schematic diagram of the entry control when the logged-in user has filled in the required information.

[0162] refer to Figure 19 a to Figure 19 c. The entry control can be in the form of a card, which may include one or more sub-controls. Different sub-controls are configured to trigger different functions. For example, triggering the "My Home Purchase Plan" (or "Fill in My Needs") sub-control can allow users to view filled-in requirement cards or trigger the requirement information collection function to fill in requirement cards.

[0163] Figure 20 a to Figure 22 b is an interface diagram illustrating how, after the user triggers the entry control in one embodiment of this disclosure, the requirement information collection function of the first functional module is triggered, thereby entering the requirement information collection process.

[0164] refer to Figure 20 a. Users can trigger the requirement information collection function of the first functional module by triggering the "Fill in my requirements" collection trigger control, so as to enter the requirement information collection process.

[0165] refer to Figure 20 b to Figure 22 b. User needs information can be collected through one or more of the following dimensions: purpose of purchasing a house, budget, room preference, family structure, intended area, essential needs, preferred schools, and other requirements. These dimensions are exemplified below. (Reference) Figure 22 b, that is, the last interface of the demand information collection process is configured with a collection completion control (such as "Generate my home purchase plan" or "Complete" control).

[0166] This can be achieved by providing users with input elements such as selection controls, input boxes, and drag bars to collect user demand information. This collection process corresponds to the first functional module collecting user demand information. The collected user demand information is then sent to the third functional module, which configures it into at least one demand card based on a preset demand card template.

[0167] refer to Figure 19 c. Users can view or modify requirement information by triggering the "My Requirements" sub-control, that is, view or modify the corresponding stored requirement card.

[0168] Figure 22 c is a schematic diagram of the interface after triggering "My Needs" in one embodiment of this disclosure.

[0169] Figure 23 a is a schematic diagram of the interface following the triggering of the demand information viewing / modification control (i.e., the demand card editing control described above) in one embodiment of this disclosure.

[0170] Figure 23 b shows a diagram illustrating how the requirement information viewing / modification control is triggered, leading to a re-entry into the requirement information collection process.

[0171] refer to Figure 22 c. User requirements can be displayed on the interface in the form of graphical requirement cards (i.e., rendered images). Users can access the requirement viewing / modification interface by manipulating the requirement information viewing / modification controls (e.g., "Housing Requirements") (i.e., requirement card editing controls). (See reference...) Figure 23 Users can view or modify the multi-dimensional requirements they have filled in. Technically, this process can be implemented by the second or first functional module reading and calling the stored requirement cards in the third functional module for display and editing.

[0172] In other embodiments of this disclosure, reference is made to Figure 22 c. Provide at least two types of requirement information viewing / modification controls (i.e., requirement card editing controls), and one requirement information viewing / modification control (e.g., Figure 22 When the "Housing Demands" control in the upper right corner is triggered, it displays the user's multi-dimensional demand information through text content, such as... Figure 23 As shown in a.

[0173] Another type of requirement is information viewing / modification controls (e.g.) Figure 22 After the "Not accurate enough, modify my requirements" control in C is triggered, it re-enters... Figure 20 b to Figure 22 The process for collecting demand information (b) can optionally be re-entered. Figure 20 b to Figure 22 After the demand information collection process for b, it is possible to... Figure 22 Based on the interface of c, the requirement card configuration interface is displayed in the form of a floating layer or a pop-up layer to execute the requirement information collection process. (See reference...) Figure 23 b. The floating or pop-up-style requirement card configuration interface can provide selection controls, input boxes, and drag bars.

[0174] In some other embodiments of this disclosure, user demand information is collected without the user logging into the application software of this disclosure.

[0175] Figure 23 c is a schematic diagram of a functional interface of an application software according to one embodiment of the present disclosure. It can be the homepage interface of the application software or an interface switched from the homepage.

[0176] In this embodiment, the entry control can be in the form of an operable floating layer or an operable pop-up layer, and this disclosure does not impose any particular limitation.

[0177] refer to Figure 23 c. In response to the user's triggering operation on the entry control (such as clicking, swiping up, etc.), the application software disclosed herein triggers the requirement information collection function of the first functional module, thereby triggering the requirement information collection process.

[0178] Figure 24 a to Figure 25 a is a schematic diagram of the interface in some other embodiments of this disclosure, showing the user entering the demand information collection process after triggering the entry control.

[0179] refer to Figure 24 a to Figure 25a) User needs information can be collected through one or more of the following dimensions: purpose of purchasing a house, budget, room preference, family structure, intended area, essential needs, preferred school, and other requirements. Details will not be elaborated further. In this offline state, the collected user needs information can be temporarily stored locally on the electronic device and can be synchronized to the third functional module after the user logs in to be configured as a needs card.

[0180] Figure 25 b to Figure 25 d is a schematic diagram illustrating the collection of user demand information in some other embodiments of this disclosure.

[0181] refer to Figure 25 b to Figure 25 d. User needs information can be collected through dialogue, i.e., information flow. Technically, this dialogue-based data collection process corresponds to the application software intelligent agent interaction module in the first functional module, which automatically acquires user needs information based on the interaction content between the user and the intelligent agent.

[0182] For example in Figure 23 Based on C, in response to user actions triggered by the entry control, it can display... Figure 25 The interface shown in b allows an intelligent agent (such as a "personal butler") to conduct dialogues with the user and collect the user's needs information through dialogue. The user's needs information can be collected through one or more of the following dimensions: purpose of purchasing a house, budget for purchasing a house, room preference, family structure, intended area, essential needs to be met, preferred school, and other requirements. Details will not be elaborated further.

[0183] based on Figure 19 a to Figure 25 In addition to the various embodiments shown in d, this disclosure also provides the following methods for managing demand information.

[0184] Based on the above-mentioned related implementation methods, the requirement information management method of this implementation method, wherein the entry control is in the form of a card, the card form includes at least one sub-control, and different sub-controls are configured to trigger different functions; In response to the triggering of the sub-control, the first functional module can view the demand cards stored in the third functional module or trigger the demand information collection function.

[0185] Based on the aforementioned related embodiments, the demand information management method of this embodiment, after the first functional module collects user demand information via the demand card management interface, further includes: The collected user demand information is displayed on the interface in the form of a graphical demand card.

[0186] Based on the above-mentioned related implementation methods, the demand information management method of this implementation method displays at least two types of demand card editing controls on the demand card management interface; Once the first type of requirement card editing control is triggered, the multi-dimensional requirement information in the stored requirement card will be displayed through text content; After the second type of requirement card editing control is triggered, the requirement information collection process is entered again, and the requirement card configuration interface is displayed in the form of a floating layer or pop-up layer on the current interface to perform requirement information collection.

[0187] Based on the aforementioned related implementation methods, the demand information management method of this implementation method, in response to the first functional module of the application software being triggered to collect demand information, the first functional module collects user demand information, including: When the user is not logged into the application software, in response to the triggering of the entry control, the first functional module enters the demand information collection process through the operable floating layer or operable pop-up layer to collect user demand information. The collected user demand information is temporarily stored locally on the electronic device and synchronized to the third functional module after the user logs in, where it is configured as at least one demand card.

[0188] Based on the aforementioned related implementation methods, the demand information management method of this implementation method, wherein the first functional module collects user demand information through the automatic triggering mechanism of the application software, includes: The intelligent agent interaction module in the first functional module interacts with the user in an information flow dialogue manner and automatically obtains user demand information based on the interaction content; The interaction is executed by an intelligent agent, and the data collection process includes collecting data from at least one of the following dimensions: purpose of purchasing a house, budget for purchasing a house, room preference, family structure, intended area, essential needs to be met, preferred school, and other requirements. It should be noted that the text content, control shapes, interface colors, and even the rendered cartoon characters shown in the accompanying drawings are exemplary and intended to explain the technical solutions of the various embodiments of this disclosure. They should not be construed as limitations on the technical solutions of the various embodiments of this disclosure.

[0189] The subject executing the demand information management method in the specific embodiments of this disclosure can be an electronic device such as a mobile phone or computer.

[0190] Therefore, based on any of the above embodiments, this disclosure also provides an electronic device that can execute the demand information management method of any of the embodiments described above.

[0191] Figure 26This is a schematic block diagram of an electronic device 1000 according to one embodiment of the present disclosure.

[0192] The hardware structure of the electronic device 1000 can be implemented using a bus architecture. The bus architecture can include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the hardware. Bus 1100 connects various circuits, including one or more processors 1200, memory 1300, screens 1500, and / or hardware modules. Bus 1100 can also connect various other circuits 1400, such as peripheral devices, voltage regulators, power management circuits, external antennas, etc.

[0193] Bus 1100 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, this diagram uses only one connection line, but this does not imply that there is only one bus or one type of bus.

[0194] This disclosure also provides a readable storage medium storing a computer program that, when executed by a processor, is used to implement the methods described above. A "readable storage medium" can be any means capable of containing, storing, communicating, propagating, or transmitting a program for use by or in conjunction with an instruction execution system, apparatus, or device. More specific examples of a readable storage medium include: an electrical connection with one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and portable read-only memory (CDROM), etc.

[0195] This disclosure also provides a computer program product, the methods of which can be implemented wholly or partially through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented wholly or partially as a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed, all or part of the processes or functions of this disclosure are performed.

[0196] Computer programs or instructions can be stored in a readable storage medium or transferred from one readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The readable storage medium can be any available medium capable of access, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video optical disc; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or it can include both volatile and non-volatile types of storage media.

[0197] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, apparatus, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0198] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0199] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0200] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0201] In the description of this specification, the references to terms such as "one embodiment / mode," "some embodiments / modes," "example," "specific example," or "some examples," etc., refer to specific features, structures, or characteristics described in connection with that embodiment / mode or example, which are included in at least one embodiment / mode or example of this disclosure. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment / mode or example. Moreover, the specific features, structures, or characteristics described may be combined in any suitable manner in one or more embodiments / modes or examples. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments / modes or examples described in this specification, as well as the features of different embodiments / modes or examples.

[0202] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this disclosure, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0203] Those skilled in the art should understand that the above embodiments are merely for illustrating the present disclosure and are not intended to limit the scope of the disclosure. Those skilled in the art can make other changes or modifications based on the above disclosure, and these changes or modifications still fall within the scope of the present disclosure.

Claims

1. A method for managing demand information, characterized in that, include: In response to the first functional module of the application software being triggered to collect demand information, the first functional module collects user demand information, and the collected user demand information is stored in the third functional module and configured by the third functional module as at least one demand card. In response to the second functional module of the application software being triggered with a module-specific function, the second functional module calls at least one demand card in the third functional module to execute the module-specific function of the second functional module. Wherein, the first functional module and the third functional module are the same functional module or different functional modules; The first functional module and the second functional module may be the same functional module or different functional modules.

2. The demand information management method according to claim 1, characterized in that, In response to the first functional module of the application software being triggered to collect user demand information, the first functional module collects user demand information, including: The application software provides an entry control for the first functional module; In response to the triggering of the entry control, the electronic device with the application software installed provides a demand card management interface, through which the first functional module collects user demand information input by the user.

3. The demand information management method according to claim 1, characterized in that, In response to the first functional module of the application software being triggered to collect user demand information, the first functional module collects user demand information, including: The first functional module collects user demand information through the automatic triggering mechanism of the application software; The automatic triggering mechanism of the application software includes the application software's intelligent agent interaction module automatically obtaining user demand information based on the interaction content between the user and the intelligent agent.

4. The demand information management method according to claim 1, characterized in that, The collected user demand information is stored in a third functional module and configured by the third functional module as at least one demand card, including: Semantic analysis is performed on the collected user demand information to extract multiple different demand items; Perform correlation analysis and priority determination on the multiple different requirement items to determine the priority and correlation relationship between the different requirement items; Based on the priority and relationship between the different requirement items, the multiple different requirement items are filled into the requirement card template to obtain a requirement card containing multiple structured requirement items.

5. The demand information management method according to claim 4, characterized in that, The process of performing correlation analysis and priority determination on the multiple different requirement items, and determining the priority and correlation relationships between the different requirement items, includes: Identify the inclusion relationship between different requirements, the mutual exclusion relationship between different requirements, and the primary and secondary order between different requirements; The association relationship is determined based on the inclusion relationship and the mutual exclusion relationship, and the priority is determined based on the primary and secondary order; If the condition for satisfying the first requirement item is a subcondition of the condition for satisfying the second requirement item, then there is an inclusion relationship between the first requirement item and the second requirement item. If the conditions for satisfying the first requirement and the conditions for satisfying the second requirement cannot be met simultaneously, then there is a mutual exclusion relationship between the first requirement and the second requirement. In this process, the order of importance among different demand items is determined based on the preset demand decision rules or the conditional dependencies between demand items.

6. The demand information management method according to claim 4, characterized in that, The process of filling the multiple different requirement items into the requirement card template based on the priority and correlation between the different requirement items includes: The multiple different requirement items are classified, combined, and arranged in order according to their priority and relationship. Requirement items with a relationship are combined into requirement item groups. Requirement items within the requirement item groups are arranged according to their priority. Requirement item groups and requirement items not combined into requirement item groups are also arranged based on their priority. Fill the corresponding positions in the requirement card template with the categorized and ordered requirement groups and / or requirement items.

7. The demand information management method according to claim 2, characterized in that, The demand card management interface displays newly added control for demand cards; The first functional module collects user demand information input by the user through the demand card management interface, including: In response to the triggering of the new control for the demand card, a new demand card configuration interface is displayed on the demand card management interface for the user to input user demand information.

8. The demand information management method according to claim 7, characterized in that, The demand card management interface displays existing demand cards, and the existing demand cards display demand card editing controls. The first functional module collects user demand information input by the user through the demand card management interface, including: In response to the triggering of the demand card editing control of the existing demand card, the demand card management interface displays the demand card configuration interface of the existing demand card, allowing the user to edit the user demand information of the existing demand card.

9. An electronic device, characterized in that, include: The memory stores execution instructions; as well as A processor that executes execution instructions stored in the memory, causing the processor to perform the method of any one of claims 1 to 8.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 8.

Images