WO2017181933A1 - 数据处理方法及装置 - Google Patents

数据处理方法及装置 Download PDF

Info

Publication number
WO2017181933A1
WO2017181933A1 PCT/CN2017/080864 CN2017080864W WO2017181933A1 WO 2017181933 A1 WO2017181933 A1 WO 2017181933A1 CN 2017080864 W CN2017080864 W CN 2017080864W WO 2017181933 A1 WO2017181933 A1 WO 2017181933A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
user
temporary
level
purchase request
Prior art date
Application number
PCT/CN2017/080864
Other languages
English (en)
French (fr)
Inventor
唐燚
Original Assignee
南京唐一微数字科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201610240012.0A external-priority patent/CN105956862A/zh
Priority claimed from CN201610729813.3A external-priority patent/CN106330913A/zh
Application filed by 南京唐一微数字科技有限公司 filed Critical 南京唐一微数字科技有限公司
Priority to AU2017202892A priority Critical patent/AU2017202892A1/en
Publication of WO2017181933A1 publication Critical patent/WO2017181933A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • 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

Definitions

  • the present application relates to the field of computer data processing technologies, and in particular, to a data processing method and apparatus.
  • the embodiment of the present application provides a data processing method and device.
  • the purchase request further includes a temporary account, generating a system account for the temporary account, and allocating resources for the account having the first predetermined relationship with the generated system account according to the first predetermined rule;
  • the resource is allocated to the account having the second predetermined relationship with the system account in the purchase request according to the second predetermined rule.
  • a data processing apparatus includes: a processor and a storage medium storing computer executable instructions, when the processor runs the computer executable instructions, the processor executes:
  • Another data processing apparatus includes: a processor and a storage medium storing computer executable instructions, when the processor runs the computer executable instructions, the processor executes:
  • the purchase request further includes a temporary account, generating a system account for the temporary account, and allocating resources for the account having the first predetermined relationship with the generated system account according to the first predetermined rule;
  • the resource is allocated to the account having the second predetermined relationship with the system account in the purchase request according to the second predetermined rule.
  • FIG. 1 is a schematic diagram of interaction between a server and a user terminal according to an embodiment of the present application
  • FIG. 2 is a schematic block diagram of a server provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of a data processing method according to an embodiment of the present application.
  • FIG. 4 is a flowchart of a preset rule in a data processing method according to an embodiment of the present application.
  • FIG. 5 is a flowchart of step S360 in a data processing method according to an embodiment of the present application.
  • FIG. 6 is a flowchart of step S370 in a data processing method according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of functional modules of a data processing apparatus according to an embodiment of the present application.
  • FIG. 8 is a flowchart of another data processing method according to an embodiment of the present application.
  • FIG. 9 is a flowchart of another data processing method according to an embodiment of the present application.
  • FIG. 10 is a flowchart of another data processing method provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of functional modules of another data processing apparatus according to an embodiment of the present disclosure.
  • FIG. 1 it is a schematic diagram of the server 200 provided by the embodiment of the present application interacting with the user terminal 100 respectively.
  • the server 200 performs data communication with one or more user terminals 100 through the network 300 for data communication. Or interaction.
  • Server 200 can be a distributed file storage server, a web server, a database server, and the like.
  • the user terminal 100 may be a personal computer (PC), a tablet, a smartphone, or the like.
  • the client terminal 100 is installed with a client, and the client may be a browser or a third-party application software.
  • the user is provided with a local service, such as registration, login, and browsing. Wait.
  • the server 200 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 200 can include a data processing device 210, a memory 220, a storage controller 230, and a processor 240.
  • the components of the memory 220, the memory controller 230, and the processor 240 are electrically connected directly or indirectly to each other to implement data transmission or interaction.
  • the components can be electrically connected to one another via one or more communication buses or signal lines.
  • the data processing device 210 may include at least one software function module that may be stored in the memory 220 or in an operating system (OS) of the server 200 in the form of software or firmware.
  • the processor 240 is configured to execute executable modules stored in the memory 220, such as software functional modules or computer programs included in the data processing device 210.
  • the memory 220 may be, but not limited to, a random access memory (RAM), a read only memory (ROM), and a programmable read-only memory (PROM). Erasable Programmable Read-Only Memory (EPROM), Electric Erasable Programmable Read-Only Memory (EEPROM), and the like.
  • RAM random access memory
  • ROM read only memory
  • PROM programmable read-only memory
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electric Erasable Programmable Read-Only Memory
  • the memory 220 is used to store a program, and the processor 240 executes the program after receiving the execution instruction.
  • the method executed by the server defined by the flow process disclosed in any of the foregoing embodiments may be applied to the processor, or Implemented by the processor.
  • Processor 240 may be an integrated circuit chip with signal processing capabilities.
  • the above processor can be a pass
  • the processor includes a central processing unit (CPU), a network processor (NP), etc., and may also be a digital signal processor (DSP) or an application specific integrated circuit (Application Specific Integrated Circuit). , ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.
  • DSP digital signal processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • 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.
  • FIG. 3 is a flowchart of a data processing method provided by an embodiment of the present application. Referring to FIG. 3, the method described in this embodiment is performed by a server, and the method includes steps S310 to S350.
  • step S310 a join request of the user is received, and the join request includes the temporary account of the user and the system account of the recommender.
  • the temporary account number can be calculated according to the user unique identification code and the system unique identification code.
  • the method for implementing the unique identifier of the user may be various, and may be a social network account of the user, such as a micro signal of the user, a QR code of the WeChat, a user ID of the system platform registered by the user, etc., it can be understood that the implementation manner is It is not limited to the manner mentioned.
  • system unique identifier which may be the social network public number of the system, such as WeChat public number, WeChat public QR code, public ID of the system platform, etc. It can be understood that the implementation method is It is not limited to the manner mentioned.
  • the calculation method can also be various, and can be added, multiplied, or calculated by encryption. It can be understood that the implementation is implemented. The manner is not limited to the manner mentioned.
  • the system account number is assigned to the user by the server and is the unique authentication number of the system to the user.
  • step S320 the area where the user is located is obtained according to the temporary account of the user.
  • step S320 There are various implementations of the step S320.
  • the application interface provided by the WeChat to the third party may be invoked to invoke the interface program to obtain the request to be added to the user. region.
  • the application interface provided by the WeChat to the third party may be invoked to invoke the interface program to obtain the request to be added to the user. region.
  • the interface program may be invoked to obtain the request to be added to the user. region.
  • step S330 it is determined whether the area where the user is located is the same as the area where the recommender is located.
  • the recommender's area can be obtained from the recommender's temporary account when the recommender enters through the area verification, and stored in the server.
  • the area where the recommender is located may be obtained from the server and matched with the area where the user is located, and the matching manner may be various, for example, string matching.
  • Judging whether the user and the recommender are in the same area can be determined according to the geographical location of the user and the recommender.
  • the size of the area involved in the present application may be determined according to actual conditions, and the embodiment of the present application is not limited. For example, it can be considered that the user and the recommender who are in Jiangsu province belong to the same area; it can also be considered that the user and the recommender in China belong to the same area; in addition, users and recommenders respectively in China and Japan belong to the same area.
  • step S340 is performed; otherwise, step S350 is performed.
  • step S340 a system account is generated for the user according to a preset rule, and the system account of the user is stored.
  • step S340 may include steps S341 to S347.
  • step S341 it is determined whether the temporary account of the user is associated with the system unique identifier.
  • step S342 is performed; otherwise, step S343 is performed.
  • step S342 a system account is generated for the user, and the system account of the user is stored.
  • step S343 information corresponding to the system unique identification code is transmitted to the user terminal of the user.
  • the server returns a system unique identifier, that is, a contact interface of the WeChat public number, to the user terminal of the user.
  • step S344 a user instruction is received.
  • step S345 it is determined whether the user instruction is a selection instruction for selecting a system unique identification code.
  • step S346 is performed, otherwise, step S347 is performed.
  • step S346 a system account is generated for the user, and the system account of the user is stored.
  • the user unique identifier is a user micro-signal
  • the user pays attention to the system WeChat public number through the user terminal, that is, the user instruction is used to select a selection instruction associated with the system unique identifier, and the user joins the system.
  • the system WeChat public number through the user terminal, that is, the user instruction is used to select a selection instruction associated with the system unique identifier, and the user joins the system.
  • the user unique identifier is a user micro-signal
  • step S347 the prompt information for prompting the joining of the system to be failed is sent to the user terminal of the user.
  • the user unique identifier is the user micro-signal
  • the user selects not to pay attention to the system WeChat public number through the user terminal, and the user cannot join the system, and the user terminal of the user receives the prompt information for prompting to join the system, for example, “scanning code fails. , the area does not match, and so on.
  • the method may further include step S360.
  • step S360 the information corresponding to the temporary account of the user is sent to the user terminal of the recommender.
  • the information corresponding to the temporary account of the user includes the social network avatar of the user, the social network account or the regional information, and the like, so that the recommender can know the system of the user through the associated recommender when the user receives the information through the user terminal.
  • the account was successfully added to the system.
  • the user can associate the referrer's system account by scanning the recommender's WeChat QR code.
  • the user is a subordinate user of the recommender, which is beneficial to reasonable resource allocation.
  • step S350 the prompt information for prompting the joining of the system to be failed is sent to the user terminal of the user.
  • the method may further include step S370.
  • step S370 prompt information for prompting how to join the system is sent to the user terminal of the user.
  • the user terminal of the user may be sent "Please scan the QR code of the XX city recommender” or "Edit the area in my WeChat-click avatar-area", etc., so that the user receives the prompt information. Can know how to join the system, further increasing the proportion of system users joining by region.
  • the data processing method provided by the embodiment of the present application determines whether the user is allowed to join the system by determining whether the area where the user is located and the area where the recommender is located, that is, performing sub-regional management when the user joins the system, only in the case of the recommender. Users in the area can join the system. In this way, system users can be managed according to the area, and the subsequent system users can be allocated according to the area.
  • FIG. 7 is a functional block diagram of the data processing device 210 shown in FIG. 2 according to an embodiment of the present application.
  • the data processing device 210 operates on the server 200.
  • the data processing device 210 includes a receiving module 211, an obtaining module 212, and a processing module 213.
  • the receiving module 211 is configured to receive a join request of the user, where the join request includes the temporary account of the user and the system account of the recommender.
  • the obtaining module 212 is configured to obtain an area where the user is located according to the temporary account of the user.
  • the processing module 213 is configured to determine whether the area where the user is located is the same as the area where the recommender is located; if the same, generate a system account for the user according to a preset rule, and store the system account of the user; if different, the user is The user terminal sends a prompt message for prompting to join the system.
  • the processing module 213 determines whether the temporary account of the user is associated with a system unique identifier. If so, the processing module 213 generates a system account for requesting to join the user, and stores the system account of the user. If not, the processing module 213 sends the information corresponding to the system unique identifier to the user; receives the user instruction; if the user instruction is for selecting a selection instruction associated with the system unique identifier, generating a system account for the user and storing The user's system account.
  • the processing module 213 may further send prompt information for prompting the joining system to fail to the user terminal of the user.
  • the data processing apparatus may further include a first sending module 214, configured to send information corresponding to the temporary account of the user to the user terminal of the recommender.
  • the data processing apparatus further includes a second sending module 215, configured to send, to the user terminal of the user, prompt information for prompting how to join the system.
  • Each of the above modules may be implemented by software code.
  • each of the above modules may be stored in the memory 220 of the server 200.
  • the above modules can also be implemented by hardware such as an integrated circuit chip.
  • FIG. 8 is a flowchart of another data processing method provided by an embodiment of the present application, which may be applied to the environment shown in FIG. 1 and FIG.
  • the client installed by the user terminal 100 can also select an item to be purchased according to the operation of the user.
  • the client can also include a vendor client, and offline vendors can input product information, such as product description information and product images, through the vendor client. Offline vendors can also enter pre-defined specific rules for purchase request processing through the vendor client.
  • the server 200 may include a plurality of databases, such as a member database, a commodity database, an order database, and the like.
  • the member database may store the user's registration information, etc.
  • the product database may store the product information and the information of the offline manufacturer related to the product
  • the order database may store the order information, the user information and the product information corresponding to the order information, and Relevant logistics information, etc.
  • the commodity information in the commodity database can be input by the offline manufacturer through the vendor client and stored by the server 200 in the commodity database.
  • Product information may include product images, product descriptions, and the like.
  • the method described in this embodiment is executed by a server, and the method includes steps S810 to S840.
  • step S810 a purchase request sent by the user terminal is received and stored, and the purchase request includes a system account.
  • the system account number assigned to the user by the server is the unique authentication number of the system to the user. Understandably, having The user of the system account is a system user, for example, a user who has purchased a product on the system, and the temporary user only has a temporary account and does not have a system account.
  • the receiving and storing the purchase request sent by the user terminal may have two situations. One is: the server receives the purchase request sent by the system user through the user terminal, so the system account included in the purchase request is the system user in the system. In another case, the server receives the purchase request sent by the temporary user through the user terminal, so the system account included in the purchase request is the system account of the recommender. Therefore, the server can determine whether the purchase request is initiated by the temporary user or by the system user by determining whether the purchase request further includes a temporary account.
  • step S820 it is determined whether a temporary account is further included in the purchase request.
  • the temporary account number can be calculated according to the user unique identification code and the system unique identification code.
  • the method for implementing the unique identifier of the user may be various, and may be a social network account of the user, such as a user's micro-signal, a WeChat QR code, a user ID of a system platform registered by the user, etc., which can be understood to be implemented.
  • the manner is not limited to the manner mentioned.
  • system unique identifier which may be the social network public number of the system, such as WeChat public number, WeChat public QR code, public ID of the system platform, etc. It can be understood that the implementation method is It is not limited to the manner mentioned.
  • the calculation method can also be various, and can be added, multiplied, or calculated by encryption. It can be understood that the implementation method is It is not limited to the manner mentioned.
  • step S830 when the purchase request further includes a temporary account, a system account is generated for the temporary account, and resources are allocated for the account having the first predetermined relationship with the generated system account according to the first predetermined rule.
  • the resources here can be monetary amount, or resources such as virtual currency or points.
  • Both the first predetermined rule and the first predetermined relationship may be rules or relationships set in advance.
  • the account number of the system account having the first predetermined relationship may include the N-level upper-level account of the system account, where N is a natural number, and the value of N may be determined according to actual conditions, which is not limited in the embodiment of the present application.
  • the account having the first predetermined relationship with the generated system account may include a layer upper level account of the system account, a second level upper account of the system account, and a third level upper level of the system account. account number.
  • allocating resources for an account having a first predetermined relationship with the generated system account according to the first predetermined rule may include: transferring the first quantity of resources to a layer upper level account of the system account; The second quantity of resources is transferred to the second-level upper-level account of the system account; the third quantity of resources is transferred to the third-level upper-level account of the system account.
  • the ratio between the first quantity, the second quantity, and the third quantity may be determined according to actual conditions, and is not limited in the embodiment of the present application.
  • the third amount can be greater than the second amount, the second amount can be greater than the first amount, and so on.
  • the ratio of the first quantity, the second quantity, and the third quantity may be 1:2:3, and the like.
  • step S840 when the temporary account is not included in the purchase request, the resource is allocated to the account having the second predetermined relationship with the system account in the purchase request 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 with the second predetermined relationship with the system account in the purchase request may include the account itself and the N-level upper account of the system account, where N is a natural number, and the value of N may be determined according to actual conditions. No restrictions.
  • the account with the second predetermined relationship with the system account in the purchase request may include the system account itself, a layer upper account of the system account, and a second-level upper account of the system account.
  • allocating resources for the account having the second predetermined relationship with the system account in the purchase request according to the second predetermined rule may include: transferring the fourth quantity of resources to the system account in the purchase request; The resource is transferred to a layer upper level account of the system account in the purchase request; the sixth quantity resource is transferred to the second level upper account of the system account in the purchase request.
  • the ratio between the fourth quantity, the fifth quantity, and the sixth quantity may be determined according to actual conditions, and is not limited in the embodiment of the present application.
  • the fourth number can be greater than the fifth number
  • the fifth number can be greater than the sixth number, and so on.
  • the ratio of the fourth quantity, the fifth quantity, and the sixth quantity may be 3:2:1 Wait.
  • the server When the server receives the purchase request, it 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 system account included in the purchase request, prompting the purchase request to complete information, for example, the server may send the content to the user terminal as "Purchase success" information.
  • the time when the prompt message is sent and the content sent may be various embodiments, and is not limited to the manner.
  • the data processing method provided by the embodiment of the present application 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 resources of the application.
  • the distribution mechanism can be more conducive to the promotion of goods and expand sales channels.
  • FIG. 9 is a flowchart of another data processing method provided by an embodiment of the present application. Referring to FIG. 9, the method described in this embodiment is performed by a server, and the method includes steps S910 to S9110.
  • step S910 a login request sent by the user terminal is received, where the login request includes a temporary account and a system account.
  • the login request may be that the temporary user logs in to his social network account through the user terminal, and pays attention to the social network public number of the system. For example, after the temporary user logs in to his own micro-signal and pays attention to the WeChat public number of the system, the temporary account of the temporary user is obtained, and the user terminal scans the system two-dimensional code corresponding to the system account of the system user, and then initiates to the server.
  • the implementation manner of the login request may be various, and is not limited thereto.
  • step S920 it is determined whether the temporary account is stored in the server.
  • step S930 when the temporary account is not stored in the server, the temporary account is matched and stored in the system account, and the system account is a layer upper account of the temporary account.
  • the server determines that the temporary account has been stored in the server, the temporary account and the system account included in the login request are not matched and stored, that is, the server only uses the temporary account and the first initiated login request.
  • the included system account is matched and stored.
  • the server receives the login request sent by the user terminal again, when the login request includes the system account and the system account included in the first initiated login request is different, the server does not Match and store the system account included in this login request with the temporary account in this login request.
  • the server matches and stores the temporary account with the system account included in the first initiated login request, and ensures that the system account included in the first initiated login request is always a higher level of the temporary account.
  • the server allocates resources for the upper account of the temporary account according to a predetermined rule. In this way, the rights of the users corresponding to the system account included in the login request initiated by the first time can be always guaranteed, which further facilitates the promotion of the products and the widening of the sales channels of the products.
  • step S940 a purchase request sent by the user terminal is received and stored, and the purchase request includes a system 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; and when the temporary account is not stored On the server, information for prompting the access failure is sent to the user terminal.
  • the server When the temporary account in the access request received by the server is not stored on the server, it indicates that the temporary account has not purchased the product on the system, or the temporary account does not pass the scanning system user's system QR code.
  • the server initiates a login request, so the server sends information to the user terminal for prompting access failure. In this way, 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 S950 it is determined whether the temporary account is further included in the purchase request; when the purchase request further includes the temporary account, step S960 to step S9100 are performed; otherwise, step S9110 is performed.
  • step S960 it is determined whether the temporary account is stored in the server; when the temporary account is not stored in the server, Step S970 is performed, otherwise, step S980 is performed.
  • step S970 a system account is generated for the temporary account, and the system account generated by the temporary account, the temporary account, and the system account in the purchase request are matched and stored, and the system account in the purchase request is a layer of the system account generated by the temporary account.
  • Upper account is generated for the temporary account, and the system account generated by the temporary account, the temporary account, and the system account in the purchase request are matched and stored, and the system account in the purchase request is a layer of the system account generated by the temporary account.
  • step S980 a system account is generated for the temporary account, and the temporary account stored in the server, the upper account of the temporary account stored in the server, and the system account generated by the temporary account are matched and stored.
  • step S990 a system two-dimensional code or the like is generated for the temporary account, and the system account is matched with the system account and the two-dimensional code generated by the temporary account, and the system two-dimensional code includes graphic information.
  • the system 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 system two-dimensional code is the avatar information of the user, so that the server can quickly identify the identity information.
  • step S9100 a system account is generated for the temporary account, and resources are allocated for the account having the first predetermined relationship with the generated system account according to the first predetermined rule.
  • step S9110 is performed.
  • step S9110 the resource is allocated to the account having the second predetermined relationship with the system account in the purchase request according to the second predetermined rule.
  • step S940, step S950, step S9100 and step S9110 are similar to steps S810 to S840 in the embodiment shown in FIG. 8, respectively, and are not described in this embodiment.
  • the data processing method provided by the embodiment of the present application by determining whether the purchase request further includes a temporary account, uses different subscription rules to allocate resources, and the allocation manner is bound to the identity of the user, so that the application is
  • the resource allocation mechanism can be more conducive to the promotion of goods and expand sales channels.
  • the user experience is further improved by further binding the upper-level account and the standard of the user entering the system, which can further facilitate the promotion of the product and broaden the sales channel.
  • FIG. 10 is a flowchart of another data processing and processing method provided by an embodiment of the present application. Referring to FIG. 10, the method described in this embodiment is performed by a server, and the method includes steps S1010 to S1090.
  • step S1010 a purchase request sent by the user terminal is received and stored, and the purchase request includes a system account.
  • step S1020 it is determined whether a temporary account is further included in the purchase request.
  • step S1030 when the purchase request further includes a temporary account, a system account is generated for the temporary account, and resources are allocated for the account having the first predetermined relationship with the generated system account according to the first predetermined rule.
  • step S1040 when the temporary account is not included in the purchase request, the resource is allocated according to the second predetermined rule for the account having the second predetermined relationship with the system account in the purchase request.
  • the steps S1010 to S1040 are similar to the steps S810 to S840 in the embodiment shown in FIG. 8, and are not described in this embodiment.
  • step S1050 a return request sent by the user through the user terminal is received and stored, and the return request includes a system account number.
  • step S1060 a confirmation request corresponding to the return request is received and agreed.
  • the server When the server receives and agrees to the confirmation request corresponding to the return request, the corresponding return information is stored in the order database of the server.
  • step S1070 according to the system account, it is determined whether the order corresponding to the return request is the first order corresponding to the system account.
  • the server can look up the order corresponding to the account in the order database according to the system account included in the return request. If there is no order corresponding to the account in the order database, it can be determined that the order corresponding to the return request is the first order corresponding to the account; if there is already an order corresponding to the system account in the order database, the return can be determined. The request for the corresponding order is not the first order corresponding to the system account.
  • step S1080 if the order corresponding to the return request is the first order of the system account, the system account stored in the server and the matching system QR code are deleted, and the lower account of the system account is set as a layer of the system account. The subordinate account of the superior account, and refund the amount of the order corresponding to the return request to the user corresponding to the system account.
  • step S1090 if the order corresponding to the return request is not the first order of the system account, the amount of the order corresponding to the return request is transferred to the system account.
  • the data processing method may further include: receiving and storing an exit request sent by the user through the user terminal, where the exit request includes a system account; sending a confirmation request to the user terminal; the user terminal is used to confirm the exit request, and the server deletes the system account and Match the system QR code.
  • 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. The other is that after the user sends the purchase request through the user terminal for the first time, the server sends a return request to the server. Will take the initiative to give a refund and disconnect the system account and other account matching relationship, can avoid the lawless elements to take profits, and can protect the legitimate rights and interests of users to a greater extent.
  • the data processing method provided by the embodiment of the present application 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 resources of the application.
  • the distribution mechanism can be more conducive to the promotion of goods and expand sales channels. Further, by setting the mode of exiting the system, the server can actively exit when the user uses the device, or the user who the server considers to be unqualified will actively let it quit, further improving the user experience of using the system, and further facilitating the promotion of the product. And broaden sales channels.
  • the above data processing method can be applied to a distribution system.
  • the upper account can be a superior distribution account
  • the lower account can be a lower distribution account.
  • FIG. 11 shows a data processing apparatus provided by an embodiment of the present application.
  • the device includes: a first receiving module 1111, a first determining module 1112, a first resource transfer module 1113, and a second resource transfer module 1114.
  • the first receiving module 1111 is configured to receive and store a purchase request sent by the user terminal, where the purchase request includes a system account.
  • the first determining module 1112 is configured to determine whether a temporary account is further included in the purchase request.
  • the first resource transfer module 1113 is configured to: when the purchase request further includes a temporary account, generate a system account for the temporary account, and allocate resources for the account having the first predetermined relationship with the generated system account according to the first predetermined rule.
  • the second resource transfer module 1114 is configured to allocate a resource to an account having a second predetermined relationship with a system account in the purchase request according to the second predetermined rule when the purchase request does not include the temporary account.
  • Each of the above modules may be implemented by software code.
  • each of the above modules may be stored in the memory 220 of the server 200.
  • the above modules can also be implemented by hardware such as an integrated circuit chip.
  • each block of the flowchart or block diagram can represent a module, a program segment, or a portion of code that includes one or more of the Executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may also occur in a different order than those illustrated in the drawings.
  • each block of the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts can be implemented in a dedicated hardware-based system that performs the specified function or function. Or it can be implemented by a combination of dedicated hardware and computer instructions.
  • each functional module in each embodiment of the present application may be integrated to form a separate part, or each module may exist separately, or two or more modules may be integrated to form a separate part.
  • the functions, if implemented in the form of software functional modules and sold or used as separate products, may be stored in a computer readable storage medium.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. . It should be noted that in the present application, relational terms such as first and second, etc. are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities or operations. There is any such actual relationship or order between them.
  • the term “comprises” or “comprises” or “comprises” or any other variations thereof is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device that comprises a plurality of elements includes not only those elements but also Other elements, or elements that are inherent to such a process, method, item, or device.
  • An element that is defined by the phrase “comprising a " does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

