Subsystem data interconnection method suitable for commercial investment production management platform

Abstract

The application relates to the technical field of data processing, in particular to a subsystem data interconnection method suitable for a commercial investment production management platform. The method comprises the following steps: collecting interaction log data; dividing the interaction log data into different fields; determining an adaptation degree based on the number of field sending and the number of subsystem receiving and the number of field request passing; determining a protocol focus degree based on the field adaptation degree and the difference between the adaptation degrees of all fields; screening high-focus subsystems for the protocol focus degrees of the subsystems corresponding to the fields, and determining effectiveness by using the historical transmission times, the historical protocol focus degrees, the number of requests and the protocol focus degrees of the high-focus subsystems; determining a first-hop transmission node based on the effectiveness; determining a priority according to the effectiveness and the hop number change of the high-focus subsystems and the effectiveness and the hop number change of the first-hop transmission node, and then completing data transmission. The application improves the stability of network transmission.

Description

Technical Field

[0001] This application relates to the field of data processing technology, specifically to a subsystem data interconnection method applicable to a commercial investment asset management platform. Background Technology

[0002] The subsystem data interconnection method selects data channels and pre-allocates traffic based on system status assessment results. An integration platform adapts the system's interactive capabilities, enabling a multi-dimensional and comprehensive evaluation of system connectivity. Traditional solutions allocate channels based on manual interface configuration. The subjectivity of manual configuration and insufficient understanding of the underlying system load conditions can easily reduce the accuracy of scheduling decisions. Therefore, in the process of evaluating the data processing capabilities between business systems through an integration platform, the existing static routing method based on preset rules for merging transmission requirements has poor sensitivity to dynamic changes in business traffic. This results in a failure to obtain data transmission paths more suited to the current load, leading to poor transmission security and stability, necessitating optimization. Summary of the Invention

[0003] To address the technical problem of poor data transmission stability, this application provides a subsystem data interconnection method suitable for commercial investment asset management platforms. The specific technical solution adopted is as follows:

[0004] This application proposes a subsystem data interconnection method applicable to a commercial investment asset management platform, the method comprising the following steps:

[0005] Collect interaction log data;

[0006] Pre-defined domains are used to distribute interaction log data to different domains. For any subsystem, the adaptability of each domain is obtained based on the ratio of the number of successful transmission requests to the total number of transmission requests sent, and the ratio of the number of concurrent requests in each domain to the rated concurrent capacity allocated to the domain by the subsystem. The adaptability of all domains in the subsystem is sorted in ascending order of the number of concurrent requests to obtain an adaptability sequence. The protocol focus of each domain on the subsystem is obtained based on the ranking of each domain in the adaptability sequence and the difference between the adaptability of each domain and the overall adaptability of the subsystem.

[0007] For any domain, sort the protocol focus of the subsystems that can transmit data in that domain in descending order to obtain a descending focus sequence; perform first-order difference on the descending focus sequence, and determine the high-focus subsystems based on the maximum protocol focus and the maximum difference value; determine the transmission stability based on the difference between the number of times the high-focus subsystems have simultaneously transmitted data from each domain in history and the number of requests within each domain; compare the average protocol focus of the domain in the historical transmission of data from the subsystems with the maximum protocol focus of the corresponding high-focus subsystems to determine the transmission history fitness; and obtain the effectiveness of the high-focus subsystems in each domain based on the transmission stability and transmission history fitness.

[0008] The first-hop transmission node is determined based on its effectiveness; the priority of the high-focus subsystem is determined based on the similarity between the effectiveness of each high-focus subsystem and the effectiveness of the first-hop transmission node, as well as the change in the number of hops to the target address after data transmission to the high-focus subsystem; the next-hop transmission node is determined based on the priority, and a data transmission network is constructed to complete the data transmission.

