Calling logic shows method, business system and electronic device

By converting the call logic into component form, the problem of difficulty in locating the call logic in complex business systems is solved, achieving clear and intuitive display and efficient location, thus improving the user experience.

CN115599781BActive Publication Date: 2026-04-21中国移动通信集团云南有限公司 +1
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
中国移动通信集团云南有限公司
Filing Date
2021-07-08
Publication Date
2026-04-21

AI Technical Summary

Technical Problem

Existing technologies struggle to clearly and intuitively demonstrate the call logic of complex business systems, leading to lengthy and time-consuming process for locating incorrect points and a poor user experience.

Method used

The call logic is converted into a component format for display, and display information is generated through preset mapping relationships, including component identification and call duration, which simplifies the display and improves intuitiveness.

Benefits of technology

It provides a clear and intuitive display of the calling logic, improving the efficiency of error location and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115599781B_ABST
    Figure CN115599781B_ABST
Patent Text Reader

Abstract

This invention discloses a method for displaying call logic, a business system, and an electronic device. The business system is used to run one or more services. The business system includes a preset mapping relationship between call logic and components. Each service includes multiple call logics and multiple components. The method includes: generating call information during the operation of the service, the call information indicating that the call logic is called by the service; and outputting display information based on the preset mapping relationship and the call information, the display information including multiple components corresponding to the call logic called by the service.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] This invention relates to the field of method invocation technology, and in particular to a method for displaying invocation logic, a business system, and an electronic device. [Background Technology]

[0002] A method (also known as a function) is a block of code that implements specific functionalities. In software implementation, a function is typically accomplished by one or more methods. During business logic implementation, business users can identify or pinpoint which call logic caused an exception or error by demonstrating the entire call logic's call logic (or call chain).

[0003] However, as business systems continue to accumulate and develop, especially for complex business systems that are difficult to microservices, it is difficult to clearly and intuitively display the calling logic of the entire business processing method, and there are problems such as difficulty in locating errors in the calling logic and difficulty in optimization.

[0004] In related technologies, business call logic is displayed in the form of method call chains. However, because method call chains are very fine-grained and have many layers, they cannot clearly and intuitively display the business call logic. Complex business logic can generate method call chain messages that are tens of megabytes in size, which not only causes slow page loading and puts a lot of pressure on the browser itself, but also results in a poor user experience. Furthermore, business errors are not easy to locate, requiring users to click through layers to find the error location. Since most business logic is quite complex and the call chains are nested, locating the exact location of a problem error often takes a long time, which greatly tests the patience of users. [Summary of the Invention]

[0005] In view of this, embodiments of the present invention provide a method for displaying call logic, a business system, and an electronic device, which convert the call logic of the business call into components for display, which helps to simplify the displayed information, make it clear and intuitive, and improve the user experience.

[0006] In a first aspect, embodiments of the present invention provide a method for displaying call logic, applied to a business system. The business system is used to run one or more services, and the business system includes a preset mapping relationship between call logic and components. Each service includes multiple call logics and multiple components. The method includes:

[0007] During the execution of the service, invocation information is generated, which indicates that the invocation logic is invoked by the service.

[0008] Based on the preset mapping relationship and the call information, display information is output, which includes multiple components corresponding to the call logic invoked by the service.

[0009] In one possible implementation, each of the business operations further includes a business process, and the method further includes:

[0010] According to the business process, multiple components corresponding to the calling logic invoked by the business are displayed.

[0011] In one possible implementation, each component includes multiple sub-components, and the business process includes a preset first relationship between the multiple components, a preset second relationship between the component and the sub-components, and a preset third relationship between the multiple sub-components. The step of displaying the multiple components corresponding to the calling logic invoked by the business process according to the business process includes:

[0012] According to the preset first relationship, multiple components are displayed;

[0013] According to the preset second relationship and the third relationship, multiple sub-components contained in the component will be displayed.

[0014] In one possible implementation, the component includes a component identifier and a component enhancement class name, the business process includes a business process identifier and a business process enhancement class name, the business process also includes an entry method and an end method, multiple invocation logics are located between the entry method and the end method, and the method further includes:

[0015] Generate the first configuration file required for the business process tracking points according to the business process identifier and the business process enhancement class name;

[0016] Generate a second configuration file for each component's embedding points based on each component identifier and component enhancement class name;

