CN108629582B - Service processing method and device - Google Patents

Service processing method and device Download PDF

Info

Publication number
CN108629582B
CN108629582B CN201710160542.9A CN201710160542A CN108629582B CN 108629582 B CN108629582 B CN 108629582B CN 201710160542 A CN201710160542 A CN 201710160542A CN 108629582 B CN108629582 B CN 108629582B
Authority
CN
China
Prior art keywords
transaction data
historical transaction
agent
data samples
historical
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201710160542.9A
Other languages
Chinese (zh)
Other versions
CN108629582A (en
Inventor
何进龙
李路
易旭昆
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201710160542.9A priority Critical patent/CN108629582B/en
Publication of CN108629582A publication Critical patent/CN108629582A/en
Application granted granted Critical
Publication of CN108629582B publication Critical patent/CN108629582B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • 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/382—Payment protocols; Details thereof insuring higher security of transaction
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Abstract

The application discloses a service processing method and device, and belongs to the technical field of networks. The method comprises the following steps: receiving a request message of an agent account, and inquiring whether the agent account belongs to a blacklist, wherein the blacklist is used for storing the agent accounts of which historical transactions do not accord with preset rules, each agent account stored by the blacklist is determined based on a plurality of historical transaction data samples of each agent account, each historical transaction data sample comprises historical position information of each agent user and each individual user when each historical transaction is realized, and when the agent account is determined not to belong to the blacklist, service processing is carried out based on the request message. Therefore, each historical transaction data sample comprises position information of both transaction parties, the position information can be obtained through a positioning technology, whether the preset rule is met or not when the agent account number requests for the service can be identified without additionally adding hardware equipment, and cost is reduced.

Description

Service processing method and device
Technical Field
The present application relates to the field of network technologies, and in particular, to a service processing method and apparatus.
Background
A Mobile payment (MM) system refers to a system capable of implementing various network transaction services, and mainly includes a terminal and an MM management server, for example, capable of implementing a deposit service, a transfer service, a consumption service, and the like. The MM management server is used for managing various network transaction services, and a user can register an account in the MM management server through a terminal and log in the MM management server based on the registered account to perform various network transactions.
In a practical application scenario, the users include individual users and agent users, and the agent users exist in the form of units or organizations, and the individual users can manage various services, such as deposit services, through the agent users. In the MM management server, a large amount of deposit amount is generally stored in the agent account of the agent user, for example, when an individual user needs to transact deposit transaction, the agent user logs in the MM management server through a terminal based on the agent account to request the MM management server to transfer a certain deposit amount from the agent account to the individual account, thereby realizing the deposit transaction of the individual user. In order to encourage users to use the MM system, the operator of the MM management server typically provides that the agent user may avoid handling certain services, such as deposit services, for individual users, and certain handling fees, such as transfer services, for other services. In order to avoid additional handling fees, some individual users may request the broker user to handle other services requiring handling fees through a hands-free service handling channel. For example, if the provision of deposit services may be exempt from handling fees, individual user A may request that the agent user transfer funds to individual user B's individual account number in a deposit channel, which is against the operator's provision.
In the prior art, in order to identify the business transacted by the agent account and judge whether the business transacted by the agent account has violation, an identity information identification mechanism is added in the MM system. That is, in the service processing process, if the agent account requests to transact the service free of the procedure fee, the agent account is required to carry the identity information of the individual user who needs to transact the service in the transmitted request message, for example, the identity information is fingerprint information or the like. The MM management server checks the identity information, if the identity information is determined to be the identity information of the individual account to be deposited, the MM management server performs service processing based on the request message, otherwise, the MM management server does not perform the operation of performing service processing based on the request message. In order to acquire the identity information of the individual user, an information acquisition device needs to be added to the MM system, for example, the information acquisition device is a fingerprint acquisition device for recording fingerprint information of the individual user. However, this requires additional hardware devices, resulting in higher cost.
Disclosure of Invention
In order to solve the problem that in the prior art, additional hardware equipment is needed to be added, so that the cost is high, the application provides a service processing method and a service processing device. The technical scheme is as follows:
in a first aspect, a method for processing a service is provided, where the method includes:
receiving a request message of an agent account; inquiring whether the agent account belongs to a blacklist or not, wherein the blacklist is used for storing the agent accounts of which historical transactions do not accord with preset rules, each agent account stored in the blacklist is determined based on a plurality of historical transaction data samples of each agent account, and each historical transaction data sample comprises historical position information of each agent user and each individual user when each historical transaction is realized; and when determining that the agent account does not belong to the blacklist, performing service processing based on the request message.
In the embodiment of the invention, when a request message of the agent account is received, whether the agent account belongs to a blacklist or not is inquired, and when the agent account is determined not to belong to the blacklist, service processing is carried out based on the request message. The agent account number of which the historical transaction does not accord with the preset rule and is stored in the blacklist is determined based on a plurality of historical transaction data samples of each agent account number, each historical transaction data sample comprises position information of both transaction parties, and the position information can be obtained through a positioning technology, so that the service type requested by the agent account number can be identified without additionally adding hardware equipment, and the cost is reduced.
Optionally, before the querying whether the agent account belongs to the blacklist, the method further includes: acquiring a plurality of historical transaction data samples of the agent account in a specified time period, wherein each historical transaction data sample comprises historical position information of the agent user and each individual user when each historical transaction is realized; obtaining all appointed historical transaction data samples from the plurality of historical transaction data samples, wherein the appointed historical transaction data samples comprise historical position information of the agent user and individual users related to the historical transactions when the historical transactions are realized, and the historical position information does not belong to the same position area; and judging whether to store the agent account number into the blacklist or not based on all the acquired designated historical transaction data samples.
In a specific implementation, the MM management server periodically performs data mining and big data analysis on historical transaction data samples transacted by each agent account to identify whether illegal agent transactions exist. When such a transaction is identified, the agent account number may be stored on a blacklist. Therefore, when the MM management server receives the request message, whether the service processing is carried out based on the request message can be judged according to the agent account and the blacklist. In addition, in the embodiment of the invention, big data analysis is carried out based on the position information in the historical transaction data sample to judge whether the historical transaction of the agent account accords with the preset rule or not, and no additional hardware equipment is needed, so that the cost is saved.
Optionally, the determining whether to store the agent account into the blacklist based on all the obtained designated historical transaction data samples includes: counting the number of all the designated historical transaction data samples; and if the number of all the designated historical transaction data samples is greater than or equal to a first preset threshold value, storing the agent account number into the blacklist.
In a specific implementation, if the number of the specified historical transaction data samples in the plurality of historical transaction data samples is large, it may be said that the agent user often transacts illegal business for an individual user, and in this case, the MM management server determines that the agent user has an illegal condition, and stores the agent account number in a blacklist.
Optionally, the determining whether to store the agent account into the blacklist based on all the obtained designated historical transaction data samples includes: acquiring the number of stored appointed historical transaction data samples of each agent account; and if the number of the appointed historical transaction data samples of the agent account number in the obtained number is the maximum, storing the agent account number into the blacklist.
In a specific implementation, if the number of the specified historical transaction data samples of the agent account is the largest, it is determined that the number of times that the agent user corresponding to the agent account transacts the violation service for the individual user is the largest, and in this case, the MM management server determines that the agent user has the violation condition, and stores the agent account in a blacklist.
Optionally, the determining whether to store the agent account into the blacklist based on all the obtained designated historical transaction data samples includes: when each designated historical transaction data sample further comprises an individual account number, counting the number of the designated historical transaction data samples corresponding to each individual account number in all the designated historical transaction data samples to obtain the number of a plurality of individual account number samples; and if the individual account number sample number which is greater than or equal to a second preset threshold value exists in the plurality of individual account number sample numbers, storing the agent account number into the blacklist.
In a specific implementation, if the number of individual account samples greater than or equal to a second preset threshold exists in the plurality of individual account sample numbers, it is indicated that the agent user transacts the violation service for a certain individual user for multiple times, and in this case, the MM management server determines that the agent user has a violation condition, and stores the agent account in a blacklist.
Optionally, the determining whether to store the agent account into the blacklist based on all the obtained designated historical transaction data samples includes: when each appointed historical transaction data sample also comprises a transaction amount, counting the number of the appointed historical transaction data samples of which the transaction amounts are larger than a preset amount and which are included in all the appointed historical transaction data samples; and if the transaction amount included in the appointed historical transaction data sample is larger than the number of the appointed historical transaction data samples with the preset amount and is larger than or equal to a third preset threshold value, storing the agent account number into the blacklist.
In a specific implementation, if the number of the designated historical transaction data samples of which the transaction limit is greater than the preset limit and which include the transaction limit is greater than or equal to a third preset threshold, the agent business user transacts the violation business with a large limit for many times, and in this case, the MM management server determines that the agent business user has a violation condition and stores the agent account number in a blacklist.
Optionally, the determining whether to store the agent account into the blacklist based on all the obtained designated historical transaction data samples includes: when each appointed historical transaction data sample further comprises transaction time, counting the number of appointed historical transaction data samples, wherein the transaction time in all the appointed historical transaction data samples is within a preset time range; and if the number of the appointed historical transaction data samples of which the transaction time is in a preset time range is greater than or equal to a fourth preset threshold value, storing the agent account number into the blacklist.
In a specific implementation, if the number of the designated historical transaction data samples of which the transaction time is within the preset time range and which are included in the designated historical transaction data samples is greater than or equal to a fourth preset threshold, it indicates that the agent business user transacts the violation business for the individual user for many times in abnormal working time, and in this case, the MM management server determines that the agent business user has the violation situation, and stores the agent business account number into the blacklist.
Optionally, after the service processing is performed based on the request message, the method further includes:
when the request message carries a first mobile subscriber international integrated services digital network (MSISDN) number and a second MSISDN, generating a position query request based on the first MSISDN and the second MSISDN, wherein the first MSISDN is the MSISDN of a target individual subscriber requesting service handling, and the second MSISDN is the MSISDN of the agent subscriber; sending a location query request to a location based server LBS, so that the LBS queries and returns location information of the target individual user and the agent user based on the first MSISDN and the second MSISDN; receiving the position information of the target individual user and the agent user sent by the LBS; generating historical transaction data samples based on the location information of the target individual user and the agent user.
In a specific implementation, in order to facilitate the subsequent MM management server to continue data statistical analysis, after the MM management server performs service processing based on the request message when determining that the agent account does not belong to the blacklist, a historical transaction data sample may be generated based on the current transaction, so that the accuracy of data analysis may be improved.
In a second aspect, a service processing apparatus is provided, where the apparatus is configured to implement the service processing method according to the first aspect.
In a third aspect, an embodiment of the present invention provides a computer storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method described in the first aspect.
In a fourth aspect, embodiments of the present invention also provide a computer program product containing instructions, which when run on a computer, cause the computer to perform the method according to the first aspect.
In a fifth aspect, an embodiment of the present invention further provides a communication chip, where the communication chip is applied in an MM management server, and the communication chip includes: the MM management server comprises an input/output interface, a memory and at least one processor, wherein the memory and the input/output interface are communicated with the at least one processor through a bus, the memory stores program codes, and the at least one processor is used for calling the program codes so that the MM management server executes the business processing method of the first aspect.
The technical effect obtained by the second aspect of the embodiment of the present invention is similar to the technical effect obtained by the corresponding technical means in the first aspect, and is not described herein again.
The beneficial effect that technical scheme that this application provided brought is: and when a request message of the agent account is received, inquiring whether the agent account belongs to a blacklist, and when the agent account is determined not to belong to the blacklist, performing service processing based on the received request message. The agent account number of which the historical transaction does not accord with the preset rule and is stored in the blacklist is determined based on a plurality of historical transaction data samples of each agent account number, each historical transaction data sample comprises position information of both transaction parties, and the position information can be obtained through a positioning technology, so that whether the agent account number accords with the preset rule or not when the agent account number requests for service can be identified without additionally adding hardware equipment, and the cost is reduced.
Drawings
Fig. 1 is a schematic structural diagram of an MM system according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a computer device according to an embodiment of the present invention;
fig. 3 is a flowchart of a service processing method according to an embodiment of the present invention;
fig. 4A is a schematic structural diagram of a service processing apparatus according to an embodiment of the present invention;
fig. 4B is a schematic structural diagram of another service processing apparatus according to an embodiment of the present invention;
fig. 4C is a schematic structural diagram of another service processing apparatus according to an embodiment of the present invention.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Fig. 1 is a schematic structural diagram of an MM system according to an embodiment of the present invention. The MM system mainly includes a terminal 110 and an MM management server 120, and the terminal 110 may be connected to the MM management server 120 through a wired network or a wireless network.
In an actual application scenario, the MM system may include a plurality of terminals 110, and here, only one terminal is exemplarily shown. The MM client may be installed in the terminal 110, and the terminal 110 may transmit a request message to the MM management server 120 through the MM client to request the MM management server 120 to implement various network transaction services. Alternatively, the terminal 110 may open an MM-related web page by operating a browser and transmit a request message to the MM management server 120 through the related web page to request the MM management server 120 to implement various network transaction services. Still alternatively, third party cooperative software may be installed in the terminal 110, and the terminal 110 sends a request message to the MM management server 120 through the third party cooperative software to request the MM management server 120 to implement various network transaction services. In addition, the terminal 110 may send a request message to the MM management server 120 through a conventional telecommunication channel to request the MM management server 120 to implement various network transaction services. The terminal 110 may be a device such as a mobile phone, a tablet computer, or a computer, which is not limited in the embodiment of the present invention.
The MM management server 120 is mainly used to implement the service processing method provided in the embodiment of the present invention. Referring to fig. 1, the MM management server 120 mainly includes a transaction access interface 1201, a base layer management service module 1203 and a transaction management service module 1202.
The transaction access Interface 1201 is mainly used to support access of the terminal 120, for example, the transaction access Interface 1201 may include any one of an Unstructured Supplementary Service Data (USSD)/Short Messaging Service (SMS) access Interface, an Application program (APP) access Interface, an Application Programming Interface (API), and a web portal access Interface (web portal). The USSD/SMS access interface may enable the terminal 110 to access the MM management server 120 through a conventional telecommunication channel, the APP access interface may enable the terminal 110 to access the MM management server 120 through an MM client, the API access interface may enable the terminal 110 to access the MM management server 120 through third-party collaboration software, and the web portal may enable the terminal 110 to access the MM management server 120 through a related web page.
The basic level management service module 1203 may include a database access unit, a rule engine unit, a security service unit, a cache unit, and the like. The MM management server may store various data information through the database, for example, the data information may include historical transaction data samples and the like. The rule engine unit may be configured to determine rules of various network transactions, the security service unit may be configured to perform identity verification on an account requesting transaction, and the cache unit may be configured to cache various data information.
The transaction management service module 1202 is mainly used for managing and implementing various network transaction services, and the transaction management service module 1202 may include a deposit processing (cash in) unit, a withdrawal processing (cash out) unit, a transfer processing unit, a bill processing (bill payment) unit, and a goods transaction processing (buy goods) unit. The system comprises a deposit processing unit, a withdrawal processing unit, a transfer processing unit, a bill processing unit, an article transaction processing unit and the like, wherein the deposit processing unit is used for processing deposit services, the withdrawal processing unit is used for processing withdrawal services, the transfer processing unit is used for processing transfer services, the bill processing unit is used for processing consumption bills in an MM system, and the article transaction processing unit can be used for processing transaction services and the like.
It should be noted that the Transfer processing unit is mainly used for implementing a Point-to-Point (P2P) Transfer (Transfer) service. That is, in the MM system, the Transfer from one account to another is usually implemented in the P2P Transfer mode, and this kind of transaction may be initiated by an individual user through a terminal, and after receiving the Transfer transaction request, the MM management server 120 may implement the Transfer transaction through the Transfer processing unit.
Currently, for an individual account, an operator generally needs to charge a certain percentage of commission fees during the Transfer process, for example, if an individual user a wants to Transfer 1000 dollars to an individual user B, the funds can be transferred to the individual account of the individual user B through P2P Transfer, and assuming that the commission fee for the Transfer is 1%, the individual user a actually needs to pay 1010 dollars.
In order to encourage the use of the users, in MM systems, it is generally not necessary to pay a commission for certain services, for example, for credit services, i.e. if the user deals with the credit service via a broker, the commission is generally not paid. Thus, some individual users may request the agent user to perform money transfer in a deposit transaction when they want to transfer money to other individual users, for example, if individual user a wants to transfer money to individual user B, the agent user may be requested to deposit money into the individual account of individual user B, and such a transaction belongs to a violation transaction. Therefore, the embodiment of the present invention provides a service processing method, which can determine whether to process a service for an account of an agent requesting the service without adding additional hardware devices, and a specific implementation process of the service processing method may refer to the embodiment described in fig. 3 below.
In the embodiment of the present invention, the case where the payment of the handling fee is not required when the deposit transaction is performed is described as an example. Of course, in another embodiment, depending on different policies established by an operator, a commission fee may not be paid for other services, but the method provided in the embodiment of the present invention may also be used to perform service processing, which is not limited in the embodiment of the present invention.
It should be noted that the MM management server 120 may be one server or a server cluster composed of a plurality of servers, which is not limited in this embodiment of the present invention.
Further, the MM system further includes a positioning device 130, and the positioning device 130 may be connected to the MM management server 120 through a communication network. The positioning device 130 is mainly used for implementing a positioning function, in a specific implementation, the positioning device 130 may be a wireless access device such as a base station, a Location Based Service (LBS) is configured in the wireless access device, and the LBS may be used for implementing the positioning function, so that the positioning function may be implemented through an existing LBS of an operator without adding additional devices in the MM system, thereby saving cost.
It should be noted that the MM system may further include a Big Data Platform (BDP) 140, and in a specific implementation, the BDP 140 implements historical Data information mining and analyzing processes involved in the service processing method provided in the embodiment of the present invention, and the historical Data information may be a historical transaction Data sample. That is, the MM management server 120 may invoke the BDP 140 to perform data mining analysis on the historical transaction data samples, which is not limited in the embodiment of the present invention.
Fig. 2 is a schematic structural diagram of a computer device according to an embodiment of the present invention. The MM management server 120 in fig. 1 may be implemented by a computer device shown in fig. 2. Referring to fig. 2, the computer device comprises at least one processor 201, a communication bus 202, a memory 203 and at least one communication interface 204.
The processor 201 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present invention.
The communication bus 202 may include a path that conveys information between the aforementioned components.
The Memory 203 may be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory 203 may be self-contained and coupled to the processor 201 via the communication bus 202. The memory 203 may also be integrated with the processor 201.
Communication interface 204, using any transceiver or the like, is used for communicating with other devices or communication Networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.
In particular implementations, processor 201 may include one or more CPUs, such as CPU0 and CPU1 shown in fig. 2, as one embodiment.
In particular implementations, a computer device may include multiple processors, such as processor 201 and processor 205 shown in fig. 2, as one embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).
The computer device may be a general purpose computer device or a special purpose computer device. In a specific implementation, the computer device may be a desktop computer, a laptop computer, a network server, a Personal Digital Assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, or an embedded device. The embodiment of the invention does not limit the type of the computer equipment.
The memory 203 is used for storing program codes for executing the scheme of the application, and the processor 201 controls the execution. The processor 201 is operable to execute program code 206 stored in the memory 203. One or more software modules (e.g., a receiving module, a querying module, a processing module, an obtaining module, a determining module, a generating module, a transmitting module, etc.) may be included in program code 206. The MM management server 120 shown in fig. 1 may determine data for developing an application by the processor 201 and one or more software modules in the program code 206 in the memory 203.
It should be noted that the receiving module herein actually includes a first receiving module and a second receiving module, the obtaining module actually includes a first obtaining module and a second obtaining module, and the generating module actually includes a first generating module and a second generating module.
An embodiment of the present invention provides a service processing method, which is shown in fig. 3 and includes:
301: the first terminal transmits a request message to the MM management server based on the agent account, and the MM management server receives the request message of the agent account.
The first terminal is a terminal used by an agent user, and in general, the first terminal is a mobile phone, that is, when the agent user transacts services for an individual user, the first terminal is generally implemented by a mobile phone. In a possible implementation manner, the MM client may be installed in the mobile phone, and the agent business user may input an agent business account in the MM client, and send the request message to the MM management server through the MM client based on the agent business account. In a specific implementation, the request message may carry information such as the agent account of the agent user, the individual account of the individual user requesting to handle the service, and the transaction amount.
Of course, the first terminal is only a mobile phone as an example, in another embodiment, the first terminal may also be a device such as a tablet computer, and the embodiment of the present invention does not limit this.
Wherein the request message is used for requesting a transaction without paying a commission fee, for example, in an embodiment of the present invention, the request message is used for requesting a deposit transaction.
It should be noted that, in the embodiment of the present invention, the request message is used to request a deposit service as an example, in another embodiment, the request message may also be used to request other services according to different service types of free charges made by an operator, for example, if the operator specifies that a withdrawal service can be free from free charges, the request message may also be used to request a withdrawal service, which is not limited in the embodiment of the present invention.
The MM management server receives the request message and may then verify the identity of the agent user based on the agent account. In a possible implementation manner, the MM management server stores the self-managed agent account, so that the MM management server may determine whether the agent account carried in the request message belongs to the self-managed agent account. And if the agent account carried in the request message belongs to the agent account managed by the user, determining that the agent user passes the verification, otherwise, if the agent account carried in the request message does not belong to the agent account managed by the user, determining that the agent user fails the verification.
Further, in a specific implementation, each agent may include multiple operators, that is, account numbers of multiple operators may correspond to each agent account number, in this case, the request message may also carry account numbers of the operators, and in the process of performing identity verification on the agent account numbers, it is further required to determine whether the account numbers of the operators belong to the agent account numbers, if the account numbers of the operators belong to the agent account numbers, it is determined that the identity verification is passed, and otherwise, if the account numbers of the operators do not belong to the agent account numbers, it is determined that the identity verification is not passed.
It should be noted that the above implementation process of performing identity verification on an agent user based on an agent account is only an example, and in another embodiment, the MM management server may also perform identity verification on the agent user based on the agent account in other manners, which is not limited in the embodiment of the present invention.
After the identity of the agent user is verified by the MM management server, the services handled by the agent user need to be identified, which is described in detail below.
302: the MM management server inquires whether the agent account belongs to a blacklist, the blacklist is used for storing the agent accounts of which historical transactions do not accord with preset rules, each agent account stored by the blacklist is determined based on a plurality of historical transaction data samples of each agent account, and each historical transaction data sample comprises historical position information of each agent user and each individual user when each historical transaction is realized.
The preset rule may be set by an operator according to an actual operation policy, which is not limited in the embodiment of the present invention.
In an actual application scenario, the MM management server may determine the business transaction credit of the agent account according to the historical transaction business of the agent account, so as to automatically identify the business type requested by the request message of the agent account. Further, the MM management server may determine the type of the handled service according to the location information of the historical service handling time and the location information of the individual user requesting to handle the service, for example, if it is determined that the agent user is currently in the same location area as the individual user according to the location information of the historical service handling time and the location information of the individual user requesting to handle the service, it may be determined that the handled service conforms to a preset rule, otherwise, it may be determined that the handled service does not conform to the preset rule.
Therefore, in each business of the historical transaction, the MM management server acquires the position information of the agent user and the position information of the individual user requesting to transact the business, and produces a historical transaction data sample according to the acquired position information of the agent user and the position information of the individual user requesting to transact the business, so that the MM management server can count and analyze the business transaction credit of the agent account number based on the historical transaction data sample.
That is, the MM management server periodically performs data mining and big data analysis on historical transaction data samples transacted by various agent accounts to identify suspected agent transactions such as transfers. When the transaction is identified, the agent account may be stored in a blacklist, that is, in the embodiment of the present invention, it may be determined whether the historical transaction of the agent account meets a preset rule according to the blacklist. If the agent account does not belong to the blacklist, it can be determined that the historical transaction of the agent account conforms to a preset rule, and if the agent account belongs to the blacklist, it can be determined that the historical transaction of the agent account does not conform to the preset rule.
Before the MM management server queries whether the agent account belongs to the blacklist, it needs to determine whether to store the agent account of the agent user in the blacklist, and according to different preset rules, the specific implementation may include the following steps:
3021: and acquiring a plurality of historical transaction data samples of the agent account in a specified time period, wherein each historical transaction data sample comprises historical position information of the agent user and each individual user when each historical transaction is realized.
In an actual application scenario, for each historical transaction requested by the agent account, the MM management server records the location information of the individual user requesting the service and the location information of the agent user handling the service. In a possible implementation manner, the MM management server may obtain location information of the individual user and the agent user from the LBS according to Mobile Subscriber International Integrated Services Digital Network/Public Switched Telephone Network Number (MSISDN) used by the individual user and the agent user, respectively.
In a specific implementation, a request message sent by each agent account needs to carry its MSISDN and the MSISDN of the individual account requesting to transact a service, and the MM management server generates a location query request based on the MSISDN of the agent account and the MSISDN of the individual account requesting to transact a service. Then, the MM management server sends the location query request to the LBS, so that the LBS queries and returns the location information of the agent user and the location information of the individual user requesting to transact the service based on the MSISDN of the agent account and the MSISDN of the individual account requesting to transact the service. After receiving the data, the MM management server generates a historical transaction data sample based on the position information of the agent user and the position information of the individual user requesting to transact the business.
It should be noted that, the above implementation manner of obtaining the location information is only described by taking a case that the terminals used by the agent user and the individual user are both mobile phones, in another implementation manner, when the terminal used by the agent user or the individual user is not a mobile phone, the location information may be determined through a GIS positioning technology, and in the process of implementing the transaction service, the determined location information is sent to the MM management server.
For example, if the transaction amount historically handled by the agent is large, the designated time period may be selected as a week or a day, and if the transaction amount historically handled by the agent is small, the designated time period may be selected as a month.
The specified time period is 30 days as an example, that is, the MM management server may obtain a plurality of historical transaction data samples within the 30 days every 30 days, where each historical transaction data sample may be a historical transaction running list, and each historical transaction running list is valid. In this context, valid is to be understood as a historical transaction list of successfully completed transactions.
In a specific implementation, the MM management server may obtain all historical transaction running lists within 30 days, and extract all historical transaction running lists into a specified data carrier, for example, the data carrier may be a relational database such as Mysql or Oracle, or may be a Nosql database such as Redis or MongoDB. Then, all the extracted historical transaction running lists are screened, for example, the historical transaction running list in which the transaction fails or is not completed due to various reasons and the historical transaction running list which does not include the location information (for example, the location information may not be obtained in a state that the terminal is powered off) are deleted, so that the plurality of historical transaction data samples are obtained. Therefore, the phenomenon of distortion of subsequent statistical results can be avoided.
3022: and obtaining all appointed historical transaction data samples from the plurality of historical transaction data samples, wherein the appointed historical transaction data samples comprise historical position information of the agent user and the individual user involved in the historical transaction when the historical transaction is realized, and the historical position information does not belong to the same position area.
If the historical location information of the agent user and the individual user involved in the historical transaction when the historical transaction is implemented, which is included in the historical transaction data sample, does not belong to the same location area, it indicates that the agent user does not deposit into the individual account of the individual user, for example, if the individual user a requests the agent user to do deposit transaction, the individual user a and the agent user should be in the same location area, and if the individual user a and the agent user are not in the same location area, it may indicate that the individual user requesting the agent user to handle the deposit may not be the individual user a, for example, the individual user B may want to deposit into the individual account of the individual user a, and such an action does not meet the regulations. Therefore, the MM management server obtains all the designated historical transaction data samples from the plurality of historical transaction data samples, wherein the designated historical transaction data samples comprise the historical position information of the agent user and the individual user involved in the historical transaction when the historical transaction is realized, and the historical position information does not belong to the same position area.
3023: and judging whether to store the agent account number into the blacklist or not based on all the acquired specified historical transaction data samples.
The implementation manner of judging whether to store the agent account number in the blacklist is also different based on all the acquired specified historical transaction data samples according to different preset rules, and may specifically include the following possible implementation manners:
the first mode is as follows: counting the number of all the designated historical transaction data samples, and if the number of all the designated historical transaction data samples is greater than or equal to a first preset threshold value, storing the agent account number into the blacklist.
The first preset threshold may be set by a user (e.g., an operator) in a customized manner according to actual requirements, or may be set by the MM management server in a default manner, which is not limited in the embodiment of the present invention.
If the number of the specified historical transaction data samples in the plurality of historical transaction data samples is larger, the fact that the agent business user frequently transacts illegal deposit business for the individual user can be shown, in this case, the MM management server determines that the agent business user has an illegal condition, and the agent business account number is stored in a blacklist.
The second mode is as follows: and acquiring the number of the stored specified historical transaction data samples of each agent account, and if the number of the specified historical transaction data samples of the agent account in the acquired number is the largest, storing the agent account into the blacklist.
In this implementation manner, the MM management server may count the number of designated historical transaction data samples of each agent account, and if the number of designated historical transaction data samples of the agent account is the largest, determine that the number of times that an agent user corresponding to the agent account transacts the illegal deposit service for an individual user is the largest, in this case, the MM management server determines that the agent user has an illegal condition, and stores the agent account in a blacklist.
The third mode is as follows: when each designated historical transaction data sample also comprises an individual account number, counting the number of the designated historical transaction data samples corresponding to each individual account number in all the designated historical transaction data samples to obtain a plurality of individual account number sample numbers, and if the individual account number sample number which is greater than or equal to a second preset threshold value exists in the plurality of individual account number sample numbers, storing the agent account number into the blacklist.
The second preset threshold may be set by a user (e.g., an operator) in a customized manner according to actual requirements, or may be set by the MM management server in a default manner, which is not limited in the embodiment of the present invention.
In an actual application scenario, each designated historical transaction data sample may include an individual account number, where the individual account number refers to an individual account number for handling a transaction in a transaction service corresponding to the designated historical transaction data sample. And the MM management server counts the number of the appointed historical transaction data samples corresponding to each individual account in all the appointed historical transaction data samples to obtain the number of a plurality of individual account samples. If the individual account number sample number which is greater than or equal to the second preset threshold value exists in the individual account number sample numbers, the fact that the agent user transacts illegal deposit business for a certain individual user for many times is indicated, and under the condition, the MM management server determines that the agent user has illegal conditions, and stores the agent account number into a blacklist.
The fourth mode is that: when each appointed historical transaction data sample also comprises a transaction amount, counting the number of the appointed historical transaction data samples of which the transaction amounts are larger than a preset amount and which are included in all the appointed historical transaction data samples, and if the number of the appointed historical transaction data samples of which the transaction amounts are larger than the preset amount is larger than or equal to a third preset threshold value, storing the agent account number into the blacklist.
The preset quota may be set by a user (e.g., an operator) in a self-defined manner according to actual requirements, or may be set by the MM management server in a default manner, which is not limited in the embodiment of the present invention.
The third preset threshold may be set by a user (e.g., an operator) in a customized manner according to actual requirements, or may be set by the MM management server in a default manner, which is not limited in the embodiment of the present invention.
In a practical application scenario, each specified historical transaction data sample may include a transaction amount. The MM management server counts the number of the appointed historical transaction data samples with transaction limits larger than the preset limit in all the appointed historical transaction data samples, if the number of the appointed historical transaction data samples with transaction limits larger than the preset limit is larger than or equal to a third preset threshold, the agent business user transacts the illegal deposit business with large limit for many times, and under the condition, the MM management server determines that the agent business user has illegal conditions, and stores the agent business account number into a blacklist.
The fifth mode is as follows: when each appointed historical transaction data sample further comprises transaction time, counting the number of the appointed historical transaction data samples of which the transaction time is in a preset time range, and if the number of the appointed historical transaction data samples of which the transaction time is in the preset time range is greater than or equal to a fourth preset threshold, storing the agent account number in the blacklist.
The preset time range may be set by a user (e.g., an operator) in a customized manner according to actual requirements, or may be set by the MM management server in a default manner, which is not limited in the embodiment of the present invention.
The fourth preset threshold may be set by a user (e.g., an operator) in a customized manner according to actual requirements, or may be set by the MM management server in a default manner, which is not limited in the embodiment of the present invention.
In a practical application scenario, each specified historical transaction data sample may include a transaction time. The MM management server may count the number of times that the agent user transacts the illegal deposit service for the individual user within a preset time range, for example, the preset time range may be 12 pm to 3 am, and if the number of the specified historical transaction data samples whose transaction time is within the preset time range included in the specified historical transaction data samples is greater than or equal to a fourth preset threshold, it indicates that the agent user transacts the illegal deposit service for the individual user at an abnormal working time many times, in this case, the MM management server determines that the agent user has an illegal condition, and stores the agent account number in the blacklist.
It should be noted that, in the embodiment of the present invention, it is determined whether to store the agent account in the blacklist based on all the acquired designated historical transaction data samples in the above five implementation manners, and in another embodiment, it may also be determined whether to store the agent account in the blacklist in other manners.
That is, the MM management server may perform statistical analysis according to different information according to actual requirements, for example, at least two of the five implementation manners may be combined, for example, in a possible implementation manner, when each specified historical transaction data sample further includes an individual account and a transaction time, the MM management server may further count the number of the specified historical transaction data samples within a preset time range for each individual account, and if there is more than a certain number in each counted number, store the agent account into the blacklist, that is, count a case that the agent account initiates a large amount of inconsistent positions for an individual user within a certain time.
It should be noted that, in practical application, not only may the service identification be performed in the above manner, but also the MM management server may obtain a historical transaction data sample of an individual account currently requesting to handle the deposit service, and determine whether there is a large difference in the position of the deposit transaction position of the individual account according to the historical transaction data sample of the individual account, so as to determine whether to handle the deposit service for the request message sent by the agent account. If the historical deposit transactions of the individual account are all in the same relatively fixed position area, or are handled by the same agent account, but if the deposit transactions recently handled by the individual account and the position information of the individual account are far deviated from the historical position area, it can be shown that the deposit of the individual account has certain doubtful property, and under the condition, the agent account can be temporarily prohibited from handling the deposit service for the individual account.
303: and when the MM management server determines that the agent account does not belong to the blacklist, performing service processing based on the request message.
For example, when the MM management server determines that the agent account does not belong to the blacklist and the request message is used to request a deposit transaction, the MM management server transacts the deposit transaction based on the agent account and the individual account, and a specific implementation process thereof may be referred to in the related art and will not be described in detail herein.
Further, after the deposit transaction is successfully transacted, the MM management server may transmit a response message to the first terminal and the second terminal, the response message indicating that the deposit transaction has been successfully implemented. Wherein the second terminal is a terminal used by an individual user requesting to transact the service.
It should be noted that, if the MM management server determines that the agent account belongs to the blacklist, it may temporarily prohibit the transaction of the deposit service for the agent account, and send a failure message to the first terminal and the second terminal, so as to notify the agent user and the individual user who requests to transact the deposit service that the transaction of the deposit service fails.
It should be noted that, here, it is only described as an example that the transaction of depositing money for the agent account may be temporarily prohibited when the MM management server determines that the agent account does not belong to the blacklist, in another embodiment, when the MM management server determines that the agent account does not belong to the blacklist, the agent user may also be punished in other manners, for example, the service transaction qualification of the agent account may also be cancelled in a manner of manual intervention, or certain penalty processing may also be performed on the agent account, and the like, which is not limited in the embodiment of the present invention.
It should be noted that, for each agent account stored in the black list, the operator may perform manual review or recheck on the agent account to further check the agent account, and if the check is passed, the agent account may be deleted from the black list.
To this end, in an actual application scenario, in order to facilitate a subsequent MM management server to continue data statistical analysis, after the MM management server performs service processing based on the request message when determining that the agent account does not belong to the blacklist, a historical transaction data sample may be generated based on the current transaction, which specifically includes the following implementation steps:
304: when the request message carries a first MSISDN and a second MSISDN, the MM management server generates a location query request based on the first MSISDN and the second MSISDN, where the first MSISDN is the MSISDN of the target individual user requesting to handle the service, and the second MSISDN is the MSISDN of the agent user.
It should be noted that, here, the terminals used by the target individual user and the agent user are both mobile phones as an example. That is, after completing the deposit transaction or during the process of implementing the deposit transaction, the MM management server may generate the location query request based on the first MSISDN and the second MSISDN.
305: the MM management server transmits a location query request to the LBS.
306: the LBS queries and returns location information of the target individual user and the agent user based on the first MSISDN and the second MSISDN.
In a specific implementation, the Location information queried by the LBS based on the first MSISDN and the second MSISDN may be a Location Area Cell identity (LAC-CI), and the LAC-CI may be used to identify a sector of a base station, and determine whether the target individual user and the agent user are in the same Location Area according to the LAC-CI.
307: the MM management server receives the location information of the target individual user and the agent user sent by the LBS.
308: the MM management server generates historical transaction data samples based on the location information of the target individual user and the agent user.
That is, the generated historical transaction data sample includes the location information of the target individual user and the location information of the agent user. Further, the historical transaction data sample may also include an individual account number of the target individual user, or the historical transaction data sample may also include a transaction time, or the historical transaction data sample may also include a transaction amount, etc.
After the MM management server generates the historical transaction data sample, the MM management server stores the historical transaction data sample, so that the MM management server can periodically perform data mining and big data analysis based on the historical transaction data sample.
In the embodiment of the invention, when a request message of the agent account is received, whether the agent account belongs to a blacklist or not is inquired, and when the agent account is determined not to belong to the blacklist, service processing is carried out based on the received request message. The agent account number of which the historical transaction does not accord with the preset rule and is stored in the blacklist is determined based on a plurality of historical transaction data samples of each agent account number, each historical transaction data sample comprises position information of both transaction parties, and the position information can be obtained through a positioning technology, so that whether the agent account number accords with the preset rule or not when the agent account number requests for service can be identified without additionally adding hardware equipment, and the cost is reduced.
Referring to fig. 4A, an embodiment of the present invention provides a service processing apparatus, where the apparatus includes:
a first receiving module 410, configured to perform the operations performed by the MM management server in step 301 in the embodiment of fig. 3;
a query module 420 for performing step 302 in the embodiment of fig. 3;
a processing module 430, configured to perform step 303 in the embodiment of fig. 3.
Optionally, referring to fig. 4B, the apparatus further includes:
a first obtaining module 440, configured to perform step 3031 in the embodiment in fig. 3;
a second obtaining module 450, configured to perform step 3032 in the embodiment in fig. 3;
the determining module 460 is configured to execute the step 3033 in the embodiment in fig. 3.
Optionally, referring to fig. 4C, the apparatus further includes:
a first generating module 470, configured to perform step 304 in the embodiment of fig. 3;
a sending module 480, configured to execute step 305 in the foregoing embodiment in fig. 3;
a second receiving module 490, configured to perform step 307 in the embodiment of fig. 3;
a second generating module 412, configured to perform step 308 in the embodiment of fig. 3.
In the embodiment of the invention, when a request message of the agent account is received, whether the agent account belongs to a blacklist or not is inquired, and when the agent account is determined not to belong to the blacklist, service processing is carried out based on the received request message. The agent account number of which the historical transaction does not accord with the preset rule and is stored in the blacklist is determined based on a plurality of historical transaction data samples of each agent account number, each historical transaction data sample comprises position information of both transaction parties, and the position information can be obtained through a positioning technology, so that whether the agent account number accords with the preset rule or not when the agent account number requests for service can be identified without additionally adding hardware equipment, and the cost is reduced.
It should be noted that: in the service processing apparatus provided in the foregoing embodiment, when implementing the service processing method, only the division of each functional module is illustrated, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the service processing apparatus and the service processing method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.
In the above embodiments, the implementation may be wholly or partly realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with embodiments of the invention, to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., Digital Versatile Disk (DVD)), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above-mentioned embodiments are provided not to limit the present application, and any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (5)