Landscapes

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

Abstract

一种数据处理方法及装置，该方法包括：接受用户的加入请求，所述加入请求包括所述用户的临时帐号以及推荐人的系统帐号（S310）；根据所述用户的临时帐号，获取所述用户所在区域（S320）；判断所述用户所在区域与所述推荐人所在区域是否相同（S330）；如果相同，按照预设规则为所述用户生成系统帐号，并存储所述用户的系统帐号（S340）；如果不同，提示所述用户加入系统失败（S350）。

Description

数据处理方法及装置
本申请要求于2016年4月18日提交中国专利局、申请号为201610240012.0、发明名称为“购买请求方法及装置”的中国专利申请，以及2016年8月25日提交中国专利局、申请号201610729813.3、发明名称为“数据处理方法及装置”的中国专利申请为优先权，其全部内容通过引用结合在本申请中。
技术领域
本本申请涉及计算机数据处理技术领域，具体涉及一种数据处理方法及装置。
背景技术
现有技术中，用户通常可以直接通过访问系统的页面加入系统或从系统上购物。但现有的访问方式和购物方式在设置上不利于对用户的管理以及商品的推广。
发明内容
本申请实施例提供一种数据处理方法及装置。
本申请实施例所提供的一种数据处理方法，包括：
接收用户的加入请求，所述加入请求包括所述用户的临时账号以及推荐人的系统账号；
根据所述用户的临时账号，获取所述用户所在区域；
判断所述用户所在区域与所述推荐人所在区域是否相同；
如果相同，按照预设规则为所述用户生成系统账号，并存储所述用户的系统账号；
如果不同，提示所述用户加入系统失败。
本申请实施例提供的另一种数据处理方法，包括：
接收并存储用户的购买请求，所述购买请求中包括系统账号；
判断所述购买请求中是否还包括临时账号；
当所述购买请求中还包括临时账号，为所述临时账号生成系统账号，按照第一预定规则为与所述生成的系统账号具有第一预定关系的账号分配资源；
当所述购买请求中不包括临时账号，按照第二预定规则为与所述购买请求中的所述系统账号具有第二预定关系的账号分配资源。
本申请实施例提供的一种数据处理装置，包括：处理器和存储有计算机可执行指令的存储介质，当所述处理器运行所述计算机可执行指令时，所述处理器执行：
接收用户的加入请求，所述加入请求包括所述用户的临时账号以及推荐人的系统账号；
根据所述用户的临时账号，获取所述用户所在区域；
判断所述用户所在区域与所述推荐人所在区域是否相同；
如果相同，按照预设规则为所述用户生成系统账号，并存储所述用户的系统账号；
如果不同，提示所述用户加入系统失败。
本申请实施例提供的另一种数据处理装置，包括：处理器和存储有计算机可执行指令的存储介质，当所述处理器运行所述计算机可执行指令时，所述处理器执行：
接收并存储用户的购买请求，所述购买请求中包括系统账号；
判断所述购买请求中是否还包括临时账号；
当所述购买请求中还包括临时账号，为所述临时账号生成系统账号，按照第一预定规则为与所述生成的系统账号具有第一预定关系的账号分配资源；
当所述购买请求中不包括临时账号，按照第二预定规则为与所述购买请求中的所述系统账号具有第二预定关系的账号分配资源。
附图说明
图1是本申请实施例提供的一种服务器与用户终端交互的示意图；
图2是本申请实施例提供的服务器的方框示意图；
图3是本申请实施例提供的一种数据处理方法的流程图；
图4是本申请实施例提供的一种数据处理方法中预设规则的流程图；
图5是本申请实施例提供的一种数据处理方法中步骤S360的流程图；
图6是本申请实施例提供的一种数据处理方法中步骤S370的流程图；
图7是本申请实施例提供的一种数据处理装置的功能模块示意图；
图8是本申请实施例提供的另一种数据处理方法的流程图；
图9是本申请实施例提供的另一种数据处理方法的流程图；
图10是本申请实施例提供的另一种数据处理方法的流程图；以及
图11是本申请实施例提供的另一种数据处理装置的功能模块示意图。
具体实施方式
为了使本技术领域的人员更好地理解本发明方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分的实施例，而不是全部的实施例。以下对在附图中提供的本申请的实施例的详细描述并非旨在限制要求保护的本申请的范围，而是仅仅表示本申请的选定实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本申请保护的范围。
相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步定义和解释。另外，在本申请的描述中，术语“第一”、“第二”等仅用于区分描述，而不能理解为指示或暗示相对重要性或时间先后。
如图1所示，是本申请实施例提供的服务器200分别与用户终端100进行交互的示意图。服务器200通过网络300与一个或多个用户终端100进行数据通信，以进行数据通信 或交互。服务器200可以是分布式文件存储服务器、网络服务端、数据库服务端等。用户终端100可以是个人电脑(personal computer，PC)、平板电脑、智能手机等。
于本申请实施例中，用户终端100中安装有客户端，该客户端可以是浏览器也可以是第三方应用软件，与服务器200相对应，为用户提供本地服务，例如注册，登录，浏览页面等。
本实施例中的服务器200可以是单个的服务器，也可以是一个服务器集群，可以包括WEB服务器、搜索服务器、计算服务器等多个服务器。
如图2所示，是服务器200的方框示意图。服务器200可以包括数据处理装置210、存储器220、存储控制器230、处理器240。
存储器220、存储控制器230、处理器240各元件相互之间直接或间接地电性连接，以实现数据的传输或交互。例如，这些元件相互之间可通过一条或多条通讯总线或信号线实现电性连接。数据处理装置210可以包括至少一个可以软件或固件(firmware)的形式存储于存储器220中或固化在服务端200的操作系统(operating system，OS)中的软件功能模块。处理器240用于执行存储器220中存储的可执行模块，例如数据处理装置210包括的软件功能模块或计算机程序。
其中，存储器220可以是，但不限于，随机存取存储器(Random Access Memory，RAM)，只读存储器(Read Only Memory，ROM)，可编程只读存储器(Programmable Read-Only Memory，PROM)，可擦除只读存储器(Erasable Programmable Read-Only Memory，EPROM)，电可擦除只读存储器(Electric Erasable Programmable Read-Only Memory，EEPROM)等。其中，存储器220用于存储程序，处理器240在接收到执行指令后，执行该程序，前述本申请任一实施例揭示的流过程定义的服务端所执行的方法可以应用于处理器中，或者由处理器实现。
处理器240可能是一种集成电路芯片，具有信号的处理能力。上述的处理器可以是通 用处理器，包括中央处理器(Central Processing Unit，CPU)、网络处理器(Network Processor，NP)等；还可以是数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
可以理解，图2所示的结构仅为示意，服务器200还可包括比图2中所示更多或者更少的组件，或者具有与图2所示不同的配置。图2中所示的各组件可以采用硬件、软件或其组合实现。
图3示出了本申请实施例提供的数据处理方法的流程图，请参阅图3，本实施例所描述的方法由服务器执行，该方法包括步骤S310至步骤S350。
在步骤S310中，接收用户的加入请求，该加入请求包括该用户的临时账号以及推荐人的系统账号。
其中，临时账号可以根据用户唯一识别码以及系统唯一识别码计算获得。
其中，用户唯一识别码的实施方法有多种，可以是用户的社交网络账号，例如用户的微信号，微信二维码，用户注册的系统平台的用户ID等，可以理解的是，实施方式并不局限于所述提到的方式。
同样的，系统唯一识别码的实施方法有多种，可以是该系统的社交网络公众号，例如微信公众号，微信公众二维码，系统平台的公众ID等，可以理解的是，实施方式并不局限于所述提到的方式。
通过在用户唯一识别码以及系统唯一识别码之间进行计算得出该用户的临时账号，计算方式也可以有多种，可以相加，相乘，也可以通过加密计算，可以理解的是，实施方式并不局限于所述提到的方式。
系统账号，是指由服务器分配给用户的，是系统对用户的唯一认证号。
在步骤S320中，根据该用户的临时账号，获取该用户所在区域。
步骤S320的实施方式有多种，例如，若用户唯一识别码为用户的社交网络账号，例如微信号，则可以根据微信提供给第三方的应用接口，调用接口程序，获取到请求待加入用户所在区域。当然，并不局限于此。
在步骤S330中，判断该用户所在区域与推荐人所在区域是否相同。
其中，推荐人所在区域可以在推荐人通过区域验证进入时，服务器从推荐人的临时账号中获取，并储存于服务器中。在判断该用户所在区域与推荐人所在区域是否相同时，可以从服务器中获取推荐人所在区域，并与该用户所在区域进行匹配，匹配的方式可以有多种，例如，字符串匹配等。
判断用户与推荐人所在区域是否相同，可以根据用户与推荐人的地理位置所确定。其中，本申请中所涉及区域的大小可以根据实际情况确定，本申请实施例不做限制。例如可以认为同处于江苏省的用户和推荐人属于同一区域；也可以认为同处于中国的用户和推荐人属于同一区域；另外，还可认为分别处于中国与日本的用户和推荐人属于同一区域。
如果该用户所在区域与推荐人所在区域相同，则执行步骤S340，否则，执行步骤S350。
在步骤S340中，按照预设规则为该用户生成系统账号，并存储该用户的系统账号。
作为一种实施方式，请参阅图4，步骤S340可以包括步骤S341至步骤S347。
在步骤S341中，判断该用户的临时账号是否与系统唯一识别码关联。
如果该用户的临时账号与系统唯一识别码关联，则执行步骤S342，否则，执行步骤S343。
在步骤S342中，为该用户生成系统账号，并存储该用户的系统账号。
此时，该用户加入系统，成为系统用户。
在步骤S343中，向该用户的用户终端发送系统唯一识别码对应的信息。
若用户唯一识别码为用户社交网络账号，例如微信号，则此时服务器向该用户的用户终端返回系统唯一识别码，即微信公众号的关注界面。
在步骤S344中，接收用户指令。
在步骤S345中，判断用户指令是否为用于选择与系统唯一识别码相关联的选择指令。
如果用户指令用于选择与系统唯一识别码相关联，执行步骤S346，否则，执行步骤S347。
在步骤S346中，为该用户生成系统账号，并存储该用户的系统账号。
当用户唯一识别码为用户微信号时，用户通过用户终端对系统微信公众号进行关注，即此时所述用户指令是用于选择与系统唯一识别码相关联的选择指令，该用户加入系统，成为系统用户。
在步骤S347中，向该用户的用户终端发送用于提示加入系统失败的提示信息。
当用户唯一识别码为用户微信号时，用户通过用户终端选择不关注系统微信公众号，用户则不能加入系统，该用户的用户终端接收用于提示加入系统失败的提示信息，例如“扫码失败，地区不匹配”等等提示信息。
可选的，请参阅图5，在步骤S340之后，该方法还可以包括步骤S360。
在步骤S360中，将该用户的临时账号对应的信息发送到推荐人的用户终端。
其中，该用户的临时账号对应的信息包括该用户的社交网络头像，社交网络账号或者地域信息等，以使推荐人通过用户终端接收到该信息时，能够了解到该用户通过关联推荐人的系统账号成功加入到系统中。例如，该用户可以通过扫描推荐人的微信二维码等方式关联推荐人的系统账号。在后续的资源分配中，该用户为所述推荐人的下级用户，有利于合理的资源分配。
在步骤S350中，向该用户的用户终端发送用于提示加入系统失败的提示信息。
可选的，请参阅图6，在步骤S350之后，该方法还可以包括步骤S370。
在步骤S370中，向该用户的用户终端发送用于提示如何加入系统的提示信息。
例如，可以向该用户的用户终端发送“请扫描XX市推荐人的二维码”或“在我的微信-点击头像-地区进行地区修改”等等，以使该用户接收到该提示信息后，能够知道如何加入系统，进一步提升了系统用户按照区域加入的比例。
本申请实施例提供的数据处理方法，通过判断用户所在区域与推荐人所在区域是否相同，来确定是否允许该用户加入系统，即对用户在加入系统时进行分区域管理，只有跟推荐人在一个区域的用户才能加入系统，这种方式，能够实现系统用户按照区域进行管理，并为后续系统用户按照区域进行资源分配提供了准备。
请参阅图7，是本申请实施例提供的图2所示的数据处理装置210的功能模块示意图。数据处理装置210运行于服务器200。数据处理装置210包括接收模块211，获取模块212，处理模块213。
接收模块211，用于接收用户的加入请求，该加入请求包括该用户的临时账号以及推荐人的系统账号。
获取模块212，用于根据该用户的临时账号，获取该用户所在区域。
处理模块213，用于判断该用户所在区域与推荐人所在区域是否相同；如果相同，则按照预设规则为该用户生成系统账号，并存储该用户的系统账号；如果不同，则向该用户的用户终端发送用于提示加入系统失败的提示信息。
其中，处理模块213判断该用户的临时账号是否与系统唯一识别码关联。如果是，处理模块213为请求加入用户生成系统账号，并存储该用户的系统账号。如果否，处理模块213向该用户发送系统唯一识别码对应的信息；接收用户指令；若用户指令为用于选择与系统唯一识别码相关联的选择指令，则为该用户生成系统账号，并存储该用户的系统账号。
可选的，若用户指令为用于选择不与系统唯一识别码相关联的选择指令，处理模块213还可以向该用户的用户终端发送用于提示加入系统失败的提示信息。
作为一种实施方式，数据处理装置还可以包括第一发送模块214，用于将该用户的临时账号对应的信息发送到推荐人的用户终端。
作为另一种实施方式，数据处理装置还包括第二发送模块215，用于向该用户的用户终端发送用于提示如何加入系统的提示信息。
以上各模块可以是由软件代码实现，此时，上述的各模块可存储于服务器200的存储器220内。以上各模块同样可以由硬件例如集成电路芯片实现。
图8示出了本申请实施例提供的另一种数据处理方法的流程图，该方法可以应用于图1和图2所示出的环境中。
在本实施例中，用户终端100所安装的客户端还可以根据用户的操作来选择要购买的商品。该客户端还可以包括厂商客户端，线下的厂商可以通过厂商客户端输入商品信息，例如商品说明信息和商品图像等。线下的厂商还可以通过厂商客户端输入预先制定的购买请求处理的具体规则。
在本实施例中，服务器200中可以包括多个数据库，例如会员数据库、商品数据库和订单数据库等。其中，会员数据库可以储存用户的注册信息等，商品数据库可以储存商品信息以及与商品相关的线下的厂商的信息等，订单数据库可以储存订单信息，与订单信息对应的用户的信息、商品信息以及相关的物流信息等。
商品数据库中的商品信息可以由线下厂商通过厂商客户端输入，并由服务器200存储在商品数据库中。商品信息中可以包括商品图像以及商品说明等。
图1至图2所示只是本申请实施例的一种应用环境的举例，本申请的具体实施方式并不以此为限。
请参阅图8，本实施例所描述的方法由服务器执行，该方法包括步骤S810至步骤S840。
在步骤S810中，接收并存储用户终端发送的购买请求，该购买请求中包括系统账号。
系统账号由服务器分配给用户的，是系统对用户的唯一认证号。可以理解的是，具有 系统账号的用户是系统用户，例如，可以是在系统上购买过产品的用户，而临时用户只具有临时账号，而不具备系统账号。
其中，接收并存储用户终端发送的购买请求可能有两种情况，一种是：服务器接收到系统用户通过用户终端发送的购买请求，因此该购买请求中包括的系统账号为该系统用户在系统中的系统账号；另一种情况是，服务器接收到临时用户通过用户终端发送的购买请求，因此该购买请求中包括的系统账号为推荐人的系统账号。因此服务器可以通过判断购买请求中是否还包括临时账号可以判断出该购买请求是由临时用户发起还是由系统用户发起的。
在步骤S820中，判断购买请求中是否还包括临时账号。
其中，临时账号可以根据用户唯一识别码以及系统唯一识别码计算获得。
其中，所述用户唯一识别码的实施方法有多种，可以是用户的社交网络账号，例如用户的微信号，微信二维码，用户注册的系统平台的用户ID等，可以理解的是，实施方式并不局限于所述提到的方式。
同样的，系统唯一识别码的实施方法有多种，可以是该系统的社交网络公众号，例如微信公众号，微信公众二维码，系统平台的公众ID等，可以理解的是，实施方式并不局限于所述提到的方式。
通过在用户唯一识别码以及系统唯一识别码之间进行计算得出临时账号，计算的方式也可以有多种，可以相加，相乘，也可以通过加密计算，可以理解的是，实施方式并不局限于所述提到的方式。
在步骤S830中，当购买请求中还包括临时账号，为临时账号生成系统账号，按照第一预定规则为与所生成的系统账号具有第一预定关系的账号分配资源。
其中，这里的资源可以是货币金额，也可以是虚拟货币或者积分等资源。
第一预定规则以及第一预定关系均可以为事先设置的规则或关系。例如，与该所生成 的系统账号具有第一预定关系的账号可以包括该系统账号的N层上级账号，其中N为自然数，N的取值可以根据实际情况确定，本申请实施例不做限制。例如，当N等于3时，与该所生成的系统账号具有第一预定关系的账号可以包括该系统账号的一层上级账号，该系统账号的二层上级账号，以及该系统账号的三层上级账号。
当N等于3时，按照第一预定规则为与该所生成的系统账号具有第一预定关系的账号分配资源可以包括：将第一数量的资源转移至该系统账号的一层上级账号；将第二数量的资源转移至该系统账号的二层上级账号；将第三数量的资源转移至该系统账号的三层上级账号等。其中，第一数量、第二数量和第三数量之间比值可以根据实际情况确定，本申请实施例不做限制。例如，第三数量可以大于第二数量，第二数量可以大于第一数量，以此类推。可选的，第一数量、第二数量以及第三数量的比值可以为1:2:3等。
在步骤S840中，当购买请求中不包括临时账号，按照第二预定规则为与购买请求中的系统账号具有第二预定关系的账号分配资源。
其中，第二预定规则以及第二预定关系也可以为事先设置的规则或关系。例如，与购买请求中的系统账号具有第二预定关系的账号可以包括该账号本身以及该系统账号的N层上级账号，其中N为自然数，N的取值可以根据实际情况确定，本申请实施例不做限制。例如，当N等于2时，与购买请求中的系统账号具有第二预定关系的账号可以包括该系统账号本身、该系统账号的一层上级账号，该系统账号的二层上级账号。
当N等于2时，按照第二预定规则为与购买请求中的系统账号具有第二预定关系的账号分配资源可以包括：将第四数量的资源转移至该购买请求中系统账号；将第五数量的资源转移至该购买请求中的系统账号的一层上级账号；将第六数量的资源转移至该购买请求中的系统账号的二层上级账号。其中，第四数量、第五数量和第六数量之间比值可以根据实际情况确定，本申请实施例不做限制。例如，第四数量可以大于第五数量，第五数量可以大于第六数量，以此类推。可选的，第四数量、第五数量以及第六数量的比值可以为3:2:1 等。
当服务器接收到购买请求后，根据购买请求向线下厂商的客户端发送订单信息。线下厂商根据该订单信息可以安排发货，并将与发货相关的物流信息通过所述厂商客户端传递至服务器，服务器可以将所述物流信息储存进订单数据库。
当服务器收到购买请求或者当购买请求完成后，服务器可以向购买请求中包含的系统账号对应的用户终端发送用于提示的消息，提示购买请求完成等信息，例如服务器可以向用户终端发送内容为“购买成功”的信息。其中提示消息发送的时间以及发送的内容可以有多种实施方式，并不局限于所述方式。
本申请实施例提供的数据处理方法，通过判断购买请求中是否还包括临时账号，来采用不同的预订规则对资源进行分配，这种分配方式与使用者的身份进行绑定，使得本申请的资源分配机制能够更利于商品的推广，拓宽销售渠道。
图9示出了本申请实施例提供的另一种数据处理方法的流程图，请参阅图9，本实施例描述方法由服务器执行，该方法包括步骤S910至步骤S9110。
在步骤S910中，接收用户终端发送的登录请求，该登录请求中包括临时账号及系统账号。
其中，登录请求可以是临时用户通过用户终端登录自己的社交网络账号，并关注系统的社交网络公众号。例如临时用户登录自己的微信号，并关注系统的微信公众号后，获得临时用户的临时账号，通过用户终端扫描系统用户的系统账号对应的系统二维码后，向服务器发起的。其中，登录请求发起的实施方式可以有多种，并不局限于此。
在步骤S920中，判断临时账号是否存储在服务器中。
在步骤S930中，当临时账号没有存储在服务器，将该临时账号与系统账号匹配并存储起来，该系统账号为该临时账号的一层上级账号。
如果服务器判断该临时账号已经存储在服务器中，并不会将登录请求中包括的临时账号以及系统账号匹配并存储起来，也就是说，服务器只会将临时账号与第一次发起的登录请求中包括的系统账号进行匹配并存储，当服务器再次接收到用户终端发送的登录请求时，当登录请求中包括系统账号与第一次发起的登录请求中包括的系统账号不相同时，服务器并不会将这次登录请求中包括的系统账号与这次登录请求中的临时账号进行匹配并存储。
通过这种方式，服务器将临时账号与第一次发起的登录请求中包括的系统账号进行匹配并存储，并保证第一次发起的登录请求中包括的系统账号始终为该临时账号的一层上级账号，当用户终端发起的购买请求完成后，服务器会按照预定规则为该临时账号的上级账号分配资源。这样能够始终保障第一次发起的登录请求中包括的系统账号对应的用户的权益，进一步有利于商品的推广，以及商品销售渠道的扩宽。
在步骤S940中，接收并存储用户终端发送的购买请求，购买请求中包括系统账号。
在服务器接收并存储用户终端发送的购买请求之前，该方法还可以包括：接收用户终端发送的访问请求，访问请求中包括临时账号；判断该临时账号是否存储在服务器中；当该临时账号没有存储在服务器上，向该用户终端发送用于提示访问失败的信息。
当服务器接收到的访问请求中的临时账号没有存储在服务器上时，表示该临时账号并没有在该系统上购买过产品，或者该临时账号并没有通过扫描系统用户的系统二维码的方式向服务器发起过登录请求，因此服务器向用户终端发送用于提示访问失败的信息。服务器通过这种方式对进入系统的用户进行筛选，将不合乎标准的用户拒之门外，使得能够进入系统的用户能够得到更优质的服务，用户体验进一步提升。
在步骤S950中，判断购买请求中是否还包括临时账号；当购买请求中还包括临时账号时，执行步骤S960至步骤S9100，否则，执行步骤S9110。
在步骤S960中，判断临时账号是否存储在服务器中；当临时账号没有存储在服务器中， 执行步骤S970，否则，执行步骤S980。
在步骤S970中，为临时账号生成系统账号，将临时账号、临时账号生成的系统账号及购买请求中的系统账号匹配并存储起来，购买请求中的系统账号为临时账号生成的系统账号的一层上级账号。
在步骤S980中，为临时账号生成系统账号，将服务器中存储的临时账号，及服务器中存储的临时账号的上级账号，以及临时账号生成的系统账号匹配并存储起来。
在步骤S990中，为临时账号生成系统二维码等，并将系统账号与所述临时账号生成的系统账号及二维码匹配起来，所述系统二维码包括图形信息。
其中，所述系统二维码还可以包括了用户的头像、用户名、临时账号、用户的收货地址、用户的联系方式等信息。可选的，系统二维码中包括的图形信息为用户的头像信息，以便于服务器迅速识别身份信息。
在步骤S9100中，为临时账号生成系统账号，按照第一预定规则为与生成的系统账号具有第一预定关系的账号分配资源。
当购买请求中不包括临时账号，执行步骤S9110。
在步骤S9110中，按照第二预定规则为与购买请求中的系统账号具有第二预定关系的账号分配资源。
可以理解的是，步骤S940，步骤S950，步骤S9100以及步骤S9110分别与图8所示实施例中的步骤S810至步骤S840相类似，此实施例中就不再累述。
本申请实施例提供的数据处理方法，通过判断所述购买请求中是否还包括临时账号，来采用不同的预订规则对资源进行分配，这种分配方式与使用者的身份进行绑定，使得本申请的资源分配机制能够更利于商品的推广，拓宽销售渠道。并且，进一步的通过始终绑定上级账号的方式以及制定用户进入系统的标准，使得用户体验进一步提升，能够进一步有利于商品的推广，以及拓宽销售渠道。
图10示出了本申请实施例提供的另一种数据处理处理方法的流程图，请参阅图10，本实施例描述的方法由是服务器执行，该方法包括步骤S1010至步骤S1090。
在步骤S1010中，接收并存储用户终端发送的购买请求，购买请求中包括系统账号。
在步骤S1020中，判断购买请求中是否还包括临时账号。
在步骤S1030中，当购买请求中还包括临时账号，为临时账号生成系统账号，按照第一预定规则为与生成的系统账号具有第一预定关系的账号分配资源。
在步骤S1040中，当购买请求中不包括临时账号，按照第二预定规则为与购买请求中的系统账号具有第二预定关系匹配的账号分配资源。
其中，步骤S1010至步骤S1040与图8所示实施例中的步骤S810至步骤S840相类似，此实施例中就不再累述。
在步骤S1050中，接收并存储用户通过用户终端发送的退货请求，退货请求中包括系统账号。
在步骤S1060中，接收并同意该退货请求相对应的确认请求。
当服务器接收并同意该退货请求相对应的确认请求后，对应的退货信息会存储进所述服务器的订单数据库。
在步骤S1070中，根据系统账号，判断退货请求对应的订单是否为该系统账号对应的首次订单。
服务器可以根据与退货请求中包括的系统账号在订单数据库中查找与账号对应的订单。若在订单数据库中，没有与该账号对应的订单，则可以判定退货请求对应的订单为该账号对应的首次订单；若在订单数据库中，已经有与该系统账号对应的订单，则可以判定退货请求对应的订单并不是该系统账号对应的首次订单。
在步骤S1080中，如果退货请求对应的订单是该系统账号的首次订单，删除服务器中存储的系统账号及匹配的系统二维码，将该系统账号的下级账号设置为该系统账号的一层 上级账号的下级账号，并将退货请求对应的订单的金额退还至该系统账号所对应的用户。
在步骤S1090中，如果退货请求对应的订单不是该系统账号的首次订单，将该退货请求对应的订单的金额转移至该系统账号。
该数据处理方法还可以包括：接收并存储用户通过用户终端发送的退出请求，退出请求中包括系统账号；向用户终端发送确认请求；所述用户终端用于确认退出的请求，服务器删除系统账号及匹配的系统二维码。
服务器可以设置两种退出系统的方式，一种是用户可以主动通过用户终端向服务器发送退出请求；另一种是，用户首次通过用户终端发送购买请求后，又向服务器发送退货请求，此时服务器会主动给予退款并断开该系统账号与其他账号的匹配关系，可以避免不法分子套取利润的行为，又可以较大限度地保护用户的合法权益。
本申请实施例提供的数据处理方法，通过判断购买请求中是否还包括临时账号，来采用不同的预订规则对资源进行分配，这种分配方式与使用者的身份进行绑定，使得本申请的资源分配机制能够更利于商品的推广，拓宽销售渠道。进一步的，服务器通过设置退出系统的方式，使得用户在使用时可以主动退出，或者服务器认为不合格的用户会主动让它退出，进一步提高了使用该系统的用户体验，能够进一步有利于商品的推广，以及拓宽销售渠道。
上述的数据处理方法可以运用于分销系统中。其中，上级账号可以为上级分销账号，下级账号可以为下级分销账号。
图11示出了本申请实施例提供的数据处理装置。该装置包括：第一接收模块1111，第一判断模块1112，第一资源转移模块1113，第二资源转移模块1114。
第一接收模块1111，用于接收并存储用户终端发送的购买请求，该购买请求中包括系统账号。
第一判断模块1112，用于判断购买请求中是否还包括临时账号。
第一资源转移模块1113，用于当购买请求中还包括临时账号，为临时账号生成系统账号，按照第一预定规则为与生成的系统账号具有第一预定关系的账号分配资源。
第二资源转移模块1114，用于当购买请求中不包括临时账号，按照第二预定规则为与购买请求中的系统账号具有第二预定关系的账号分配资源。
以上各模块可以是由软件代码实现，此时，上述的各模块可存储于服务器200的存储器220内。以上各模块同样可以由硬件例如集成电路芯片实现。
需要说明的是，本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。
本申请实施例所提供的数据处理装置，其实现原理及产生的技术效果和前述方法实施例相同，为简要描述，装置实施例部分未提及之处，可参考前述方法实施例中相应内容。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，也可以通过其它的方式实现。以上所描述的装置实施例仅仅是示意性的，例如，附图中的流程图和框图显示了根据本申请的多个实施例的装置、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段或代码的一部分，所述模块、程序段或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现方式中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个连续的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或动作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
另外，在本申请各个实施例中的各功能模块可以集成在一起形成一个独立的部分，也可以是各个模块单独存在，也可以两个或两个以上模块集成形成一个独立的部分。
所述功能如果以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务端，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。需要说明的是，在本申请中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上所述仅为本申请的优选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步定义和解释。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (29)

  1. 一种数据处理方法，包括：
    接收用户的加入请求，所述加入请求包括所述用户的临时账号以及推荐人的系统账号；
    根据所述用户的临时账号，获取所述用户所在区域；
    判断所述用户所在区域与所述推荐人所在区域是否相同；
    如果相同，按照预设规则为所述用户生成系统账号，并存储所述用户的系统账号；
    如果不同，提示所述用户加入系统失败。
  2. 根据权利要求1所述的方法，所述按照预设规则为所述用户生成系统账号，并存储所述用户的系统账号，包括：
    判断所述用户的临时账号是否与系统唯一识别码关联；
    如果是，则为所述用户生成系统账号，并存储所述用户的系统账号；
    如果否，则向所述用户的用户终端发送系统唯一识别码对应的信息；接收用户指令；若所述用户指令为用于选择与所述系统唯一识别码相关联的选择指令，则为所述用户生成系统账号，并存储所述用户的系统账号。
  3. 根据权利要求2所述的方法，还包括：
    若所述用户指令为用于选择不与所述系统唯一识别码相关联的选择指令，则提示所述用户加入系统失败。
  4. 根据权利要求1或2所述的方法，在存储所述用户的系统账号之后，还包括：
    提示所述推荐人所述用户加入系统成功。
  5. 根据权利要求1或3所述的方法，在提示所述用户加入系统失败之后，还包括：
    提示所述用户如何加入系统。
  6. 根据权利要求1或2所述的方法，还包括：
    接收所述用户发送的购买请求；
    根据所述购买请求判断所述用户是否是首次购买用户；
    当所述用户是首次购买用户时，按照第一预定规则为所述用户的N层上级账号分配资源；
    当所述用户是非首次购买用户时，按照第二预定规则为所述用户以及所述用户的N层上级账号分配资源；
    其中N为自然数，所述用户的推荐人的账号为所述用户的一层上级账号，以此类推。
  7. 根据权利要求6所述的方法，所述按照第一预定规则为所述用户的N层上级账号分配资源，包括：
    所述用户的一层上级账号所分配资源小于所述用户的二层上级账号所分配资源，以此类推。
  8. 根据权利要求6所述的方法，所述按照第二预定规则所述用户以及所述用户的N层上级账号分配资源，包括：
    所述用户所分配资源大于所述用户的一层上级账号所分配资源，所述用户的一层上级账号所分配资源大于所述用户的二层上级账号所分配资源，以此类推。
  9. 一种数据处理方法，包括：
    接收并存储用户的购买请求，所述购买请求中包括系统账号；
    判断所述购买请求中是否还包括临时账号；
    当所述购买请求中还包括临时账号，为所述临时账号生成系统账号，按照第一预定规则为与所述生成的系统账号具有第一预定关系的账号分配资源；
    当所述购买请求中不包括临时账号，按照第二预定规则为与所述购买请求中的所述系统账号具有第二预定关系的账号分配资源。
  10. 根据权利要求9所述的方法，所述为临时账号生成系统账号，包括：
    判断所述临时账号是否存储在服务器中；
    当所述临时账号没有存储在服务器中，为所述临时账号生成系统账号，将所述临时账号、所述临时账号生成的系统账号及所述购买请求中的系统账号匹配并存储，所述购买请求中的系统账号为所述临时账号生成的系统账号的一层上级账号；
    当所述临时账号已经存储在服务器中，为所述临时账号生成系统账号，将所述服务器中存储的临时账号，及服务器中存储的所述临时账号的上级账号，以及所述临时账号生成的系统账号匹配并存储。
  11. 根据权利要求9所述的方法，所述接收并存储用户发送的购买请求之前，还包括：
    接收所述用户发送的登录请求，所述登录请求中包括临时账号及系统账号；
    判断所述临时账号是否存储在服务器中；
    当所述临时账号没有存储在服务器，将所述临时账号与所述系统账号匹配并存储，所述系统账号为所述临时账号的一层上级账号。
  12. 根据权利要求9所述的方法，所述临时账号根据用户唯一识别码以及系统唯一识别码计算获得。
  13. 根据权利要求9所述的方法，所述接收并存储所述用户发送的购买请求之前，还包括：
    接收所述用户发送的访问请求，所述访问请求中包括临时账号；
    判断所述临时账号是否存储在服务器中；
    当所述临时账号没有存储在服务器上，提示所述用户访问失败。
  14. 根据权利要求9所述的方法，还包括：当所述购买请求中包括临时账号，为所述临时账号生成系统二维码，并将所述系统与所述临时账号生成的系统账号及二维码匹配，所述系统二维码包括图形信息。
  15. 根据权利要求13所述方法，还包括：
    接收并存储所述用户发送的退货请求，所述退货请求中包括所述用户的系统账号；
    根据所述系统账号，判断所述退货请求对应的订单是否为所述用户的系统账号对应的首次订单；
    如果是，删除服务器中存储的所述用户的系统账号，将所述用户的系统账号的下级账号设置为所述用户的系统账号的一层上级账号的下级账号。
  16. 根据权利要求9所述方法，所述按照第一预定规则为与所述生成的系统账号具有第一预定关系的账号分配资源，包括：
    为所述生成的系统账号的N层上级账号分配资源，N为自然数；
    其中，所述生成的系统账号的一层上级账号所分配资源小于所述生成的账号的二层上级账号所分配资源，以此类推。
  17. 根据权利要求9所述方法，所述按照第二预定规则为与所述购买请求中的所述系统账号具有第二预定关系的账号分配资源，包括：
    为所述购买请求中的系统账号以及所述购买请求中的系统账号的N层上级账号分配资源，N为自然数；
    其中，所述购买请求中的系统账号所分配资源大于所述购买请求中的系统账号的一层上级账号所分配资源，所述购买请求中的系统账号的一层上级账号所分配资源大于所述购买请求中的系统账号的二层上级账号所分配资源，以此类推。
  18. 一种数据处理装置，包括：处理器和存储有计算机可执行指令的存储介质，当所述处理器运行所述计算机可执行指令时，所述处理器执行：
    接收用户的加入请求，所述加入请求包括所述用户的临时账号以及推荐人的系统账号；
    根据所述用户的临时账号，获取所述用户所在区域；
    判断所述用户所在区域与所述推荐人所在区域是否相同；
    如果相同，按照预设规则为所述用户生成系统账号，并存储所述用户的系统账号；
    如果不同，提示所述用户加入系统失败。
  19. 根据权利要求18所述的装置，当按照预设规则为所述用户生成系统账号，并存储所述用户的系统账号时，所述处理器执行：
    判断所述用户的临时账号是否与系统唯一识别码关联；
    如果是，则为所述用户生成系统账号，并存储所述用户的系统账号；
    如果否，则向所述用户的用户终端发送系统唯一识别码对应的信息；接收用户指令；若所述用户指令为用于选择与所述系统唯一识别码相关联的选择指令，则为所述用户生成 系统账号，并存储所述用户的系统账号。
  20. 根据权利要求18或19所述的装置，所述处理器还执行：
    接收所述用户发送的购买请求；
    根据所述购买请求判断所述用户是否是首次购买用户；
    当所述用户是首次购买用户时，按照第一预定规则为所述用户的N层上级账号分配资源；
    当所述用户是非首次购买用户时，按照第二预定规则为所述用户以及所述用户的N层上级账号分配资源；
    其中N为自然数，所述用户的推荐人的账号为所述用户的一层上级账号，以此类推。
  21. 根据权利要求20所述的装置，所述按照第一预定规则为所述用户的N层上级账号分配资源，包括：
    所述用户的一层上级账号所分配资源小于所述用户的二层上级账号所分配资源，以此类推。
  22. 根据权利要求20所述的装置，所述按照第二预定规则所述用户以及所述用户的N层上级账号分配资源，包括：
    所述用户所分配资源大于所述用户的一层上级账号所分配资源，所述用户的一层上级账号所分配资源大于所述用户的二层上级账号所分配资源，以此类推。
  23. 一种数据处理装置，包括：处理器和存储有计算机可执行指令的存储介质，当所述处理器运行所述计算机可执行指令时，所述处理器执行：
    接收并存储用户的购买请求，所述购买请求中包括系统账号；
    判断所述购买请求中是否还包括临时账号；
    当所述购买请求中还包括临时账号，为所述临时账号生成系统账号，按照第一预定规则为与所述生成的系统账号具有第一预定关系的账号分配资源；
    当所述购买请求中不包括临时账号，按照第二预定规则为与所述购买请求中的所述系统账号具有第二预定关系的账号分配资源。
  24. 根据权利要求23所述的装置，当为临时账号生成系统账号时，所述处理器执行：
    判断所述临时账号是否存储在服务器中；
    当所述临时账号没有存储在服务器中，为所述临时账号生成系统账号，将所述临时账号、所述临时账号生成的系统账号及所述购买请求中的系统账号匹配并存储，所述购买请求中的系统账号为所述临时账号生成的系统账号的一层上级账号；
    当所述临时账号已经存储在服务器中，为所述临时账号生成系统账号，将所述服务器中存储的临时账号，及服务器中存储的所述临时账号的上级账号，以及所述临时账号生成的系统账号匹配并存储。
  25. 根据权利要求23所述的装置，所述处理器还执行：
    接收所述用户发送的登录请求，所述登录请求中包括临时账号及系统账号；
    判断所述临时账号是否存储在服务器中；
    当所述临时账号没有存储在服务器，将所述临时账号与所述系统账号匹配并存储，所述系统账号为所述临时账号的一层上级账号。
  26. 根据权利要求23所述的装置，所述处理器还执行：
    接收所述用户发送的访问请求，所述访问请求中包括临时账号；
    判断所述临时账号是否存储在服务器中；
    当所述临时账号没有存储在服务器上，提示所述用户访问失败。
  27. 根据权利要求26所述的装置，还包括：
    接收并存储所述用户发送的退货请求，所述退货请求中包括所述用户的系统账号；
    根据所述系统账号，判断所述退货请求对应的订单是否为所述用户的系统账号对应的首次订单；
    如果是，删除服务器中存储的所述用户的系统账号，将所述用户的系统账号的下级账号设置为所述用户的系统账号的一层上级账号的下级账号。
  28. 根据权利要求23所述的装置，当按照第一预定规则为与所述生成的系统账号具有第一预定关系的账号分配资源时，所述处理器执行：
    为所述生成的系统账号的N层上级账号分配资源，N为自然数；
    其中，所述生成的系统账号的一层上级账号所分配资源小于所述生成的账号的二层上级账号所分配资源，以此类推。
  29. 根据权利要求23所述的装置，当按照第二预定规则为与所述购买请求中的所述系统账号具有第二预定关系的账号分配资源时，所述处理器执行：
    为所述购买请求中的系统账号以及所述购买请求中的系统账号的N层上级账号分配资源，N为自然数；
    其中，所述购买请求中的系统账号所分配资源大于所述购买请求中的系统账号的一层上级账号所分配资源，所述购买请求中的系统账号的一层上级账号所分配资源大于所述购 买请求中的系统账号的二层上级账号所分配资源，以此类推。