[0017] Insert the first configuration file into the entry method and / or the end method;

[0018] The second configuration file is embedded in the calling logic.

[0019] In one possible implementation, the call information includes timestamps of multiple call logics, and the display information also includes the call duration of the call logic corresponding to each component. The step of outputting display information based on the preset mapping relationship and the call information includes:

[0020] Based on the preset mapping relationship, the timestamp of the call logic corresponding to each component is obtained from the call information;

[0021] Based on the timestamps of adjacent call logics, the call duration of the call logic corresponding to each component is obtained.

[0022] In one possible implementation, the call information further includes the call time and number of calls to the business process, and the display information further includes the access duration of the business process and the access volume within a preset time period. The step of outputting display information based on the mapping relationship and the call information further includes:

[0023] The access duration of the business process is obtained based on the call duration of the call logic corresponding to each component in the business process.

[0024] Based on the invocation time and number of invocations of the business process, the access volume of the business process within a preset time period is obtained.

[0025] In one possible implementation, the business system further includes a first database and a second database, the call information includes full data and indexed data, and the generation of call information during the operation of the business includes:

[0026] Log information is generated each time the aforementioned call logic is invoked;

[0027] The log information is stream processed to obtain the full data and the index data. The full data is used to represent the information of the calling logic being invoked, and the index data is used to search for the information of the calling logic being invoked.

[0028] Store the full amount of data into the first database;

[0029] The index data is stored in the second database.

[0030] Secondly, this application provides a business system for running one or more services. The business system includes a preset mapping relationship between calling logic and components. Each service includes multiple calling logics and multiple components. The business system further includes:

[0031] A generation module is used to generate call information during the execution of the business, the call information being used to indicate that the call logic is called by the business;

[0032] The output module is used to output display information based on the preset mapping relationship and the call information, wherein the display information includes multiple components corresponding to the call logic called by the service.

[0033] Thirdly, embodiments of the present invention provide an electronic device, including: a memory and a processor:

[0034] The memory is used to store computer programs;

[0035] The processor is configured to execute a computer program stored in the memory to cause the electronic device to perform the method as described in the first aspect.

[0036] Fourthly, embodiments of the present invention provide a computer-readable storage medium including a program or instructions that, when the program or instructions are run on a computer, execute the method described in the first aspect.

[0037] Compared with the prior art, this technical solution has at least the following beneficial effects:

[0038] The calling logic display method, system, and electronic device disclosed in the embodiments of the present invention display the calling logic called by the business in the form of components, which helps to simplify the display information, make it clear and intuitive, and improve the user experience. [Attached Image Description]

[0039] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 This is a schematic diagram of the calling logic display method provided in Embodiment 1 of the present invention;

[0041] Figure 2 This is a system block diagram of the calling logic display method provided in Embodiment 1 of the present invention applied to a business system;

[0042] Figure 3 This is a schematic diagram illustrating the display information of multiple components and call duration in the call logic display method provided in Embodiment 1 of the present invention;

[0043] Figure 4 This is a schematic diagram illustrating the display information of the business process in the call logic display method provided in Embodiment 1 of the present invention;

[0044] Figure 5 This is a schematic diagram illustrating the display information of components and sub-components in the business process of the call logic display method provided in Embodiment 1 of the present invention;

[0045] Figure 6 This is a schematic diagram illustrating the display of access duration information for the business process in the call logic display method provided in Embodiment 1 of the present invention;

[0046] Figure 7This is a schematic diagram illustrating the display of business volume information for multiple business processes in the call logic display method provided in Embodiment 1 of the present invention;

[0047] Figure 8 This is a schematic diagram of the business process provided in Embodiment 2 of the present invention.

[0048] Figure label:

[0049] 10 - Generation module; 20 - Output module.

Detailed Implementation Methods

[0050] To better understand the technical solution of the present invention, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0051] It should be understood that the described embodiments are merely some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0052] The main methods for displaying the calling logic of related technologies are as follows:

[0053] One related technology uses hard-coded event tracking to trace method call logic. During business execution, call information is recorded and stored in a traditional relational database. This information is then processed and displayed as a method call chain. However, this hard-coded tracking method requires modifications to existing business code, resulting in tight coupling between the tracking code and the business code, hindering scalability, requiring highly skilled users, and exhibiting a high error rate.