1. A service processing method is applied to a mobile payment MM management server, and comprises the following steps:
receiving a request message of an agent account, wherein the request message is used for requesting services without paying a commission charge, and the services requested by the request message are related to the service types of the commission charge-free established by an operator; acquiring a plurality of historical transaction data samples of the agent account in a specified time period, wherein each historical transaction data sample comprises historical position information of the agent user and each individual user when each historical transaction is realized;
obtaining all appointed historical transaction data samples from the plurality of historical transaction data samples, wherein the appointed historical transaction data samples comprise historical position information of the agent user and individual users related to the historical transactions when the historical transactions are realized, and the historical position information does not belong to the same position area; judging whether to store the agent account number into a blacklist or not based on all acquired designated historical transaction data samples;
inquiring whether the agent account belongs to the blacklist or not, wherein the blacklist is used for storing the agent accounts of which historical transactions do not accord with preset rules, each agent account stored by the blacklist is determined based on a plurality of historical transaction data samples of each agent account, each historical transaction data sample comprises historical position information of each agent user and each individual user when each historical transaction is realized, and the preset rules are set by an operator according to operation strategies; when determining that the agent account does not belong to the blacklist, performing service processing based on the request message;
the determining whether to store the agent account number in the blacklist based on all the obtained designated historical transaction data samples includes:
counting the number of all the designated historical transaction data samples; if the number of all the designated historical transaction data samples is greater than or equal to a first preset threshold value, storing the agent account number into the blacklist;
and/or acquiring the number of the stored specified historical transaction data samples of each agent account, and if the number of the specified historical transaction data samples of the agent account in the acquired number is the largest, storing the agent account into the blacklist;
and/or when each designated historical transaction data sample further comprises an individual account number, counting the number of the designated historical transaction data samples corresponding to each individual account number in all the designated historical transaction data samples to obtain the number of a plurality of individual account number samples, and if the number of the individual account number samples which is greater than or equal to a second preset threshold exists in the number of the plurality of individual account number samples, storing the agent account number into the blacklist;
and/or when each appointed historical transaction data sample also comprises a transaction amount, counting the number of the appointed historical transaction data samples of which the transaction amounts are larger than a preset amount and which are included in all the appointed historical transaction data samples, and if the number of the appointed historical transaction data samples of which the transaction amounts are larger than the preset amount and which are included in the appointed historical transaction data samples is larger than or equal to a third preset threshold value, storing the agent account number into the blacklist;
and/or when each appointed historical transaction data sample further comprises transaction time, counting the number of appointed historical transaction data samples of which the transaction time is in a preset time range, wherein the number of the appointed historical transaction data samples is included in all the appointed historical transaction data samples, and if the number of the appointed historical transaction data samples of which the transaction time is in the preset time range is greater than or equal to a fourth preset threshold value, storing the agent account number into the blacklist.
2. The method of claim 1, wherein after the service processing based on the request message, further comprising:
when the request message carries a first mobile subscriber international integrated services digital network (MSISDN) number and a second MSISDN, generating a position query request based on the first MSISDN and the second MSISDN, wherein the first MSISDN is the MSISDN of a target individual subscriber requesting service handling, and the second MSISDN is the MSISDN of the agent subscriber;
sending a location query request to a location based server LBS, so that the LBS queries and returns location information of the target individual user and the agent user based on the first MSISDN and the second MSISDN;
receiving the position information of the target individual user and the agent user sent by the LBS;
generating historical transaction data samples based on the location information of the target individual user and the agent user.
3. A traffic processing apparatus, characterized in that the apparatus comprises:
the system comprises a first receiving module, a second receiving module and a third receiving module, wherein the first receiving module is used for receiving a request message of an agent account, the request message is used for requesting a service without paying a commission charge, and the service requested by the request message is related to a service type without the commission charge formulated by an operator;
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a plurality of historical transaction data samples of the agent account in a specified time period, and each historical transaction data sample comprises historical position information of the agent user and each individual user when each historical transaction is realized;
a second obtaining module, configured to obtain all specified historical transaction data samples from the multiple historical transaction data samples, where historical location information of the agent user and historical location information of an individual user involved in the historical transaction do not belong to the same location area when the historical transaction is implemented, where the historical location information is included in the specified historical transaction data samples;
the judging module is used for judging whether the agent account is stored in a blacklist or not based on all the acquired designated historical transaction data samples;
the inquiry module is used for inquiring whether the agent account belongs to the blacklist or not, the blacklist is used for storing the agent accounts of which historical transactions do not accord with preset rules, each agent account stored by the blacklist is determined based on a plurality of historical transaction data samples of each agent account, each historical transaction data sample comprises historical position information of each agent user and each individual user when each historical transaction is realized, and the preset rules are set by an operator according to operation strategies;
the processing module is used for performing service processing based on the request message received by the first receiving module when the inquiry module determines that the agent account does not belong to the blacklist;
the judging module is used for:
counting the number of all the designated historical transaction data samples; if the number of all the designated historical transaction data samples is greater than or equal to a first preset threshold value, storing the agent account number into the blacklist;
and/or acquiring the number of the stored specified historical transaction data samples of each agent account, and if the number of the specified historical transaction data samples of the agent account in the acquired number is the largest, storing the agent account into the blacklist;
and/or when each designated historical transaction data sample further comprises an individual account number, counting the number of the designated historical transaction data samples corresponding to each individual account number in all the designated historical transaction data samples to obtain the number of a plurality of individual account number samples, and if the number of the individual account number samples which is greater than or equal to a second preset threshold exists in the number of the plurality of individual account number samples, storing the agent account number into the blacklist;
and/or when each appointed historical transaction data sample also comprises a transaction amount, counting the number of the appointed historical transaction data samples of which the transaction amounts are larger than a preset amount and which are included in all the appointed historical transaction data samples, and if the number of the appointed historical transaction data samples of which the transaction amounts are larger than the preset amount and which are included in the appointed historical transaction data samples is larger than or equal to a third preset threshold value, storing the agent account number into the blacklist;
and/or when each appointed historical transaction data sample further comprises transaction time, counting the number of appointed historical transaction data samples of which the transaction time is in a preset time range, wherein the number of the appointed historical transaction data samples is included in all the appointed historical transaction data samples, and if the number of the appointed historical transaction data samples of which the transaction time is in the preset time range is greater than or equal to a fourth preset threshold value, storing the agent account number into the blacklist.
4. The apparatus of claim 3, wherein the apparatus further comprises:
a first generating module, configured to generate a location query request based on a first MSISDN and a second MSISDN when the request message carries a first mobile subscriber international integrated services digital network number MSISDN and the second MSISDN, where the first MSISDN is a MSISDN of a target individual subscriber requesting to handle a service, and the second MSISDN is a MSISDN of the agent subscriber;
a sending module, configured to send a location query request to a location based server LBS, so that the LBS queries and returns location information of the target individual user and the agent user based on the first MSISDN and the second MSISDN;
the second receiving module is used for receiving the position information of the target individual user and the agent user sent by the LBS;
a second generation module to generate historical transaction data samples based on the location information of the target individual user and the agent user.
5. A computer-readable storage medium, having a computer program stored thereon, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1-2.
CN201710160542.9A 2017-03-17 2017-03-17 Service processing method and device Active CN108629582B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710160542.9A CN108629582B (en) 2017-03-17 2017-03-17 Service processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710160542.9A CN108629582B (en) 2017-03-17 2017-03-17 Service processing method and device

