A method and system for managing access to aggregated payment information based on permission levels

Abstract

The application relates to the technical field of information security access control, and relates to a permission level-based aggregated payment information access control method and system, which comprises the following steps: confirming a user access terminal, analyzing the user access terminal to obtain a user identifier, a requested access data category, a request timestamp, a terminal IP address, a terminal longitude and a terminal latitude, confirming a static permission level and a field permission attribute based on the user identifier, adjusting the static permission level by using a dynamic risk coefficient to obtain an effective permission level, confirming a minimum permission level based on the requested access data category, monitoring a target access terminal to obtain an updated effective permission level, and if the updated effective permission level is smaller than the minimum permission level, issuing a pre-constructed termination instruction to the target access terminal to obtain a final user terminal and complete the aggregated payment information access control. The application can effectively control the access of aggregated payment information, and further guarantees the data security and stable operation of a payment platform.

Description

Technical Field

[0001] This invention relates to the field of information security access control technology, and in particular to a method and system for managing access to aggregated payment information based on hierarchical permissions. Background Technology

[0002] Aggregated payment is a payment method that integrates multiple third-party payment channels to provide merchants with a unified payment interface and fund settlement services. Due to its advantages such as convenient access, good channel compatibility, and unified reconciliation management, it is widely used in retail, catering, e-commerce and various online and offline transaction scenarios.

[0003] Currently, access control for aggregated payment information mainly relies on access control methods based on unified permissions or simple role division.

[0004] While the methods described above can control access to aggregated payment information, their granularity is relatively coarse, making it difficult to implement refined, differentiated management for personnel at different levels and in different positions, as well as for payment information with varying levels of sensitivity. The relatively fixed permission configurations and lack of flexible hierarchical control mechanisms fail to meet the needs of aggregated payment platforms for secure, accurate, and flexible information access control. Therefore, how to effectively control access to aggregated payment information, thereby ensuring the data security and stable operation of the payment platform, has become an urgent problem to be solved. Summary of the Invention

[0005] This invention provides a method for controlling access to aggregated payment information based on hierarchical access permissions and a computer-readable storage medium. Its main purpose is to effectively control access to aggregated payment information, thereby ensuring the data security and stable operation of the payment platform.

[0006] To achieve the above objectives, the present invention provides a method for access control of aggregated payment information based on hierarchical access permissions, comprising: Once the user access terminal is identified, it is parsed to obtain the user identifier, the type of data requested, the request timestamp, the terminal IP address, the terminal longitude, and the terminal latitude. Static permission levels and field permission attributes are determined based on user identifiers; The dynamic risk coefficient is determined based on the user access point, request timestamp, terminal IP address, terminal longitude, and terminal latitude. The static permission level is adjusted using a dynamic risk coefficient to obtain the effective permission level; Determine the lowest permission level based on the type of data requested for access; Compare the effective permission level with the minimum permission level. If the effective permission level is lower than the minimum permission level, the pre-built access denial information is sent to the user access terminal to obtain the end user terminal. If the effective permission level is greater than or equal to the lowest permission level, the field masking strategy is determined based on the effective permission level and the field permission attribute. Based on the requested data category, payment information is extracted from the pre-built aggregated payment system to obtain the original payment information; The original payment information is anonymized according to the field masking strategy to obtain secure payment information; Secure payment information is used as the target information; The target information is sent to the user access terminal to obtain the target access terminal; Monitor the target access endpoint to obtain the updated and effective permission level; Compare the updated permission level with the minimum permission level. If the updated permission level is greater than or equal to the minimum permission level, then the target access terminal is taken as the end user terminal. If the updated permission level is lower than the minimum permission level, the pre-built termination command will be sent to the target access terminal to obtain the end user terminal and complete the access control of aggregated payment information.

[0007] Optionally, the step of determining the static permission level and field permission attributes based on the user identifier includes: The user identifier is parsed to obtain the role type identifier and the identifier validity verification code. The role type identifier is: system administrator, senior merchant or ordinary merchant. The user identifier is validated using an identifier validity check code to obtain a validation result, which is either valid or invalid. If the validation result is invalid, the preset level zero will be used as the static permission level, and the preset no permission will be used as the field permission attribute. If the verification result is valid, then the role type identifier is checked. If the role type identifier is system administrator, then the preset level three is used as the static permission level, and the preset third permission is used as the field permission attribute. If the role type is identified as a senior merchant, the preset level 2 will be used as the static permission level, and the preset second permission will be used as the field permission attribute. If the role type is identified as a regular merchant, the preset level 1 will be used as the static permission level, and the preset first permission will be used as the field permission attribute.

[0008] Optionally, the step of using the identifier validity check code to verify the legitimacy of the user identifier and obtaining the verification result includes: Remove the identity validity check code from the user identity to obtain the feature string to be verified, which includes multiple characters; Perform the following operation on each of the multiple characters: Based on the character, determine the character value and character sequence number; Calculate the weight value based on the character's numerical value and character sequence number; Summarize the weight values ​​to obtain multiple weight values; The total weight value is determined based on multiple weight values, where the total weight value is the sum of the multiple weight values; The remainder is calculated based on the total weight value and the preset prime modulus, where the remainder is the remainder when the total weight value is divided by the prime modulus. The recalculated check code is determined based on the remainder value and the pre-constructed check character mapping table; Compare the recalculated check code with the identifier validity check code. If the recalculated check code is equal to the identifier validity check code, then the preset valid code is taken as the verification result. Otherwise, the default invalidity will be used as the verification result.

[0009] Optionally, the step of determining the dynamic risk coefficient based on the user access terminal, request timestamp, terminal IP address, terminal longitude, and terminal latitude includes: Extract historical access records from the user's access terminal to obtain a set of historical access records. The set of historical access records includes: multiple historical access times, multiple historical terminal IP addresses, and multiple historical terminal locations. Map the request timestamp to the second of the current day to get the current time; Based on the current time and multiple historical access times in the historical access record set, the most recent access time and the time dimension risk sub-coefficient are identified. Convert the terminal IP address to a binary number and obtain the converted binary string. For each historical terminal IP address in the set of historical access records, perform the following operation: Convert the historical terminal IP address into a binary string of the conversion history. Based on the converted binary string and the historical binary string, consecutive identical digits were identified. Summarize consecutive identical digits to obtain multiple consecutive identical digits; The largest consecutive number of digits is determined based on multiple consecutive identical digits, where the largest consecutive identical digit is the largest consecutive identical digit among multiple consecutive identical digits; Calculate the IP dimension risk sub-coefficient based on the maximum consecutive number of bits; The location dimension risk sub-coefficient is determined based on multiple historical terminal locations in the terminal longitude, terminal latitude, current time, most recent access time, and historical access record set; The dynamic risk coefficient is calculated based on the risk sub-coefficients of the time dimension, IP dimension, and location dimension.

[0010] Optionally, the step of determining the most recent access time and time-dimensional risk sub-coefficient based on the current time and multiple historical access times in the historical access record set includes: For each historical access time in the set of historical access records, perform the following operation: Map the historical access time to the second of the current day to obtain the historical access time; Summarize historical access times to obtain multiple historical access times; Based on multiple historical access times, the historical time mean, historical time standard deviation and most recent access time are determined. The historical time mean is the average of multiple historical access times, and the historical time standard deviation is the standard deviation of multiple historical access times. The time dimension risk sub-coefficient is calculated based on the current time, the historical time mean, and the historical time standard deviation.

[0011] Optionally, the step of determining the location dimension risk sub-coefficient based on multiple historical terminal locations in the terminal longitude, terminal latitude, current time, most recent access time, and historical access record set includes: The most recently accessed historical location is determined based on the current time and multiple historical terminal locations in the historical access record set. The most recently accessed historical location includes historical longitude and historical latitude. Calculate the spatial displacement distance based on the terminal's longitude, latitude, and most recently accessed historical location; The time interval is calculated based on the current time and the most recent access time, where the time interval is equal to the current time minus the most recent access time; The location dimension risk sub-coefficient is calculated based on the time interval and spatial displacement distance, as shown in the following formula:

[0012] in, This represents the risk sub-coefficient based on location dimension. Indicates time interval, This represents the preset feasible movement speed threshold. Indicates spatial displacement distance. This indicates the preset speed steepness coefficient. Indicates An exponential function with base 0. It is a natural constant.

