A cloud platform data acquisition and processing intelligent control method

Abstract

This invention relates to the field of cloud platform data processing technology, specifically to an intelligent control method for cloud platform data acquisition and processing, comprising the following steps: S1, receiving the flow record of the target business object, identifying splitting, merging, code changing, or reloading, and generating a form migration result; S2, cutting off the default control inheritance based on the form migration result, generating an inheritance isolation surface; S3, projecting the control request onto the inheritance isolation surface, identifying whether the control qualification before the change is used, generating a qualification mismatch mark or rebuilding the control qualification; S4, executing blocking release or rebuilding release based on the qualification mismatch mark or rebuilt control qualification, and outputting a trusted control result. This invention achieves secure isolation, intelligent reconstruction, and trusted execution of control requests in the automotive film supply chain and aftermarket cloud platform, effectively improving the traceability of business flow, the accuracy of access control, and the overall efficiency of business collaboration.

Description

Technical Field

[0001] This invention relates to the field of cloud platform data processing technology, and in particular to an intelligent control method for cloud platform data acquisition and processing. Background Technology

[0002] With the deepening of digitalization and supply chain collaborative management in the automotive aftermarket, automotive film products are gradually evolving from traditional manual management methods to centralized control via cloud platforms across multiple business stages, including order creation, warehousing and allocation, distribution, store installation, and after-sales service. In actual business operations, automotive film products and their related business objects typically undergo complex processes such as order splitting, work order merging, code switching, carrier unit migration, and after-sales re-application. To achieve efficient collaboration across warehouses, stores, and installation scenarios, existing cloud platforms typically need to uniformly collect, process, and intelligently control the flow status, control permissions, and publishing actions of business objects to ensure business continuity and execution efficiency throughout the entire supply chain.

[0003] However, existing technologies often retain the control qualifications and publishing permissions corresponding to the previous business object when the business object undergoes morphological changes such as splitting, merging, code changing, or reloading. They lack inheritance isolation mechanisms and dynamic qualification reconstruction mechanisms for object morphological migration, which can easily lead to old order permissions, old work order permissions, or historical warranty qualifications being incorrectly inherited to the new business object. This can cause problems such as permission mismatch, unauthorized control, incorrect after-sales publishing, and chaotic business object status. Especially in the automotive film supply chain and aftermarket cloud platform scenarios, if the object flow relationship cannot be accurately identified and the default control inheritance cannot be severed, it will seriously affect business traceability, the accuracy of permission control, and the overall platform's reliable control capabilities. Summary of the Invention

[0004] This invention provides a cloud platform data acquisition and processing intelligent control method that can accurately identify the flow and migration relationship of target business objects when the target business objects undergo morphological changes, cut off the default control inheritance between business objects before and after the change, and perform cross-isolation surface qualification identification and control qualification reconstruction for the control request to be executed, thereby realizing the blocking release or trusted reconstruction release of control requests, and improving the security control capability, business collaboration capability and trusted execution capability of the automotive film supply chain and automotive aftermarket cloud platform in complex business flow scenarios.

[0005] A cloud platform data acquisition and processing intelligent control method includes the following steps: S1, the cloud platform receives the flow record of the target business object, identifies whether the target business object has been split, merged, recoded or reloaded, and if so, generates the form migration result corresponding to the target business object. S2, based on the morphological migration result, the cloud platform cuts off the default control inheritance from the business object before the change to the business object after the change, and generates the inheritance isolation surface corresponding to the target business object; S3, the cloud platform projects the control request to be executed to the inheritance isolation surface, identifies whether the control request to be executed continues to use the control qualification before the change across the inheritance isolation surface. If yes, a qualification mismatch mark is generated; otherwise, a control qualification reconstruction mark is generated. S4, the cloud platform performs blocking release or rebuild release on the control request to be executed based on the qualification mismatch mark or the rebuild control qualification, and outputs the trusted control result corresponding to the target business object.

[0006] Optionally, S1 includes: S11, the cloud platform receives the flow records of the target business object, performs field alignment and format standardization on the object identifier, business code, bearer unit identifier, timestamp and status fields in the flow records to form a unified flow record set, and establishes the association relationship between the preceding object and the following object based on the consistency of object identifier, similarity of business code, consistency of bearer unit and time continuity, and generates an object flow association set; S12, the cloud platform, based on the object flow association set, counts the number of successor objects of the preceding object and the number of predecessor objects of the following object, and, in combination with the changes in business coding and the changes in the bearing unit, identifies whether the target business object has been split, merged, recoded or reloaded, and generates the corresponding form change type. S13, the cloud platform performs structured encapsulation of the object mapping relationship of the target business object before and after the change based on the morphological change type, and generates a morphological migration result including the object set before the change, the object set after the change, and the change type label set.

