Method and system for sim / esim report consistency check facing mno service entry

Abstract

The application relates to the technical field of Internet of Vehicles communication cards, and discloses a SIM and eSIM bottom layer capability report consistency checking method and system for an MNO customer service entrance, which comprises the following steps: obtaining an MNO customer service entrance operation, establishing cross-system object mapping of MNO and CMP, generating a target evidence set and a prohibited change set, collecting CMP execution, asynchronous report, MNO write-back and TSP notification evidence, performing consistency scoring and abnormal attribution, performing supplementary checking or compensation verification when the evidence is not closed, and finally outputting a report and an access control result. The application solves the problem that the existing single-interface test cannot verify the consistency of entrance success and background capability report, can find defects such as silent failure and object mismatch, automatically locates a fault link, forms an auditable release access control, and improves test efficiency and business reliability.

Description

Technical Field

[0001] This invention relates to the field of vehicle network communication card technology, specifically to a SIM / eSIM consistency verification method and system for MNO service entry. Background Technology

[0002] In IoT applications such as connected vehicles, the service entry point provided by the mobile network operator (MNO) to customers is typically decoupled from the connection management platform (CMP) responsible for managing SIM / eSIM card resources, plans, and lifecycle. When a customer initiates a service operation at the MNO entry point and receives a successful response, it only indicates that the service request has been accepted or entered the processing flow; it does not necessarily equate to the CMP successfully invoking the operator's network interface and completing the corresponding SIM / eSIM underlying capability execution. This disconnect between successful acceptance and successful capability completion is the core challenge currently facing the quality assurance of connected vehicle communication card services.

[0003] Currently, various publicly available technologies and tools exist for system testing and monitoring, but none can effectively solve the aforementioned problem of verifying cross-system business consistency. For example, the eSIM architecture and specifications released by GSMA and related 3GPP standards mainly define the network architecture and interface protocols for eSIM remote configuration and machine-type communication, without addressing how to perform closed-loop verification of the MNO entry point and CMP backend execution results. Common interface testing and monitoring tools, such as contract testing based on OpenAPI, interface monitoring using Postman, stress testing using JMeter, or the pytest testing framework, focus on the correctness of request and response, performance, or test case organization of a single interface. They lack semantic understanding and cross-system association capabilities for key business objects such as Vehicle Identification Number (VIN), eSIM Identifier (EID), Integrated Circuit Card Identifier (ICCID), and Mobile Subscriber Number (MSISDN) in the context of vehicle networking, and therefore cannot identify object mapping errors such as wrong vehicle, wrong card, or wrong plan.

[0004] Therefore, existing technologies have significant shortcomings: First, point-based interface testing cannot verify end-to-end closed-loop consistency across multiple systems, starting from customer business operations; second, general tools lack support for the vehicle network card business object model and asynchronous reporting semantics; and third, there is a lack of a systematic mechanism to automatically correlate evidence scattered across multiple systems, making it impossible to accurately attribute problems such as silent failures. Summary of the Invention

[0005] The purpose of this invention is to provide a SIM / eSIM completion consistency verification method and system for MNO business entry points. This method acquires MNO customer business entry point operations, establishes a cross-system object mapping between MNO and CMP, generates a target evidence set and a prohibited change set, collects evidence from CMP execution, asynchronous completion, MNO write-back, and TSP notification, performs consistency scoring and anomaly attribution, performs supplementary checks or compensation verification when evidence is not closed, and finally outputs a report and access control results. This invention can detect defects such as silent failures and object mismatches, automatically locate faulty links, form an auditable release access control system, improve testing efficiency and business reliability, and solve the problems mentioned in the background technology.

