WO2016161892A1 - 一种基于地址匹配的风险识别方法及装置 - Google Patents

一种基于地址匹配的风险识别方法及装置 Download PDF

Info

Publication number
WO2016161892A1
WO2016161892A1 PCT/CN2016/076883 CN2016076883W WO2016161892A1 WO 2016161892 A1 WO2016161892 A1 WO 2016161892A1 CN 2016076883 W CN2016076883 W CN 2016076883W WO 2016161892 A1 WO2016161892 A1 WO 2016161892A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
information
user
risk
determining
Prior art date
Application number
PCT/CN2016/076883
Other languages
English (en)
French (fr)
Inventor
徐敏
许凯
何帝君
Original Assignee
阿里巴巴集团控股有限公司
徐敏
许凯
何帝君
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司, 徐敏, 许凯, 何帝君 filed Critical 阿里巴巴集团控股有限公司
Priority to SG11201708150YA priority Critical patent/SG11201708150YA/en
Priority to EP16776067.7A priority patent/EP3282666A4/en
Priority to JP2017553170A priority patent/JP2018514035A/ja
Priority to KR1020177032085A priority patent/KR102112913B1/ko
Publication of WO2016161892A1 publication Critical patent/WO2016161892A1/zh
Priority to US15/720,410 priority patent/US20180024943A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/14—Protection against unauthorised use of memory or access to memory
    • G06F12/1458—Protection against unauthorised use of memory or access to memory by checking the subject access rights
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/35—Network arrangements, protocols or services for addressing or naming involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
    • G06F21/577—Assessing vulnerabilities and evaluating computer system security
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/03—Credit; Loans; Processing thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/26—Government or public services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present application relates to the field of network technologies, and in particular, to a method and device for identifying a risk based on address matching.
  • the risk identification is mainly performed by matching and verifying the digital information, for example, by verifying whether the credit card number, the expiration date, the mobile phone number, the ID number, etc. are correct, to determine whether the current user's processing request is correct. There is a risk.
  • Applicants have found that the use of address information verification plays a more important role in risk identification for users. For example, if the receiving address entered by the user in the processing request does not match the credit card billing address of the user, it indicates that there may be a risk of user identity theft in the processing request.
  • the embodiment of the present application provides a method and device for identifying a risk based on address matching, which is used to provide a solution for performing risk identification by performing address information verification.
  • the embodiment of the present application provides a risk identification method based on address matching, including:
  • the risk verification request information includes identity identification information of a user requesting processing of a service and first address encoding information for identifying a first address;
  • the first address encoding information and the second address encoding information are address information identified by numbers and/or letters.
  • the risk identification is performed according to the obtained address matching result, including:
  • the identification information is fuzzified identification information, and the fuzzified identification information includes partial information in each complete identification information of the plurality of complete identification information;
  • Determining the stored second address encoding information corresponding to the fuzzified identification information including:
  • the second address encoding information is extracted from the user information.
  • the method further includes:
  • the feedback indicates that the user matches the failed message.
  • the service is a network transaction service
  • the first address is a billing address
  • the second address is a logistics receipt address
  • the method further includes:
  • risk rating information of the user for performing risk identification is determined.
  • the first credit record information includes one or more of the following information:
  • the first set time length is less than the second set time length.
  • the second credit record information includes one or more of the following information:
  • the blacklist user is a user with a bad credit record
  • the service is a pre-lending application service or a network application service
  • the second credit record information includes information indicating a number of servers of the service requested by the user within a fourth set time period
  • the method further includes:
  • Determining, by the user, the number of servers that apply for the service within the fourth set time period belongs to the application level, and is used for risk identification.
  • the method before receiving the risk verification request information, the method further includes:
  • the geographic extent of the address content at any non-lowest level includes a plurality of geographical ranges of address content at a lower level than the level;
  • the coded values corresponding to the address contents of the split levels are combined according to the level from highest to lowest, forming an address code value corresponding to the first address, and the feedback includes the address.
  • the address encoding information of the encoded value is not limited to the coded values corresponding to the address contents of the split levels.
  • the address encoding information further includes address validity level information
  • the address validity level information is determined according to the following steps:
  • the embodiment of the present application provides a risk identification device based on address matching, including:
  • a receiving module configured to receive risk verification request information, where the risk verification request information includes identity identification information of a user requesting to process a service, and first address encoding information used to identify the first address;
  • a determining module configured to determine the stored second address encoding information corresponding to the identification information for identifying the second address
  • the matching module is configured to determine whether the first address and the second address are consistent by matching the first address encoding information and the second address encoding information, and perform risk identification according to the obtained address matching result.
  • the embodiment of the present application can introduce the result of the address matching into the risk identification, and increases the accuracy of the risk identification of the current processing request of the user.
  • the embodiment of the present application uses the user's fuzzified identification information to perform user identification, which reduces the risk of user information leakage and protects user privacy.
  • FIG. 1 is a flowchart of a method for identifying a risk based on address matching according to Embodiment 1 of the present application;
  • FIG. 2 is a flowchart of a method for identifying a risk based on address matching according to Embodiment 2 of the present application;
  • FIG. 3 is a flowchart of a method for identifying a risk based on address matching according to Embodiment 3 of the present application;
  • FIG. 4 is a flowchart of a method for identifying a risk based on address matching according to Embodiment 4 of the present application;
  • FIG. 5 is a flowchart of a method for identifying a risk based on address matching according to Embodiment 5 of the present application;
  • FIG. 6 is a schematic structural diagram of an address matching based risk identification apparatus according to Embodiment 6 of the present application.
  • FIG. 7 is a schematic structural diagram of an address matching based risk identification apparatus according to Embodiment 7 of the present application.
  • the address verification process is implemented by using address coding information; specifically, after receiving the identity identification information carrying the user and the risk verification request information for identifying the first address coding information of the first address, determining the storage Corresponding to the identification information, the second address encoding information for identifying the second address; determining the first address and the first by matching the first address encoding information with the second address encoding information Whether the two addresses are consistent, and the risk identification is performed according to the obtained address matching result.
  • the embodiment of the present application can introduce the result of the address matching into the risk identification, which increases the accuracy of the risk identification of the current processing request of the user.
  • the embodiment of the present application uses the user's fuzzified identification information to perform user identification, which reduces the risk of user information leakage and protects user privacy.
  • a flow chart of an address matching based risk identification method includes the following steps:
  • S101 Receive risk verification request information, where the risk verification request information includes identity identification information of a user requesting processing of a service and first address encoding information used to identify a first address.
  • the embodiments of the present application may be implemented in any risk identification product.
  • any other possible application scenarios are within the protection scope of the embodiments of the present application.
  • the embodiment of the present application mainly describes the matching of the Chinese address.
  • the address matching may be performed by using the address coding method proposed in the embodiment of the present application.
  • the executor of the embodiment of the present application may be considered as a server for performing risk identification.
  • the server may serve as a service server for the user at the same time, or may not have the function of the service server, and is only responsible for the service server.
  • Request for risk identification may specifically refer to the risk verification request information sent by the service server (the server performing the risk identification is different from the service server), or may refer to the risk verification request of the receiving user equipment.
  • the risk verification request information may actually be service request information (the server performing the risk identification is the same device as the service server).
  • the above identification information may be one or more of the user's name, ID number, mobile phone number, bank card number and the like.
  • the address coding information is information that digitizes and/or characterizes the address information.
  • the digitized address coding mode is preferred in the embodiment of the present application.
  • the address encoding service may be provided in addition to the original service; that is, before S101, the method further includes: receiving an address encoding request that carries the first address; and according to the content of each address under different levels of storage Corresponding relationship between the coded values and the content of the addresses at each level after the first address is split, and determining the coded values corresponding to the address contents of the split levels; wherein any non-lowest level
  • the geographic range of the address content includes a plurality of geographic ranges of address content at a lower level than the level; the encoded values corresponding to the address contents of the split levels are combined in descending order of rank Forming an address code value corresponding to the first address, and feeding back address code information including the address code value.
  • the server for performing risk identification in the embodiment of the present application may provide a function of specifically providing address coding.
  • the service server and the server for performing risk identification in the embodiment of the present application are different devices, the service server may first send an address code request carrying the first address to the server that performs risk identification in the embodiment of the present application, and After obtaining the address coding information, the server that performs risk identification according to the embodiment of the present application sends the risk verification request information based on the address coding information.
  • the service server may directly send the server that performs the risk identification in the embodiment of the present application, including the identity identification information of the user requesting the processing service and the risk verification request information of the first address, and the server for performing risk identification in the embodiment of the present application. Address matching is performed after mapping the first address to address coded information.
  • the address can be divided into more than 10 levels of address content (or standardized fields), including provinces, cities, districts/counties, towns, roads, house numbers, buildings/buildings, units, room numbers, points of interest. (POI) Etc., respectively, map each level of address content to an N-bit coded value, for example, N can be 2; for some provinces/municipalities, for example, the codes of different provinces/municipalities can be: Beijing: 10, Shanghai City: 20, Tianjin: 30, Chongqing: 40, Heilongjiang province: 11, Jilin province: 12, Liaoning province: 13, Inner Mongolia: 15, Hebei City: 31, Shanxi province: 32, Jiangsu province: 21, Zhejiang province : 22; then, the code values corresponding to the address contents of the address are arranged in order from the largest to the smallest, that is, the address code value corresponding to the address is obtained.
  • N can be 2
  • the codes of different provinces/municipalities can be: Beijing: 10, Shanghai City
  • the address encoding information further includes address validity level information; specifically, the address validity level information may be determined according to the following steps:
  • the upper and lower levels of the stored different code values may be used (for example, the code value 20 corresponding to Shanghai has a superior relationship with the code value 51 corresponding to the Changning District of Shanghai), and the first determined
  • the code values corresponding to the address contents of each level in the address are used to determine whether the address content of different levels in the first address has a correct attribution relationship.
  • the number 0 to 5 can be used to indicate the address validity level (the address validity level is 0 to 5 in descending order from low to high). If the address code value of the first address is 1051**, where 10 represents Beijing, 51 represents Changning District, and ** is the invalid address content, because in the stored address information database, the code value 51 and representation of the Changning District are represented. There is no subordinate relationship between the coded values of 10 in Beijing (the Changning District itself is not a zone belonging to Beijing), so the first address is invalid, and the number 0 can be used to indicate the address validity level of the first address. The verification of address validity will be further explained in the following fifth embodiment.
  • S102 Determine the stored second location corresponding to the identity identification information for identifying the second address. Address encoding information.
  • the first address may be a service server (such as a bank).
  • the billing address provided (the billing address may be a home address or a unit address, etc.), and the second address may be a logistics receiving address provided by the user when trading online.
  • the service requested by the user is a pre-lending application or a network application
  • the first address may be a billing address of the user provided by the service server (such as a bank)
  • the second address may be in the user information database of the embodiment of the present application.
  • the various address information of the user collected including the logistics receipt address, unit address, home address, and the like.
  • the service requested by the user is a network transaction service
  • the server for performing risk identification in the embodiment of the present application is a service server
  • the first address may be a logistics receipt address sent by the user equipment
  • the second address may be an application example.
  • S103 Determine whether the first address and the second address are consistent by matching the first address encoding information with the second address encoding information, and perform risk identification according to the obtained address matching result.
  • the second address encoding information in the user information database is matched with the first address encoding information sent by the server, and the second address and the first address encoding information indication indicated by the second address encoding information are determined.
  • the first address encoding information may be identical to the second address encoding information, or may include the same part of the information, and the remaining information does not conflict, for example, the first address encoding information indication
  • the first address is the Chaoyang District of Beijing
  • the second address coded information indicates that the second address is the Beijing-based Chaoyang District
  • the first address coded information is the same as the second address coded information
  • the second address coded information is The address content indicated by the partial information that is different from the first address encoding information is not conflicting with the first address, and the second address may be considered to be consistent with the first address.
  • the service that is currently requested by the user may be identified based on the result of the address matching.
  • the server that performs risk identification in the embodiment of the present application is the service server, the result may be directly matched based on the address. Determining the results of risk identification, for example, when When the address matching result is that the first address is inconsistent with the second address, it is determined that the service currently requested by the user is at risk, and the processing of the service is controlled based on the result of the risk identification. If the risk verification request information is sent by a service server different from the server for performing risk identification in the embodiment of the present application, the address matching result may be sent to the service server, where the service server performs risk identification and controls the processing of the service.
  • the risk identification may be first performed, and the risk identification result is fed back to the service server.
  • the service server is fed back to the service server to indicate the current request of the user.
  • the processed business has risk response information.
  • the results of risk identification can also be determined in combination with specific business scenarios. For example, if the service requested by the user is a network transaction service, if the address matching fails, for example, the delivery address of the user network transaction and the billing address of the used credit card are inconsistent, and the transaction amount is huge, it is judged that the transaction is risky. The user can further verify the information, verify whether the credit card used in the transaction is stolen, and finally determine whether to provide the transaction payment service for the user.
  • the user's fuzzified identification information is used for user identification, which can reduce the risk of user information leakage and protect user privacy.
  • the server that performs the risk identification from the service server and the embodiment of the present application is a different device, and the service server describes the angle of the risk identification request information sent by the server that performs the risk identification in the embodiment of the present application.
  • a flowchart of an address matching based risk identification method includes the following steps:
  • S201 Receive risk verification request information sent by the service server, where the risk verification request information includes fuzzified identification information of a user requesting to process the service, and first address encoding information used to identify the first address; wherein the blurring
  • the personalized identification information includes some of the complete identification information of the plurality of complete identification information.
  • the user's fuzzified identification information includes multiple identification information, each identification Information is part of the information of a corresponding complete identification information.
  • each identification Information may include at least two of a fuzzy name, a fuzzy phone number, a fuzzy ID card number, and a fuzzy card number;
  • the fuzzified name may be a first name or a first name in the user name;
  • the blurred mobile phone number may be a user.
  • the number of digits in the mobile phone number can be customized according to the application scenario.
  • the fuzzy ID card number can be the partial digit number of the user ID number, which can be based on
  • the application scene customization for example, may be the last 4 digits of the ID number
  • the fuzzification card number may be a part of the digits of the user card number (such as a credit card, a bank card number, etc.), which may be customized according to the application scenario, such as a card number.
  • the first 6 and the last 4 are equal.
  • S202 Determine whether user information matching the fuzzified identification information is stored.
  • user matching is first performed. Specifically, based on the user information in the maintained user information database, it is determined whether there is user information of the user that matches the fuzzy identification information indicated by the risk verification request information. If yes, the user matches successfully, and the risk verification is continued. Otherwise, the information indicating that the user fails to match is fed back to the service server.
  • the second address encoding information of the user is extracted from the user information.
  • S205 Determine whether the first address and the second address are consistent by matching the first address encoding information with the second address encoding information, and feed back the obtained address matching result to the service server. Used for risk identification of the service server.
  • the result of the risk identification may be determined based on the obtained address matching result, and the result of the risk identification may be fed back to the service server. For example, if the first address is inconsistent with the second address, the current service processing is indicated to the service server. .
  • the service requested by the user may be a network transaction service or a pre-lending application industry. Any one of the service, the network application, and the like; wherein, in addition to the address matching result, the network transaction service may also determine the user's risk rating information in combination with the user's credit record, and the business server or the embodiment of the present application carries out the risk.
  • the identified server can combine risk matching results with risk matching information and risk rating information.
  • the server performing risk identification in the embodiment of the present application may send the result of the address matching and the risk rating information to the service server, or may be based on After the result of the address matching and the risk rating information determine the result of the risk identification, the result of the risk identification is sent to the service server.
  • the address information carried in the transaction packet between the server and the service server in the risk identification of the embodiment of the present application is transmitted in a digital form, and the third party can avoid the interception of the message during the message transmission process.
  • Information security risks on the other hand, can effectively reduce message bytes and improve transmission efficiency; for example, for UnionPay standard transaction messages (8583 messages), two of the reserved fields can be used to transmit address coding information and feedback risks. Rating information.
  • the user's application rating information may be determined in combination with the user's recent business situation, and the business server or the embodiment of the present application performs risk identification.
  • the server can combine the address matching result, the risk rating information, and the application rating information to identify the current business of the user.
  • the server performing risk identification in the embodiment of the present application may send the address matching result, the risk rating information, and the application degree rating information to the service server.
  • the result of the risk identification may also be sent to the service server after the result of the risk identification is determined based on the result of the address matching, the risk rating information, and the application rating information.
  • the embodiment of the present application can separately provide the function of address validity check, that is, verify whether the user address sent by the service server is authentic.
  • the service server may carry a specific service scenario code in the sent risk verification request information or the address validity verification request message, so that the embodiment of the present application determines the verification service specifically needed by the service server; for example, before the loan
  • the service scenario code of the application service may be 01
  • the service scenario code of the network application service may be 02
  • the service scenario code of the network transaction service may be 03
  • Embodiments 3 to 5 are specifically described below.
  • a flowchart of an address matching based risk identification method includes the following steps:
  • S301 Receive risk verification request information sent by the service server, where the risk verification request information includes the fuzzified identification information of the user requesting the processing service and the first address encoding information used to identify the first address.
  • S302 Determine whether user information matching the fuzzified identification information is stored.
  • the first credit record information includes one or more of the following information:
  • address validity level information of the first address indicated in the first address encoding information here, in the process of digitizing the address, there may be a process of fuzzy matching and automatic information completion, If there is an address validity problem, a number (such as 0 to 5) may be added to the mapped address coding information to identify the validity of the address coding information. The larger the digital value, the higher the validity of the address coding information, for example, if The addition of the number 0 indicates that the first address is invalid. If the number 5 is added, it indicates that the first address is valid.
  • the first set time length is less than the second set time length, for example, when the first set is recently
  • the length of the longest period is the last 3 months
  • the length of the second set time is the latest 1 year.
  • the second credit record information includes one or more of the following information:
  • the third set time length and the fourth set time length may be the same or different.
  • the third set time may be the latest one year
  • the second set time length may be the last three months.
  • S305 Determine whether the first address and the second address are consistent by matching the first address encoding information with the second address encoding information; and, based on the first credit record information and the second credit record Information determining the risk rating information of the user.
  • an application hierarchy analysis (AHP) scoring algorithm may be adopted, and the risk rating scores corresponding to each credit record information are weighted and added to determine a final risk rating score (for example, a value of 0 to 10 points, The higher the risk score, the greater the risk, or vice versa.
  • a final risk rating score for example, a value of 0 to 10 points, The higher the risk score, the greater the risk, or vice versa.
  • the risk score corresponding to each of the different results of each credit record information may be set in detail.
  • S307 The service server performs risk identification on the service currently requested by the user based on the address matching result and the risk rating information.
  • the result of the address matching affects the credibility of the risk rating information. If the address matches successfully, then The reliability of the risk rating information is high. If the address matching fails, the reliability of the risk rating information is low.
  • a flowchart of an address matching based risk identification method includes the following steps:
  • S401 Receive risk verification request information sent by the service server, where the risk verification request information includes fuzzification identification information of a user requesting to process the pre-lending application service or the network application service, and a first address for identifying the first address. Encoding information.
  • S402 Determine whether user information matching the fuzzified identification information is stored.
  • S404 If it is determined that user information matching the fuzzified identification information is stored, extracting second address encoding information and second credit record information for identifying the second address from the user information, and determining Decoding first credit record information corresponding to the first address encoding information; the second credit record information includes information indicating a number of servers of the service requested by the user within a fourth set time period.
  • S405 Determine whether the first address and the second address are consistent by matching the first address encoding information with the second address encoding information, and based on the first credit record information and the second credit record information. Determining the risk rating information of the user; and determining the number of servers to which the user applied for the service within the fourth set time period belongs to the application level.
  • the application level can be classified into three levels: high, medium, and low.
  • the number of servers that apply for the service at the lower level (that is, the number of applicants) is less than or equal to 2, and the number of servers at the higher level corresponding to the application service. (that is, the number of applicants) is greater than or equal to 5, and the number of servers (that is, the number of applicants) corresponding to the application service of the medium-level is greater than 2 and less than 5.
  • S406 The information that the user matches successfully, and the address matching result, the risk rating information, and the application level are fed back to the service server.
  • the service server performs risk identification on the service currently requested by the user based on the address matching result, the risk rating information, and the application level.
  • the service server combines the address matching result, the risk rating information, and the three-party result of the application level to identify the risk of the service currently requested by the user. For example, if the address matching fails, the risk rating information indicates that the risk is high, and the application degree is high. If the number of servers that indicate the user's recent application for the service (that is, the number of application organizations) is high, it indicates that the user is currently requesting a higher risk of business, and can perform business risk control on the user, for example, refusing to provide the user with Business service, or further information verification for the user, or restrict credit or limit the transaction amount when providing business services to the user.
  • Embodiment 5 of the present application provides a solution for performing address validity verification.
  • the address is validated to determine whether the address exists or not, so that the service server can request the user based on the true validity of the address.
  • the processed business conducts risk identification.
  • a flowchart of a risk identification method provided in Embodiment 5 of the present application includes the following steps:
  • S501 Receive an address validity verification request that carries a user address sent by any service server.
  • S502 Determine, according to the corresponding relationship between the content of each address and the coded value at different levels of the storage, and the content of the address at each level after the user address is split, determine the address content corresponding to each level after the splitting. An encoded value, and an invalid address content in the user address that does not have a corresponding relationship with the encoded value; wherein, the geographic range of the address content at any non-lowest level includes a plurality of address contents at a lower level than the level Geographical scope.
  • the user address is divided into a plurality of address contents under different levels, and the code values corresponding to each address content are sequentially determined.
  • some address contents may be invalid in themselves or have no address information in the embodiment of the present application. If the records in the library record, the contents of these addresses cannot correspond to the encoded values. In this case, special characters can be used in the mapped address encoding information to identify the invalid address contents.
  • the address coded information mapped to the address "A certain road in Chaoyang District, Beijing" is 1001**, Among them, Beijing corresponds to the code value of 10, Chaoyang District corresponds to the code value of 01, a certain road can not correspond to the code value in the address library, using the special character ** to identify, indicating that a certain way is invalid address content.
  • S503 Determine, according to the determined code values corresponding to the address contents of the respective levels, and the upper and lower levels of the stored different code values, determine a attribution relationship between address contents of different levels in the user address; The affiliation relationship, and the invalid address content of the user address that does not have a corresponding relationship with the coded value, verify whether the user address is valid, and send the verification result to the service server.
  • the user address is validated based on the superior relationship between the respective encoded values and/or the invalid address content, for example, an address encoding information is 1051**, where 10 represents Beijing, and 51 represents Changning District, ** is the invalid address content, because the code value of Beijing 10 and the code value 51 of Changning District do not have a subordinate relationship (Changning District itself belongs to the district of Shanghai), so the user address is Invalid.
  • the server can confirm that the service requested by the user is at risk, so that the user can be risk-controlled, refuse to provide business services for the user, or limit the credit amount/transaction amount.
  • the address matching-based risk identification device corresponding to the address matching-based risk identification method is also provided in the embodiment of the present application, and the method for solving the problem is related to the address matching based risk identification method in the embodiment of the present application.
  • the implementation of the device can be referred to the implementation of the method, and the repeated description will not be repeated.
  • FIG. 6 is a schematic structural diagram of an address matching-based risk identification apparatus according to Embodiment 6 of the present application, including:
  • the receiving module 61 is configured to receive the risk verification request information, where the risk verification request information includes the identity identification information of the user requesting the processing service and the first address encoding information used to identify the first address;
  • a determining module 62 configured to determine the stored second address encoding information corresponding to the identification information for identifying the second address
  • a matching module 63 configured to: by using the first address encoding information and the second address encoding information Perform matching, determine whether the first address and the second address are consistent, and perform risk identification according to the obtained address matching result.
  • the first address encoding information and the second address encoding information are address information identified by numbers and/or letters.
  • the matching module 63 is further configured to:
  • the identification information is fuzzified identification information, and the fuzzified identification information includes partial information in each complete identification information of the plurality of complete identification information;
  • the determining module 62 is specifically configured to:
  • the device further includes:
  • the sending module 64 is configured to: if the determining module 62 determines that the user information that matches the fuzzified identification information is not stored, feed back information indicating that the user fails to match.
  • the service is a network transaction service
  • the first address is a billing address
  • the second address is a logistics receipt address
  • the determining module 62 is further configured to:
  • the first credit record information includes one or more of the following information:
  • the first set time length is less than the second set time length.
  • the second credit record information includes one or more of the following information:
  • the blacklist user is a user with a bad credit record
  • the service is a pre-lending application service or a network application service
  • the second credit record information includes information indicating a number of servers of the service requested by the user within a fourth set time period
  • the determining module 62 is further configured to:
  • Determining, by the user, the number of servers that apply for the service within the fourth set time period belongs to the application level, and is used for risk identification.
  • the receiving module 61 is further configured to: before receiving the risk verification request information, receive an address encoding request that carries the first address;
  • the determining module 62 is further configured to:
  • the code values corresponding to the content of the address are combined in order of the level from high to low, forming an address code value corresponding to the first address, and feeding back address code information including the address code value.
  • the address encoding information further includes address validity level information
  • the determining module 62 is further configured to determine the address validity level information according to the following steps:
  • FIG. 7 is a schematic structural diagram of an address matching-based risk identification apparatus according to Embodiment 7 of the present application, including:
  • the receiving module 71 is configured to receive an address validity verification request that carries a user address sent by any service server;
  • the determining module 72 is configured to determine, according to the corresponding relationship between each address content and the encoded value under different levels of storage, and the address content at each level after the user address is split, determine the address under each level after the splitting The encoded value corresponding to the content, and the invalid address content in the user address that does not have a corresponding relationship with the encoded value; wherein the geographical range of the address content under any non-lowest level includes a plurality of levels lower than the level The geographical extent of the address content;
  • the verification module 73 is configured to determine, according to the determined code values corresponding to the address contents of the respective levels, and the upper and lower levels of the stored different code values, determining the attribution relationship between the address contents of different levels in the user address. And verifying, according to the determined attribution relationship, and the invalid address content in the user address that does not have a corresponding relationship with the encoded value, verifying whether the user address is valid;
  • the sending module 74 is configured to send the verification result to the service server.
  • embodiments of the present application can be provided as a method, system, or computer program product. Therefore, the present application can employ an entirely hardware embodiment, an entirely software embodiment, or a junction. In the form of an embodiment of the software and hardware aspects. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Hardware Design (AREA)
  • Signal Processing (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Software Systems (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Computing Systems (AREA)
  • Tourism & Hospitality (AREA)
  • Technology Law (AREA)
  • Primary Health Care (AREA)
  • Human Resources & Organizations (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Educational Administration (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Power Engineering (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种基于地址匹配的风险识别方法及装置，用以提供一种通过进行地址验证来实现风险识别的方案。该风险识别方法包括：接收风险验证请求信息，所述风险验证请求信息包括请求处理业务的用户的身份识别信息和用于标识第一地址的第一地址编码信息（S101）；确定存储的与所述身份识别信息对应的用于标识第二地址的第二地址编码信息（S102）；通过将所述第一地址编码信息与所述第二地址编码信息进行匹配，判断所述第一地址与第二地址是否一致，并根据得到的地址匹配结果进行风险识别（S103）。

Description

一种基于地址匹配的风险识别方法及装置 技术领域
本申请涉及网络技术领域，尤其涉及一种基于地址匹配的风险识别方法及装置。
背景技术
目前，在响应用户的业务处理请求的过程中主要通过对数字类信息的匹配核实来进行风险识别，比如通过验证信用卡卡号、有效期、手机号码、证件号码等是否正确来判断当前用户的处理请求是否存在风险。
申请人发现，采用地址信息验证对用户进行风险识别起着更加重要的作用。比如，若用户在处理请求中输入的收货地址与该用户的信用卡账单地址不一致，则说明此次处理请求可能存在用户身份盗用风险。
在风险识别场景中，对进行地址信息验证有着强烈需求，但是，由于在文字上进行地址信息验证存在较大困难，现有技术中尚没有通过进行中文地址验证来进行风险识别的方案，除中文外，其它语言的地址匹配也相类似地存在较大困难，匹配结果的可靠性较低。
发明内容
本申请实施例提供一种基于地址匹配的风险识别方法及装置，用以提供一种通过进行地址信息验证来进行风险识别的方案。
本申请实施例提供一种基于地址匹配的风险识别方法，包括：
接收风险验证请求信息，所述风险验证请求信息包括请求处理业务的用户的身份识别信息和用于标识第一地址的第一地址编码信息；
确定存储的与所述身份识别信息对应的用于标识第二地址的第二地址编码信息；
通过将所述第一地址编码信息与所述第二地址编码信息进行匹配，判断所述第一地址与第二地址是否一致，并根据得到的地址匹配结果进行风险识别。
可选地，所述第一地址编码信息和第二地址编码信息为采用数字和/或字母标识的地址信息。
可选地，根据得到的地址匹配结果进行风险识别，包括：
当所述地址匹配结果为第一地址与第二地址不一致时，确定所述用户当前请求处理的业务存在风险。
可选地，所述身份识别信息为模糊化身份识别信息，所述模糊化身份识别信息包括多种完整身份识别信息中每种完整身份识别信息中的部分信息；
确定存储的与所述模糊化身份识别信息对应的第二地址编码信息，包括：
判断是否存储有与所述模糊化身份识别信息相匹配的用户信息；
若确定存储有与所述模糊化身份识别信息相匹配的用户信息，则从该用户信息中提取第二地址编码信息。
可选地，若确定没有存储与所述模糊化身份识别信息相匹配的用户信息，则该方法还包括：
反馈指示用户匹配失败的信息。
可选地，所述业务为网络交易业务，所述第一地址为账单地址，所述第二地址为物流收货地址。
可选地，所述方法还包括：
确定与所述第一地址编码信息对应的第一信用记录信息，以及与所述身份识别信息对应的第二信用记录信息；
基于所述第一信用记录信息和第二信用记录信息，确定用于进行风险识别的所述用户的风险评级信息。
可选地，所述第一信用记录信息包括以下信息中的一种或多种：
所述第一地址编码信息中指示的所述第一地址的地址有效性等级信息；
指示在最近第一设定时间长度内是否存在与所述第一地址相关的欺诈案件发生的信息；
指示在最近第二设定时间长度内，与所述第一地址相关的欺诈案件发生的 次数、金额、以及在所有欺诈案件中的数量比重中的至少一种；
其中，所述第一设定时间长度小于所述第二设定时间长度。
可选地，所述第二信用记录信息包括以下信息中的一种或多种：
指示所述用户是否是黑名单用户的信息；所述黑名单用户为具有不良信用记录的用户；
指示所述用户是否与黑名单用户具有关联关系的信息；
指示所述用户是否与在最近第三设定时间长度内存在欺诈行为的用户具有关联关系的信息；
指示所述用户是否存在欺诈行为，或是否与欺诈案件存在关联关系的信息；
指示所述用户在最近第四设定时间长度内所申请业务的服务端的数目的信息。
可选地，所述业务为贷前申请业务或网申授信业务；所述第二信用记录信息包括指示所述用户在最近第四设定时间长度内所申请业务的服务端的数目的信息；
所述方法还包括：
确定所述用户在最近第四设定时间长度内所申请业务的服务端的数目所属申请度等级，用于进行风险识别。
可选地，接收风险验证请求信息之前，还包括：
接收携带所述第一地址的地址编码请求；
根据存储的不同级别下的各个地址内容与编码值的对应关系，以及将所述第一地址拆分后的各个级别下的地址内容，确定拆分后的各个级别下的地址内容分别对应的编码值；其中，任一非最低级别下的地址内容的地理范围内包含多个比该级别低的级别下的地址内容的地理范围；
将拆分后的各个级别下的地址内容分别对应的编码值按照级别由高到低的顺序组合在一起，形成所述第一地址对应的地址编码值，并反馈包含该地址 编码值的地址编码信息。
可选地，所述地址编码信息中还包含地址有效性等级信息；
根据以下步骤确定所述地址有效性等级信息：
基于所述第一地址中各个级别下的地址内容分别对应的编码值，以及存储的不同编码值之间的上下级关系，确定所述第一地址中不同级别的地址内容之间的归属关系；
根据确定的归属关系，以及所述第一地址中与编码值不具有对应关系的无效地址内容，确定所述第一地址的地址有效性等级信息。
本申请实施例提供一种基于地址匹配的风险识别装置，包括：
接收模块，用于接收风险验证请求信息，所述风险验证请求信息包括请求处理业务的用户的身份识别信息和用于标识第一地址的第一地址编码信息；
确定模块，用于确定存储的与所述身份识别信息对应的用于标识第二地址的第二地址编码信息；
匹配模块，用于通过将所述第一地址编码信息与所述第二地址编码信息进行匹配，判断所述第一地址与第二地址是否一致，并根据得到的地址匹配结果进行风险识别。
本申请实施例可以将地址匹配的结果引入到风险识别中，增加了对用户当前的处理请求进行风险识别的准确性。在本申请优选的实施方式中，本申请实施例采用用户的模糊化身份识别信息来进行用户识别，减少了用户信息泄露的风险，保护了用户隐私。
附图说明
图1为本申请实施例一提供的基于地址匹配的风险识别方法流程图；
图2为本申请实施例二提供的基于地址匹配的风险识别方法流程图；
图3为本申请实施例三提供的基于地址匹配的风险识别方法流程图；
图4为本申请实施例四提供的基于地址匹配的风险识别方法流程图；
图5为本申请实施例五提供的基于地址匹配的风险识别方法流程图；
图6为本申请实施例六提供的基于地址匹配的风险识别装置结构示意图；
图7为本申请实施例七提供的基于地址匹配的风险识别装置结构示意图。
具体实施方式
本申请实施例中，采用地址编码信息来实现地址验证过程；具体地，在接收到携带用户的身份识别信息和用于标识第一地址的第一地址编码信息的风险验证请求信息后，确定存储的与所述身份识别信息对应的用于标识第二地址的第二地址编码信息；通过将所述第一地址编码信息与所述第二地址编码信息进行匹配，判断所述第一地址与第二地址是否一致，并根据得到的地址匹配结果进行风险识别。
可见，本申请实施例可以将地址匹配的结果引入到风险识别中，增加了对用户当前的处理请求进行风险识别的准确性。在本申请优选的实施方式中，本申请实施例采用用户的模糊化身份识别信息来进行用户识别，减少了用户信息泄露的风险，保护了用户隐私。
下面结合说明书附图对本申请实施例作进一步详细描述。
实施例一
如图1所示，为本申请实施例一提供的基于地址匹配的风险识别方法流程图，包括以下步骤：
S101：接收风险验证请求信息，所述风险验证请求信息包括请求处理业务的用户的身份识别信息和用于标识第一地址的第一地址编码信息。
本申请实施例可以在任意风险识别产品中实施，除此之外，任何其它可能的应用场景均在本申请实施例的保护范围内。本申请实施例主要描述针对中文地址的匹配，当然，除中文外，对其它任何语言也都可以采用本申请实施例提出的进行地址编码的方式进行地址匹配。
本申请实施例的执行主体可以认为是进行风险识别的服务器，在具体实施中，该服务器可以同时作为业务服务端为用户提供业务处理服务，或者不具有业务服务端的功能，只负责基于业务服务端的请求进行风险识别。基于此，上 述S101中，接收风险验证请求消息具体可以是指接收业务服务端发送的风险验证请求信息(进行风险识别的服务器与业务服务端为不同的设备)，或者可以是指接收用户设备的风险验证请求信息，此时该风险验证请求信息实际可以是业务请求信息(进行风险识别的服务器与业务服务端为相同的设备)。
上述身份识别信息可以为用户的姓名、身份证号、手机号、银行卡号等信息中的一种或多种。地址编码信息为将地址信息数字化和/或字符化后的信息；本申请实施例中优选数字化的地址编码方式。本申请实施例中，可以在原有服务之外，提供地址编码服务；也即：S101之前，还包括：接收携带所述第一地址的地址编码请求；根据存储的不同级别下的各个地址内容与编码值的对应关系，以及将所述第一地址拆分后的各个级别下的地址内容，确定拆分后的各个级别下的地址内容分别对应的编码值；其中，任一非最低级别下的地址内容的地理范围内包含多个比该级别低的级别下的地址内容的地理范围；将拆分后的各个级别下的地址内容分别对应的编码值按照级别由高到低的顺序组合在一起，形成所述第一地址对应的地址编码值，并反馈包含该地址编码值的地址编码信息。
这里，本申请实施例进行风险识别的服务器可以提供专门提供地址编码的功能。在业务服务端与本申请实施例进行风险识别的服务器为不同设备的情况下，业务服务端可以首先向本申请实施例进行风险识别的服务器发送携带所述第一地址的地址编码请求，并在得到地址编码信息后，再基于该地址编码信息向本申请实施例进行风险识别的服务器发送风险验证请求信息。或者，业务服务端也可以直接将本申请实施例进行风险识别的服务器发送包括请求处理业务的用户的身份识别信息和所述第一地址的风险验证请求信息，本申请实施例进行风险识别的服务器将所述第一地址映射为地址编码信息后再进行地址匹配。
在具体实施中，可以将地址划分为10多级的地址内容(或称标准化字段)，包括省、市、区/县、镇、路、门牌号、幢/栋、单元、房间号、兴趣点(POI) 等，分别将每一级地址内容分别映射为一个N位的编码值，比如N可以是2；以部分省/直辖市为例，不同省/直辖市的编码值可以分别为：北京市：10，上海市：20，天津市：30，重庆市：40，黑龙江省：11，吉林省：12，辽宁省：13，内蒙古：15，河北省：31，山西省：32，江苏省：21，浙江省：22等；然后将该地址的各级地址内容对应的编码值按照地址内容范围从大到小依次排列起来，即得到该地址对应的地址编码值。在实际的风险识别场景下，考虑用户隐私和风险识别的需要，可以选择3到5级地址内容进行风险识别；这里，同一级别的地址内容对应的编码值不同，不同级别的地址内容对应的编码值可以相同，也可以不同。
可选地，所述地址编码信息中还包含地址有效性等级信息；具体可以根据以下步骤确定所述地址有效性等级信息：
基于所述第一地址中各个级别下的地址内容分别对应的编码值，以及存储的不同编码值之间的上下级关系，确定所述第一地址中不同级别的地址内容之间的归属关系；根据确定的归属关系，以及所述第一地址中与编码值不具有对应关系的无效地址内容，确定所述第一地址的地址有效性等级信息。
在具体实施中，可以基于存储的不同编码值之间的上下级关系(比如上海市对应的编码值20与上海市长宁区对应的编码值51之间具有上下级关系)，以及确定的第一地址中各个级别下的地址内容分别对应的编码值，来判断第一地址中不同级别的地址内容之间是否具有正确的归属关系，
比如，可以采用数字0～5来表示地址有效性等级(地址有效性等级由低到高依次为0～5)。若第一地址的地址编码值为1051**，其中，10表示北京市，51表示长宁区，**为无效地址内容，由于在存储的地址信息库中，表示长宁区的编码值51与表示北京市的编码值10之间不具有上下级关系(长宁区本身不是属于北京市的区)，所以该第一地址是无效的，可以采用数字0来表示该第一地址的地址有效性等级。以下实施例五将对地址有效性的验证作进一步说明。
S102：确定存储的与所述身份识别信息对应的用于标识第二地址的第二地 址编码信息。
这里，若用户请求办理的业务为网络交易业务，且风险验证请求信息为与本申请实施例进行风险识别的服务器不同的业务服务端发送的，则第一地址可以是业务服务端(比如银行)提供的账单地址(该账单地址可以是家庭住址或单位地址等)，第二地址可以是用户在网上交易时提供的物流收货地址。若用户请求办理的业务为贷前申请或网申授信业务，第一地址可以是业务服务端(比如银行)提供的用户的账单地址，第二地址则可以是本申请实施例的用户信息库中采集的该用户的各种地址信息，包括物流收货地址、单位地址、家庭住址等等。若用户请求办理的业务为网络交易业务，且本申请实施例进行风险识别的服务器本身为业务服务端，则第一地址可以是用户设备发送的物流收货地址，第二地址可以是申请实施例进行风险识别的服务器保存的账单地址。
S103：通过将所述第一地址编码信息与所述第二地址编码信息进行匹配，判断所述第一地址与第二地址是否一致，并根据得到的地址匹配结果进行风险识别。
这里，将本申请实施例提供的用户信息库中的第二地址编码信息与服务端发送的第一地址编码信息进行匹配，判断第二地址编码信息指示的第二地址与第一地址编码信息指示的第一地址是否一致，这里的一致可以包括：第一地址编码信息与第二地址编码信息完全相同，也可以包括两者的部分信息相同，其余信息不冲突，比如，第一地址编码信息指示第一地址为北京市朝阳区，第二地址编码信息指示第二地址为北京市朝阳区芍药居北里，则第一地址编码信息与第二地址编码信息的部分信息相同，第二地址编码信息中所具有的与第一地址编码信息中不相同的部分信息所指示的地址内容“芍药居北里”与第一地址并不冲突，则这时也可以认为第二地址与第一地址是一致的。
在得到地址匹配结果后，可以基于该地址匹配结果对用户当前请求办理的业务进行风险识别，这里，若本申请实施例进行风险识别的服务器本身为业务服务端，则可以直接基于该地址匹配结果确定风险识别的结果，比如，当所述 地址匹配结果为第一地址与第二地址不一致时，确定所述用户当前请求处理的业务存在风险，并基于风险识别的结果，控制业务的处理。若风险验证请求信息为与本申请实施例进行风险识别的服务器不同的业务服务端发送的，则可以将该地址匹配结果发送给业务服务端，由业务服务端进行风险识别并控制业务的处理，或者也可以首先进行风险识别，将风险识别结果反馈给业务服务端；比如，当所述地址匹配结果为第一地址与第二地址不一致时，向所述业务服务端反馈指示所述用户当前请求处理的业务存在风险的响应信息。
除了直接基于地址匹配的结果确定风险识别的结果外，还可以结合具体的业务场景确定风险识别的结果。比如，若用户请求办理的业务为网络交易业务，若地址匹配失败，比如用户网络交易的收货地址和使用的信用卡的账单地址不一致，且此次交易金额巨大，则判断此次交易存在风险，可以进一步对用户进行信息验证，核实交易所用信用卡是否处于被盗状态，再最终确定是否为用户提供交易支付服务。
以下实施例二中，采用用户的模糊化身份识别信息来进行用户识别，可以减少用户信息泄露的风险，保护用户隐私。
以下实施例二～五将从业务服务端与本申请实施例进行风险识别的服务器为不同的设备，由业务服务端向本申请实施例进行风险识别的服务器发送风险验证请求信息的角度进行描述。
实施例二
如图2所示，为本申请实施例二提供的基于地址匹配的风险识别方法流程图，包括以下步骤：
S201：接收业务服务端发送的风险验证请求信息，所述风险验证请求信息包括请求处理业务的用户的模糊化身份识别信息和用于标识第一地址的第一地址编码信息；其中，所述模糊化身份识别信息包括多种完整身份识别信息中每种完整身份识别信息中的部分信息。
这里，用户的模糊化身份识别信息包括多种身份识别信息，每种身份识别 信息是其对应的一种完整身份识别信息中的部分信息。比如，可以包括模糊化姓名、模糊化手机号、模糊化身份证号、模糊化卡号中的至少两种；这里，模糊化姓名可以是用户姓名中的姓或名；模糊化手机号可以是用户手机号中的部分位数，具体可根据应用场景定制，比如可以是手机号的前3位和后4位等；模糊化身份证号可以是用户身份证号中的部分位数，具体可根据应用场景定制，比如可以是身份证号的后4位；模糊化卡号可以是用户卡号(比如信用卡、银行卡的卡号等)中的部分位数，具体可根据应用场景定制，比如可以是卡号的前6位和后4位等。
S202：判断是否存储有与所述模糊化身份识别信息相匹配的用户信息。
S203：若确定没有存储与所述模糊化身份识别信息相匹配的用户信息，则向业务服务端反馈指示用户匹配失败的信息。
在接收到风险验证请求信息后，首先进行用户匹配，具体地，基于维护的用户信息库中的用户信息，判断是否存在与风险验证请求信息指示的模糊化身份识别信息相匹配的用户的用户信息，若存在，则说明用户匹配成功，继续进行风险验证，否则，向业务服务端反馈指示用户匹配失败的信息。
S204：若确定存储有与所述模糊化身份识别信息相匹配的用户信息，则从该用户信息中提取用于标识第二地址的第二地址编码信息。
这里，在查找到与所述模糊化身份识别信息相匹配的用户的用户信息后，从该用户信息中提取出该用户的第二地址编码信息。
S205：通过将所述第一地址编码信息与所述第二地址编码信息进行匹配，判断所述第一地址与第二地址是否一致，并将得到的地址匹配结果反馈给所述业务服务端，用于所述业务服务端进行风险识别。
这里，也可以首先基于得到的地址匹配结果确定风险识别的结果，并向业务服务端反馈风险识别的结果，比如若第一地址与第二地址不一致，向业务服务端指示当前的业务处理存在风险。
本申请实施例中，用户请求办理的业务可以是网络交易业务、贷前申请业 务、网申授信业务等中的任何一种；其中，针对网络交易业务，除了地址匹配结果外，还可以结合用户的信用记录确定用户的风险评级信息，业务服务端或本申请实施例进行风险识别的服务器可以结合地址匹配结果和风险评级信息进行风险识别。这里，当业务服务端和本申请实施例进行风险识别的服务器为不同设备时，本申请实施例进行风险识别的服务器可以将地址匹配的结果和风险评级信息发送给业务服务端，也可以在基于地址匹配的结果和风险评级信息确定风险识别的结果后，将风险识别的结果发送给业务服务端。在具体实施中，本申请实施例进行风险识别的服务器与业务服务端之间的交易报文中携带的地址信息以数字形式传输，一方面可以避免报文传输过程中被第三方截取而产生的信息安全隐患，另一方面还可以有效减少报文字节，提高传输效率；比如，针对银联标准交易报文(8583报文)，可以利用其中的两个保留域来传输地址编码信息和反馈风险评级信息。
针对贷前申请业务和网申授信业务，除地址匹配结果和风险评级信息外，还可以结合用户最近的业务情况，确定用户的申请度评级信息，业务服务端或本申请实施例进行风险识别的服务器可以结合地址匹配结果、风险评级信息和申请度评级信息对用户当前业务进行风险识别。这里，当业务服务端和本申请实施例进行风险识别的服务器为不同设备时，本申请实施例进行风险识别的服务器可以将地址匹配的结果、风险评级信息和申请度评级信息发送给业务服务端，也可以在基于地址匹配的结果、风险评级信息和申请度评级信息确定风险识别的结果后，将风险识别的结果发送给业务服务端。
除此之外，本申请实施例还可以单独提供地址有效性校验的功能，即验证业务服务端发送的用户地址是否真实有效。在具体实施中，业务服务端可以在发送的风险验证请求信息或地址有效性验证请求消息中携带具体的业务场景代码，以便本申请实施例确定业务服务端具体需要的验证服务；比如，贷前申请业务的业务场景代码可以为01、网申授信业务的业务场景代码可以为02、网络交易业务的业务场景代码可以为03、地址有效性验证业务的业务场景代码 可以为04等。
下面通过实施例三～五的内容作具体介绍。
实施例三
如图3所示，为本申请实施例三提供的基于地址匹配的风险识别方法流程图，包括以下步骤：
S301：接收业务服务端发送的风险验证请求信息，所述风险验证请求信息包括请求处理业务的用户的模糊化身份识别信息和用于标识第一地址的第一地址编码信息。
S302：判断是否存储有与所述模糊化身份识别信息相匹配的用户信息。
S303：若确定没有存储与所述模糊化身份识别信息相匹配的用户信息，则向业务服务端反馈用户匹配失败的信息。
S304：若确定存储有与所述模糊化身份识别信息相匹配的用户信息，则从该用户信息中提取用于标识第二地址的第二地址编码信息和第二信用记录信息，并确定与所述第一地址编码信息对应的第一信用记录信息。
在具体实施中，所述第一信用记录信息包括以下信息中的一种或多种：
1)所述第一地址编码信息中指示的所述第一地址的地址有效性等级信息；这里，在进行地址的数字化映射的过程中，有可能涉及模糊匹配和信息自动补全的过程，因此存在地址有效性的问题，可以在映射后的地址编码信息中添加数字(比如0～5)标识地址编码信息的有效性，该数字值越大，表示地址编码信息的有效性越高，比如若添加了数字0，则表示该第一地址是无效的，若添加了数字5，则表示该第一地址是有效的。
2)指示在最近第一设定时间长度内是否存在与所述第一地址相关的欺诈案件发生的信息。
3)指示在最近第二设定时间长度内，与所述第一地址相关的欺诈案件发生的次数、金额、以及在所有欺诈案件中的数量比重中的至少一种；
这里，第一设定时间长度小于第二设定时间长度，比如，最近第一设定时 长长度为最近3个月，最近第二设定时间长度为最近1年。
在具体实施中，所述第二信用记录信息包括以下信息中的一种或多种：
1)指示所述用户是否是黑名单用户的信息；所述黑名单用户为具有不良信用记录的用户；
2)指示所述用户是否与黑名单用户具有关联关系的信息；
3)指示所述用户是否与在最近第三设定时间长度内存在欺诈行为的用户具有关联关系的信息；
4)指示所述用户是否存在欺诈行为，或是否与欺诈案件存在关联关系的信息；
5)指示所述用户在最近第四设定时间长度内所申请业务的服务端的数目的信息。
这里，第三设定时间长度与第四设定时间长度可以相同也可以不同，比如，最近第三设定时长度可以为最近1年，最近第二设定时间长度可以为最近3个月。
S305：通过将所述第一地址编码信息与所述第二地址编码信息进行匹配，判断所述第一地址与第二地址是否一致；并，基于所述第一信用记录信息和第二信用记录信息，确定所述用户的风险评级信息。
在具体实施中，可以采用应用层次分析(AHP)打分算法，将每一种信用记录信息对应的风险评级分数加权相加，确定最终的风险评级分数(比如可以是0～10分的取值，风险分数越高，可以表示风险度越大，或者相反)。在具体实施中，可以详细设置每一种信用记录信息的不同结果所分别对应的风险分数。
S306：将得到的地址匹配结果和风险评级信息反馈给所述业务服务端。
S307：业务服务端基于所述地址匹配结果和风险评级信息，对所述用户当前请求办理的业务进行风险识别。
这里，地址匹配的结果影响风险评级信息的可信度，若地址匹配成功，则 说明风险评级信息的可信度较高，若地址匹配失败，则说明风险评级信息的可信度较低。
实施例四
如图4所示，为本申请实施例四提供的基于地址匹配的风险识别方法流程图，包括以下步骤：
S401：接收业务服务端发送的风险验证请求信息，所述风险验证请求信息包括请求处理贷前申请业务或网申授信业务的用户的模糊化身份识别信息和用于标识第一地址的第一地址编码信息。
S402：判断是否存储有与所述模糊化身份识别信息相匹配的用户信息。
S403：若确定没有存储与所述模糊化身份识别信息相匹配的用户信息，则向业务服务端反馈用户匹配失败的信息。
S404：若确定存储有与所述模糊化身份识别信息相匹配的用户信息，则从该用户信息中提取用于标识第二地址的第二地址编码信息和第二信用记录信息，并确定与所述第一地址编码信息对应的第一信用记录信息；所述第二信用记录信息包括指示所述用户在最近第四设定时间长度内所申请业务的服务端的数目的信息。
S405：通过将所述第一地址编码信息与所述第二地址编码信息进行匹配，判断所述第一地址与第二地址是否一致；并基于所述第一信用记录信息和第二信用记录信息，确定所述用户的风险评级信息；以及，确定所述用户在最近第四设定时间长度内所申请业务的服务端的数目所属申请度等级。
比如，可以将申请度等级划分为高、中、低三个等级，其中，低等级对应申请业务的服务端的数目(也即申请机构数)小于或等于2，高等级对应申请业务的服务端的数目(也即申请机构数)大于或等于5，中等级对应申请业务的服务端的数目(也即申请机构数)大于2、且小于5。
S406：将用户匹配成功的信息，以及地址匹配结果、风险评级信息和所述申请度等级反馈给所述业务服务端。
S407：业务服务端基于所述地址匹配结果、风险评级信息和申请度等级，对所述用户当前请求办理的业务进行风险识别。
这里，业务服务端结合地址匹配结果、风险评级信息和申请度等级三方结果，对用户当前请求办理的业务进行风险识别，比如，若地址匹配失败，风险评级信息中指示风险度较高，申请度等级中指示该用户最近申请业务的服务端的数目(也即申请机构数)较多，则说明该用户当前请求办理的业务风险度较高，可以对用户进行业务风险控制，比如，拒绝为用户提供业务服务，或对该用户进行进一步的信息验证，或在为该用户提供业务服务时限制授信或限制交易额度等。
本申请实施例五提供了进行地址有效性验证的方案，在该方案中，对地址进行有效性验证，判断该地址是否真实存在，这样，业务服务端可以基于地址的真实有效性，对用户请求处理的业务进行风险识别。
实施例五
如图5所示，为本申请实施例五提供的风险识别方法流程图，包括以下步骤：
S501：接收任一业务服务端发送的携带用户地址的地址有效性验证请求。
S502：根据存储的不同级别下的各个地址内容与编码值的对应关系，以及将所述用户地址拆分后的各个级别下的地址内容，确定拆分后的各个级别下的地址内容分别对应的编码值，以及所述用户地址中与编码值不具有对应关系的无效地址内容；其中，任一非最低级别下的地址内容的地理范围内包含多个比该级别低的级别下的地址内容的地理范围。
这里，将用户地址划分为不同级别下的多个地址内容，依次确定每个地址内容对应的编码值，在这个过程中，有些地址内容可能本身是无效的或者没有在本申请实施例的地址信息库中记录，则这些地址内容便无法与编码值相对应，此时可以在映射后的地址编码信息中采用特殊字符来标识这些无效地址内容。比如将地址“北京市朝阳区某某路”映射后的地址编码信息为1001**，其 中，北京市对应编码值10，朝阳区对应编码值01，某某路无法对应地址库中的编码值，采用特殊字符**来标识，表示某某路为无效地址内容。
S503：基于确定的各个级别下的地址内容分别对应的编码值，以及存储的不同编码值之间的上下级关系，确定所述用户地址中不同级别的地址内容之间的归属关系；根据确定的归属关系，以及所述用户地址中与编码值不具有对应关系的无效地址内容，验证所述用户地址是否有效，并将验证结果发送给所述业务服务端。
这里，基于各个编码值之间的上下级关系和/或所述无效地址内容，对所述用户地址进行有效性验证，比如某地址编码信息为1051**其中，10表示北京市，而51表示长宁区，**为无效地址内容，由于表示北京市的编码值10与表示长宁区的编码值51之间不具有上下级关系(长宁区本身是属于上海市的区)，所以该用户地址是无效的。服务端在得知用户提供的地址无效后，可以确认用户请求的业务存在风险，从而可以对该用户进行风险控制，拒绝为该用户提供业务服务或限制授信额度/交易金额等。
基于同一发明构思，本申请实施例中还提供了与基于地址匹配的风险识别方法对应的基于地址匹配的风险识别装置，由于该装置解决问题的原理与本申请实施例基于地址匹配的风险识别方法相似，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
实施例六
如图6所示，为本申请实施例六提供的基于地址匹配的风险识别装置结构示意图，包括：
接收模块61，用于接收风险验证请求信息，所述风险验证请求信息包括请求处理业务的用户的身份识别信息和用于标识第一地址的第一地址编码信息；
确定模块62，用于确定存储的与所述身份识别信息对应的用于标识第二地址的第二地址编码信息；
匹配模块63，用于通过将所述第一地址编码信息与所述第二地址编码信息 进行匹配，判断所述第一地址与第二地址是否一致，并根据得到的地址匹配结果进行风险识别。
可选地，所述第一地址编码信息和第二地址编码信息为采用数字和/或字母标识的地址信息。
可选地，所述匹配模块63还用于：
当所述地址匹配结果为第一地址与第二地址不一致时，确定所述用户当前请求处理的业务存在风险。
可选地，所述身份识别信息为模糊化身份识别信息，所述模糊化身份识别信息包括多种完整身份识别信息中每种完整身份识别信息中的部分信息；
所述确定模块62具体用于：
判断是否存储有与所述模糊化身份识别信息相匹配的用户信息，若确定存储有与所述模糊化身份识别信息相匹配的用户信息，则从该用户信息中提取第二地址编码信息。
可选地，所述装置还包括：
发送模块64，用于若所述确定模块62确定没有存储与所述模糊化身份识别信息相匹配的用户信息，则反馈指示用户匹配失败的信息。
可选地，所述业务为网络交易业务，所述第一地址为账单地址，所述第二地址为物流收货地址。
可选地，所述确定模块62还用于：
确定与所述第一地址编码信息对应的第一信用记录信息，以及与所述身份识别信息对应的第二信用记录信息；基于所述第一信用记录信息和第二信用记录信息，确定用于进行风险识别的所述用户的风险评级信息。
可选地，所述第一信用记录信息包括以下信息中的一种或多种：
所述第一地址编码信息中指示的所述第一地址的地址有效性等级信息；
指示在最近第一设定时间长度内是否存在与所述第一地址相关的欺诈案件发生的信息；
指示在最近第二设定时间长度内，与所述第一地址相关的欺诈案件发生的次数、金额、以及在所有欺诈案件中的数量比重中的至少一种；
其中，所述第一设定时间长度小于所述第二设定时间长度。
可选地，所述第二信用记录信息包括以下信息中的一种或多种：
指示所述用户是否是黑名单用户的信息；所述黑名单用户为具有不良信用记录的用户；
指示所述用户是否与黑名单用户具有关联关系的信息；
指示所述用户是否与在最近第三设定时间长度内存在欺诈行为的用户具有关联关系的信息；
指示所述用户是否存在欺诈行为，或是否与欺诈案件存在关联关系的信息；
指示所述用户在最近第四设定时间长度内所申请业务的服务端的数目的信息。
可选地，所述业务为贷前申请业务或网申授信业务；所述第二信用记录信息包括指示所述用户在最近第四设定时间长度内所申请业务的服务端的数目的信息；
所述确定模块62还用于：
确定所述用户在最近第四设定时间长度内所申请业务的服务端的数目所属申请度等级，用于进行风险识别。
可选地，所述接收模块61还用于，在接收风险验证请求信息之前，接收携带所述第一地址的地址编码请求；
所述确定模块62还用于：
根据存储的不同级别下的各个地址内容与编码值的对应关系，以及将所述第一地址拆分后的各个级别下的地址内容，确定拆分后的各个级别下的地址内容分别对应的编码值；其中，任一非最低级别下的地址内容的地理范围内包含多个比该级别低的级别下的地址内容的地理范围；将拆分后的各个级别下的地 址内容分别对应的编码值按照级别由高到低的顺序组合在一起，形成所述第一地址对应的地址编码值，并反馈包含该地址编码值的地址编码信息。
可选地，所述地址编码信息中还包含地址有效性等级信息；
所述确定模块62还用于根据以下步骤确定所述地址有效性等级信息：
基于所述第一地址中各个级别下的地址内容分别对应的编码值，以及存储的不同编码值之间的上下级关系，确定所述第一地址中不同级别的地址内容之间的归属关系；
根据确定的归属关系，以及所述第一地址中与编码值不具有对应关系的无效地址内容，确定所述第一地址的地址有效性等级信息。
实施例七
如图7所示，为本申请实施例七提供的基于地址匹配的风险识别装置结构示意图，包括：
接收模块71，用于接收任一业务服务端发送的携带用户地址的地址有效性验证请求；
确定模块72，用于根据存储的不同级别下的各个地址内容与编码值的对应关系，以及将所述用户地址拆分后的各个级别下的地址内容，确定拆分后的各个级别下的地址内容分别对应的编码值，以及所述用户地址中与编码值不具有对应关系的无效地址内容；其中，任一非最低级别下的地址内容的地理范围内包含多个比该级别低的级别下的地址内容的地理范围；
验证模块73，用于基于确定的各个级别下的地址内容分别对应的编码值，以及存储的不同编码值之间的上下级关系，确定所述用户地址中不同级别的地址内容之间的归属关系；根据确定的归属关系，以及所述用户地址中与编码值不具有对应关系的无效地址内容，验证所述用户地址是否有效；
发送模块74，用于将验证结果发送给所述业务服务端。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结 合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、装置(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (24)

  1. 一种基于地址匹配的风险识别方法，其特征在于，该方法包括：
    接收风险验证请求信息，所述风险验证请求信息包括请求处理业务的用户的身份识别信息和用于标识第一地址的第一地址编码信息；
    确定存储的与所述身份识别信息对应的用于标识第二地址的第二地址编码信息；
    通过将所述第一地址编码信息与所述第二地址编码信息进行匹配，判断所述第一地址与第二地址是否一致，并根据得到的地址匹配结果进行风险识别。
  2. 如权利要求1所述的方法，其特征在于，所述第一地址编码信息和第二地址编码信息为采用数字和/或字母标识的地址信息。
  3. 如权利要求1所述的方法，其特征在于，根据得到的地址匹配结果进行风险识别，包括：
    当所述地址匹配结果为第一地址与第二地址不一致时，确定所述用户当前请求处理的业务存在风险。
  4. 如权利要求1所述的方法，其特征在于，所述身份识别信息为模糊化身份识别信息，所述模糊化身份识别信息包括多种完整身份识别信息中每种完整身份识别信息中的部分信息；
    确定存储的与所述模糊化身份识别信息对应的第二地址编码信息，包括：
    判断是否存储有与所述模糊化身份识别信息相匹配的用户信息；
    若确定存储有与所述模糊化身份识别信息相匹配的用户信息，则从该用户信息中提取第二地址编码信息。
  5. 如权利要求4所述的方法，其特征在于，若确定没有存储与所述模糊化身份识别信息相匹配的用户信息，则该方法还包括：
    反馈指示用户匹配失败的信息。
  6. 如权利要求1所述的方法，其特征在于，所述业务为网络交易业务，所述第一地址为账单地址，所述第二地址为物流收货地址。
  7. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    确定与所述第一地址编码信息对应的第一信用记录信息，以及与所述身份识别信息对应的第二信用记录信息；
    基于所述第一信用记录信息和第二信用记录信息，确定用于进行风险识别的所述用户的风险评级信息。
  8. 如权利要求7所述的方法，其特征在于，所述第一信用记录信息包括以下信息中的一种或多种：
    所述第一地址编码信息中指示的所述第一地址的地址有效性等级信息；
    指示在最近第一设定时间长度内是否存在与所述第一地址相关的欺诈案件发生的信息；
    指示在最近第二设定时间长度内，与所述第一地址相关的欺诈案件发生的次数、金额、以及在所有欺诈案件中的数量比重中的至少一种；
    其中，所述第一设定时间长度小于所述第二设定时间长度。
  9. 如权利要求7所述的方法，其特征在于，所述第二信用记录信息包括以下信息中的一种或多种：
    指示所述用户是否是黑名单用户的信息；所述黑名单用户为具有不良信用记录的用户；
    指示所述用户是否与黑名单用户具有关联关系的信息；
    指示所述用户是否与在最近第三设定时间长度内存在欺诈行为的用户具有关联关系的信息；
    指示所述用户是否存在欺诈行为，或是否与欺诈案件存在关联关系的信息；
    指示所述用户在最近第四设定时间长度内所申请业务的服务端的数目的信息。
  10. 如权利要求7～9任一所述的方法，其特征在于，所述业务为贷前申请业务或网申授信业务；所述第二信用记录信息包括指示所述用户在最近第四设 定时间长度内所申请业务的服务端的数目的信息；
    所述方法还包括：
    确定所述用户在最近第四设定时间长度内所申请业务的服务端的数目所属申请度等级，用于进行风险识别。
  11. 如权利要求1所述的方法，其特征在于，接收风险验证请求信息之前，还包括：
    接收携带所述第一地址的地址编码请求；
    根据存储的不同级别下的各个地址内容与编码值的对应关系，以及将所述第一地址拆分后的各个级别下的地址内容，确定拆分后的各个级别下的地址内容分别对应的编码值；其中，任一非最低级别下的地址内容的地理范围内包含多个比该级别低的级别下的地址内容的地理范围；
    将拆分后的各个级别下的地址内容分别对应的编码值按照级别由高到低的顺序组合在一起，形成所述第一地址对应的地址编码值，并反馈包含该地址编码值的地址编码信息。
  12. 如权利要求11所述的方法，其特征在于，所述地址编码信息中还包含地址有效性等级信息；
    根据以下步骤确定所述地址有效性等级信息：
    基于所述第一地址中各个级别下的地址内容分别对应的编码值，以及存储的不同编码值之间的上下级关系，确定所述第一地址中不同级别的地址内容之间的归属关系；
    根据确定的归属关系，以及所述第一地址中与编码值不具有对应关系的无效地址内容，确定所述第一地址的地址有效性等级信息。
  13. 一种基于地址匹配的风险识别装置，其特征在于，该装置包括：
    接收模块，用于风险验证请求信息，所述风险验证请求信息包括请求处理业务的用户的身份识别信息和用于标识第一地址的第一地址编码信息；
    确定模块，用于确定存储的与所述身份识别信息对应的用于标识第二地址 的第二地址编码信息；
    匹配模块，用于通过将所述第一地址编码信息与所述第二地址编码信息进行匹配，判断所述第一地址与第二地址是否一致，并根据得到的地址匹配结果进行风险识别。
  14. 如权利要求13所述的装置，其特征在于，所述第一地址编码信息和第二地址编码信息为采用数字和/或字母标识的地址信息。
  15. 如权利要求13所述的装置，其特征在于，所述匹配模块具体用于：
    当所述地址匹配结果为第一地址与第二地址不一致时，确定所述用户当前请求处理的业务存在风险。
  16. 如权利要求13所述的装置，其特征在于，所述身份识别信息为模糊化身份识别信息，所述模糊化身份识别信息包括多种完整身份识别信息中每种完整身份识别信息中的部分信息；
    所述确定模块具体用于：
    判断是否存储有与所述模糊化身份识别信息相匹配的用户信息，若确定存储有与所述模糊化身份识别信息相匹配的用户信息，则从该用户信息中提取第二地址编码信息。
  17. 如权利要求16所述的装置，其特征在于，所述装置还包括：
    发送模块，用于若所述确定模块确定没有存储与所述模糊化身份识别信息相匹配的用户信息，则反馈指示用户匹配失败的信息。
  18. 如权利要求13所述的装置，其特征在于，所述业务为网络交易业务，所述第一地址为账单地址，所述第二地址为物流收货地址。
  19. 如权利要求13所述的装置，其特征在于，所述确定模块还用于：
    确定与所述第一地址编码信息对应的第一信用记录信息，以及与所述身份识别信息对应的第二信用记录信息；基于所述第一信用记录信息和第二信用记录信息，确定用于进行风险识别的所述用户的风险评级信息。
  20. 如权利要求19所述的装置，其特征在于，所述第一信用记录信息包 括以下信息中的一种或多种：
    所述第一地址编码信息中指示的所述第一地址的地址有效性等级信息；
    指示在最近第一设定时间长度内是否存在与所述第一地址相关的欺诈案件发生的信息；
    指示在最近第二设定时间长度内，与所述第一地址相关的欺诈案件发生的次数、金额、以及在所有欺诈案件中的数量比重中的至少一种；
    其中，所述第一设定时间长度小于所述第二设定时间长度。
  21. 如权利要求19所述的装置，其特征在于，所述第二信用记录信息包括以下信息中的一种或多种：
    指示所述用户是否是黑名单用户的信息；所述黑名单用户为具有不良信用记录的用户；
    指示所述用户是否与黑名单用户具有关联关系的信息；
    指示所述用户是否与在最近第三设定时间长度内存在欺诈行为的用户具有关联关系的信息；
    指示所述用户是否存在欺诈行为，或是否与欺诈案件存在关联关系的信息；
    指示所述用户在最近第四设定时间长度内所申请业务的服务端的数目的信息。
  22. 如权利要求19～21任一所述的装置，其特征在于，所述业务为贷前申请业务或网申授信业务；所述第二信用记录信息包括指示所述用户在最近第四设定时间长度内所申请业务的服务端的数目的信息；
    所述确定模块还用于：
    确定所述用户在最近第四设定时间长度内所申请业务的服务端的数目所属申请度等级，用于进行风险识别。
  23. 如权利要求13所述的装置，其特征在于，所述接收模块还用于，在接收风险验证请求信息之前，接收携带所述第一地址的地址编码请求；
    所述确定模块还用于：
    根据存储的不同级别下的各个地址内容与编码值的对应关系，以及将所述第一地址拆分后的各个级别下的地址内容，确定拆分后的各个级别下的地址内容分别对应的编码值；其中，任一非最低级别下的地址内容的地理范围内包含多个比该级别低的级别下的地址内容的地理范围；将拆分后的各个级别下的地址内容分别对应的编码值按照级别由高到低的顺序组合在一起，形成所述第一地址对应的地址编码值，并反馈包含该地址编码值的地址编码信息。
  24. 如权利要求23所述的装置，其特征在于，所述地址编码信息中还包含地址有效性等级信息；
    所述确定模块还用于根据以下步骤确定所述地址有效性等级信息：
    基于所述第一地址中各个级别下的地址内容分别对应的编码值，以及存储的不同编码值之间的上下级关系，确定所述第一地址中不同级别的地址内容之间的归属关系；
    根据确定的归属关系，以及所述第一地址中与编码值不具有对应关系的无效地址内容，确定所述第一地址的地址有效性等级信息。
PCT/CN2016/076883 2015-04-09 2016-03-21 一种基于地址匹配的风险识别方法及装置 WO2016161892A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
SG11201708150YA SG11201708150YA (en) 2015-04-09 2016-03-21 Address matching-based risk identification method and apparatus
EP16776067.7A EP3282666A4 (en) 2015-04-09 2016-03-21 Address matching-based risk identification method and device
JP2017553170A JP2018514035A (ja) 2015-04-09 2016-03-21 住所のマッチングに基づくリスク識別方法及び装置
KR1020177032085A KR102112913B1 (ko) 2015-04-09 2016-03-21 주소 매칭 기반 위험성 식별 방법 및 장치
US15/720,410 US20180024943A1 (en) 2015-04-09 2017-09-29 Risk identification based on address matching

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510166871.5 2015-04-09
CN201510166871.5A CN106161372B (zh) 2015-04-09 2015-04-09 一种基于地址匹配的风险识别方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/720,410 Continuation US20180024943A1 (en) 2015-04-09 2017-09-29 Risk identification based on address matching

Publications (1)

Publication Number Publication Date
WO2016161892A1 true WO2016161892A1 (zh) 2016-10-13

Family

ID=57073062

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/076883 WO2016161892A1 (zh) 2015-04-09 2016-03-21 一种基于地址匹配的风险识别方法及装置

Country Status (7)

Country Link
US (1) US20180024943A1 (zh)
EP (1) EP3282666A4 (zh)
JP (1) JP2018514035A (zh)
KR (1) KR102112913B1 (zh)
CN (1) CN106161372B (zh)
SG (2) SG10201901963WA (zh)
WO (1) WO2016161892A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113746946A (zh) * 2020-05-29 2021-12-03 Sap欧洲公司 全球地址解析器

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106598965B (zh) * 2015-10-14 2020-03-20 阿里巴巴集团控股有限公司 一种基于地址信息的账户映射方法及装置
CN107993006A (zh) * 2017-11-30 2018-05-04 平安科技（深圳）有限公司 预警等级确定方法、装置、设备及可读存储介质
CN112598321B (zh) * 2018-07-10 2024-07-02 创新先进技术有限公司 一种风险防控方法、系统及终端设备
CN109033086A (zh) * 2018-08-03 2018-12-18 银联数据服务有限公司 一种地址解析、匹配的方法及装置
US11321467B2 (en) * 2018-08-21 2022-05-03 Beijing Didi Infinity Technology And Development Co., Ltd. System and method for security analysis
CN110895651B (zh) * 2018-08-23 2024-02-02 京东科技控股股份有限公司 地址标准化处理方法、装置、设备及计算机可读存储介质
CN109379361B (zh) * 2018-10-22 2021-09-24 同盾控股有限公司 一种地址的标签确定方法和装置
CN109447751A (zh) * 2018-10-25 2019-03-08 苏州商信宝信息科技有限公司 一种基于大数据的交流方身份反欺诈识别方法及其系统
CN109584041A (zh) * 2018-10-25 2019-04-05 深圳壹账通智能科技有限公司 信贷欺诈分析方法、装置、设备及计算机可读存储介质
CN111400417A (zh) * 2018-12-28 2020-07-10 航天信息股份有限公司 一种自助办税服务大厅选址方法、装置、介质和设备
CN111490964B (zh) * 2019-01-28 2023-09-05 北京京东尚科信息技术有限公司 安全认证方法、装置及终端
CN110046352A (zh) * 2019-04-19 2019-07-23 无锡伽玛信息科技有限公司 地址标准化方法及装置
CN110633345B (zh) * 2019-08-16 2023-04-11 创新先进技术有限公司 一种企业注册地址的识别方法及系统
CN112929458B (zh) * 2019-12-06 2023-04-07 中国电信股份有限公司 App应用的服务端地址确定方法、装置以及存储介质
CN111861733B (zh) * 2020-07-31 2023-09-15 重庆富民银行股份有限公司 基于地址模糊匹配的欺诈防控系统及方法
US11616809B1 (en) * 2020-08-18 2023-03-28 Wells Fargo Bank, N.A. Fuzzy logic modeling for detection and presentment of anomalous messaging
CN112039861B (zh) * 2020-08-20 2023-04-18 咪咕文化科技有限公司 风险识别方法、装置、电子设备和计算机可读存储介质
US20230026121A1 (en) * 2021-07-22 2023-01-26 Stripe, Inc. Systems and methods for privacy preserving fraud detection during electronic transactions
CN113723777A (zh) * 2021-08-16 2021-11-30 南京航空航天大学 一种民用飞机运行风险的管理方法及装置
CN113807777A (zh) * 2021-08-30 2021-12-17 北京京东乾石科技有限公司 站点确认方法、任务切换方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101034984A (zh) * 2006-09-22 2007-09-12 北京国政通网络科技有限公司 利用用户提交的个人信息建立用户真实身份数据库
US20130211985A1 (en) * 2002-11-01 2013-08-15 Id Insight Incorporated System, method and computer program product for assessing risk of identity theft
CN103577991A (zh) * 2012-08-03 2014-02-12 阿里巴巴集团控股有限公司 一种用户的识别方法和装置
CN103577987A (zh) * 2012-07-20 2014-02-12 阿里巴巴集团控股有限公司 一种风险用户的识别方法和装置
US8725613B1 (en) * 2010-04-27 2014-05-13 Experian Information Solutions, Inc. Systems and methods for early account score and notification

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3787431B2 (ja) * 1997-04-11 2006-06-21 株式会社日立製作所 不正利用検出方法
US7403922B1 (en) * 1997-07-28 2008-07-22 Cybersource Corporation Method and apparatus for evaluating fraud risk in an electronic commerce transaction
AU2002228700A1 (en) * 2000-11-02 2002-05-15 Cybersource Corporation Method and apparatus for evaluating fraud risk in an electronic commerce transaction
US20020138371A1 (en) 2001-03-20 2002-09-26 David Lawrence Online transaction risk management
US20020181466A1 (en) * 2001-04-06 2002-12-05 Simon Neustein System for converting a fuzzy address into a precise address and completing a communication or delivery
US7346551B2 (en) * 2002-12-23 2008-03-18 Cybersource Corporation Method and apparatus for custom strategy specification in a hosted electronic transaction service system
JP4514134B2 (ja) * 2005-01-24 2010-07-28 株式会社コナミデジタルエンタテインメント ネットワークシステム、サーバ装置、不正利用検出方法、ならびに、プログラム
JP4906447B2 (ja) * 2006-09-06 2012-03-28 克佳 長嶋 住所名寄サーバおよび住所名寄方法
US20100106611A1 (en) * 2008-10-24 2010-04-29 Uc Group Ltd. Financial transactions systems and methods
US20130117081A1 (en) * 2011-11-07 2013-05-09 Fair Isaac Corporation Lead Fraud Detection
CN103297267B (zh) * 2013-05-10 2016-05-11 中华通信系统有限责任公司河北分公司 一种网络行为的风险评估方法和系统
US9563768B2 (en) * 2013-11-25 2017-02-07 Intel Corporation Methods and apparatus to manage password security
US10187366B2 (en) * 2016-04-28 2019-01-22 Visa International Service Association Systems and methods of user authentication for data services

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130211985A1 (en) * 2002-11-01 2013-08-15 Id Insight Incorporated System, method and computer program product for assessing risk of identity theft
CN101034984A (zh) * 2006-09-22 2007-09-12 北京国政通网络科技有限公司 利用用户提交的个人信息建立用户真实身份数据库
US8725613B1 (en) * 2010-04-27 2014-05-13 Experian Information Solutions, Inc. Systems and methods for early account score and notification
CN103577987A (zh) * 2012-07-20 2014-02-12 阿里巴巴集团控股有限公司 一种风险用户的识别方法和装置
CN103577991A (zh) * 2012-08-03 2014-02-12 阿里巴巴集团控股有限公司 一种用户的识别方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3282666A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113746946A (zh) * 2020-05-29 2021-12-03 Sap欧洲公司 全球地址解析器
CN113746946B (zh) * 2020-05-29 2023-12-12 Sap欧洲公司 全球地址解析器

Also Published As

Publication number Publication date
JP2018514035A (ja) 2018-05-31
KR102112913B1 (ko) 2020-05-19
CN106161372A (zh) 2016-11-23
US20180024943A1 (en) 2018-01-25
SG10201901963WA (en) 2019-04-29
SG11201708150YA (en) 2017-11-29
EP3282666A1 (en) 2018-02-14
KR20170137138A (ko) 2017-12-12
CN106161372B (zh) 2019-05-31
EP3282666A4 (en) 2018-09-05

Similar Documents

Publication Publication Date Title
WO2016161892A1 (zh) 一种基于地址匹配的风险识别方法及装置
US11025409B1 (en) Systems and methods for generating a blockchain-based user profile
US20150356523A1 (en) Decentralized identity verification systems and methods
US8682755B2 (en) Systems and methods for detecting tax refund fraud
US10911455B2 (en) Using third party information to improve predictive strength for authentications
CN108009445B (zh) 一种半中心化的可信数据管理系统
CN108683667B (zh) 账户保护方法、装置、系统和存储介质
CN107016473B (zh) 一种风险控制方法和设备
IL219511A (en) Cookie-wise for analyzing spoofs
CN110084600B (zh) 决议事务请求的处理、验证方法、装置、设备及介质
US8452965B1 (en) Self-identification of tokens
CN105608579A (zh) 一种预防信用卡盗刷的方法和系统
CN112632409A (zh) 同一用户识别方法、装置、计算机设备和存储介质
CN111507815A (zh) 基于区块链的信息获取方法、装置、设备及存储介质
CN114117264A (zh) 基于区块链的非法网站识别方法、装置、设备及存储介质
CN107506355B (zh) 对象分组方法及装置
CN113269649B (zh) 一种数字货币追踪的系统和方法
CN110598479B (zh) 一种数据处理方法、装置以及计算机可读存储介质
CN105827873A (zh) 一种解决异地客户业务办理受限的方法及装置
CN111901299A (zh) 申请认证方法、装置、电子设备和存储介质
CN113051257B (zh) 一种业务数据清洗方法及装置
CN112765588B (zh) 一种身份识别方法、装置、电子设备及存储介质
CN115099800A (zh) 基于区块链的用于对不良资产数据进行转让的方法及装置
CN114706932A (zh) 地理信息加密脱敏及查询的方法和系统
CN105427143B (zh) 一种进行系统安全控制的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16776067

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 11201708150Y

Country of ref document: SG

ENP Entry into the national phase

Ref document number: 2017553170

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20177032085

Country of ref document: KR

Kind code of ref document: A