[0007] Optionally, S11 includes: S111, the cloud platform receives target business object flow records from the order end, warehousing end, delivery end, store end or construction end, extracts the object identifier, business code, carrier unit identifier, timestamp and status fields from the flow records, and performs unified mapping and standardization on the field names, field formats and field missing situations in flow records from different sources to form a unified flow record set; S112, the cloud platform sorts the unified flow record set according to time order, takes the flow record with earlier time as the preceding record and the flow record with later time as the following record, calculates the object identifier consistency, business code similarity, bearing unit consistency and time continuity between the preceding record and the following record respectively, and performs weighted fusion to obtain the corresponding association score; S113, the cloud platform compares the association score with the preset association judgment threshold. When the association score is not less than the association judgment threshold, it determines that there is a valid flow association relationship between the corresponding preceding record and the following record, and writes the corresponding record pair into the object flow association set, thereby generating the object flow association set corresponding to the target business object.

[0008] Optionally, S12 includes: S121, The cloud platform, based on the object flow association set, counts the number of successor objects corresponding to each predecessor object and the number of predecessor objects corresponding to each successor object, and generates object flow quantity features. S122, the cloud platform identifies whether the target business object has been split or merged based on the object flow quantity characteristics. When the same predecessor object corresponds to two or more successor objects, it is determined that the target business object has been split. When the same successor object corresponds to two or more predecessor objects, it is determined that the target business object has been merged. S123, the cloud platform targets each group of associated objects in the object flow association set. The system compares the business codes and bearer unit identifiers of the preceding and succeeding objects respectively. When the business code changes, it is identified as a code change form change. When the bearer unit identifier changes, it is identified as a load change form change. The system also combines the splitting mark, merging mark, code change mark, and load change mark to generate the corresponding form change type.

[0009] Optionally, S2 includes: S21, based on the morphological migration results, the cloud platform extracts the set of business objects before the change, the set of business objects after the change, and the corresponding morphological change types, and constructs the default control inheritance mapping relationship from the business objects before the change to the business objects after the change; S22, the cloud platform blocks the default control inheritance mapping relationship according to the type of morphological change, cuts off the default control inheritance relationship between business object pairs that have undergone splitting, merging, code changing or reloading, and generates a cut-off control inheritance relationship matrix. S23, the cloud platform performs boundary abstraction mapping on the business object pairs whose default control inheritance has been cut off, based on the cut-off control inheritance relationship matrix, and generates the inheritance isolation surface corresponding to the target business object.

[0010] Optionally, S3 includes: S31, the cloud platform receives the control request to be executed, extracts the request object identifier, control action type, qualification source identifier and target control object identifier, and generates the control request projection vector corresponding to the control request to be executed based on the source matching relationship between the qualification source identifier and the business object before the change and the target matching relationship between the target control object identifier and the business object after the change. S32, the cloud platform projects the control request projection vector onto the inheritance isolation surface, and determines whether the control request to be executed hits the object pair whose default control inheritance has been cut off. If it hits, it identifies that the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change. S33, the cloud platform performs traffic splitting based on the cross-identification result. If the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change, a qualification mismatch mark is generated. If the control request to be executed does not cross the inheritance isolation surface and continues to use the control qualification before the change, a reconstructed control qualification is generated based on the current object attributes, current control context and current control rules of the changed business object.

[0011] Optionally, S32 includes: S321, the cloud platform obtains the inheritance isolation surface corresponding to the target business object, and extracts the isolation boundary object pair between the business object before the change and the business object after the change in the inheritance isolation surface; S322, the cloud platform projects the control request to be executed onto the inheritance isolation surface, calculates the projection result on each isolation boundary object pair, and determines whether the control request to be executed crosses the inheritance isolation surface to continue to use the control qualification before the change; S323, the cloud platform calculates the cross-isolation plane qualification retention strength corresponding to the control request to be executed. If the cross-isolation plane qualification retention strength is not less than 1, it is determined that there is at least one qualification retention path that crosses the inherited isolation plane, and thus it is determined that the control request to be executed continues to retain the control qualification before the change across the inherited isolation plane.

[0012] Optionally, S33 includes: S331, the cloud platform reads the result of the cross-judgment and determines whether the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change. When the determination result shows that the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change, a corresponding qualification mismatch flag is generated. S332, when the cloud platform determines that the control request to be executed has not crossed the inheritance isolation surface and continues to use the control qualification before the change, it performs control qualification reconstruction on the control request to be executed according to the changed business object that matches the target control object identifier, the current control action type, and the current control context information, and generates the corresponding reconstructed control qualification.

