Business request processing method and apparatus, electronic device, and computer readable medium

Abstract

Embodiments of the present disclosure disclose a service request processing method and device, electronic equipment and a computer readable medium. A specific embodiment of the method comprises: in response to receiving a service participation request, querying object participation flow information corresponding to the service participation request; determining the number of historical participations of the object according to the object participation flow information; constructing an object participation flow identifier according to the number of historical participations of the object and service object information; and storing the object participation flow identifier in a database corresponding to the object participation flow information. The embodiment is related to digital marketing, realizes user concurrency inventory restriction in a lock-free manner, and meets the user dimension inventory restriction of a business scenario.

Description

Technical Field

[0001] Embodiments of this disclosure relate to the field of computers, and more particularly to business request processing methods, apparatus, electronic devices, and computer-readable media. Background Technology

[0002] In real-world business scenarios, we frequently encounter situations where related business operations target user-level inventory. For example, user-level inventory might limit the number of times a user can participate in activities or claim prizes within the same business scenario. During system design, we often need to implement corresponding anti-overrun measures to prevent concurrent inventory deductions for the same user across related business scenarios. Currently, the common approach is to use distributed locks to prevent concurrent operations on user-level inventory within the relevant business scenarios.

[0003] However, the above approach usually has the following technical problems: over-reliance on distributed locks, lock failure or loss, and easy failure of user-level business inventory limits.

[0004] The information disclosed in this background section is only intended to enhance the understanding of the background of the inventive concept, and therefore may contain information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] The summary portion of this disclosure is intended to provide a brief overview of the concepts, which will be described in detail in the detailed description portion. This summary portion is not intended to identify key or essential features of the claimed technical solutions, nor is it intended to limit the scope of the claimed technical solutions.

[0006] Some embodiments of this disclosure provide service request processing methods, apparatuses, electronic devices, computer-readable media, and program products to address the technical problems mentioned in the background section above.

[0007] In a first aspect, some embodiments of this disclosure provide a business request processing method, the method comprising: in response to receiving a business participation request, querying object participation log information corresponding to the business participation request; determining the historical participation count of an object based on the object participation log information; constructing an object participation log identifier based on the historical participation count of the object and business object information; and storing the object participation log identifier in the database corresponding to the object participation log information.

[0008] Optionally, the above query of the object participation log information corresponding to the above business participation request includes: determining the object identifier and business identifier corresponding to the above business participation request; and querying the object participation log information corresponding to the above object identifier and the above business identifier.

[0009] Optionally, the aforementioned business object information includes an object identifier and a business identifier; and the aforementioned construction of an object participation serial identifier based on the object's historical participation count and business object information includes: determining whether the object's historical participation count is greater than or equal to a preset object participation count; in response to determining that the object's historical participation count is less than the preset object participation count, concatenating the object identifier, the business identifier, and the object's historical participation count into an object participation serial identifier.

[0010] Optionally, before querying the object participation log information corresponding to the above business participation request, the method further includes: determining whether the object identifier carried in the above business participation request is associated with the business identifier corresponding to the above business participation request; in response to determining that the object identifier is associated with the business identifier corresponding to the above business participation request, determining the business configuration information corresponding to the object identifier and the business identifier, wherein the business configuration information includes a preset number of object participations.

[0011] Optionally, the above method further includes: in response to determining whether the historical participation count of the above object is greater than or equal to the preset participation count of the above object, sending service participation restriction information to the terminal corresponding to the service participation request, wherein the service participation restriction information indicates that the service participation count has reached the upper limit.

[0012] Secondly, some embodiments of this disclosure provide a business request processing apparatus, the apparatus comprising: a query unit configured to query object participation log information corresponding to the business participation request in response to receiving a business participation request; a determination unit configured to determine the historical participation count of an object based on the object participation log information; a construction unit configured to construct an object participation log identifier based on the historical participation count of the object and business object information; and a storage unit configured to store the object participation log identifier in a database corresponding to the object participation log information.

[0013] Optionally, the query unit is further configured to: determine the object identifier and business identifier corresponding to the above-mentioned business participation request; and query the object participation log information corresponding to the above-mentioned object identifier and business identifier.

[0014] Optionally, the above-mentioned business object information includes object identifier and business identifier.

[0015] Optionally, the construction unit is further configured to: determine whether the historical participation count of the above object is greater than or equal to the preset object participation count; in response to determining that the historical participation count of the above object is less than the preset object participation count, concatenate the above object identifier, the above business identifier and the above object historical participation count into an object participation serial identifier.