PCT/CN2017/080864 2016-04-18 2017-04-18 数据处理方法及装置 WO2017181933A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2017202892A AU2017202892A1 (en) 2016-04-18 2017-04-18 Data processing method and apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201610240012.0A CN105956862A (zh) 2016-04-18 2016-04-18 购买请求处理方法及装置
CN201610240012.0 2016-04-18
CN201610729813.3A CN106330913A (zh) 2016-08-25 2016-08-25 数据处理方法及装置
CN201610729813.3 2016-08-25

Publications (1)

Publication Number Publication Date
WO2017181933A1 true WO2017181933A1 (zh) 2017-10-26

Family

ID=60116554

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/080864 WO2017181933A1 (zh) 2016-04-18 2017-04-18 数据处理方法及装置

Country Status (2)

Country Link
AU (1) AU2017202892A1 (zh)
WO (1) WO2017181933A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101794285A (zh) * 2009-11-06 2010-08-04 丁亮 一种产品防伪防窜货编码方法
CN102708507A (zh) * 2012-06-19 2012-10-03 重庆先迈通信技术有限公司 一种互联网络交易业务的返利推广方法
CN103325008A (zh) * 2013-05-22 2013-09-25 上海鸿润科技有限公司 基于计算机系统的信息交互方法及其系统
CN105469294A (zh) * 2015-11-17 2016-04-06 南京唐一微数字科技有限公司 购买请求处理方法及装置
CN105956862A (zh) * 2016-04-18 2016-09-21 南京唐微数字科技有限公司 购买请求处理方法及装置
CN106330913A (zh) * 2016-08-25 2017-01-11 南京唐微数字科技有限公司 数据处理方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101794285A (zh) * 2009-11-06 2010-08-04 丁亮 一种产品防伪防窜货编码方法
CN102708507A (zh) * 2012-06-19 2012-10-03 重庆先迈通信技术有限公司 一种互联网络交易业务的返利推广方法
CN103325008A (zh) * 2013-05-22 2013-09-25 上海鸿润科技有限公司 基于计算机系统的信息交互方法及其系统
CN105469294A (zh) * 2015-11-17 2016-04-06 南京唐一微数字科技有限公司 购买请求处理方法及装置
CN105956862A (zh) * 2016-04-18 2016-09-21 南京唐微数字科技有限公司 购买请求处理方法及装置
CN106330913A (zh) * 2016-08-25 2017-01-11 南京唐微数字科技有限公司 数据处理方法及装置

