CN108446926B - Data processing method and server - Google Patents

Data processing method and server Download PDF

Info

Publication number
CN108446926B
CN108446926B CN201810149386.0A CN201810149386A CN108446926B CN 108446926 B CN108446926 B CN 108446926B CN 201810149386 A CN201810149386 A CN 201810149386A CN 108446926 B CN108446926 B CN 108446926B
Authority
CN
China
Prior art keywords
transaction
position information
identification
payer
payee
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
CN201810149386.0A
Other languages
Chinese (zh)
Other versions
CN108446926A (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.)
Advanced Nova Technology Singapore Holdings Ltd
Original Assignee
Advanced New 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 Advanced New Technologies Co Ltd filed Critical Advanced New Technologies Co Ltd
Priority to CN201810149386.0A priority Critical patent/CN108446926B/en
Priority to CN202210378830.2A priority patent/CN114742556A/en
Publication of CN108446926A publication Critical patent/CN108446926A/en
Application granted granted Critical
Publication of CN108446926B publication Critical patent/CN108446926B/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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3224—Transactions dependent on location of M-devices
    • 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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0213—Consumer transaction fees
    • 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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0222—During e-commerce, i.e. online 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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0239—Online discounts or incentives

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Development Economics (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The embodiment of the specification provides a data processing method and a server. The method comprises the following steps: receiving a payer identification and a payee identification; sending the payee identification to a resource management server; receiving payee position information corresponding to the payee identification fed back by the resource management server; and storing the position information of the payee as the transaction position information corresponding to the identifier of the payer.

Description

Data processing method and server
Technical Field
The embodiment of the specification relates to the technical field of computers, in particular to a data processing method and a server.
Background
With the development of the intelligent client and the popularization of network application, a user can realize various transaction operations through the intelligent client, so that the operations of shopping or consumption and the like of people are more convenient and faster. In the related art, when a payer and a payee need to perform offline transaction payment, the payer may perform on-site interaction with a client of the payee through a payment platform to implement the transaction payment. The payment platform can record transaction information such as payer identification and payee identification related to transaction payment, wherein the payer identification can be used for identifying the payer, and the payee identification can be used for identifying the payee.
In some cases, the paymate needs to count the transaction metrics of the payor in a certain geographic area. For example, to support the development of offline payment services, payment platforms typically launch marketing campaigns. Specifically, for example, when the number of times that the payer completes the transaction payment in a certain geographic area reaches a preset number, the payment platform may present a certain amount of bonus to the payer.
When the payment platform counts the transaction indexes of the payer in a certain geographic area, a plurality of payee identifiers having a transaction payment relation with the payer identifiers are required to be obtained from the recorded historical transaction information; and judging whether the payee identified by the acquired payee identification is located in the geographic area one by one so as to count the transaction indexes of the payer in the geographic area. Typically, the number of payee identifiers having a transaction payment relationship with the payer identifier is very large. The payment platform judges whether the payee identified by the acquired payee identification is located in the geographic area one by one, so that the speed of counting transaction indexes is low. In particular, historical transaction information is typically located within a database. This may lead to a crash of the database if the number of payee identifiers having a transaction payment relationship with the payer identifier is very large.
Disclosure of Invention
The embodiment of the specification aims to provide a data processing method and a server so as to improve the statistical speed of transaction indexes.
To achieve the above object, an embodiment of the present specification provides a data processing method, including: receiving a payer identification and a payee identification; sending the payee identification to a resource management server; receiving payee position information corresponding to the payee identification fed back by the resource management server; and storing the position information of the payee as the transaction position information corresponding to the identifier of the payer.
To achieve the above object, an embodiment of the present specification provides a server, including: a first receiving unit for receiving a payer identification and a payee identification; the sending unit is used for sending the payee identification to the resource management server; the second receiving unit is used for receiving payee position information which is fed back by the resource management server and corresponds to the payee identification; and the storage unit is used for storing the position information of the payee as the transaction position information corresponding to the identifier of the payer.
To achieve the above object, an embodiment of the present specification provides a server, including: the communication assembly is used for establishing communication connection and carrying out data transmission; a processor for receiving a payer identification and a payee identification; sending the payee identification to a resource management server; receiving payee position information corresponding to the payee identification fed back by the resource management server; and storing the position information of the payee as the transaction position information corresponding to the identifier of the payer.
To achieve the above object, an embodiment of the present specification provides a data processing method, including: providing at least one transaction location information; the transaction position information corresponds to a payer identification; receiving the identifier of the appointed payer and the appointed position information; taking the appointed position information as a constraint condition, and counting transaction indexes corresponding to the appointed payer identification based on the provided transaction position information; and feeding back the transaction index.
To achieve the above object, an embodiment of the present specification provides a server, including: a providing unit for providing at least one transaction location information; the transaction position information corresponds to a payer identification; a receiving unit for receiving the designated payer identification and the designated location information; the counting unit is used for counting transaction indexes corresponding to the appointed payer identification based on the provided transaction position information by taking the appointed position information as a constraint condition; and the feedback unit is used for feeding back the transaction index.
To achieve the above object, an embodiment of the present specification provides a server, including: the communication assembly is used for establishing communication connection and carrying out data transmission; the processor is used for providing at least one transaction position information, and the transaction position information corresponds to a payer identification; receiving the identifier of the appointed payer and the appointed position information; taking the appointed position information as a constraint condition, and counting transaction indexes corresponding to the appointed payer identification based on the provided transaction position information; and feeding back the transaction index.
To achieve the above object, an embodiment of the present specification provides a data processing method, including: receiving a virtual object acquisition request; the virtual object acquisition request comprises a payer identification; sending the payer identification and location information to a storage server; receiving a transaction index fed back by a storage server and counted based on the payer identification and the position information; and when the transaction index meets a preset condition, distributing a virtual object to the payer identification.
To achieve the above object, an embodiment of the present specification provides a server, including: a first receiving unit configured to receive a virtual object acquisition request; the virtual object acquisition request comprises a payer identification; a sending unit for sending the payer identification and location information to a storage server; the second receiving unit is used for receiving the transaction index fed back by the storage server and counted on the basis of the payer identification and the position information; and the allocation unit is used for allocating the virtual object to the payer identification when the transaction index meets a preset condition.
To achieve the above object, an embodiment of the present specification provides a server, including: the communication assembly is used for establishing communication connection and carrying out data transmission; a processor for receiving a virtual object acquisition request; the virtual object acquisition request comprises a payer identification; sending the payer identification and location information to a storage server; receiving a transaction index fed back by a storage server and counted based on the payer identification and the position information; and when the transaction index meets a preset condition, distributing a virtual object to the payer identification.
As can be seen from the technical solutions provided in the embodiments of the present specification, the storage server may receive the payer identifier and the payee identifier; the payee identification may be sent to a resource management server; receiving payee position information corresponding to the payee identification fed back by the resource management server; the payee location information may be stored as transaction location information corresponding to the payer identification. In this way, the storage server can directly provide the transaction position information corresponding to the payer identification, thereby facilitating the rapid statistics of transaction indexes of the payer based on the geographic area.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.
FIG. 1 is a diagram illustrating a data processing method according to an embodiment of the present disclosure;
FIG. 2 is a flow chart of a data processing method according to an embodiment of the present disclosure;
FIG. 3 is a flow chart of a data processing method according to an embodiment of the present disclosure;
FIG. 4 is a flow chart of a data processing method according to an embodiment of the present disclosure;
FIG. 5 is a functional block diagram of a server according to an embodiment of the present disclosure;
FIG. 6 is a functional block diagram of a server according to an embodiment of the present disclosure;
FIG. 7 is a functional block diagram of a server according to an embodiment of the present disclosure;
fig. 8 is a functional block diagram of a server according to an embodiment of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.
Please refer to fig. 1. The embodiment of the specification provides a data processing system.
In this embodiment, the data processing system may include a resource management server. The resource management server may be one server or a plurality of servers, and may also be a server cluster including a plurality of servers.
In this embodiment, the asset management server may provide at least one payee location information. The payee location information may correspond to a payee identification. The payee identification may be used to identify the payee, for example, may be the name, account, or number of the payee, and the like. The payee may be a merchant who provides offline business services to consumers in a mall, hotel, restaurant, etc. The payee location information may be used to indicate a geographic area for offline business services provided by the payee. The payee position information indicates the size of the geographical area, which can be flexibly set according to business needs, for example, the payee position information can be a street, a business district, a city, a country, or a region formed by a plurality of countries, etc.
The receiving position information may include any one of a geographical area identifier, a latitude and longitude, a geographical position code, and an Internet Protocol Address (IP). The geographic area identifier may be used to identify a geographic area, and may be, for example, a country name, a country number, a region name, a region number, or the like. The geographical area represented by the longitude and latitude may be a geographical area in which a geographical position corresponding to the longitude and latitude is located. For example, the latitude and longitude (116.389550, 39.928167) may correspond to a geographic location in Beijing, China. The geographic region represented by the latitude and longitude (116.389550, 39.928167) may then be Beijing, China. The geographical position code can be a character string generated by calculating the longitude and latitude according to a preset algorithm. The preset algorithm may be, for example, a tail-removing algorithm, a GeoHash algorithm, or the like. For example, the longitude and latitude (116.389550, 39.928167) may be calculated according to the GeoHash algorithm to generate a geographical position code wx4 g. The geographical area represented by the geographical position code may be a geographical area in which the geographical position corresponding to the geographical position code is located. The geographic area represented by the network address may be the geographic area to which the network address is mapped. For example, the geographic region to which the network address (222.92.255.XXX) is mapped may be suzhou, china.
For example, the resource management server provides the payee location information as shown in table 1 below.
TABLE 1
Payee location information Payee identification
Hong Kong, China MA
Europe MB
North America MC
In this embodiment, the developer may input payee identification and payee location information at the asset management server. The resource management server can receive payee identification and payee position information input by a developer; the received payee location information may be used as payee location information corresponding to the payee identification. Of course, the resource management server may also provide the location information of the at least one payee in other manners, which is not limited in this embodiment.
In this embodiment, the data processing system may further include a payer client. The payer may be a consumer. The payer client may be a smart phone, a tablet electronic device, a portable computer, a Personal Digital Assistant (PDA), or a smart wearable device, etc.
In this embodiment, the data processing system may further include a payee client. The payee client may be a mobile device, such as a smart phone, a tablet electronic device, a portable computer, a Personal Digital Assistant (PDA), a POS (e.g., a merchant POS, a public transit POS, etc.), or a smart wearable device, etc. The payee client may also be a desktop device, such as a server, an industrial personal computer (industrial control computer), a Personal Computer (PC), a kiosk, or a smart self-service terminal (kiosk) (e.g., subway self-service ticket machine, train ticket self-service ticket machine), etc. The payee client may be one client or a system including a plurality of clients.
In this embodiment, the data processing system may further include a payment server. The payment server may be one server or a plurality of servers, and may also be a server cluster including a plurality of servers. The payment server may be a separate server or may be integrated with the resource management server.
In this embodiment, the payment server may receive a payment request, where the payment request may carry a payer identifier, a payee identifier, and a payment amount; the payment operation may be based on the payer identification, payee identification, and payment amount. The payer identification may be used to identify the payer, which may be, for example, the name, account, or number of the payer, and so on.
The payment request may come from a payer client. For example, the payee may have a payment code. The payment code can be a graphical code or a sound wave code, and the graphical code can comprise a bar code, a two-dimensional code and the like. The payment code may include a payee identifier and a payment page identifier. The payment page identifier may be used to identify a payment page, and may be, for example, a link address of the payment page, or a code of the link address, etc. The payer client may scan the payee's payment code; the scanned payment code can be analyzed to obtain a payee identifier and a payment page identifier; the payment page may be presented based on the payment page identification; the payment amount input by the user on the payment page can be acquired; the identifier of the payer who logs in currently can be obtained; a payment request may be sent to the payment server, where the payment request may carry a payer identifier, a payee identifier, and a payment amount. As another example, the payer client may provide a payment page; the payment amount and the payee identification input by the user on the payment page can be obtained; the identifier of the payer who logs in currently can be obtained; a payment request may be sent to the payment server, where the payment request may carry a payer identifier, a payee identifier, and a payment amount. Of course, those skilled in the art should understand that the payer client may also send the payment request to the payment server in other manners, which is not limited in this embodiment.
Alternatively, the payment request may also come from the payee client. For example, the payer client may provide a payment code, which may include the payer identification. The payee client may scan the payment code provided by the payer client; the scanned payment code can be analyzed to obtain the identifier of the payer; a payment amount and a payee identification may be obtained; a payment request may be sent to the payment server, where the payment request may carry a payer identifier, a payee identifier, and a payment amount. Specifically, the payee client may obtain a preset default amount as the payment amount, or may also obtain an amount input by the user as the payment amount. The payee client may obtain a preset payee identifier or may obtain a payee identifier input by the user. Of course, those skilled in the art should understand that the payee client may also send the payment request to the payment server in other manners, which is not limited in this embodiment.
In this embodiment, the data processing system may further include a storage server. The storage server may be one server or a plurality of servers, and may also be a server cluster including a plurality of servers. The storage server may be a separate server, or may be integrated with the resource management server or the payment server.
In this embodiment, the storage server may provide at least one transaction location information. The transaction location information may correspond to a payer identification. The transaction location information may be used to indicate a geographic area in which the payer is conducting the transaction. The size of the geographic area represented by the transaction location information can be flexibly set according to business needs, and can be, for example, a street, a business district, a city, a country, or a region formed by a plurality of countries.
For example, the transaction location information provided by the storage server may be as shown in table 2 below.
TABLE 2
Transaction location information Payer identification Number of transactions
Hong Kong, China CA 6
Europe CA 3
North America CA 3
Hong Kong, China CB 2
Antarctic pole CB 6
Europe CC 1
North America CC 1
In an implementation manner of this embodiment, the transaction location information provided by the storage server may correspond to a transaction time. The transaction time may be the time when the payer conducts the transaction in the geographical area indicated by the transaction location information.
For example, the transaction location information provided by the storage server may be as shown in table 3 below.
TABLE 3
Transaction location information Payer identification Time of transaction
Hong Kong, China CA 2017-11-01,00:01:00
Hong Kong, China CA 2017-11-01,01:01:03
Hong Kong, China CB 2017-11-01,02:11:23
Europe CA 2017-11-01,11:01:00
Europe CB 2017-11-01,15:01:00
North America CC 2017-11-02,00:01:00
Antarctic pole CB 2017-11-03,10:01:00
In another implementation of this embodiment, the transaction location information provided by the storage server may correspond to a transaction amount. The transaction amount may be an amount of a transaction performed by a payer in a geographic area indicated by the transaction location information.
For example, the transaction location information provided by the storage server may be as shown in table 4 below.
TABLE 4
Transaction location information Payer identification Time of transaction Amount of transaction
Hong Kong, China CA 2017-11-01,00:01:00 10
Hong Kong, China CA 2017-11-01,01:01:03 100
Hong Kong, China CB 2017-11-01,02:11:23 20
Europe CA 2017-11-01,11:01:00 45
Europe CB 2017-11-01,15:01:00 32
North America CC 2017-11-02,00:01:00 28
Antarctic pole CB 2017-11-03,10:01:00 75
In this embodiment, after receiving the payment request, the payment server may further send a payer identifier and a payee identifier to the storage server. The storage server may receive a payer identification and a payee identification; the payee identification may be sent to the resource management server. The resource management server may receive the payee identification; payee location information corresponding to the payee identification may be obtained; the payee location information may be sent to the storage server. The storage server may receive the payee location information; the payee location information may be stored as transaction location information corresponding to the payer identification.
In an implementation manner of this embodiment, after receiving the payment request, the payment server may further send a payment amount to the storage server. The storage server may receive the payment amount; the payment amount may be stored as a transaction amount corresponding to the transaction location information.
In another implementation manner of this embodiment, the storage server may further store the current time as a transaction time corresponding to the transaction location information.
In this embodiment, the payer client may send a virtual object obtaining request to the resource management server, where the virtual object obtaining request may carry a payer identifier. The resource management server may receive the virtual object acquisition request; the payer identification and location information may be sent to the storage server. The storage server may receive the payer identification and the location information; the received payer identification and the position information can be respectively used as the appointed payer identification and the appointed position information; the appointed position information can be used as a constraint condition, and transaction indexes corresponding to the appointed payer identification are counted based on the provided transaction position information; the transaction metrics may be sent to the resource management server. The resource management server may receive the transaction metrics; when the transaction index meets a preset condition, a virtual object can be allocated to the payer identification.
Please refer to fig. 1 and fig. 2. The embodiment of the specification provides a data processing method. The data processing method takes the storage server as an execution subject and can comprise the following steps.
Step S10: a payer identification and a payee identification are received.
In this embodiment, the payment server may send the payer identification and the payee identification to the storage server. The storage server may receive the payer identification and the payee identification. Specifically, the payment server may directly send the payer identifier and the payee identifier to the storage server after receiving the payment request carrying the payer identifier, the payee identifier, and the payment amount. Or, the payment server may perform a payment operation after receiving a payment request carrying a payer identifier, a payee identifier, and a payment amount; the payer identification and payee identification may be sent to the storage server after the payment operation is completed.
Step S12: and sending the payee identification to a resource management server.
Step S14: and receiving payee position information corresponding to the payee identification fed back by the resource management server.
In this embodiment, the storage server may send the payee identifier to the resource management server. The resource management server may receive the payee identification; payee location information corresponding to the payee identification may be obtained; the payee location information may be sent to the storage server. The storage server may receive the payee location information.
Step S16: and storing the position information of the payee as the transaction position information corresponding to the identifier of the payer.
In this embodiment, after receiving the payee location information, the storage server may store the payee location information as the transaction location information corresponding to the payer identifier, so as to provide the transaction location information corresponding to the payer identifier in a subsequent process.
In this embodiment, the storage server may store the transaction location information in any manner, which is not limited in this embodiment. For example, the storage server may be provided with a first set of transaction location information. The first set of transaction location information may include at least one transaction location information, each of which may correspond to a payer identification. A payer identification may correspond to one or more of the same transaction location information in the first set of transaction location information. Specifically, for example, the first transaction location information set may be as shown in table 3 above. Then, the storage server may use the payee location information as the transaction location information corresponding to the payer identification; the transaction location information may be added directly to the first set of transaction location information. As another example, the storage server may be provided with a second set of transaction location information. The second set of transaction location information may include at least one transaction location information, each of which may correspond to a payer identification and a number of transactions. Specifically, for example, the second transaction location information set may be as shown in table 2 described above. Then, the storage server may use the payee location information as the transaction location information corresponding to the payer identification; when the second transaction location information set includes the transaction location information, the number of transactions corresponding to the transaction location information may be increased by 1; when the transaction position information is not included in the second transaction position information set, the transaction position information may be added to the second transaction position information set, and the number of transactions corresponding to the transaction position information is set to 1.
In an implementation manner of this embodiment, after receiving the payment request, the payment server may further send a payment amount to the storage server. The storage server may receive the payment amount; the payment amount may be stored as a transaction amount corresponding to the transaction location information.
In another implementation manner of this embodiment, the storage server may further store the current time as a transaction time corresponding to the transaction location information.
In this embodiment, the storage server may receive a payer identification and a payee identification; the payee identification may be sent to a resource management server; receiving payee position information corresponding to the payee identification fed back by the resource management server; the payee location information may be stored as transaction location information corresponding to the payer identification. In this way, the storage server can directly provide the transaction position information corresponding to the payer identification, thereby facilitating the rapid statistics of transaction indexes of the payer based on the geographic area.
Please refer to fig. 1 and fig. 3. The embodiment of the present specification further provides another data processing method, where the data processing method takes a storage server as an execution subject, and may include the following steps.
Step S20: at least one transaction location information is provided.
In this embodiment, the transaction location information may correspond to a payer identifier. For a detailed description of the transaction location information, reference may be made to the foregoing embodiments, which are not described herein again.
In this embodiment, the storage server may provide the at least one transaction location information in any manner, which is not limited in this embodiment. For example, the storage server may provide a first transaction location information set or a second transaction location information set, and for detailed descriptions of the first transaction location information set and the second transaction location information set, reference may be made to the foregoing examples, which are not described herein again.
Step S22: an identification of a designated payer and designated location information are received.
In this embodiment, the specified payer identification may be used to identify the payer. The specified location information may include any one of a geographical area identification, a longitude and latitude, a geographical location code, and a network address. The specified location information may be used to represent a geographic area. The size of the geographic area represented by the designated location information can be flexibly set according to business needs, and can be, for example, a street, a business district, a city, a country, or a region composed of a plurality of countries, and the like.
In this embodiment, the resource management server may send payer identification and location information to the storage server. The storage server may receive the payer identification and the location information; the received payer identification and location information may be referred to as a designated payer identification and designated location information, respectively. The process of the resource management server sending payer identification and location information to the storage server will be described in detail in the following embodiments.
Step S24: and counting transaction indexes corresponding to the appointed payer identification based on the provided transaction position information by taking the appointed position information as a constraint condition.
In this embodiment, the transaction index may include at least one of a transaction amount and a transaction number. The transaction index may identify a corresponding transaction index for the designated payer within the geographic area represented by the designated location information. For example, the geographic region represented by the specified location information may be europe, and then the transaction indicator may identify a corresponding transaction indicator within europe for the specified payer.
In this embodiment, the storage server may obtain, from the provided transaction location information, transaction location information that corresponds to the specified payer identification and that matches the geographic area represented by the specified location information; and counting transaction indexes corresponding to the specified payer identification based on the acquired transaction position information. Here, the geographic area represented by the transaction location information matches the geographic area represented by the designated location information, and may be understood as: the geographical area represented by the transaction position information is the same as the geographical area represented by the designated position information; alternatively, the geographical area represented by the transaction location information is within the geographical area represented by the designated location information.
In an implementation manner of this embodiment, the storage server may count transaction times based on the acquired transaction location information, as a transaction index corresponding to the specified payer identifier.
In view of the different ways in which the storage server provides the transaction location information, the ways in which the transaction times are counted may also be different. For example, the storage server may be provided with a first transaction location information set, and details regarding the first transaction location information set may be referred to in the foregoing examples, which are not described herein again. Then, the storage server may count the number of acquired transaction location information as the number of transactions. For another example, the storage server may be provided with a second transaction location information set, and details regarding the second transaction location information set may refer to the foregoing examples, which are not described herein again. Then, the storage server may calculate a sum of transaction times corresponding to the acquired transaction location information as a counted transaction time.
To facilitate understanding of the technical solutions of the present embodiment by those skilled in the art, a detailed scenario example is introduced below. In this scenario example, the transaction location information provided by the storage server may be as shown in table 3. The designated payer identification may be a CA, and the geographic region represented by the designated location information may be hong kong, china. Then, the storage server may acquire transaction location information corresponding to the designated payer identification CA and indicating that the geographic area matches hong kong, china; the number of the acquired transaction position information can be counted to be 2; the number 2 may be taken as the number of transactions.
In another implementation of this embodiment, the transaction location information provided by the storage server may correspond to a transaction amount. The storage server can count the transaction amount based on the acquired transaction position information, and the transaction amount is used as a transaction index corresponding to the appointed payer identification. Specifically, for example, the storage server may calculate a sum of transaction amounts corresponding to the acquired transaction location information as a statistical transaction amount.
Step S26: and feeding back the transaction index.
In this embodiment, the storage server may send the transaction index to the resource management server. The resource management server may receive the transaction metrics.
In an implementation manner of this embodiment, the transaction location information provided by the storage server may correspond to a transaction time. The resource management server may send a time interval to the storage server. The time interval may be, for example, 2017-11-01,00:00:00 to 2017-11-01,23:59: 59. The storage server may receive the time interval; the received time interval may be taken as a specified time interval; and counting transaction indexes corresponding to the specified payer identification based on the provided transaction position information by taking the specified time interval and the specified position information as constraint conditions.
In this embodiment, the storage server may obtain, from the provided transaction location information, transaction location information that corresponds to the specified payer identifier, that matches the geographic area represented by the specified location information, and that has a corresponding transaction time within the specified time interval; and counting transaction indexes corresponding to the specified payer identification based on the acquired transaction position information.
In this embodiment, the storage server may provide at least one transaction location information; can receive the identifier of the designated payer and the information of the designated position; the appointed position information can be used as a constraint condition, and transaction indexes corresponding to the appointed payer identification are counted based on the provided transaction position information; the transaction index may be fed back. In this way, the storage server may feed back the transaction index to the resource management server, which facilitates the resource management server to allocate the virtual object according to the transaction index.
Please refer to fig. 1 and 4. The embodiment of the present specification further provides another data processing method, where the data processing method takes a resource management server as an execution subject, and may include the following steps.
Step S30: a virtual object acquisition request is received.
In this embodiment, the virtual object acquisition request may include a payer identifier. The virtual object acquisition request may be for requesting acquisition of a virtual object including, but not limited to, electronic money, coupons, red packs, and the like.
In this embodiment, the payer client may send a virtual object acquisition request to the resource management server. The resource management server may receive the virtual object acquisition request. The payer client may send a virtual object acquisition request to the resource management server in any manner, which is not specifically limited in this embodiment. For example, the payer client may send a virtual object acquisition request to the resource management server upon detecting a virtual object acquisition instruction. The virtual object acquisition instruction may be generated by the payer client when detecting that a designated key is triggered. The designated key can be a physical key or a virtual key, etc. Here, the specific key is triggered, which includes but is not limited to the specific key being pressed, clicked, double-clicked, stroked, pressed for more than a predetermined time, and the like. Alternatively, the virtual object obtaining instruction may be generated by the payer client when a preset gesture is recognized. The preset gesture may be a touch trajectory on the touch-sensitive display. Alternatively, the virtual object acquisition instruction may be generated when the payer client senses a preset motion state through a gyroscope and/or an acceleration sensor.
Step S32: the payer identification and location information is sent to a storage server.
Step S34: and receiving a transaction index fed back by the storage server and based on the payer identification and the position information statistics.
Step S36: and when the transaction index meets a preset condition, distributing a virtual object to the payer identification.
In this embodiment, according to the requirement of the actual service, a developer may configure the location information in advance in the resource management server. The resource management server can acquire the pre-configured position information after receiving the virtual object acquisition request carrying the payer identification; the payer identification and the location information may be sent to a storage server. The storage server may receive payer identification and location information; the received payer identification and the position information can be respectively used as the appointed payer identification and the appointed position information; the appointed position information can be used as a constraint condition, and transaction indexes corresponding to the appointed payer identification are counted based on the provided transaction position information; the transaction metrics may be sent to the resource management server. The resource management server may receive the transaction metrics; a virtual object may be assigned to the payer identification when the transaction index satisfies a preset condition. The preset condition may include at least one of: the transaction amount is larger than or equal to a first preset threshold value, and the transaction times are larger than or equal to a second preset threshold value. The first preset threshold and the second preset threshold can be flexibly set according to actual needs. It should be noted that, after receiving the virtual object acquisition request carrying the payer identifier, the resource management server may also acquire the location information in other manners. For example, the resource management server may obtain the location information input by the developer on a certain interface.
In an implementation manner of this embodiment, the resource management server may obtain a time interval after receiving a virtual object obtaining request carrying a payer identifier; the time interval may be sent to a storage server to facilitate the storage server in counting transaction metrics based on the time interval. The resource management server may acquire the time interval in any manner, which is not specifically limited in this embodiment. For example, according to the actual business requirement, a developer may pre-configure the time interval acquisition rule in the resource management server. The resource management server may obtain the time interval based on a pre-configured time interval obtaining rule. The time interval obtaining rule may be, for example: a time interval of a specified size bounded by the current time is obtained. The specified size may be, for example, 30 days, 35 days, or 60 days, etc.
In an implementation manner of this embodiment, when the transaction index does not satisfy the preset condition, the resource management server may further feed back a prompt message to the payer client to prompt the payer to be unable to obtain the virtual object. The prompt message can be a text message, an image message, a sound message, a video message, any combination thereof, and the like.
In this embodiment, the resource management server may receive a virtual object acquisition request; payer identification and location information may be sent to a storage server; transaction metrics based on the payer identification and the location information statistics, which are fed back by the storage server, can be received; a virtual object may be assigned to the payer identification when the transaction index satisfies a preset condition. Therefore, the resource management server can allocate the virtual object to the payer identification according to the transaction index of the payer identification, so that marketing activities can be developed.
Please refer to fig. 5. The embodiment of the specification also provides a server. The server includes the following elements.
A first receiving unit 40 for receiving a payer identification and a payee identification;
a sending unit 42, configured to send the payee identifier to the resource management server;
a second receiving unit 44, configured to receive payee location information corresponding to the payee identifier, which is fed back by the resource management server;
and a storage unit 46, configured to store the payee location information as transaction location information corresponding to the payer identifier.
Please refer to fig. 6. The embodiment of the specification also provides another server. The server includes a communication component and a processor.
The communication component includes but is not limited to a wired network card, a wireless network card, a bluetooth module, an infrared transceiver module, an ultra-wideband communication module, a zigbee protocol communication module, and the like. The communication component may be used to establish a communication connection and perform data transmission.
In this embodiment, the processor may be implemented in any suitable manner. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth.
In this embodiment, the processor may be configured to receive a payer identification and a payee identification; sending the payee identification to a resource management server; receiving payee position information corresponding to the payee identification fed back by the resource management server; storing the payee location information as transaction location information corresponding to the payer identification
Please refer to fig. 7. The embodiment of the specification also provides another server. The server includes the following elements.
A providing unit 50 for providing at least one transaction location information; the transaction position information corresponds to a payer identification;
a receiving unit 52 for receiving the specified payer identification and the specified location information;
a counting unit 54, configured to count a transaction index corresponding to the specified payer identifier based on the provided transaction location information with the specified location information as a constraint condition;
and the feedback unit 56 is used for feeding back the transaction index.
Please refer to fig. 6. The embodiment of the specification also provides another server. The server includes a communication component and a processor.
The communication component includes but is not limited to a wired network card, a wireless network card, a bluetooth module, an infrared transceiver module, an ultra-wideband communication module, a zigbee protocol communication module, and the like. The communication component may be used to establish a communication connection and perform data transmission.
In this embodiment, the processor may be implemented in any suitable manner. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth.
In this embodiment, the processor may be configured to provide at least one transaction location information, where the transaction location information corresponds to a payer identifier; receiving the identifier of the appointed payer and the appointed position information; taking the appointed position information as a constraint condition, and counting transaction indexes corresponding to the appointed payer identification based on the provided transaction position information; and feeding back the transaction index.
Please refer to fig. 8. The embodiment of the specification also provides another server. The server includes the following elements.
A first receiving unit 60 configured to receive a virtual object acquisition request; the virtual object acquisition request comprises a payer identification;
a sending unit 62, configured to send the payer identification and location information to a storage server;
a second receiving unit 64, configured to receive a transaction index fed back by the storage server and counted based on the payer identification and the location information;
an allocating unit 66, configured to allocate a virtual object to the payer identifier when the transaction index satisfies a preset condition.
Please refer to fig. 6. The embodiment of the specification also provides another server. The server includes a communication component and a processor.
The communication component includes but is not limited to a wired network card, a wireless network card, a bluetooth module, an infrared transceiver module, an ultra-wideband communication module, a zigbee protocol communication module, and the like. The communication component may be used to establish a communication connection and perform data transmission.
In this embodiment, the processor may be implemented in any suitable manner. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth.
In this embodiment, the processor may be configured to receive a virtual object acquisition request; the virtual object acquisition request comprises a payer identification; sending the payer identification and location information to a storage server; receiving a transaction index fed back by a storage server and counted based on the payer identification and the position information; and when the transaction index meets a preset condition, distributing a virtual object to the payer identification.
It should be noted that, in the present specification, each embodiment is described in a progressive manner, and the same or similar parts in each embodiment may be referred to each other, and each embodiment focuses on differences from other embodiments. In particular, for the server embodiment, since it is basically similar to the transaction processing method embodiment, the description is relatively simple, and for relevant points, reference may be made to part of the description of the transaction processing method embodiment.
In addition, it is understood that one skilled in the art, after reading this specification document, may conceive of any combination of some or all of the embodiments listed in this specification without the need for inventive faculty, which combinations are also within the scope of the disclosure and protection of this specification.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate a dedicated integrated circuit chip 2. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardbyscript Description Language (vhr Description Language), and the like, which are currently used by Hardware compiler-software (Hardware Description Language-software). It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
From the above description of the embodiments, it is clear to those skilled in the art that the present specification can be implemented by software plus a necessary general hardware platform. Based on such understanding, the technical solutions of the present specification may be essentially or partially implemented in the form of software products, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and include instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.
The description is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
While the specification has been described with examples, those skilled in the art will appreciate that there are numerous variations and permutations of the specification that do not depart from the spirit of the specification, and it is intended that the appended claims include such variations and modifications that do not depart from the spirit of the specification.

Claims (16)

1. A data processing method is applied to a storage server and comprises the following steps:
receiving a payer identification and a payee identification, wherein the payer identification and the payee identification are sent to the storage server by the payment server after receiving the payment request;
sending the payee identification to a resource management server;
receiving payee position information corresponding to the payee identification fed back by the resource management server;
and storing the position information of the payee as the transaction position information corresponding to the identifier of the payer.
2. The method of claim 1, further comprising:
and storing the current time as the transaction time corresponding to the transaction position information.
3. The method of claim 1, further comprising:
receiving a payment amount;
and storing the payment amount as the transaction amount corresponding to the transaction position information.
4. A storage server, comprising:
a first receiving unit for receiving a payer identification and a payee identification, which are transmitted to the storage server by the payment server after receiving the payment request;
the sending unit is used for sending the payee identification to the resource management server;
the second receiving unit is used for receiving payee position information which is fed back by the resource management server and corresponds to the payee identification;
and the storage unit is used for storing the position information of the payee as the transaction position information corresponding to the identifier of the payer.
5. A storage server, comprising:
the communication assembly is used for establishing communication connection and carrying out data transmission;
a processor for receiving a payer identification and a payee identification, the payer identification and the payee identification being sent by a payment server to the storage server after receiving a payment request; sending the payee identification to a resource management server; receiving payee position information corresponding to the payee identification fed back by the resource management server; and storing the position information of the payee as the transaction position information corresponding to the identifier of the payer.
6. A data processing method is applied to a storage server and comprises the following steps:
providing at least one transaction location information; the transaction position information corresponds to a payer identification;
receiving an appointed payer identification and appointed position information, wherein the appointed payer identification and the appointed position information are sent to the storage server by the resource management server after receiving the virtual object acquisition request;
taking the appointed position information as a constraint condition, and counting transaction indexes corresponding to the appointed payer identification based on the provided transaction position information, wherein the transaction indexes are the transaction indexes corresponding to the appointed payer identification and within the geographic area represented by the appointed position information;
and feeding back the transaction index to a resource management server.
7. The method as recited in claim 6, wherein said accounting for the transaction metrics corresponding to the designated payer identification comprises:
acquiring transaction position information which corresponds to the specified payer identification and is matched with the geographic area represented by the specified position information from the provided transaction position information;
and counting transaction indexes corresponding to the appointed payer identification based on the acquired transaction position information.
8. The method of claim 6, wherein the provided transaction location information corresponds to a transaction time; the method further comprises the following steps:
receiving a specified time interval;
correspondingly, the counting of the transaction indexes corresponding to the specified payer identification comprises the following steps:
and counting transaction indexes corresponding to the specified payer identification based on the provided transaction position information by taking the specified time interval and the specified position information as constraint conditions.
9. The method as recited in claim 8, wherein said accounting for the transaction metrics corresponding to the designated payer identification comprises:
acquiring transaction position information which corresponds to the specified payer identification, is matched with the geographic area represented by the specified position information, and is within the specified time interval at the corresponding transaction time from the provided transaction position information;
and counting transaction indexes corresponding to the appointed payer identification based on the acquired transaction position information.
10. The method of claim 6, 7, 8 or 9, the transaction metrics comprising at least one of a number of transactions and an amount of transactions.
11. A storage server, comprising:
a providing unit for providing at least one transaction location information; the transaction position information corresponds to a payer identification;
a receiving unit, configured to receive an identifier of a designated payer and designated location information, where the identifier of the designated payer and the designated location information are sent to the storage server by the resource management server after receiving the virtual object acquisition request;
the counting unit is used for counting transaction indexes corresponding to the appointed payer identification based on the provided transaction position information by taking the appointed position information as a constraint condition, wherein the transaction indexes are the transaction indexes which correspond to the appointed payer identification and are in the geographic area represented by the appointed position information;
and the feedback unit is used for feeding back the transaction index to the resource management server.
12. A storage server, comprising:
the communication assembly is used for establishing communication connection and carrying out data transmission;
the processor is used for providing at least one transaction position information, and the transaction position information corresponds to a payer identification; receiving an appointed payer identification and appointed position information, wherein the appointed payer identification and the appointed position information are sent to the storage server by the resource management server after receiving the virtual object acquisition request; taking the appointed position information as a constraint condition, and counting transaction indexes corresponding to the appointed payer identification based on the provided transaction position information, wherein the transaction indexes are the transaction indexes corresponding to the appointed payer identification and within the geographic area represented by the appointed position information; and feeding back the transaction index to a resource management server.
13. A data processing method is applied to a resource management server and comprises the following steps:
receiving a virtual object acquisition request; the virtual object acquisition request comprises a payer identification;
sending the payer identification and location information to a storage server;
receiving a transaction index which is fed back by a storage server and is counted based on the payer identification and the position information, wherein the transaction index is a transaction index which corresponds to the payer identification and is within a geographic area represented by the position information;
and when the transaction index meets a preset condition, distributing a virtual object to the payer identification.
14. The method of claim 13, the virtual object comprising at least one of electronic money and a coupon.
15. A resource management server, comprising:
a first receiving unit configured to receive a virtual object acquisition request; the virtual object acquisition request comprises a payer identification;
a sending unit for sending the payer identification and location information to a storage server;
the second receiving unit is used for receiving a transaction index which is fed back by the storage server and counted on the basis of the payer identification and the position information, wherein the transaction index is a transaction index which corresponds to the payer identification and is within a geographic area represented by the position information;
and the allocation unit is used for allocating the virtual object to the payer identification when the transaction index meets a preset condition.
16. A resource management server, comprising:
the communication assembly is used for establishing communication connection and carrying out data transmission;
a processor for receiving a virtual object acquisition request; the virtual object acquisition request comprises a payer identification; sending the payer identification and location information to a storage server; receiving a transaction index which is fed back by a storage server and is counted based on the payer identification and the position information, wherein the transaction index is a transaction index which corresponds to the payer identification and is within a geographic area represented by the position information; and when the transaction index meets a preset condition, distributing a virtual object to the payer identification.
CN201810149386.0A 2018-02-13 2018-02-13 Data processing method and server Active CN108446926B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201810149386.0A CN108446926B (en) 2018-02-13 2018-02-13 Data processing method and server
CN202210378830.2A CN114742556A (en) 2018-02-13 2018-02-13 Data processing method and device and server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810149386.0A CN108446926B (en) 2018-02-13 2018-02-13 Data processing method and server

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN202210378830.2A Division CN114742556A (en) 2018-02-13 2018-02-13 Data processing method and device and server

Publications (2)

Publication Number Publication Date
CN108446926A CN108446926A (en) 2018-08-24
CN108446926B true CN108446926B (en) 2022-03-04

Family

ID=63192341

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202210378830.2A Pending CN114742556A (en) 2018-02-13 2018-02-13 Data processing method and device and server
CN201810149386.0A Active CN108446926B (en) 2018-02-13 2018-02-13 Data processing method and server

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202210378830.2A Pending CN114742556A (en) 2018-02-13 2018-02-13 Data processing method and device and server

Country Status (1)

Country Link
CN (2) CN114742556A (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102419851A (en) * 2011-11-04 2012-04-18 韩壮 Method and device for collecting consumption data of consumers
CN105376286A (en) * 2014-08-29 2016-03-02 阿里巴巴集团控股有限公司 Method and apparatus for obtaining position information

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140172537A1 (en) * 2012-12-17 2014-06-19 Bank Of America Corporation Transaction cost recovery discount offering

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102419851A (en) * 2011-11-04 2012-04-18 韩壮 Method and device for collecting consumption data of consumers
CN105376286A (en) * 2014-08-29 2016-03-02 阿里巴巴集团控股有限公司 Method and apparatus for obtaining position information

Also Published As

Publication number Publication date
CN114742556A (en) 2022-07-12
CN108446926A (en) 2018-08-24

Similar Documents

Publication Publication Date Title
US10699301B2 (en) Data-processing method and apparatus, and computer storage medium for electronic resource transfer
CN106487872B (en) Method and device for providing discount coupons and method for distributing and receiving virtual resources
US9559992B2 (en) System and method for updating information in an instant messaging application
CN105530175A (en) Message processing method, device and system
WO2020119231A1 (en) Electronic certificate pushing method and apparatus based on position information, and electronic device
CN108388512B (en) Data processing method and server
CN110148014B (en) Information processing method, information processing device, blockchain node equipment and storage medium
CN105654321A (en) Method and device for establishing incidence relation
CN104616142B (en) Data transfer method, server, mobile terminal and system
WO2014176896A1 (en) System and method for updating information in an instant messaging application
JP6138975B2 (en) Coupon issuing device, coupon issuing system, coupon issuing method and program
CN111031140A (en) Resource settlement method and device, electronic equipment and storage medium
CN106817394B (en) Method and server for transmitting product configuration parameters
US20140143107A1 (en) Mobile payment service for helping consumer to choose payment card
CN108280648B (en) Transaction processing method and server
US10360600B1 (en) Big tree method and system for verifying user reviews
US20190370850A1 (en) Reliability metrics for real-time auctions
KR102197650B1 (en) Service providing device for providing target marketing, target marketing system comprising the same, control method thereof and computer readable medium having computer program recorded therefor
CN108446926B (en) Data processing method and server
US11651394B2 (en) Systems and methods for dynamic context-based electronic offer communication
CN109685561B (en) Electronic certificate pushing method and device based on user behavior and electronic equipment
JP5869615B2 (en) Coupon issuing device, coupon issuing system, coupon issuing method and program
US20170278123A1 (en) System for managing membership, method for managing membership using registration of membership by user and apparatus using the same
US11615123B2 (en) Method, system, and apparatus for rapid geographic search in an actor-based geographic search network
US20160148252A1 (en) Systems and methods for attributing purchase events to previous online activity

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
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1259095

Country of ref document: HK

TA01 Transfer of patent application right

Effective date of registration: 20201021

Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands

Applicant after: Innovative advanced technology Co.,Ltd.

Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands

Applicant before: Advanced innovation technology Co.,Ltd.

Effective date of registration: 20201021

Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands

Applicant after: Advanced innovation technology Co.,Ltd.

Address before: Greater Cayman, British Cayman Islands

Applicant before: Alibaba Group Holding Ltd.

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

Effective date of registration: 20240229

Address after: Guohao Times City # 20-01, 128 Meizhi Road, Singapore

Patentee after: Advanced Nova Technology (Singapore) Holdings Ltd.

Country or region after: Singapore

Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands

Patentee before: Innovative advanced technology Co.,Ltd.

Country or region before: Cayman Islands

TR01 Transfer of patent right