[0006] To achieve the above objectives, the present invention provides the following technical solution: A SIM / eSIM completion consistency verification method for MNO service entry points includes: S1. Capture initial operation requests and their acceptance responses from the customer service entry point of the mobile network operator in real time or asynchronously, and obtain entry evidence containing service order number, service request identifier, and service object identifier; S2. Based on the type of the business operation request, extract at least one of the vehicle identification number (VIN), eSIM identifier (EID), integrated circuit card identifier (ICCID), and mobile subscriber number (MSISDN) as the object key, establish the object association relationship between the MNO side and the connection management platform (CMP) side through the pre-configured mapping rules, and generate the target change object set and the prohibited change object set corresponding to this operation based on this. S3. Based on the target evidence set template pre-configured for different business types, within a preset time window, collect multi-party evidence related to the initial operation request from multiple distributed data sources in read-only mode from the MNO system, CMP platform, operator network interface, message channel and vehicle network service platform; the multi-party evidence covers at least two of the following: connection management platform capability execution evidence, asynchronous completion callback evidence, status write-back and final status evidence, and customer-side perception evidence. S4. Based on the multi-party evidence and the object association, the evidence chain is quantitatively evaluated from five preset dimensions: object consistency, state consistency, event integrity, side effect constraint, and time closure. Among them, object consistency is used to verify whether the state change accurately affects the target changed object set, and side effect constraint is used to determine whether there are non-target object changes in the prohibited changed object set. The comprehensive judgment score of the report consistency is calculated by a weighted summation algorithm, and the score is compared with a preset threshold to output the judgment result of "pass", "warning", "failure" or "isolation". S5. For scenarios where the judgment result is "warning" or "failure", perform compensation operations such as supplementary investigation, replay callback or status re-query according to the abnormal label, transaction number and object key, isolate abnormal samples caused by network jitter or collection delay, and re-execute the quantitative judgment process of step S4 after compensation, and output the review conclusion. S6. Based on the final judgment result and anomaly type, generate an auditable test report containing standardized evidence values ​​and a summary of the original data; at the same time, automatically determine the release conclusion of the access control based on the risk level of the anomaly, and execute release blocking for high-risk anomalies involving customer-visible services not taking effect, incorrect card suspension and resumption, and incorrect package subscription; S7. Return the process data, evidence, and judgment results of each verification to the knowledge base as assets; based on historical data, dynamically optimize the evidence collection strategy, sample selection strategy, and scoring weight for subsequent verifications. The optimization includes: increasing the collection weight of corresponding evidence for test scenarios that repeatedly show anomalies or upgrading them to mandatory evidence; increasing the credibility level of test samples that have passed multiple times and giving them priority; and permanently isolating samples that have failed multiple times due to historical contamination.

[0007] Preferably, in step S3, the specific method for collecting evidence in read-only mode includes one or more combinations of interface query, database read-only query, log retrieval, message consumption record query and callback reception record query.

[0008] Preferably, in step S4, the state consistency dimension is used to compare the MNO order status, the CMP card / package lifecycle status, and the vehicle network service provider notification status to determine whether they are ultimately consistent in business semantics; the event integrity dimension is used to evaluate whether the entire event chain from the CMP execution request initiation to the asynchronous callback reception, and then to the status write-back to the MNO order system is closed.

[0009] Preferably, in step S4, the judgment result is as follows: "Pass" indicates that the core evidence is complete and there are no high-risk anomalies; "Warning" indicates that the non-core evidence is delayed or can be closed by supplementary investigation; "Fail" indicates that the core evidence is missing, the object is mismatched, the state is inconsistent or there are side effects; "Isolation" indicates that the sample or environment has historical contamination and the current result cannot be directly attributed as a business defect.

[0010] Preferably, in step S5, the compensation operation is specifically performed for at least one of the following abnormal scenarios: successful entry but no CMP capability to execute the request, successful CMP execution but no MNO side status write-back, object mismatch, missing notification from the vehicle network service platform, and asynchronous callback timeout.

[0011] Preferably, in step S2, the pre-configured mapping rules are used to determine the associated EID, ICCID, and MSISDN based on the VIN, thereby locating the corresponding SIM / eSIM card file, primary / secondary card relationship, current package, and lifecycle status in the CMP platform.

[0012] Preferably, in step S4, the time closure dimension is used to determine whether the entire process from the initiation of the operation request to the final state consistency is completed within the time window specified in the business service level agreement.