[0054] The second related technology involves non-intrusive instrumentation of business code through Java (a computer programming language) enhancement. During business operation, the generated log information is sent to a Kafka cluster (a high-throughput distributed publish-subscribe messaging system). After being processed by a Flink cluster (a stream processing platform), the logs are stored in a database and the business call logic is displayed in the form of a method call chain via a web page.

[0055] In related technologies one and two, because the method call chain is very fine-grained and has many levels, it is not possible to clearly and intuitively display the business call logic. The method call chain messages generated by complex business can be as large as tens of megabytes, which not only causes the display page to load slowly and puts a lot of pressure on the browser itself, but also makes it unfriendly to users. Moreover, business errors are not easy to locate, requiring users to click through layers to find the error location. Since most businesses are quite complex and the call chain is nested, it often takes a long time to locate the exact location of a problem error, which is a great test of the user's patience.

[0056] To this end, this application provides a method, system, and electronic device for displaying call logic, which converts the call logic of the business call into components for display, which helps to simplify the displayed information, make it clear and intuitive, improve the user experience, and does not require changes to the existing business code.

[0057] Example 1

[0058] Embodiment 1 of this invention proposes a method for displaying call logic, such as... Figure 1 and Figure 2 As shown, the method is applied to a business system that runs one or more business processes (such as product ordering, customer center operations, and retail inventory management). Each business process can contain calling logic corresponding to multiple methods. For example, taking a web login process as an example, it requires multiple methods such as user verification, password verification, and page content loading. When implementing this business process, the calling logic of these methods needs to be invoked by the business process itself. Some methods may be invoked by the calling logic of multiple business processes. For instance, the password format verification method may be invoked when setting payment passwords or login passwords. Therefore, the calling logic of the same method invoked by different business processes may be inconsistent.

[0059] In this embodiment, the business system may include a preset mapping relationship between calling logic and components, and each business may also contain multiple components. That is, the calling logic of a method in each business can be abstracted into the concept of a component, and the preset mapping relationship between the calling logic and the components is configured in the business system. Preferably, a component may include a component identifier and a component enhanced class name. The component identifier may be such as a component name or component ID, etc. The component may also include a component entry class name, a component entry method, etc., and the component can be configured according to the corresponding calling logic.

[0060] For example, multiple business processes can include business A, business B, etc. Business A can include call logic A1, call logic A2, call logic A3, etc. Business B can include call logic B1, call logic B2, call logic B3, etc.

[0061] Specifically, the business system may include a configuration center, such as a Relational Database Management System (RDBMS), for storing configuration information such as components and the preset mapping relationship between components and calling logic. Components can be pre-configured based on the name, function, or entry class name, entry method, enhancement class name, etc. of the calling logic. Each component can be configured in the corresponding business logic to establish the preset mapping relationship between the component and the calling logic.

[0062] For example, in the configuration center, call logic A1 is configured as component 1, call logic A2 is configured as component 2, ..., and a mapping relationship is established between call logic and components.

[0063] For example, taking the product ordering business as an example, according to the multiple call logic functions of the product ordering business, the corresponding component names may include, but are not limited to, "Process payment fees: whether to call the payment page and synchronize operating expenses to the accounting department", "Rules verification before business acceptance", "Delete GPRS service and delete the bound platform service", "Broadband marketing activities - activity expiration calculation", "Broadband account opening - create fee item information", "Create product feature information", "Construct product information", "Cancel the national comic package on the front end and upload it to the platform", "Create user developer information", "Process product changes and automatically unsubscribe from associated products", etc.

[0064] like Figure 1 As shown, calling the logic display method may include the following steps:

[0065] S101. During the operation of the service, call information is generated, which is used to indicate that the call logic is called by the service.

[0066] For example, the business system may also include an application service cluster, which may contain a WEB (web page) module, an ESB (Enterprise Service Bus) module, or an APP (application) module. The WEB module is used to run business on the web page, the ESB is used to run business on the enterprise service bus, and the APP module is used to run business on the APP.

[0067] Preferably, each business function's multiple call logics can include configuration files (or code) for the embedded points. These configuration files are generated based on the components corresponding to the call logic. The configuration file for each embedded point in the call logic can record the preset mapping relationship between the current business's call logic and the component, and can include component identifiers, such as component name or component ID. To avoid affecting existing business code in the business system, Java Instrumentation technology can be used to embed the embedded points into the corresponding call logic using the configuration file. Compared to hard-coding, this method is more scalable, requires less technical expertise from users, and has a lower error rate.

