WO2017084245A1 - 购买请求处理方法及装置 - Google Patents

购买请求处理方法及装置 Download PDF

Info

Publication number
WO2017084245A1
WO2017084245A1 PCT/CN2016/080370 CN2016080370W WO2017084245A1 WO 2017084245 A1 WO2017084245 A1 WO 2017084245A1 CN 2016080370 W CN2016080370 W CN 2016080370W WO 2017084245 A1 WO2017084245 A1 WO 2017084245A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
user
purchase request
user account
temporary
Prior art date
Application number
PCT/CN2016/080370
Other languages
English (en)
French (fr)
Inventor
唐燚
Original Assignee
南京唐一微数字科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 南京唐一微数字科技有限公司 filed Critical 南京唐一微数字科技有限公司
Priority to US15/522,293 priority Critical patent/US20180308138A1/en
Publication of WO2017084245A1 publication Critical patent/WO2017084245A1/zh

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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0605—Supply or demand aggregation
    • 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/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0607—Regulated
    • 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
    • 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/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0613—Third-party assisted
    • 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/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
    • G06Q30/0635—Processing of requisition or of purchase orders

Definitions

  • the present invention relates to the field of Internet technologies, and in particular, to a purchase request processing method and apparatus.
  • the existing purchase request processing methods and devices are less involved in the scope of the rebate mechanism, and the method involving the rebate mechanism is not systematically and perfect in setting, which is not conducive to the promotion of commodities, and the sales channels of commodities are narrow.
  • the present invention provides a purchase request processing method to improve the existing methods and devices that are not conducive to product promotion and narrow sales channels of goods.
  • the present invention provides the following technical solutions:
  • an embodiment of the present invention provides a method for processing a purchase request, the method comprising: receiving and storing a purchase request sent by a user terminal, where the purchase request includes a user account; determining whether the purchase request is Determining a first order corresponding to the user account; if yes, allocating resources according to the first predetermined rule for the account that matches the user account according to the first predetermined relationship; otherwise, according to the second predetermined rule, following the second reservation with the user account Relationship matching account allocation resources.
  • the embodiment of the present invention further provides a purchase request processing device, which is configured to be operated by the server, and includes: a first receiving module, configured to receive and store a purchase request sent by the user terminal, where the purchase request includes a user account; a first determining module, configured to determine whether the purchase request is a first order corresponding to the user account, and a first resource transfer module, configured to: when the purchase request is a first order corresponding to the user account, The first predetermined rule is that the user account is allocated resources according to the first predetermined relationship; the second resource transfer module is configured to: when the purchase request is not the first order corresponding to the user account, according to the second reservation The rule allocates resources for an account that matches the user account according to the second predetermined relationship.
  • a purchase request processing method and apparatus provided by an embodiment of the present invention allocates resources by using different subscription rules by determining whether the purchase request is a first order corresponding to the user account. Therefore, the resource allocation mechanism of the present invention can be more conducive to the promotion of commodities and broaden the sales channels.
  • FIG. 1 is a schematic diagram of an application environment of a purchase request processing method according to an embodiment of the present invention
  • FIG. 2 is a structural block diagram of a server applicable to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for processing a purchase request according to a first embodiment of the present invention
  • FIG. 4 is a flowchart of a method for processing a purchase request according to a second embodiment of the present invention.
  • FIG. 5 is a flowchart of a method for processing a purchase request according to a third embodiment of the present invention.
  • FIG. 6 is a flowchart of a method for processing a purchase request according to a fourth embodiment of the present invention.
  • FIG. 7 is a flowchart of a method for processing a purchase request according to a fifth embodiment of the present invention.
  • FIG. 8 is a flowchart of a method for processing a purchase request according to a sixth embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a purchase request processing apparatus according to an embodiment of the present invention.
  • FIG. 1 is a diagram showing an application environment of a purchase request processing method according to an embodiment of the present invention.
  • the user terminal 100 and the server 200 are located in a wireless or wired network 300 through which the user terminal 100 and the server 200 communicate with each other.
  • the user terminal 100 may specifically include a smartphone, a tablet, an e-book reader, a laptop portable computer, an in-vehicle terminal, a wearable device, and the like.
  • a client of a browser or various applications can be installed in the user terminal 100.
  • FIG. 2 shows a block diagram of a server.
  • the server 200 includes a memory 201, a processor 202, and a network module 203.
  • the structure shown in FIG. 2 is merely illustrative, and the server 200 may further include more or less components than those shown in FIG. 2, or have a different configuration than that shown in FIG. 2.
  • the components shown in Figure 2 can be implemented in hardware, software, or a combination thereof.
  • the server in the embodiment of the present invention may further include multiple servers with different functions.
  • the memory 201 can be used to store software programs and modules, such as the purchase request processing method and the program instructions/modules corresponding to the device in the embodiment of the present invention.
  • the processor 202 executes various programs by running software programs and modules stored in the memory 201.
  • the function application and data processing that is, the purchase request processing method in the embodiment of the present invention.
  • Memory 201 can include high speed random access memory and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • memory 201 can further include memory remotely located relative to processor 202, which can be connected to server 200 over a network.
  • the above software program and module may further include: a service module 221 and an operating system 222.
  • the operating system 222 may be LINUX, UNIX, WINDOWS, which may include various software components and/or drivers for managing system tasks (eg, memory management, storage device control, power management, etc.), and may be various Hardware or software components communicate with one another to provide an operating environment for other software components.
  • the service module 221 runs on the basis of the operating system 222, and listens for requests from the network through the network service of the operating system 222, completes corresponding data processing according to the request, and returns the processing result to the client. That is to say, the service module 221 is used to provide network services to the client.
  • the network module 203 is configured to receive and transmit network signals.
  • the above network signal may include a wireless signal or a wired signal.
  • the client terminal 100 is installed with a client, and the client may be a browser or a third-party application software, and corresponding to the server (Server), providing local services for the user, such as registering and browsing products. Information, according to the user's operation to select the goods to be purchased, and the like.
  • the user terminal 100 may further include a vendor client, and the offline manufacturer may input product information, such as product description information and product image, through the vendor client. Offline vendors can also enter pre-defined specific rules for purchase request processing through the vendor client.
  • the server in this embodiment may be a single server or a server cluster, and may include multiple servers such as a WEB server, a search server, and a computing server.
  • the server may include multiple databases, such as a member database, a commodity database, and an order database.
  • the member database may store user registration information and the like;
  • the product database may store product information and information of offline manufacturers related to the product;
  • the order database may store order information.
  • the product information in the commodity database can be input by the offline manufacturer through the vendor client and stored in the commodity database by the server.
  • Product information may include product images, product descriptions, and the like.
  • FIG. 1 to FIG. 2 are only examples of an application environment of the embodiment of the present invention, and the specific embodiments of the present invention are not limited thereto.
  • FIG. 3 is a flowchart of a method for processing a purchase request according to an embodiment of the present invention. Referring to FIG. 3, this embodiment describes a process flow of a server, where the method includes:
  • Step S301 receiving and storing a purchase request sent by the user terminal, where the purchase request includes a user account;
  • Step S302 determining whether the purchase request is a first order corresponding to the user account
  • step S303 is performed; otherwise, step S304 is performed.
  • Step S303 allocating resources according to the first predetermined rule for an account that matches the user account according to the first predetermined relationship
  • Step S304 allocating resources according to the second predetermined rule for an account that matches the user account according to the second predetermined relationship.
  • a method and a device for processing a purchase request according to an embodiment of the present invention, by determining whether the purchase request is a first order corresponding to the user account, using different subscription rules to allocate resources, so that the resource allocation of the present invention
  • the mechanism can be more conducive to the promotion of goods and expand sales channels.
  • FIG. 4 shows a purchase request processing method provided by the first embodiment of the present invention.
  • the purchase request processing method may include the following steps S401 to S404.
  • Step S401 receiving and storing a purchase request sent by the user terminal, where the purchase request includes a user account;
  • Step S402 determining, according to the user account, whether the purchase request is a first order corresponding to the user account; if yes, executing step S403; otherwise, performing step S404.
  • the server may look up an order corresponding to the user account in the order database according to a user account included in the purchase request. If there is no order corresponding to the user account in the order database, it may be determined that the order corresponding to the purchase request is the first order corresponding to the user account; if there is already an order corresponding to the user account in the order database Then, it can be determined that the order corresponding to the purchase request is not the first order corresponding to the user account.
  • Step S403 allocating resources according to the first predetermined rule for an account that matches the user account according to the first predetermined relationship
  • the resources here can be monetary amounts or resources such as virtual currency or points.
  • the first predetermined rule and the first predetermined relationship may both be rules or relationships set in advance.
  • the account number matched according to the first predetermined relationship may include: an upper account of the user account included in the purchase request; an upper account of the user account included in the purchase request; and the purchase request includes The upper and upper accounts of the user account.
  • the account number matched according to the first predetermined relationship is not limited to the implementation manner, and may also include an upper-level multi-level account of the user account included in the purchase request, where the number of upper-level multi-levels is Can be set in advance.
  • the allocating the resources to the account that matches the user account according to the first predetermined relationship according to the first predetermined rule may include: transferring the first quantity of resources to the upper account of the account of the user included in the purchase request; Transferring a second quantity of resources to an upper-level account with an account of a user included in the purchase request; The amount of resources is transferred to the upper-level superior account number of the user's account number included in the purchase request.
  • Allocating resources may include: respectively transferring a corresponding quantity of resources to an account of a corresponding number of levels.
  • the account number matched according to the first predetermined relationship includes: the upper level account of the user account included in the purchase request; and the upper two levels of the user account included in the purchase request, The upper three-level account of the user account included in the purchase request; the upper four-level account of the user account included in the purchase request, and the upper five-level account of the user account included in the purchase request, according to the first
  • the scheduling rule is that the resource is allocated to the account that matches the user account according to the first predetermined relationship, and may include: transferring the first quantity of resources to the upper-level account of the account of the user included in the purchase request; Transferring the quantity of resources to the upper two-level account of the account of the user included in the purchase request; transferring the third amount of resources to the upper three-level account of the account of the user included in the purchase request; The quantity of resources is transferred to the upper four level account with the user's account number included in the purchase request; the fifth number of resources are transferred to the user included in the purchase request
  • the number of levels of the upper multi-level can be set in advance and the number of corresponding resources can be set in advance.
  • the allocating resources according to the first predetermined rule that is matched with the user account according to the first predetermined relationship may further include: first removing a certain number of resources according to a preset ratio, and then depositing the remaining resources in the user account. Assignment between accounts that match the first predetermined relationship.
  • Step S404 allocating resources according to the second predetermined rule for an account that matches the user account according to the second predetermined relationship.
  • the second predetermined rule and the second predetermined relationship may also be rules or relationships set in advance.
  • the account number matched according to the second predetermined relationship may include: an account of the user included in the purchase request; an upper account of the account of the user included in the purchase request; and a user included in the purchase request The upper level account of the account.
  • the allocating the resource to the account that matches the user account according to the second predetermined relationship according to the second predetermined rule may include: transferring the third quantity of resources to the account of the user included in the purchase request; Transferring the resource to the upper-level account of the user's account included in the purchase request; transferring the first amount of resources to the upper-level account of the user's account included in the purchase request.
  • the second predetermined rule and the number of levels of the upper multi-level and the corresponding resources included in the second predetermined relationship may also be set in advance, and a certain amount of resources may be removed in advance according to a preset ratio, and then The remaining resources are allocated between the accounts whose user accounts are matched according to the first predetermined relationship, and details are not described herein again.
  • the offline manufacturer can formulate resource allocation rules through the vendor client. Different order types correspond to different resource allocation rules, and the prepared resource allocation rules (including the first predetermined rule and the second predetermined rule described above) are stored in the server. Offline manufacturers can also use the manufacturer's client to determine the amount that should be returned when returning.
  • the purchase request processing method can allocate a resource to a corresponding user account according to different order types, and can provide a larger amount of resources to the upper and upper accounts when the order is first, or It is not the first time to increase the amount of resources for the user corresponding to the purchase request, which is conducive to better promoting the product, and is conducive to a strong expansion of the channel for the sale of goods.
  • FIG. 5 shows a purchase request processing method according to a second embodiment of the present invention.
  • the purchase request processing method may include the following steps S501 to S513.
  • Step S501 Receive registration information sent by the user terminal.
  • Step S502 generating a new user account according to the registration information.
  • the new user account can be stored in the member database of the server.
  • step S503 when the registration information includes the identification information of the other user account, the user account corresponding to the identification information is set as the upper account of the new user account, and the new user account is set to The subordinate account of the user account corresponding to the identifier information.
  • the server can establish a correspondence between the newly registered user account and the user account corresponding to the identification information.
  • the user account that is newly registered may be regarded as not registered by the user account.
  • the newly registered user account is regarded by the server as having no superior account.
  • the identifier information may be a two-dimensional code or a unique string of characters, and the specific expression of the identifier information should not be construed as limiting the present invention.
  • Step S504 receiving and storing a purchase request sent by the user terminal, where the purchase request includes a user account.
  • the server After receiving the purchase request, the server sends the order information to the client of the offline manufacturer according to the purchase request.
  • the offline manufacturer can arrange delivery according to the order information, and deliver the logistics information related to the delivery to the server through the manufacturer client, and the server can store the logistics information into the order database.
  • Step S505 Determine, according to the user account, whether the purchase request is a first order corresponding to the user account. If yes, steps S506 and S508 to S511 are performed, and if no, steps S507, S509 to S511 are performed.
  • Step S506 transferring the first quantity of resources to the upper-level account of the account of the user included in the purchase request, and transferring the second quantity of resources to the upper-level account of the account of the user included in the purchase request; Transferring the third amount of resources to the upper-level upper-level account with the account of the user included in the purchase request.
  • the upper-level account of the account number included in the purchase request may be the upper-level account of the upper-level account of the account included in the purchase request.
  • the upper-level upper-level account of the account number included in the purchase request may be the upper-level account of the upper-level account of the upper-level account of the account included in the purchase request.
  • the ratio of the first quantity, the second quantity, and the third quantity may specifically be 1:2:3.
  • the first quantity of resources is the least, and the third quantity of resources is the most.
  • the third amount of resources can be increased to obtain the income of the account, so that the user account has more enthusiasm for promotion, which is beneficial to the promotion of the product.
  • Step S507 transferring a third quantity of resources to an account of a user included in the purchase request; transferring a second quantity of resources to an upper account of an account of a user included in the purchase request; and the first quantity of resources Transfer to the upper-level account of the user's account number included in the purchase request.
  • the upper-level account of the account number included in the purchase request may be the upper-level account of the upper-level account of the account included in the purchase request.
  • the third quantity of resources is transferred to the account number included in the purchase request, and the account corresponding to the purchase request is obtained the most, which is beneficial to improving the purchasing enthusiasm of the user, and is beneficial for continuing the purchase behavior for a long time. .
  • the third quantity may be greater than the second quantity, and the second quantity may be greater than the first quantity.
  • the ratio of the first quantity, the second quantity, and the third quantity may specifically be 1:2:3.
  • Step S508 generating identification information unique to the user account.
  • the order information is stored in the order database, and after receiving the payment-related information, the server sets the order to the completion status.
  • the purchase request is a first subscription corresponding to the user account
  • the identification information corresponding to the user account is generated.
  • the identification information may specifically be a two-dimensional code.
  • Step S509 Receive and store a return request sent by the user terminal, where the return request includes the user account.
  • Step S510 receiving a confirmation request corresponding to the return request.
  • the server When the server receives the confirmation request corresponding to the return request, the corresponding return information is stored in the order database of the server.
  • Step S511 determining, according to the user account, whether the order corresponding to the return request is the first order corresponding to the user account. If yes, step S512 is performed, otherwise, step S513 is performed.
  • Step S512 sending a cancel command to the user account to cancel the identification information corresponding to the user account, setting a lower account of the user account as a subordinate account of the upper account of the user account, and corresponding to the return request The amount of the order is transferred to the account number.
  • the server sends a cancellation command to the account corresponding to the returning behavior to cancel the identification information corresponding to the user account, and then the superior account of the user account is matched with the subordinate account of the account, and disconnected. The matching relationship between this user account and other user accounts. Then return the amount of the corresponding order to the user account.
  • Step S513 transferring the amount of the order corresponding to the return request to the user account.
  • the above purchase request processing method can be applied to a distribution system.
  • the upper level account may be a superior distribution account
  • the lower level account may be a lower level distribution account.
  • FIG. 6 is a flowchart of a method for processing a purchase request according to a fourth embodiment of the present invention. Referring to FIG. 6, this embodiment describes a process flow of a server, where the method includes:
  • Step S601 receiving and storing a purchase request sent by the user terminal, where the purchase request includes a user account;
  • the user account is a unique authentication number of the system to the user when the server receives the purchase request initiated by the user terminal and is allocated to the user by the server. It can be understood that the user who has the user account is the user who has already purchased the product, and the user who has not purchased the product only has the temporary account and does not have the user account.
  • the receiving and storing the purchase request sent by the user terminal may have two situations. One is that the server receives the purchase request sent by the old user through the user terminal, so the user account included in the purchase request is the old one. User account in the system; in another case, the server receives the purchase request sent by the new user through the user terminal, so the user account included in the purchase request is the old user who recommends the new user in the system. account number. It can be understood that the server can determine whether the purchase request is initiated by a new user or an old user by determining whether the purchase request further includes a temporary account.
  • Step S602 determining whether the temporary account is further included in the purchase request
  • the temporary account number is calculated according to the user unique identification code and the system unique identification code.
  • the user unique identification code may be implemented in various manners, such as a user's micro-signal, a user's WeChat QR code, a user ID of a system platform registered by the user, etc., it being understood that the implementation manner is not limited to The way mentioned.
  • the user unique identification code and the system unique identification code are calculated to obtain a temporary account, and the calculation manner may also be multiple, and may be added, multiplied, or calculated by encryption. It can be understood that the implementation manner and It is not limited to the manner mentioned.
  • the purchase request further includes a temporary account, and a user account is generated for the temporary account, and the user account generated by the temporary account is allocated according to the first predetermined rule according to the account matched by the first predetermined relationship;
  • the resources here can be monetary amount, or resources such as virtual currency or points.
  • the first predetermined rule and the first predetermined relationship may both be rules or relationships set in advance.
  • the account number matched by the user account generated by the temporary account in accordance with the first predetermined relationship includes: a superior account of the user account generated by the temporary account; an upper account of the user account generated by the temporary account; The upper-level upper-level account of the user account generated by the temporary account.
  • the account number matched according to the first predetermined relationship is not limited to the implementation manner, and may also include an upper-level multi-level account of the user account included in the purchase request, where the number of upper-level multi-levels is Can be set in advance.
  • the allocating resources according to the first predetermined rule that the user account generated by the temporary account is matched according to the first predetermined relationship includes: transferring the first quantity of resources to the upper account of the user account generated by the temporary account Transferring the second quantity of resources to the upper-level account of the user account generated by the temporary account; transferring the third quantity of resources to the upper-level upper-level account of the user account generated by the temporary account.
  • Allocating resources may include: respectively transferring a corresponding quantity of resources to an account of a corresponding number of levels.
  • the account number matched according to the first predetermined relationship includes: the upper level account of the user account included in the purchase request; and the upper two levels of the user account included in the purchase request, The upper three-level account of the user account included in the purchase request; the upper four-level account of the user account included in the purchase request, and the upper five-level account of the user account included in the purchase request, according to the first
  • the scheduling rule is that the resource is allocated to the account that matches the user account according to the first predetermined relationship, and may include: transferring the first quantity of resources to the upper-level account of the account of the user included in the purchase request; Transferring the quantity of resources to the upper two-level account of the account of the user included in the purchase request; transferring the third amount of resources to the upper three-level account of the account of the user included in the purchase request; The quantity of resources is transferred to the upper four level account with the user's account number included in the purchase request; the fifth number of resources are transferred to the user included in the purchase request
  • the number of levels of the upper multi-level can be set in advance and the number of corresponding resources can be set in advance.
  • the allocating resources according to the first predetermined rule that is matched with the user account according to the first predetermined relationship may further include: first removing a certain number of resources according to a preset ratio, and then depositing the remaining resources in the user account. Assignment between accounts that match the first predetermined relationship.
  • step S604 when the temporary account is not included in the purchase request, the user accounts in the purchase request are allocated resources according to the account matched by the second predetermined relationship according to the second predetermined rule.
  • the second predetermined rule and the second predetermined relationship may also be rules or relationships set in advance.
  • the account number matched by the user account in the purchase request according to the second predetermined relationship includes: the user account in the purchase request; the upper account of the user account in the purchase request; The upper-level account of the user account in the purchase request.
  • Allocating resources for the user account in the purchase request according to the second predetermined relationship according to the second predetermined rule includes: transferring a third quantity of resources to the user account in the purchase request; Transferring the second quantity of resources to the upper level account of the user account in the purchase request; transferring the first quantity of resources to the upper level account of the user account in the purchase request.
  • the second predetermined rule and the number of levels of the upper multi-level and the corresponding resources included in the second predetermined relationship may also be set in advance, and a certain amount of resources may be removed in advance according to a preset ratio, and then The remaining resources are allocated between the accounts whose user accounts are matched according to the first predetermined relationship, and details are not described herein again.
  • the third quantity may be greater than the second quantity, and the second quantity may be greater than the first quantity.
  • the ratio of the first quantity, the second quantity, and the third quantity may specifically be 1:2:3. It is to be understood that the third, second, and first number of specific values are not to be construed as limiting the invention.
  • the server sends the order information to the client of the offline manufacturer according to the purchase request.
  • the offline manufacturer can arrange delivery according to the order information, and deliver the logistics information related to the delivery to the server through the manufacturer client, and the server can store the logistics information into the order database.
  • the server may send a message for prompting to the user terminal corresponding to the user account included in the purchase request, prompting the
  • the information such as the completion of the purchase request, for example, the server may transmit the information that the content is "purchased successfully" to the user terminal.
  • the time when the prompt message is sent and the content sent can be implemented in various manners, and is not limited to the manner described.
  • the purchase request processing method provided by the embodiment of the present invention allocates resources by using different subscription rules by determining whether the purchase request further includes a temporary account, and the allocation manner is bound to the identity of the user, so that the method is
  • the resource allocation mechanism of the invention can be more conducive to the promotion of commodities and broaden the sales channels.
  • FIG. 7 is a flowchart of a method for processing a purchase request according to a fifth embodiment of the present invention. Referring to FIG. 7, this embodiment describes a process flow of a server, where the method includes:
  • Step S701 receiving a login request sent by the user terminal, where the login request includes a temporary account and a user account;
  • the login request may be a new user logging in to the micro-signal of the user through the user terminal, and paying attention to the WeChat public number of the system, obtaining a temporary account of the new user, and then scanning the user account corresponding to the user account of the old user through the user terminal. After the dimension code, it is initiated to the server. It can be understood that the implementation manner of the login request may be various, and is not limited thereto.
  • Step S702 determining whether the temporary account is stored in a server
  • Step S703 when the temporary account is not stored in the server, the temporary account is matched and stored in the user account, and the user account is an upper account of the temporary account;
  • the server determines that the temporary account has been stored in the server, the temporary account and the user account included in the login request are not matched and stored, that is, the server will only temporarily The account is matched and stored in the user account included in the login request initiated by the first time.
  • the server receives the login request sent by the user terminal again, when the login request includes the user account and the first initiated login request, When the included user accounts are different, the server does not match and store the user account included in the login request with the temporary account in the login request.
  • the server matches and stores the temporary account with the user account included in the first initiated login request, and ensures that the user account included in the first initiated login request is always the temporary account.
  • the server allocates resources for the upper-level account according to the predetermined rule. In this way, the rights of the user corresponding to the user account included in the first initiated login request can be always guaranteed, which further facilitates the promotion of the product and the widening of the product sales channel.
  • Step S704 receiving and storing a purchase request sent by the user terminal, where the purchase request includes a user account;
  • the method may further include: receiving an access request sent by the user terminal, where the access request includes a temporary account; determining whether the temporary account is stored in the server; The temporary account is not stored on the server, and is sent to the user terminal for prompting access loss. Lost information.
  • the temporary account in the access request received by the server is not stored on the server, it indicates that the temporary account does not have purchased the product on the server, or the temporary account does not pass the scan.
  • the old user's system QR code mode initiates a login request to the server, so the server sends information to the user terminal for prompting access failure.
  • the server filters users entering the system, and rejects users who are not in compliance with the standard, so that users who can enter the system can get better service and the user experience is further improved.
  • Step S705 it is determined whether the purchase request further includes a temporary account; when the purchase request further includes a temporary account, step S706 to step S710, otherwise, step S711;
  • Step S706 it is determined whether the temporary account is stored in the server; when the temporary account is not stored in the server, step S707 is performed, otherwise, step S708 is performed;
  • Step S707 generating a user account for the temporary account, matching and storing the temporary account, the user account generated by the temporary account, and the user account in the purchase request, where the user account in the purchase request is The superior account of the user account generated by the temporary account;
  • Step S708 Generate a user account for the temporary account, match and store the temporary account stored in the server, the upper account of the temporary account stored in the server, and the user account generated by the temporary account.
  • Step S709 generating a user two-dimensional code for the temporary account, and matching the user account generated by the temporary account with the user two-dimensional code, where the user two-dimensional code includes graphic information.
  • the user two-dimensional code may further include information such as a user's avatar, a user name, a temporary account number, a user's delivery address, and a user's contact information.
  • the graphic information included in the user two-dimensional code is the avatar information of the user, so that the server can quickly identify the identity information.
  • step S710 a user account is generated for the temporary account, and the user account generated by the temporary account is allocated according to the first predetermined rule according to the account matched by the first predetermined relationship.
  • step S711 is performed.
  • Step S711 Allocate resources for the account that is matched by the second predetermined relationship in the user account in the purchase request according to the second predetermined rule.
  • step S704, step S705, step S710 and step S711 are the same as steps S601 to S604 in the previous embodiment, and are not described in this embodiment.
  • the purchase request processing method provided by the embodiment of the present invention allocates resources by using different subscription rules by determining whether the purchase request further includes a temporary account, and the allocation manner is bound to the identity of the user, so that the method is
  • the resource allocation mechanism of the invention can be more conducive to the promotion of commodities and broaden the sales channels.
  • the user experience is further improved by further binding the upper-level account and the criteria for the user to enter the system, which can further facilitate the promotion of the product and broaden the sales channel.
  • FIG. 8 is a flowchart of a method for processing a purchase request according to a sixth embodiment of the present invention. Referring to FIG. 8 , this embodiment describes a process flow of a server, where the method includes:
  • Step S801 receiving and storing a purchase request sent by the user terminal, where the purchase request includes a user account;
  • Step S802 determining whether the temporary account is further included in the purchase request
  • Step S803 the purchase request further includes a temporary account, and the user account is generated for the temporary account, and the user account generated by the temporary account is allocated according to the first predetermined rule according to the account matched by the first predetermined relationship;
  • Step S804 When the purchase request does not include a temporary account, the user account in the purchase request is allocated resources according to the second predetermined relationship according to the second predetermined rule;
  • steps S801 to S804 are the same as steps S601 to S604 in the fourth embodiment, This embodiment will not be repeated.
  • Step S805 receiving and storing a return request sent by the user terminal, where the return request includes a user account;
  • Step S806 receiving a confirmation request corresponding to the consent of the return request
  • the server When the server receives the confirmation request corresponding to the return request, the corresponding return information is stored in the order database of the server.
  • Step S807 determining, according to the user account, whether the order corresponding to the return request is a first order corresponding to the user account;
  • the server may look up an order corresponding to the account in the order database according to the user account included in the return request. If there is no order corresponding to the account in the order database, it may be determined that the order corresponding to the purchase request is the first order corresponding to the account; if there is already an order corresponding to the account in the order database, The order corresponding to the purchase request is not the first order corresponding to the account.
  • Step S808 if yes, sending a cancel command to the user account to cancel the identification information corresponding to the user account, setting a lower account of the user account as a subordinate account of the upper account of the user account, and The amount of the order corresponding to the return request is transferred to the user account;
  • Step S809 otherwise, transferring the amount of the order corresponding to the return request to the user account.
  • the method may further include: receiving and storing an exit request sent by the user terminal, where the exit request includes a user account; sending a confirmation request to the user terminal; receiving the request for confirming the exit by the user terminal, and deleting the user by the server ID information corresponding to the account.
  • the server can set two ways to log out of the system. One is that the user can actively send an exit request to the server through the user terminal, and the other is that after the user sends the purchase request through the user terminal for the first time, the user sends a return to the server. Request, at this time, the server will actively give a refund and disconnect the matching relationship between the user account and other accounts, which can prevent the criminals from using the purchase request processing method to take profits, and can protect the legality of the user to a greater extent. rights and interests.
  • the purchase request processing method provided by the embodiment of the present invention allocates resources by using different subscription rules by determining whether the purchase request further includes a temporary account, and the allocation manner is bound to the identity of the user, so that the method is
  • the resource allocation mechanism of the invention can be more conducive to the promotion of commodities and broaden the sales channels.
  • the server is configured to log out of the system, so that the user can actively quit when using, or the user who the server considers to be unqualified will actively let it quit, further improving the user experience of the user who uses the system, and further beneficial to the product. Promotion and expansion of sales channels.
  • the above purchase request processing method can be applied to a distribution system.
  • the upper level account may be a superior distribution account, and the lower level account may be a lower level distribution account.
  • FIG. 9 shows a purchase request processing apparatus provided by an embodiment of the present invention.
  • the device 600 includes: a first receiving module 610, a first determining module 620, a first resource transfer module 630, and a second resource transfer module 640.
  • the first receiving module 610 is configured to receive and store a purchase request sent by the user terminal, where the purchase request includes a user account;
  • the first determining module 620 is configured to determine whether the purchase request is a first order corresponding to the user account
  • the first resource transfer module 630 is configured to allocate, according to the first predetermined rule, an account that matches the user account according to the first predetermined relationship, when the purchase request is a first order corresponding to the user account;
  • the second resource transfer module 640 is configured to allocate resources according to the second predetermined rule for the account that matches the user account according to the second predetermined relationship, when the purchase request is not the first order corresponding to the user account.
  • Each of the above modules may be implemented by software code.
  • each of the above modules may be stored in the memory 201 of the server 200.
  • the above modules can also be implemented by hardware such as an integrated circuit chip.
  • a person skilled in the art can understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium to which it is obtained may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

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

