WO2017101703A1 - 变更手机号码的业务请求的识别方法及装置 - Google Patents

变更手机号码的业务请求的识别方法及装置 Download PDF

Info

Publication number
WO2017101703A1
WO2017101703A1 PCT/CN2016/108626 CN2016108626W WO2017101703A1 WO 2017101703 A1 WO2017101703 A1 WO 2017101703A1 CN 2016108626 W CN2016108626 W CN 2016108626W WO 2017101703 A1 WO2017101703 A1 WO 2017101703A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
user
transaction record
historical transaction
historical
Prior art date
Application number
PCT/CN2016/108626
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
Priority to EP16874760.8A priority Critical patent/EP3373521A4/en
Priority to AU2016372749A priority patent/AU2016372749A1/en
Priority to JP2018530877A priority patent/JP6629973B2/ja
Priority to KR1020187019450A priority patent/KR102060262B1/ko
Priority to MYPI2018702212A priority patent/MY193475A/en
Priority to SG11201805014PA priority patent/SG11201805014PA/en
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2017101703A1 publication Critical patent/WO2017101703A1/zh
Priority to US16/005,404 priority patent/US10149152B2/en
Priority to PH12018501283A priority patent/PH12018501283A1/en
Priority to US16/206,220 priority patent/US10327134B2/en
Priority to AU2019101568A priority patent/AU2019101568A4/en
Priority to AU2020202997A priority patent/AU2020202997B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/12—Detection or prevention of fraud
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H04W8/28—Number portability ; Network address portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • 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/4014—Identity check for transactions
    • 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/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/105—Multiple levels of security
    • 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
    • H04L63/1408—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/71—Hardware identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/72—Subscriber identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • the present application relates to the field of computer technology, and in particular, to a method and apparatus for identifying a service request for changing a mobile phone number.
  • the service request for identifying the mobile phone number when the service request for identifying the mobile phone number is trusted, it is usually necessary to interact with the user multiple times, such as requiring the user to input a message verification code, a certificate number, an email address, or a security question, etc., in the user input. After the user information is verified, the service request is identified as a trusted service request, and the business operation of changing the mobile phone number is performed.
  • the above identification method usually requires the user to memorize a plurality of different user information, and the verification process is cumbersome, which brings a poor experience to the user; in addition, multiple interactions with the user may affect the service request identification of changing the mobile phone number. s efficiency.
  • the embodiment of the present application provides a method and a device for identifying a service request for changing a mobile phone number, which can improve the user experience and improve the efficiency of service request identification for changing the mobile phone number.
  • a method for identifying a service request for changing a mobile phone number comprising:
  • the preset storage unit is configured to record the service type information of the at least one user to meet the preset One or more historical transaction record information of the condition, the historical transaction record information including historical environment information;
  • the service request is identified as a trusted service request, and a business operation of changing the mobile number is performed.
  • a second aspect provides an identification device for changing a service request of a mobile phone number, the device comprising: a receiving unit, a reading unit, a determining unit, and an executing unit;
  • the receiving unit is configured to receive a service request for changing a mobile phone number sent by the first user, where the service request carries the identification information of the first user and current environment information;
  • the reading unit is configured to read, according to the identifier information of the first user received by the receiving unit, the corresponding at least one historical transaction record information, where the preset storage unit is used. Recording one or more historical transaction record information that meets a preset condition of at least one user's service type information, the historical transaction record information including historical environment information;
  • the determining unit is configured to determine whether the current environment information of the first user matches the historical environment information in the at least one historical transaction record information read by the reading unit;
  • the executing unit is configured to identify the service request as a trusted service request and perform a service operation of changing a mobile phone number if the current environment information matches the historical environment information.
  • the method and device for identifying a service request for changing a mobile phone number when receiving a service request for changing a mobile phone number sent by a user, reads from a preset storage unit according to the identification information of the user carried in the service request.
  • Corresponding historical transaction record information, and matching the current environment information carried in the service request with the historical environment information carried in the historical transaction record information, and if matched, identifying the service request as a trusted service request, and executing the change of the mobile phone The business operation of the number. It can be seen that the present application does not interact with the user when identifying the service request for changing the mobile phone number, but reads the historical transaction record information from the preset storage unit and the current environment information carried in the service request. When the historical environment information carried in the historical transaction record information is matched, the service request is identified as a trusted service request, thereby improving the user experience and improving the efficiency of the service request identification for changing the mobile phone number.
  • FIG. 1 is a flowchart of a method for identifying a service request for changing a mobile phone number according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of generating a preset storage unit provided by the present application.
  • FIG. 3 is a flowchart of a service request process for changing a mobile phone number according to another embodiment of the present application
  • FIG. 4 is a schematic diagram of an apparatus for identifying a service request for changing a mobile phone number according to another embodiment of the present application.
  • the method and device for identifying a service request for changing a mobile phone number provided in the embodiment of the present application are applicable to a scenario in the Internet system for identifying whether a service request for changing a mobile phone number is trusted. For example, a service request for changing the mobile number in the payment system can be identified.
  • FIG. 1 is a flowchart of a method for identifying a service request for changing a mobile phone number according to an embodiment of the present disclosure.
  • the executor of the method may be a device having a processing capability: a server or a system or a device. As shown in FIG. 1 , the method may specifically include:
  • Step 110 Receive a service request for changing a mobile phone number sent by the first user, where the service request carries the identifier information of the first user and current environment information.
  • the current environment information herein may be one or more of the following: a user's Internet Protocol (IP) address information, a user's Medium Access Control (MAC) address information, a user's device related information, and User's operating system information, etc.
  • IP Internet Protocol
  • MAC Medium Access Control
  • the device related information may include one or more of the following types: browser type (eg, IE, chrome, safari) information, browser version information, and MAC address identification information (umid).
  • the device related information may include one or more of the following: International Mobile Equipment Identification Number (IMEI) information and international mobile users. International Mobile Subscriber Identification Number (IMSI) information.
  • the operating system information may include operating system type and version information, such as IOS (6, 7.2, 8+), Andriod (2.3, 3, 4.2, 4.4.4, 5+) or Windows Phone.
  • the identification information of the user carried in the service request for changing the mobile phone number is “0001”
  • the current environment information includes the following four types of information: IP address information, MAC address information, browser version information, and operating system. Version information, and the four types of information are: "192.168.1.6”, “00-01-6C-06-A6-29", “IE7.0”, and "IOS8.0”.
  • Step 120 The corresponding at least one historical transaction record information is read from the preset storage unit according to the identifier information of the first user, where the preset storage unit is configured to record service type information of at least one user. One or more historical transaction record information satisfying a preset condition, the historical transaction record information including historical environment information.
  • a method for establishing a preset storage unit may be as shown in FIG. 2.
  • the preset storage unit is established as follows:
  • Step 1201 Collect a plurality of historical transaction record information of at least one user, where the historical transaction record information includes service type information.
  • the server may collect a plurality of historical transaction record information of at least one user from a background database of a plurality of Internet systems (eg, Alipay system, Taobao system, Tmall system, etc.).
  • a background database of a plurality of Internet systems eg, Alipay system, Taobao system, Tmall system, etc.
  • the historical transaction record information of the user may be recorded by the server when the user performs a transaction operation in the Internet system within a preset historical time period.
  • the collected historical transaction information of at least one user may be recorded in a data warehouse. It can be understood that since the user history transaction record information recorded in the data warehouse is unprocessed, it is unstructured. Chemical.
  • the service request for identifying the mobile phone number is changed.
  • the service type information in FIG. 2 may include one or more of the following: a mobile phone recharge record, a delivery address, a mobile phone record, a Taobao account binding mobile phone number record, and Terminal device login record, etc.
  • the plurality of historical transaction record information of at least one user in the data warehouse may be updated by T+1, where T may be 1 day or 1 hour.
  • T may be 1 day or 1 hour.
  • the server will update the historical transaction record information of the user collected on May 5, 2015 to the data warehouse on May 6, 2015. .
  • Step 1202 Select, from any one of the at least one user, one or more historical transaction record information that the service type information meets the preset condition from the plurality of historical transaction record information of the any user.
  • the preset condition may be preset multiple service type information, and the one or more historical transaction record information that meets the preset condition is that the service type information in the one or more historical transaction record information is preset. Business type information.
  • the field “User_id” is the identification information of the user
  • the field “Record_id” is the record identification information of the historical transaction record information of the user (ie, in this example, the three historical transaction record information of the user is collected), the field “Record_biz_type” For the service type information; here, it is assumed that the contents "1", “2", and “3" of the field “Record_biz_type” indicate that the service type information is "mobile phone recharge record”, "receipt address contact mobile phone record”, and “terminal device”, respectively.
  • “Login record” when the preset service type information is "mobile phone recharge record” and “receipt address contact mobile phone record", the historical transaction record information satisfying the preset condition is the first row and the second row in Table 1. Row.
  • Step 1203 Add the correspondence between the user and the one or more historical transaction record information that meets the preset condition by the service type information to the preset storage unit.
  • step 1202 - step 1203 is repeatedly performed until the correspondence between the at least one user and one or more historical transaction record information whose service type information meets the preset condition is added to the preset storage unit.
  • the preset storage unit can be as shown in Table 2.
  • the preset storage unit passes the structure shown in Table 3 and Table 4 below. And storing one or more historical transaction record information of the at least one user, the service type information of the at least one user, and the corresponding relationship.
  • the record identification information of the historical transaction record information of the user identified by the identification information may be read from the table 3 according to the identification information of the user, and then the user's IP address may be read from the table 4 according to the read record identification information.
  • Information, MAC address information, device related information, and operating system information may be read from the table 3 according to the identification information of the user, and then the user's IP address may be read from the table 4 according to the read record identification information.
  • Information, MAC address information, device related information, and operating system information may be read from the table 3 according to the identification information of the user.
  • the field “Record_mobile” in Table 3 may be changed according to actual conditions. For example, it may be changed to “Record_mail”, that is, changed to an email address, or may be changed to “Record_address”. That is, it is changed to a common communication address or the like.
  • step 120 it is assumed that the contents of the fields shown in Table 3 in the preset storage unit are as shown in Table 5.
  • two historical transaction record information of the user can be read according to the identification information “0001” of the user, and the record identification information of the two historical transaction record information is “001” and “002”, respectively.
  • Step 130 Determine whether the current environment information of the first user matches the historical environment information in the at least one historical transaction record information.
  • the service request for changing the mobile phone number in the foregoing example may further carry the changed mobile phone number.
  • step 130 may further include the step of filtering the historical transaction record information, by which the number of matching historical transaction record information may be reduced, thereby improving the service request.
  • the efficiency of identification including:
  • the changed mobile phone number carried in the service request for changing the mobile phone number is "15544667733", and the content of the "Record_mobile” field in the historical transaction record information of the record identification information is "001" and the changed mobile phone. If the number is inconsistent, that is, the historical transaction record information whose record identification information is "001" does not include the changed mobile phone number, and after the historical transaction record information is filtered, the historical transaction record information whose record identification information is "002" is obtained; That is, only the current environment information of the first user and the historical environment information in the historical transaction record information whose record identification information is "002" may be matched.
  • step 130 may specifically be:
  • Step 1301 Read historical environment information in a historical transaction record information, and sequentially record historical environment information. Each type of information is compared with the corresponding information in the current environmental information, and the number of pieces of information that is consistent with the comparison is counted.
  • the historical environment information in the historical transaction record information whose record identification information is "002" can be read, that is, the fields “Record_ip” and “Record_mac” in the record row in which the field “Record_id” in Table 6 is “002" are respectively read.
  • the four kinds of information read above are respectively compared with the corresponding information in the current environment information received in step 110, that is, "192.168.1.6” and "00-01-6C-06-A6-29” respectively read.
  • Step 1302 Determine a score result corresponding to the one historical transaction record information according to the number of pieces of information consistent with the comparison.
  • the scoring rule may be preset, and then the scoring result corresponding to one historical transaction record information is determined according to the scoring rule.
  • the predetermined scoring rule may be: if all the information is consistent (that is, all the four information are identical), the scoring result is “ 9"; if any three kinds of information are identical, the score result is "7”; if any two kinds of information are identical, the score is "5"; if any information is consistent, the result is "2"; of course, you can also set the priority for each type of information. If the information with higher priority is consistent, you can increase the score accordingly. For example, if the priority of the IP address information and the MAC address information in the environmental information is set to a high priority, when the two kinds of information are aligned, the scoring result may be “6”.
  • the score of the historical transaction record information corresponding to the record identification information of "002" is "7", that is, the information of the matching is consistent.
  • the number is three.
  • Step 1303, step 1301 - step 1302 is repeatedly executed until a score result corresponding to at least one historical transaction record information is determined.
  • the historical transaction record information in which the identification information is "003" is also included in Tables 5 and 6, and the content of the field "Record_mobile" in the historical transaction record information is consistent with the changed mobile phone number, and can be read.
  • the historical environment information in the historical transaction record information whose record identification information is “003” is taken, and the read four kinds of information are respectively compared with the corresponding information in the current environment information received in step 110, and the corresponding record identification information is determined.
  • the score of the historical transaction record information of "003" is assumed to be "5". Similarly, if there is Other historical transaction record information determines the score results corresponding to other historical transaction record information.
  • Step 1304 Determine a total result value according to the determined score result corresponding to the at least one historical transaction record information.
  • the largest rating result can be taken as the total result value.
  • the score result of the historical transaction record information corresponding to the record identification information of "002" can be taken as the total result value, that is, 7 as the total result value.
  • an average value, a weighted average value of a plurality of scoring results corresponding to the plurality of historical transaction record information, or a result value calculated according to other algorithms may be used as the total result value.
  • Step 1305 Determine, according to the total result value, whether the current environment information of the first user matches the historical environment information in the at least one historical transaction record information.
  • the threshold may be preset. If the total result value is greater than the preset threshold, it is determined that the current environment information of the first user matches the historical environment information in the at least one historical transaction record information; otherwise, the determination is a mismatch.
  • the preset threshold which can be adjusted in combination with the actual situation
  • the maximum score result is taken as the total result value, that is, when the total result value is 7, because 7>2
  • step 1301 - step 1305 is only one implementation manner of the present application.
  • the current environment information of the first user and the at least one historical transaction record information may also be determined by other manners. Whether the historical environment information matches, for example, the similarity value of the two can be calculated by the similarity algorithm, and then the similarity value is used to determine whether the two match.
  • Step 140 If it matches, the service request is identified as a trusted service request, and a business operation of changing the mobile phone number is performed.
  • step 140 is an operation performed in the case of matching; if not, the interaction with the user may further determine whether the service request for changing the mobile phone number is trusted, and if it is trusted, execute The business operation of changing the mobile number; if it is not trusted, it refuses to perform the business operation of changing the mobile number.
  • the method for identifying the service request for changing the mobile phone number when receiving the service request for changing the mobile phone number sent by the user, reads the corresponding information from the preset storage unit according to the identification information of the user carried in the service request.
  • the historical transaction record information matches the current environment information carried in the service request with the historical environment information carried in the historical transaction record information, and if matched, identifies the service request as a trusted service request, and executes Change the business operation of the mobile number. Thereby, the user experience is improved, and the efficiency of the service request identification for changing the mobile phone number can be improved.
  • FIG. 3 is a flowchart of a service request process for changing a mobile phone number according to another embodiment of the present application. As shown in FIG. 3, the method may specifically include:
  • Step 310 Receive a service request for changing a mobile phone number sent by the user, where the service request carries the identification information of the user and the current environment information.
  • the service request for changing the mobile number here may be sent by the user after logging in to the Alipay system.
  • Step 320 Perform pre-checking on the information of the user according to the identification information of the user; if the pre-check does not pass, go to step 330; otherwise, go to step 340.
  • the user's information may be a mobile phone number bound to the user's Alipay account; and if the pre-check is not passed, the mobile phone number bound to the user's Alipay account may not be detected.
  • Step 330 displaying prompt information to the user.
  • the prompt information can be used to prompt the user to directly bind the changed mobile phone number.
  • Step 340 jumping to the changed mobile phone number input page, and receiving the changed mobile phone number input by the user.
  • step 350 the changed mobile phone number is verified; if the verification is passed, step 360 is performed; otherwise, step 370 is performed.
  • the verification of the changed mobile phone number includes: verifying whether the changed mobile phone number conforms to the format of the mobile phone number (for example, whether it is composed of 11 digits) and whether the changed mobile phone number is occupied or the like.
  • Step 360 Display a first error prompt information to the user, where the first error prompt information may be used to instruct the user to re-enter the correct changed mobile phone number.
  • Step 370 Send a short message verification code to the changed mobile phone number.
  • Step 380 receiving the short message verification code input by the user, and performing verification; if the verification fails, step 390 is performed; otherwise, step 3100 is performed.
  • Step 390 Display a second error prompt information to the user, where the second error prompt information may be used to instruct the user to re-enter the correct short message verification code.
  • Step 3100 Read, according to the identification information of the user, the corresponding at least one historical transaction record information from the preset storage unit.
  • Step 3110 Determine whether the current environment information of the first user matches the historical environment information in the at least one historical transaction record information. If yes, go to step 3120; otherwise, go to step 3130.
  • step 3120 a business operation of changing the mobile phone number is performed.
  • the present application does not interact with the user when identifying the service request for changing the mobile phone number, but reads the historical transaction record information from the preset storage unit, and the current environment information and historical transaction records carried in the service request.
  • the service request is identified as a trusted service request, thereby simplifying the change process of the mobile phone number and improving the user experience.
  • step 3130 the user is verified by the body; if the verification is passed, step 3140 is performed; otherwise, step 3150 is performed.
  • step 3140 a business operation of changing the mobile phone number is performed.
  • step 3150 the third error prompt information is displayed to the user, and the number of verifications by the same user on the same day is controlled.
  • the Alipay system when the Alipay system receives the service request for changing the mobile phone number, the Alipay system does not directly perform the verification of the user, but the current environment information of the same user and the pre-collection.
  • the historical environment information in the historical transaction record information is matched. If the matching is successful, the business operation of changing the mobile phone number is directly executed, and if the matching is unsuccessful, the user is authenticated, and in fact, if it is a trusted service request
  • the changed mobile phone number is often reflected in the user's historical transaction record information; therefore, the above-mentioned automatic matching of the server can not only improve the user experience, but also improve the efficiency of the service request identification of changing the mobile phone number.
  • the embodiment of the present application further provides an identification device for changing the service request of the mobile phone number.
  • the device includes: a receiving unit 401, and a reading unit. 402, a judging unit 403, and an executing unit 404.
  • the receiving unit 401 is configured to receive a service request for changing the mobile phone number sent by the first user, where the service request carries the identifier information of the first user and current environment information.
  • the environment information includes one or more of the following information: the user's Internet Protocol IP address information, the user's multimedia access control MAC address information, the user's device related information, and the user's operating system information.
  • the reading unit 402 is configured to read, according to the identifier information of the first user received by the receiving unit 401, the corresponding at least one historical transaction record information, where the preset storage unit is used. And recording one or more historical transaction record information that meets a preset condition of the at least one user's business type information, the historical transaction record information including historical environment information.
  • the determining unit 403 is configured to determine current environment information of the first user and the read by the reading unit 402 Whether the historical environment information in at least one historical transaction record information matches.
  • the determining unit 403 is specifically configured to:
  • Reading historical environment information in a historical transaction record information sequentially comparing each type of information in the historical environment information with corresponding information in the current environment information, and counting the number of pieces of information that are consistent with each other;
  • the executing unit 404 is configured to: if the current environment information matches the historical environment information, identify the service request as a trusted service request, and perform a service operation of changing a mobile phone number.
  • the device further includes: an establishing unit 405, configured to pre-collect a plurality of historical transaction record information of the at least one user, where the historical transaction record information includes service type information;
  • the steps of selecting and adding are repeated until the correspondence between the at least one user and one or more historical transaction information that meets the preset condition of the service type information is added to the preset storage unit.
  • the service request for changing the mobile phone number further carries the changed mobile phone number.
  • the determining unit 403 is also specifically configured to:
  • the receiving unit 401 receives the service request for changing the mobile phone number sent by the first user, where the service request carries the identification information of the first user and the current Environmental information.
  • the reading unit 402 reads the corresponding at least one historical transaction record information from the preset storage unit according to the identification information of the first user, where the preset storage unit is configured to record the service type of the at least one user.
  • the information satisfies one or more historical transaction record information of a preset condition, the historical transaction record information including historical environment information.
  • the determining unit 403 determines whether the current environment information of the first user matches the historical environment information in the at least one historical transaction record information.
  • the execution unit 404 identifies the service request as a trusted service request, and performs a business operation of changing the mobile phone number. Thereby, the user experience is improved, and the efficiency of the business request identification for changing the mobile phone number is improved.
  • the steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented in hardware, a software module executed by a processor, or a combination of both.
  • the software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例涉及一种变更手机号码的业务请求的识别方法及装置，包括：在接收到用户发送的变更手机号码的业务请求时，根据业务请求中携带的用户的标识信息，从预设的存储单元中读取对应的历史交易记录信息，并将业务请求中携带的当前环境信息与历史交易记录信息中携带的历史环境信息进行匹配，若匹配，则将业务请求识别为可信的业务请求，并执行变更手机号码的业务操作。由此，既提升了用户体验，又能够提高变更手机号码的业务请求识别的效率。