[0013] A SIM / eSIM completion consistency verification system for MNO service entry points includes: The customer entry collection module is configured to collect business operation requests and responses from the customer service entry points of mobile network operators to obtain entry evidence. The object mapping module is configured to establish the association between business objects on the mobile network operator side and the connection management platform side based on entry evidence, and to determine the expected scope of changes; The evidence collection module is configured to collect multi-party evidence related to the business operation from multiple distributed data sources within a preset time window to form an evidence chain; The judgment and scoring module is configured to perform quantitative evaluation from multiple dimensions based on the chain of evidence and the relationship between them, and generate a judgment result on the consistency of the report. The compensation and review module is configured to perform a compensation operation on non-passing judgment results, re-judge the result, and output the review conclusion. The access control module is configured to generate a test report based on the final judgment result and output access control conclusions according to the level of abnormal risk.

[0014] Compared with the prior art, the beneficial effects of the present invention are: 1. This invention starts with customer business operations to perform end-to-end evidence chain tracking and judgment. By capturing entry evidence of mobile network operator business entry points in real time, and intelligently associating business objects on the management platform side based on pre-configured mapping rules, it can accurately define the expected set of target change objects and the set of prohibited change objects for each operation, providing clear semantic targets for subsequent verification. This fundamentally changes the situation where traditional tools lack understanding of business objects and relationships.

[0015] 2. Based on a pre-configured template, this invention actively collects evidence covering the entire chain from multiple distributed data sources such as MNO, CMP, operator networks, and vehicle networking service platforms in a read-only manner. Through a multi-dimensional quantitative scoring model, it automatically evaluates and judges the evidence chain, which can not only identify whether the business is successful or failed, but also finely distinguish intermediate states such as warnings and isolation, and automatically trigger compensation and review for abnormal scenarios. This greatly reduces the false alarm rate caused by network jitter or collection delay, and realizes the localization of problems such as silent failure.

[0016] 3. This invention has the ability to continuously evolve. The process and result data of each verification will be returned to the knowledge base as an asset, driving the system to self-optimize, so that the accuracy, efficiency and adaptability of the entire verification system will continue to improve over time. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the system flow of the present invention. Detailed Implementation

[0018] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0019] To address the potential discrepancy between the visible success result of an operation initiated by a customer from the mobile network operator's service entry point and the actual SIM / eSIM underlying capability result executed by the backend connection management platform in existing vehicle-to-everything (V2X) communication card services, please refer to [link to relevant documentation]. Figure 1 This embodiment provides the following technical solution: The system acquires and parses initial operation requests and responses from mobile network operator customer service portals. These initial operation requests include, but are not limited to, vehicle binding, real-name authentication, package subscription / cancellation / renewal, service suspension / resumption, SIM card replacement, eSIM profile download and activation, and status query. The system comprises a customer portal acquisition module, an object mapping module, an evidence collection module, a judgment and scoring module, a compensation review module, and a report and access control module. The specific operation flow of each module is as follows: I. Customer Entry Data Acquisition Module When a customer initiates an operation request for a vehicle or communication card, the customer entry acquisition module captures the entry evidence of the current operation request in real time or asynchronously. The entry evidence includes, but is not limited to, the business order number or serial number, the business request identifier, the business object identifier, and the acceptance response result returned by the mobile network operator.

[0020] This step serves as an index for subsequent cross-system tracing, providing initial clues for further associations.

[0021] II. Object Mapping Module The object mapping module extracts object keys, including VIN, EID, ICCID, MSISDN, primary / secondary SIM card number, and plan code, based on the business operation type. Through pre-configured mapping rules, it establishes object mappings and associations between the mobile network operator and the connectivity management platform. For example, based on the VIN, it determines the associated eSIM identifier, integrated circuit card identifier, and mobile user number, thereby locating the corresponding SIM / eSIM card file, primary / secondary SIM card relationship, current plan, and lifecycle status on the connectivity management platform. Based on this mapping relationship, it generates the expected set of target change objects for this operation, as well as the set of prohibited change objects that should not be affected, laying the foundation for subsequent accurate verification.

[0022] III. Evidence Collection Module After the mobile operator completes the acceptance and returns a response, the evidence collection module actively and continuously collects evidence from multiple distributed data sources within a preset time window, based on the target evidence set templates pre-configured for different business types.