Abstract

本发明提供了一种购买请求处理方法及装置。该方法包括：接收并存储用户终端发送的购买请求，所述购买请求中包括用户帐号；判断所述购买请求是否为与所述用户帐号对应的首次订单；如果是，按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源；否则，按照第二预定规则为与所述用户帐号按照第二预定关系匹配的帐号分配资源。与现有技术相比，本发明的资源分配机制能够利于商品的推广，拓宽销售渠道。

Description

购买请求处理方法及装置
本申请要求于2015年11月17日提交中国专利局、申请号为201510789563.8、发明名称为“购买请求处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及互联网技术领域，具体而言，涉及一种购买请求处理方法及装置。
背景技术
现有的购买请求处理方法及装置较少涉及到返利机制的范畴，涉及到返利机制的方法在设置上也不够系统、完善，不利于商品的推广，商品的销售渠道较窄。
发明内容
有鉴于此，本发明提供了一种购买请求处理方法，以改善现有的方法及装置不利于商品推广以及商品的销售渠道较窄的不足。
为实现上述目的，本发明提供如下技术方案：
第一方面，本发明实施例提供了一种购买请求处理方法，所述方法包括：接收并存储用户终端发送的购买请求，所述购买请求中包括用户帐号；判断所述购买请求是否为与所述用户帐号对应的首次订单；如果是，按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源；否则，按照第二预定规则为与所述用户帐号按照第二预定关系匹配的帐号分配资源。
另一方面，本发明实施例还提供了一种购买请求处理装置，运行于服务器，包括：第一接收模块，用于接收并存储用户终端发送的购买请求，所述购买请求中包括用户帐号；第一判断模块，用于判断所述购买请求是否为与所述用户帐号对应的首次订单；第一资源转移模块，用于当所述购买请求是与所述用户帐号对应的首次订单时，按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源；第二资源转移模块，用于当所述购买请求不是与所述用户帐号对应的首次订单时，按照第二预定规则为与所述用户帐号按照第二预定关系匹配的帐号分配资源。
与现有技术相比，本发明实施例提供的一种购买请求处理方法及装置，通过判断所述购买请求是否为与所述用户帐号对应的首次订单，来采用不同的预订规则对资源进行分配，使得本发明的资源分配机制能够更利于商品的推广，拓宽销售渠道。
附图说明
为了更清楚的说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单的介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1所示为本发明实施例提供的购买请求处理方法的应用环境示意图；
图2是一种可应用于本发明实施例的服务器的结构框图；
图3为本发明第一实施例提供的购买请求处理方法的流程图；
图4为本发明第二实施例提供的购买请求处理方法的流程图；
图5为本发明第三实施例提供的购买请求处理方法的流程图；
图6为本发明第四实施例提供的购买请求处理方法的流程图；
图7为本发明第五实施例提供的购买请求处理方法的流程图；
图8为本发明第六实施例提供的购买请求处理方法的流程图；
图9是本发明实施例提供的购买请求处理装置的结构示意图。
具体实施方式
下面将结合本发明实施例中附图，对本发明实施例中的技术方案进行清楚、完整地描述。显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。以下对在附图中提供的本发明的实施例的详细描述并非旨在限制要求保护的本发明的范围，而是仅仅表示本发明的选定实施例。基于本发明的实施例，本领域技术人员在没有做出创造性劳动的前提下所获得的所有其他实施例，都属于本发明保护的范围。
图1所示为本发明实施例提供的购买请求处理方法的应用环境图。如图1所示，用户终端100以及服务器200位于无线或有线网络300中，通过该无线或有线网络300，用户终端100以及服务器200相互通信。
用户终端100具体可以包括智能手机、平板电脑、电子书阅读器、膝上型便携计算机、车载终端、可穿戴设备等等。用户终端100中可以安装浏览器或各种应用(包括系统应用以及第三方应用)的客户端。
图2示出了一种服务器的结构框图。如图2所示，服务器200包括：存储器201、处理器202以及网络模块203。
可以理解，图2所示的结构仅为示意，服务器200还可包括比图2中所示更多或者更少的组件，或者具有与图2所示不同的配置。图2中所示的各组件可以采用硬件、软件或其组合实现。另外，本发明实施例中的服务器还可以包括多个具体不同功能的服务器。
存储器201可用于存储软件程序以及模块，如本发明实施例中的购买请求处理方法及装置对应的程序指令/模块，处理器202通过运行存储在存储器201内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现本发明实施例中的购买请求处理方法。存储器201可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器201可进一步包括相对于处理器202远程设置的存储器，这些远程存储器可以通过网络连接至服务器200。进一步地，上述软件程序以及模块还可包括：服务模块221以及操作系统222。其中操作系统222，例如可为LINUX、UNIX、WINDOWS，其可包括各种用于管理系统任务(例如内存管理、存储设备控制、电源管理等)的软件组件和/或驱动，并可与各种硬件或软件组件相互通讯，从而提供其他软件组件的运行环境。服务模块221运行在操作系统222的基础上，并通过操作系统222的网络服务监听来自网络的请求，根据请求完成相应的数据处理，并返回处理结果给客户端。也就是说，服务模块221用于向客户端提供网络服务。
网络模块203用于接收以及发送网络信号。上述网络信号可包括无线信号或者有线信号。
于发明实施例中，用户终端100中安装有客户端，该客户端可以是浏览器也可以是第三方应用软件，与服务器(Server)端相对应，为用户提供本地服务，例如注册，浏览商品信息，根据用户的操作来选择要购买的商品等。所述用户终端100还可以包括厂商客户端，线下的厂商可以通过所述厂商客户端输入商品信息，例如商品说明信息和商品图像等。线下的厂商还可以通过所述厂商客户端输入预先制定的购买请求处理的具体规则。
本实施例中的服务器可以是单个的服务器，也可以是一个服务器集群，可以包括WEB服务器、搜索服务器、计算服务器等多个服务器。
本发明实施例中，所述服务器中可以包括多个数据库，例如会员数据库、商品数据库和订单数据库等。所述会员数据库可以储存用户的注册信息等；所述商品数据库可以储存商品信息以及与商品相关的线下的厂商的信息等；订单数据库可以储存订单信息， 与订单信息对应的用户的信息、商品信息以及相关的物流信息等。
商品数据库中的商品信息可以由线下厂商通过厂商客户端输入，并由服务器存储在商品数据库中。商品信息中可以包括商品图像以及商品说明等。
图1至图2所示只是本发明实施例的一种应用环境的举例，本发明的具体实施方式并不以此为限。
下面将结合附图，对本发明实施例提供的购买请求处理方法和装置进行详细介绍。
图3示出了本发明一实施例提供的一种购买请求处理方法的流程图，请参阅图3，本实施例描述的是服务端的处理流程，所述方法包括：
步骤S301，接收并存储用户终端发送的购买请求，所述购买请求中包括用户帐号；
步骤S302，判断所述购买请求是否为与所述用户帐号对应的首次订单；
当所述购买请求为与所述用户帐号对应的首次订单时，执行步骤S303，否则，执行步骤S304。
步骤S303，按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源；
步骤S304，按照第二预定规则为与所述用户帐号按照第二预定关系匹配的帐号分配资源。
本发明实施例提供的一种购买请求处理方法及装置，通过判断所述购买请求是否为与所述用户帐号对应的首次订单，来采用不同的预订规则对资源进行分配，使得本发明的资源分配机制能够更利于商品的推广，拓宽销售渠道。
图4示出了本发明第一实施例提供的一种购买请求处理方法。所述购买请求处理方法可以包括以下步骤S401至S404。
步骤S401，接收并存储用户终端发送的购买请求，所述购买请求中包括用户帐号；
接收并存储用户终端发送的购买请求，所述购买请求中包括用户帐号，服务器可以根据所述购买请求中的用户帐号建立购买请求与用户帐号之间的对应关系。
步骤S402，根据所述用户帐号，判断所述购买请求是否为与所述用户帐号对应的首次订单；如果是，执行步骤S403；否则，执行步骤S404。
服务器可以根据与所述购买请求中包括的用户帐号在订单数据库中查找与所述用户帐号对应的订单。若在订单数据库中，没有与该用户帐号对应的订单，则可以判定所述购买请求对应的订单为所述用户帐号对应的首次订单；若在订单数据库中，已经有与该用户帐号对应的订单，则可以判定所述购买请求对应的订单并不是所述用户帐号对应的首次订单。
步骤S403，按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源；
这里的资源可以是货币金额，也可以是虚拟货币或者积分等资源。
所述第一预定规则以及所述第一预定关系均可以为事先设置的规则或关系。例如，所述按照第一预定关系匹配的帐号，可以包括：所述购买请求中包括的用户帐号的上级帐号；所述购买请求中包括的用户帐号的上上级帐号；以及所述购买请求中包括的用户帐号的上上上级帐号。
可以理解的是，所述按照第一预定关系匹配的帐号并不局限于所述实施方式，也可以包括所述购买请求中包括的用户帐号的上层多级账号，其中，上层多级的级数可以事先设置。
所述按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源，可以包括：将第一数量的资源转移至与所述购买请求中包括的用户的帐号的上级帐号；将第二数量的资源转移至与所述购买请求中包括的用户的帐号的上上级帐号；将第三数 量的资源转移至与所述购买请求中包括的用户的帐号的上上上级帐号。
可以理解的是，当所述按照第一预定关系匹配的帐号包括用户帐号的上层多级账号时，其对应的所述按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源，可以包括：分别将对应数量的资源转移至对应的所在级数的账号。
例如，假设为5级，则所述按照第一预定关系匹配的帐号包括：所述购买请求中包括的用户帐号的上一级帐号；所述购买请求中包括的用户帐号的上两级帐号，所述购买请求中包括的用户帐号的上三级帐号；所述购买请求中包括的用户帐号的上四级帐号，所述购买请求中包括的用户帐号的上五级帐号，所述按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源，可以包括：将第一数量的资源转移至与所述购买请求中包括的用户的帐号的上一级帐号；将第二数量的资源转移至与所述购买请求中包括的用户的帐号的上两级帐号；将第三数量的资源转移至与所述购买请求中包括的用户的帐号的上三级帐号；将第四数量的资源转移至与所述购买请求中包括的用户的帐号的上四级帐号；将第五数量的资源转移至与所述购买请求中包括的用户的帐号的上五级帐号。
可以理解的是，上层多级的级数可以事先设置以及对应的资源的数量可以事先设置。
另外，所述按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源还可以包括，首先按照预设比例去掉一定数量的资源，然后将剩余的资源在所述用户帐号按照第一预定关系匹配的帐号之间进行分配。
步骤S404，按照第二预定规则为与所述用户帐号按照第二预定关系匹配的帐号分配资源。
所述第二预定规则以及所述第二预定关系也可以为事先设置的规则或关系。例如，所述按照第二预定关系匹配的帐号，可以包括：所述购买请求中包括的用户的帐号；所述购买请求中包括的用户的帐号的上级帐号；以及所述购买请求中包括的用户的帐号的上上级帐号。
所述按照第二预定规则为与所述用户帐号按照第二预定关系匹配的帐号分配资源，可以包括：将第三数量的资源转移至所述购买请求中包括的用户的帐号；将第二数量的资源转移至所述购买请求中包括的用户的帐号的上级帐号；将第一数量的资源转移至所述购买请求中包括的用户的帐号的上上级帐号。
同样的，所述第二预定规则以及所述第二预定关系中包括的上层多级的级数以及对应的资源的数量也可以事先设置，并且可以事先按照预设比例去掉一定数量的资源，然后将剩余的资源在所述用户帐号按照第一预定关系匹配的帐号之间进行分配，这里就不再赘述。
线下厂商可以通过厂商客户端制定资源分配规则，不同的订单类型对应不同的资源分配规则，制定好的资源分配规则(包括上述的第一预定规则和第二预定规则)存储在服务器中。线下厂商还可以通过厂商客户端制定退货时应退回的金额等。
该购买请求处理方法通过对不同的订单类型将资源按照不同的数量分配给相应的用户帐号的方式，可以在订单为首次时，给上上上级帐号提供较多数量的资源，也可以在订单为非首次时给购买请求对应的用户提高较多数量的资源，有利于更好地对商品进行推广，有利于较强地拓展商品销售的渠道。
图5示出的本发明第二实施例提供的一种购买请求处理方法。所述购买请求处理方法可以包括以下步骤S501至S513。
步骤S501，接收用户终端发送的注册信息。
步骤S502，根据所述注册信息生成新的用户帐号。
所述新的用户帐号可以被存储于服务器的会员数据库中。
步骤S503，当所述注册信息中包括其他用户帐号的标识信息时，将与所述标识信息对应的用户帐号设置为所述新的用户帐号的上级帐号，将所述新的用户帐号设置为与所述标识信息对应的用户帐号的下级帐号。
当服务器接收到的所述注册信息中包括其他用户帐号的标识信息时，可以视为新注册的用户帐号通过其他用户帐号推荐注册，标识信息可以作为推荐用户帐号的身份标识。此时，服务器便可以建立新注册用户帐号与标识信息对应用户帐号的对应关系。
当服务器接收到的所述注册信息中不包括其他用户帐号的标识信息时，即可以视为新注册的用户帐号未通过其他用户帐号的推荐而自行注册。此时，新注册的用户帐号被服务器视为无上级帐号。
可以理解，所述标识信息可以为二维码，也可以为唯一的一段字符串，所述标识信息的具体表现形式不应该理解为是对本发明的限制。
步骤S504，接收并存储用户终端发送的购买请求，所述购买请求中包括用户帐号。
当服务器接收到所述购买请求后，根据购买请求向线下厂商的客户端发送订单信息。线下厂商根据该订单信息可以安排发货，并将与发货相关的物流信息通过所述厂商客户端传递至服务器，服务器可以将所述物流信息储存进订单数据库。
步骤S505，根据所述用户帐号，判断所述购买请求是否为与所述用户帐号对应的首次订单。如果是，则执行步骤S506及S508至S511，如果否，则执行步骤S507、S509至S511。
步骤S506，将第一数量的资源转移至与所述购买请求中包括的用户的帐号的上级帐号；将第二数量的资源转移至与所述购买请求中包括的用户的帐号的上上级帐号；将第三数量的资源转移至与所述购买请求中包括的用户的帐号的上上上级帐号。
所述购买请求中包括的帐号的上上级帐号具体可以为所述购买请求中包括的帐号的上级帐号的上级帐号。
所述购买请求中包括的帐号的上上上级帐号具体可以为所述购买请求中包括的帐号的上级帐号的上级帐号的上级帐号。
第一数量、第二数量以及第三数量的比值具体可以为1:2:3。第一数量的资源最少，第三数量的资源最多，可以提高第三数量的资源获得帐号的收入，使该用户帐号更有进行推广的积极性，利于商品的推广。
步骤S507，将第三数量的资源转移至所述购买请求中包括的用户的帐号；将第二数量的资源转移至所述购买请求中包括的用户的帐号的上级帐号；将第一数量的资源转移至所述购买请求中包括的用户的帐号的上上级帐号。
所述购买请求中包括的帐号的上上级帐号具体可以为所述购买请求中包括的帐号的上级帐号的上级帐号。
当不是首次订单时，将第三数量的资源转移至所述购买请求中包括的帐号，与购买请求对应的帐号获得的最多，有利于提高用户的购买积极性，并利于将购买行为长时间持续下去。
具体地，所述第三数量可以大于所述第二数量，所述第二数量可以大于所述第一数量。优选的，第一数量、第二数量以及第三数量的比值具体可以为1:2:3。
可以理解，所述第三数量、第二数量以及第一数量的具体数值不应该理解为是对本发明的限制。
步骤S508，生成唯一与所述用户帐号对应的标识信息。
用户完成支付后，订单信息会存储于订单数据库中，且服务器于接收到与支付相关的信息后，将该订单设置为完成状态。当所述购买请求为与所述用户帐号对应的首次订 单时，生成唯一与所述用户帐号对应的标识信息。该标识信息具体可以是二维码。
步骤S509，接收并存储用户终端发送的退货请求，所述退货请求中包括所述用户帐号。
步骤S510，接收与同意所述退货请求相对应的确认请求。
当服务器接收与同意所述退货请求相对应的确认请求后，对应的退货信息会存储进所述服务器的订单数据库。
步骤S511，根据所述用户帐号，判断所述退货请求对应的订单是否为所述用户帐号对应的首次订单。如果是，则执行步骤S512，否则，执行步骤S513。
步骤S512，发送取消指令至所述用户帐号以取消所述用户帐号对应的标识信息，将所述用户帐号的下级帐号设置为所述用户帐号的上级帐号的下级帐号，并将所述退货请求对应的订单的金额转移至所述帐号。
若退货行为发生在首次订单时，服务器发送取消指令至退货行为对应的帐号以取消该用户帐号所对应的标识信息，然后将该用户帐号的上级帐号与该帐号的下级帐号建立匹配关系，断开该用户帐号与其他用户帐号的匹配关系。然后退回相应的订单的金额至所述用户帐号。
在退货行为发生于首次订单时，给予退款并断开该用户帐号与其他用户帐号的匹配关系，可以避免不法分子利用所述购买请求处理方法套取利润的行为，又可以较大限度地保护用户的合法权益。
步骤S513，将所述退货请求对应的订单的金额转移至所述用户帐号。
当退货行为发生于非首次订单时，仅发生退款行为，不改变该用户帐号与其他用户帐号的匹配关系。
上述的购买请求处理方法可以运用于分销系统中。其中，所述上级帐号具体可以为上级分销帐号，所述下级帐号具体可以为下级分销帐号。
图6示出了本发明第四实施例提供的购买请求处理方法的流程图，请参阅图6，本实施例描述的是服务器的处理流程，所述方法包括：
步骤S601，接收并存储用户终端发送的购买请求，所述购买请求中包括用户帐号；
所述用户帐号，是当服务器接收到用户终端发起的购买请求后，由服务器分配给用户的，是系统对用户的唯一认证号。可以理解的是，具有所述用户账号的用户是已经购买过产品的用户，而没有购买过产品的用户只具有临时账号，而不具备用户账号。
其中，所述接收并存储用户终端发送的购买请求可能有两种情况，一种是：服务器接收到老用户通过用户终端发送的购买请求，因此所述购买请求中包括的用户账号为所述老用户在系统中的用户账号；另一种情况是，服务器接收到新用户通过用户终端发送的购买请求，因此所述购买请求中包括的用户账号为推荐所述新用户的老用户在系统中的账号。可以理解的是，因此服务器可以通过判断所述购买请求中是否还包括临时帐号可以判断出所述购买请求是由新用户发起还是由老用户发起的。
步骤S602，判断所述购买请求中是否还包括临时帐号；
所述临时帐号，是根据用户唯一识别码以及系统唯一识别码计算获得。
其中，所述用户唯一识别码的实施方法有多种，例如用户的微信号，用户的微信二维码，用户注册的系统平台的用户ID等，可以理解的是，实施方式并不局限于所述提到的方式。
同样的，所述系统唯一识别码的实施方法有多种，例如微信公众号，微信公众二维码，系统平台的公众ID等，可以理解的是，实施方式并不局限于所述提到的方式。
将所述用户唯一识别码以及所述系统唯一识别码通过计算得出临时账号，计算的方式也可以有多种，可以相加，相乘，也可以通过加密计算，可以理解的是，实施方式并 不局限于所述提到的方式。
步骤S603，当所述购买请求中还包括临时帐号，为所述临时帐号生成用户账号，按照第一预定规则为由所述临时帐号生成的用户账号按照第一预定关系匹配的帐号分配资源；
其中，这里的资源可以是货币金额，也可以是虚拟货币或者积分等资源。
所述第一预定规则以及所述第一预定关系均可以为事先设置的规则或关系。例如，由所述临时帐号生成的用户账号按照第一预定关系匹配的帐号，包括：由所述临时帐号生成的用户账号的上级帐号；由所述临时帐号生成的用户账号的上上级帐号；以及由所述临时帐号生成的用户账号的上上上级帐号。
可以理解的是，所述按照第一预定关系匹配的帐号并不局限于所述实施方式，也可以包括所述购买请求中包括的用户帐号的上层多级账号，其中，上层多级的级数可以事先设置。
所述按照第一预定规则为由所述临时帐号生成的用户账号按照第一预定关系匹配的帐号分配资源，包括：将第一数量的资源转移至由所述临时帐号生成的用户账号的上级帐号；将第二数量的资源转移至由所述临时帐号生成的用户账号的上上级帐号；将第三数量的资源转移至由所述临时帐号生成的用户账号的上上上级帐号。
可以理解的是，当所述按照第一预定关系匹配的帐号包括用户帐号的上层多级账号时，其对应的所述按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源，可以包括：分别将对应数量的资源转移至对应的所在级数的账号。
例如，假设为5级，则所述按照第一预定关系匹配的帐号包括：所述购买请求中包括的用户帐号的上一级帐号；所述购买请求中包括的用户帐号的上两级帐号，所述购买请求中包括的用户帐号的上三级帐号；所述购买请求中包括的用户帐号的上四级帐号，所述购买请求中包括的用户帐号的上五级帐号，所述按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源，可以包括：将第一数量的资源转移至与所述购买请求中包括的用户的帐号的上一级帐号；将第二数量的资源转移至与所述购买请求中包括的用户的帐号的上两级帐号；将第三数量的资源转移至与所述购买请求中包括的用户的帐号的上三级帐号；将第四数量的资源转移至与所述购买请求中包括的用户的帐号的上四级帐号；将第五数量的资源转移至与所述购买请求中包括的用户的帐号的上五级帐号。
可以理解的是，上层多级的级数可以事先设置以及对应的资源的数量可以事先设置。
另外，所述按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源还可以包括，首先按照预设比例去掉一定数量的资源，然后将剩余的资源在所述用户帐号按照第一预定关系匹配的帐号之间进行分配。
步骤S604，当所述购买请求中不包括临时帐号，按照第二预定规则为所述购买请求中的所述用户账号按照第二预定关系匹配的帐号分配资源。
其中，所述第二预定规则以及所述第二预定关系也可以为事先设置的规则或关系。例如，所述购买请求中的所述用户账号按照第二预定关系匹配的帐号，包括：所述购买请求中的所述用户账号；所述购买请求中的所述用户账号的上级帐号；以及所述购买请求中的所述用户账号的上上级帐号。
按照第二预定规则为所述购买请求中的所述用户账号按照第二预定关系匹配的帐号分配资源，包括：将第三数量的资源转移至所述购买请求中的所述用户账号；将第二数量的资源转移至所述购买请求中的所述用户账号的上级帐号；将第一数量的资源转移至所述购买请求中的所述用户账号的上上级帐号。
同样的，所述第二预定规则以及所述第二预定关系中包括的上层多级的级数以及对应的资源的数量也可以事先设置，并且可以事先按照预设比例去掉一定数量的资源，然后将剩余的资源在所述用户帐号按照第一预定关系匹配的帐号之间进行分配，这里就不再赘述。
具体地，所述第三数量可以大于所述第二数量，所述第二数量可以大于所述第一数量。优选的，第一数量、第二数量以及第三数量的比值具体可以为1:2:3。可以理解，所述第三数量、第二数量以及第一数量的具体数值不应该理解为是对本发明的限制。
可以理解的是，当服务器接收到所述购买请求后，根据购买请求向线下厂商的客户端发送订单信息。线下厂商根据该订单信息可以安排发货，并将与发货相关的物流信息通过所述厂商客户端传递至服务器，服务器可以将所述物流信息储存进订单数据库。
并且，可以理解的是，当服务器收到所述购买请求或者当所述购买请求完成后，服务器可以向所述购买请求中包含的用户账号对应的用户终端发送用于提示的消息，提示所述购买请求完成等信息，例如服务器可以向用户终端发送内容为“购买成功”的信息。可以理解的是，所述提示消息发送的时间以及发送的内容可以有多种实施方式，并不局限于所述所述方式。
本发明实施例提供的购买请求处理方法，通过判断所述购买请求中是否还包括临时帐号，来采用不同的预订规则对资源进行分配，这种分配方式与使用者的身份进行绑定，使得本发明的资源分配机制能够更利于商品的推广，拓宽销售渠道。
图7示出了本发明第五实施例提供的购买请求处理方法的流程图，请参阅图7，本实施例描述的是服务器的处理流程，所述方法包括：
步骤S701，接收用户终端发送的登录请求，所述登录请求中包括临时帐号及用户账号；
其中，所述登录请求，可以是新用户通过用户终端登录自己的微信号，并关注系统的微信公众号后，获得新用户的临时账号，然后通过用户终端扫描老用户的用户账号对应的系统二维码后，向服务器发起的。可以理解的是，所述登录请求发起的实施方式可以有多种，并不局限于此。
步骤S702，判断所述临时帐号是否存储在服务器中；
步骤S703，当所述临时帐号没有存储在服务器，将所述临时帐号与所述用户账号匹配并存储起来，所述用户账号为所述临时帐号的上级帐号；
可以理解的是，如果服务器判断所述临时账号已经存储在服务器中，并不会将所述登录请求中包括的临时帐号以及用户账号匹配并存储起来，也就是说，所述服务器只会将临时帐号与第一次发起的登录请求中包括的用户账号进行匹配并存储，当服务器再次接收到用户终端发送的登录请求时，当所述登录请求中包括用户账号与第一次发起的登录请求中包括的用户账号不相同时，服务器并不会将这次登录请求中包括的用户账号与这次登录请求中的临时账号进行匹配并存储。
通过这种方式，所述服务器将临时帐号与第一次发起的登录请求中包括的用户账号进行匹配并存储，并保证第一次发起的登录请求中包括的用户账号始终为所述临时帐号的上级帐号，当用户终端发起的购买请求完成后，服务器会按照预定规则为上级账号分配资源。这样能够始终保障第一次发起的登录请求中包括的用户账号对应的用户的权益，进一步有利于商品的推广，以及商品销售渠道的扩宽。
步骤S704，接收并存储用户终端发送的购买请求，所述购买请求中包括用户账号；
在服务器接收并存储用户终端发送的购买请求之前，所述方法还可以包括：接收用户终端发送的访问请求，所述访问请求中包括临时帐号；判断所述临时帐号是否存储在服务器中；当所述临时帐号没有存储在服务器上，向所述用户终端发送用于提示访问失 败的信息。
可以理解的是，当服务器接收到的所述访问请求中的临时帐号没有存储在服务器上时，表示所述临时账号并没有在所述服务器上购买过产品，或者所述临时账号并没有通过扫描老用户的系统二维码的方式向服务器发起过登录请求，因此服务器向所述用户终端发送用于提示访问失败的信息。服务器通过这种方式对进入系统的用户进行筛选，将不合乎标准的用户拒之门外，使得能够进入系统的用户能够得到更优质的服务，用户体验进一步提升。
步骤S705，判断所述购买请求中是否还包括临时帐号；当所述购买请求中还包括临时帐号，执行步骤S706至步骤S710，否则，执行步骤S711；
步骤S706，判断所述临时帐号是否存储在服务器中；当所述临时帐号没有存储在服务器中，执行步骤S707，否则，执行步骤S708；
步骤S707，为所述临时帐号生成用户账号，将所述临时帐号、所述临时帐号生成的用户账号及所述购买请求中的用户账号匹配并存储起来，所述购买请求中的用户账号为所述临时帐号生成的用户账号的上级帐号；
步骤S708，为所述临时帐号生成用户账号，将所述服务器中存储的临时帐号，及服务器中存储的所述临时帐号的上级帐号，以及所述临时帐号生成的用户账号匹配并存储起来。
步骤S709，为所述临时帐号生成用户二维码，并将所述临时帐号生成的用户账号及用户二维码匹配起来，所述用户二维码包括图形信息。
其中，所述用户二维码，还可以包括了用户的头像、用户名、临时账号、用户的收货地址、用户的联系方式等信息。优选的，所述用户二维码中包括的图形信息为用户的头像信息，以便于服务器迅速识别身份信息。
步骤S710，为所述临时帐号生成用户账号，按照第一预定规则为由所述临时帐号生成的用户账号按照第一预定关系匹配的帐号分配资源。
当所述购买请求中不包括临时帐号，执行步骤S711，
步骤S711，按照第二预定规则为所述购买请求中的所述用户账号按照第二预定关系匹配的帐号分配资源。
可以理解的是，步骤S704，步骤S705，步骤S710以及步骤S711分别与上一实施例中的步骤S601至步骤S604相同，此实施例中就不再累述。
本发明实施例提供的购买请求处理方法，通过判断所述购买请求中是否还包括临时帐号，来采用不同的预订规则对资源进行分配，这种分配方式与使用者的身份进行绑定，使得本发明的资源分配机制能够更利于商品的推广，拓宽销售渠道。并且，进一步的的通过始终绑定上级账号的方式以及制定用户进入系统的标准，使得用户体验进一步提升，能够进一步有利于商品的推广，以及拓宽销售渠道。
图8示出了本发明第六实施例提供的购买请求处理方法的流程图，请参阅图8，本实施例描述的是服务器的处理流程，所述方法包括：
步骤S801，接收并存储用户终端发送的购买请求，所述购买请求中包括用户账号；
步骤S802，判断所述购买请求中是否还包括临时帐号；
步骤S803，当所述购买请求中还包括临时帐号，为所述临时帐号生成用户账号，按照第一预定规则为由所述临时帐号生成的用户账号按照第一预定关系匹配的帐号分配资源；
步骤S804，当所述购买请求中不包括临时帐号，按照第二预定规则为所述购买请求中的所述用户账号按照第二预定关系匹配的帐号分配资源；
可以理解的是，步骤S801至步骤S804与第四实施例中的步骤S601至步骤S604相同， 此实施例中就不再累述。
步骤S805，接收并存储用户终端发送的退货请求，所述退货请求中包括用户帐号；
步骤S806，接收与同意所述退货请求相对应的确认请求；
当服务器接收与同意所述退货请求相对应的确认请求后，对应的退货信息会存储进所述服务器的订单数据库。
步骤S807，根据所述用户账号，判断所述退货请求对应的订单是否为所述用户账号对应的首次订单；
服务器可以根据与所述退货请求中包括的用户账号在订单数据库中查找与帐号对应的订单。若在订单数据库中，没有与该帐号对应的订单，则可以判定所述购买请求对应的订单为所述帐号对应的首次订单；若在订单数据库中，已经有与该帐号对应的订单，则可以判定所述购买请求对应的订单并不是所述帐号对应的首次订单。
步骤S808，如果是，发送取消指令至所述用户帐号以取消所述用户帐号对应的标识信息，将所述用户帐号的下级帐号设置为所述用户帐号的上级帐号的下级帐号，并将所述退货请求对应的订单的金额转移至所述用户帐号；
步骤S809，否则，将所述退货请求对应的订单的金额转移至所述用户帐号。
所述方法还可以包括：接收并存储用户终端发送的退出请求，所述退出请求中包括用户账号；向所述用户终端发送确认请求；接收所述用户终端用于确认退出的请求，服务器删除用户帐号对应的标识信息。
可以理解的是，服务器可以设置两种退出系统的方式，一种是用户可以主动通过用户终端向服务器发送退出请求，另一种是，用户首次通过用户终端发送购买请求后，又向服务器发送退货请求，此时服务器会主动给予退款并断开该用户账号与其他帐号的匹配关系，可以避免不法分子利用所述购买请求处理方法套取利润的行为，又可以较大限度地保护用户的合法权益。
本发明实施例提供的购买请求处理方法，通过判断所述购买请求中是否还包括临时帐号，来采用不同的预订规则对资源进行分配，这种分配方式与使用者的身份进行绑定，使得本发明的资源分配机制能够更利于商品的推广，拓宽销售渠道。进一步的，服务器通过设置退出系统的方式，使得用户在使用时可以主动退出，或者服务器认为不合格的用户会主动让它退出，进一步提高了使用该系统的用户的用户体验，能够进一步有利于商品的推广，以及拓宽销售渠道。
上述的购买请求处理方法可以运用于分销系统中。其中，所述上级帐号具体可以为上级分销帐号，所述下级帐号具体可以为下级分销帐号。图9示出了本发明实施例提供的购买请求处理装置。所述装置600包括：第一接收模块610、第一判断模块620、第一资源转移模块630以及第二资源转移模块640。第一接收模块610，用于接收并存储用户终端发送的购买请求，所述购买请求中包括用户帐号；
第一判断模块620用于用于判断所述购买请求是否为与所述用户帐号对应的首次订单；
第一资源转移模块630用于用于当所述购买请求是与所述用户帐号对应的首次订单时，按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源；
第二资源转移模块640用于当所述购买请求不是与所述用户帐号对应的首次订单时，按照第二预定规则为与所述用户帐号按照第二预定关系匹配的帐号分配资源。
以上各模块可以是由软件代码实现，此时，上述的各模块可存储于服务器200的存储器201内。以上各模块同样可以由硬件例如集成电路芯片实现。
需要说明的是，本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。 对于装置类实施例而言，由于其与方法实施例基本相似，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，该的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述，仅是本发明的较佳实施例而已，并非对本发明作任何形式上的限制，虽然本发明已以较佳实施例揭露如上，然而并非用以限定本发明，任何熟悉本专业的技术人员，在不脱离本发明技术方案范围内，当可利用上述揭示的技术内容做出些许更动或修饰为等同变化的等效实施例，但凡是未脱离本发明技术方案内容，依据本发明的技术实质对以上实施例所作的任何简单修改、等同变化与修饰，均仍属于本发明技术方案的范围内。