Description

变更手机号码的业务请求的识别方法及装置
本申请要求2015年12月14日递交的申请号为201510927308.5、发明名称为“变更手机号码的业务请求的识别方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，特别是涉及一种变更手机号码的业务请求的识别方法及装置。
背景技术
传统技术中，在识别变更手机号码的业务请求是否可信时，通常需要与用户进行多次互动，如需要用户输入短信校验码、证件号码、邮箱地址或者安保问题等用户信息，在用户输入的用户信息验证通过后，才将该业务请求识别为可信的业务请求，并执行变更手机号码的业务操作。然而上述识别方法，通常需要用户记忆多种不同的用户信息，且验证流程比较繁琐，这给用户带来较差的体验；此外，与用户进行多次互动，会影响变更手机号码的业务请求识别的效率。
发明内容
本申请实施例提供了一种变更手机号码的业务请求的识别方法及装置，可以提升用户的体验，且可以提高变更手机号码的业务请求识别的效率。
第一方面，提供了一种变更手机号码的业务请求的识别方法，该方法包括：
接收第一用户发送的变更手机号码的业务请求，所述业务请求中携带所述第一用户的标识信息以及当前环境信息；
根据所述第一用户的标识信息，从预设的存储单元中读取对应的至少一个历史交易记录信息，其中，所述预设的存储单元用于记录至少一个用户的业务类型信息满足预设条件的一个或多个历史交易记录信息，所述历史交易记录信息包含历史环境信息；
判断所述第一用户的当前环境信息与所述至少一个历史交易记录信息中的历史环境信息是否匹配；
若匹配，则将所述业务请求识别为可信的业务请求，并执行变更手机号码的业务操作。
第二方面，提供了一种变更手机号码的业务请求的识别装置，该装置包括：接收单元、读取单元、判断单元和执行单元；
所述接收单元，用于接收第一用户发送的变更手机号码的业务请求，所述业务请求中携带所述第一用户的标识信息以及当前环境信息；
所述读取单元，用于根据接收单元接收的所述第一用户的标识信息，从预设的存储单元中读取对应的至少一个历史交易记录信息，其中，所述预设的存储单元用于记录至少一个用户的业务类型信息满足预设条件的一个或多个历史交易记录信息，所述历史交易记录信息包含历史环境信息；
所述判断单元，用于判断所述第一用户的当前环境信息与所述读取单元读取的所述至少一个历史交易记录信息中的历史环境信息是否匹配；
所述执行单元，用于若所述当前环境信息与所述历史环境信息匹配，将所述业务请求识别为可信的业务请求，并执行变更手机号码的业务操作。
本申请提供的变更手机号码的业务请求的识别方法及装置，在接收到用户发送的变更手机号码的业务请求时，根据业务请求中携带的用户的标识信息，从预设的存储单元中读取对应的历史交易记录信息，并将业务请求中携带的当前环境信息与历史交易记录信息中携带的历史环境信息进行匹配，若匹配，则将业务请求识别为可信的业务请求，并执行变更手机号码的业务操作。由此可以看出，本申请在识别变更手机号码的业务请求时，不与用户进行互动，而是从预设的存储单元中读取历史交易记录信息，并在业务请求中携带的当前环境信息与历史交易记录信息中携带的历史环境信息相匹配的情况下，将业务请求识别为可信的业务请求，由此，既提升了用户体验，又能够提高变更手机号码的业务请求识别的效率。
附图说明
为了更清楚地说明本申请或现有技术中的技术方案，下面将对本申请或现有技术描述中所需要使用的附图作简单的介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请一种实施例提供的变更手机号码的业务请求的识别方法流程图；
图2为本申请提供的预设的存储单元的生成示意图；
图3为本申请另一种实施例提供的变更手机号码的业务请求处理流程图；
图4为本申请再一种实施例提供的变更手机号码的业务请求的识别装置示意图。
具体实施方式
下面将结合本申请中的附图，对本申请中的技术方案进行清楚、完整的描述，显然，所描述的实施例是本申请的一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员获得的其他实施例，都属于本申请保护的范围。
为便于对本申请实施例的理解，下面将结合附图以具体实施例做进一步的解释说明，实施例并不构成对本申请实施例的限定。
本申请实施例提供的变更手机号码的业务请求的识别方法及装置，适用于互联网系统中对变更手机号码的业务请求是否可信进行识别的场景。如，可以对支付系统中的变更手机号码的业务请求进行识别。
图1为本申请一种实施例提供的变更手机号码的业务请求的识别方法流程图。所述方法的执行主体可以为具有处理能力的设备：服务器或者系统或者装置，如图1所示，所述方法具体可以包括：
步骤110，接收第一用户发送的变更手机号码的业务请求，所述业务请求中携带所述第一用户的标识信息以及当前环境信息。
此处的当前环境信息可以为以下一种或者多种信息：用户的互联网协议(Internet Protocol，IP)地址信息、用户的多媒体访问控制(Medium Access Control，MAC)地址信息、用户的设备相关信息和用户的操作系统信息等。需要说明的是，当设备是固定终端时，则设备相关信息可以包括以下一种或者多种：浏览器类型(例如IE、chrome、safari)信息，浏览器版本信息以及MAC地址的标识信息(umid)等；而当设备是移动终端(如，各类智能手机)时，设备相关信息可以包括以下一种或多种：国际移动设备识别码(International Mobile Equipment Identification Number，IMEI)信息以及国际移动用户识别码(International Mobile Subscriber Identification Number，IMSI)信息等。此外，操作系统信息可以包括操作系统类型以及版本信息，如IOS(6，7.2，8+)、Andriod(2.3，3，4.2，4.4.4，5+)或者Windows Phone等。
举例来说，假设该变更手机号码的业务请求中携带的用户的标识信息为“0001”，而当前环境信息中包括如下四种信息：IP地址信息、MAC地址信息、浏览器版本信息以及操作系统版本信息，且该四种信息分别为：“192.168.1.6”、“00-01-6C-06-A6-29”、“IE7.0”以及“IOS8.0”。
步骤120，根据所述第一用户的标识信息，从预设的存储单元中读取对应的至少一个历史交易记录信息，其中，所述预设的存储单元用于记录至少一个用户的业务类型信息满足预设条件的一个或多个历史交易记录信息，所述历史交易记录信息包含历史环境信息。
可选地，预设的存储单元的一种建立方式可以参见图2所示，图2中，预设的存储单元的建立步骤如下：
步骤1201，预先收集至少一个用户的多个历史交易记录信息，其中，所述历史交易记录信息中包含业务类型信息。
图2中，服务器可以预先从多个互联网系统(如，支付宝系统、淘宝系统、天猫系统等)的后台数据库中收集至少一个用户的多个历史交易记录信息。需要说明的是，用户的历史交易记录信息可以是该用户在预设的历史时间段内在互联网系统中进行交易操作时由服务器记录的。在一个例子中，收集的至少一个用户的多个历史交易记录信息可以记录在数据仓库中，可以理解的是，因为记录在数据仓库中的用户历史交易记录信息是未处理过的，所以是非结构化的。
以在支付宝系统中，识别变更手机号码的业务请求为例，图2中的业务类型信息可以包括以下一种或者多种：手机充值记录、收货地址联系手机记录淘宝账号绑定手机号码记录以及终端设备登录记录等。
需要说明的是，上述数据仓库中至少一个用户的多个历史交易记录信息可以通过T+1的方式进行更新，此处，T可以为1天或者1小时等。举例来说，若T为1天，则服务器将在2015年5月5日收集到的用户的历史交易记录信息，在2015年5月6日将该用户的历史交易记录信息更新到数据仓库中。
步骤1202，对至少一个用户中的任一用户，从所述任一用户的多个历史交易记录信息中选取业务类型信息满足预设条件的一个或多个历史交易记录信息。
此处，预设条件可以为预设的多个业务类型信息，满足预设条件的一个或多个历史交易记录信息即为该一个或多个历史交易记录信息中的业务类型信息为预设的业务类型信息。
举例来说，任一用户的历史交易记录信息如表1所示。
表1
User_id Record_id Record_biz_type 其它环境信息
0001 001 1 …
0001 002 2 …
0001 003 3 …
其中，字段“User_id”为用户的标识信息，字段“Record_id”为用户的历史交易记录信息的记录标识信息(即该例中，收集到该用户的三个历史交易记录信息)，字段“Record_biz_type”为业务类型信息；此处，假设字段“Record_biz_type”的内容“1”、“2”以及“3”分别表示业务类型信息为“手机充值记录”、“收货地址联系手机记录”以及“终端设备登录记录”；则当预设的业务类型信息为“手机充值记录”和“收货地址联系手机记录”时，则满足预设条件的历史交易记录信息为表1中的第1行和第2行。
步骤1203，将所述任一用户以及所述业务类型信息满足预设条件的一个或多个历史交易记录信息的对应关系加入所述预设的存储单元中。
如前述例子，将字段“User_id”的内容“0001”与字段“Record_id”的内容“001”、“002”的对应关系分别加入到预设的存储单元中。
步骤1204，重复执行步骤1202-步骤1203，直至将至少一个用户以及业务类型信息满足预设条件的一个或多个历史交易记录信息的对应关系加入所述预设的存储单元中。
在一个例子中，预设的存储单元可以如表2所示。
表2
User_id Record_id Record_biz_type 其它环境信息
0001 001 1 …
0001 002 2 …
0002 005 1 …
0003 009 2 …
当然，在实际应用中，由于统计的用户个数比较多，且每个用户的历史交易记录信息的个数都是海量的，所以预设的存储单元通过如下表3以及表4所示的结构存储至少一个用户、至少一个用户的业务类型信息满足预设条件的一个或多个历史交易记录信息及其对应关系。
表3
Figure PCTCN2016108626-appb-000001
表4
Figure PCTCN2016108626-appb-000002
具体地，可以根据用户的标识信息从表3中读取该标识信息标识的用户的历史交易记录信息的记录标识信息，之后可以根据读取的记录标识信息从表4中读取用户的IP地址信息、MAC地址信息、设备相关信息以及操作系统信息等。
需要说明的是，在不同的应用场景下，表3中字段“Record_mobile”可以根据实际情况进行变更，如，可以变更为“Record_mail”，即变更为邮箱地址，或者也可以变更为“Record_address”，即变更为常用通信地址等。
回到步骤120中，假设预设的存储单元中表3所示各字段的内容如表5所示。
表5
Figure PCTCN2016108626-appb-000003
则如前述例子，根据用户的标识信息“0001”可以读取到用户的两个历史交易记录信息，且该两个历史交易记录信息的记录标识信息分别为“001”和“002”。
具体地，假设记录标识信息分别为“001”和“002”的两个历史交易记录信息中如表4所示的各字段的内容如表6所示。
表6
Record_id 001 002
Record_biz_type 1 2
Record_ip 192.168.1.6 192.168.1.6
Record_mac 00-01-6C-06-A6-29 00-01-6C-06-A6-29
Record_device IE7.0 IE8.0
Record_os IOS7.2 IOS8.0
Gmt_create 2015-10-1 00：00：00 2015-11-1 00：00：00
Gmt_modified 2015-10-1 00：00：00 2015-11-1 00：00：00
步骤130，判断所述第一用户的当前环境信息与所述至少一个历史交易记录信息中的历史环境信息是否匹配。
可选地，前述例子中的变更手机号码的业务请求还可以携带变更后的手机号码。
在变更手机号码的业务请求中携带有变更后的手机号码时，步骤130进一步可以包括过滤历史交易记录信息的步骤，通过该步骤可以减少匹配的历史交易记录信息的个数，从而可以提高业务请求识别的效率，具体包括：
从所述至少一个历史交易记录信息中过滤不包含所述变更后的手机号码的历史交易记录信息，得到过滤后的至少一个历史交易记录信息。
判断所述第一用户的当前环境信息与过滤后的至少一个历史交易记录信息中的历史环境信息是否匹配。
如前述例子，假设变更手机号码的业务请求中携带的变更后的手机号码为“15544667733”，而因为记录标识信息为“001”的历史交易记录信息中“Record_mobile”字段的内容与变更后的手机号码不一致，也即记录标识信息为“001”的历史交易记录信息中不包含变更后的手机号码，在将该历史交易记录信息过滤后，得到记录标识信息为“002”的历史交易记录信息；也即只将第一用户的当前环境信息与记录标识信息为“002”的历史交易记录信息中的历史环境信息进行匹配即可。
回到步骤130中，在一个例子中，步骤130具体可以为：
步骤1301，读取一个历史交易记录信息中的历史环境信息，依次将历史环境信息中 的每种信息与当前环境信息中对应的信息进行比对，并统计比对一致的信息个数。
如，可以读取记录标识信息为“002”的历史交易记录信息中的历史环境信息，即分别读取表6中字段“Record_id”为“002”的记录行中字段“Record_ip”、“Record_mac”、“Record_device”以及“Record_os”的内容，也即读取“192.168.1.6”、“00-01-6C-06-A6-29”、“IE8.0”以及“IOS8.0”；之后分别将上述读取的四种信息分别与步骤110中接收的当前环境信息中的对应信息进行比对，即分别将读取的“192.168.1.6”、“00-01-6C-06-A6-29”、“IE8.0”以及“IOS8.0”与当前环境信息中的“192.168.1.6”、“00-01-6C-06-A6-29”、“IE7.0”以及“IOS8.0”进行比对，并统计比对一致的个数，在该例子中，比对一致的个数为3个，即只有浏览器版本信息不一致。
步骤1302，根据比对一致的信息个数，确定对应所述一个历史交易记录信息的评分结果。
此处，可以预设评分规则，之后根据评分规则确定对应一个历史交易记录信息的评分结果。在一个具体例子中，以环境信息中包括四种信息为例来说，上述预设的评分规则可以为：若全部信息比对一致(即四种信息全部比对一致)，则评分结果为“9”；若任意三种信息比对一致，则评分结果为“7”；若任意两种信息比对一致，则评分结果为“5”；若任意一种信息比对一致，则评分结果为“2”；当然，也可以给每种信息设置优先级，若优先级高的信息比对一致，则可以相应的增大评分结果。举例来说，假设将环境信息中的IP地址信息和MAC地址信息的优先级设置为高优先级，则当该两种信息比对一致时，则上述评分结果可以为“6”。
如前述例子，在没有设置优先级的情况下，根据上述预设的评分规则，则对应记录标识信息为“002”的历史交易记录信息的评分结果为“7”，即比对一致的信息个数为3个。
步骤1303，重复执行步骤1301-步骤1302，直至确定对应至少一个历史交易记录信息的评分结果。
如前述例子，假设表5和表6中还包括记录标识信息为“003”的历史交易记录信息，且该历史交易记录信息中字段“Record_mobile”的内容与变更后的手机号码一致，则可以读取记录标识信息为“003”的历史交易记录信息中的历史环境信息，并将读取的四种信息分别与步骤110中接收的当前环境信息中的对应信息进行比对，确定对应记录标识信息为“003”的历史交易记录信息的评分结果，假设评分结果为“5”。同理，若还有 其它历史交易记录信息，则确定对应其它历史交易记录信息的评分结果。
步骤1304，根据确定的对应至少一个历史交易记录信息的评分结果，确定总的结果值。
在确定对应每个历史交易记录信息的评分结果之后，可以将最大的评分结果作为总的结果值。如前述例子，可以将对应记录标识信息为“002”的历史交易记录信息的评分结果作为总的结果值，即将7作为总的结果值。或者，可以将对应多个历史交易记录信息的多个评分结果的平均值、加权平均值或者将根据其它算法计算的结果值作为总的结果值。
步骤1305，根据所述总的结果值，判断所述第一用户的当前环境信息与所述至少一个历史交易记录信息中的历史环境信息是否匹配。
此处可以预先设定阈值，若总的结果值大于预先设定的阈值，则判断第一用户的当前环境信息与至少一个历史交易记录信息中的历史环境信息匹配；否则判断为不匹配。如前述例子，假设预先设定的阈值(可结合实际情况进行调整)为2，则将最大的评分结果作为总的结果值时，也即总的结果值为7时，因为7>2，所以判断第一用户的当前环境信息与记录标识信息为“002”与“003”的历史交易记录信息中的历史环境信息匹配。
需要说明的是，上述步骤1301-步骤1305只是本申请的一种实现方式，在实际应用中，也可以通过其它方式判断所述第一用户的当前环境信息与所述至少一个历史交易记录信息中的历史环境信息是否匹配，如，可以通过相似度算法计算两者的相似度值，之后通过相似度值确定两者是否匹配。
步骤140，若匹配，则将所述业务请求识别为可信的业务请求，并执行变更手机号码的业务操作。
如前述例子，因为两者相匹配，则可以执行变更手机号码的业务操作。
需要说明的是，上述步骤140是在匹配的情况下，所执行的操作；若不匹配，则可以通过与用户的互动来进一步确定变更手机号码的业务请求是否可信，若可信，则执行变更手机号码的业务操作；若不可信，则拒绝执行变更手机号码的业务操作。
本申请提供的变更手机号码的业务请求的识别方法，在接收到用户发送的变更手机号码的业务请求时，根据业务请求中携带的用户的标识信息，从预设的存储单元中读取对应的历史交易记录信息，并将业务请求中携带的当前环境信息与历史交易记录信息中携带的历史环境信息进行匹配，若匹配，则将业务请求识别为可信的业务请求，并执行 变更手机号码的业务操作。由此，既提升了用户体验，又能够提高变更手机号码的业务请求识别的效率。
以下将通过实施例的方式介绍如何将本申请的变更手机号码的业务请求的识别方法应用到支付宝系统中。
图3为本申请另一种实施例提供的变更手机号码的业务请求处理流程图。如图3所示，所述方法具体可以包括：
步骤310，接收用户发送的变更手机号码的业务请求，该业务请求中携带用户的标识信息以及当前环境信息。
此处的变更手机号码的业务请求可以是用户在登录到支付宝系统后发送的。
步骤320，根据用户的标识信息对该用户的信息进行前置检查；若前置检查不通过，则执行步骤330；否则执行步骤340。
此处，用户的信息可以为与用户的支付宝账号绑定的手机号码；而前置检查不通过则可以为未检测到与用户的支付宝账号绑定的手机号码。
步骤330，向用户显示提示信息。
该提示信息可以用于提示用户直接绑定变更后的手机号码即可。
步骤340，跳转至变更后的手机号码输入页面，并接收用户输入的变更后的手机号码。
步骤350，对变更后的手机号码进行验证；若验证通过，则执行步骤360；否则执行步骤370。
此处，对变更后的手机号码进行验证包括：验证变更后的手机号码是否符合手机号码的格式(如，是否由11位的数字构成)以及变更后的手机号码是否被占用等。
步骤360，向用户显示第一错误提示信息，该第一错误提示信息可以用于指示用户重新输入正确的变更后的手机号码。
步骤370，向变更后的手机号码发送短信验证码。
步骤380，接收用户输入的短信验证码，并进行验证；若验证不通过，则执行步骤390；否则执行步骤3100。
步骤390，向用户显示第二错误提示信息，该第二错误提示信息可以用于指示用户重新输入正确的短信验证码。
步骤3100，根据用户的标识信息，从预设的存储单元中读取对应的至少一个历史交易记录信息。
步骤3110，判断第一用户的当前环境信息与至少一个历史交易记录信息中的历史环境信息是否匹配；若匹配，则执行步骤3120；否则执行步骤3130。
步骤3120，执行变更手机号码的业务操作。
也即本申请在识别变更手机号码的业务请求时，不与用户进行互动，而是从预设的存储单元中读取历史交易记录信息，并在业务请求中携带的当前环境信息与历史交易记录信息中携带的历史环境信息相匹配的情况下，将业务请求识别为可信的业务请求，从而可以精简手机号码的变更流程，提升用户体验。
步骤3130，对用户进行核身验证；若验证通过，则执行步骤3140；否则执行步骤3150。
步骤3140，执行变更手机号码的业务操作。
步骤3150，向用户显示第三错误提示信息，并控制同一用户当天核身验证的次数。
综上，在本申请的变更手机号码的业务请求的处理流程中，支付宝系统在接收到变更手机号码的业务请求时，不是直接对用户进行核身，而是将同一用户当前环境信息与预先收集的历史交易记录信息中的历史环境信息进行匹配，若匹配成功，则直接执行变更手机号码的业务操作，而若匹配不成功，再对用户进行核身，而事实上，若是可信的业务请求，则变更后的手机号码往往会体现在用户的历史交易记录信息中；因此，通过上述服务器自动匹配的方式既可以提升用户的体验，又能够提高变更手机号码的业务请求识别的效率。
与上述变更手机号码的业务请求的识别方法对应地，本申请实施例还提供的一种变更手机号码的业务请求的识别装置，如图4所示，该装置包括：接收单元401、读取单元402、判断单元403和执行单元404。
接收单元401，用于接收第一用户发送的变更手机号码的业务请求，所述业务请求中携带所述第一用户的标识信息以及当前环境信息。
其中，环境信息包括以下一种或者多种信息：用户的互联网协议IP地址信息、用户的多媒体访问控制MAC地址信息、用户的设备相关信息和用户的操作系统信息。
读取单元402，用于根据接收单元401接收的所述第一用户的标识信息，从预设的存储单元中读取对应的至少一个历史交易记录信息，其中，所述预设的存储单元用于记录至少一个用户的业务类型信息满足预设条件的一个或多个历史交易记录信息，所述历史交易记录信息包含历史环境信息。
判断单元403，用于判断所述第一用户的当前环境信息与读取单元402读取的所述 至少一个历史交易记录信息中的历史环境信息是否匹配。
判断单元403具体用于：
读取一个历史交易记录信息中的历史环境信息，依次将历史环境信息中的每种信息与当前环境信息中对应的信息进行比对，并统计比对一致的信息个数；
根据比对一致的信息个数，确定对应所述一个历史交易记录信息的评分结果；
重复执行上述比对以及确定评分结果的步骤，直至确定对应至少一个历史交易记录信息的评分结果；
根据确定的对应至少一个历史交易记录信息的评分结果，确定总的结果值；
根据所述总的结果值，判断所述第一用户的当前环境信息与所述至少一个历史交易记录信息中的历史环境信息是否匹配。
执行单元404，用于若所述当前环境信息与所述历史环境信息匹配，将所述业务请求识别为可信的业务请求，并执行变更手机号码的业务操作。
可选地，所述装置还包括：建立单元405，用于预先收集至少一个用户的多个历史交易记录信息，其中，所述历史交易记录信息中包含业务类型信息；
对至少一个用户中的任一用户，从所述任一用户的多个历史交易记录信息中选取业务类型信息满足预设条件的一个或多个历史交易记录信息；
将所述任一用户以及所述业务类型信息满足预设条件的一个或多个历史交易记录信息的对应关系加入所述预设的存储单元中；
重复上述选取以及加入的步骤，直至将至少一个用户以及业务类型信息满足预设条件的一个或多个历史交易记录信息的对应关系加入所述预设的存储单元中。
可选地，所述变更手机号码的业务请求中还携带变更后的手机号码。
判断单元403还具体用于：
从所述至少一个历史交易记录信息中过滤不包含所述变更后的手机号码的历史交易记录信息，得到过滤后的至少一个历史交易记录信息；
判断所述第一用户的当前环境信息与过滤后的至少一个历史交易记录信息中的历史环境信息是否匹配。
本申请实施例装置的各功能模块的功能，可以通过上述方法实施例的各步骤来实现，因此，本申请提供的装置的具体工作过程，在此不复赘述。
本申请提供的变更手机号码的业务请求的识别装置，接收单元401接收第一用户发送的变更手机号码的业务请求，所述业务请求中携带所述第一用户的标识信息以及当前 环境信息。读取单元402根据所述第一用户的标识信息，从预设的存储单元中读取对应的至少一个历史交易记录信息，其中，所述预设的存储单元用于记录至少一个用户的业务类型信息满足预设条件的一个或多个历史交易记录信息，所述历史交易记录信息包含历史环境信息。判断单元403判断所述第一用户的当前环境信息与所述至少一个历史交易记录信息中的历史环境信息是否匹配。执行单元404在所述当前环境信息与所述历史环境信息匹配时，将所述业务请求识别为可信的业务请求，并执行变更手机号码的业务操作。由此，既提升了用户体验，又能够提高业变更手机号码的业务请求识别的效率。
专业人员应该还可以进一步意识到，结合本文中所公开的实施例描述的各示例的对象及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
结合本文中所公开的实施例描述的方法或算法的步骤可以用硬件、处理器执行的软件模块，或者二者的结合来实施。软件模块可以置于随机存储器(RAM)、内存、只读存储器(ROM)、电可编程ROM、电可擦除可编程ROM、寄存器、硬盘、可移动磁盘、CD-ROM、或技术领域内所公知的任意其它形式的存储介质中。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (10)

  1. 一种变更手机号码的业务请求的识别方法，其特征在于，该方法包括：
    接收第一用户发送的变更手机号码的业务请求，所述业务请求中携带所述第一用户的标识信息以及当前环境信息；
    根据所述第一用户的标识信息，从预设的存储单元中读取对应的至少一个历史交易记录信息，其中，所述预设的存储单元用于记录至少一个用户的业务类型信息满足预设条件的一个或多个历史交易记录信息，所述历史交易记录信息包含历史环境信息；
    判断所述第一用户的当前环境信息与所述至少一个历史交易记录信息中的历史环境信息是否匹配；
    若匹配，则将所述业务请求识别为可信的业务请求，并执行变更手机号码的业务操作。
  2. 根据权利要求1所述的方法，其特征在于，所述变更手机号码的业务请求中还携带变更后的手机号码；
    所述判断所述第一用户的当前环境信息与所述至少一个历史交易记录信息中的历史环境信息是否匹配，具体为：
    从所述至少一个历史交易记录信息中过滤不包含所述变更后的手机号码的历史交易记录信息，得到过滤后的至少一个历史交易记录信息；
    判断所述第一用户的当前环境信息与过滤后的至少一个历史交易记录信息中的历史环境信息是否匹配。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：建立所述预设的存储单元的步骤，包括：
    预先收集至少一个用户的多个历史交易记录信息，其中，所述历史交易记录信息中包含业务类型信息；
    对至少一个用户中的任一用户，从所述任一用户的多个历史交易记录信息中选取业务类型信息满足预设条件的一个或多个历史交易记录信息；
    将所述任一用户以及所述业务类型信息满足预设条件的一个或多个历史交易记录信息的对应关系加入所述预设的存储单元中；
    重复上述选取以及加入的步骤，直至将至少一个用户以及业务类型信息满足预设条件的一个或多个历史交易记录信息的对应关系加入所述预设的存储单元中。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述环境信息包括以下一 种或者多种信息：
    用户的互联网协议IP地址信息、用户的多媒体访问控制MAC地址信息、用户的设备相关信息和用户的操作系统信息。
  5. 根据权利要求4所述的方法，其特征在于，所述判断所述第一用户的当前环境信息与所述至少一个历史交易记录信息中的历史环境信息是否匹配，具体为：
    读取一个历史交易记录信息中的历史环境信息，依次将历史环境信息中的每种信息与当前环境信息中对应的信息进行比对，并统计比对一致的信息个数；
    根据比对一致的信息个数，确定对应所述一个历史交易记录信息的评分结果；
    重复执行上述比对以及确定评分结果的步骤，直至确定对应至少一个历史交易记录信息的评分结果；
    根据确定的对应至少一个历史交易记录信息的评分结果，确定总的结果值；
    根据所述总的结果值，判断所述第一用户的当前环境信息与所述至少一个历史交易记录信息中的历史环境信息是否匹配。
  6. 一种变更手机号码的业务请求的识别装置，其特征在于，该装置包括：接收单元、读取单元、判断单元和执行单元；
    所述接收单元，用于接收第一用户发送的变更手机号码的业务请求，所述业务请求中携带所述第一用户的标识信息以及当前环境信息；
    所述读取单元，用于根据所述接收单元接收的所述第一用户的标识信息，从预设的存储单元中读取对应的至少一个历史交易记录信息，其中，所述预设的存储单元用于记录至少一个用户的业务类型信息满足预设条件的一个或多个历史交易记录信息，所述历史交易记录信息包含历史环境信息；
    所述判断单元，用于判断所述第一用户的当前环境信息与所述读取单元读取的所述至少一个历史交易记录信息中的历史环境信息是否匹配；
    所述执行单元，用于若所述当前环境信息与所述历史环境信息匹配，将所述业务请求识别为可信的业务请求，并执行变更手机号码的业务操作。
  7. 根据权利要求6所述的装置，其特征在于，所述变更手机号码的业务请求中还携带变更后的手机号码；
    所述判断单元具体用于：
    从所述至少一个历史交易记录信息中过滤不包含所述变更后的手机号码的历史交易记录信息，得到过滤后的至少一个历史交易记录信息；
    判断所述第一用户的当前环境信息与过滤后的至少一个历史交易记录信息中的历史环境信息是否匹配。
  8. 根据权利要求6或7所述的装置，其特征在于，所述装置还包括：建立单元，用于预先收集至少一个用户的多个历史交易记录信息，其中，所述历史交易记录信息中包含业务类型信息；
    对至少一个用户中的任一用户，从所述任一用户的多个历史交易记录信息中选取业务类型信息满足预设条件的一个或多个历史交易记录信息；
    将所述任一用户以及所述业务类型信息满足预设条件的一个或多个历史交易记录信息的对应关系加入所述预设的存储单元中；
    重复上述选取以及加入的步骤，直至将至少一个用户以及业务类型信息满足预设条件的一个或多个历史交易记录信息的对应关系加入所述预设的存储单元中。
  9. 根据权利要求6-8任一项所述的装置，其特征在于，所述环境信息包括以下一种或者多种信息：
    用户的互联网协议IP地址信息、用户的多媒体访问控制MAC地址信息、用户的设备相关信息和用户的操作系统信息。
  10. 根据权利要求9所述的装置，其特征在于，所述判断单元具体用于：
    读取一个历史交易记录信息中的历史环境信息，依次将历史环境信息中的每种信息与当前环境信息中对应的信息进行比对，并统计比对一致的信息个数；
    根据比对一致的信息个数，确定对应所述一个历史交易记录信息的评分结果；
    重复执行上述比对以及确定评分结果的步骤，直至确定对应至少一个历史交易记录信息的评分结果；
    根据确定的对应至少一个历史交易记录信息的评分结果，确定总的结果值；
    根据所述总的结果值，判断所述第一用户的当前环境信息与所述至少一个历史交易记录信息中的历史环境信息是否匹配。
