CN111145033A - Service item receiving authority processing method and device and storage medium - Google Patents
Service item receiving authority processing method and device and storage medium Download PDFInfo
- Publication number
- CN111145033A CN111145033A CN201911170117.3A CN201911170117A CN111145033A CN 111145033 A CN111145033 A CN 111145033A CN 201911170117 A CN201911170117 A CN 201911170117A CN 111145033 A CN111145033 A CN 111145033A
- Authority
- CN
- China
- Prior art keywords
- user
- permission
- background server
- picking
- service item
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
Abstract
The disclosure relates to the technical field of data processing, and provides a service item receiving authority processing method, a service item receiving authority processing device, a computer storage medium and an electronic device, wherein the service item receiving authority processing method comprises the following steps: responding to the receiving operation of a user to a service project, and acquiring portrait information of the user; based on the portrait information, calling a background server to inquire whether a user has a picking authority; if the query result of the picking permission is not received in the first time period, judging that the background server fails to query; and if the received query result indicates that the user does not have the getting permission, calling the background server again to enable the background server to generate the getting permission for the user. The service item receiving authority processing method can solve the technical problems of heavy burden and tight coupling of the server, avoid error generation and repeated generation of the receiving authority, and ensure the accuracy of the receiving authority generation.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a method and an apparatus for processing a service item receiving right, a computer storage medium, and an electronic device.
Background
With the rapid development of computer and internet technologies, the related data processing field is also rapidly developing. Taking the insurance industry as an example, generally, after a user purchases a certain kind of risk, an insurance company gives a service item related to the user, such as: since the telephone doctor service (the user can consult the doctor for free telephone to solve his health problem), when the user data is huge, how to handle the right to receive the service item becomes a focus of attention of the relevant personnel.
At present, items such as right acquisition, right query, right generation, subsequent management and the like of service items are generally centralized in the same system or server for execution, so that the server is overloaded, and a tight coupling phenomenon exists in programs.
In view of the above, there is a need in the art to develop a new method and apparatus for processing the acquisition right of a service item.
It is to be noted that the information disclosed in the background section above is only used to enhance understanding of the background of the present disclosure.
Disclosure of Invention
The purpose of the present disclosure is to provide a service item receiving permission processing method, a service item receiving permission processing apparatus, a computer storage medium, and an electronic device, thereby avoiding, at least to a certain extent, the defects of the prior art that a server is overloaded and tightly coupled.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.
According to a first aspect of the present disclosure, a method for processing a pickup permission of a service item is provided, which is applied to a client that processes the pickup permission, and includes: responding to the receiving operation of the user to the service item, and acquiring portrait information of the user; based on the portrait information, calling a background server to inquire whether the user has the picking authority; if the query result of the picking permission is not received in a first time period, judging that the background server fails to query; if the received query result indicates that the user does not have the picking permission, the background server is called again so that the background server generates the picking permission for the user.
In an exemplary embodiment of the present disclosure, the method further comprises: and if the generation result of the picking permission is not received in a second time period, judging that the background server fails to generate the picking permission.
In an exemplary embodiment of the present disclosure, the method further comprises: and if the received query result indicates that the user has the picking permission, receiving a first permission number sent by the background server.
According to a second aspect of the present disclosure, a method for processing a pickup permission of a service item is provided, which is applied to a background server that processes the pickup permission, and includes: responding to the calling operation of the client, and inquiring whether the user has the picking permission or not based on the portrait information; if the user has the pickup permission, the first permission number corresponding to the pickup permission is sent to the client; and if the user does not have the picking permission, responding to the recall operation of the client side, and generating the picking permission for the user.
In an exemplary embodiment of the disclosure, after generating the pickup right for the user, the method further comprises: inquiring the generation result of the receiving authority; if the generation result is successful, sending a second permission number corresponding to the picking permission to the client; and if the generation result is failure, sending a failure message to the client.
In an exemplary embodiment of the present disclosure, the method further comprises: and storing the second authority number into a database.
According to a third aspect of the present disclosure, there is provided a device for processing a pickup permission of a service item, applied to a client that processes the pickup permission, the device including: the first calling module is used for responding to the receiving operation of the user on the service item and acquiring portrait information of the user; based on the portrait information, calling a background server to inquire whether the user has the picking authority; the first judgment module is used for judging that the background server fails to inquire if the inquiry result of the picking permission is not received within a first time period; and the second calling module is used for calling the background server again to enable the background server to generate the pickup permission for the user if the received query result indicates that the user does not have the pickup permission.
According to a fourth aspect of the present disclosure, there is provided a device for processing pickup permission of a service item, applied to a background server that processes the pickup permission, including: the permission query module is used for responding to the calling operation of the client and querying whether the user has the picking permission or not based on the portrait information; the sending module is used for sending the first permission number corresponding to the getting permission to the client if the user has the getting permission; and the permission generation module is used for responding to the recall operation of the client and generating the pickup permission for the user if the user does not have the pickup permission.
According to a fifth aspect of the present disclosure, there is provided a computer storage medium having stored thereon a computer program which, when executed by a processor, implements the method for processing the right to receive a service item according to the first and second aspects.
According to a sixth aspect of the present disclosure, there is provided an electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the method for processing the right to receive of the service item according to the first aspect and the second aspect via executing the executable instructions.
As can be seen from the foregoing technical solutions, the method for processing right to receive a service item, the device for processing right to receive a service item, the computer storage medium, and the electronic device in the exemplary embodiments of the present disclosure have at least the following advantages and positive effects:
in the technical solutions provided by some embodiments of the present disclosure, on one hand, in response to a user's operation of getting a service item, portrait information of the user is acquired; based on the portrait information, the background server is called to inquire whether the user has the picking authority or not, the technical problem that the picking authority is repeatedly generated or the picking authority is not generated for the user can be solved, and the inquiry accuracy of the picking authority is improved. Furthermore, if the query result of the receiving permission is not received in the first time period, the query of the background server is judged to be failed, so that the technical problem of wrong query caused by endless waiting during network interruption can be avoided, and the stability of the server is improved. On the other hand, if the received query result indicates that the user does not have the getting right, the background server is called again so that the background server generates the getting right for the user, and the rights and interests of each user can be reasonably guaranteed.
In the technical solutions provided by some embodiments of the present disclosure, generally, the present disclosure concentrates relevant operations of getting permission on a client, and concentrates relevant operations of querying, generating, and the like of the getting permission on a backend server, so as to solve the technical problems in the prior art that a server is overloaded, a program is tightly coupled, and the getting permission cannot be correctly generated, and improve the generation accuracy and the generation efficiency of the getting permission.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.
FIG. 1 is a flow chart illustrating a method for processing a service item's picking right in an exemplary embodiment of the disclosure;
FIG. 2 is a flow chart illustrating a method for processing a service item's picking right in another exemplary embodiment of the present disclosure;
FIG. 3 is a flowchart illustrating an overall method for processing a service item's right to receive according to an exemplary embodiment of the disclosure;
fig. 4 is a schematic structural diagram of a pickup right processing device for a service item in an exemplary embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a pickup right processing device for a service item in an exemplary embodiment of the present disclosure;
FIG. 6 shows a schematic diagram of a structure of a computer storage medium in an exemplary embodiment of the disclosure;
fig. 7 shows a schematic structural diagram of an electronic device in an exemplary embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
The terms "a," "an," "the," and "said" are used in this specification to denote the presence of one or more elements/components/parts/etc.; the terms "comprising" and "having" are intended to be inclusive and mean that there may be additional elements/components/etc. other than the listed elements/components/etc.; the terms "first" and "second", etc. are used merely as labels, and are not limiting on the number of their objects.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities.
At present, items such as right acquisition, right query, right generation, subsequent management and the like of service items are generally centralized in the same system or server for execution, so that the server is overloaded, and a tight coupling phenomenon exists in programs.
In the embodiment of the disclosure, firstly, a method for processing the right to receive a service item is provided, which overcomes the defects of heavy burden and tight coupling phenomenon of a server in the method for processing the right to receive a service item provided in the prior art at least to a certain extent.
Fig. 1 is a flowchart illustrating a method for processing a pickup right of a service item in an exemplary embodiment of the disclosure, where an execution subject of the method for processing a pickup right of a service item may be a server that processes a pickup right of a service item.
Referring to fig. 1, a method for processing a pickup right of a service item according to one embodiment of the present disclosure includes the steps of:
step S110, responding to the receiving operation of the user to the service item, and acquiring portrait information of the user;
step S120, based on the portrait information, calling a background server to inquire whether the user has the picking authority;
step S130, if the query result of the picking permission is not received in a first time period, judging that the background server fails to query;
step S140, if the received query result indicates that the user does not have the getting right, the background server is called again to enable the background server to generate the getting right for the user.
In the technical scheme provided by the embodiment shown in fig. 1, on one hand, the portrait information of the user is obtained in response to the user's pickup operation on the service item, and based on the portrait information, the background server is called to inquire whether the user has pickup permission, so that the technical problem that the pickup permission is repeatedly generated or is not generated for the user can be solved, and the inquiry accuracy of the pickup permission is improved. Furthermore, if the query result of the receiving permission is not received in the first time period, the query of the background server is judged to be failed, so that the technical problem of wrong query caused by endless waiting during network interruption can be avoided, and the stability of the server is improved. On the other hand, if the received query result indicates that the user does not have the getting right, the background server is called again so that the background server generates the getting right for the user, and the rights and interests of each user can be reasonably guaranteed.
In the technical solution provided in the embodiment shown in fig. 1, generally, the present disclosure concentrates the operations related to the receiving permission on the client, and concentrates the operations related to the query, generation, and the like of the receiving permission on the background server, so that the front-end client is separated from the back-end management server, and each client performs its own professional task, and the division of work is clear, thereby increasing the flexibility of system docking, being able to solve the technical problems that the server in the prior art is overloaded, the program is tightly coupled, and the receiving permission cannot be correctly generated, and improving the generation accuracy and the generation efficiency of the receiving permission.
The following describes the specific implementation of each step in fig. 1 in detail:
in an exemplary embodiment of the present disclosure, the client may be, for example, an official WeChat, an official website, etc. of an insurance company. The backend server may be a backend management system of some insurance company.
In step S110, in response to a user' S operation to receive the service item, portrait information of the user is acquired.
In an exemplary embodiment of the present disclosure, the user may be a customer who purchases a target risk, for example: a client who has purchased a health insurance (the health insurance is a Chinese short for health insurance, and refers to a client who pays insurance money for loss caused by health reasons in a mode of disease insurance, medical insurance, disability income loss insurance, nursing insurance, and the like, or a client who has purchased a life insurance (life insurance, one of life insurance, using the life of an insured person as an insurance target, and using the survival or death of the insured person as a payment condition).
In an exemplary embodiment of the present disclosure, the service item refers to service content provided by a customer to meet the customer demand, and different types of companies may provide different service items for the customer. Taking an insurance company as an example, the service item may be an additional gifting service provided by the insurance company for the user who purchased the target risk species, such as: the insurance company provides health consultation services for users who purchase health insurance (for example, the users can consult doctors 10 times by free telephone to solve the daily health problems).
In an exemplary embodiment of the present disclosure, the operation of the user to pick up the service item may be an operation of the user clicking a relevant pick-up icon to confirm the pick-up of the service item through an operation interface of the client (an official WeChat of an insurance company, an official website, and the like), or reserving a service time of the service item.
In an exemplary embodiment of the present disclosure, when receiving a user's operation of getting a service item, portrait information of the user may be acquired, for example: face information of the user, fingerprint information of the user, account information (user name, telephone number or identification number) of the user, and the like. The image information of the user may be set by itself according to actual conditions, and the present disclosure is not limited to this.
In step S120, based on the portrait information, a background server is called to query whether the user has the right to pick up.
In an exemplary embodiment of the present disclosure, after obtaining the portrait information of the user, the client may invoke the background server to query whether the user has pickup permission (i.e., pickup qualification) based on the portrait information. For example, the background server may compare the similarity between the face information of the user and the pre-stored face information with the picking-up right, and if the similarity is greater than a preset threshold (e.g., 90%), it may be queried that the user has the picking-up right. For example, the background server may further query whether the user has the right to receive through account information (a user name, a phone number, an identity card number, or the like) of the user, and if the user has the right to receive, the background server may obtain a first right number of the user (a preset right to receive number when the right to receive is generated for the user), and send the first right number to the client.
In the exemplary embodiment of the disclosure, whether the user has the picking authority or not is queried according to the user portrait information, so that the query accuracy can be improved, and repeated generation of subsequent picking authority is avoided.
In an exemplary embodiment of the present disclosure, while the client invokes the background server, a timeout mechanism (similar to a countdown mechanism) may be started, for example, a first time period (for example, 0.2 second) may be set, and then, the query result returned by the background server is received only within the first time period, and if the first time period is exceeded, the invocation of the background server is terminated, and the query process of the background server is terminated. Therefore, system breakdown of the background server can be avoided, and internal resources of the server are saved.
In the exemplary embodiment of the present disclosure, it should be noted that the specific duration of the first time period may be set according to actual situations, and belongs to the protection scope of the present disclosure.
In step S130, if the query result of the pickup permission is not received within the first time period, it is determined that the background server query fails.
In an exemplary embodiment of the present disclosure, if the client does not receive the query result of the pickup permission within the first time period, it may be determined that the query is overtime, that is, the query of the background server fails. Therefore, the background server can immediately terminate the related query process, the technical problem of query errors caused by endless waiting during network interruption is avoided, and the stability of the server is improved.
In step S140, if the received query result indicates that the user does not have the pickup right, the background server is called again, so that the background server generates the pickup right for the user.
In an exemplary embodiment of the present disclosure, if in the first time period, the query result received by the client is: and if the user has the receiving authority, the first authority number sent by the background server can be received.
In an exemplary embodiment of the present disclosure, if in the first time period, the query result received by the client is: and if the user does not have the receiving authority, the background server can be called again so that the background server generates the receiving authority for the user. Specifically, when a recall operation of the client is received, the background server may create a second permission number for the user, associate the second permission number with the user, and generate the pickup permission for the user.
In the exemplary embodiment of the disclosure, referring to the related explanation of the step S110, when the client calls the backend server again, the timeout mechanism is started, and it is determined whether the generation result of the pickup right is received within the second time period (for example, 0.3 second, which may be set according to the actual situation), and if the generation result is not received within the second time period, it may be determined that the generation is timeout, that is, the backend server fails to generate the pickup right. Therefore, the background server can immediately terminate the related process for generating the picking permission, and avoid the situation that the picking permission is not generated or is repeatedly generated under the conditions that the service system is not strictly designed or program bugs occur due to network delay.
In the exemplary embodiment of the present disclosure, it should be noted that the specific duration of the second time period may be set according to practical situations, may be set to be the same as the specific duration of the first time period, and may also be set to be different from the specific duration of the first time period, which all belong to the protection scope of the present disclosure.
In an exemplary embodiment of the present disclosure, referring to fig. 2, fig. 2 schematically illustrates a flowchart of a method for processing a pickup right of a service item in another exemplary embodiment of the present disclosure, specifically illustrating a relevant flowchart of a result generated by querying a right by a background server after generating a pickup right for a user, and the following explains a specific implementation manner with reference to fig. 2.
In step S201, the result of generating the pickup right is queried.
In an exemplary embodiment of the disclosure, after generating the pickup right for the user, the background server may query the generation result of the pickup right to determine whether the pickup right is successfully generated for the user.
In step S202, if the generation result is that the generation is successful, the second permission number corresponding to the pickup permission is sent to the client.
In an exemplary embodiment of the disclosure, if the generation result queried by the background server is successful, that is, the user has the second permission number, the second permission number may be sent to the client. Furthermore, the second authority number can be stored in the database, so that data loss is avoided, and the effect of permanently storing data is realized.
In step S203, if the generation result is a generation failure, a failure message is sent to the client.
In an exemplary embodiment of the present disclosure, if the query of the backend server generates a result that: if the generation of the pickup right fails, that is, the user still does not have the second right number, a failure message (indicating that the generation of the pickup right for the user fails) may be returned to the client.
In an exemplary embodiment of the present disclosure, the backend server may further obtain user usage information (i.e., the number of times the user uses the service item, the frequency of use, etc.), and referring to the related explanation of step S110, when the service item gives the user 10 times telemedicine services, the user usage information may be the number of times the user currently uses the service item, and further, the usage status of the service item may be updated in real time according to the user usage information. Illustratively, the usage status of a service item may be updated to "50% used already" when it is detected that the user has used 5 times. When it is detected that the user has used 8 times, the use status of the service item may be updated to "80% used already". Therefore, the technical problems of low efficiency and high error probability caused by manual statistics can be solved, the workload of related statistics personnel can be reduced, and the statistical efficiency can be improved.
In an exemplary embodiment of the present disclosure, fig. 3 schematically illustrates an overall flowchart of a method for processing a service item pickup permission in an exemplary embodiment of the present disclosure, and a specific implementation manner is explained below with reference to fig. 3.
In step S301, start;
in step S302, the client obtains portrait information of the user in response to a user getting a service item, and calls a background server;
in step S303, the background server queries whether the user has the right to receive based on the image information;
in step S304, the client starts a timeout mechanism to determine whether the background server is queried overtime;
in step S305, if the time is out (the client does not receive the query result of the pickup permission within the first time period), it is determined that the background server fails to query, and the procedure is ended;
in step S306, if not, determining whether the user has the picking right according to the query result;
in step S307, if the query result indicates that the user has the right to receive, the client receives the first right number sent by the background server, and ends the program;
in step S308, if the query result indicates that the user does not have the picking right, the client calls the background server again,
in step S309, the background server generates a pickup right for the user;
in step S310, the client starts the timeout mechanism again, and determines whether the background server generates an authority timeout;
in step S311, if the time is out (that is, the client does not receive the result of generating the pickup permission within the second time period), it is determined that the generation of the permission by the background server fails;
in step S312, if not, the background server queries whether the receiving right (whether the second right number is provided) is successfully generated;
in step S313, if yes, the generated second permission number is sent to the client and stored in the database;
in step S314, the call feedback result (second authority number) is fed back to the user.
In step S315, the process ends.
According to the method and the device, the relevant operations of the receiving authority are concentrated on the client side, the relevant operations of inquiring, generating and the like of the receiving authority are concentrated on the background server, so that a front-end service system and a rear-end qualification management system are separated and do professional matters respectively, the division of labor is clear, the flexibility of system butt joint is improved, the technical problems that one server in the prior art is overloaded and is tightly coupled with a program, and the receiving authority cannot be generated correctly are solved, and the generating accuracy and the generating efficiency of the receiving authority are improved.
The present disclosure further provides a device for processing the picking authority of a service item, which is applied to a client for processing the picking authority, and fig. 4 shows a schematic structural diagram of the device for processing the picking authority of the service item in an exemplary embodiment of the present disclosure; as shown in fig. 4, the apparatus 400 for processing the right to receive a service item may include a first calling module 401, a first determining module 402, and a second calling module 403. Wherein:
a first calling module 401, configured to respond to a user's operation of getting the service item, and obtain portrait information of the user; and calling a background server to inquire whether the user has the picking authority or not based on the portrait information.
In an exemplary embodiment of the disclosure, the first calling module is used for responding to a user's operation of getting a service item, and acquiring portrait information of the user; and calling a background server to inquire whether the user has the picking authority or not based on the image information.
A first determining module 402, configured to determine that the background server fails to query if a query result of the pickup permission is not received within a first time period.
In an exemplary embodiment of the disclosure, the first determination module is configured to determine that the background server query fails if a query result for the pickup permission is not received within a first time period.
In an exemplary embodiment of the disclosure, the first determining module is further configured to determine that the background server fails to generate the pickup right if the generation result of the pickup right is not received within the second time period.
A second calling module 403, configured to, if the received query result indicates that the user does not have the pickup permission, call the background server again, so that the background server generates the pickup permission for the user.
In an exemplary embodiment of the disclosure, the second invoking module is configured to invoke the background server again if the received query result indicates that the user does not have the getting right, so that the background server generates the getting right for the user.
In an exemplary embodiment of the disclosure, the second invoking module is further configured to receive the first permission number sent by the background server if the received query result indicates that the user has the right to receive.
The specific details of each module in the device for processing the picking permission of the service item have been described in detail in the method for processing the picking permission of the corresponding service item, and therefore are not described herein again.
The present disclosure further provides a device for processing the picking authority of a service item, which is applied to a background server for processing the picking authority, and fig. 5 shows a schematic structural diagram of the device for processing the picking authority of the service item in an exemplary embodiment of the present disclosure; as shown in fig. 5, the apparatus 500 for processing right to receive service item may include a right inquiry module 501, a transmission module 502, and a right generation module 503. Wherein:
and the permission query module 501 is configured to respond to a calling operation of the client, and query whether the user has the pickup permission based on the portrait information.
In an exemplary embodiment of the disclosure, the permission query module is configured to query whether the user has a right to receive based on the portrait information in response to a call operation of the client.
In an exemplary embodiment of the disclosure, the permission query module is further configured to query a generation result of the getting permission after the getting permission is generated for the user, and if the generation result is successful, send a second permission number corresponding to the getting permission to the client; and if the generation result is failure, sending a failure message to the client.
A sending module 502, configured to send the first permission number corresponding to the pickup permission to the client if the user has the pickup permission.
In an exemplary embodiment of the disclosure, the sending module is configured to send a first permission number corresponding to the fetching permission to the client if the user has the fetching permission.
And an authority generation module 503, configured to respond to a recall operation of the client if the user does not have the pickup authority, and generate the pickup authority for the user.
In an exemplary embodiment of the disclosure, the permission generation module is configured to generate the pickup permission for the user in response to a recall operation of the client if the user does not have the pickup permission.
In an exemplary embodiment of the disclosure, the permission generation module is further configured to save the second permission number to the database.
The specific details of each module in the device for processing the picking permission of the service item have been described in detail in the method for processing the picking permission of the corresponding service item, and therefore are not described herein again.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, there is also provided a computer storage medium capable of implementing the above method. On which a program product capable of implementing the above-described method of the present specification is stored. In some possible embodiments, various aspects of the disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to perform the steps according to various exemplary embodiments of the disclosure described in the "exemplary methods" section above of this specification, when the program product is run on the terminal device.
Referring to fig. 6, a program product 600 for implementing the above method according to an embodiment of the present disclosure is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
In addition, in an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.
As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, method or program product. Accordingly, various aspects of the present disclosure may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 700 according to this embodiment of the disclosure is described below with reference to fig. 7. The electronic device 700 shown in fig. 7 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 7, electronic device 700 is embodied in the form of a general purpose computing device. The components of the electronic device 700 may include, but are not limited to: the at least one processing unit 710, the at least one memory unit 720, and a bus 730 that couples various system components including the memory unit 720 and the processing unit 710.
Wherein the storage unit stores program code that is executable by the processing unit 710 to cause the processing unit 710 to perform steps according to various exemplary embodiments of the present disclosure as described in the above section "exemplary methods" of this specification. For example, the processing unit 710 may perform the following as shown in fig. 1: step S110, responding to the receiving operation of the user to the service item, and acquiring portrait information of the user; step S120, based on the portrait information, calling a background server to inquire whether the user has the picking authority; step S130, if the query result of the picking permission is not received in a first time period, judging that the background server fails to query; step S140, if the received query result indicates that the user does not have the getting right, the background server is called again to enable the background server to generate the getting right for the user.
The storage unit 720 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)7201 and/or a cache memory unit 7202, and may further include a read only memory unit (ROM) 7203.
The storage unit 720 may also include a program/utility 7204 having a set (at least one) of program modules 7205, such program modules 7205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 700 may also communicate with one or more external devices 800 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 700, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 700 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 750. Also, the electronic device 700 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the internet) via the network adapter 760. As shown, the network adapter 760 communicates with the other modules of the electronic device 700 via the bus 730. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
Furthermore, the above-described figures are merely schematic illustrations of processes included in methods according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (10)
1. A service item receiving authority processing method is applied to a client side which processes the receiving authority, and is characterized by comprising the following steps:
responding to the receiving operation of the user to the service item, and acquiring portrait information of the user;
based on the portrait information, calling a background server to inquire whether the user has the picking authority;
if the query result of the picking permission is not received in a first time period, judging that the background server fails to query;
if the received query result indicates that the user does not have the picking permission, the background server is called again so that the background server generates the picking permission for the user.
2. The method of claim 1, further comprising:
and if the generation result of the picking permission is not received in a second time period, judging that the background server fails to generate the picking permission.
3. The method according to claim 1 or 2, characterized in that the method further comprises:
and if the received query result indicates that the user has the picking permission, receiving a first permission number sent by the background server.
4. A service item receiving authority processing method is applied to a background server for processing the receiving authority, and is characterized by comprising the following steps:
responding to the calling operation of the client, and inquiring whether the user has the picking permission or not based on the portrait information;
if the user has the pickup permission, the first permission number corresponding to the pickup permission is sent to the client;
and if the user does not have the picking permission, responding to the recall operation of the client side, and generating the picking permission for the user.
5. The method of claim 4, wherein after generating the pickup rights for the user, the method further comprises:
inquiring the generation result of the receiving authority;
if the generation result is successful, sending a second permission number corresponding to the picking permission to the client;
and if the generation result is failure, sending a failure message to the client.
6. The method of claim 5, further comprising:
and storing the second authority number into a database.
7. A service item reception right processing device applied to a client for processing the reception right, the device is characterized by comprising:
the first calling module is used for responding to the receiving operation of the user on the service item and acquiring portrait information of the user; based on the portrait information, calling a background server to inquire whether the user has the picking authority;
the first judgment module is used for judging that the background server fails to inquire if the inquiry result of the picking permission is not received within a first time period;
and the second calling module is used for calling the background server again to enable the background server to generate the pickup permission for the user if the received query result indicates that the user does not have the pickup permission.
8. A service item receiving authority processing device is applied to a background server for processing the receiving authority, and is characterized by comprising:
the permission query module is used for responding to the calling operation of the client and querying whether the user has the picking permission or not based on the portrait information;
the sending module is used for sending the first permission number corresponding to the getting permission to the client if the user has the getting permission;
and the permission generation module is used for responding to the recall operation of the client and generating the pickup permission for the user if the user does not have the pickup permission.
9. A computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method of processing the right to receive for a service item of any one of claims 1 to 6.
10. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to execute the method for processing the right to receive of any one of claims 1 to 6 via executing the executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911170117.3A CN111145033A (en) | 2019-11-26 | 2019-11-26 | Service item receiving authority processing method and device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911170117.3A CN111145033A (en) | 2019-11-26 | 2019-11-26 | Service item receiving authority processing method and device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111145033A true CN111145033A (en) | 2020-05-12 |
Family
ID=70516673
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911170117.3A Pending CN111145033A (en) | 2019-11-26 | 2019-11-26 | Service item receiving authority processing method and device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111145033A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111681745A (en) * | 2020-05-28 | 2020-09-18 | 泰康保险集团股份有限公司 | Data processing method and device |
| CN112596818A (en) * | 2020-12-30 | 2021-04-02 | 上海众源网络有限公司 | Application program control method, system and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105046478A (en) * | 2015-06-18 | 2015-11-11 | 广州市百果园网络科技有限公司 | Method of processing article and system thereof |
| CN107342966A (en) * | 2016-04-29 | 2017-11-10 | 北京京东尚科信息技术有限公司 | Authority credentials distribution method and device |
| CN107590698A (en) * | 2017-09-19 | 2018-01-16 | 深圳市优户科技有限公司 | The management method and managing device of a kind of electronic coupons |
| CN110147664A (en) * | 2019-04-19 | 2019-08-20 | 深圳壹账通智能科技有限公司 | The method and relevant device of authentication based on centralization database |
| CN110209060A (en) * | 2019-05-23 | 2019-09-06 | 无锡小天鹅电器有限公司 | A kind of control method and device, equipment and computer storage medium |
-
2019
- 2019-11-26 CN CN201911170117.3A patent/CN111145033A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105046478A (en) * | 2015-06-18 | 2015-11-11 | 广州市百果园网络科技有限公司 | Method of processing article and system thereof |
| CN107342966A (en) * | 2016-04-29 | 2017-11-10 | 北京京东尚科信息技术有限公司 | Authority credentials distribution method and device |
| CN107590698A (en) * | 2017-09-19 | 2018-01-16 | 深圳市优户科技有限公司 | The management method and managing device of a kind of electronic coupons |
| CN110147664A (en) * | 2019-04-19 | 2019-08-20 | 深圳壹账通智能科技有限公司 | The method and relevant device of authentication based on centralization database |
| CN110209060A (en) * | 2019-05-23 | 2019-09-06 | 无锡小天鹅电器有限公司 | A kind of control method and device, equipment and computer storage medium |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111681745A (en) * | 2020-05-28 | 2020-09-18 | 泰康保险集团股份有限公司 | Data processing method and device |
| CN111681745B (en) * | 2020-05-28 | 2024-03-15 | 泰康保险集团股份有限公司 | Data processing method and device |
| CN112596818A (en) * | 2020-12-30 | 2021-04-02 | 上海众源网络有限公司 | Application program control method, system and device |
| CN112596818B (en) * | 2020-12-30 | 2023-12-05 | 上海众源网络有限公司 | Application program control method, system and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110135590B (en) | Information processing method, information processing apparatus, information processing medium, and electronic device | |
| CN111240940B (en) | Real-time service monitoring method and device, electronic equipment and storage medium | |
| CN111698319B (en) | Method, device and system for automatically popping screen when incoming call | |
| CN109951553B (en) | Data processing method, system, electronic device and computer readable storage medium | |
| CN113254969B (en) | Business data processing method and device, electronic equipment and storage medium | |
| CN112346794A (en) | Interface calling method, device, equipment and medium | |
| CN111145033A (en) | Service item receiving authority processing method and device and storage medium | |
| CN111586177B (en) | Cluster session loss prevention method and system | |
| CN111080390B (en) | Order information modification method, system, equipment and storage medium | |
| CN113220403A (en) | Method and device for h5 intercepting Android return event and electronic equipment | |
| US20190333013A1 (en) | Systems, devices, and methods for machine reading | |
| CN112491940A (en) | Request forwarding method and device of proxy server, storage medium and electronic equipment | |
| CN113535439B (en) | Service request processing method, device, equipment and storage medium | |
| CN111681032B (en) | Method and device for configuring additional resources and electronic equipment | |
| CN111680867B (en) | Resource allocation method and device and electronic equipment | |
| CN111061576A (en) | Method and system for creating entity object | |
| CN111680914B (en) | Event distribution method, event distribution device, storage medium, and electronic device | |
| CN109525630B (en) | Method, apparatus, medium, and electronic device for transmitting data analysis request | |
| CN111506567B (en) | Cross-database cleaning method and device for data, computer equipment and medium | |
| CN111831274B (en) | Metadata analysis engine configuration system, method, terminal and readable storage medium | |
| JP2012128581A (en) | Communication code generation apparatus, function utilization computer, function disclosure computer, computer system, communication code generation method and program | |
| US20220129332A1 (en) | Handling of Metadata for Microservices Processing | |
| US20230195504A1 (en) | Systems and methods for resolving interdependencies between user interfaces in a domain driven design microservice architecture | |
| CN109471849B (en) | Model processing method and device, storage medium and electronic equipment | |
| CN111784482A (en) | Order processing method and device, computer readable storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |