Order processing method, electronic device and storage medium for weak network

Abstract

The present application provides an order processing method, electronic device and storage medium for weak networking, the method comprising: responding to a user's startup operation on a client, determining whether there is order archive information in the client, and if there is the order archive information, further determining the type of the order archive information; if the order archive information is the first type of order archive information, sending a request to a payment server to obtain the first payment result information corresponding to the first type of order archive information; if the order archive information is the second type of order archive information, sending a request to a distribution server to obtain the distribution result information corresponding to the second type of order archive information. The present application can effectively monitor the loss of orders in a weak networking environment, and enable users to have a good payment experience in a weak networking environment.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to an order processing method, electronic device and storage medium for weak networking. Background Art

[0002] In a weakly connected gaming environment, users may be disconnected from the payment server during payment or forced to exit the game. In this case, there may be problems such as missed orders and escaping orders. Therefore, timely detection of problems such as missed orders and escaping orders and improving the user's gaming payment experience are issues that need to be addressed in this field. Summary of the invention

[0003] In view of this, the purpose of the present application is to propose an order processing method, electronic device and storage medium for weak networking.

[0004] As a first aspect of the present application, a method for processing orders for weak network connection is provided, which is implemented through a client and includes:

[0005] In response to a user's startup operation on the client, determining whether order archive information exists in the client, and if the order archive information exists, further determining the type of the order archive information;

[0006] If the order archive information is first-category order archive information, sending a request to the payment server to obtain first payment result information corresponding to the first-category order archive information;

[0007] If the order archive information is the second type of order archive information, a request for obtaining the distribution result information corresponding to the second type of order archive information is sent to the distribution server.

[0008] Optionally, the method further includes:

[0009] In response to the user's payment operation, construct the first type of order archive information, and send a request to the payment server to obtain first payment result information corresponding to the first type of order archive information;

[0010] receiving the first payment result information sent by the payment server, and if the first payment result information is payment success information, constructing the second type of order archive information, deleting the first type of order archive information, and sending a request for executing the allocation corresponding to the second type of order archive information to the allocation server, and if the first payment result information is payment failure information, deleting the first type of order archive information;

[0011] In response to receiving the distribution result information sent by the distribution server, the second-category order archive information is deleted.

[0012] As a second aspect of the present application, a method for processing an order for a weak network is provided, which is implemented by a payment server and includes:

[0013] Receive a request from a client to obtain first payment result information corresponding to first-category order archive information, query whether the order corresponding to the first-category order archive information is paid successfully and generate the first payment result information, and send the first payment result information to the client.

[0014] Optionally, the method further includes:

[0015] Receive a request from a distribution server for obtaining second payment result information corresponding to the second type of order archive information, query whether the order corresponding to the second type of order archive information is paid successfully and generate the second payment result information, and send the second payment result information to the distribution server.

[0016] As a third aspect of the present application, a method for processing orders for weak networking is provided, which is implemented by a distribution server and includes:

[0017] Receive a request from a client to obtain distribution result information corresponding to the second type of order archive information, query whether the order corresponding to the second type of order archive information is successfully distributed and generate the distribution result information, and send the distribution result information to the client.

[0018] Optionally, the method further includes:

[0019] Receive a request sent by the client to execute the provisioning corresponding to the second-category order archive information, send a request to the payment server to obtain the second payment result information corresponding to the second-category order archive information, receive the second payment result information sent by the payment server, if the second payment result information is payment success information, execute the provisioning corresponding to the second-category order archive information, and send provisioning result information indicating successful provisioning to the client; if the second payment result information is payment failure information, send provisioning result information indicating failed provisioning to the client.

[0020] As a fourth aspect of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the above-mentioned order processing method provided in the present application can be implemented.

[0021] As a fifth aspect of the present application, a non-transitory computer-readable storage medium is provided, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the above-mentioned order processing method provided in the present application.

[0022] It can be seen from the above that the order processing method, electronic device and storage medium for weak networking provided by the present application can further improve the accuracy of order processing by verifying user payment information. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the present application or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1A A schematic diagram of an order processing method implemented by a client for weak networking provided in an embodiment of the present application;

[0025] Figure 1B A schematic diagram of another order processing method implemented by a client for weak networking provided in an embodiment of the present application;

[0026] Figure 1C A schematic diagram of an order information archive constructed by a client provided in an embodiment of the present application;

[0027] Figure 1D A schematic diagram of a payment interface provided in an embodiment of the present application;

[0028] Figure 2A A schematic diagram of an order processing method implemented by a payment server for weak networking provided in an embodiment of the present application;

[0029] Figure 2B A schematic diagram of another order processing method implemented by a payment server for weak network connection provided in an embodiment of the present application;

