Service ecosystem abstraction and implicit demand analysis method for multi-entity complex scenarios

Through service entity and relationship modeling, log analysis and large model capabilities, combined with rough-fuzzy decision-making, the problem of insufficient identification of implicit demands in the service ecosystem of multi-entity complex scenarios in the existing technology is solved, and more accurate and efficient Requirement identification and optimization suggestions.

CN118674239BActive Publication Date: 2024-11-26ZHEJIANG UNIV +1
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202411155492.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-22
Publication Date
2024-11-26
Estimated Expiration
2044-08-22

AI Technical Summary

Technical Problem

The existing technology is difficult to effectively respond to the hidden needs of complex interactions and dynamic changes between multiple entities, and lacks a mechanism for in-depth analysis and optimization suggestions for service ecosystems.

Method used

Through service entity and relationship modeling, service capabilities and process modeling, log analysis and performance monitoring, combined with large model capabilities, hidden requirements are mined, and rough-fuzzy decisions are used to determine the best requirements.

Benefits of technology

It significantly improves the accuracy and efficiency of identifying implicit needs in complex service ecosystems, provides a scientific basis for service optimization, and fully considers the complexity and dynamics of multiple entities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118674239B_ABST
    Figure CN118674239B_ABST
Patent Text Reader

Abstract

The present invention discloses a service ecology abstraction and implicit demand analysis method for multi-entity complex scenarios, including the following steps: step 1, service entity and relationship modeling, then service capability and process modeling, and service ecology abstract modeling; step 2, based on the service ecology model, service log analysis and performance monitoring report, evaluate the current service status, and then use the large model capability to take the current service status index as input to mine the current service implicit demand; step 3, based on rough-fuzzy comprehensive decision-making, determine the best implicit demand. The service ecology abstraction and implicit demand analysis method for multi-entity complex scenarios of the present invention can effectively mine the best implicit demand.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to an implicit demand analysis method, and more specifically to a service ecosystem abstraction and implicit demand analysis method for multi-entity complex scenarios. Background Art

[0002] In the prior art, the modeling of service ecosystems mainly relies on single-dimensional analysis methods, such as UML-based service modeling or simple business process mapping. These methods are difficult to effectively deal with the complex interactions between multiple entities and dynamically changing implicit needs. Although the service modeling framework proposed in the prior art can describe basic service entities and relationships, it is unable to cope with large-scale, multi-dimensional, and dynamically changing service scenarios, especially the lack of effective mechanisms for the identification and analysis of implicit needs. Therefore, the analysis methods of service ecosystems in the prior art have the following disadvantages:

[0003] 1. Failure to fully consider the multi-entity complexity and dynamic nature of the service ecosystem.

[0004] 2. There is a lack of effective means to deeply explore and accurately identify hidden needs in the service ecosystem.

[0005] 3. The model building and demand analysis processes are separated, resulting in a poor match between optimization suggestions and actual business processes. Summary of the invention

[0006] In view of the shortcomings of the prior art, the purpose of the present invention is to provide a service ecosystem abstraction and implicit demand analysis method for multi-entity complex scenarios that can avoid the above-mentioned shortcomings.

[0007] To achieve the above purpose, the present invention provides the following technical solution: a service ecosystem abstraction and implicit demand analysis method for multi-entity complex scenarios, characterized in that it includes the following steps:

[0008] Step 1: Model service entities and relationships, then model service capabilities and processes to complete the abstract modeling of the service ecosystem.

[0009] Step 2: Evaluate the current service status based on the service ecosystem model, service log analysis, and performance monitoring reports. Then, with the help of the big model capability, use the current service status indicators as input to explore the hidden needs of the current service.

[0010] Step three: Determine the optimal implicit demand based on rough-fuzzy comprehensive decision-making.

[0011] As a further improvement of the present invention, the specific steps of performing service entity and relationship modeling in step 1 are as follows:

[0012] Step 1, based on the multi-agent modeling method, define and describe the types and attributes of each entity in the service ecosystem, including participant entity, service entity, data entity, resource entity to complete entity abstraction;

[0013] Steps one and two: Model and describe entity relationships through the entity-relationship ER model and domain-driven design methods. The entity relationships include mutual exclusion, dependency, call, and cooperation, thereby completing the modeling of service entities and relationships.

[0014] As a further improvement of the present invention, the specific steps of performing service capability and process modeling in step 1 are as follows:

[0015] Step 13: Model and describe each business process in the service ecosystem through the business process execution language BPEL and the eTOM business process framework method. Each business process includes the input, output, process control and execution details of the business process;