[0023] The data sources include, but are not limited to, mobile network operators, connection management platforms, operator interfaces, message channels, and vehicle networking service platforms; the evidence collection methods include one or more of the following: interface query, database read-only query, log retrieval, message consumption record query, and callback reception record query, and the read-only method is used to avoid generating additional side effects.

[0024] The evidence collection process covers the following stages: First, there is the evidence of capability execution from the connection management platform, used to verify whether the connection management platform has generated an actual capability call request to the operator's network; second, there is the evidence of asynchronous completion callback, used to capture asynchronous notifications or messages from the mobile network operator or the connection management platform regarding the capability execution result; third, there is the evidence of status write-back and final status, used to verify the record of the connection management platform writing back the execution result to the mobile network operator's order system, and the final status of the business object presented in the mobile network operator's customer query interface and the connection management platform's management interface; and fourth, there is the evidence of customer-side perception, used to confirm whether the vehicle-to-everything (V2X) service provider has received accurate business result notifications.

[0025] IV. Judgment and Scoring Module Once evidence collection is completed or the time window limit is reached, the judgment and scoring module quantitatively evaluates the completeness and consistency of the evidence chain from multiple dimensions based on the evidence set and mapping rules. The comprehensive judgment score of the consistency of the report is calculated through a weighted summation algorithm. The evaluation dimensions include five dimensions: object consistency, state consistency, event completeness, temporal rationality, and time closure. The weight of each dimension is configured according to business risk.

[0026] The evaluation dimensions mainly include: Object consistency is used to verify that all state changes are accurately applied to the target set of changed objects. State consistency is used to compare the order status of mobile network operators, the card / package status of connection management platforms, and the notification status of vehicle network service providers to determine whether they are ultimately consistent in terms of business semantics. Event integrity is used to assess whether the entire asynchronous event chain, from the execution of the request by the connection management platform to the receipt of the callback and the writing back of the status, is closed. Side effect constraint is used to determine whether there are changes to non-target objects in the set of objects that are prohibited from being changed. Time closure is used to determine whether the entire process is completed within the time window specified in the business service level agreement.

[0027] The judgment and scoring module compares the comprehensive judgment score with the preset threshold and outputs the judgment result. The judgment result is divided into "pass", "warning", "failure" and "isolation". "Pass" means that the core evidence is complete and there are no high-risk anomalies; "warning" means that the non-core evidence is delayed or can be closed by supplementary investigation; "failure" means that the core evidence is missing, the object is mismatched, the state is inconsistent or there are side effects; "isolation" means that the sample or environment has historical contamination and the current result cannot be directly attributed to the business defect.

[0028] V. Compensation Review Module For scenarios where the judgment result is a warning or failure, the compensation review module performs supplementary checks, replays, status re-queries, or sample isolation based on the anomaly tag, transaction number, object key, and time window to avoid misjudgments caused by network jitter. For anomalies such as successful entry without connection to the management platform request, successful connection to the management platform without mobile operator write-back, object mismatch, missing notification from the vehicle networking service platform, and asynchronous timeout, corresponding compensation actions are performed, including freezing abnormal samples, replaying callbacks, and isolating contaminated samples. After completion, the module re-verifies and outputs the review conclusion.

[0029] If the compensation operation can obtain the missing evidence and bring the consistency score to the passing standard, the judgment conclusion is revised; if it is confirmed to be a real defect that cannot be compensated, the failure conclusion is retained and the abnormal link is located. The above method can significantly reduce the false alarm rate caused by momentary jitter or acquisition delay.

[0030] VI. Reporting Access Control Module The access control module generates a complete and auditable test report based on the final judgment result and the anomaly type. The report includes standardized evidence values ​​and a summary of the original data, which facilitates personnel to quickly understand the overall process of consistency judgment and to directly trace the original interface and logs for problem localization.

[0031] Meanwhile, the access control module automatically determines the access control conclusion based on the risk level of the anomaly. For high-risk anomalies such as customer-visible services not working, incorrect card suspension or resumption, incorrect package subscription, duplicate charges, or duplicate notifications, the system will be directly blocked from issuing the conclusion. For situations such as missing non-core evidence or temporary unavailability of query interfaces, a warning will be issued and a supplementary investigation will be required within a specified time. For isolated samples, the business will not be directly judged as a failure, but will be transferred to a special sample recovery process for processing.