[0030] Figure 3A A schematic diagram of an order processing method implemented by a distribution server for weak networking provided in an embodiment of the present application;

[0031] Figure 3B A schematic diagram of another order processing method implemented by a distribution server for weak networking provided in an embodiment of the present application;

[0032] Figure 4 A schematic diagram of the electronic device structure of an order processing method for weak networking provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0034] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present application should be understood by people with ordinary skills in the field to which the present application belongs. The "first", "second" and similar words used in the embodiments of the present application do not indicate any order, quantity or importance, but are only used to distinguish different components. "Include" or "comprising" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects.

[0035] In the gaming environment, there are two common reasons for missed orders: First, when a user intends to purchase virtual props, the user's payment archive information is usually uploaded to the cloud, but in a weak network environment, the user may be disconnected from the payment server during payment, resulting in the user being unable to correctly upload the archive information to the cloud. Therefore, the game operator may cause progress errors when reading the cloud archive; second, the user actively kills the APP during the payment process, so that the order cannot be monitored when it is started again, resulting in missed orders, causing inconvenience to the user. Therefore, because it usually takes too long to manually review orders, some game operators usually send game props to customers in order to protect the rights and interests of customers, which may also cause the situation of escaping orders.

[0036] In response to the above problems, the embodiments of the present application provide an order processing method, electronic device and storage medium that are specifically targeted at weak networking. This method may reduce the occurrence of missed orders or order escapes in a weak networking environment and enhance the user's gaming experience.

[0037] Figure 1A A schematic diagram of an order processing method implemented by a client for weak networking provided in an embodiment of the present application is shown.

[0038] Figure 1B A schematic diagram of another order processing method implemented by a client for weak networking provided in an embodiment of the present application is shown.

[0039] like Figure 1A As shown, in some embodiments, after the user opens the game APP and starts the client 100, the client 100 will enter the Unity IAP module initialization. After the Unity IAP module initialization is completed, the user can start the game normally. When the client 100 enters the Unity IAP module initialization, it will also start the order verification program S102, such as Figure 1BAs shown, the order verification procedure of the client 100 includes the following steps:

[0040] S1022: In response to the user's startup operation on the client 100, determining whether there is order archive information in the client, and if there is the order archive information, further determining the type of the order archive information;

[0041] S1024: If the order archive information is the first type of order archive information, sending a request to the payment server 200 to obtain first payment result information corresponding to the first type of order archive information;

[0042] S1026: If the order archive information is the second type of order archive information, a request for obtaining the distribution result information corresponding to the second type of order archive information is sent to the distribution server 300.

[0043] In some embodiments, the client may provide gaming services to users, the payment server may be an official payment program or a third-party payment platform, and the distribution server may be a gaming server of a gaming operator.

[0044] It is understandable that in the gaming environment, especially in a weak network environment, the client often cannot receive the payment result information returned by the payment server due to network delays, or the user is disconnected from the allocation server before receiving the allocation result from the allocation server. Therefore, when reconnecting or restarting the game next time, setting up an order verification program can effectively monitor the payment results and protect the rights and interests of users.

[0045] Figure 1C A schematic diagram of order information archiving constructed by a client according to an embodiment of the present application is shown.

[0046] In some embodiments, users may make purchases in the game, such as Figure 1A As shown, when the user initiates a payment operation, the client 100 will start the corresponding payment program, such as Figure 1C As shown, the payment procedure of the client 100 includes the following steps:

[0047] S1042: In response to the user's payment operation, construct the first type of order archive information, and send a request to the payment server 200 to obtain first payment result information corresponding to the first type of order archive information;

[0048] S1044: receiving the first payment result information sent by the payment server 200;

[0049] S1045: If the first payment result information is payment failure information, deleting the first type of order archive information;

[0050] S1046: If the first payment result information is payment success information, construct the second type of order archive information, delete the first type of order archive information, and send a request to the distribution server 300 to execute the distribution corresponding to the second type of order archive information;

[0051] S1047: In response to receiving the distribution result information sent by the distribution server 300, delete the second-category order archive information.