[0068] In step S101, during the operation of the business, each time a call logic containing the embedded point is invoked, a log message (or record data, trace) is generated. Then, the log message is stream-processed to obtain the call information.

[0069] Understandably, call information can be used to locate the call logic invoked by the current business logic, or to determine whether an error or exception has occurred in the call logic invoked by the current business logic. The call information may contain timestamps of multiple call logics, and each timestamp may contain information such as the original file information, signature parameters, and signature time of the call logic invoked by the corresponding business logic.

[0070] Preferably, the business system may further include a first database and a second database, the call information includes full data and index data, and step S101 may include:

[0071] S201. Generate log information each time the invocation logic is invoked;

[0072] S202. Perform stream processing on the log information to obtain the full data and the index data. The full data is used to represent the information of the call logic being invoked, and the index data is used to search for the information of the call logic being invoked.

[0073] S203. Store the full data into the first database;

[0074] S204. Store the index data into the second database.

[0075] Specifically, the business system may also include a calling module, a consumer cluster (such as a Kafka cluster), and a stream processing platform. The calling module generates log information (trace) and pushes it onto a stack each time the business logic is invoked. At the end of the call, the generated log information is popped from the stack and asynchronously sent to the Kafka cluster. The stream processing platform may include a Flink cluster (a distributed streaming data engine written in Java and Scala). The Flink cluster is used to continuously consume data from the Kafka cluster through trace tasks. The consumed data is transformed, analyzed, and processed by operators such as json to map (a format conversion utility class that converts JSON format to Java map format), es-bean (an Elasticsearch search engine object wrapped in Java), and hbase-bean (an HBase distributed storage system object wrapped in Java) to obtain the full data and indexed data.

[0076] The first database may include a distributed storage system (HBase) for storing all data. In step S203, the full data is written to HBase for storage via the HBase-sink subtask. The second database may include a search server (Elasticsearch). In step S204, index data is written to Elasticsearch for storage via the Elasticsearch-sink subtask.

[0077] S102. Based on the preset mapping relationship and the call information, output display information, wherein the display information includes multiple components corresponding to the call logic called by the service.

[0078] In other words, each call logic is displayed in the form of a component. For example, the display information can include the component identifier of each component (such as component name or component ID). For example, the component name can be used to locate the call logic, such as its location, thereby simplifying the display information, making it clear and intuitive, and improving the user experience.

[0079] Specifically, in step S102, according to the preset mapping relationship, the call information is retrieved from the first database and the second database. Based on the component identifier contained in the call information, the corresponding component is retrieved from the configuration center. After integrating the call information and the component, the display information is output.

[0080] For example, taking the product ordering business as an example, the multiple components displayed in the information may include, but are not limited to, "determining whether the employee has the authority to order products", "constructing product change business data", "unified rule verification processing before business submission", and "unified rule verification processing after business submission". Compared with the related technologies that display the calling logic called by the business in the form of a method call chain, this embodiment displays the calling logic called by the business in the form of components, which is clearer and more intuitive and helps to improve the user experience.

[0081] In one possible implementation, each of the business operations further includes a business process, and the method further includes:

[0082] S301. According to the business process, display the multiple components corresponding to the calling logic invoked by the business.

[0083] Depending on the function or calling logic of each business, the business process will be different for each business. For example, business A may include business process A, business B may include business process B, and so on.

[0084] like Figure 4As shown, for example, a business process can include the calling relationships between multiple calling logics, and multiple components can be displayed according to these calling relationships. That is, the relationship between adjacent components (such as connection relationships, hierarchical relationships, or reference relationships) can be determined based on the calling relationships between corresponding adjacent calling logics. This business process can include multiple components corresponding to the calling logics called by the business. In step S301, the business process of each business can be displayed. For example, taking the product ordering business as an example, the business process can include calling logics from start to finish, which are "determine if the employee has the permission to order products", "build product change business data", "unified rule verification processing before business submission", and "unified rule verification processing after business submission", etc. Correspondingly, the multiple components belonging to this business process can include the first component such as "start", the second component such as "determine if the employee has the permission to order products", the third component such as "build product change business data", the fourth component such as "unified rule verification processing before business submission", the fifth component such as "unified rule verification processing after business submission", and the sixth component such as "end", etc., and are displayed in sequence. Therefore, displaying multiple components in the form of a business process is more conducive to users' viewing.