[0013] Optionally, the step of determining the field masking strategy based on the effective permission level and field permission attributes includes: The scope of accessible data is determined based on the effective permission level, wherein the scope of accessible data is: the first scope, the second scope, or the third scope; If the accessible data range is the first range, then the field masking strategy is determined based on the field permission attributes and the pre-built first masking strategy. If the accessible data range is the second range, then the field masking strategy is determined based on the field permission attributes and the pre-built second masking strategy. If the accessible data range is the third range, then the field masking strategy is determined based on the field permission attributes and the pre-built third masking strategy.

[0014] Optionally, monitoring the target access endpoint to obtain the updated and effective permission level includes: Access behavior of the target access terminal is collected according to the preset sampling interval to obtain multiple session operation times and multiple session query field types; Anomaly scores for session behavior were determined based on multiple session operation times and multiple session query field types. Compare the abnormal conversation behavior score with the preset low-risk threshold. If the abnormal session behavior score is less than the low-risk threshold, the effective permission level will be used as the updated effective permission level. If the abnormal conversation behavior score is greater than or equal to the low-risk threshold, then compare the abnormal conversation behavior score with the preset high-risk threshold. If the abnormal session behavior score is less than the high-risk threshold, the effective permission level will be reduced by a preset step size of one level to obtain the updated effective permission level. If the abnormal session behavior score is greater than or equal to the high-risk threshold, then level zero will be used as the level for updating the effective permission.

[0015] Optionally, the step of determining the abnormal session behavior score based on multiple session operation times and multiple session query field types includes: An ordered sequence of operation times is determined based on multiple session operation times; Multiple adjacent time intervals were identified based on the ordered operation time sequence; The mean of adjacent operation time intervals is determined based on multiple adjacent time intervals, where the mean of adjacent operation time intervals is the average of multiple adjacent time intervals; Perform the following operation for each of the multiple session query field types: The field sensitivity value is determined based on the field type of the session query and the pre-built field sensitivity mapping table; Summarize the sensitivity values ​​of the fields to obtain sensitivity values ​​for multiple fields; The average sensitivity value of the session field was determined based on the sensitivity values ​​of multiple fields. The average sensitivity value of the session field is the average of the sensitivity values ​​of multiple fields. The abnormal session behavior score is calculated based on the average time interval between adjacent operations and the average sensitivity of session fields, as shown in the following formula:

[0016] in, Indicates the score for abnormal session behavior. This represents the preset normal operating frequency reference value. This represents the average sensitivity of the session field. This represents the average time interval between adjacent operations.

[0017] To achieve the above objectives, the present invention also provides a hierarchical access control system for aggregated payment information, comprising: The dynamic risk calculation module is used to identify the user access terminal, parse the user access terminal to obtain the user identifier, requested access data category, request timestamp, terminal IP address, terminal longitude and terminal latitude, and determine the static permission level and field permission attributes based on the user identifier. It also determines the dynamic risk coefficient based on the user access terminal, request timestamp, terminal IP address, terminal longitude and terminal latitude. The basic permission confirmation module is used to adjust the static permission level using dynamic risk coefficients to obtain the effective permission level, determine the minimum permission level based on the requested access data category, compare the effective permission level with the minimum permission level, and if the effective permission level is less than the minimum permission level, send the pre-built access denial information to the user access terminal to obtain the end user terminal. The target information delivery module is used to determine the field masking strategy based on the effective permission level and field permission attributes if the effective permission level is greater than or equal to the minimum permission level. It extracts payment information from the pre-built aggregated payment system according to the requested access data category to obtain the original payment information. It performs desensitization processing on the original payment information according to the field masking strategy to obtain secure payment information. The secure payment information is used as target information and delivered to the user access terminal to obtain the target access terminal. The payment information control module is used to monitor the target access terminal, obtain the update effective permission level, compare the update effective permission level with the minimum permission level, and if the update effective permission level is greater than or equal to the minimum permission level, the target access terminal is designated as the end user terminal. If the update effective permission level is less than the minimum permission level, a pre-built termination command is sent to the target access terminal to obtain the end user terminal, thus completing the aggregated payment information access control.

[0018] To address the above problems, the present invention also provides an electronic device, the electronic device comprising: Memory, storing at least one instruction; and The processor executes the instructions stored in the memory to implement the above-described method for managing access to aggregated payment information based on hierarchical permissions.

[0019] To address the aforementioned issues, the present invention also provides a computer-readable storage medium storing at least one instruction, which is executed by a processor in an electronic device to implement the above-described method for managing access to aggregated payment information based on hierarchical permissions.

[0020] To address the problems described in the background art, this invention identifies the user's access terminal, parses the access terminal to obtain the user identifier, requested data type, request timestamp, terminal IP address, terminal longitude, and terminal latitude. This invention identifies the specific device initiating the access and extracts the user's identity information, the type of data required, the access time, and the device's geographical location and network address from that device. This provides the basic input for subsequent permission determination and risk assessment. Furthermore, based on the user identifier, the static permission level and field permission attributes are determined. This invention queries the permission database for the user's preset basic permission level and access permissions for different payment data fields based on the user's unique identifier. The control attributes are determined based on the user access terminal, request timestamp, terminal IP address, terminal longitude, and terminal latitude to establish a dynamic risk coefficient. This embodiment of the invention assesses the potential security risk of the access by comprehensively considering the characteristics of the accessing device, the current request time, the IP address's location, and geographical location information. The dynamic risk coefficient is then used to adjust the static permission level to obtain the effective permission level. This embodiment uses the dynamic risk coefficient as an adjustment factor to modify the static permission level, maintaining or increasing permissions when the risk is low and decreasing permissions when the risk is high, thus obtaining the actual effective permission level for the access. The minimum permission level is determined based on the requested access data category. This embodiment of the invention, through... The system identifies the data category the user needs to access and determines the minimum access permission level required for that category. This minimum access level is used as a threshold to determine if the current user has the right to access the data. The effective permission level is compared to the minimum permission level. If the effective permission level is lower than the minimum permission level, a pre-built access denial message is sent to the user's end. Thus, this embodiment of the invention compares the effective permission level with the minimum permission level required by the data. If the current user's permissions are insufficient to access the requested data, an access denial message is directly returned, terminating the access and preventing unauthorized operations. If the effective permission level is greater than or equal to the minimum permission level, a field masking strategy is determined based on the effective permission level and field permission attributes. For example, when the minimum permission requirements are met, based on the effective permission level and the permission attributes of each field, it is determined which fields should be fully displayed and which fields should be partially masked or completely hidden, forming a specific data anonymization scheme for this access. Payment information is extracted from a pre-built aggregated payment system according to the requested data category to obtain the original payment information. Thus, this embodiment of the invention extracts the corresponding original payment data record from the aggregated payment system's database based on the user's requested data category, containing complete field content, providing a data source for subsequent anonymization processing. The original payment information is then anonymized according to the field masking strategy to obtain secure payment information. Therefore, this embodiment of the invention, based on the established field masking strategy...Sensitive fields in the original payment information are replaced, partially hidden, or masked. The processed result is used as secure payment information, which is then used as the target information. This embodiment of the invention determines the anonymized secure payment information as the returned data for this access, sends the target information to the user access terminal, and obtains the target access terminal. This embodiment of the invention completes the data access response by returning the secure payment information to the user device that initiated the access via the network, while recording the access behavior and monitoring the target access terminal to obtain the updated effective permission level. This embodiment of the invention continuously monitors the subsequent behavior and environmental changes of the target access terminal after obtaining data, recalculates the effective permission level at the current time, determines whether the permission status has changed during the access process, prevents security vulnerabilities caused by expired permission status, and compares the updated effective permission level with the lowest permission level. The invention employs a hierarchical approach: if the updated permission level is greater than or equal to the minimum permission level, the target access endpoint is designated as the end user. This means that the updated permission level is compared with the minimum requirement; if the condition is still met, the current access status is considered secure and controllable, and the target access endpoint is confirmed as the end user, allowing continued access. If the updated permission level is lower than the minimum permission level, a pre-built termination command is sent to the target access endpoint, thus obtaining the end user and completing the access control for aggregated payment information. In essence, this invention, by comparing the updated permission level to the minimum requirement, indicates a change in the access environment or user status, prompting the issuance of a termination command to the target access endpoint to forcibly interrupt access and ensure data security. This completes the access control for the entire process. Therefore, this invention can effectively control access to aggregated payment information, thereby ensuring the data security and stable operation of the payment platform. Attached Figure Description