PCT/CN2016/108626 2015-12-14 2016-12-06 变更手机号码的业务请求的识别方法及装置 WO2017101703A1 (zh)

Priority Applications (11)

Application Number Priority Date Filing Date Title
AU2016372749A AU2016372749A1 (en) 2015-12-14 2016-12-06 Method and apparatus for recognizing service request to change mobile phone number
JP2018530877A JP6629973B2 (ja) 2015-12-14 2016-12-06 携帯電話番号を変更するためのサービス要求を認識する方法及び装置
KR1020187019450A KR102060262B1 (ko) 2015-12-14 2016-12-06 이동전화번호를 변경하기 위한 서비스 요청을 인식하기 위한 방법 및 장치
MYPI2018702212A MY193475A (en) 2015-12-14 2016-12-06 Method and apparatus for recognizing service request to change mobile phone number
SG11201805014PA SG11201805014PA (en) 2015-12-14 2016-12-06 Method and apparatus for recognizing service request to change mobile phone number
EP16874760.8A EP3373521A4 (en) 2015-12-14 2016-12-06 METHOD AND APPARATUS FOR RECOGNIZING A SERVICE REQUEST TO CHANGE A MOBILE PHONE NUMBER
US16/005,404 US10149152B2 (en) 2015-12-14 2018-06-11 Method and apparatus for recognizing service request to change mobile phone number
PH12018501283A PH12018501283A1 (en) 2015-12-14 2018-06-14 Method and apparatus for recognizing service request to change mobile phone number
US16/206,220 US10327134B2 (en) 2015-12-14 2018-11-30 Method and apparatus for recognizing service request to change mobile phone number
AU2019101568A AU2019101568A4 (en) 2015-12-14 2019-12-12 Method and apparatus for recognizing service request to change mobile phone number
AU2020202997A AU2020202997B2 (en) 2015-12-14 2020-05-06 Method and apparatus for recognizing service request to change mobile phone number

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510927308.5A CN106878970B (zh) 2015-12-14 2015-12-14 变更手机号码的业务请求的识别方法及装置
CN201510927308.5 2015-12-14

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/005,404 Continuation US10149152B2 (en) 2015-12-14 2018-06-11 Method and apparatus for recognizing service request to change mobile phone number