[0013] Optionally, S4 includes: S41, the cloud platform receives the qualification mismatch flag and the rebuild control qualification corresponding to the control request to be executed, and determines whether the control request to be executed meets the release conditions. When the qualification mismatch flag indicates that the control request to be executed has the behavior of continuing to use the control qualification before the change across the inheritance isolation surface, it is determined that the control request to be executed enters the blocking release path. When no qualification mismatch flag is generated and the rebuild control qualification matching the changed business object has been generated, it is determined that the control request to be executed enters the rebuild release path. S42, the cloud platform executes the corresponding release action for the control request to be executed based on the control release determination result. When the control release determination result indicates that the control request to be executed has entered the blocking release path, a blocking release result is generated and the control request to be executed is prevented from acting on the target business object. When the control release determination result indicates that the control request to be executed has entered the reconstruction release path, a reconstruction release execution result is generated based on the reconstruction control qualification, and the control request to be executed is acted on the target business object with the reconstructed control qualification. S43, the cloud platform performs trusted encapsulation of the release execution result, generates a trusted control result including the target business object identifier, release path type, qualification judgment basis and final control status, and outputs the trusted control result corresponding to the target business object.

[0014] Optionally, S43 includes: S431, the cloud platform receives the output release execution result and extracts the target business object identifier, release path type, qualification judgment basis and final control status corresponding to the control request to be executed; S432, the cloud platform determines the release path type and final control status corresponding to the control request to be executed based on the blocking release result or the rebuilding release result; S433, the cloud platform encapsulates the target business object identifier, publishing path type, qualification judgment basis and final control status in a structured manner, generates the trusted control result corresponding to the control request to be executed, and outputs the trusted control result corresponding to the target business object.

[0015] The beneficial effects of this invention are: This invention utilizes a cloud platform to uniformly receive, standardize, associate, score, and identify the morphological migration records of target business objects across multiple stages, including orders, warehousing, delivery, stores, and construction. It can accurately identify morphological changes of business objects in the automotive film supply chain and aftermarket scenarios, such as splitting, merging, code changing, or reloading, and form a structured mapping relationship between objects before and after the change. This effectively solves the problems of data link breakage, discontinuous status tracking, and business object mismatch caused by changes in object identifiers, code switching, or carrier migration in traditional cloud platforms, significantly improving the traceability, continuity, and data consistency of business objects throughout their entire lifecycle.

[0016] This invention proactively severs the default control inheritance relationship from the pre-change business object to the post-change business object based on the form migration result, constructs an inheritance isolation surface, and then projects the control request to be executed onto the inheritance isolation surface for cross-identification and qualification mismatch judgment. This effectively prevents the erroneous use of old orders, old construction work orders, old warranty certificates, or historical authorization information in scenarios such as object splitting, vehicle replacement, code replacement, and after-sales re-application. It avoids the unconstrained inheritance of control permissions after the form of the business object changes, thereby significantly improving the security, isolation, and permission reliability of the car film supply chain cloud platform in the process of store construction control, after-sales service control, and warranty permission control.

[0017] This invention, by re-executing control qualification reconstruction based on the current business state, bearer unit state, control rule matching results, and control action type of the changed business object without qualification mismatch, and by combining a dual-path control mechanism of blocking release and reconstructing release to output reliable control results, enables intelligent diversion and reliable release of control requests under different business scenarios. This avoids abnormal requests directly affecting the target business object and ensures that legitimate requests can quickly restore control capabilities under the new business state. As a result, it improves the intelligent decision-making capabilities, control accuracy, and overall business execution efficiency of the automotive aftermarket cloud platform in the processes of film installation release, after-sales re-application release, warranty activation, and store collaborative control. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in this invention 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 for this invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a schematic diagram of the control method flow according to an embodiment of the present invention; Figure 2 This is a schematic diagram of the construction of the inheritance isolation surface in an embodiment of the present invention. Detailed Implementation

[0020] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. Those skilled in the art may employ other alternative methods to implement some well-known technologies; moreover, the accompanying drawings are only for more specific description of the embodiments and are not intended to specifically limit the present invention.

[0021] like Figures 1-2 As shown, a cloud platform data acquisition and processing intelligent control method includes the following steps: S1, the cloud platform receives the flow record of the target business object, identifies whether the target business object has been split, merged, recoded or reloaded, and if so, generates the form migration result corresponding to the target business object. S2, based on the form migration results, the cloud platform cuts off the default control inheritance from the business object before the change to the business object after the change, and generates the inheritance isolation surface corresponding to the target business object; S3, the cloud platform projects the control request to be executed to the inheritance isolation surface, identifies whether the control request to be executed continues to use the control qualification before the change across the inheritance isolation surface. If so, a qualification mismatch mark is generated; otherwise, a control qualification reconstruction is generated. S4, the cloud platform performs blocking or re-release of the control request to be executed based on the qualification mismatch mark or rebuild control qualification, and outputs the trusted control result corresponding to the target business object.

[0022] S1 includes: S11, the cloud platform receives the flow records of the target business object, performs field alignment and format standardization on the object identifier, business code, bearer unit identifier, timestamp and status fields in the flow records to form a unified flow record set, and establishes the association relationship between the preceding object and the following object based on the consistency of object identifier, similarity of business code, consistency of bearer unit and time continuity, and generates an object flow association set; S12, the cloud platform, based on the object flow association set, counts the number of successor objects of the preceding object and the number of predecessor objects of the following object, and, in combination with the changes in business coding and the changes in the bearing unit, identifies whether the target business object has been split, merged, recoded or reloaded, and generates the corresponding form change type. S13, based on the morphological change type, the cloud platform structurally encapsulates the object mapping relationship of the target business object before and after the change, generating a morphological migration result including the set of objects before the change, the set of objects after the change, and the set of change type tags, represented as: ; ; in, For the first The form migration results corresponding to each target business object For the collection of objects before the change, For the changed collection of objects, For a set of change type tags, For elements of the form change type, For splitting, For the purpose of merger, To change the code, For load replacement, The value is 0 or 1, which corresponds to the determination result of the change type.

[0023] S11 includes: S111, the cloud platform receives target business object flow records from the order end, warehousing end, delivery end, store end, or construction end. It extracts the object identifier, business code, carrier unit identifier, timestamp, and status fields from the flow records. It then performs unified mapping and standardization on field names, field formats, and missing field conditions from flow records from different sources, forming a unified flow record set, represented as: ; in, To unify the first in the circulation record set One transfer record, For the first The object identifier of the transfer record, For the first The business code of the transfer record, For the first The identifier of the carrying unit of the transfer record. For the first The timestamp of the transfer record For the first The status field of each transfer record; S112, the cloud platform sorts the unified flow record set according to time order, taking the flow records with earlier times as the preceding records and the flow records with later times as the following records. It calculates the consistency of object identifiers, similarity of business codes, consistency of bearer units, and temporal continuity between the preceding and following records, and performs weighted fusion to obtain the corresponding association score, represented as: ; in, For the preceding record With subsequent records Correlation ratings between them Identify consistency functions for objects. For business code similarity, For the consistency function of the carrying unit, It is a time-continuous function. , , , These are the weighting coefficients for object identifier consistency, business code similarity, bearer unit consistency, and time continuity, respectively. ; ; ; in, To identify precisely consistent items for objects, To identify objects with consistent inheritance prefixes, , These are the corresponding weight coefficients. For the identifier of the preceding record object, For identifying subsequent record objects, The length of the longest common prefix of the two. for The length of the string. for The length of the string; ; in, The Levenshtein edit distance between encoded strings. For encoding The length of the characters, For encoding The length of the characters; ; ; ; in, For the exact consistency of the bearing unit, For items with consistent hierarchical affiliation, , These are the corresponding weight coefficients. This represents the number of common level nodes in the hierarchical encoding of the carrier unit. for The number of hierarchical nodes, for The number of hierarchical nodes; ; in, For the preset time window, The time interval between subsequent records and preceding records; S113, the cloud platform compares the association score with a preset association judgment threshold. When the association score is not less than the association judgment threshold, it determines that there is a valid flow association relationship between the corresponding preceding and subsequent records, and writes the corresponding record pair into the object flow association set, thereby generating the object flow association set corresponding to the target business object, represented as follows: ; in, For object flow association sets, The threshold for determining association; ; in, , These are the mean and standard deviation of the association scores for the candidate record pairs corresponding to the current target business object. This is the threshold adjustment coefficient.

[0024] S12 includes: S121, the cloud platform, based on the object flow association set, counts the number of successor objects corresponding to each preceding object and the number of predecessor objects corresponding to each subsequent object, generating object flow quantity characteristics, represented as: ; ; in, For the preceding object The number of successor objects, For elements in the object association matrix, when hour, ,when hour, ; S122, the cloud platform identifies whether a target business object has been split or merged based on the characteristics of the number of object transfers. When the same predecessor object corresponds to two or more successor objects, it is determined that the target business object has been split; when the same successor object corresponds to two or more predecessor objects, it is determined that the target business object has been merged. This is represented as follows: ; ; in, For object The splitting marker, when When, it represents an object When a split occurs, When, it represents an object No split occurred. For object The merge tag, when When, it represents an object When a merger occurs, When, it represents an object No merger occurred; S123, the cloud platform targets each group of associated objects in the object flow association set. The system compares the service codes and bearer unit identifiers of the preceding and succeeding objects. When the service code changes, it is identified as a code replacement change; when the bearer unit identifier changes, it is identified as a load change change. The system then combines the splitting marker, merging marker, code replacement marker, and load change marker to generate the corresponding change type, represented as follows: ; ; ; in, For associated object pairs The code change marker, For associated object pairs The identifier of the carrying unit, For associated object pairs The corresponding set of morphological change types.

[0025] S2 includes: S21, based on the form migration results, the cloud platform extracts the set of business objects before the change, the set of business objects after the change, and the corresponding form change types, and constructs the default control inheritance mapping relationship from the business objects before the change to the business objects after the change, represented as: ; in, For the business object before the change To the changed business object The default control inheritance relationship, This indicates that control eligibility inheritance is allowed by default. This indicates that there is no default inheritance relationship; S22, the cloud platform, based on the type of form change, blocks the default control inheritance mapping relationship, severing the default control inheritance relationship between business object pairs that have undergone splitting, merging, code changing, or reloading, and generating a severed control inheritance relationship matrix, represented as: ; ; in, For the control inheritance relationship matrix after severance, when When this occurs, it indicates that default control privileges have been revoked. At this time, it indicates that control over inheritance is still retained. For business object pairs Inheritance blocking marker, For business object pairs Corresponding morphological change types; S23, based on the severed control inheritance relationship matrix, the cloud platform performs boundary abstraction mapping on the business object pairs whose default control inheritance has been severed, generating the inheritance isolation surface corresponding to the target business object, represented as: ; ; in, For the first The inheritance isolation surface corresponding to each target business object. For business object pairs The isolation strength, when When, it indicates complete isolation, when At that time, it indicated that no quarantine had been implemented.

[0026] S3 includes: S31, the cloud platform receives the control request to be executed, extracts the request object identifier, control action type, qualification source identifier, and target control object identifier, and generates a control request projection vector corresponding to the control request to be executed based on the source matching relationship between the qualification source identifier and the business object before the change, and the target matching relationship between the target control object identifier and the business object after the change, as follows: ; ; ; in, For the first One control request to be executed. For the identifier of the requested object, To control the type of action, For the source of eligibility, Identify the target controlled object. for The control request projection vector corresponding to each control request to be executed. For the control request to be executed, the first The projection components of the modified business object , The number of objects in the changed business object set. For the source of qualification Compared with the business objects before the change The source matching function, Identify the target control object With the changed business object The target matching function; ; ; ; in, For exact source matches, For historical inheritance chain matching items, , These are the defined weight coefficients, For the business object before the change Unique identifier, For the business object before the change The set of historical succession chains, such as ; ; ; ; ; ; ; ; ; ; ; ; in, For precise target matching, For business semantic similarity items, , These are the defined weight coefficients, This serves as a unique identifier for the changed business object. The business characteristic matching score between the target request object and the modified object. To achieve the highest possible matching score, For vehicle VIN matching accuracy. For store workstation matching, For membrane model matching, For exact matches, For similar matching items, , These are the corresponding weight coefficients. For the vehicle identification on the requesting side, For vehicle identification on the target side, The length of the longest common prefix. For VIN standard length, For store matching degree, For workstation matching degree, To request the store number, Store number for the target. To request the workstation number, Assign workstation number to the object. , These are the corresponding weight coefficients. To request the side membrane model, For the object-side membrane model, Edit distance for Levenshtein, To request the model length, The length of the object model; S32, the cloud platform projects the control request projection vector to the inheritance isolation surface, and determines whether the control request to be executed hits the object pair whose default control inheritance has been cut off. If it does, it identifies that the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change. S33, the cloud platform performs traffic splitting based on the cross-identification results. If the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change, a qualification mismatch mark is generated. If the control request to be executed does not cross the inheritance isolation surface and continues to use the control qualification before the change, a reconstructed control qualification is generated based on the current object attributes, current control context and current control rules of the changed business object.

[0027] S32 includes: S321, the cloud platform obtains the inheritance isolation surface corresponding to the target business object, and extracts the isolation boundary object pair between the business object before the change and the business object after the change in the inheritance isolation surface; S322, the cloud platform projects the control request to be executed onto the inheritance isolation surface, calculates the projection result on each pair of isolation boundary objects, and determines whether the control request to be executed should continue to use the control qualification before the change across the inheritance isolation surface, as shown below: ; ; in, For the first The result of the cross-judgment of a pending control request, when When this occurs, it indicates that the control request to be executed crosses the inheritance isolation surface and continues to use the control qualifications before the change. This indicates that the control request to be executed has not crossed the inheritance isolation surface and continues to use the control qualification before the change; S323, the cloud platform calculates the cross-isolation plane qualification retention strength corresponding to the control request to be executed. If the cross-isolation plane qualification retention strength is not less than 1, it is determined that there is at least one qualification retention path across the inherited isolation plane, and thus it is determined that the control request to be executed continues to retain the control qualification before the change across the inherited isolation plane, as expressed as: ; in, For the first The cross-isolation surface qualification retention strength corresponding to each pending control request.

[0028] S33 includes: S331, the cloud platform reads the result of the cross-jurisdictional judgment and determines whether the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change. When the judgment result shows that the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change, a corresponding qualification mismatch flag is generated, which is represented as: ; in, For the first The qualification mismatch flag corresponding to each pending control request. This indicates the generation of a qualification mismatch flag. This indicates that no qualification mismatch flag will be generated; S332, when the cloud platform determines that the control request to be executed does not cross the inheritance isolation surface and continue to use the control qualification before the change, it performs control qualification reconstruction on the control request to be executed based on the changed business object matching the target control object identifier, the current control action type, and the current control context information, and generates the corresponding reconstructed control qualification, represented as: ; in, For the first Reconstruction control eligibility corresponding to each pending control request. To control the eligibility reconstruction function, This includes the set of attributes of the current object and the current control context information corresponding to the changed business object. Rate the current business status. Score the current status of the bearing unit. Scoring is assigned based on the matching of the current control rule. , , , These are the corresponding weight coefficients. For qualification mapping function; ; ; ; ; ; ; ; ; in, For comprehensive qualification scoring, To control the eligibility reconstruction threshold, To meet the number of status fields required for control actions, This represents the total number of status fields. The number of matching items for the carrying unit. For the total load verification item, For the first The result of the rule matching. For the number of rules, This is a function for controlling the mapping of action types. For the first The control action type identifier corresponding to each pending control request; ; in, Based on the threshold, , , These are the corresponding weighting coefficients.

[0029] S4 includes: S41, the cloud platform receives the qualification mismatch flag and the rebuild control qualification corresponding to the control request to be executed. It then determines whether the control request meets the release conditions. If the qualification mismatch flag indicates that the control request to be executed continues to use the control qualification before the change by crossing the inheritance isolation surface, the control request to be executed is determined to enter the blocked release path. If no qualification mismatch flag has been generated and a rebuild control qualification matching the changed business object has been generated, the control request to be executed is determined to enter the rebuild release path, as shown below: ; in, For the first The control release determination result corresponding to each pending control request. This indicates that the release will be blocked. This indicates that the reconstruction has been implemented and released. This indicates that the release will not be executed and the status will remain pending. S42, based on the control release determination result, the cloud platform executes the corresponding release action for the control request to be executed. When the control release determination result indicates that the control request to be executed has entered the blocking release path, a blocking release result is generated, and the control request to be executed is prevented from acting on the target business object. When the control release determination result indicates that the control request to be executed has entered the rebuilding release path, a rebuilding release execution result is generated based on the rebuilding control qualification, and the control request to be executed is applied to the target business object with the rebuilt control qualification, as shown below: ; ; ; in, For the first The blocking publication flag corresponding to each pending control request. This indicates that the release will be blocked. This indicates that the blocking of the release will not be implemented. For the first The rebuild release flag corresponding to each pending control request. This indicates that the reconstruction has been implemented and released. This indicates that the rebuild release will not be executed. For the first The execution results corresponding to each pending control request will be published. This indicates that the release of the results has been blocked. This indicates the results of the reconstruction announcement; S43, the cloud platform performs trusted encapsulation of the release execution results, generates trusted control results including the target business object identifier, release path type, qualification judgment basis and final control status, and outputs the trusted control results corresponding to the target business object.

[0030] S43 includes: S431, the cloud platform receives the output release execution result and extracts the target business object identifier, release path type, qualification judgment basis and final control status corresponding to the control request to be executed; S432, the cloud platform determines the release path type and final control status corresponding to the control request to be executed based on the blocking release result or the rebuild release result, as follows: ; ; in, For the publish path type, To block the release path, To rebuild the release path, For the path to be decided, This is the final control state. For reliable blocking results, To ensure the reliability of the published results, Results not yet published; S433, the cloud platform structurally encapsulates the target business object identifier, publication path type, qualification determination criteria, and final control status, generates a trusted control result corresponding to the control request to be executed, and outputs the trusted control result corresponding to the target business object, represented as: ; ; in, For the first Trusted control results corresponding to each pending control request. Identify the target business object. This serves as the basis for qualification determination.

[0031] This invention encompasses any substitutions, modifications, equivalent methods, and solutions made within the spirit and scope of this invention. To provide the public with a thorough understanding of this invention, specific details are described in detail in the following preferred embodiments; however, those skilled in the art will fully understand the invention even without these details. Furthermore, to avoid unnecessary misunderstanding of the essence of this invention, well-known methods, processes, procedures, components, and circuits are not described in detail.

[0032] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A cloud platform data acquisition and processing intelligent control method, characterized in that, Includes the following steps: S1, the cloud platform receives the flow record of the target business object, identifies whether the target business object has been split, merged, recoded or reloaded, and if so, generates the form migration result corresponding to the target business object. S2, based on the morphological migration result, the cloud platform cuts off the default control inheritance from the business object before the change to the business object after the change, and generates the inheritance isolation surface corresponding to the target business object; S3, the cloud platform projects the control request to be executed to the inheritance isolation surface, identifies whether the control request to be executed continues to use the control qualification before the change across the inheritance isolation surface. If yes, a qualification mismatch mark is generated; otherwise, a control qualification reconstruction mark is generated. S4, the cloud platform performs blocking release or rebuild release on the control request to be executed based on the qualification mismatch mark or the rebuild control qualification, and outputs the trusted control result corresponding to the target business object.

2. The intelligent control method for cloud platform data acquisition and processing according to claim 1, characterized in that, S1 includes: S11, the cloud platform receives the flow records of the target business object, performs field alignment and format standardization on the object identifier, business code, bearer unit identifier, timestamp and status fields in the flow records to form a unified flow record set, and establishes the association relationship between the preceding object and the following object based on the consistency of object identifier, similarity of business code, consistency of bearer unit and time continuity, and generates an object flow association set; S12, the cloud platform, based on the object flow association set, counts the number of successor objects of the preceding object and the number of predecessor objects of the following object, and, in combination with the changes in business coding and the changes in the bearing unit, identifies whether the target business object has been split, merged, recoded or reloaded, and generates the corresponding form change type. S13, the cloud platform performs structured encapsulation of the object mapping relationship of the target business object before and after the change based on the morphological change type, and generates a morphological migration result including the object set before the change, the object set after the change, and the change type label set.

3. The intelligent control method for cloud platform data acquisition and processing according to claim 2, characterized in that, S11 includes: S111, the cloud platform receives target business object flow records from the order end, warehousing end, delivery end, store end or construction end, extracts the object identifier, business code, carrier unit identifier, timestamp and status fields from the flow records, and performs unified mapping and standardization on the field names, field formats and field missing situations in flow records from different sources to form a unified flow record set; S112, the cloud platform sorts the unified flow record set according to time order, takes the flow record with earlier time as the preceding record and the flow record with later time as the following record, calculates the object identifier consistency, business code similarity, bearing unit consistency and time continuity between the preceding record and the following record respectively, and performs weighted fusion to obtain the corresponding association score; S113, the cloud platform compares the association score with the preset association judgment threshold. When the association score is not less than the association judgment threshold, it determines that there is a valid flow association relationship between the corresponding preceding record and the following record, and writes the corresponding record pair into the object flow association set, thereby generating the object flow association set corresponding to the target business object.

4. The intelligent control method for cloud platform data acquisition and processing according to claim 3, characterized in that, S12 includes: S121, The cloud platform, based on the object flow association set, counts the number of successor objects corresponding to each predecessor object and the number of predecessor objects corresponding to each successor object, and generates object flow quantity features. S122, the cloud platform identifies whether the target business object has been split or merged based on the object flow quantity characteristics. When the same predecessor object corresponds to two or more successor objects, it is determined that the target business object has been split. When the same successor object corresponds to two or more predecessor objects, it is determined that the target business object has been merged. S123, the cloud platform targets each group of associated objects in the object flow association set. The system compares the business codes and bearer unit identifiers of the preceding and succeeding objects respectively. When the business code changes, it is identified as a code change form change. When the bearer unit identifier changes, it is identified as a load change form change. The system also combines the splitting mark, merging mark, code change mark, and load change mark to generate the corresponding form change type.

5. The intelligent control method for cloud platform data acquisition and processing according to claim 1, characterized in that, S2 includes: S21, based on the morphological migration results, the cloud platform extracts the set of business objects before the change, the set of business objects after the change, and the corresponding morphological change types, and constructs the default control inheritance mapping relationship from the business objects before the change to the business objects after the change; S22, the cloud platform blocks the default control inheritance mapping relationship according to the type of morphological change, cuts off the default control inheritance relationship between business object pairs that have undergone splitting, merging, code changing or reloading, and generates a cut-off control inheritance relationship matrix. S23, the cloud platform performs boundary abstraction mapping on the business object pairs whose default control inheritance has been cut off, based on the cut-off control inheritance relationship matrix, and generates the inheritance isolation surface corresponding to the target business object.

6. The intelligent control method for cloud platform data acquisition and processing according to claim 1, characterized in that, S3 includes: S31, the cloud platform receives the control request to be executed, extracts the request object identifier, control action type, qualification source identifier and target control object identifier, and generates the control request projection vector corresponding to the control request to be executed based on the source matching relationship between the qualification source identifier and the business object before the change and the target matching relationship between the target control object identifier and the business object after the change. S32, the cloud platform projects the control request projection vector onto the inheritance isolation surface, and determines whether the control request to be executed hits the object pair whose default control inheritance has been cut off. If it hits, it identifies that the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change. S33, the cloud platform performs traffic splitting based on the cross-identification result. If the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change, a qualification mismatch mark is generated. If the control request to be executed does not cross the inheritance isolation surface and continues to use the control qualification before the change, a reconstructed control qualification is generated based on the current object attributes, current control context and current control rules of the changed business object.

7. The intelligent control method for cloud platform data acquisition and processing according to claim 6, characterized in that, S32 includes: S321, The cloud platform obtains the inheritance isolation surface corresponding to the target business object, and extracts the isolation boundary object pair between the business object before the change and the business object after the change in the inheritance isolation surface; S322, the cloud platform projects the control request to be executed onto the inheritance isolation surface, calculates the projection result on each isolation boundary object pair, and determines whether the control request to be executed crosses the inheritance isolation surface to continue to use the control qualification before the change; S323, the cloud platform calculates the cross-isolation plane qualification retention strength corresponding to the control request to be executed. If the cross-isolation plane qualification retention strength is not less than 1, it is determined that there is at least one qualification retention path that crosses the inherited isolation plane, and thus it is determined that the control request to be executed continues to retain the control qualification before the change across the inherited isolation plane.

8. The intelligent control method for cloud platform data acquisition and processing according to claim 7, characterized in that, S33 includes: S331, the cloud platform reads the result of the cross-judgment and determines whether the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change. When the determination result shows that the control request to be executed crosses the inheritance isolation surface and continues to use the control qualification before the change, a corresponding qualification mismatch flag is generated. S332, when the cloud platform determines that the control request to be executed has not crossed the inheritance isolation surface and continues to use the control qualification before the change, it performs control qualification reconstruction on the control request to be executed according to the changed business object that matches the target control object identifier, the current control action type, and the current control context information, and generates the corresponding reconstructed control qualification.

9. The intelligent control method for cloud platform data acquisition and processing according to claim 8, characterized in that, S4 includes: S41, the cloud platform receives the qualification mismatch flag and the rebuild control qualification corresponding to the control request to be executed, and determines whether the control request to be executed meets the release conditions. When the qualification mismatch flag indicates that the control request to be executed has the behavior of continuing to use the control qualification before the change across the inheritance isolation surface, it is determined that the control request to be executed enters the blocking release path. When no qualification mismatch flag is generated and the rebuild control qualification matching the changed business object has been generated, it is determined that the control request to be executed enters the rebuild release path. S42, the cloud platform executes the corresponding release action for the control request to be executed based on the control release determination result. When the control release determination result indicates that the control request to be executed has entered the blocking release path, a blocking release result is generated and the control request to be executed is prevented from acting on the target business object. When the control release determination result indicates that the control request to be executed has entered the reconstruction release path, a reconstruction release execution result is generated based on the reconstruction control qualification, and the control request to be executed is acted on the target business object with the reconstructed control qualification. S43, the cloud platform performs trusted encapsulation of the release execution result, generates a trusted control result including the target business object identifier, release path type, qualification judgment basis and final control status, and outputs the trusted control result corresponding to the target business object.

10. The intelligent control method for cloud platform data acquisition and processing according to claim 9, characterized in that, S43 includes: S431, the cloud platform receives the output release execution result and extracts the target business object identifier, release path type, qualification judgment basis and final control status corresponding to the control request to be executed; S432, the cloud platform determines the release path type and final control status corresponding to the control request to be executed based on the blocking release result or the rebuilding release result; S433, the cloud platform encapsulates the target business object identifier, publishing path type, qualification judgment basis and final control status in a structured manner, generates the trusted control result corresponding to the control request to be executed, and outputs the trusted control result corresponding to the target business object.

Images