[0021] Figure 1 This is a flowchart illustrating a method for controlling access to aggregated payment information based on hierarchical permissions, according to an embodiment of the present invention. Figure 2 A functional block diagram of an aggregated payment information access control system based on hierarchical access permissions provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of an electronic device that implements the access control method for aggregated payment information based on hierarchical permissions, according to an embodiment of the present invention.

[0022] Explanation of reference numerals in the attached figures: 10. Electronic device; 11. Processor; 12. Memory; 13. Bus.

[0023] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0024] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0025] This application provides a method for access control of aggregated payment information based on hierarchical access permissions. The executing entity of this method includes, but is not limited to, at least one electronic device that can be configured to execute the method provided in this application, such as a server or a terminal. In other words, the method can be executed by software or hardware installed on a terminal device or a server device, and the software can be a blockchain platform. The server includes, but is not limited to, a single server, a server cluster, a cloud server, or a cloud server cluster.

[0026] Reference Figure 1 The diagram shown is a flowchart illustrating a permission-based hierarchical access control method for aggregated payment information according to an embodiment of the present invention. In this embodiment, the permission-based hierarchical access control method for aggregated payment information includes: S1. Identify the user access terminal, parse the user access terminal to obtain the user identifier, requested data type, request timestamp, terminal IP address, terminal longitude and terminal latitude.

[0027] For example, Xiao Zhang is an employee of an aggregated payment information management company. He needs to control user requests to access aggregated payment information. Therefore, Xiao Zhang identifies the user's access point to facilitate subsequent parsing of the user's access segment, thereby completing the control of aggregated payment information access.

[0028] It should be explained that the user access terminal refers to the device (e.g., mobile phone, computer) used by the user to access aggregated payment information. Parsing the user access terminal means analyzing the user access terminal to obtain a string representing the user type, an identifier representing the type of data the user needs to access, the user access time, the IP address of the user access terminal, the longitude and latitude of the user access terminal. The string representing the user type is the user identifier, the identifier representing the type of data the user needs to access is the requested data category, the user access time is the request timestamp, the IP address of the user access terminal is the terminal IP address, the longitude of the user access terminal is the terminal longitude, and the latitude of the user access terminal is the terminal latitude.

[0029] S2. Determine the static permission level and field permission attributes based on the user identifier.

[0030] Specifically, the step of determining the static permission level and field permission attributes based on the user identifier includes: The user identifier is parsed to obtain the role type identifier and the identifier validity verification code. The role type identifier is: system administrator, senior merchant or ordinary merchant. The user identifier is validated using an identifier validity check code to obtain a validation result, which is either valid or invalid. If the validation result is invalid, the preset level zero will be used as the static permission level, and the preset no permission will be used as the field permission attribute. If the verification result is valid, then the role type identifier is checked. If the role type identifier is system administrator, then the preset level three is used as the static permission level, and the preset third permission is used as the field permission attribute. If the role type is identified as a senior merchant, the preset level 2 will be used as the static permission level, and the preset second permission will be used as the field permission attribute. If the role type is identified as a regular merchant, the preset level 1 will be used as the static permission level, and the preset first permission will be used as the field permission attribute.

[0031] It should be explained that parsing the user identifier means: extracting the string used to distinguish the role type and the string used to verify the validity of the identifier from the string corresponding to the user identifier according to a preset encoding method and a preset field order; then confirming the role type identifier corresponding to the string used to distinguish the role type according to the string used to distinguish the role type and the preset corresponding rules. The role type identifier includes: system administrator, senior merchant, and ordinary merchant. Among them, the system administrator refers to the person who has the highest management authority in the aggregated payment system and can access and manage all data in the system; the senior merchant refers to the merchant who needs to manage multiple sub-merchants, and the sub-merchant can refer to a second-level company; the ordinary merchant refers to the merchant who only needs to manage one merchant. The string used to distinguish the role type is the role type identifier, and the string used to verify the validity of the identifier is the validity verification code. It is understood that the preset encoding method, the preset field order, and the preset corresponding rules are all set during the development of the aggregated payment system. For example, if the user identifier format set during the development of the aggregated payment system is: role code (2 digits) + subject serial number (8 digits) + time code (6 digits) + check code (2 digits), for example: an 18-digit identifier 100000004220230157, where the first two digits 10 are the role type identifier (10=system administrator, 20=advanced merchant, 30=ordinary merchant), the middle 00000042 is the subject serial number, 202301 is the time code, and the last two digits 57 are the check code. The role code is a string used to reflect the role type, the subject serial number refers to the serial number assigned to the user access terminal during registration, the time code is a string used to identify the time of the user access terminal during registration, and the check code is a string used to verify the validity of the identifier. For a detailed explanation of the aggregated payment system, please refer to the following embodiments.

[0032] Understandably, Level 0 refers to a level with no access permissions, and "no permission" means that all fields are masked. Level 3 refers to a level where all data in the aggregated payment system can be accessed. Third-level permission means that all data in the aggregated payment system is displayed in plaintext. Level 2 refers to a level where data from multiple sub-merchants can be accessed, and second-level permission means that only data from multiple sub-merchants is displayed in plaintext. Level 1 refers to a level where only data from one merchant can be accessed, and first-level permission means that only data from one merchant is displayed in plaintext. For a detailed explanation of the aggregated payment system, please refer to the following embodiments.

[0033] In detail, the step of using an identifier validity check code to verify the legitimacy of the user identifier and obtaining the verification result includes: Remove the identity validity check code from the user identity to obtain the feature string to be verified, which includes multiple characters; Perform the following operation on each of the multiple characters: Based on the character, determine the character value and character sequence number; The weight value is calculated based on the character's numerical value and character sequence number, using the following formula:

[0034] in, Indicates the weight value. Represents a character value. Indicates character sequence number. This represents the modulo operation; Summarize the weight values ​​to obtain multiple weight values; The total weight value is determined based on multiple weight values, where the total weight value is the sum of the multiple weight values; The remainder is calculated based on the total weight value and the preset prime modulus, where the remainder is the remainder when the total weight value is divided by the prime modulus. The recalculated check code is determined based on the remainder value and the pre-constructed check character mapping table; Compare the recalculated check code with the identifier validity check code. If the recalculated check code is equal to the identifier validity check code, then the preset valid code is taken as the verification result. Otherwise, the default invalidity will be used as the verification result.

[0035] For example, if the user identifier is 100000004220230157 and the identifier validity check code is 57, then after removing the identifier validity check code from the user identifier, the resulting feature string to be verified is 1000000042202301, which consists of multiple characters: 1, 0, 0, 0, 0, 0, 0, 4, 2, 2, 0, 2, 3, 0, 1.

[0036] It should be explained that the character value refers to the numerical value of the character, and the character sequence number refers to the sequence number of the character in the feature string to be verified. For example, if the feature string to be verified is 1000000042202301, and the multiple characters are: 1, 0, 0, 0, 0, 0, 0, 4, 2, 2, 0, 2, 3, 0, 1, then the character value of the character 4 is 4, and the character sequence number is 9.

[0037] It is understandable that the weight value refers to the value calculated after weighting the character values. The recalculated check code refers to the check code corresponding to the remainder value in the check character mapping table. The check code is the string recorded in the check character mapping table corresponding to the remainder value. Furthermore, the check character mapping table is a character mapping table set during the development of the aggregated payment system, and it includes multiple remainder values ​​and the strings corresponding to those remainder values. "Valid" means the user identifier passes verification, and "invalid" means the user identifier fails verification. The prime number modulus is equal to the modulo coefficient in the weight value calculation formula. In this embodiment of the invention, the modulo coefficient in the weight calculation formula is set to 11, which is a well-known fact in the field of check code design that conforms to international standards (ISO7064) and national standards (GB11643).

[0038] S3. Based on the user access terminal, request timestamp, terminal IP address, terminal longitude and terminal latitude, determine the dynamic risk coefficient, and use the dynamic risk coefficient to adjust the static permission level to obtain the effective permission level.