Publications (2)

Publication Number Publication Date
CN108629582A CN108629582A (en) 2018-10-09
CN108629582B true CN108629582B (en) 2021-04-09

Family

ID=63687821

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710160542.9A Active CN108629582B (en) 2017-03-17 2017-03-17 Service processing method and device

Country Status (1)

Country Link
CN (1) CN108629582B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110264242A (en) * 2019-05-21 2019-09-20 中国平安人寿保险股份有限公司 A kind of business handling qualification verification mechanism, equipment and computer readable storage medium
CN110889689A (en) * 2019-12-16 2020-03-17 中国建设银行股份有限公司 Transaction request processing method and device, electronic equipment and readable storage medium
CN111918225B (en) * 2020-09-15 2022-03-29 北京值得买科技股份有限公司 Method for sending short message based on multiple operators

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729591A (en) * 2008-10-29 2010-06-09 中国移动通信集团公司 User guide device, system and method
CN103035078A (en) * 2012-11-30 2013-04-10 深圳天源迪科信息技术股份有限公司 Payment security monitoring method based on position
CN103679966A (en) * 2013-12-30 2014-03-26 上海富友支付服务有限公司 Financial terminal monitoring system and method based on smart device hybrid positioning technology
CN104572393A (en) * 2013-10-24 2015-04-29 世纪禾光科技发展（北京）有限公司 Buyer and seller login monitoring method and buyer and seller login monitoring system
CN105654303A (en) * 2015-12-31 2016-06-08 拉扎斯网络科技（上海）有限公司 High-risk user recognition method and device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103700192B (en) * 2012-09-27 2016-05-18 中国银联股份有限公司 The telephone-moving monitoring system of Mobile POS Terminal and the telephone-moving method for supervising of Mobile POS Terminal

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729591A (en) * 2008-10-29 2010-06-09 中国移动通信集团公司 User guide device, system and method
CN103035078A (en) * 2012-11-30 2013-04-10 深圳天源迪科信息技术股份有限公司 Payment security monitoring method based on position
CN104572393A (en) * 2013-10-24 2015-04-29 世纪禾光科技发展（北京）有限公司 Buyer and seller login monitoring method and buyer and seller login monitoring system
CN103679966A (en) * 2013-12-30 2014-03-26 上海富友支付服务有限公司 Financial terminal monitoring system and method based on smart device hybrid positioning technology
CN105654303A (en) * 2015-12-31 2016-06-08 拉扎斯网络科技（上海）有限公司 High-risk user recognition method and device