[0016] Optionally, prior to the query unit, the business request processing apparatus further includes: a first determining unit configured to determine whether the object identifier carried in the business participation request is associated with the business identifier corresponding to the business participation request; and a second determining unit configured to determine business configuration information corresponding to the object identifier and the business identifier in response to determining that the object identifier is associated with the business identifier corresponding to the business participation request, wherein the business configuration information includes a preset number of object participations.

[0017] Optionally, the service request processing apparatus further includes: a sending unit configured to send service participation restriction information to the terminal corresponding to the service participation request in response to determining whether the historical participation count of the object is greater than or equal to the preset participation count of the object, wherein the service participation restriction information indicates that the service participation count has reached the upper limit.

[0018] Thirdly, some embodiments of this disclosure provide an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation of the first aspect above.

[0019] Fourthly, some embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method described in any of the implementations of the first aspect above.

[0020] Fifthly, some embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the method described in any of the implementations of the first aspect above.

[0021] The above embodiments of this disclosure have the following beneficial effects: The business request processing methods of some embodiments of this disclosure achieve user concurrent inventory limits without relying on distributed locks. Specifically, the reason why user-level business inventory limits are prone to failure is that they rely too heavily on distributed locks, leading to lock failure or loss. Based on this, the business request processing methods of some embodiments of this disclosure first, in response to receiving a business participation request, query the object participation log information corresponding to the business participation request. This allows querying the object's (user's) historical business participation. Next, based on the object participation log information, determine the object's historical participation count. This allows determining whether the user's concurrent inventory limit has been reached based on the object's historical participation count. Thus, it can be determined whether the business participation request can continue to execute. Then, based on the object's historical participation count and business object information, construct an object participation log identifier. This allows setting a business log identifier for each successful user participation, facilitating whether subsequent business participation reaches the user's concurrent inventory limit. Finally, store the object participation log identifier in the database corresponding to the object participation log information. Thus, each time a user sends a business participation request, the historical participation count can be determined based on the object participation log identifier in the database. This enables the limitation of concurrent inventory for users in a lock-free environment, thereby meeting the business scenario's requirements for user-level inventory. Attached Figure Description

[0022] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and elements are not necessarily drawn to scale.

[0023] Figure 1 This is a schematic diagram illustrating an application scenario of the business request processing method according to some embodiments of this disclosure;

[0024] Figure 2 These are flowcharts of some embodiments of the business request processing method according to this disclosure;

[0025] Figure 3 These are flowcharts of some other embodiments of the business request processing method according to this disclosure;

[0026] Figure 4 These are schematic diagrams illustrating the structure of some embodiments of the service request processing apparatus according to this disclosure;

[0027] Figure 5 This is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. Detailed Implementation

[0028] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0029] It should also be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.

[0030] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0031] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0032] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0033] This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0034] Figure 1 This is a schematic diagram of an application scenario of a business request processing method according to some embodiments of this disclosure.

[0035] exist Figure 1 In the application scenario, firstly, the computing device 101 can respond to receiving a business participation request 102 by querying the object participation log information 103 corresponding to the business participation request 102. Next, the computing device 101 can determine the object's historical participation count 104 based on the object participation log information 103. Then, the computing device 101 can construct an object participation log identifier 106 based on the object's historical participation count 104 and the business object information 105. Finally, the computing device 101 can store the object participation log identifier 106 in the database corresponding to the object participation log information.

[0036] It should be noted that the aforementioned computing device 101 can be either hardware or software. When the computing device is hardware, it can be implemented as a distributed cluster consisting of multiple servers or terminal devices, or as a single server or a single terminal device. When the computing device is software, it can be installed within the hardware devices listed above. It can be implemented as, for example, multiple software programs or software modules used to provide distributed services, or as a single software program or software module. No specific limitations are made here.

[0037] It should be understood that Figure 1 The number of computing devices shown is merely illustrative. Any number of computing devices can be used depending on implementation needs.

[0038] Continue to refer to Figure 2 The flowchart 200 illustrates some embodiments of a service request processing method according to this disclosure. The service request processing method includes the following steps:

[0039] Step 201: In response to receiving a business participation request, query the object participation log information corresponding to the above business participation request.