[0039] It should be explained that adjusting the static permission level using a dynamic risk coefficient to obtain the effective permission level means: first, determining the downgrade step size based on the dynamic risk coefficient according to a preset risk range step size rule; then, downgrading the static permission level according to the downgrade step size to obtain the effective permission level. The risk range step size rule is as follows: 0 ≤ dynamic risk coefficient < 0.3, then downgrade step size = 0; 0.3 ≤ dynamic risk coefficient < 0.7, then downgrade step size = 1; 0.7 ≤ dynamic risk coefficient ≤ 1.0, then downgrade step size = 2. Specifically, the determination of the dynamic risk coefficient based on the user access terminal, request timestamp, terminal IP address, terminal longitude, and terminal latitude includes: Extract historical access records from the user's access terminal to obtain a set of historical access records. The set of historical access records includes: multiple historical access times, multiple historical terminal IP addresses, and multiple historical terminal locations. Map the request timestamp to the second of the current day to get the current time; Based on the current time and multiple historical access times in the historical access record set, the most recent access time and the time dimension risk sub-coefficient are identified. Convert the terminal IP address to a binary number and obtain the converted binary string. For each historical terminal IP address in the set of historical access records, perform the following operation: Convert the historical terminal IP address into a binary string of the conversion history. Based on the converted binary string and the historical binary string, consecutive identical digits were identified. Summarize consecutive identical digits to obtain multiple consecutive identical digits; The largest consecutive number of digits is determined based on multiple consecutive identical digits, where the largest consecutive identical digit is the largest consecutive identical digit among multiple consecutive identical digits; The risk sub-coefficient for the IP dimension is calculated based on the maximum number of consecutive bits, as shown in the following formula:

[0040] in, This represents the risk sub-coefficient of the IP dimension. Indicates the maximum number of consecutive digits. This indicates the preset prefix sensitivity index; The location dimension risk sub-coefficient is determined based on multiple historical terminal locations in the terminal longitude, terminal latitude, current time, most recent access time, and historical access record set; The dynamic risk coefficient is calculated based on the time-dimensional risk sub-coefficient, the IP-dimensional risk sub-coefficient, and the location-dimensional risk sub-coefficient. The calculation formula is shown below:

[0041] in, Indicates the dynamic risk coefficient. This represents the risk sub-coefficient over the time dimension. This represents the risk sub-coefficient based on location dimension. Indicates the weight of the time dimension. Indicates the IP dimension weight. This indicates the weight of the location dimension.

[0042] It should be explained that the extraction of historical access records for user access terminals refers to: extracting from the operation logs of the aggregated payment system the times when multiple user access terminals accessed the aggregated payment system in history, the IP addresses of multiple user access terminals in history, and the geographical locations of multiple user access terminals in history. The times when multiple user access terminals accessed the aggregated payment system in history are multiple historical access times, the IP addresses of multiple user access terminals in history are multiple historical terminal IP addresses, and the geographical locations of multiple user access terminals in history are multiple historical terminal locations. The set of historical access records is a set composed of multiple historical access times, multiple historical terminal IP addresses, and multiple historical terminal locations.

[0043] It is understood that mapping the request timestamp to the current day and second means representing the request timestamp in the form of hours, minutes, and seconds. For example, if the request timestamp is 1784297298, then mapping the request timestamp to the current day and second will give the current time as 2026-07-17-22:08:18. Converting the terminal IP address to a binary representation means converting the terminal IP address to binary representation. The converted binary string is the terminal IP address after the binary conversion. For example, if the terminal IP address is 117.61.212.44, then the converted binary string after the binary conversion is 01110101.00111101.11010100.00101100.

[0044] It should be understood that the method for converting the historical terminal IP address to a binary string is the same as the method for converting the terminal IP address to a binary string, and will not be repeated here. The number of consecutive identical digits refers to the number of consecutive numbers that are identical from left to right in both the converted binary string and the historical binary string. For example, if the converted binary string is 01110101.00111101.11010100.00101100, and the historical binary string is 01110101.01111101.11010100.00101100, then the number of consecutive identical digits is 9. It should be noted that when counting the number of consecutive identical digits from left to right in both the converted binary string and the historical binary string, only the numerical value is considered, and the period (.) is not considered.

[0045] Understandably, the IP-dimensional risk sub-coefficient reflects the degree of difference between the current user's IP address and its historical IP address. A higher IP-dimensional risk sub-coefficient indicates a greater difference between the current and historical IP addresses, making the current user more susceptible to risks such as account theft. The prefix sensitivity index is a parameter used to adjust the impact of changes in the maximum number of consecutive bits on the IP-dimensional risk sub-coefficient. It can be set according to the security requirements of the aggregated payment system. If the system has high security requirements, the prefix sensitivity index can be set to a larger value, such as 2; if the system has medium security requirements, it can be set to a medium value, such as 1.4; and if the system has low security requirements, it can be set to a smaller value, such as 1. The dynamic risk coefficient reflects the likelihood of hidden risks on the user's end; a higher dynamic risk coefficient indicates a greater likelihood of hidden risks on the user's end. The weights for the time dimension, IP dimension, and location dimension are all manually set by the staff of the aggregated payment information management company. Optionally, the weight for the time dimension is 0.3, the weight for the IP dimension is 0.3, and the weight for the location dimension is 0.4. It should be noted that when calculating the dynamic risk coefficient, only the numerical values ​​of each parameter are substituted for calculation, and their dimensions are not considered.

[0046] Specifically, the process of determining the most recent access time and time-dimensional risk sub-coefficient based on the current time and multiple historical access times in the historical access record set includes: For each historical access time in the set of historical access records, perform the following operation: Map the historical access time to the second of the current day to obtain the historical access time; Summarize historical access times to obtain multiple historical access times; Based on multiple historical access times, the historical time mean, historical time standard deviation and most recent access time are determined. The historical time mean is the average of multiple historical access times, and the historical time standard deviation is the standard deviation of multiple historical access times. The time-dimensional risk sub-coefficient is calculated based on the current time, the historical mean, and the historical standard deviation, using the following formula:

[0047] in, This represents the risk sub-coefficient over the time dimension. Indicates the current time value. This represents the average value at historical moments. Indicates the standard deviation at a historical moment. This represents the preset zero-smoothing constant. Indicates An exponential function with base 0. It is a natural constant.

[0048] It should be understood that the method of mapping historical access time to the second of the current day to obtain the historical access time is the same as the method of mapping the request timestamp to the second of the current day to obtain the current time, and will not be described again here.

[0049] It should be explained that the most recent access time refers to the historical access time closest to the current time among multiple historical access times. The time dimension risk sub-coefficient reflects the degree of difference between the user's current access time and historical access times. The larger the time dimension risk sub-coefficient, the greater the difference between the user's current access time and historical access time, and the more likely the user's access time is to be at risk of account theft. The zero-smoothing constant is a constant used to prevent division by zero in the denominator. Optionally, the zero-smoothing constant is 0.001, and the unit of the zero-smoothing constant is consistent with the standard deviation of historical times.

[0050] Specifically, the step of determining the location dimension risk sub-coefficient based on multiple historical terminal locations from the terminal longitude, terminal latitude, current time, most recent access time, and historical access record set includes: The most recently accessed historical location is determined based on the current time and multiple historical terminal locations in the historical access record set. The most recently accessed historical location includes historical longitude and historical latitude. The spatial displacement distance is calculated based on the terminal's longitude, latitude, and most recently accessed historical location. The calculation formula is as follows:

[0051] in, Indicates spatial displacement distance. This represents the preset average radius of the Earth. This indicates the historical latitude within the recently visited historical location. This indicates the historical longitude of the most recently visited location. Indicates the terminal latitude. Indicates the terminal longitude. Represents the arcsine function; The time interval is calculated based on the current time and the most recent access time, where the time interval is equal to the current time minus the most recent access time; The location dimension risk sub-coefficient is calculated based on the time interval and spatial displacement distance, as shown in the following formula:

[0052] in, This represents the risk sub-coefficient based on location dimension. Indicates time interval, This represents the preset feasible movement speed threshold. Indicates spatial displacement distance. This indicates the preset speed steepness coefficient. Indicates An exponential function with base 0. It is a natural constant.

[0053] It should be explained that the most recently accessed historical location refers to the historical terminal location corresponding to the most recent access time among multiple historical terminal locations. This historical terminal location includes both historical longitude and historical latitude. Historical longitude refers to the longitude of the user's access terminal at the most recent access time, and historical latitude refers to the latitude of the user's access terminal at the most recent access time. Spatial displacement distance refers to the distance between the most recently accessed historical location and the current location of the user's access terminal. The greater the spatial displacement distance, the greater the distance between the most recently accessed historical location and the current location of the user's access terminal, and the more distance the user's access terminal has moved. Based on common knowledge, the average radius of the Earth is 6371 kilometers.