[0016] Step 14: Based on the SID service design specification method, clarify the roles, responsibilities, functions, interfaces and dependencies of each entity in the service ecosystem;

[0017] Step 15: Combine the Petri net model to model and describe the relationships between business processes and entities in the service ecosystem. The relationships between business processes and entities include process control and data transmission, thereby completing service capability and process modeling.

[0018] As a further improvement of the present invention, the specific steps of evaluating the current service status based on the service ecological model, service log analysis and performance monitoring report in step 2 are as follows:

[0019] Step 21: Inspect the performance indicators such as service response time and success rate, analyze resource utilization, allocation efficiency and redundancy to conduct entity status assessment;

[0020] Step 22: Use network analysis and social network analysis to evaluate the collaboration efficiency between entities, the rationality of dependencies, and potential bottlenecks or conflict points. Specifically, use tools such as BPEL process instance monitoring logs and Petri net simulation to identify delays, bottlenecks, and abnormal paths in the process, and quantify process efficiency and flexibility.

[0021] As a further improvement of the present invention, the specific steps of mining the hidden demand of the current service in step 2 are as follows:

[0022] Step 23: Set up a service knowledge base, which contains service status indicator benchmarks, service ecology and other related service information;

[0023] Step 24: Set the prompt words for mining the standardized large model requirements;

[0024] Step 25, combining the current service status information and prompt words as model input;

[0025] Step 26: Output specific implicit needs through the service ecosystem model.

[0026] As a further improvement of the present invention, the specific steps of determining the optimal implicit demand in step 3 are as follows:

[0027] Step 31: Use the big model as a demand analysis expert to score the invisible demand for services from the perspectives of economic value, timeliness value, reliability value, flexibility value, social value, trustworthiness value, and tangible value;

[0028] Step 3.2: Define the implicit demand set as ,in, is the demand quantity; the evaluation index set is Corresponding to the above 7 key values, for each requirement and indicators , each has an evaluation score given by a large model ;

[0029] Step 33: Calculate the total support of the indicator: The support of measures its ability to distinguish different demand instances. After that, the different demand instances become indistinguishable, indicating The support degree of is high, so the total support degree calculation formula of this indicator is:

[0030]

[0031] in, It is removing the indicator The subsequent demand set;

[0032] Step 3 and 4, calculate the support of each indicator, and then identify the minimum reduction set, that is, the set that retains the least number of indicators while keeping the decision table's distinguishing ability unchanged;

[0033] Step 35, repeat steps 33 and 34 until further removal results in information loss;

[0034] Step 36: For the final retained Key value indicators, for each indicator , construct a fuzzy set , its As a membership function, it represents the demand In the indicator The degree of membership on , its comprehensive evaluation value for:

[0035]

[0036]

[0037] in, is the weight of the corresponding indicator;

[0038] Step 37: Select the demand with a comprehensive evaluation value greater than a given threshold as the final service implicit demand.

[0039] The beneficial effect of the present invention is that, through the settings of steps one to three, it is possible to effectively model the service ecosystem abstraction, then use the current service status indicators as input, explore the current service implicit needs, and finally determine the optimal implicit needs. Compared with the methods in the prior art, the present invention fully considers the multi-entity complexity and dynamics of the service ecosystem through comprehensive modeling, intelligent analysis and decision optimization, significantly improves the accuracy and efficiency of implicit demand identification in a complex service ecosystem, provides a scientific basis for service optimization, and effectively solves the shortcomings of the prior art in complexity and dynamic analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 It is a flow chart of the service ecology abstraction and implicit demand analysis method for multi-entity complex scenarios of the present invention;

[0041] Figure 2 Schematic diagram of the process for abstract modeling of service ecology. DETAILED DESCRIPTION

[0042] The present invention will be further described below in conjunction with the embodiments given in the accompanying drawings. The terms used in this embodiment are interpreted as follows:

[0043] Multi-Agent: A computational model that simulates the interaction of multiple intelligent agents.

[0044] ER model: Entity-relationship model, used for conceptual modeling of database design.

[0045] BPEL: Business Process Execution Language, used to define executable business processes.

[0046] eTOM: Enhanced Telecom Operations Map is a business process framework proposed by the Telecom Management Forum.

[0047] Reference Figures 1 to 2 As shown, a service ecosystem abstraction and implicit demand analysis method for multi-entity complex scenarios in this embodiment specifically includes the following steps:

[0048] 1. Abstract modeling of service ecology.

[0049] 1.1 Service entity and relationship modeling.