[0040] In some embodiments, the execution body of the business request processing method (e.g., Figure 1 The computing device 101 shown can, in response to receiving a business participation request, query the object participation log information corresponding to the business participation request. Here, the business participation request can be a request sent by a user to participate in a certain business. For example, the business participation request can be a request to participate in a certain business activity (a shopping discount activity) or to claim virtual prizes (coupons). Here, the business participation request can carry an object identifier and a business identifier. The object identifier can uniquely represent an object (user). The business identifier can uniquely point to a business. The object participation log information can refer to the historical participation information of a certain object in a certain business. For example, the object participation log information can be an object participation log detail table.

[0041] In practice, the object participation log information pointed to by the object identifier carried in the business participation request can be queried in the associated database.

[0042] In some optional implementations of some embodiments, the aforementioned execution entity can query the object participation log information corresponding to the aforementioned business participation request through the following steps:

[0043] The first step is to determine the object identifier and business identifier corresponding to the aforementioned business participation request. That is, to determine the object identifier and business identifier carried in the business participation request.

[0044] The second step is to query the object participation log information corresponding to the aforementioned object identifier and the aforementioned business identifier. This can be done by querying the database storing the object participation log information that associates the aforementioned object identifier with the aforementioned business identifier.

[0045] Optionally, before querying the object participation log information corresponding to the above business participation request, the above method further includes:

[0046] The first step is to determine whether the object identifier carried in the aforementioned business participation request is associated with the business identifier corresponding to the business participation request. That is, to determine whether there is a mapping relationship between the object identifier and the business identifier corresponding to the business participation request. For example, the business identifier corresponding to the object identifier can be queried in the database. This will determine whether the object corresponding to the object identifier is participating in the business activity for the first time.

[0047] The second step involves determining the association between the aforementioned object identifier and the service identifier corresponding to the aforementioned service participation request, and then determining the service configuration information corresponding to the aforementioned object identifier and the aforementioned service identifier. This service configuration information includes a preset number of object participation attempts. That is, the service configuration information corresponding to the aforementioned object identifier and the aforementioned service identifier can be queried from the associated database. The preset number of object participation attempts may refer to the maximum number of times an object can participate in this service.

[0048] Step 202: Determine the number of times an object has participated in the transaction based on the above-mentioned object participation information.

[0049] In some embodiments, the executing entity can determine the number of times an object has participated in the past based on the object participation log information. For example, the number of times an object has participated in the past can be determined based on the number of historical object participation log identifiers recorded in the object participation log information.

[0050] Step 203: Based on the above-mentioned historical participation counts and business object information, construct an object participation log identifier.

[0051] In some embodiments, the executing entity can construct an object participation log identifier based on the object's historical participation count and business object information. Here, the business object information can refer to the information about the object's participation in the business corresponding to the business participation request, and may include the object identifier. That is, the object's historical participation count and business object information can be combined to form the object participation log identifier.

[0052] Step 204: Store the above-mentioned object participation serial identifier in the database corresponding to the above-mentioned object participation serial information.

[0053] In some embodiments, the executing entity may store the object participation serial identifier in the database corresponding to the object participation serial information. Here, the database corresponding to the object participation serial information may refer to a database that stores object participation serial information.

[0054] The above embodiments of this disclosure have the following beneficial effects: The business request processing methods of some embodiments of this disclosure achieve user concurrent inventory limits without relying on distributed locks. Specifically, the reason why user-level business inventory limits are prone to failure is that they rely too heavily on distributed locks, leading to lock failure or loss. Based on this, the business request processing methods of some embodiments of this disclosure first, in response to receiving a business participation request, query the object participation log information corresponding to the business participation request. This allows querying the object's (user's) historical business participation. Next, based on the object participation log information, determine the object's historical participation count. This allows determining whether the user's concurrent inventory limit has been reached based on the object's historical participation count. Thus, it can be determined whether the business participation request can continue to execute. Then, based on the object's historical participation count and business object information, construct an object participation log identifier. This allows setting a business log identifier for each successful user participation, facilitating whether subsequent business participation reaches the user's concurrent inventory limit. Finally, store the object participation log identifier in the database corresponding to the object participation log information. Thus, each time a user sends a business participation request, the historical participation count can be determined based on the object participation log identifier in the database. This enables the limitation of concurrent inventory for users in a lock-free environment, thereby meeting the business scenario's requirements for user-level inventory.

[0055] Continue to refer to Figure 3 , Figure 3 A flow 300 of another embodiment of the service request processing method according to this disclosure is shown. The service request processing method includes the following steps:

[0056] Step 301: In response to receiving a business participation request, query the object participation log information corresponding to the above business participation request.

[0057] Step 302: Determine the number of times an object has participated in the transaction based on the above-mentioned object participation information.

[0058] In some embodiments, the content of steps 301-302 is the same as that of steps 201-202, and will not be described in detail here.