[0085] In one possible implementation, each component may contain multiple sub-components, and the business logic may also include a preset first relationship between multiple components, a preset second relationship between a component and its sub-components, and a preset third relationship between multiple sub-components. Step S301 may include:

[0086] S302. Display the multiple components according to the preset first relationship;

[0087] S303. According to the preset second relationship and the third relationship, multiple sub-components contained in the component are displayed.

[0088] For example, the first preset relationship can include a parallel relationship, the second preset relationship can include an inclusion relationship, and the third preset relationship can include a parallel relationship. That is, components are parallel to each other, multiple components can be displayed sequentially according to the parallel relationship, each component can contain multiple sub-components, the components and sub-components are inclusion relationships, the multiple sub-components are parallel relationships, and the component can be operated by the user (or user personnel) (expand by mouse click, etc.) and displayed in the form of multiple sub-components.

[0089] like Figure 5As shown, for example, the third component, such as "Constructing Product Change Business Data," can contain multiple sub-components, which are displayed sequentially. These sub-components include: "Verification of Business Number Existence and In-Processing Business," "Rule Verification Before Business Acceptance," "Processing of Instance Data for User Main Products, Atomic Products, and Combination Products," "Effective Time of Special Handling for Product Change Orders," "Atomic Product Instance Creation Processing," "Voice Product Feature Processing," "Processing of Synchronizing Product Feature Specifications with Price Feature Specifications," "Processing Automatic Unsubscription of Related Products After Main Product Change," "Processing of Adding Discounted Products Along with Adding Service Products," "Processing Discounted Products Along with Service Products," "Processing Discounted Products Along with Products," "Processing Discount Information When Changing Packages," "Processing the Effective and Expiration Time of Special Offers," "Create Instances of Business Interaction Item Features," "Fee Discount Processing," "Processing Discounted Products Bound to Discount Offers," "Special Handling of Main Product Changes on the Day of Account Opening," and "Rule Verification After Business Acceptance," etc.

[0090] Preferably, each business process can be configured by the user, such as adding or deleting components within the business process. Specifically, the business system may also include a component library, which stores multiple components and their corresponding sub-components. These components and sub-components are arranged in a list. When configuring a business process, the user can select one or more components and their corresponding sub-components from the list and add them to the corresponding business process. For example, a business process may contain multiple nodes, and each node may contain multiple child nodes. The user can add components to nodes and sub-components to child nodes to configure a business process corresponding to the actual business.

[0091] In one possible implementation, the component may include a component identifier and a component enhancement class name; the business process may include a business process identifier and a business process enhancement class name; the business process may also include an entry method and an end method; multiple invocation logics are located between the entry method and the end method; and the method may further include:

[0092] S401. Generate the first configuration file required for the business process tracking points according to the business process identifier and the business process enhancement class name;

[0093] S402. Generate a second configuration file required for each component's embedding points according to each component identifier and the component enhancement class name;

[0094] S403. Insert the first configuration file into the entry method and / or the end method;

[0095] S404. Insert the second configuration file into the calling logic.

[0096] For example, business processes and components can be obtained by user input. A business process identifier may include the business process name, business process ID, and the business it belongs to; a business process may also include the business process entry class name or business process entry method. A component identifier may include the component name, component ID, and the business it belongs to; a component may also include the component entry class name or component entry method.

[0097] In other words, when configuring a business process, information such as the component name, the business it belongs to, the business process entry class name, the business process entry method, the business process enhancement class name, or the business process type, inputted by the user, is obtained to generate the first configuration file required for the business process's tracking points. This first configuration file is then used to track data in the business's entry method and / or termination method. When configuring a component, information such as the component name, the business it belongs to, the component entry class name, the component entry method, the component enhancement class name, or the component type, inputted by the user, is obtained to generate the second configuration file required for the component's tracking points. This second configuration file is then used to track data in any location within the corresponding call logic.

[0098] Preferably, in steps S403 and S404, Java Instrumentation technology can be used to package the first configuration file and the second configuration file independently (such as a jar compressed package) and enhance them into the business system to achieve non-intrusive instrumentation without changing the existing business code.