[0054] Understandably, the location-dimensional risk sub-coefficient reflects the degree of difference between the current location of the user's access terminal and the location of the user's access terminal at the most recent access time. The larger the location-dimensional risk sub-coefficient, the greater the degree of difference between the current location of the user's access terminal and the location of the user's access terminal at the most recent access time, and the greater the risk of account theft. It should be noted that when calculating the location-dimensional risk sub-coefficient, only the numerical values ​​of each parameter are substituted for calculation, and their dimensions are not considered.

[0055] It should be understood that the feasible movement speed threshold reflects the reasonable maximum movement rate under normal conditions. It can be set according to the user's application scenario. For example, if the user's application scenario is a fixed location, the feasible movement speed threshold can be set to a smaller value, such as 2. If the user's application scenario is regular urban commuting, the feasible movement speed threshold can be set to a medium value, such as 70. If the user's application scenario is intercity transportation, the feasible movement speed threshold can be set to a larger value, such as 200. The speed steepness coefficient is a parameter used to adjust the impact of spatial location anomalies on the location dimension risk sub-coefficient. It can be set according to the security requirements of the aggregated payment system. If the aggregated payment system has high security requirements, the prefix sensitivity index can be set to a larger value, such as 1.5. If the aggregated payment system has medium security requirements, the prefix sensitivity index can be set to a medium value, such as 0.8. If the aggregated payment system has low security requirements, the prefix sensitivity index can be set to a smaller value, such as 0.2.

[0056] S4. Based on the requested data category, determine the minimum permission level. Compare the effective permission level with the minimum permission level. If the effective permission level is lower than the minimum permission level, send the pre-built access denial information to the user's access end to obtain the final user information. If the effective permission level is greater than or equal to the minimum permission level, determine the field masking strategy based on the effective permission level and field permission attributes.

[0057] It should be explained that the lowest permission level refers to the lowest level of access allowed for the requested data category. For example, if the requested data category is all data in the system, the lowest level is level three; if the requested data category is data from multiple sub-merchants, the lowest level is level two; and if the requested data category is data from a single merchant, the lowest level is level one. The end-user terminal refers to the user terminal that receives the access denied information. The access denied information is used to inform the user terminal that it does not have permission to access the requested data category.

[0058] Specifically, the process of determining the field masking strategy based on the effective permission level and field permission attributes includes: The scope of accessible data is determined based on the effective permission level, wherein the scope of accessible data is: the first scope, the second scope, or the third scope; If the accessible data range is the first range, then the field masking strategy is determined based on the field permission attributes and the pre-built first masking strategy. If the accessible data range is the second range, then the field masking strategy is determined based on the field permission attributes and the pre-built second masking strategy. If the accessible data range is the third range, then the field masking strategy is determined based on the field permission attributes and the pre-built third masking strategy.

[0059] It should be explained that the scope of accessible data refers to the range of data in the aggregated payment system that can be accessed by the effective permission level, and the scope of accessible data can be a first scope, a second scope, or a third scope. The first scope refers to the data of one merchant in the aggregated payment system, the second scope refers to the data of multiple sub-merchants in the aggregated payment system, and the third scope refers to all data in the aggregated payment system.

[0060] Understandably, a field masking strategy refers to a strategy that processes payment data limited by field permission attributes using a first masking strategy when the accessible data range is a first range; a strategy that processes payment data limited by field permission attributes using a second masking strategy when the accessible data range is a second range; or a strategy that processes payment data limited by field permission attributes using a third masking strategy when the accessible data range is a third range. The first masking strategy involves displaying low-sensitivity fields in plaintext within the data within the first range, partially masking medium-sensitivity fields within the data within the first range, and completely masking high-sensitivity fields within the data within the first range, as well as data outside the first range in the aggregated payment system. The second masking strategy involves displaying low-sensitivity fields in plaintext within the data within the second range, partially masking medium-sensitivity fields within the data within the second range, and completely masking high-sensitivity fields within the data within the second range, as well as data outside the second range in the aggregated payment system. The third masking strategy involves displaying all fields in plaintext within the data of the aggregated payment system. The low-sensitivity fields refer to the transaction serial number, transaction time, merchant name, and transaction status; the medium-sensitivity fields refer to the transaction amount, receiving account, and user name; and the high-sensitivity fields refer to the bank card number, ID card number, and complete mobile phone number.

[0061] It should be understood that partial masking refers to retaining only the first and last preset number of characters (e.g., 4 characters) of the field, replacing the middle part with the masking symbol. For example, if the bank card number is 6222031502645789, partial masking results in 6222********5789. Complete masking refers to replacing all characters in the field with a preset masking symbol (e.g., *), making the value of the field completely unreadable. Plain text display refers to displaying the value of the field completely without any masking. The masking process includes both complete and partial masking.

[0062] S5. Extract payment information from the pre-built aggregated payment system according to the requested data category to obtain the original payment information. Perform desensitization processing on the original payment information according to the field masking strategy to obtain secure payment information.

[0063] It should be explained that extracting payment information from the pre-built aggregated payment system based on the requested access data category means extracting data related to the requested access data category from the database of the aggregated payment system. The data related to the requested access data category is the original payment information. The aggregated payment system refers to a system that integrates multiple payment channels such as WeChat Pay, Alipay, and UnionPay QuickPass. In this embodiment, the database of the aggregated payment system stores payment information such as transaction records, settlement records, and refund details for each user.

[0064] It is understood that the process of desensitizing the original payment information according to the field masking strategy refers to the process of masking the fields in the original payment information according to the field masking strategy, and the secure payment information refers to the original payment information after the desensitization process.

[0065] S6. Use secure payment information as target information, send the target information to the user access terminal, obtain the target access terminal, monitor the target access terminal, and obtain the updated and effective permission level.

[0066] It should be explained that the target access terminal refers to the user access terminal that receives the target information.

[0067] In detail, the monitoring of the target access terminal to obtain the updated and effective permission level includes: Access behavior of the target access terminal is collected according to the preset sampling interval to obtain multiple session operation times and multiple session query field types; Anomaly scores for session behavior were determined based on multiple session operation times and multiple session query field types. Compare the abnormal conversation behavior score with the preset low-risk threshold. If the abnormal session behavior score is less than the low-risk threshold, the effective permission level will be used as the updated effective permission level. If the abnormal conversation behavior score is greater than or equal to the low-risk threshold, then compare the abnormal conversation behavior score with the preset high-risk threshold. If the abnormal session behavior score is less than the high-risk threshold, the effective permission level will be reduced by a preset step size of one level to obtain the updated effective permission level. If the abnormal session behavior score is greater than or equal to the high-risk threshold, then level zero will be used as the level for updating the effective permission.

[0068] It should be explained that the collection of access behavior data from the target access terminal according to the preset sampling interval means that at each sampling interval, the time when the target access terminal accesses data and the type of the data field queried by the target access terminal are collected. The time when the target access terminal accesses data is the session operation time, and the type of the data field queried by the target access terminal is the session query field type. Optionally, the sampling interval is 2 seconds.

[0069] Understandably, the low-risk threshold is a value manually set by the staff of the aggregated payment information management company based on the minimum abnormal session behavior score of users who have historically accessed securely. For example, if the minimum abnormal session behavior score of users who have historically accessed securely is 20, then the low-risk threshold is 20. The high-risk threshold is a value manually set by the staff of the aggregated payment information management company based on the minimum abnormal session behavior score of users who have historically accessed abnormally. For example, if the minimum abnormal session behavior score of users who have historically accessed abnormally is 70, then the high-risk threshold is 70. The first-level step size is the step size used to downgrade the effective permission level. Optionally, the first-level step size is 1 level.

[0070] Specifically, the process of determining abnormal session behavior scores based on multiple session operation times and multiple session query field types includes: An ordered sequence of operation times is determined based on multiple session operation times; Multiple adjacent time intervals were identified based on the ordered operation time sequence; The mean of adjacent operation time intervals is determined based on multiple adjacent time intervals, where the mean of adjacent operation time intervals is the average of multiple adjacent time intervals; Perform the following operation for each of the multiple session query field types: The field sensitivity value is determined based on the field type of the session query and the pre-built field sensitivity mapping table; Summarize the sensitivity values ​​of the fields to obtain sensitivity values ​​for multiple fields; The average sensitivity value of the session field was determined based on the sensitivity values ​​of multiple fields. The average sensitivity value of the session field is the average of the sensitivity values ​​of multiple fields. The abnormal session behavior score is calculated based on the average time interval between adjacent operations and the average sensitivity of session fields, as shown in the following formula:

[0071] in, Indicates the score for abnormal session behavior. This represents the preset normal operating frequency reference value. This represents the average sensitivity of the session field. This represents the average time interval between adjacent operations.

