CN114240682A - Request response method and device, electronic equipment and storage medium - Google Patents
Request response method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114240682A CN114240682A CN202210172377.XA CN202210172377A CN114240682A CN 114240682 A CN114240682 A CN 114240682A CN 202210172377 A CN202210172377 A CN 202210172377A CN 114240682 A CN114240682 A CN 114240682A
- Authority
- CN
- China
- Prior art keywords
- event
- server
- target
- request
- information
- 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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/01—Customer relationship services
- G06Q30/015—Providing customer assistance, e.g. assisting a customer within a business location or via helpdesk
- G06Q30/016—After-sales
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Technology Law (AREA)
- Computational Linguistics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a request response method, a request response device, electronic equipment and a storage medium, which are applied to a first server, wherein the method comprises the following steps: acquiring a relation release request sent by a client corresponding to a target user; acquiring an associated event set corresponding to a target user from a local database according to the identification information of the target user; determining whether the associated event set contains a first target event, and if so, acquiring an expiration time t2 corresponding to the first target event; in the case that the request issuing time is earlier than the deadline, deleting the first target event from the associated event set; acquiring f (N1, t2-t1), and sending a query request to the second server; acquiring N4= N1-k f (N1, t2-t1), wherein k is a preset parameter in the event information; generating first indication information and sending the first indication information to a third server; the first instruction information includes N4, and the first instruction information is used to instruct the third server to process the second attribute corresponding to the target user according to N4, and the second attribute is stored in the third server.
Description
Technical Field
The invention relates to the field of aviation ticket refunding, in particular to a request response method, a request response device, electronic equipment and a storage medium.
Background
After the user has purchased the ticket, can apply for the operation of refunding the ticket or changing the sign when the journey has changed, the change process can produce the commission, and the user if having purchased refunding and changing the sign insurance, when the ticket takes place to refund or changes the sign, can obtain insurance company's certain compensation, the loss that can effectual reduction journey change is showing and is improving passenger's trip experience.
However, the conventional compensation method is that after the user finishes the ticket refund or the ticket change and is charged with the commission fee, the related materials are actively submitted to the underwriting party for compensation processing. The method requires the user to actively operate the operation, and is tedious.
Disclosure of Invention
In view of the above, the present invention provides a request response method, apparatus, electronic device and storage medium, which at least partially solve the problems in the prior art.
According to one aspect of the present application, there is provided a request response method applied to a first server, including:
step S100, obtaining a relation release request sent by a client corresponding to a target user; the relation release request is used for indicating the first server to release the incidence relation between the target user and the first target event; the relation release request comprises target user identification information, first target event identification information and request sending time t 1;
step S200, acquiring a correlated event set corresponding to the target user from a local database according to the identification information of the target user;
step S300, determining whether the associated event set is an empty set, if not, executing step S400;
step S400, determining whether the associated event set contains the first target event or not according to the first target event identification information, and if so, executing step S500;
step S500, obtaining an expiration time t2 corresponding to the first target event;
step S600, deleting the first target event from the associated event set under the condition that the request sending time is earlier than the deadline;
step S700, f (N1, t2-t1) is obtained, wherein N1 is a first attribute which corresponds to the first target event and is stored in a local database; f () is a preset processing function stored in the configuration file;
step S800, sending a query request to a second server; the query request is used for indicating the second server to return event information corresponding to a second target event under the condition that the target user and the second target event have an incidence relation; the second target event has an incidence relation with the first target event; if the event information is received within the set time interval, step S810 is performed;
the step S810 includes:
step S811, obtaining N4= N1-k × f (N1, t2-t1), where k is a preset parameter in the event information, and a value range of k is 0 to 1;
step S812, generating first indication information and sending the first indication information to a third server; the first indication information includes N4, and the first indication information is used for indicating the third server to process a second attribute corresponding to the target user according to the N4, wherein the second attribute is stored in the third server.
In an exemplary embodiment of the present application, if the event information is not received within a set time interval, step S820 is performed;
the step S820 includes:
step S821, acquiring acquisition N5= N1-f (N1, t2-t 1);
step S822, generating second indication information and sending the second indication information to a third server; the second indication information includes N5, and the second indication information is used for indicating the third server to process a second attribute corresponding to the target user according to the N5, and the second attribute is stored in the third server.
In an exemplary embodiment of the present application, the step S300 further includes:
and if the associated event set is an empty set, returning request failure information to the client.
In an exemplary embodiment of the present application, the step S400 further includes:
and if the correlated event set does not contain the first target event, returning request failure information to the client.
In an exemplary embodiment of the present application, after the step S810 or the step S820, the method further includes:
returning request success information to the client, the request success information including N4 or N5.
In an exemplary embodiment of the present application, after the step S812, the step 810 further includes:
and sending notification information to the second server, wherein the notification information contains N4.
In an exemplary embodiment of the present application, k has a value ranging from 0 to 0.5.
According to an aspect of the present application, there is provided a request response apparatus disposed in a first server, including:
the first acquisition module is used for acquiring a relation release request sent by a client corresponding to a target user; the relation release request is used for indicating the first server to release the incidence relation between the target user and the first target event; the relation release request comprises target user identification information, first target event identification information and request sending time t 1;
the second acquisition module is used for acquiring the associated event set corresponding to the target user from a local database according to the identification information of the target user;
the first judgment module is used for determining whether the associated event set is an empty set or not, and if not, entering the second judgment module;
the second judging module is used for determining whether the associated event set contains the first target event or not according to the identification information of the first target event, and if so, entering a third acquiring module;
a third obtaining module, configured to obtain an expiration time t2 corresponding to the first target event;
a first processing module, configured to delete the first target event from the associated event set if the request issuance time is earlier than the deadline;
a second processing module, configured to obtain f (N1, t2-t1), where N1 is a first attribute that corresponds to the first target event and is stored in a local database; f () is a preset processing function stored in the configuration file;
the request sending module is used for sending a query request to the second server; the query request is used for indicating the second server to return event information corresponding to a second target event under the condition that the target user and the second target event have an incidence relation; the second target event has an incidence relation with the first target event; if the event information is received within a set time interval, entering an indication sending module;
the indication sending module is configured to obtain N4= N1-k × f (N1, t2-t1), where k is a preset parameter in the event information, and a value range of k is 0 to 1; generating first indication information and sending the first indication information to a third server; the first indication information includes N4, and the first indication information is used for indicating the third server to process a second attribute corresponding to the target user according to the N4, wherein the second attribute is stored in the third server.
According to one aspect of the present application, there is provided a computer program product comprising a processor and a memory;
the processor is configured to perform the steps of any of the above methods by calling a program or instructions stored in the memory.
According to an aspect of the application, there is provided a computer-readable storage medium storing a program or instructions for causing a computer to perform the steps of any of the methods described above.
According to the response request method, after the target user sends the relation release request, whether the target user meets the limitation condition of releasing the relation with the first target event (such as air ticket ordering) can be automatically judged. And automatically releasing the association relation between the target user and the first target event under the condition that the condition is met. Meanwhile, after the association relationship is released, whether the target user has an associated second target event (such as the purchase of a refund or a change of ticket) is determined by sending a query request to the second server. In the case of the second target event having an association, the method provided by the application processes the obtained N4 according to the relevant parameters of the first target event and the second target event, and sends the first indication information containing N4 to the third server, so as to complete automatic processing (insurance compensation) on the second target event. The target user does not need to additionally perform other operations, so that the operation cost of the target user is reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart of a request response method provided in this embodiment.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
It should be noted that, in the case of no conflict, the features in the following embodiments and examples may be combined with each other; moreover, all other embodiments that can be derived by one of ordinary skill in the art from the embodiments disclosed herein without making any creative effort fall within the scope of the present disclosure.
It is noted that various aspects of the embodiments are described below within the scope of the appended claims. It should be apparent that the aspects described herein may be embodied in a wide variety of forms and that any specific structure and/or function described herein is merely illustrative. Based on the disclosure, one skilled in the art should appreciate that one aspect described herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented and/or a method practiced using any number of the aspects set forth herein. Additionally, such an apparatus may be implemented and/or such a method may be practiced using other structure and/or functionality in addition to one or more of the aspects set forth herein.
Referring to fig. 1, according to an aspect of the present application, there is provided a request response method applied to a first server, including:
step S100, obtaining a relation release request sent by a client corresponding to a target user; the relation release request is used for indicating the first server to release the incidence relation between the target user and the first target event; the relation release request comprises target user identification information, first target event identification information and request sending time t 1; the first target event may be order information for purchasing an air ticket or other items, and the like. Disassociating may be understood as the performance of a refund or change of sign, etc. The target user identification information may be information having identification such as an ID of the target user. The first target event identification information may be information such as an order number, and the request sending time t1 is the system time corresponding to the click of the "ticket refund" or "confirm" button when the target user performs the ticket refund operation on the client.
And step S200, acquiring the associated event set corresponding to the target user from a local database according to the identification information of the target user. The correlated events in the set of correlated events may be characterized as successful ticket purchases by the target user, or the like.
Step S300, determining whether the associated event set is an empty set, if not, executing step S400; the associated set is an empty set, indicating that the target user has not purchased an airline ticket, etc.
Step S400, determining whether the associated event set includes the first target event according to the first target event identification information, and if so, executing step S500.
Step S500, obtaining an expiration time t2 corresponding to the first target event; the expiration time t2 may be predetermined in advance and may be stored in the local database in response to the first target event.
Step S600, deleting the first target event from the associated event set when the request issue time is earlier than the deadline. And deleting the first target event (the correlated event corresponding to the first target event in the correlated event set) from the correlated events, namely, the target user and the first target event are disassociated.
Step S700, f (N1, t2-t1) is obtained, wherein N1 is a first attribute (such as the actual price of the ticket corresponding to the first target event purchased by the target user) corresponding to the first target event and stored in a local database; f () is a preset processing function stored in the configuration file. The interval between the request issuing time t1 and the deadline t2 when the target user issues the relationship release request, and the first attribute are input into the process f (), and the commission fee corresponding to the release relationship is obtained.
Step S800, sending a query request to a second server; the query request is used for indicating the second server to return event information corresponding to a second target event (such as purchase of a refund insurance or change of an insurance) under the condition that the target user has an association relationship with the second target event; the second target event has an incidence relation with the first target event; if the event information is received within the set time interval, step S810 is performed; the event information may be the specific content of the refund or change sign insurance, the number reduction condition, the compensation method, or the like.
The step S810 includes:
step S811, obtaining N4= N1-k × f (N1, t2-t1), where k is a preset parameter (such as an indemnity ratio) in the event information, and a value range of k is 0 to 1, and more preferably, a value range of k is 0 to 0.5; n4 represents a refund from the target user disassociating from the first target event, including an actual refund and an indemnity.
Step S812, generating first indication information and sending the first indication information to a third server; the first indication information includes N4, and the first indication information is used for indicating the third server to process a second attribute corresponding to the target user according to the N4, wherein the second attribute is stored in the third server.
The third server may be a server of the fund management account corresponding to the first server and/or the target user, and the processing of the account balance corresponding to the first server or the target user is completed.
According to the response request method, after the target user sends the relation release request, whether the target user meets the limitation condition of releasing the relation with the first target event (such as air ticket ordering) can be automatically judged. And automatically releasing the association relation between the target user and the first target event under the condition that the condition is met. Meanwhile, after the association relationship is released, whether the target user has an associated second target event (such as the purchase of a refund or a change of ticket) is determined by sending a query request to the second server. In the case of the second target event having an association, the method provided by the application processes the obtained N4 according to the relevant parameters of the first target event and the second target event, and sends the first indication information containing N4 to the third server, so as to complete automatic processing (insurance compensation) on the second target event. The actual refund and the compensation of the refund or the change of the ticket are directly processed in a one-time processing mode, the target user does not need to additionally perform other operations, and the operation cost of the target user is reduced.
In an exemplary embodiment of the present application, if the event information is not received within a set time interval, step S820 is performed;
the step S820 includes:
step S821, acquiring acquisition N5= N1-f (N1, t2-t 1);
step S822, generating second indication information and sending the second indication information to a third server; the second indication information includes N5, and the second indication information is used for indicating the third server to process a second attribute corresponding to the target user according to the N5, and the second attribute is stored in the third server.
If the event information is not received within the set time interval, the target user does not have a related second target event, at this time, the related processing of the second target event is not needed, but the N5 is directly acquired, the second indication information is sent to the third server, and the corresponding processing of the account balance is completed.
In an exemplary embodiment of the present application, the step S300 further includes:
and if the associated event set is an empty set, returning request failure information to the client.
And if the associated event set is an empty set, indicating that the target user and the first target event do not have an association relationship.
In this embodiment, the request failure information is used to inform that the target user fails to release the association relationship, and the target user does not have an association relationship with the first target event.
In an exemplary embodiment of the present application, the step S400 further includes:
and if the correlated event set does not contain the first target event, returning request failure information to the client.
If the associated event set does not contain the first target event, it indicates that the target user and the first target event do not have an association relationship.
In this embodiment, the request failure information is used to inform that the target user fails to release the association relationship, and the target user does not have an association relationship with the first target event.
In an exemplary embodiment of the present application, after the step S810 or the step S820, the method further includes:
returning request success information to the client, the request success information including N4 or N5.
The request success information is used for informing the target user that the association relation is successfully removed and the final refund generated after the association relation is removed is what.
In an exemplary embodiment of the present application, after the step S812, the step 810 further includes:
and sending notification information to the second server, wherein the notification information contains N4.
The notification information is used to notify the second server of the processing result for the second target event and the corresponding money amount information (N4).
According to an aspect of the present application, there is provided a request response apparatus disposed in a first server, including:
the first acquisition module is used for acquiring a relation release request sent by a client corresponding to a target user; the relation release request is used for indicating the first server to release the incidence relation between the target user and the first target event; the relation release request comprises target user identification information, first target event identification information and request sending time t 1;
the second acquisition module is used for acquiring the associated event set corresponding to the target user from a local database according to the identification information of the target user;
the first judgment module is used for determining whether the associated event set is an empty set or not, and if not, entering the second judgment module;
the second judging module is used for determining whether the associated event set contains the first target event or not according to the identification information of the first target event, and if so, entering a third acquiring module;
a third obtaining module, configured to obtain an expiration time t2 corresponding to the first target event;
a first processing module, configured to delete the first target event from the associated event set if the request issuance time is earlier than the deadline;
a second processing module, configured to obtain f (N1, t2-t1), where N1 is a first attribute that corresponds to the first target event and is stored in a local database; f () is a preset processing function stored in the configuration file;
the request sending module is used for sending a query request to the second server; the query request is used for indicating the second server to return event information corresponding to a second target event under the condition that the target user and the second target event have an incidence relation; the second target event has an incidence relation with the first target event; if the event information is received within a set time interval, entering an indication sending module;
the indication sending module is configured to obtain N4= N1-k × f (N1, t2-t1), where k is a preset parameter in the event information, and a value range of k is 0 to 1; generating first indication information and sending the first indication information to a third server; the first indication information includes N4, and the first indication information is used for indicating the third server to process a second attribute corresponding to the target user according to the N4, wherein the second attribute is stored in the third server.
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, 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 invention may be embodied as a system, method or program product. Thus, various aspects of the invention 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 according to this embodiment of the invention. The electronic device is only an example and should not bring any limitation to the function and the scope of use of the embodiments of the present invention.
The electronic device is in the form of a general purpose computing device. Components of the electronic device may include, but are not limited to: the at least one processor, the at least one memory, and a bus connecting the various system components (including the memory and the processor).
Wherein the storage stores program code executable by the processor to cause the processor to perform steps according to various exemplary embodiments of the present invention as described in the "exemplary methods" section above.
The memory may include readable media in the form of volatile memory, such as Random Access Memory (RAM) and/or cache memory, and may further include Read Only Memory (ROM).
The storage may also include a program/utility having a set (at least one) of program modules 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 bus may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures.
The electronic device may also communicate with one or more external devices (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface. Also, the electronic device 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 a network adapter. As shown, the network adapter communicates with other modules of the electronic device over a bus. 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, including but not limited to: microcode, device drivers, redundant processors, 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.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal 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 aspects of the present invention 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).
Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, 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.
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.
The above description is only for the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A request response method is applied to a first server and is characterized by comprising the following steps:
step S100, obtaining a relation release request sent by a client corresponding to a target user; the relation release request is used for indicating the first server to release the incidence relation between the target user and the first target event; the relation release request comprises target user identification information, first target event identification information and request sending time t 1;
step S200, acquiring a correlated event set corresponding to the target user from a local database according to the identification information of the target user;
step S300, determining whether the associated event set is an empty set, if not, executing step S400;
step S400, determining whether the associated event set contains the first target event or not according to the first target event identification information, and if so, executing step S500;
step S500, obtaining an expiration time t2 corresponding to the first target event;
step S600, deleting the first target event from the associated event set under the condition that the request sending time is earlier than the deadline;
step S700, f (N1, t2-t1) is obtained, wherein N1 is a first attribute which corresponds to the first target event and is stored in a local database; f () is a preset processing function stored in the configuration file;
step S800, sending a query request to a second server; the query request is used for indicating the second server to return event information corresponding to a second target event under the condition that the target user and the second target event have an incidence relation; the second target event has an incidence relation with the first target event; if the event information is received within the set time interval, step S810 is performed;
the step S810 includes:
step S811, obtaining N4= N1-k × f (N1, t2-t1), where k is a preset parameter in the event information, and a value range of k is 0 to 1;
step S812, generating first indication information and sending the first indication information to a third server; the first indication information includes N4, and the first indication information is used for indicating the third server to process a second attribute corresponding to the target user according to the N4, wherein the second attribute is stored in the third server.
2. The method according to claim 1, wherein if the event information is not received within a predetermined time interval, step S820 is performed;
the step S820 includes:
step S821, acquiring acquisition N5= N1-f (N1, t2-t 1);
step S822, generating second indication information and sending the second indication information to a third server; the second indication information includes N5, and the second indication information is used for indicating the third server to process a second attribute corresponding to the target user according to the N5, and the second attribute is stored in the third server.
3. The request response method according to claim 1, wherein the step S300 further comprises:
and if the associated event set is an empty set, returning request failure information to the client.
4. The request response method according to claim 1, wherein the step S400 further comprises:
and if the correlated event set does not contain the first target event, returning request failure information to the client.
5. The request response method according to claim 2, wherein after the step S810 or the step S820, the method further comprises:
returning request success information to the client, the request success information including N4 or N5.
6. The request response method according to claim 1, wherein after the step S812, the step 810 further comprises:
and sending notification information to the second server, wherein the notification information contains N4.
7. The request response method of claim 1, wherein k has a value ranging from 0 to 0.5.
8. A request responding apparatus disposed in a first server, comprising:
the first acquisition module is used for acquiring a relation release request sent by a client corresponding to a target user; the relation release request is used for indicating the first server to release the incidence relation between the target user and the first target event; the relation release request comprises target user identification information, first target event identification information and request sending time t 1;
the second acquisition module is used for acquiring the associated event set corresponding to the target user from a local database according to the identification information of the target user;
the first judgment module is used for determining whether the associated event set is an empty set or not, and if not, entering the second judgment module;
the second judging module is used for determining whether the associated event set contains the first target event or not according to the identification information of the first target event, and if so, entering a third acquiring module;
a third obtaining module, configured to obtain an expiration time t2 corresponding to the first target event;
a first processing module, configured to delete the first target event from the associated event set if the request issuance time is earlier than the deadline;
a second processing module, configured to obtain f (N1, t2-t1), where N1 is a first attribute that corresponds to the first target event and is stored in a local database; f () is a preset processing function stored in the configuration file;
the request sending module is used for sending a query request to the second server; the query request is used for indicating the second server to return event information corresponding to a second target event under the condition that the target user and the second target event have an incidence relation; the second target event has an incidence relation with the first target event; if the event information is received within a set time interval, entering an indication sending module;
the indication sending module is configured to obtain N4= N1-k × f (N1, t2-t1), where k is a preset parameter in the event information, and a value range of k is 0 to 1; generating first indication information and sending the first indication information to a third server; the first indication information includes N4, and the first indication information is used for indicating the third server to process a second attribute corresponding to the target user according to the N4, wherein the second attribute is stored in the third server.
9. An electronic device comprising a processor and a memory;
the processor is adapted to perform the steps of the method of any one of claims 1 to 7 by calling a program or instructions stored in the memory.
10. A computer-readable storage medium, characterized in that it stores a program or instructions for causing a computer to carry out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210172377.XA CN114240682A (en) | 2022-02-24 | 2022-02-24 | Request response method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210172377.XA CN114240682A (en) | 2022-02-24 | 2022-02-24 | Request response method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114240682A true CN114240682A (en) | 2022-03-25 |
Family
ID=80748094
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210172377.XA Pending CN114240682A (en) | 2022-02-24 | 2022-02-24 | Request response method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114240682A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115134173A (en) * | 2022-08-31 | 2022-09-30 | 中航信移动科技有限公司 | Request response method for determining user authority |
| CN115203172A (en) * | 2022-06-30 | 2022-10-18 | 北京亚控科技发展有限公司 | Model construction method, model data subscription method, model construction device, model data subscription device, electronic equipment and medium |
| CN115239349A (en) * | 2022-09-22 | 2022-10-25 | 中航信移动科技有限公司 | Civil aviation event processing system based on digital currency |
| WO2023240993A1 (en) * | 2022-06-14 | 2023-12-21 | Oppo广东移动通信有限公司 | Abnormal positioning solving method and related apparatus |
| CN117332160A (en) * | 2023-12-01 | 2024-01-02 | 中航信移动科技有限公司 | Multi-target identification display method, storage medium and electronic equipment |
| CN117331722B (en) * | 2023-12-01 | 2024-03-15 | 中航信移动科技有限公司 | Multi-input event information processing system |
| CN117726148A (en) * | 2024-02-08 | 2024-03-19 | 中航信移动科技有限公司 | Method for determining adaptation degree of server, electronic equipment and storage medium |
| CN118069674A (en) * | 2024-04-22 | 2024-05-24 | 中航信移动科技有限公司 | Data calling method and device based on multiple data sources, medium and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109191311A (en) * | 2018-08-01 | 2019-01-11 | 平安科技（深圳）有限公司 | Delayed processing method, device, computer equipment and storage medium |
| CN109409856A (en) * | 2017-08-18 | 2019-03-01 | 阿里巴巴集团控股有限公司 | Reimbursement information processing method and device |
| CN110348858A (en) * | 2019-02-01 | 2019-10-18 | 北京三快在线科技有限公司 | Product data processing method and processing device, electronic equipment |
| CN111784292A (en) * | 2020-06-30 | 2020-10-16 | 中国民航信息网络股份有限公司 | Electronic passenger ticket refunding method and device, airline department system and payment system |
| CN113487338A (en) * | 2021-07-26 | 2021-10-08 | 携程商旅信息服务（上海）有限公司 | Ticket refunding processing method and system, electronic equipment and storage medium |
-
2022
- 2022-02-24 CN CN202210172377.XA patent/CN114240682A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109409856A (en) * | 2017-08-18 | 2019-03-01 | 阿里巴巴集团控股有限公司 | Reimbursement information processing method and device |
| CN109191311A (en) * | 2018-08-01 | 2019-01-11 | 平安科技（深圳）有限公司 | Delayed processing method, device, computer equipment and storage medium |
| CN110348858A (en) * | 2019-02-01 | 2019-10-18 | 北京三快在线科技有限公司 | Product data processing method and processing device, electronic equipment |
| CN111784292A (en) * | 2020-06-30 | 2020-10-16 | 中国民航信息网络股份有限公司 | Electronic passenger ticket refunding method and device, airline department system and payment system |
| CN113487338A (en) * | 2021-07-26 | 2021-10-08 | 携程商旅信息服务（上海）有限公司 | Ticket refunding processing method and system, electronic equipment and storage medium |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023240993A1 (en) * | 2022-06-14 | 2023-12-21 | Oppo广东移动通信有限公司 | Abnormal positioning solving method and related apparatus |
| CN115203172B (en) * | 2022-06-30 | 2023-11-07 | 北京亚控科技发展有限公司 | Model construction and model data subscription method and device, electronic equipment and medium |
| CN115203172A (en) * | 2022-06-30 | 2022-10-18 | 北京亚控科技发展有限公司 | Model construction method, model data subscription method, model construction device, model data subscription device, electronic equipment and medium |
| CN115134173B (en) * | 2022-08-31 | 2022-11-04 | 中航信移动科技有限公司 | Request response method for determining user permission |
| CN115134173A (en) * | 2022-08-31 | 2022-09-30 | 中航信移动科技有限公司 | Request response method for determining user authority |
| CN115239349B (en) * | 2022-09-22 | 2022-12-09 | 中航信移动科技有限公司 | Civil aviation event processing system based on digital currency |
| CN115239349A (en) * | 2022-09-22 | 2022-10-25 | 中航信移动科技有限公司 | Civil aviation event processing system based on digital currency |
| CN117332160A (en) * | 2023-12-01 | 2024-01-02 | 中航信移动科技有限公司 | Multi-target identification display method, storage medium and electronic equipment |
| CN117332160B (en) * | 2023-12-01 | 2024-02-09 | 中航信移动科技有限公司 | Multi-target identification display method, storage medium and electronic equipment |
| CN117331722B (en) * | 2023-12-01 | 2024-03-15 | 中航信移动科技有限公司 | Multi-input event information processing system |
| CN117726148A (en) * | 2024-02-08 | 2024-03-19 | 中航信移动科技有限公司 | Method for determining adaptation degree of server, electronic equipment and storage medium |
| CN117726148B (en) * | 2024-02-08 | 2024-04-26 | 中航信移动科技有限公司 | Method for determining adaptation degree of server, electronic equipment and storage medium |
| CN118069674A (en) * | 2024-04-22 | 2024-05-24 | 中航信移动科技有限公司 | Data calling method and device based on multiple data sources, medium and electronic equipment |
| CN118069674B (en) * | 2024-04-22 | 2024-07-12 | 中航信移动科技有限公司 | Data calling method and device based on multiple data sources, medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114240682A (en) | Request response method and device, electronic equipment and storage medium | |
| CN111598538A (en) | Payment method, system, equipment and storage medium for over-standard business travel orders | |
| CN112308552A (en) | Ordering method and device for medical insurance medicines | |
| CN111028074A (en) | Overdue bill updating and inquiring method, system, server and storage medium | |
| CN113919918A (en) | Order full-flow canceling method and device, electronic equipment and computer storage medium | |
| CN115456227B (en) | Digital currency system for civil aviation event | |
| CN111429074A (en) | Warehouse-out control method, device and system | |
| CN111027977A (en) | Data verification method and device and electronic equipment | |
| US20170249637A1 (en) | Online transaction processing system for transactions including multiple product suppliers | |
| CN115239348B (en) | Digital currency system for processing joint association request | |
| CN112418765A (en) | Logistics order cancellation confirmation method and device | |
| CN113988964A (en) | Air ticket monitoring method, system, electronic equipment and storage medium | |
| CN111553547B (en) | Control method, device, equipment and storage medium for task production | |
| CN114881270A (en) | Method and device for booking business travel ticket, electronic equipment and storage medium | |
| CN115249159B (en) | Event processing system based on digital currency | |
| CN115271732B (en) | Event processing system for controlling digital currency | |
| CN110888917A (en) | Batch running task execution method, device, server and storage medium | |
| CN111415263A (en) | Data matching method and device | |
| CN115456621B (en) | Digital currency processing system | |
| CN113763094A (en) | Service information processing method, device, server, medium and system | |
| CN115239349B (en) | Civil aviation event processing system based on digital currency | |
| CN115239318B (en) | Event processing system for civil aviation insurance | |
| CN115456802B (en) | Insurance event processing system based on digital currency | |
| CN112308661B (en) | Order processing method and device | |
| CN117332160B (en) | Multi-target identification display method, 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220325 |