[0009] In the above scheme, this application divides the transmission domain by judging the performance requirements of the data to be transmitted, and further evaluates the compatibility between the network nodes and the data at the same level of the preset request performance data classification, thereby matching a portion of the subsystem transmission nodes with high transmission stability for the data to be transmitted, so that the network transmission process has higher security and stability, and completes the secure and efficient interconnection of commercial investment asset data.

[0010] In one embodiment, the interaction log data includes transmission data and transmission requirements; the transmission data includes a system ID identifier, interface protocol type, service version number, average daily call count, service health rating, average response time, timeout rate, requester satisfaction score, and number of error alarms; the transmission requirements include a requirement ID, transmission priority, bandwidth requirements, and timeliness requirements. The requirement ID corresponds to an ID identifier.

[0011] In one embodiment, the adaptability is positively correlated with the transmission success rate and negatively correlated with the concurrency ratio: the transmission success rate is the ratio of the number of transmission requests that pass in each domain to the total number of transmission requests sent; the concurrency ratio is the ratio of the number of concurrent requests in each domain to the rated concurrency allocated to the domain by the subsystem.

[0012] In one embodiment, the protocol focus is positively correlated with the ranking of each domain in the fitness sequence and the difference between the fitness of each domain and the fitness of the subsystem as a whole.

[0013] In one embodiment, the high-focus subsystem is determined based on the maximum and maximum difference values ​​of protocol focus:

[0014] The subsystem with the highest protocol focus among the two subsystems corresponding to the maximum difference value is taken as the first segment point; the subsystem with the highest protocol focus in the descending sequence of focus is taken as the second segment point; the interval between the first segment point and the second segment point is denoted as the high focus interval, and the subsystems in the high focus interval are denoted as high focus subsystems.

[0015] In one embodiment, the transmission stability is the ratio of the number of times the highly focused subsystem has simultaneously transmitted data from each domain to the number of requests within each domain in the past.

[0016] In one embodiment, the transmission history fitness is the ratio of the average protocol focus of the domain in the historical transmission of the subsystem to the maximum protocol focus of the high-focus subsystem corresponding to the domain.

[0017] In one embodiment, the effectiveness is positively correlated with both transmission history adaptability and transmission stability.

[0018] In one embodiment, the priority of a high-focus subsystem is positively correlated with the similarity between the effectiveness of each high-focus subsystem and the effectiveness of the first-hop transmission node, and with the change in the number of hops the high-focus subsystem takes to reach the target address before and after data transmission.

[0019] In one embodiment, the method for determining the next-hop transmission node based on priority and constructing a data transmission network to complete data transmission is as follows:

[0020] The high-focus subsystem corresponding to the highest priority is selected as the next-hop transmission node. After transmission to the next-hop transmission node, the previous-hop transmission node is removed from the high-focus interval. When selecting the next-hop transmission node in the future, the removed transmission node is not selected. All next-hop transmission nodes are determined to build a data network and complete the data transmission.

[0021] The beneficial effects of this application are as follows:

[0022] This application divides the transmission domain by judging the performance requirements of the data to be transmitted, and further evaluates the compatibility between network nodes and data of the same level of preset request performance data classification. This allows for the matching of a subset of subsystem transmission nodes with high transmission stability for the data to be transmitted, resulting in higher security and stability in the network transmission process and enabling secure and efficient interconnection of commercial investment asset data. Attached Figure Description

[0023] To more clearly illustrate the technical solutions and advantages in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a flowchart illustrating a subsystem data interconnection method for a commercial investment asset management platform, provided as an embodiment of this application. Detailed Implementation

[0025] To further illustrate the technical means and effects adopted by this application to achieve the intended purpose of the invention, the following, in conjunction with the accompanying drawings and preferred embodiments, details the specific implementation, structure, features, and effects of the subsystem data interconnection method applicable to a commercial investment asset management platform proposed in this application. In the following description, different "one embodiment" or "another embodiment" do not necessarily refer to the same embodiment. Furthermore, specific features, structures, or characteristics in one or more embodiments can be combined in any suitable form.