[0072] It should be explained that the ordered operation time sequence refers to the sequence obtained by arranging multiple session operation times in chronological order. The determination of multiple adjacent time intervals based on the ordered operation time sequence means: taking the difference between two adjacent session operation times in the ordered operation time sequence in turn to obtain the difference value, and using the difference value as the adjacent time interval, and finally obtaining multiple adjacent time intervals. The taking the difference refers to the process of calculating the absolute difference between two adjacent session operation times in the ordered operation time sequence.

[0073] Understandably, the field sensitivity value refers to the numerical value corresponding to the session query field type in the field sensitivity mapping table. This field sensitivity mapping table is a pre-constructed table that includes multiple session query field types and their corresponding sensitivity values. The session behavior anomaly score reflects the degree of anomaly when the target accessing the data. The higher the score, the higher the degree of anomaly, and the greater the potential risk of account theft. The normal operation frequency benchmark value refers to the frequency of data access in the aggregated payment system under normal circumstances. Optionally, the normal operation frequency benchmark value is 0.5, meaning data is accessed once every two seconds. Optionally, if anomalies are detected during access by the target accessing the system, other verification methods can be used to ensure the normal use of the target accessing device.

[0074] S7. Compare the update effective permission level with the minimum permission level. If the update effective permission level is greater than or equal to the minimum permission level, the target access terminal is taken as the end user terminal. If the update effective permission level is less than the minimum permission level, the pre-built termination instruction is sent to the target access terminal to obtain the end user terminal, thus completing the access control of aggregated payment information.

[0075] It should be explained that the termination instruction refers to an instruction that prohibits users from accessing data in the aggregated payment system.

[0076] For example, once the end-user terminal is obtained, Xiao Zhang can monitor the subsequent behavior of the end-user terminal and ultimately complete the access control of aggregated payment information.

[0077] To address the problems described in the background art, this invention identifies the user's access terminal, parses the access terminal to obtain the user identifier, requested data type, request timestamp, terminal IP address, terminal longitude, and terminal latitude. This invention identifies the specific device initiating the access and extracts the user's identity information, the type of data required, the access time, and the device's geographical location and network address from that device. This provides the basic input for subsequent permission determination and risk assessment. Furthermore, based on the user identifier, the static permission level and field permission attributes are determined. This invention queries the permission database for the user's preset basic permission level and access permissions for different payment data fields based on the user's unique identifier. The control attributes are determined based on the user access terminal, request timestamp, terminal IP address, terminal longitude, and terminal latitude to establish a dynamic risk coefficient. This embodiment of the invention assesses the potential security risk of the access by comprehensively considering the characteristics of the accessing device, the current request time, the IP address's location, and geographical location information. The dynamic risk coefficient is then used to adjust the static permission level to obtain the effective permission level. This embodiment uses the dynamic risk coefficient as an adjustment factor to modify the static permission level, maintaining or increasing permissions when the risk is low and decreasing permissions when the risk is high, thus obtaining the actual effective permission level for the access. The minimum permission level is determined based on the requested access data category. This embodiment of the invention, through... The system identifies the data category the user needs to access and determines the minimum access permission level required for that category. This minimum access level is used as a threshold to determine if the current user has the right to access the data. The effective permission level is compared to the minimum permission level. If the effective permission level is lower than the minimum permission level, a pre-built access denial message is sent to the user's end. Thus, this embodiment of the invention compares the effective permission level with the minimum permission level required by the data. If the current user's permissions are insufficient to access the requested data, an access denial message is directly returned, terminating the access and preventing unauthorized operations. If the effective permission level is greater than or equal to the minimum permission level, a field masking strategy is determined based on the effective permission level and field permission attributes. For example, when the minimum permission requirements are met, based on the effective permission level and the permission attributes of each field, it is determined which fields should be fully displayed and which fields should be partially masked or completely hidden, forming a specific data anonymization scheme for this access. Payment information is extracted from a pre-built aggregated payment system according to the requested data category to obtain the original payment information. Thus, this embodiment of the invention extracts the corresponding original payment data record from the aggregated payment system's database based on the user's requested data category, containing complete field content, providing a data source for subsequent anonymization processing. The original payment information is then anonymized according to the field masking strategy to obtain secure payment information. Therefore, this embodiment of the invention, based on the established field masking strategy...Sensitive fields in the original payment information are replaced, partially hidden, or masked. The processed result is used as secure payment information, which is then used as the target information. This embodiment of the invention determines the anonymized secure payment information as the returned data for this access, sends the target information to the user access terminal, and obtains the target access terminal. This embodiment of the invention completes the data access response by returning the secure payment information to the user device that initiated the access via the network, while recording the access behavior and monitoring the target access terminal to obtain the updated effective permission level. This embodiment of the invention continuously monitors the subsequent behavior and environmental changes of the target access terminal after obtaining data, recalculates the effective permission level at the current time, determines whether the permission status has changed during the access process, prevents security vulnerabilities caused by expired permission status, and compares the updated effective permission level with the lowest permission level. The invention employs a hierarchical approach: if the updated permission level is greater than or equal to the minimum permission level, the target access endpoint is designated as the end user. This means that the updated permission level is compared with the minimum requirement; if the condition is still met, the current access status is considered secure and controllable, and the target access endpoint is confirmed as the end user, allowing continued access. If the updated permission level is lower than the minimum permission level, a pre-built termination command is sent to the target access endpoint, thus obtaining the end user and completing the access control for aggregated payment information. In essence, this invention, by comparing the updated permission level to the minimum requirement, indicates a change in the access environment or user status, prompting the issuance of a termination command to the target access endpoint to forcibly interrupt access and ensure data security. This completes the access control for the entire process. Therefore, this invention can effectively control access to aggregated payment information, thereby ensuring the data security and stable operation of the payment platform.

[0078] like Figure 2 The diagram shown is a functional block diagram of an aggregated payment information access control system based on hierarchical permissions provided in an embodiment of the present invention.

[0079] The permission-based hierarchical aggregated payment information access control system 100 described in this invention can be installed in an electronic device. Depending on the functions implemented, the permission-based hierarchical aggregated payment information access control system 100 may include a dynamic risk calculation module 101, a basic permission confirmation module 102, a target information distribution module 103, and a payment information control module 104. The module described in this invention can also be referred to as a unit, which refers to a series of computer program segments that can be executed by the processor of an electronic device and can perform a fixed function, and are stored in the memory of the electronic device.

[0080] The dynamic risk calculation module 101 is used to identify the user access terminal, parse the user access terminal to obtain the user identifier, requested access data category, request timestamp, terminal IP address, terminal longitude and terminal latitude, determine the static permission level and field permission attributes based on the user identifier, and determine the dynamic risk coefficient based on the user access terminal, request timestamp, terminal IP address, terminal longitude and terminal latitude. The basic permission confirmation module 102 is used to adjust the static permission level using a dynamic risk coefficient to obtain the effective permission level, confirm the minimum permission level based on the requested access data category, compare the effective permission level with the minimum permission level, and if the effective permission level is less than the minimum permission level, send the pre-built access denial information to the user access terminal to obtain the final user terminal. The target information delivery module 103 is used to determine the field masking strategy based on the effective permission level and field permission attributes if the effective permission level is greater than or equal to the minimum permission level, extract payment information from the pre-built aggregated payment system according to the requested access data category, obtain the original payment information, perform desensitization processing on the original payment information according to the field masking strategy, obtain secure payment information, use the secure payment information as target information, and deliver the target information to the user access terminal to obtain the target access terminal; The payment information control module 104 is used to monitor the target access terminal, obtain the update effective permission level, compare the update effective permission level with the minimum permission level, and if the update effective permission level is greater than or equal to the minimum permission level, then the target access terminal is regarded as the end user terminal; if the update effective permission level is less than the minimum permission level, then a pre-built termination instruction is sent to the target access terminal to obtain the end user terminal, thus completing the aggregated payment information access control.

[0081] In detail, the modules in the permission-based aggregated payment information access control system 100 described in this embodiment of the invention adopt the same approach as described above when in use. Figure 1 The method used here is the same as the access control method for aggregated payment information based on hierarchical permissions described above, and can produce the same technical effect, so it will not be elaborated here.

[0082] like Figure 3 The diagram shown is a structural schematic of an electronic device that implements a permission-based hierarchical aggregated payment information access control method according to an embodiment of the present invention.