[0050] 1.1.1 Entity abstraction: Based on the multi-agent modeling method, the types and attributes of various entities in the service ecosystem are defined and described, including participant entities, service entities, data entities, resource entities, etc.

[0051] 1.1.2 Relationship abstraction: Model and describe entity relationships through the entity-relationship ER model and domain-driven design methods, including mutual exclusion, dependency, call, cooperation, etc.

[0052] 1.2 Service Capabilities and Process Modeling

[0053] 1.2.1 Model and describe each business process in the service ecosystem through the business process execution language BPEL and the eTOM business process framework method, including the input, output, process control and execution details of the business process;

[0054] 1.2.2 Based on the standardized approach of SID service design, the roles, responsibilities, functions, interfaces and dependencies of each entity in the service ecosystem are clarified;

[0055] 1.2.3 Combined with the Petri net model, model and describe the relationships between business processes and entities in the service ecosystem, including process control and data transmission.

[0056] 2. Mining implicit service demands based on service evaluation and large-scale demand analysis.

[0057] 2.1 Evaluate the current service status based on the service ecosystem model, service log analysis and performance monitoring report.

[0058] 2.1.1 Entity status assessment: Inspect the service response time, success rate and other performance indicators, and analyze the utilization, allocation efficiency and redundancy of resources (such as computing resources and storage resources).

[0059] 2.1.2 Relationship and process analysis: Use network analysis, social network analysis and other methods to evaluate the efficiency of collaboration between entities, the rationality of dependencies, and potential bottlenecks or conflict points. Use tools such as BPEL process instance monitoring logs and Petri net simulation to identify delays, bottlenecks, and abnormal paths in the process, and quantify process efficiency and flexibility.

[0060] 2.2 With the help of big model capabilities, the current service status indicators are used as input to explore the hidden needs of the current service. The specific steps are as follows.

[0061] 2.2.1 Set up a service knowledge base, including service status indicator benchmarks, service ecology and other related service information.

[0062] 2.2.2 Set standardized large model demand mining prompt words.

[0063] 2.2.3 Combine the current service status information and prompt words as model input.

[0064] 2.2.4 Output specific implicit requirements.

[0065] 3 Based on rough-fuzzy comprehensive decision-making, determine the optimal implicit demand. The specific steps are as follows.

[0066] 3.1 Use the big model as a demand analysis expert to score the invisible service needs from the perspectives of economic value, timeliness value, reliability value, flexibility value, social value, trustworthiness value, and tangible value.

[0067] 3.2 Define the implicit demand set as ,in is the demand quantity; the evaluation index set is Corresponding to the above 7 key values. For each requirement and indicators , each has an evaluation score given by a large model .

[0068] 3.3 Calculate the total support of indicators: indicators The support of measures its ability to distinguish different demand instances. After that, the different demand instances become indistinguishable, indicating The support degree is high. The support degree calculation formula is:

[0069]

[0070] in, It is removing the indicator The subsequent demand set.

[0071] 3.4 By calculating the support of each indicator, the minimum reduction set is identified, that is, the minimum number of indicators is retained while keeping the decision table's discrimination ability unchanged.

[0072] 3.5 Repeat steps 2.3.3 and 2.3.4 until further removal results in loss of information.

[0073] 3.6 For the final retention Key value indicators, for each indicator , we construct a fuzzy set , its As a membership function, it represents the demand In the indicator For each demand , its comprehensive evaluation value for:

[0074]

[0075]

[0076] in, is the weight of the corresponding indicator.

[0077] 3.7 Select the demand with a comprehensive evaluation value greater than a given threshold as the final service implicit demand.

[0078] To sum up, the service ecosystem abstraction and implicit demand analysis method for multi-entity complex scenarios in this embodiment constructs a model that can comprehensively abstract and describe the multi-entity service ecosystem, covering multiple dimensions such as entities, relationships, and processes. It proposes a method that combines service log analysis, performance monitoring, and large model analysis to effectively explore the implicit demands in the service ecosystem, establish a mechanism based on rough-fuzzy comprehensive decision-making, and accurately evaluate and determine the highest priority implicit demands to guide service optimization.

[0079] The above is only a preferred embodiment of the present invention, and the protection scope of the present invention is not limited to the above embodiments. All technical solutions under the concept of the present invention belong to the protection scope of the present invention. It should be pointed out that for ordinary technicians in this technical field, some improvements and modifications without departing from the principle of the present invention should also be regarded as the protection scope of the present invention.

Claims