Publications (1)

Publication Number Publication Date
WO2017101703A1 true WO2017101703A1 (zh) 2017-06-22

Family

ID=59055806

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/108626 WO2017101703A1 (zh) 2015-12-14 2016-12-06 变更手机号码的业务请求的识别方法及装置

Country Status (10)

Country Link
US (2) US10149152B2 (zh)
EP (1) EP3373521A4 (zh)
JP (1) JP6629973B2 (zh)
KR (1) KR102060262B1 (zh)
CN (2) CN106878970B (zh)
AU (3) AU2016372749A1 (zh)
MY (1) MY193475A (zh)
PH (1) PH12018501283A1 (zh)
SG (1) SG11201805014PA (zh)
WO (1) WO2017101703A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109120798B (zh) * 2018-09-30 2021-01-08 维沃移动通信有限公司 绑定应用的识别处理方法和移动终端
CN109905398B (zh) * 2019-03-13 2020-07-24 北京字节跳动网络技术有限公司 手机号换绑验证方法、装置、设备及存储介质
CN110209820B (zh) * 2019-06-05 2023-06-06 腾讯科技（深圳）有限公司 用户标识检测方法、装置及存储介质
CN114071450B (zh) * 2020-08-05 2023-07-21 中国移动通信集团重庆有限公司 换机换卡行为的识别方法及装置
CN113610078B (zh) * 2021-07-27 2024-03-12 递易（上海）智能科技有限公司 一种手机号识别结果的校准的方法及设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102325062A (zh) * 2011-09-20 2012-01-18 北京神州绿盟信息安全科技股份有限公司 异常登录检测方法及装置
CN103593376A (zh) * 2012-08-17 2014-02-19 阿里巴巴集团控股有限公司 一种采集用户行为数据的方法及装置
CN104469768A (zh) * 2014-11-06 2015-03-25 中国联合网络通信集团有限公司 基于应用软件的用户身份校验方法和装置
CN104516918A (zh) * 2013-09-30 2015-04-15 深圳市腾讯计算机系统有限公司 用户身份信息的维护方法、装置、服务器及系统
CN104580091A (zh) * 2013-10-21 2015-04-29 深圳市腾讯计算机系统有限公司 一种身份验证方法、装置及系统
CN104902033A (zh) * 2014-03-05 2015-09-09 腾讯科技（深圳）有限公司 登陆地址记录方法及装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPWO2006109462A1 (ja) * 2005-04-05 2008-10-16 松下電器産業株式会社 無線通信システムおよび無線通信方法
WO2008147353A1 (en) * 2007-05-29 2008-12-04 Heffez Guy S Method and system for authenticating internet user indentity
KR100645296B1 (ko) * 2005-07-05 2006-11-14 에스케이 텔레콤주식회사 이동통신 단말기 전화번호 변경 방법
US7979899B2 (en) * 2008-06-02 2011-07-12 Microsoft Corporation Trusted device-specific authentication
KR101072930B1 (ko) * 2009-05-21 2011-10-17 주식회사 신한은행 통신번호 변경요청 승인 방법
KR101189804B1 (ko) * 2010-11-19 2012-10-10 넷큐브테크놀러지 주식회사 무선랜 접속 프로파일 생성 시스템 및 방법
US10257194B2 (en) * 2012-02-14 2019-04-09 Airwatch Llc Distribution of variably secure resources in a networked environment
WO2014078569A1 (en) * 2012-11-14 2014-05-22 The 41St Parameter, Inc. Systems and methods of global identification
CN103338148B (zh) * 2013-06-28 2018-11-23 小米科技有限责任公司 通讯录的更新方法及装置
CN104348809B (zh) * 2013-08-02 2018-09-04 深圳市腾讯计算机系统有限公司 网络安全监控方法及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102325062A (zh) * 2011-09-20 2012-01-18 北京神州绿盟信息安全科技股份有限公司 异常登录检测方法及装置
CN103593376A (zh) * 2012-08-17 2014-02-19 阿里巴巴集团控股有限公司 一种采集用户行为数据的方法及装置
CN104516918A (zh) * 2013-09-30 2015-04-15 深圳市腾讯计算机系统有限公司 用户身份信息的维护方法、装置、服务器及系统
CN104580091A (zh) * 2013-10-21 2015-04-29 深圳市腾讯计算机系统有限公司 一种身份验证方法、装置及系统
CN104902033A (zh) * 2014-03-05 2015-09-09 腾讯科技（深圳）有限公司 登陆地址记录方法及装置
CN104469768A (zh) * 2014-11-06 2015-03-25 中国联合网络通信集团有限公司 基于应用软件的用户身份校验方法和装置

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US10327134B2 (en) 2019-06-18
US20180295504A1 (en) 2018-10-11
US10149152B2 (en) 2018-12-04
AU2016372749A1 (en) 2018-06-28
EP3373521A4 (en) 2019-05-08
JP6629973B2 (ja) 2020-01-15
AU2020202997B2 (en) 2021-11-25
CN106878970A (zh) 2017-06-20
KR102060262B1 (ko) 2019-12-27
PH12018501283A1 (en) 2019-01-21
KR20180092319A (ko) 2018-08-17
CN106878970B (zh) 2020-05-05
MY193475A (en) 2022-10-15
US20190098491A1 (en) 2019-03-28
AU2020202997A1 (en) 2020-05-28
EP3373521A1 (en) 2018-09-12
AU2019101568A4 (en) 2020-01-23
CN111542043A (zh) 2020-08-14
SG11201805014PA (en) 2018-07-30
CN111542043B (zh) 2023-01-31
JP2019504545A (ja) 2019-02-14