[0052] As an optional embodiment, Figure 1C As shown, after the client 100 makes a payment, the client archive will be modified to the first type of order information archive, and a payment result request will be sent to the payment server, and the first payment result information sent by the payment server 200 will be accepted. The payment result information can be a "payment successful" or "payment failed" information prompt sent by the payment server 200. When the client 100 fails to pay due to network delays or other reasons or receives a "payment failed" message sent by the payment server 200, the default payment result is payment failure, and the first type of order information archive is directly deleted. The client 100 accepts the "payment successful" information prompt sent by the payment server as follows Figure 1D The display of "Payment Successful" is shown; when the client 100 has successfully obtained the payment success request, it will default to no longer accept multiple payment result information of the same order sent by the payment server, and only modify the order information archive once for the payment result of the same order, that is, change the first category of order information archive to the second category of order information archive, delete the first category of order information archive, and send a request for allocation corresponding to the second category of order archive information to the allocation server 300. When the allocation result information sent by the allocation server is received, the second category of order archive information is deleted. If the client 100 is disconnected from the payment server 200 due to network delay or the game APP is forcibly killed during payment, the client 100 will start the order verification program the next time the game is started or reconnected.

[0053] Figure 2A A schematic diagram of an order processing method implemented by a payment server for weak networking provided in an embodiment of the present application is shown.

[0054] like Figure 1C As shown, in some embodiments, when the client 100 starts the payment program, it will start the payment server 200 to start the payment process. Figure 2A As shown, the payment process of the payment server 200 includes:

[0055] S202: receiving a request from the client 100 for obtaining first payment result information corresponding to the first type of order archive information;

[0056] S204: Query whether the order corresponding to the first type of order archive information is paid successfully and generate the first payment result information, and send the first payment result information to the client 100.

[0057] As an optional embodiment, Figure 2A As shown, when the payment server 200 receives the payment result request sent by the client 100, the payment server 200 will query and verify the payment results in the order queue in sequence. When it is confirmed that the client 100 has successfully paid, a "payment success" message is sent to the client 200; when it is determined that the client 200 has not successfully paid, a "payment failure" message is sent to the client 100.

[0058] In some embodiments, in a weak network environment, when the client 100 is disconnected from the payment server 200 and cannot receive the payment result information from the payment server 200, the payment server 200 will continue to send the payment result of the corresponding order query to the client 100 until the client 100 reconnects with the payment server 200 and receives it successfully.

[0059] Figure 2B A schematic diagram of another order processing method implemented by a payment server for weak networking provided in an embodiment of the present application is shown.

[0060] like Figure 2B As shown, in some embodiments, the verification steps of the payment server 200 for the distribution server 300 include:

[0061] S206: receiving a request sent by the distribution server 300 for obtaining second payment result information corresponding to the second type of order archive information;

[0062] S208: Query whether the order corresponding to the second type of order archive information is paid successfully and generate the second payment result information, and send the second payment result information to the distribution server 300.

[0063] As an optional embodiment, Figure 2B As shown, when the payment server 200 receives the payment result request sent by the distribution server 300, the payment server 200 will query the order payment result corresponding to the second category order information, and when it is confirmed that the order corresponding to the second category order archive information is successfully paid, it will send an "order real" message to the distribution server 300; when it is confirmed that the order corresponding to the second category order archive information fails to pay, it will send an "order false" message to the distribution server 300.

[0064] Figure 3A A schematic diagram of an order processing method implemented by a distribution server for weak networking provided in an embodiment of the present application is shown.

[0065] like Figure 3A As shown, in some embodiments, the verification process of the distribution server 300 for the client 100 is:

[0066] S302: receiving a request sent by the client 100 for obtaining the distribution result information corresponding to the second type of order archive information;

[0067] S304: Query whether the order corresponding to the second-category order archive information is successfully distributed and generate the distribution result information, and send the distribution result information to the client 100.

[0068] As an optional embodiment, Figure 3A As shown, when the distribution server 300 receives the request for the distribution result information corresponding to the second type of order archive information sent by the client 100, it sends a payment result request for the corresponding order to the payment server, queries whether the order corresponding to the second type of order archive information is successfully distributed, and generates the distribution result information and sends it to the client 100. If the query finds that the distribution server 300 has successfully shipped the goods, the client is reminded to delete the archive; if the query finds that the distribution server 300 has not shipped the goods, the goods are shipped to the client and the client is reminded to delete the archive.

[0069] Figure 3B A schematic diagram of another order processing method implemented by a distribution server for weak networking provided in an embodiment of the present application is shown.

[0070] like Figure 3B As shown, in some embodiments, the verification process of the distribution server 300 for the payment server 200 further includes:

[0071] S302: receiving a request sent by the client 100 to execute a provisioning corresponding to the second type of order archive information;

[0072] S306: Send a request to the payment server 200 to obtain the second payment result information corresponding to the second type of order archive information, receive the second payment result information sent by the payment server 100, if the second payment result information is payment success information, execute the allocation corresponding to the second type of order archive information, and send the allocation result information of successful allocation to the client 100; if the second payment result information is payment failure information, send the allocation result information of failed allocation to the client.