1. A service ecosystem abstraction and implicit demand analysis method for multi-entity complex scenarios, characterized by: The steps include: Step 1: Model service entities and relationships, then model service capabilities and processes to complete the abstract modeling of the service ecosystem. Step 2: Based on the service ecosystem abstract model, service log analysis, and performance monitoring reports, evaluate the current service status. Then, with the help of the big model capability, use the current service status indicators as input to explore the hidden needs of the current service. Step 3: Determine the optimal implicit demand based on rough-fuzzy comprehensive decision-making; The specific steps for determining the optimal implicit demand in step 3 are as follows: Step 31: Use the big model as a demand analysis expert to score the invisible demand for services from the perspectives of economic value, timeliness value, reliability value, flexibility value, social value, trustworthiness value, and tangible value; Step 3.2: Define the implicit demand set as ,in, is the demand quantity; the evaluation index set is Corresponding to the above 7 key values, for each requirement and indicators , each has an evaluation score given by a large model ; Step 33: Calculate the total support of the indicator: The support of measures its ability to distinguish different demand instances. After that, the different demand instances become indistinguishable, indicating The support degree of is high, so the total support degree calculation formula of this indicator is: ; in, It is removing the indicator The subsequent demand set; Step 3 and 4, calculate the support of each indicator, and then identify the minimum reduction set, that is, the set that retains the least number of indicators while keeping the decision table's distinguishing ability unchanged; Step 35, repeat steps 33 and 34 until further removal results in information loss; Step 36: For the final retained Key value indicators, for each indicator , construct a fuzzy set , its As a membership function, it represents the demand In the indicator The degree of membership on , its comprehensive evaluation value for: ; ; in, is the weight of the corresponding indicator; Step 37: Select the demand with a comprehensive evaluation value greater than a given threshold as the final service implicit demand.

2. The service ecosystem abstraction and implicit demand analysis method for multi-entity complex scenarios according to claim 1 is characterized by: The specific steps for service entity and relationship modeling in step 1 are as follows: Step 1, based on the multi-agent modeling method, define and describe the types and attributes of each entity in the service ecosystem, including participant entity, service entity, data entity, resource entity to complete entity abstraction; Steps one and two: Model and describe entity relationships through the entity-relationship ER model and domain-driven design methods. The entity relationships include mutual exclusion, dependency, call, and cooperation, thereby completing the modeling of service entities and relationships.

3. The service ecology abstraction and implicit demand analysis method for multi-entity complex scenarios according to claim 1 or 2 is characterized by: The specific steps for service capability and process modeling in step 1 are as follows: Step 13: Model and describe each business process in the service ecosystem through the business process execution language BPEL and the eTOM business process framework method. Each business process includes the input, output, process control and execution details of the business process; Step 14: Based on the SID service design specification method, clarify the roles, responsibilities, functions, interfaces and dependencies of each entity in the service ecosystem; Step 15: Combine the Petri net model to model and describe the relationships between business processes and entities in the service ecosystem. The relationships between business processes and entities include process control and data transmission, thereby completing service capability and process modeling.

4. The service ecology abstraction and implicit demand analysis method for multi-entity complex scenarios according to claim 1 or 2 is characterized by: In step 2, the specific steps for evaluating the current service status based on the service ecosystem model, service log analysis, and performance monitoring report are as follows: Step 21: Inspect the performance indicators such as service response time and success rate, analyze resource utilization, allocation efficiency and redundancy to conduct entity status assessment; Step 22: Use network analysis and social network analysis to evaluate the collaboration efficiency between entities, the rationality of dependencies, and potential bottlenecks or conflict points. Specifically, use tools such as BPEL process instance monitoring logs and Petri net simulation to identify delays, bottlenecks, and abnormal paths in the process, and quantify process efficiency and flexibility.

5. The service ecosystem abstraction and implicit demand analysis method for multi-entity complex scenarios according to claim 4 is characterized by: The specific steps of mining the hidden needs of current services in step 2 are as follows: Step 23: Set up a service knowledge base, which contains service status indicator benchmarks, service ecology and other related service information; Step 24: Set the prompt words for mining the standardized large model requirements; Step 25, combining the current service status information and prompt words as model input; Step 26: Output specific implicit needs through the service ecosystem model.

Citation Information

Patent Citations

  • Composite service optimizing method and device based on protocol composition mechanism

    CN101820428A

  • Cross-boundary service demand analysis method and system and readable medium

    CN111191088A

  • Design method of product service system

    CN112270563A

  • Generation method based on domain knowledge model modeling and dynamic optimization configuration

    CN116737119A