[0059] Step 303: Determine whether the historical participation count of the above-mentioned object is greater than or equal to the preset participation count of the object.

[0060] In some embodiments, the execution body of the business request processing method (e.g., Figure 1 The computing device 101 shown can determine whether the historical participation count of the aforementioned object is greater than or equal to the preset object participation count. The preset object participation count may refer to the maximum number of times an object can participate in a business corresponding to a business participation request.

[0061] Step 304: In response to determining that the historical participation count of the above object is less than the preset object participation count, the object identifier, business identifier and the historical participation count of the above object are concatenated to form the object participation serial identifier.

[0062] In some embodiments, the execution entity may, in response to determining that the number of times the object has participated in the past is less than the preset number of times the object has participated, concatenate the object identifier, the business identifier and the number of times the object has participated in the past to form an object participation serial identifier.

[0063] Step 305: Store the above-mentioned object participation serial identifier in the database corresponding to the above-mentioned object participation serial information.

[0064] In some embodiments, the content of step 305 is the same as that of step 204, and will not be described in detail here.

[0065] Optionally, in response to determining whether the historical participation count of the aforementioned object is greater than or equal to the preset participation count of the aforementioned object, service participation restriction information is sent to the terminal corresponding to the aforementioned service participation request.

[0066] In some embodiments, the executing entity may send service participation restriction information to the terminal corresponding to the service participation request in response to determining whether the historical participation count of the object is greater than or equal to the preset object participation count. The service participation restriction information indicates that the service participation count has reached its limit.

[0067] from Figure 3 It can be seen from this that, with Figure 2 Compared to the description of some corresponding embodiments, Figure 3 In some corresponding embodiments, the process 300 of the business request processing method can generate a unique business flow identifier (object participation flow identifier) ​​containing the user's inventory consumption (number of object participations). Therefore, based on the object participation flow identifier containing the user's inventory consumption, inventory deduction can be implemented under concurrent, lock-free conditions.

[0068] Further reference Figure 4 As an implementation of the methods shown in the above figures, this disclosure provides some embodiments of a service request processing apparatus, which are similar to... Figure 2 Corresponding to the method embodiments shown, this service request processing device can be specifically applied to various electronic devices.

[0069] like Figure 4As shown, a business request processing apparatus 400 in some embodiments includes: a query unit 401, a determination unit 402, a construction unit 403, and a storage unit 404. The query unit 401 is configured to query object participation log information corresponding to a received business participation request in response to such request; the determination unit 402 is configured to determine the historical participation count of an object based on the object participation log information; the construction unit 403 is configured to construct an object participation log identifier based on the historical participation count and the business object information; and the storage unit 404 is configured to store the object participation log identifier in the database corresponding to the object participation log information.

[0070] Optionally, the query unit 401 is further configured to: determine the object identifier and business identifier corresponding to the above-mentioned business participation request; and query the object participation flow information corresponding to the above-mentioned object identifier and business identifier.

[0071] Optionally, the above-mentioned business object information includes object identifier and business identifier.

[0072] Optionally, the construction unit 403 is further configured to: determine whether the historical participation count of the above object is greater than or equal to the preset object participation count; in response to determining that the historical participation count of the above object is less than the preset object participation count, concatenate the above object identifier, the above business identifier and the above historical participation count of the object into an object participation serial identifier.

[0073] Optionally, before the query unit 401, the service request processing device 400 further includes: a first determining unit configured to determine whether the object identifier carried in the service participation request is associated with the service identifier corresponding to the service participation request; and a second determining unit configured to determine service configuration information corresponding to the object identifier and the service identifier in response to determining that the object identifier is associated with the service identifier corresponding to the service participation request, wherein the service configuration information includes a preset number of object participations.

[0074] Optionally, the service request processing apparatus 400 further includes: a sending unit configured to send service participation restriction information to the terminal corresponding to the service participation request in response to determining whether the historical participation count of the object is greater than or equal to the preset participation count of the object, wherein the service participation restriction information indicates that the service participation count has reached the upper limit.

[0075] It is understandable that the units described in the service request processing device 400 are related to the reference. Figure 2 The steps in the described method correspond to each other. Therefore, the operations, features, and beneficial effects described above for the method also apply to the business request processing device 400 and the units contained therein, and will not be repeated here.

[0076] The following is for reference. Figure 5 It illustrates electronic devices suitable for implementing some embodiments of this disclosure (e.g., Figure 1 The diagram shows the structure of the computing device 101)500. Electronic devices in some embodiments of this disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of this disclosure.

[0077] like Figure 5 As shown, the electronic device 500 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the electronic device 500. The processing unit 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0078] Typically, the following devices can be connected to I / O interface 505: input devices 506 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 508 including, for example, magnetic tapes, hard disks, etc.; and communication devices 509. Communication device 509 allows electronic device 500 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 An electronic device 500 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 5 Each box shown can represent a device or multiple devices as needed.