[0032] Furthermore, the process and results of each verification will be fed back to the knowledge base as assets, serving as important input for subsequent regression testing. When a certain type of anomaly repeatedly occurs during testing, the system will automatically increase the collection weight of the corresponding evidence or upgrade it to mandatory evidence for that business scenario. When a set of test samples consistently passes all verification stages multiple times, its credibility level will be increased, and it will be given priority in subsequent regression testing. When a set of samples fails testing multiple times due to historical contamination, it will be permanently isolated, and targeted environmental recovery suggestions will be output to continuously optimize evidence collection strategies, sample selection strategies, and scoring weights, thereby achieving the evolution and optimization of verification capabilities.

[0033] How it works: When a customer initiates operations such as vehicle binding or plan change at the mobile network operator's service portal, the system captures the request and its successful acceptance response in real time, forming entry evidence containing key information such as the order number and vehicle identification number. Based on this, the system automatically associates the corresponding eSIM card, plan, and other target objects on the connection management platform through pre-defined mapping rules, and clarifies the scope of the expected changes and the set of objects prohibited from being affected by this operation, establishing accurate semantic anchors for subsequent verification.

[0034] The system has entered the stage of automated collection and construction of cross-system evidence chains. Based on different business type templates, within a set time window, it queries and collects full-link evidence from multiple dispersed data sources such as the MNO order system, CMP platform, operator network interface, and vehicle networking service platform. This covers the evidence chain from the CMP initiating capability calls to the network side, to the asynchronous receipt of execution result callbacks, to the writing of business status back to the MNO order, and finally to the customer side being able to query the final status.

[0035] Once evidence collection is complete or the time window limit is reached, the system comprehensively quantifies and scores the evidence chain from five dimensions: object consistency, state consistency, event integrity, side effect constraint, and time closure. After obtaining the comprehensive score through a weighted algorithm, the system will output a pass, warning, failure, or isolation conclusion.

[0036] For warnings or failures, the system triggers a compensation and review mechanism, automatically attempting supplementary checks, replay callbacks, or isolating contaminated samples to eliminate false alarms caused by environmental factors such as network fluctuations. After compensation, a new assessment is performed to confirm whether it is a genuine defect. Finally, all verification processes, evidence, and conclusions are generated into a structured test report. Based on the risk level of the identified defects, the system automatically makes access control decisions to block the release of the report or mark it as a warning, achieving proactive control over business quality.

[0037] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0038] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention.

Claims

1. A SIM / eSIM completion consistency verification method for MNO service entry points, characterized in that, include: Step S1: Collect and parse the initial operation requests and responses from the customer service entry points of the mobile network operator to obtain entry evidence containing service identifiers and service object identifiers; Step S2: Based on the entry evidence, extract the business object key, and establish the object mapping relationship between the MNO side and the connection management platform side according to the pre-configured mapping rules, generating the target change object set and the prohibited change object set; Step S3: Within the preset time window, collect multi-party evidence related to this operation from multiple distributed data sources based on the target evidence set template pre-configured for different business types. Step S4: Based on multiple sources of evidence and object mapping relationships, the integrity and consistency of the evidence chain are quantitatively evaluated from multiple preset dimensions, the comprehensive judgment score of the report consistency is calculated, and the judgment result is output according to the score. Step S5: For scenarios where the judgment result is a warning or failure, perform compensation operations, re-verify, and output the review conclusion; Step S6: Based on the final judgment result and anomaly type, generate a test report containing standardized evidence values ​​and a summary of the original data, and determine the release conclusion of the access control system based on the anomaly risk level.

2. The SIM / eSIM completion consistency verification method for MNO service entry as described in claim 1, characterized in that, In step S4, the preset dimensions include object consistency, state consistency, event integrity, side effect constraint, and time closure. The object consistency is used to verify whether all state changes are accurately applied to the target set of changed objects; The state consistency is used to compare the order status of the mobile network operator, the card / package status of the connection management platform, and the notification status of the vehicle network service provider to determine whether they are ultimately consistent in terms of business semantics. The event integrity is used to assess whether the entire asynchronous event chain, from the execution of the request by the connection management platform to the reception of the callback and the writing back of the status, is closed. The side effect constraint is used to determine whether there are changes to non-target objects in the set of prohibited objects; The time closure is used to determine whether the entire process is completed within the time window specified in the business service level agreement; The overall judgment score is calculated using a weighted summation algorithm based on the scores of each dimension, with the weights of each dimension configured according to business risk.