[0099] It should be noted that business event tracking specifications through enhancement can include target class configuration specifications, target method configuration specifications, and enhancement class naming specifications. In the target class configuration specification, the target class is defined as the class containing the entry method of the business process or component (e.g., the entry class name). The target class configuration uses the fully qualified name, for example: com.ai.comframe.vm.workflow.service.impl.WorkflowEngineSVImpl. In the target method configuration specification, the target method is defined as the entry method of the business process or component. The target method configuration needs to specify the entire method definition, for example: Protectedvoid doService(javax.servlet.http.HttpServletRequest request, javax.servlet.http.HttpServlet Response response). Here, the parameter types and return type are both written in fully qualified names. In the enhancement class naming specification, the enhancement class is defined as an aspect class of the target method, and the enhancement class needs to be configured with a pointcut. The naming convention for enhancement classes is com.ai.agent.trans.adapter.impl.center_name (lowercase).target_class_name + Adapter, for example, com.ai.agent.trans.adapter.impl.comframe.WorkflowEngineSVImplAdapter.

[0100] In one possible implementation, the display information may further include the call duration of the calling logic corresponding to each component, and step S102 may include:

[0101] S501. Based on the preset mapping relationship, obtain the timestamp of the call logic corresponding to each component from the call information;

[0102] S502. Based on the timestamps of adjacent calling logics, obtain the calling duration of the calling logic corresponding to each component.

[0103] For example, the call duration of a call logic represents the time consumed when the logic is invoked by the business logic, or the time consumed when the business logic executes the invoked method. This duration can be derived from the time interval between the timestamps of adjacent call logic calls. Figure 3 As shown, for example, the call duration of the calling logic A1 corresponding to component 1 is T1, the call duration of the calling logic A2 corresponding to component 2 is T2, the call duration of the calling logic A3 corresponding to component 3 is T3, and so on.

[0104] In this embodiment, the display information can show multiple components and the call duration of the call logic corresponding to each component. This allows users to determine whether an error has occurred in the call logic based on the call duration of the call logic corresponding to each component, and to locate the call logic, such as its location, based on the name of the component. Therefore, it is possible to quickly determine which call logic has an error and to quickly locate the exact location of the call logic that has an error.

[0105] In one possible implementation, the call information may further include the call time and number of calls of the business process, and the display information may further include the access duration of the business process and the access volume within a preset time period. Step S102 may further include:

[0106] S601. Obtain the access duration of the business process based on the call duration of the call logic corresponding to each component in the business process;

[0107] S602. Based on the invocation time and number of invocations of the business process, obtain the access volume of the business process within a preset time period.

[0108] In other words, the access time of a business process represents the time consumed from the start to the end of the business process. It can be obtained by summing the call times of the calling logic corresponding to all components in the business process, so that users can intuitively understand the access time of each business process.

[0109] like Figure 6 As shown, further, in step S601, based on the access duration of the business process, the call time of the business process, and the number of calls, the average access duration of the business process within a preset time interval (such as every 5 minutes) can be calculated, so that users can understand the average access duration of the business process every 5 minutes.

[0110] The access volume of a business process is used to represent the number of times a business process is accessed within a preset time period (e.g., every 5 minutes). For example... Figure 7 As shown, the information displayed can further include the access volume of multiple business processes within a preset time period, and display them uniformly on the same coordinate graph, so that users can intuitively understand the access volume of multiple business processes every 5 minutes and make comparisons.

[0111] It is understood that some or all of the steps or operations in the above embodiments are merely examples, and other operations or variations thereof can be performed in the embodiments of this application. Furthermore, the steps may be performed in different orders as presented in the above embodiments, and it is not necessary to perform all the operations in the above embodiments.

[0112] Example 2

[0113] like Figure 8 As shown, Embodiment 2 of the present invention discloses a business system 100, which is used to run one or more business processes. The business system 100 may include a preset mapping relationship between calling logic and components. Each business process includes multiple calling logics and multiple components. The business system 100 may also include:

[0114] The generation module 10 is used to generate call information during the operation of business. The call information is used to indicate that the calling logic is called by the business.

[0115] The output module 20 is used to output display information based on the preset mapping relationship and the call information. The display information contains multiple components corresponding to the call logic called by the business.