[0083] The electronic device 1 may include a processor 10, a memory 11 and a bus 12, and may also include a computer program stored in the memory 11 and capable of running on the processor 10, such as a method program for access control of aggregated payment information based on permission hierarchy.

[0084] The memory 11 includes at least one type of readable storage medium, such as flash memory, portable hard drive, multimedia card, card-type memory (e.g., SD or DX memory), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 11 can be an internal storage unit of the electronic device 1, such as the portable hard drive of the electronic device 1. In other embodiments, the memory 11 can be an external storage device of the electronic device 1, such as a plug-in portable hard drive, smart media card (SMC), secure digital card (SD), flash card, etc., equipped on the electronic device 1. Furthermore, the memory 11 includes both internal storage units and external storage devices of the electronic device 1. The memory 11 can be used not only to store application software and various types of data installed on the electronic device 1, such as the code of a method for managing access to aggregated payment information based on permission levels, but also to temporarily store data that has been output or will be output.

[0085] In some embodiments, the processor 10 may be composed of integrated circuits, such as a single packaged integrated circuit or multiple integrated circuits with the same or different functions, including combinations of one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and various control chips. The processor 10 is the control unit of the electronic device, connecting various components of the entire electronic device through various interfaces and lines. It executes programs or modules stored in the memory 11 (e.g., a permission-based aggregated payment information access control method program), and calls data stored in the memory 11 to perform various functions of the electronic device 1 and process data.

[0086] The bus 12 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus 12 can be divided into an address bus, a data bus, a control bus, etc. The bus 12 is configured to realize the connection and communication between the memory 11 and at least one processor 10, etc.

[0087] Figure 3 Only electronic devices with components are shown; those skilled in the art will understand that... Figure 3The structure shown does not constitute a limitation on the electronic device 1, and may include fewer or more components than shown, or combine certain components, or have different component arrangements.

[0088] For example, although not shown, the electronic device 1 may also include a power supply (such as a battery) to power the various components. Preferably, the power supply can be logically connected to the at least one processor 10 through a power management device, thereby enabling functions such as charging management, discharging management, and power consumption management. The power supply may also include one or more DC or AC power supplies, recharging devices, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components. The electronic device 1 may also include various sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be described in detail here.

[0089] Furthermore, the electronic device 1 may also include a network interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a Wi-Fi interface, a Bluetooth interface, etc.), which is typically used to establish communication connections between the electronic device 1 and other electronic devices.

[0090] Optionally, the electronic device 1 may further include a user interface, which may be a display, an input unit (such as a keyboard), and optionally, a standard wired interface or a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen, etc. The display may also be appropriately referred to as a screen or display unit, used to display information processed in the electronic device 1 and to display a visual user interface.

[0091] The access control method program for aggregated payment information based on hierarchical permissions, stored in the memory 11 of the electronic device 1, is a combination of multiple instructions. When run in the processor 10, it can achieve the following: Once the user access terminal is identified, it is parsed to obtain the user identifier, the type of data requested, the request timestamp, the terminal IP address, the terminal longitude, and the terminal latitude. Static permission levels and field permission attributes are determined based on user identifiers; The dynamic risk coefficient is determined based on the user access point, request timestamp, terminal IP address, terminal longitude, and terminal latitude. The static permission level is adjusted using a dynamic risk coefficient to obtain the effective permission level; Determine the lowest permission level based on the type of data requested for access; Compare the effective permission level with the minimum permission level. If the effective permission level is lower than the minimum permission level, the pre-built access denial information is sent to the user access terminal to obtain the end user terminal. If the effective permission level is greater than or equal to the lowest permission level, the field masking strategy is determined based on the effective permission level and the field permission attribute. Based on the requested data category, payment information is extracted from the pre-built aggregated payment system to obtain the original payment information; The original payment information is anonymized according to the field masking strategy to obtain secure payment information; Secure payment information is used as the target information; The target information is sent to the user access terminal to obtain the target access terminal; Monitor the target access endpoint to obtain the updated and effective permission level; Compare the updated permission level with the minimum permission level. If the updated permission level is greater than or equal to the minimum permission level, then the target access terminal is taken as the end user terminal. If the updated permission level is lower than the minimum permission level, the pre-built termination command will be sent to the target access terminal to obtain the end user terminal and complete the access control of aggregated payment information.

[0092] Specifically, the processor 10's implementation method for the above instructions can be found in [reference needed]. Figures 1 to 3 The descriptions of the relevant steps in the corresponding embodiments are not repeated here.

[0093] Furthermore, if the modules / units integrated in the electronic device 1 are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. The computer-readable storage medium can be volatile or non-volatile. For example, the computer-readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, or a read-only memory (ROM).

[0094] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor of an electronic device, can perform the following: Once the user access terminal is identified, it is parsed to obtain the user identifier, the type of data requested, the request timestamp, the terminal IP address, the terminal longitude, and the terminal latitude. Static permission levels and field permission attributes are determined based on user identifiers; The dynamic risk coefficient is determined based on the user access point, request timestamp, terminal IP address, terminal longitude, and terminal latitude. The static permission level is adjusted using a dynamic risk coefficient to obtain the effective permission level; Determine the lowest permission level based on the type of data requested for access; Compare the effective permission level with the minimum permission level. If the effective permission level is lower than the minimum permission level, the pre-built access denial information is sent to the user access terminal to obtain the end user terminal. If the effective permission level is greater than or equal to the lowest permission level, the field masking strategy is determined based on the effective permission level and the field permission attribute. Based on the requested data category, payment information is extracted from the pre-built aggregated payment system to obtain the original payment information; The original payment information is anonymized according to the field masking strategy to obtain secure payment information; Secure payment information is used as the target information; The target information is sent to the user access terminal to obtain the target access terminal; Monitor the target access endpoint to obtain the updated and effective permission level; Compare the updated permission level with the minimum permission level. If the updated permission level is greater than or equal to the minimum permission level, then the target access terminal is taken as the end user terminal. If the updated permission level is lower than the minimum permission level, the pre-built termination command will be sent to the target access terminal to obtain the end user terminal and complete the access control of aggregated payment information.

[0095] In the embodiments provided by this invention, it should be understood that the disclosed devices, systems, and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative, and actual implementations may have other classification methods.

[0096] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0097] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in the form of hardware plus software functional modules.

[0098] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0099] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A method for access control of aggregated payment information based on hierarchical permission levels, characterized in that, The method includes: Once the user access terminal is identified, it is parsed to obtain the user identifier, the type of data requested, the request timestamp, the terminal IP address, the terminal longitude, and the terminal latitude. Static permission levels and field permission attributes are determined based on user identifiers; The dynamic risk coefficient is determined based on the user access point, request timestamp, terminal IP address, terminal longitude, and terminal latitude. The static permission level is adjusted using a dynamic risk coefficient to obtain the effective permission level; Determine the lowest permission level based on the type of data requested for access; Compare the effective permission level with the minimum permission level. If the effective permission level is lower than the minimum permission level, the pre-built access denial information is sent to the user access terminal to obtain the end user terminal. If the effective permission level is greater than or equal to the lowest permission level, the field masking strategy is determined based on the effective permission level and the field permission attribute. Based on the requested data category, payment information is extracted from the pre-built aggregated payment system to obtain the original payment information; The original payment information is anonymized according to the field masking strategy to obtain secure payment information; Secure payment information is used as the target information; The target information is sent to the user access terminal to obtain the target access terminal; Monitor the target access endpoint to obtain the updated and effective permission level; Compare the updated permission level with the minimum permission level. If the updated permission level is greater than or equal to the minimum permission level, then the target access terminal is taken as the end user terminal. If the updated permission level is lower than the minimum permission level, the pre-built termination command will be sent to the target access terminal to obtain the end user terminal and complete the access control of aggregated payment information.

2. The method for access control of aggregated payment information based on hierarchical permission management as described in claim 1, characterized in that, The process of determining the static permission level and field permission attributes based on the user identifier includes: The user identifier is parsed to obtain the role type identifier and the identifier validity verification code. The role type identifier is: system administrator, senior merchant or ordinary merchant. The user identifier is validated using an identifier validity check code to obtain a validation result, which is either valid or invalid. If the validation result is invalid, the preset level zero will be used as the static permission level, and the preset no permission will be used as the field permission attribute. If the verification result is valid, then the role type identifier is checked. If the role type identifier is system administrator, then the preset level three is used as the static permission level, and the preset third permission is used as the field permission attribute. If the role type is identified as a senior merchant, the preset level 2 will be used as the static permission level, and the preset second permission will be used as the field permission attribute. If the role type is identified as a regular merchant, the preset level 1 will be used as the static permission level, and the preset first permission will be used as the field permission attribute.