3. The SIM / eSIM completion consistency verification method for MNO service entry as described in claim 1, characterized in that, In step S3, the distributed data source includes at least an MNO system, a CMP platform, an operator network interface, a message channel, and a vehicle networking service platform; The data collection methods include one or more of the following: interface query, database read-only query, log retrieval, message consumption record query, and callback reception record query.

4. The SIM / eSIM completion consistency verification method for MNO service entry as described in claim 1, characterized in that, In step S3, the collected multi-party evidence covers at least one of the following aspects: CMP capability execution evidence, asynchronous completion callback evidence, status write-back and final status evidence, and client-side perception evidence.

5. The SIM / eSIM completion consistency verification method for MNO service entry as described in claim 1, characterized in that, In step S5, the compensation operation includes performing one or more of the following on the abnormal label, transaction number, object key and time window: supplementary query, replay, status re-query or sample isolation.

6. The SIM / eSIM completion consistency verification method for MNO service entry as described in claim 1, characterized in that, In step S4, the judgment result is divided into pass, warning failure, and isolation. Pass indicates that the core evidence is complete and there are no high-risk anomalies; warning indicates that non-core evidence is delayed or can be closed by supplementary investigation; failure indicates that core evidence is missing, object is mismatched, state is inconsistent or there are side effects; isolation indicates that the sample or environment has historical contamination and the current result cannot be directly attributed as a business defect.

7. The SIM / eSIM completion consistency verification method for MNO service entry as described in claim 1, characterized in that, In step S6, the release of access control conclusions includes: for high-risk anomalies involving customer-visible services not taking effect, incorrect card suspension or resumption, incorrect package subscription, duplicate charges or duplicate notifications, directly blocking the system release; for cases where non-core evidence is missing or the interface is temporarily unavailable, marking it as a warning and requiring a deadline for supplementary investigation and closure; for isolated samples, transferring them to a dedicated sample recovery process.

8. The SIM / eSIM completion consistency verification method for MNO service entry as described in claim 1, characterized in that, In step S2, the service object key includes the vehicle identification number, eSIM identifier, integrated circuit card identifier, mobile user number, primary and secondary card and package code.

9. The SIM / eSIM completion consistency verification method for MNO service entry as described in claim 1, characterized in that, The method also includes step S7: returning the process data, evidence, and judgment results of each verification as assets to the knowledge base; Based on historical data, the evidence collection strategy, sample selection strategy and scoring weights for subsequent verification are dynamically optimized. The optimizations include: increasing the collection weight of corresponding evidence or upgrading it to mandatory evidence for test scenarios that repeatedly show anomalies; increasing the credibility level of test samples that have passed stably multiple times and giving them priority; and permanently isolating samples that have failed multiple times due to historical contamination.

10. A SIM / eSIM completion consistency verification system for MNO service entry points, used to implement the SIM / eSIM completion consistency verification method for MNO service entry points as described in any one of claims 1-9, characterized in that, include: The customer entry collection module is configured to collect business operation requests and responses from the customer service entry points of mobile network operators to obtain entry evidence. The object mapping module is configured to establish the association between business objects on the mobile network operator side and the connection management platform side based on entry evidence, and to determine the expected scope of changes; The evidence collection module is configured to collect multi-party evidence related to the business operation from multiple distributed data sources within a preset time window to form an evidence chain; The judgment and scoring module is configured to perform quantitative evaluation from multiple dimensions based on the chain of evidence and the relationship between them, and generate a judgment result on the consistency of the report. The compensation and review module is configured to perform a compensation operation on non-passing judgment results, re-judge the result, and output the review conclusion. The access control module is configured to generate a test report based on the final judgment result and output access control conclusions according to the level of abnormal risk.

Images