[0026] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains.

[0027] Example of a subsystem data interconnection method applicable to a commercial investment asset management platform:

[0028] The following description, in conjunction with the accompanying drawings, details the specific scheme of the subsystem data interconnection method for a commercial investment asset management platform provided in this application.

[0029] Please see Figure 1 The diagram illustrates a flowchart of a subsystem data interconnection method for a commercial investment asset management platform according to an embodiment of this application. The method includes the following steps:

[0030] Step S001: Collect interaction log data.

[0031] The system collects interaction log data and transmits it through a subsystem. The interaction log data includes transmission data and transmission requirements. In this embodiment, the transmission data includes a system ID identifier, interface protocol type, service version number, average daily call count, service health rating, average response time, timeout rate, requester satisfaction score, and number of error alarms. Transmission requirements include a requirement ID, transmission priority, bandwidth requirements, and timeliness requirements. The requirement ID corresponds to an ID identifier.

[0032] When a data transmission request is initiated, the transmission requirement is obtained through a transmission work order actively submitted by the business system; the interaction log data is saved. After a data interaction is completed, the central data processing system associates this ID with the system's call record and automatically extracts all key fields from the log to update the system performance profile.

[0033] At this point, the interaction log data has been obtained.

[0034] Step S002: Preset the domain, determine the fit based on the number of domains sent, the number of subsystems received, and the number of domain requests, and determine the protocol focus based on the domain fit and the difference in fit across all domains.

[0035] When data is transmitted through the main server, it is allocated to the corresponding service domain based on the bandwidth requirements of the transmitted data according to a preset request performance data classification, thus determining the domain to which the current request belongs. In this embodiment, every 10 Mbps increase in bandwidth requirement is considered a new domain.

[0036] The number of successful transmission requests and the total number of transmission requests sent in each domain are counted, and the ratio of the two is taken as the transmission success rate of each domain; the ratio of the number of concurrent requests in each domain to the rated concurrent number allocated to the domain by the subsystem is taken as the concurrency ratio.

[0037] The adaptability of each domain is obtained based on the transmission success rate and concurrency ratio of each domain.

[0038] The adaptability is positively correlated with the transmission success rate and negatively correlated with the concurrency ratio.

[0039] It should be noted that positive correlation means that when one variable increases, the other variable also increases, and the two variables change in the same direction. When one variable changes from large to small or from small to large, the other variable also changes from large to small or from small to large. The specific relationship is determined by the actual application, and this application does not impose any special restrictions.

[0040] It should be noted that negative correlation means that when one variable increases, the other variable decreases accordingly, and the two variables change in opposite directions. When one variable changes from large to small or from small to large, the other variable also changes from small to large or from large to small. The specific relationship is determined by the actual application, and this application does not impose any special restrictions.

[0041] Preferably, the expression for the fit is:

[0042] , This represents the transmission success rate of domain d. This represents the number of concurrent requests in domain d. This represents the rated number of concurrent connections allocated by subsystem s to domain d. This represents the fit of the domain d.

[0043] When the number of concurrent requests approaches the system's rated concurrency, the result indicates a mismatch between the concurrency level of each domain and the level allocated by the system protocol. This manifests as significant differences in the performance support range allocated to the interface within each domain, leading to poorer efficiency in transmission using the current system interface. Therefore, the higher the ratio of concurrent requests to the rated concurrency, the lower the compatibility between each domain and the system interface; the lower the transmission success rate, the lower the compatibility.

[0044] The adaptability of all domains within the subsystem is sorted in ascending order of concurrent requests to obtain an adaptability sequence. Domains with higher adaptability scores in the sequence have higher focus. The greater the difference in adaptability across domains within the subsystem, the more likely the transmission of each domain within the subsystem is to be abnormal, indicating lower focus. The average adaptability of all domains within the subsystem represents the overall adaptability of the subsystem.

[0045] Therefore, the protocol focus of each domain on the subsystem is obtained based on the ranking of each domain in the fitness sequence and the difference between the fitness of each domain and the fitness of the subsystem as a whole.

[0046] The protocol focus is positively correlated with the ranking of each domain in the fitness sequence and the difference between the fitness of each domain and the fitness of the subsystem as a whole.

[0047] Preferably, the expression for protocol focus is:

[0048] , This represents the fit of the domain d. This represents the average fit across all domains within the subsystem. This represents the index of the domain d in the fitness sequence. This represents the maximum index in the fitness sequence. This represents the protocol focus of domain d on subsystem s.

[0049] The smaller the domain is in the fitness sequence corresponding to the subsystem, the more it helps to improve the system's focus. Conversely, when the domain is abnormal, the system's focus will be disturbed by the domain, thus highlighting that the current ranking result is much smaller than the fitness corresponding to the largest sequence number, thus showing that the stability of each domain in the system begins to decline.

[0050] This provides an understanding of the protocol focus of each domain on the subsystem.

[0051] Step S003: For the protocol focus differential of the subsystem corresponding to the domain, select the high focus subsystem and determine its validity by giving historical transmission count, historical protocol focus, and the number of requests and protocol focus of the high focus subsystem.

[0052] Because some domains have poor compatibility with certain subsystems, it is necessary to screen the subsystems corresponding to different domains.

[0053] Sort the protocol focus of all subsystems that can transmit to neighborhood d at the current time in descending order to obtain a descending sequence of focus for each domain. Perform a first-order difference on the descending sequence of focus to obtain the maximum difference value. The maximum difference value corresponds to two subsystems. The subsystem with the largest protocol focus is taken as the segment point, denoted as the first segment point. The subsystem with the largest protocol focus in the descending sequence of focus is also taken as the segment point, denoted as the second segment point. Based on the two segment points, extract an interval in the descending sequence of focus, denoted as the high focus interval, and denote the subsystems within it as high focus subsystems. This achieves the differentiation of domain adaptability.

[0054] The separation between the focus results exhibited by high-focus subsystems and low-focus subsystems is not significant enough, and the number of high-focus subsystems is relatively small. This reflects the insufficient effectiveness of the subsystems selected for each domain, and the difficulty in identifying a small number of high-focus subsystems as the main transmission systems for that domain. Therefore, by using the dominant focus ratio of high-focus subsystems in the current main transmission systems, similar subsystems are selected for pre-classification of the routing process.

[0055] If a highly focused subsystem has transmitted data from each domain simultaneously more times in its history than the number of requests within each domain, then this subsystem has undertaken more data transmission tasks compared to the domain, and therefore, the subsystem can achieve a more stable data transmission process for each domain. Transmission stability is determined based on the difference between the number of times the highly focused subsystem has transmitted data from each domain simultaneously in its history and the number of requests within each domain. In this embodiment, the ratio of the number of times the highly focused subsystem has transmitted data from each domain simultaneously in its history to the number of requests within each domain is used as the transmission stability.

[0056] For each domain, there are multiple historical transmissions in each subsystem. The transmission history fitness of each domain in each subsystem is determined by comparing the average protocol focus of that domain in the historical transmissions of that subsystem with the maximum protocol focus in the corresponding high focus interval. In this embodiment, the ratio of the average protocol focus of a domain in the historical transmissions of each subsystem to the maximum protocol focus in the corresponding high focus interval is used as the transmission history fitness.

[0057] The effectiveness of highly focused subsystems in each domain is calculated based on transmission history fitness and transmission stability.

[0058] The effectiveness is positively correlated with both transmission history adaptability and transmission stability.

[0059] Preferably, in this embodiment, the expression for validity is:

[0060] , Represents a highly focused subsystem in domain d. Transmission stability, Represents a highly focused subsystem in domain d. Transmission history adaptability Represents a highly focused subsystem in domain d. The effectiveness.

[0061] Iterate through the high-focus subsystems of each domain and calculate the effectiveness of each high-focus subsystem.

[0062] Thus, the effectiveness of each domain in the high-focus subsystem has been obtained.

[0063] Step S004: Determine the first hop transmission node based on validity, determine the priority based on the validity and hop count changes of the high-focus subsystem and the validity and hop count changes of the first hop transmission node, and then complete the data transmission.

[0064] Based on the effectiveness of highly focused subsystems in each domain, transmission nodes are selected, and then routing paths are constructed.

[0065] The highly focused subsystem with the highest effectiveness is selected as the first-hop transmission node. Domain data is then transmitted from the starting transmission point to the first-hop transmission node.

[0066] Next, the priority of the high-focus subsystem needs to be determined to confirm the next-hop transmission node, thus completing the selection of a high-quality data transmission link during the data interconnection process of the system. After transmission to the next-hop transmission node, the previous transmission node is removed from the high-focus interval. That is, when selecting the next-hop transmission node later, the removed transmission node is not considered to avoid data transmission loops.

[0067] The priority of a high-focus subsystem is determined based on the similarity between the effectiveness of each high-focus subsystem and the effectiveness of the first-hop transmission node, as well as the change in the number of hops to the target address after data is transmitted to the high-focus subsystem.

[0068] The priority of a high-focus subsystem is positively correlated with the similarity between the effectiveness of each high-focus subsystem and the effectiveness of the first-hop transmission node, and the change in the number of hops the high-focus subsystem takes to reach the target address before and after data transmission.

[0069] Preferably, in this embodiment, the priority expression is:

[0070] , Represents a highly focused subsystem in domain d. The effectiveness, This indicates the validity of the first-hop transmission node in the domain d. This represents the minimum number of hops from the first-hop transmission node in domain d to the target address. Represents a highly focused subsystem in domain d. Minimum number of hops to the target address Represents a highly focused subsystem in domain d. Priority.

[0071] In this embodiment, This demonstrates the similarity between the effectiveness of each highly focused subsystem and the effectiveness of the first-hop transmission node. and The closer the ratio is to 1, the larger the fraction is, and the greater the similarity of the validity. It represents the change in the number of hops from the previous transmission node to the next transmission node; the larger the ratio, the greater the change.

[0072] Therefore, for each domain, the priority of each high-focus subsystem is obtained, and the high-focus subsystem corresponding to the highest priority is used as the next-hop transmission node until the target address is reached, thereby transmitting data for that domain.

[0073] This completes the interconnection of subsystem data, enabling data to be transmitted through different subsystems.

[0074] It should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

[0075] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments.

Claims

1. A method for interconnecting subsystem data applicable to a commercial investment management platform, characterized in that, The method comprises the following steps: Collecting interaction log data; Predefining fields, distributing the interaction log data into different fields, for any one subsystem, obtaining the adaptation degree of each field based on the ratio of the number of transmission request passes to the total number of transmission requests in each field and the ratio of the number of concurrent requests of each field to the rated concurrent number allocated by the subsystem to the field, obtaining the adaptation degree sequence of all fields in the subsystem by sorting the adaptation degrees of all fields in the subsystem from small to large according to the number of concurrent requests, and obtaining the protocol focus of each field on the subsystem based on the sorting of each field in the adaptation degree sequence and the difference between the adaptation degree of each field and the adaptation degree of the whole subsystem; For any one field, obtaining the descending sequence of the protocol focus of the field on the subsystems that can transmit the field in descending order, performing first-order difference on the descending sequence of the protocol focus, determining the high-focus subsystem according to the maximum value of the protocol focus and the maximum difference value, determining the transmission stability according to the difference between the number of times that the high-focus subsystem transmits data of each field simultaneously in history and the number of requests in each field, comparing the average value of the protocol focus of the field in the historical transmission of the subsystem with the maximum protocol focus of the high-focus subsystem corresponding to the field to determine the transmission history adaptability, and obtaining the effectiveness of the high-focus subsystem in each field according to the transmission stability and the transmission history adaptability; Determining the first-hop transmission node based on the effectiveness, determining the priority of the high-focus subsystem according to the similarity of the effectiveness of each high-focus subsystem and the effectiveness of the first-hop transmission node and the change amount of the hop number after the data transmission to the high-focus subsystem reaches the target address, determining the next-hop transmission node based on the priority, and constructing a data transmission network to complete data transmission.