Also Published As

Publication number Publication date
AU2017202892A1 (en) 2017-11-02

Similar Documents

Publication Publication Date Title
US10970692B2 (en) Method, system and server system of payment based on a conversation group
WO2019085579A1 (zh) 一种信息推送方法和装置
US20210233120A1 (en) Authorization and termination of the binding of social account interactions to a master agnostic identity
US10861000B2 (en) Method, system, and apparatus for application loading
CN105530175B (zh) 一种消息处理方法、装置及系统
TWI706265B (zh) 第三方授權登錄方法及系統
JP6463463B2 (ja) サービス処理方法、装置、及びサーバ
US20220188786A1 (en) Systems and methods for user data management across multiple devices
US20180308138A1 (en) Data processing method and apparatus
US11093482B2 (en) Managing access by third parties to data in a network
WO2019072197A1 (zh) 一种红包发放方法、设备以及介质
US10826974B2 (en) Network based application management
US9516009B2 (en) Authenticating redirection service
JP6760974B2 (ja) トランザクション処理方法及びシステム
WO2023178924A1 (zh) 支付方法、用户终端、装置、设备、系统及介质
US20130152155A1 (en) Providing user attributes to complete an online transaction
CN113179282A (zh) 合并账号的方法、装置和服务器
JP7389198B2 (ja) チケット提供方法及びチケット提供システム
WO2018121164A1 (zh) 一种用于创建服务号的方法、设备及系统
WO2017181933A1 (zh) 数据处理方法及装置
US11816091B2 (en) Method and apparatus for tracking digital content transfer
US9749849B1 (en) Systems and methods for associating user personal information with wireless enabled devices
NZ731477A (en) Data processing method and apparatus
US20240154815A1 (en) Systems and methods for reputation-based transactions over a network
CN117135277A (zh) 客服会话请求处理方法及相关设备

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2017202892

Country of ref document: AU

Date of ref document: 20170418

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17785417

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17785417

Country of ref document: EP

Kind code of ref document: A1