[0116] In one possible implementation, each business function also includes a business process, and the output module 20 is further used for:

[0117] According to the business process, multiple components corresponding to the calling logic invoked by the business are displayed.

[0118] In one possible implementation, each component contains multiple sub-components, and the business process includes a preset first relationship between multiple components, a preset second relationship between components and sub-components, and a preset third relationship between multiple sub-components. The output module 20 is further used for:

[0119] Based on the preset primary relationship, multiple components are displayed;

[0120] According to the preset second relationship and the preset third relationship, the multiple sub-components contained in the component will be displayed.

[0121] In one possible implementation, the component includes a component identifier and a component enhancement class name; the business process includes a business process identifier and a business process enhancement class name; the business process also includes an entry method and an end method; multiple call logics are located between the entry method and the end method; the business system 100 is also used for:

[0122] Generate the first configuration file required for business process tracking based on the business process identifier and the business process enhancement class name;

[0123] Generate a second configuration file for each component's embedding points based on each component's identifier and component enhancement class name;

[0124] Insert the first configuration file into the entry method and / or the end method;

[0125] Insert the second configuration file into the calling logic.

[0126] In one possible implementation, the call information includes timestamps for multiple call logics, and the display information also includes the call duration of the call logic corresponding to each component. The output module 20 is also used for:

[0127] Based on the preset mapping relationship, the timestamp of the call logic corresponding to each component is obtained from the call information;

[0128] Based on the timestamps of adjacent call logic, the call duration of the call logic corresponding to each component is obtained.

[0129] In one possible implementation, the call information also includes the call time and number of calls to the business process, and the display information also includes the access duration of the business process and the access volume within a preset time period. The output module 20 is also used for:

[0130] The access duration of the business process is obtained based on the call duration of the call logic corresponding to each component in the business process.

[0131] Based on the time and number of times the business process is invoked, the number of visits to the business process within a preset time period is obtained.

[0132] In one possible implementation, the business system also includes a first database and a second database, and the access information includes full data and indexed data. The generation module 10 is used for:

[0133] Log information is generated each time the call logic is invoked;

[0134] The log information is stream processed to obtain full data and index data. The full data is used to represent the information of the called logic, and the index data is used to search for the information of the called logic.

[0135] Store all data in the first database;

[0136] Store the index data in the second database.

[0137] Understandable, Figure 8 The business system provided in the illustrated embodiment can be used to execute this application. Figure 1 The implementation principle and technical effects of the method embodiment shown can be further referred to the relevant description in the method embodiment.

[0138] The above should be understood Figure 8The division of the business system modules shown is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or physically separated. These modules can be implemented entirely in software via processing element calls; entirely in hardware; or partially in software via processing element calls and partially in hardware. For example, the generation module can be a separate processing element or integrated into a chip in an electronic device. The implementation of other modules is similar. Furthermore, these modules can be fully or partially integrated together or implemented independently. During implementation, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.

[0139] For example, these modules can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, these modules can be integrated together as a System-On-a-Chip (SOC).

[0140] Example 3

[0141] Embodiment 3 of the present invention provides an electronic device, including: a memory and a processor:

[0142] Memory, used to store computer programs;

[0143] A processor is used to execute a computer program stored in memory to cause an electronic device to perform the method as described in Example 1.

[0144] The processor and memory can communicate with each other through an internal connection path to transmit control and / or data signals. The memory is used to store computer programs, and the processor is used to call and run the computer programs from the memory.

[0145] The aforementioned memory may be a read-only memory (ROM), other types of static storage devices capable of storing static information and instructions, random access memory (RAM), or other types of dynamic storage devices capable of storing information and instructions. It may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices. Alternatively, it may be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer.

[0146] Example 4

[0147] Embodiment 4 of the present invention provides a computer-readable storage medium including a program or instructions that, when the program or instructions are run on a computer, execute the method of Embodiment 1.

[0148] The calling logic display method, system, and electronic device disclosed in this invention strengthen the weight influence of current data and reduce the influence of historical data by using a forgetting factor to calculate the optimal position of the particle. The optimal position is then used to replace the extreme position of the particle. This helps to enhance the system's ability to respond quickly to changes in the current environment and user model, accelerate the convergence speed and optimization accuracy of the system algorithm, and solve the parameter configuration problems of base stations in various scenarios, thereby improving the service quality of base stations.