Claims (20)

  1. 一种购买请求处理方法，其特征在于，所述方法包括：
    接收并存储用户终端发送的购买请求，所述购买请求中包括用户帐号；
    判断所述购买请求是否为与所述用户帐号对应的首次订单；
    如果是，按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源；
    否则，按照第二预定规则为与所述用户帐号按照第二预定关系匹配的帐号分配资源。
  2. 根据权利要求1所述的购买请求处理方法，其特征在于，所述方法还包括：
    接收用户终端发送的注册信息；
    根据所述注册信息生成新的用户帐号；
    当所述注册信息中包括其他用户帐号的标识信息时，将与所述标识信息对应的用户帐号设置为所述新的用户帐号的上级帐号，将所述新的用户帐号设置为与所述标识信息对应的用户帐号的下级帐号。
  3. 根据权利要求1所述的购买请求处理方法，其特征在于，所述按照第一预定关系匹配的帐号，包括：
    所述购买请求中包括的用户帐号的上级帐号；
    所述购买请求中包括的用户帐号的上上级帐号；以及
    所述购买请求中包括的用户帐号的上上上级帐号。
  4. 根据权利要求3所述的购买请求处理方法，其特征在于，所述按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源，包括：
    将第一数量的资源转移至与所述购买请求中包括的用户的帐号的上级帐号；
    将第二数量的资源转移至与所述购买请求中包括的用户的帐号的上上级帐号；
    将第三数量的资源转移至与所述购买请求中包括的用户的帐号的上上上级帐号。
  5. 根据权利要求1所述的购买请求处理方法，其特征在于，所述按照第二预定关系匹配的帐号，包括：
    所述购买请求中包括的用户的帐号；
    所述购买请求中包括的用户的帐号的上级帐号；以及
    所述购买请求中包括的用户的帐号的上上级帐号。
  6. 根据权利要求5所述的购买请求处理方法，其特征在于，所述按照第二预定规则为与所述用户帐号按照第二预定关系匹配的帐号分配资源，包括：
    将第三数量的资源转移至所述购买请求中包括的用户的帐号；
    将第二数量的资源转移至所述购买请求中包括的用户的帐号的上级帐号；
    将第一数量的资源转移至所述购买请求中包括的用户的帐号的上上级帐号。
  7. 根据权利要求1所述的方法，其特征在于，所述判断所述购买请求是否为与所述帐号对应的首次订单，具体包括：
    判断所述购买请求中是否还包括临时帐号；
    当所述购买请求中还包括临时帐号，则所述购买请求为首次订单；当所述购买请求中不包括临时帐号，则所述购买请求不为首次订单。
  8. 根据权利要求7所述的方法，其特征在于，当所述购买请求中还包括临时帐号，所述方法还包括：为所述临时帐号生成用户帐号。
  9. 根据权利要求8所述的方法，其特征在于，所述为临时帐号生成用户帐号，具体包括：
    判断所述临时帐号是否存储在服务器中；
    当所述临时帐号没有存储在服务器中，为所述临时帐号生成用户帐号，将所述临时帐号、所述临时帐号生成的用户帐号及所述购买请求中的用户帐号匹配并存储起来，所述购买请求中的用户帐号为所述临时帐号生成的用户帐号的上级帐号；
    当所述临时帐号已经存储在服务器中，为所述临时帐号生成用户帐号，将所述服务器中存储的临时帐号，及服务器中存储的所述临时帐号的上级帐号，以及所述临时帐号生成的用户帐号匹配并存储起来。
  10. 根据权利要求7所述的方法，其特征在于，所述接收并存储用户终端发送的购买请求之前，所述方法还包括：
    接收用户终端发送的登录请求，所述登录请求中包括临时帐号及用户帐号；
    判断所述临时帐号是否存储在服务器中；
    当所述临时帐号没有存储在服务器，将所述临时帐号与所述用户帐号匹配并存储起来，所述用户帐号为所述临时帐号的上级帐号。
  11. 根据权利要求7所述的方法，其特征在于，所述临时帐号是根据用户唯一识别码以及系统唯一识别码计算获得。
  12. 根据权利要求7所述的方法，其特征在于，所述接收并存储用户终端发送的购买请求之前，所述方法还包括：
    接收用户终端发送的访问请求，所述访问请求中包括临时帐号；
    判断所述临时帐号是否存储在服务器中；
    当所述临时帐号没有存储在服务器上，向所述用户终端发送用于提示访问失败的信息。
  13. 根据权利要求1所述的方法，其特征在于，与所述帐号按照第一预定关系匹配的帐号，包括：
    由所述临时帐号生成的用户账号的上级帐号；
    由所述临时帐号生成的用户账号的上上级帐号；以及
    由所述临时帐号生成的用户账号的上上上级帐号。
  14. 根据权利要求13所述的方法，其特征在于，按照第一预定规则为与所述帐号按照第一预定关系匹配的帐号分配资源，包括：
    将第一数量的资源转移至由所述临时帐号生成的用户账号的上级帐号；
    将第二数量的资源转移至由所述临时帐号生成的用户账号的上上级帐号；
    将第三数量的资源转移至由所述临时帐号生成的用户账号的上上上级帐号。
  15. 根据权利要求1所述的购买请求处理方法，其特征在于，所述方法还包括：
    当所述购买请求为与所述用户帐号对应的首次订单时，生成唯一与所述帐号对应的标识信息。
  16. 根据权利要求15所述的购买请求处理方法，其特征在于，上述唯一与所述用户帐号对应的标识信息为用户二维码，并将所述用户帐号及所述用户二维码匹配起来，所述用户二维码包括图形信息。
  17. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    接收并存储用户终端发送的退出请求，所述退出请求中包括用户帐号；
    向所述用户终端发送确认请求；
    接收所述用户终端用于确认退出的请求，服务器删除用户帐号对应的标识信息。
  18. 根据权利要求15所述的购买请求处理方法，其特征在于，所述方法还包括：
    接收并存储用户终端发送的退货请求，所述退货请求中包括用户帐号；
    接收与同意所述退货请求相对应的确认请求；
    根据所述用户帐号，判断所述退货请求对应的订单是否为所述用户帐号对应的首次订单；
    如果是，发送取消指令至所述用户帐号以取消所述用户帐号对应的标识信息，将所述用户帐号的下级帐号设置为所述用户帐号的上级帐号的下级帐号，并将所述退货请求对应的订单的金额转移至所述用户帐号；
    否则，将所述退货请求对应的订单的金额转移至所述用户帐号。
  19. 根据权利要求6或14所述的购买请求处理方法，其特征在于，所述第三数量大于所述第二数量，所述第二数量大于所述第一数量。
  20. 一种购买请求处理装置，运行于服务器，其特征在于，包括：
    第一接收模块，用于接收并存储用户终端发送的购买请求，所述购买请求中包括用户帐号；
    第一判断模块，用于判断所述购买请求是否为与所述用户帐号对应的首次订单；
    第一资源转移模块，用于当所述购买请求是与所述用户帐号对应的首次订单时，按照第一预定规则为与所述用户帐号按照第一预定关系匹配的帐号分配资源；
    第二资源转移模块，用于当所述购买请求不是与所述用户帐号对应的首次订单时，按照第二预定规则为与所述用户帐号按照第二预定关系匹配的帐号分配资源。