[0079] In particular, according to some embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 509, or installed from a storage device 508, or installed from a ROM 502. When the computer program is executed by the processing device 501, it performs the functions defined in the methods of some embodiments of this disclosure.

[0080] It should be noted that, in some embodiments of this disclosure, the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In some embodiments of this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In some embodiments of this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0081] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol, such as HTTP (Hypertext Transfer Protocol), and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0082] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: in response to receiving a business participation request, query the object participation log information corresponding to the business participation request; determine the object's historical participation count based on the object participation log information; construct an object participation log identifier based on the object's historical participation count and business object information; and store the object participation log identifier in the database corresponding to the object participation log information.

[0083] Computer program code for performing operations of some embodiments of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0084] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0085] The units described in some embodiments of this disclosure can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor may be described as including a query unit, a determination unit, a construction unit, and a storage unit. The names of these units do not necessarily limit the unit itself; for example, the determination unit may also be described as "a unit that determines the historical number of times an object has participated based on the aforementioned object participation log information."

[0086] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0087] Some embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements any of the above-described business request processing methods.

[0088] The above description is merely a selection of preferred embodiments of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in the embodiments of this disclosure.

Claims

1. A business request processing method, comprising: In response to receiving a business participation request, query the object participation log information corresponding to the business participation request; Based on the object's participation information, determine the object's historical participation count; Based on the object's historical participation count and business object information, an object participation log identifier is constructed, wherein the business object information includes an object identifier and a business identifier; The object's participation identifier is stored in the database corresponding to the object's participation information. The step of constructing an object participation log identifier based on the object's historical participation count and business object information includes: Determine whether the object's historical participation count is greater than or equal to a preset object participation count; In response to determining that the object's historical participation count is less than the preset object participation count, the object identifier, the business identifier, and the object's historical participation count are concatenated to form an object participation log identifier; In response to determining whether the historical participation count of the object is greater than or equal to the preset participation count of the object, service participation restriction information is sent to the terminal corresponding to the service participation request.

2. The method according to claim 1, wherein, The query for the object participation log information corresponding to the business participation request includes: Determine the object identifier and business identifier corresponding to the business participation request; Query the transaction log information of the object corresponding to the object identifier and the business identifier.

3. The method according to claim 1, wherein, Before querying the object participation log information corresponding to the business participation request, the method further includes: Based on the object identifier carried in the service participation request, determine whether the object identifier is associated with the service identifier corresponding to the service participation request; In response to determining that the object identifier is associated with the service identifier corresponding to the service participation request, the service configuration information corresponding to the object identifier and the service identifier is determined, wherein the service configuration information includes a preset number of object participations.

4. The method according to claim 1, wherein, The business participation restriction information indicates that the maximum number of business participations has been reached.

5. A service request processing apparatus, comprising: The query unit is configured to query the object participation log information corresponding to the business participation request in response to receiving the business participation request. The determining unit is configured to determine the number of times an object has participated in the historical process based on the object's participation information. The construction unit is configured to construct an object participation log identifier based on the object's historical participation count and business object information, wherein the business object information includes an object identifier and a business identifier; The storage unit is configured to store the object participation serial identifier in the database corresponding to the object participation serial information; The step of constructing an object participation log identifier based on the object's historical participation count and business object information includes: Determine whether the object's historical participation count is greater than or equal to a preset object participation count; In response to determining that the object's historical participation count is less than the preset object participation count, the object identifier, the business identifier, and the object's historical participation count are concatenated to form an object participation log identifier; In response to determining whether the historical participation count of the object is greater than or equal to the preset participation count of the object, service participation restriction information is sent to the terminal corresponding to the service participation request.

6. The service request processing apparatus according to claim 5, wherein, The query unit is further configured to: Determine the object identifier and business identifier corresponding to the business participation request; Query the transaction log information of the object corresponding to the object identifier and the business identifier.

7. An electronic device, comprising: One or more processors; A storage device on which one or more programs are stored; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-4.

8. A computer-readable medium having a computer program stored thereon, wherein, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-4.

9. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-4.

Images