[0149] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)).

[0150] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for displaying call logic, applied to a business system, the business system being used to run one or more business processes, characterized in that, The business system includes a preset mapping relationship between calling logic and components. Each business includes multiple calling logics and multiple components. The method includes: During the execution of the service, invocation information is generated, which indicates that the invocation logic is invoked by the service. Based on the preset mapping relationship and the call information, display information is output, and the display information includes multiple components corresponding to the call logic called by the service. Each of the aforementioned business operations further includes a business process, and the method further includes: According to the business process, multiple components corresponding to the calling logic invoked by the business are displayed; The component includes a component identifier and a component enhancement class name; the business process includes a business process identifier and a business process enhancement class name; the business process also includes an entry method and an end method; multiple invocation logics are located between the entry method and the end method; the method further includes: Generate the first configuration file required for the business process tracking points according to the business process identifier and the business process enhancement class name; Generate a second configuration file for each component's embedding points based on each component identifier and component enhancement class name; Insert the first configuration file into the entry method and / or the end method; The second configuration file is embedded into the calling logic.

2. The method for displaying call logic according to claim 1, characterized in that, Each component contains multiple sub-components. The business process includes a preset first relationship between the components, a preset second relationship between the component and the sub-components, and a preset third relationship between the sub-components. The step of displaying the multiple components corresponding to the calling logic invoked by the business process, according to the business process, includes: According to the preset first relationship, multiple components are displayed; According to the preset second relationship and the preset third relationship, the multiple sub-components contained in the component will be displayed.

3. The method for displaying call logic according to claim 1, characterized in that, The call information includes timestamps of multiple call logics, and the display information also includes the call duration of the call logic corresponding to each component. The output of display information based on the preset mapping relationship and the call information includes: Based on the preset mapping relationship, the timestamp of the call logic corresponding to each component is obtained from the call information; Based on the timestamps of adjacent call logics, the call duration of the call logic corresponding to each component is obtained.

4. The method for displaying call logic according to claim 3, characterized in that, The invocation information also includes the invocation time and number of times the business process is invoked, and the display information also includes the access duration of the business process and the access volume within a preset time period. The step of outputting display information based on the mapping relationship and the invocation information further includes: The access duration of the business process is obtained based on the call duration of the call logic corresponding to each component in the business process. Based on the invocation time and number of invocations of the business process, the access volume of the business process within a preset time period is obtained.

5. The method for displaying call logic according to any one of claims 1 to 4, characterized in that, The business system also includes a first database and a second database. The call information includes full data and indexed data. During the operation of the business, the generation of call information includes: Log information is generated each time the aforementioned call logic is invoked; The log information is stream processed to obtain the full data and the index data. The full data is used to represent the information of the calling logic being invoked, and the index data is used to search for the information of the calling logic being invoked. Store the full amount of data into the first database; The index data is stored in the second database.

6. A business system for running one or more business processes, characterized in that, The business system includes a preset mapping relationship between calling logic and components. Each business includes multiple calling logics and multiple components. The business system also includes: A generation module is used to generate call information during the execution of the business, the call information being used to indicate that the call logic is called by the business; The output module is used to output display information based on the preset mapping relationship and the call information, wherein the display information includes multiple components corresponding to the call logic called by the service; Each of the aforementioned business operations further includes a business process, and the output module is further used for: According to the business process, multiple components corresponding to the calling logic invoked by the business are displayed; The component includes a component identifier and a component enhancement class name; the business process includes a business process identifier and a business process enhancement class name; the business process also includes an entry method and an end method; multiple calling logics are located between the entry method and the end method; the output module is further used for: Generate the first configuration file required for the business process tracking points according to the business process identifier and the business process enhancement class name; Generate a second configuration file for each component's embedding points based on each component identifier and component enhancement class name; Insert the first configuration file into the entry method and / or the end method; The second configuration file is embedded into the calling logic.

7. An electronic device, characterized in that, include: Memory and processor: The memory is used to store computer programs; The processor is configured to execute a computer program stored in the memory to cause the electronic device to perform the method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, Includes a program or instructions that, when run on a computer, execute the method as described in any one of claims 1 to 5.

Citation Information

Patent Citations

  • Service control method and device

    CN104715309A