Also Published As

Publication number Publication date
CN108629582A (en) 2018-10-09

Similar Documents

Publication Publication Date Title
AU2010260571B2 (en) Transaction system and method
JP5810217B2 (en) Ad hoc cash payment network
CN109961365B (en) Account receiving record processing method and system based on block chain intelligent contract
CN108629582B (en) Service processing method and device
US10089622B2 (en) Systems and methods for performing funds freeze and/or funds seizure with respect to prepaid payment cards
WO2014140675A1 (en) Method, apparatus, and computer-readable medium for advancing prepaid credit
CN110738502A (en) bill processing method and device and storage medium device
US20060117165A1 (en) Dynamic processing of data processing instructions
CN110297824B (en) Data recording method, device, equipment and storage medium based on resource transfer
US10298777B2 (en) Methods and apparatus to determine a telecommunications account status
CN111507594B (en) Data processing method and device
CN111861745B (en) Service wind control method and device
CN115421933A (en) Intelligent processing method, device and storage medium for Unionpay transaction
US20210042780A1 (en) Substantially real time cash back settlement
KR102107454B1 (en) System for multiplication of financial payment networks, method for financial services using the same and computer program for the same
JP5691427B2 (en) Communication cost settlement system, apparatus, method and program
CN113222735A (en) Method for inquiring transaction associated information and related device
CN115809922A (en) Data processing method, device, equipment and medium
WO2022008967A1 (en) Network usage product provisioning via a mobile wallet platform
CN115578176A (en) Method, device and equipment for creating resource account and storage medium
CN116882955A (en) Method and device for calculating service data
OA19720A (en) Network usage product provisioning via a mobile wallet platform
CN115860673A (en) Asset data processing method and device, electronic equipment and storage medium
CN117764730A (en) Service processing method, device, electronic equipment and computer readable medium
CN114841690A (en) Deduction processing method and device, electronic equipment and computer readable medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right

Effective date of registration: 20200211

Address after: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Applicant after: HUAWEI TECHNOLOGIES Co.,Ltd.

Address before: 210000 HUAWEI Nanjing base, 101 software Avenue, Yuhuatai District, Jiangsu, Nanjing

Applicant before: Huawei Technologies Co.,Ltd.

TA01 Transfer of patent application right
GR01 Patent grant
GR01 Patent grant