Similar Documents

Publication Publication Date Title
WO2017101703A1 (zh) 变更手机号码的业务请求的识别方法及装置
US9491182B2 (en) Methods and systems for secure internet access and services
US20230045378A1 (en) Non-repeatable challenge-response authentication
KR102179152B1 (ko) 사회 관계 데이터를 이용한 클라이언트 인증
CN106469261B (zh) 一种身份验证方法及装置
EP3211825B1 (en) Trusted terminal verification method and apparatus
CN104980402B (zh) 一种识别恶意操作的方法及装置
US11429698B2 (en) Method and apparatus for identity authentication, server and computer readable medium
CN105516133A (zh) 用户身份的验证方法、服务器及客户端
US10769270B2 (en) Password protection question setting method and device
WO2021004123A1 (zh) 基于区块链的信息处理装置、方法及存储介质
CN105205365B (zh) 一种生物特征信息的注册和认证方法及装置
CN106921626B (zh) 一种用户注册方法及装置
CN108809909A (zh) 数据处理方法及数据处理装置
CN108449367B (zh) 管理用户登录安全性的方法、装置、电子设备及可读介质
CN117874733B (zh) 一种交易执行方法以及系统
CN110032843B (zh) 一种账号注册方法、装置、电子设备及存储介质
CN117216739A (zh) 一种身份验证方法、装置、设备及介质
CN116703583A (zh) 策略生成方法、装置、设备及存储介质
CN117237110A (zh) 一种基于DPoS的交易方法、装置、设备及介质

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: 16874760

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 11201805014P

Country of ref document: SG

Ref document number: 2018530877

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 12018501283

Country of ref document: PH

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016372749

Country of ref document: AU

Date of ref document: 20161206

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20187019450

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020187019450

Country of ref document: KR