3. The method for access control of aggregated payment information based on hierarchical permissions as described in claim 2, characterized in that, The step of using an identifier validity check code to verify the legitimacy of the user identifier and obtaining the verification result includes: Remove the identity validity check code from the user identity to obtain the feature string to be verified, which includes multiple characters; Perform the following operation on each of the multiple characters: Based on the character, determine the character value and character sequence number; Calculate the weight value based on the character's numerical value and character sequence number; Summarize the weight values ​​to obtain multiple weight values; The total weight value is determined based on multiple weight values, where the total weight value is the sum of the multiple weight values; The remainder is calculated based on the total weight value and the preset prime modulus, where the remainder is the remainder when the total weight value is divided by the prime modulus. The recalculated check code is determined based on the remainder value and the pre-constructed check character mapping table; Compare the recalculated check code with the identifier validity check code. If the recalculated check code is equal to the identifier validity check code, then the preset valid code is taken as the verification result. Otherwise, the default invalidity will be used as the verification result.

4. The method for access control of aggregated payment information based on hierarchical permission management as described in claim 3, characterized in that, The dynamic risk coefficient determined based on the user access terminal, request timestamp, terminal IP address, terminal longitude, and terminal latitude includes: Extract historical access records from the user's access terminal to obtain a set of historical access records. The set of historical access records includes: multiple historical access times, multiple historical terminal IP addresses, and multiple historical terminal locations. Map the request timestamp to the second of the current day to get the current time; Based on the current time and multiple historical access times in the historical access record set, the most recent access time and the time dimension risk sub-coefficient are identified. Convert the terminal IP address to a binary number and obtain the converted binary string. For each historical terminal IP address in the set of historical access records, perform the following operation: Convert the historical terminal IP address into a binary string of the conversion history. Based on the converted binary string and the historical binary string, consecutive identical digits were identified. Summarize consecutive identical digits to obtain multiple consecutive identical digits; The largest consecutive number of digits is determined based on multiple consecutive identical digits, where the largest consecutive identical digit is the largest consecutive identical digit among multiple consecutive identical digits; Calculate the IP dimension risk sub-coefficient based on the maximum consecutive number of bits; The location dimension risk sub-coefficient is determined based on multiple historical terminal locations in the terminal longitude, terminal latitude, current time, most recent access time, and historical access record set; The dynamic risk coefficient is calculated based on the risk sub-coefficients of the time dimension, IP dimension, and location dimension.

5. The method for access control of aggregated payment information based on hierarchical permission management as described in claim 4, characterized in that, The method of identifying the most recent access time and time-dimensional risk sub-coefficient based on the current time and multiple historical access times in the historical access record set includes: For each historical access time in the set of historical access records, perform the following operation: Map the historical access time to the second of the current day to obtain the historical access time; Summarize historical access times to obtain multiple historical access times; Based on multiple historical access times, the historical time mean, historical time standard deviation and most recent access time are determined. The historical time mean is the average of multiple historical access times, and the historical time standard deviation is the standard deviation of multiple historical access times. The time dimension risk sub-coefficient is calculated based on the current time, the historical time mean, and the historical time standard deviation.

6. The method for access control of aggregated payment information based on hierarchical permissions as described in claim 5, characterized in that, The location dimension risk sub-coefficient is determined based on multiple historical terminal locations from the terminal longitude, terminal latitude, current time, most recent access time, and historical access record set, including: The most recently accessed historical location is determined based on the current time and multiple historical terminal locations in the historical access record set. The most recently accessed historical location includes historical longitude and historical latitude. Calculate the spatial displacement distance based on the terminal's longitude, latitude, and most recently accessed historical location; The time interval is calculated based on the current time and the most recent access time, where the time interval is equal to the current time minus the most recent access time; The location dimension risk sub-coefficient is calculated based on the time interval and spatial displacement distance, as shown in the following formula: ； in, This represents the risk sub-coefficient based on location dimension. Indicates time interval, This represents the preset feasible movement speed threshold. Indicates spatial displacement distance. This indicates the preset speed steepness coefficient. Indicates An exponential function with base 0. It is a natural constant.

7. The method for access control of aggregated payment information based on hierarchical permissions as described in claim 6, characterized in that, The field masking strategy determined based on the effective permission level and field permission attributes includes: The scope of accessible data is determined based on the effective permission level, wherein the scope of accessible data is: the first scope, the second scope, or the third scope; If the accessible data range is the first range, then the field masking strategy is determined based on the field permission attributes and the pre-built first masking strategy. If the accessible data range is the second range, then the field masking strategy is determined based on the field permission attributes and the pre-built second masking strategy. If the accessible data range is the third range, then the field masking strategy is determined based on the field permission attributes and the pre-built third masking strategy.

8. The method for access control of aggregated payment information based on hierarchical permissions as described in claim 7, characterized in that, The monitoring of the target access terminal to obtain the updated and effective permission level includes: Access behavior of the target access terminal is collected according to the preset sampling interval to obtain multiple session operation times and multiple session query field types; Anomaly scores for session behavior were determined based on multiple session operation times and multiple session query field types. Compare the abnormal conversation behavior score with the preset low-risk threshold. If the abnormal session behavior score is less than the low-risk threshold, the effective permission level will be used as the updated effective permission level. If the abnormal conversation behavior score is greater than or equal to the low-risk threshold, then compare the abnormal conversation behavior score with the preset high-risk threshold. If the abnormal session behavior score is less than the high-risk threshold, the effective permission level will be reduced by a preset step size of one level to obtain the updated effective permission level. If the abnormal session behavior score is greater than or equal to the high-risk threshold, then level zero will be used as the level for updating the effective permission.

9. The method for access control of aggregated payment information based on hierarchical permissions as described in claim 8, characterized in that, The method of determining abnormal session behavior scores based on multiple session operation times and multiple session query field types includes: An ordered sequence of operation times is determined based on multiple session operation times; Multiple adjacent time intervals were identified based on the ordered operation time sequence; The mean of adjacent operation time intervals is determined based on multiple adjacent time intervals, where the mean of adjacent operation time intervals is the average of multiple adjacent time intervals; Perform the following operation for each of the multiple session query field types: The field sensitivity value is determined based on the field type of the session query and the pre-built field sensitivity mapping table; Summarize the sensitivity values ​​of the fields to obtain sensitivity values ​​for multiple fields; The average sensitivity value of the session field was determined based on the sensitivity values ​​of multiple fields. The average sensitivity value of the session field is the average of the sensitivity values ​​of multiple fields. The abnormal session behavior score is calculated based on the average time interval between adjacent operations and the average sensitivity of session fields, as shown in the following formula: ； in, Indicates the score for abnormal session behavior. This represents the preset normal operating frequency reference value. This represents the average sensitivity of the session field. This represents the average time interval between adjacent operations.

10. A hierarchical access control system for aggregated payment information, characterized in that, The system includes: The dynamic risk calculation module is used to identify the user access terminal, parse the user access terminal to obtain the user identifier, requested access data category, request timestamp, terminal IP address, terminal longitude and terminal latitude, and determine the static permission level and field permission attributes based on the user identifier. It also determines the dynamic risk coefficient based on the user access terminal, request timestamp, terminal IP address, terminal longitude and terminal latitude. The basic permission confirmation module is used to adjust the static permission level using dynamic risk coefficients to obtain the effective permission level, determine the minimum permission level based on the requested access data category, compare the effective permission level with the minimum permission level, and if the effective permission level is less than the minimum permission level, send the pre-built access denial information to the user access terminal to obtain the end user terminal. The target information delivery module is used to determine the field masking strategy based on the effective permission level and field permission attributes if the effective permission level is greater than or equal to the minimum permission level. It extracts payment information from the pre-built aggregated payment system according to the requested access data category to obtain the original payment information. It performs desensitization processing on the original payment information according to the field masking strategy to obtain secure payment information. The secure payment information is used as target information and delivered to the user access terminal to obtain the target access terminal. The payment information control module is used to monitor the target access terminal, obtain the update effective permission level, compare the update effective permission level with the minimum permission level, and if the update effective permission level is greater than or equal to the minimum permission level, the target access terminal is designated as the end user terminal. If the update effective permission level is less than the minimum permission level, a pre-built termination command is sent to the target access terminal to obtain the end user terminal, thus completing the aggregated payment information access control.

Images