PCT/CN2016/080370 2015-11-17 2016-04-27 购买请求处理方法及装置 WO2017084245A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/522,293 US20180308138A1 (en) 2015-11-17 2016-04-27 Data processing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510789563.8A CN105469294A (zh) 2015-11-17 2015-11-17 购买请求处理方法及装置
CN201510789563.8 2015-11-17

Publications (1)

Publication Number Publication Date
WO2017084245A1 true WO2017084245A1 (zh) 2017-05-26

Family

ID=55606959

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/080370 WO2017084245A1 (zh) 2015-11-17 2016-04-27 购买请求处理方法及装置

Country Status (3)

Country Link
US (1) US20180308138A1 (zh)
CN (1) CN105469294A (zh)
WO (1) WO2017084245A1 (zh)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105469294A (zh) * 2015-11-17 2016-04-06 南京唐一微数字科技有限公司 购买请求处理方法及装置
AU2017202892A1 (en) * 2016-04-18 2017-11-02 Nanjin Tangyi Digital Technology Co., Ltd Data processing method and apparatus
CN105956862A (zh) * 2016-04-18 2016-09-21 南京唐微数字科技有限公司 购买请求处理方法及装置
CN106330913A (zh) * 2016-08-25 2017-01-11 南京唐微数字科技有限公司 数据处理方法及装置
CN110490572B (zh) 2018-05-15 2023-06-09 腾讯科技（深圳）有限公司 一种支付方法、装置、相关设备及系统
CN110417851B (zh) * 2019-06-12 2024-01-23 平安科技（深圳）有限公司 数据匹配方法、托管平台、存储介质及计算机设备
CN110910197A (zh) * 2019-10-16 2020-03-24 青岛合聚富电子商务有限公司 一种订单处理方法
CN111612512A (zh) * 2020-04-11 2020-09-01 上海淇玥信息技术有限公司 一种资源分配方法、装置和电子设备
CN111522830B (zh) * 2020-04-27 2023-06-09 浙江坤盈科技有限公司 资源分配方法、计算机设备和存储介质
CN112184246A (zh) * 2020-10-13 2021-01-05 深圳壹账通智能科技有限公司 账本管理方法、装置、设备以及存储介质
CN113807858B (zh) * 2021-09-23 2024-04-26 中科软科技股份有限公司 一种基于决策树模型的数据处理方法及相关设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101004822A (zh) * 2005-12-16 2007-07-25 e2因特莱科迪伏有限公司 折扣卡系统
CN101114358A (zh) * 2007-08-30 2008-01-30 徐世元 利用通讯技术的团购结算支付系统和方法
CN101593338A (zh) * 2009-07-13 2009-12-02 招商银行股份有限公司 一种处理电子交易请求的方法和系统
CN102708507A (zh) * 2012-06-19 2012-10-03 重庆先迈通信技术有限公司 一种互联网络交易业务的返利推广方法
CN105469294A (zh) * 2015-11-17 2016-04-06 南京唐一微数字科技有限公司 购买请求处理方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7966235B1 (en) * 2001-10-01 2011-06-21 Lawson Software, Inc. Method and apparatus providing automated control of spending plans
EP2425386A2 (en) * 2009-04-30 2012-03-07 Donald Michael Cardina Systems and methods for randomized mobile payment
US8401904B1 (en) * 2011-11-13 2013-03-19 Google Inc. Real-time payment authorization
US20160292663A1 (en) * 2015-03-31 2016-10-06 Capital One Services, Llc Systems and methods for allocating transactions
US10769654B2 (en) * 2015-04-27 2020-09-08 Hrb Innovations, Inc. Payment vehicle with personalized rewards program
US10097953B1 (en) * 2015-06-13 2018-10-09 United Services Automobile Association (Usaa) Network based resource management and allocation

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101004822A (zh) * 2005-12-16 2007-07-25 e2因特莱科迪伏有限公司 折扣卡系统
CN101114358A (zh) * 2007-08-30 2008-01-30 徐世元 利用通讯技术的团购结算支付系统和方法
CN101593338A (zh) * 2009-07-13 2009-12-02 招商银行股份有限公司 一种处理电子交易请求的方法和系统
CN102708507A (zh) * 2012-06-19 2012-10-03 重庆先迈通信技术有限公司 一种互联网络交易业务的返利推广方法
CN105469294A (zh) * 2015-11-17 2016-04-06 南京唐一微数字科技有限公司 购买请求处理方法及装置