2. The method for interconnecting subsystem data applicable to a commercial production management platform according to claim 1, wherein, The interaction log data comprises transmission data and transmission demand; the transmission data comprises a system ID identifier, an interface protocol type, a service version number, a daily call frequency, a service health rating, an average response time, a timeout rate, a requestor satisfaction score, and an error alarm number; The transmission demand comprises a demand ID, a transmission priority, a bandwidth demand, and a timeliness demand; the demand ID corresponds to an ID identifier.

3. The method for interconnecting subsystem data applicable to a commercial production management platform according to claim 1, wherein, The adaptation degree is positively correlated with the transmission success rate and negatively correlated with the concurrent proportion; the transmission success rate is the ratio of the number of transmission request passes to the total number of transmission requests in each field; The concurrent proportion is the ratio of the number of concurrent requests of each field to the rated concurrent number allocated by the subsystem to the field.

4. The method for interconnecting subsystem data applicable to a commercial production management platform according to claim 1, wherein, The protocol focus is positively correlated with the sorting of each field in the adaptation degree sequence and the difference between the adaptation degree of each field and the adaptation degree of the whole subsystem.

5. The method for interconnecting subsystem data applicable to a commercial production management platform according to claim 1, wherein, The method for determining the high-focus subsystem according to the maximum value of the protocol focus and the maximum difference value is as follows: The subsystem with the maximum protocol focus in the two subsystems corresponding to the maximum difference value is taken as the first segmentation point; the subsystem with the maximum protocol focus in the descending sequence of the protocol focus is taken as the second segmentation point; the interval between the first segmentation point and the second segmentation point is recorded as the high-focus interval, and the subsystems in the high-focus interval are recorded as the high-focus subsystems.

6. The method for interconnecting subsystem data applicable to a commercial production management platform according to claim 1, wherein, The transmission stability is a ratio of a number of times that each field is simultaneously transmitted by the high-focus subsystem in history to a number of requests in each field.

7. The method for interconnecting subsystem data applicable to a commercial production management platform according to claim 1, wherein, The transmission history fitness is a ratio of an average of protocol focus of the field in the subsystem history transmission to a maximum protocol focus of the high-focus subsystem corresponding to the field.

8. The method for interconnecting subsystem data applicable to a commercial production management platform according to claim 1, wherein, The effectiveness is positively correlated with the transmission history fitness and the transmission stability respectively.

9. The method for interconnecting subsystem data applicable to a commercial production management platform according to claim 1, wherein, The priority is positively correlated with the effectiveness of each high-focus subsystem and the similarity of the effectiveness of the first-hop transmission node, and the change of the hop number from the high-focus subsystem to the target address before and after data transmission.

10. The method for interconnecting subsystem data applicable to a commercial production management platform according to claim 1, wherein, The method for determining the next-hop transmission node based on the priority and constructing the data transmission network to complete data transmission is: The high-focus subsystem corresponding to the maximum priority is taken as the next-hop transmission node; after transmission to the next-hop transmission node, the previous-hop transmission node is deleted from the high-focus interval, and the deleted transmission node is not selected in subsequent selection of the next-hop transmission node; all the next-hop transmission nodes are determined to construct the data network to complete data transmission.

Images