[0073] As an optional embodiment, when the distribution server 300 receives the corresponding payment result information sent by the payment server 200 as "the order is real", it ships the goods to the client 100 and reminds the client to delete the archive; when the distribution server 300 receives the corresponding payment result information sent by the payment server 200 as "the order is false", it refuses to ship the goods to the client 100 and prompts the client 100 to delete the archive.

[0074] As an implementation method, when the client executes a payment, it will first modify the archive locally to the first type of order archive information, and send the first payment result request to the payment server. When the client receives the "payment successful" returned from the payment server, it modifies the local archive to the second type of order archive information, and sends a verification request to the distribution server. The distribution server will verify the authenticity of the order with the payment server in response to the verification request sent by the client. If the order is true, it will ship to the client. In a weak network exchange environment, because the client will automatically send an order verification request to the distribution server, whether it is disconnected or forced to kill the APP during the payment process, it will not result in missed orders or escape orders, which effectively protects the customer's gaming rights.

[0075] Based on the same technical concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the order processing method described in any of the above embodiments is implemented.

[0076] Figure 4 A more specific schematic diagram of the hardware structure of an electronic device provided in this embodiment is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.

[0077] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0078] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0079] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0080] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0081] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0082] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0083] The electronic device of the above embodiment is used to implement the corresponding order processing method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0084] Based on the same technical concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the order processing method described in any of the above embodiments.

[0085] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0086] The computer instructions stored in the storage medium of the above embodiments are used to enable the computer to execute the order processing method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0087] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present application (including the claims) is limited to these examples. In line with the concept of the present application, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of simplicity.

[0088] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present application difficult to understand, the known power supply / ground connection with the integrated circuit (IC) chip and other components may or may not be shown in the provided drawings. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform to be implemented in the embodiments of the present application (that is, these details should be fully within the scope of understanding of those skilled in the art). In the case of elaborating specific details (e.g., circuits) to describe exemplary embodiments of the present application, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details or when these specific details are changed. Therefore, these descriptions should be considered to be illustrative rather than restrictive.

[0089] Although the present application has been described in conjunction with specific embodiments of the present application, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0090] The embodiments of the present application are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the scope of protection of the present application.

Claims

1. A method for processing orders for weak networks, characterized in that: Implemented by a client, the method includes: In response to a user's startup operation on the client, determining whether order archive information exists in the client, and if the order archive information exists, further determining the type of the order archive information; If the order archive information is first-category order archive information, sending a request to the payment server to obtain first payment result information corresponding to the first-category order archive information; If the order archive information is the second type of order archive information, sending a request to the distribution server to obtain the distribution result information corresponding to the second type of order archive information; Wherein, the method further comprises: In response to the user's payment operation, construct the first type of order archive information, and send a request to the payment server to obtain first payment result information corresponding to the first type of order archive information; receiving the first payment result information sent by the payment server, and if the first payment result information is payment success information, constructing the second type of order archive information, deleting the first type of order archive information, and sending a request for executing the allocation corresponding to the second type of order archive information to the allocation server, and if the first payment result information is payment failure information, deleting the first type of order archive information; In response to receiving the distribution result information sent by the distribution server, the second-category order archive information is deleted.

2. The method according to claim 1, characterized in that Implemented by a payment server, the method comprises: receiving a request from a client for obtaining first payment result information corresponding to first-category order archive information, querying whether the order corresponding to the first-category order archive information is paid successfully and generating the first payment result information, and sending the first payment result information to the client; Wherein, the method further comprises: Receive a request from a distribution server for obtaining second payment result information corresponding to the second type of order archive information, query whether the order corresponding to the second type of order archive information is paid successfully and generate the second payment result information, and send the second payment result information to the distribution server.

3. A method for processing orders for weak network, characterized in that: Implemented by the Provisioning Server, including: receiving a request from a client for obtaining distribution result information corresponding to the second type of order archive information, querying whether the order corresponding to the second type of order archive information is successfully distributed and generating the distribution result information, and sending the distribution result information to the client; Wherein, the method further comprises: Receive a request sent by the client to execute the provisioning corresponding to the second-category order archive information, send a request to the payment server to obtain the second payment result information corresponding to the second-category order archive information, receive the second payment result information sent by the payment server, if the second payment result information is payment success information, execute the provisioning corresponding to the second-category order archive information, and send provisioning result information indicating successful provisioning to the client; if the second payment result information is payment failure information, send provisioning result information indicating failed provisioning to the client.

4. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 2 or the method according to claim 3 is implemented.

5. A non-transitory computer-readable storage medium, characterized in that: The non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the method described in any one of claims 1 to 2 or the method described in claim 3.

Images