Also Published As

Publication number Publication date
US20180308138A1 (en) 2018-10-25
CN105469294A (zh) 2016-04-06

Similar Documents

Publication Publication Date Title
WO2017084245A1 (zh) 购买请求处理方法及装置
US9251327B2 (en) Method and system for providing behavioral bi-directional authentication
US20210049579A1 (en) Multi-factor identity authentication
US9852283B2 (en) Confirming the identity of integrator applications
JP2019083068A (ja) 情報認証のための方法およびシステム
KR20170137884A (ko) 통신 세션에서의 가상 어시스턴트
CN109257321B (zh) 安全登录方法和装置
WO2014008764A1 (zh) 一种利用社交网络实现网络交易的信息处理系统和方法
US9384330B2 (en) Providing user attributes to complete an online transaction
US11636463B2 (en) System and methods for zero-step customer proximity detection using mobile device low emissions beacons
US9124570B1 (en) Providing an assessment of authentication requests
JP2021527271A (ja) アテンショントークンデジタル資産報酬
US11257105B2 (en) System and method for customer and business referral with a concierge system
CN108650289A (zh) 一种基于区块链的管理数据的方法和装置
US20150287114A1 (en) Computer-implemented system of grouping buyer requests matching in combination with a seller offer
KR102540415B1 (ko) 블록체인 기반의 안전하고 신뢰 가능한 데이터 거래 방법 및 데이터 거래 플랫폼 제공 시스템
US11270292B2 (en) Key pair authentication in a label tracking system
US20230206246A1 (en) Systems for Securing Transactions Based on Merchant Trust Score
US11856004B2 (en) Systems and methods for identifying malicious cryptographic addresses
US20170270473A1 (en) Systems and methods for securely searching and exchanging database relationships between registered inventory
US20210209518A1 (en) Peer to peer rental reservations
TWI810143B (zh) 使用統一資源定位符折價券提供數位商品之方法及其裝置與系統
CN110458670A (zh) 一种商品数字凭证处理方法及装置
US12126629B2 (en) Systems and methods for identifying malicious cryptographic addresses
KR102118339B1 (ko) WiFi AP를 이용한 자율 로그인 시스템 및 방법

Legal Events

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

Ref document number: 16865428

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15522293

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16865428

Country of ref document: EP

Kind code of ref document: A1