CN111144777B - Resource transfer method, device, electronic equipment and storage medium - Google Patents

Resource transfer method, device, electronic equipment and storage medium Download PDF

Info

Publication number
CN111144777B
CN111144777B CN201911399459.2A CN201911399459A CN111144777B CN 111144777 B CN111144777 B CN 111144777B CN 201911399459 A CN201911399459 A CN 201911399459A CN 111144777 B CN111144777 B CN 111144777B
Authority
CN
China
Prior art keywords
target service
service
transferable
resource transfer
condition
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.)
Active
Application number
CN201911399459.2A
Other languages
Chinese (zh)
Other versions
CN111144777A (en
Inventor
刘爽
王谨平
尹航
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Sankuai Online Technology Co Ltd
Qiandai Beijing Information Technology Co Ltd
Original Assignee
Beijing Sankuai Online Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Sankuai Online Technology Co Ltd filed Critical Beijing Sankuai Online Technology Co Ltd
Priority to CN201911399459.2A priority Critical patent/CN111144777B/en
Publication of CN111144777A publication Critical patent/CN111144777A/en
Application granted granted Critical
Publication of CN111144777B publication Critical patent/CN111144777B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063Operations research, analysis or management
    • G06Q10/0631Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06312Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12Accounting
    • G06Q40/125Finance or payroll

Abstract

The embodiment of the application provides a resource transfer method, a resource transfer device, electronic equipment and a storage medium. The method comprises the following steps: receiving a resource transfer request corresponding to a target service, which is sent by a terminal, wherein the resource transfer request carries a service identifier of the target service; determining an expected transfer state corresponding to the service identifier, wherein the expected transfer state is used for indicating whether the resource transfer process of the target service is allowed to be completed or not; in response to the expected transfer state of the target service being non-transferable, determining the resource transfer state of the target service as an accepted state; and under the condition that the expected transfer state of the target service is switched from the non-transferable state to the transferable state, completing the resource transfer process of the target service. The technical scheme provided by the embodiment of the application can avoid the occurrence of the situation that financial staff need to repeatedly trigger the resource transfer request when the resource transfer fails in the related technology, reduce the operation required by the resource transfer and improve the resource transfer efficiency.

Description

Resource transfer method, device, electronic equipment and storage medium
Technical Field
The embodiment of the application relates to the technical field of online payment, in particular to a resource transfer method, a resource transfer device, electronic equipment and a storage medium.
Background
At present, all industries can realize online settlement, namely, a service settlement system is used for settling accounts to be paid of all services to accounts of suppliers.
In the related art, a related person triggers a terminal to send a resource transfer request to a resource transfer system, and then the resource transfer system pays from a bank account of the company to a provider account according to the resource transfer request. When the balance of the bank account of the company is insufficient and the resource transfer cannot be completed, the resource transfer system can directly return a settlement failure prompt to the terminal. At this time, the relevant personnel need to re-trigger the resource transfer request until the resource transfer is completed.
In the related art, when the resource transfer fails, the resource transfer request needs to be repeatedly created, the process is complicated, and the settlement efficiency is low.
Disclosure of Invention
The embodiment of the application provides a resource transfer method, a resource transfer device, an electronic device and a storage medium, which can be used for solving the problem that resource transfer requests need to be repeatedly created during resource transfer in the related art and improving settlement efficiency. The technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a resource transfer method, where the method includes:
receiving a resource transfer request corresponding to a target service, which is sent by a terminal, wherein the resource transfer request carries a service identifier of the target service;
determining an expected transfer state corresponding to the service identifier, wherein the expected transfer state is used for indicating whether to allow the resource transfer process of the target service to be completed;
in response to the expected transfer state of the target service being non-transferable, determining the resource transfer state of the target service as an accepted state;
and under the condition that the expected transfer state of the target service is switched from the non-transferable state to the transferable state, completing the resource transfer process of the target service.
In a second aspect, an embodiment of the present application provides a resource transfer apparatus, where the apparatus includes:
a request receiving module, configured to receive a resource transfer request corresponding to a target service, where the resource transfer request carries a service identifier of the target service;
a first determining module, configured to determine an expected transfer state corresponding to the service identifier, where the expected transfer state is used to indicate whether to allow a resource transfer process of the target service to be completed;
a second determining module, configured to determine, in response to that the expected transfer state of the target service is non-transferable, a resource transfer state of the target service as an accepted state;
and the resource transfer module is used for completing the resource transfer process of the target service under the condition that the expected transfer state of the target service is switched from the non-transferable state to the transferable state.
In a third aspect, an embodiment of the present application provides an electronic device, where the electronic device includes a processor and a memory, where the memory stores at least one instruction, and the instruction is loaded and executed by the processor to implement the resource transfer method according to the first aspect.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where at least one instruction is stored, and the instruction is loaded and executed by a processor to implement the resource transfer method according to the first aspect.
The beneficial effects brought by the technical scheme provided by the embodiment of the application at least comprise:
when the expected transfer state of a certain service is determined to be non-transferable, the service is set to be in the accepted state, then whether the expected transfer state of the service is switched from the non-transferable state to the transferred state is continuously monitored, and when the expected transfer state of the service is monitored to be switched from the non-transferable state to the transferred state, the resource transfer process of the service is completed, so that the situation that financial staff need to repeatedly trigger resource transfer requests when the resource transfer fails in the related technology can be avoided, the operation required by the resource transfer is reduced, and the resource transfer efficiency is improved.
Drawings
FIG. 1 is a schematic illustration of an implementation environment provided by an embodiment of the present application;
FIG. 2 is a flow diagram of a resource transfer method provided by an embodiment of the present application;
FIG. 3 is a flowchart of a resource transfer method according to an embodiment of the present application;
FIG. 4 is a flow chart of a resource transfer method provided by another embodiment of the present application;
FIG. 5 is a block diagram of a resource transfer apparatus according to an embodiment of the present application;
fig. 6 is a block diagram of an electronic device provided by an embodiment of the application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, the following detailed description of the embodiments of the present application will be made with reference to the accompanying drawings.
Please refer to fig. 1, which illustrates a schematic diagram of an implementation environment provided by an embodiment of the present application. The implementation environment includes a server 10 and a terminal 20.
The server 10 has a resource transfer function. In the embodiment of the present application, the server 10 is used to transfer the resources required to settle the service to the provider account. The server 10 also has a data interaction function. Specifically, the server 10 may be configured to receive a resource transfer request sent by the terminal 20. Optionally, the server 10 also has a data storage function, for example, storing configuration data such as a non-transferable condition.
The server 10 may be one server, a server cluster composed of multiple servers, or a cloud computing service center. When the server 10 is a cluster architecture, it may include a transfer server, an interaction server, and a storage server. The transfer server is used for realizing the resource transfer function, the interaction server is used for realizing the data interaction function, and the storage server is used for storing the configuration data.
The terminal 20 has a data interaction function, such as sending a resource transfer request to the server 10. The terminal 20 may be a Personal Computer (PC), a smart phone, a tablet, a smart wearable device, or the like.
Alternatively, the terminal 20 and the server 10 establish a communication connection through a wireless network or a wired network.
Optionally, the wireless or wired networks described above use standard communication techniques and/or protocols. The Network is typically the internet, but may be any other Network including, but not limited to, a Local Area Network (LAN), a Metropolitan Area Network (MAN), a Wide Area Network (WAN), a mobile, wireline or wireless Network, a private Network, or any combination of virtual private networks. In some embodiments, data exchanged over a network is represented using techniques and/or formats including Hypertext Mark-up Language (HTML), Extensible Markup Language (XML), and the like. All or some of the links may also be encrypted using conventional encryption techniques such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), Internet Protocol Security (IPsec). In other embodiments, custom and/or dedicated data communication techniques may also be used in place of, or in addition to, the data communication techniques described above.
In the embodiment of the present application, the resource may be currency, game coins, icons, members, titles, value-added services, points, shoe-shaped gold ingots, gold beans, gift certificates, exchange certificates, coupons, greeting cards and the like. In the embodiments of the present application, only resources are described as examples of money.
According to the technical scheme provided by the embodiment of the application, when the expected transfer state of a certain service is determined to be non-transferable, the service is set to be in the accepted state, then whether the expected transfer state of the service is switched from the non-transferable state to the transferred state is continuously monitored, and when the expected transfer state of the service is monitored to be switched from the non-transferable state to the transferred state, the resource transfer process of the service is completed, so that the situation that financial staff need to repeatedly trigger resource transfer requests when resource transfer fails in the related technology can be avoided, the operation required by resource transfer is reduced, and the resource transfer efficiency is improved.
The technical scheme provided by the embodiment of the application can be applied to a service settlement scene. Specifically, a financial staff triggers a terminal to send a service settlement request (namely, a resource transfer request) of a certain service to a server, the server determines whether to complete service settlement according to a pre-configured stop payment condition (namely, an untransferable condition), if the stop payment state (namely, an expected transfer state) of the service is normal (namely, untransferable), the service settlement request of the service is accepted and queued, a stop payment prompt is returned to the terminal, if the stop payment state (namely, an expected transfer state) of the service is abnormal (namely, untransferable), a service settlement flow is initiated, whether the settlement amount of the service exceeds an available amount is further judged, if yes, the settlement service request of the service is accepted and queued, the stop payment prompt is returned to the terminal, and if not, the service settlement is completed.
Referring to fig. 2 in combination, a flowchart illustrating a resource transfer method applied to a service settlement scenario according to an embodiment of the present application is shown.
Step 201, receiving a service settlement request.
Step 202, detecting whether the service attribute information of the service meets the 1 st stop-payment condition.
If the service attribute information of the service meets the 1 st stop-payment condition, executing step 203; if the stop payment status of the service does not satisfy the 1 st stop payment condition, step 204 is executed.
And step 203, accepting and queuing the service settlement request of the service, returning the stop payment prompt, and inquiring the stop payment state at preset time intervals.
Step 204, detecting whether the service attribute information of the service meets the nth stop-payment condition.
If the service attribute information of the service meets the nth stop payment condition, executing step 203; if the stop payment status of the service does not satisfy the nth stop payment condition, step 205 is executed.
Step 205, service settlement is initiated.
Step 206, detecting whether the settlement amount of the service exceeds the available amount;
if the settlement amount of the service does not exceed the available amount, go to step 207; if the settlement amount of the service exceeds the available amount, step 203 is executed.
Step 207, the service settlement is completed.
Referring to fig. 3, a flowchart of a resource transfer method according to an embodiment of the present application is shown. The method may be applied to the server 10 in the embodiment shown in fig. 1. The method may comprise the steps of:
step 301, receiving a resource transfer request corresponding to a target service sent by a terminal.
The resource transfer request corresponding to the target service is used for requesting the completion of the resource transfer process of the target service. The resource transfer request carries a service identifier of the target service, and the service identifier is used for uniquely identifying the target service.
Optionally, the resource transfer request further carries attribute information of the target service. The attribute information of the target service includes, but is not limited to: resource preparation information, service creation time, resource transfer route, resource receiving object, number of resources to be transferred, and the like. The resource preparation information is used to indicate whether the financial staff is preparing resources for the target business, i.e., whether the financial staff is preparing money for the target business. The resource transfer way can be to balance, or to bank card, or to other virtual account. The resource receiving object is an entity object that receives the resource to be transferred, such as xx corporation. The amount of resources to be transferred refers to the amount of resources that need to be transferred.
In one possible implementation, after the financial staff managing the target service triggers the resource transfer instruction on the terminal, the terminal sends a resource transfer request to the server. In another possible implementation manner, the terminal sends the resource transfer request to the server when a preset time point arrives, where the preset time point is a preset time node for settling the target service.
Step 302, determining an expected transition state corresponding to the service identifier.
The expected transition state is used to indicate whether the expected transition flow of the target service is completed. The desired transition state may or may not be transitive. And when the expected transfer state is transferable, the resource transfer platform completes the expected transfer process of the target service. And when the expected transfer state is not transferable, the resource transfer platform does not complete the expected transfer flow of the target service.
Step 303, in response to that the expected transfer state of the target service is non-transferable, determining the resource transfer state of the target service as an accepted state, and completing the resource transfer process of the target service when it is monitored that the expected transfer state of the target service is switched from non-transferable to transferable.
In the embodiment of the application, if the expected transfer state of the target service is non-transferable, the server does not directly return a prompt message of transfer failure to the terminal, but accepts the resource transfer request, then continuously detects the expected transfer state of the target service until the expected transfer state of the target service is detected to be switched from non-transferable to transferable, and then completes the resource transfer process of the target service. In the process, the terminal cannot receive the prompt message of the transfer failure, so that the situation that financial staff repeatedly trigger resource transfer requests can be avoided, the operation required by resource transfer is reduced, and the resource transfer efficiency is improved.
Optionally, after completing the resource transfer process of the target service, the server returns a prompt message to the terminal, where the prompt message is used to indicate that the resource transfer process of the target service has been completed.
And when the expected transfer state of the target service is transferable, the resource transfer platform completes the resource transfer process.
To sum up, according to the technical solution provided in the embodiment of the present application, when it is determined that the expected transfer state of a certain service is non-transferable, the service is set to the accepted state, then whether the expected transfer state of the service is transferred from the non-transferable state to the transferred state is continuously monitored, and when it is monitored that the expected transfer state of the service is transferred from the non-transferable state to the transferred state, a resource transfer process of the service is completed, which can avoid a situation that financial staff needs to repeatedly trigger a resource transfer request when a resource transfer failure occurs in the related art, reduce operations required for resource transfer, and improve resource transfer efficiency.
In the above embodiment, the resource transfer platform needs to determine whether to complete the resource transfer process of the target service according to the expected transfer state of the target service. The following explains ways of determining the expected transition state of the target service.
Referring to fig. 4, a flowchart of a resource transfer method according to another embodiment of the present application is shown. In this embodiment, step 302 is alternatively implemented as steps 302a through 302 d.
Step 301, receiving a resource transfer request corresponding to a target service sent by a terminal.
The resource transfer request carries a service identifier of the target service.
Step 302a, obtaining the service attribute information of the target service according to the service identifier.
In the above embodiment, the service attribute information of the target service is carried in the resource transfer request, and the server directly reads the service attribute information of the target service carried in the resource configuration file.
Step 302b, obtain the non-transferable condition from the configuration file.
The configuration file is used to store the non-transferable condition. The non-transferable condition refers to a condition which is required to be met by a resource transfer process which does not complete the target service. The non-transferable condition can be one or more. Optionally, the non-transferable condition may be obtained by presetting according to the service attribute information of the target service.
Optionally, the configuration file includes n configuration items, where n is a positive integer greater than 3, and each of the n configuration items corresponds to a non-transferable condition. The configuration items include a combination of one or more of: resource preparation information, service creation time, resource transfer route, resource reception object, and the like. When the configuration item is resource preparation information, the non-transferable condition is that the resource preparation information is used to indicate that the financial staff has prepared resources for the target business; when the configuration item is the service creation time, the condition that the non-transferable is the non-transferable condition means that the service creation time of the target service is in a preset time interval; when the configuration item is a resource transfer path, the non-transferable condition is that the resource transfer path is a designated transfer path; when the configuration item is a resource reception object, the immutable condition means that the resource reception object is a specified reception object. The non-transferable condition may also be that the number of resources to be transferred of the target service is greater than the number of available resources. The preset time interval, the designated transfer route, the designated receiving object and the number of available resources can be preset.
In addition, the data format of the configuration file is not limited in the embodiment of the present application, and may be a json format. In the embodiment of the application, when the server stores the non-transferable condition in the configuration file in advance and receives a resource transfer request corresponding to a certain service, the server reads the non-transferable request from the configuration file to further determine whether to complete the resource transfer process of the target service.
In one possible implementation, different services correspond to the same non-transferable condition. In another possible implementation, different services correspond to different non-transferable conditions. In another possible implementation manner, different services may correspond to the same non-transferable condition, or may correspond to different non-transferable conditions.
Illustratively, the non-transferable condition is { "addTimeEnd": "2029-10-30", "addTimestart time", "addition start time", "addition time", "addition time", "time: "2029-10-29", "BusinessType", "resource transfer pathway": "PAY TO BANK-ACCOUNT (transfer TO Bank Account)" }. The conditions for this strip to be non-transferable were: the time of addition is 2029-10-29 to 2029-10-30 and payment is made to the bank card.
Step 302c, detecting whether the service attribute information of the target service meets the condition of non-transfer.
And the resource transfer platform determines whether to complete the resource transfer process of the target service by detecting whether the service attribute information of the target service meets the non-transferable condition. When the configuration file includes n configuration items, and each configuration item corresponds to a non-transferable condition, step 303c may be implemented as: and sequentially detecting whether the service attribute information of the target service meets different transfer conditions corresponding to each configuration item in the n configuration items.
Step 302d, in response to the service attribute information of the target service meeting the non-transferable condition, determining that the expected transfer state of the target service is non-transferable.
And when the service attribute information of the target service meets the non-transferable condition, determining the expected transfer state of the target service as non-transferable. When the configuration file comprises n configuration items, each configuration item corresponds to one non-transferable condition, and when at least one non-transferable condition is met by the service attribute information of the target service, the expected transfer state of the target service is determined to be non-transferable, namely, when the service attribute information of the target service meets any one non-transferable condition, the expected transfer state of the target service is determined to be non-transferable.
Step 302e, in response to that the service attribute information of the target service does not satisfy the non-transferable condition, determining that the expected transfer state of the target service is transferable.
And when the service attribute information responding to the target service does not meet the non-transferable condition, determining that the expected transfer state of the target service is transferable. When the non-transferable condition that the service attribute information of the target service is not satisfied does not exist, determining that the expected transfer state of the target service is transferable, that is, when the service attribute information of the target service does not satisfy all the non-transferable conditions, determining that the expected transfer state of the target service is non-transferable.
When the server determines that the expected transfer state of the target service is non-transferable, that is, when the service attribute information of the target service meets the non-transferable condition, the server can return reminding information to the terminal, wherein the reminding information is used for reminding that the resource transfer process of the target service is not finished. The reminding information carries the non-transferable condition met by the service attribute information of the target service, so that the financial staff can update the service attribute information of the target service in time after checking the information, and the resource transfer process of the target service is completed in time.
Step 303, in response to that the expected transfer state of the target service is non-transferable, determining the resource transfer state of the target service as an accepted state, and completing the resource transfer process of the target service when detecting that the expected transfer state of the target service is switched from non-transferable to transferable.
In summary, according to the technical scheme provided by the embodiment of the application, the expected transfer state of the service is determined from multiple dimensions (resource preparation information, resource transfer route, service creation time, and the like), and then whether the resource transfer process of the service is completed is determined, so that the reasonable utilization of resources can be realized.
In the above embodiment, when the expected transition state of the target service is non-transitive, the server needs to continuously monitor whether the expected transition state of the target service is switched to be transitive, so as to be able to complete the resource transition process of the target service in time. Next, a process of monitoring whether the expected transfer process of the target service is switched is explained. In an optional embodiment provided based on the embodiment shown in fig. 3 or fig. 4, the resource transfer method further includes:
step 401, in response to that the service attribute information of the target service meets the non-transferable condition, re-detecting whether the service attribute information of the target service meets the non-transferable condition every preset time.
The preset time can be preset by financial staff or can be set by a server, and the embodiment of the application does not limit the preset time. Illustratively, the preset time is 5 minutes.
Step 402, in response to that the service attribute information of the target service meets the non-transferable condition, when the service attribute information of the target service is updated, detecting whether the updated service attribute information of the target service meets the non-transferable condition.
Relevant personnel can update the service attribute information of the target service on the terminal, such as modifying the number of available resources, modifying a resource transfer path and the like, and then the terminal sends the updated service attribute information to the server, and at the moment, the server detects whether the updated service attribute information of the target service meets the non-transferable condition so as to determine whether the resource transfer process of the target service is completed or not.
Step 403, in response to that the service attribute information of the target service satisfies the non-transferable condition, when the non-transferable condition is updated, detecting whether the service attribute information of the target service satisfies the updated non-transferable condition.
The related personnel can also update the non-transferable condition on the server, such as modifying a resource transfer path and the like, and then the server detects whether the service attribute information of the target service meets the updated non-transferable condition so as to determine whether to complete the resource transfer process of the target service.
It should be noted that the server may execute only step 401, step 402, or step 403, may execute steps 401 and 402, steps 401 and 403, and steps 402 and 403, or may execute all of them.
To sum up, according to the technical scheme provided by the embodiment of the application, the expected transfer state of the service is queried at intervals of the preset time, the expected transfer state of the service is queried when the service attribute information of the service is updated, and the expected transfer state of the service is queried when the non-transferable condition is updated, so that whether the expected transfer state of the service is switched can be monitored in time, whether the resource transfer process of the service is completed or not is determined, and the resource transfer efficiency of the service is improved.
In the following, embodiments of the apparatus of the present application are described, and for portions of the embodiments of the apparatus not described in detail, reference may be made to technical details disclosed in the above-mentioned method embodiments.
Referring to fig. 5, a block diagram of a resource transfer apparatus according to an exemplary embodiment of the present application is shown. The resource transfer means may be implemented as all or part of the terminal by software, hardware or a combination of both. The resource transfer apparatus includes:
a request receiving module 501, configured to receive a resource transfer request corresponding to a target service, where the resource transfer request carries a service identifier of the target service.
A first determining module 502, configured to determine an expected transfer state corresponding to the service identifier, where the expected transfer state is used to indicate whether to allow a resource transfer process of the target service to be completed.
A second determining module 503, configured to determine, in response to that the expected transition state of the target service is non-transitive, a resource transition state of the target service as an accepted state.
A resource transfer module 504, configured to complete a resource transfer process of the target service when it is detected that the expected transfer state of the target service is switched from the non-transferable state to the transferable state.
To sum up, according to the technical solution provided in the embodiment of the present application, when it is determined that the expected transfer state of a certain service is non-transferable, the service is set to the accepted state, then whether the expected transfer state of the service is transferred from the non-transferable state to the transferred state is continuously monitored, and when it is monitored that the expected transfer state of the service is transferred from the non-transferable state to the transferred state, a resource transfer process of the service is completed, which can avoid a situation that financial staff needs to repeatedly trigger a resource transfer request when a resource transfer failure occurs in the related art, reduce operations required for resource transfer, and improve resource transfer efficiency.
In an alternative embodiment provided based on the embodiment shown in fig. 5, the first determining module 502 is configured to:
acquiring the service attribute information of the target service according to the service identifier;
acquiring an untransferred condition from a configuration file, wherein the untransferred condition is a condition which is required to be met by a resource transfer process which does not complete the target service;
detecting whether the service attribute information of the target service meets the non-transferable condition;
responding to the service attribute information of the target service meeting the non-transferable condition, and determining that the expected transfer state of the target service is non-transferable;
and determining that the expected transfer state of the target service is transferable in response to the service attribute information of the target service not meeting the non-transferable condition.
Optionally, the configuration file includes n configuration items, each of the n configuration items corresponds to one of the non-transferable conditions, and n is a positive integer;
the first determining module 502 is configured to:
sequentially detecting whether the service attribute information of the target service meets the non-transferable condition corresponding to each configuration item in the n configuration items;
when at least one non-transferable condition is met by the service attribute information of the target service, determining that the expected transfer state of the target service is the non-transferable state;
and when the non-transferable condition that the service attribute information of the target service is not satisfied does not exist, determining that the expected transfer state of the target service is transferable.
Optionally, the non-transferable condition comprises a combination of one or more of: the resource preparation information of the target service is used for indicating that resources are not prepared for the target service, the service creation time of the target service is in a preset time interval, the service transfer path of the target service is an appointed transfer path, and the resource receiving object of the target service is an appointed object, wherein the quantity of the resources to be transferred of the target service is greater than the quantity of the available resources of the target service.
Optionally, the first determining module 502 is further configured to send a reminding message to the terminal, where the reminding message carries the non-transferable condition that is satisfied by the service attribute information of the target service.
Optionally, the first determining module is further configured to:
responding to that the service attribute information of the target service meets the non-transferable condition, and re-detecting whether the service attribute information of the target service meets the non-transferable condition at preset time intervals;
alternatively, the first and second liquid crystal display panels may be,
responding to that the service attribute information of the target service meets the non-transferable condition, and detecting whether the updated service attribute information of the target service meets the non-transferable condition or not when the service attribute information of the target service is updated;
alternatively, the first and second electrodes may be,
and responding to that the service attribute information of the target service meets the non-transferable condition, and detecting whether the service attribute information of the target service meets the updated non-transferable condition or not when the non-transferable condition is updated.
It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to implement all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.
Referring to fig. 6, a schematic structural diagram of an electronic device according to an embodiment of the present application is shown. The electronic device may be a server. The server 600 is the server in fig. 2. Specifically, the method comprises the following steps: the server 600 includes a Central Processing Unit (CPU)601, a system memory 604 including a Random Access Memory (RAM)602 and a Read Only Memory (ROM)603, and a system bus 605 connecting the system memory 604 and the central processing unit 601. The server 600 also includes a basic input/output system (I/O system) 606, which facilitates the transfer of information between devices within the computer, and a mass storage device 607, which stores an operating system 613, application programs 614, and other program modules 615.
The basic input/output system 606 includes a display 606 for displaying information and an input device 609 such as a mouse, keyboard, etc. for a user to input information. Wherein the display 606 and the input device 609 are connected to the central processing unit 601 through an input output controller 610 connected to the system bus 605. The basic input/output system 606 may also include an input/output controller 610 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input/output controller 610 may also provide output to a display screen, a printer, or other type of output device.
The mass storage device 607 is connected to the central processing unit 601 through a mass storage controller (not shown) connected to the system bus 605. The mass storage device 607 and its associated computer-readable media provide non-volatile storage for the server 600. That is, the mass storage device 607 may include a computer-readable medium (not shown) such as a hard disk or a CD-ROI drive.
Without loss of generality, the computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage media is not limited to the foregoing. The system memory 604 and mass storage device 607 described above may be collectively referred to as memory.
The server 600 may also operate in accordance with various embodiments of the present application by connecting to remote computers over a network, such as the internet. That is, the server 600 may be connected to the network 612 through the network interface unit 611 connected to the system bus 605, or may be connected to other types of networks or remote computer systems (not shown) using the network interface unit 611.
The memory further includes one or more programs, the one or more programs are stored in the memory, and the one or more programs include steps executed by the server for performing the resource transfer method provided by the embodiment of the application.
In an exemplary embodiment, a computer-readable storage medium is further provided, in which at least one instruction is stored, and the at least one instruction is loaded and executed by a processor of a terminal to implement the resource transfer method in the above-described method embodiment.
Alternatively, the computer-readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, a computer program product is also provided, which, when executed, is adapted to implement the resource transfer method provided in the above-described method embodiments.
It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. As used herein, the terms "first," "second," and the like, do not denote any order, quantity, or importance, but rather are used to distinguish one element from another.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (6)

1. A method of resource transfer, the method comprising:
receiving a resource transfer request corresponding to a target service, which is sent by a terminal, wherein the resource transfer request carries a service identifier of the target service;
acquiring the service attribute information of the target service according to the service identifier;
acquiring an immutable condition from a configuration file, wherein the configuration file comprises n configuration items, each configuration item in the n configuration items corresponds to one immutable condition, the immutable condition refers to a condition which is required to be met by a resource transfer process which does not complete the target service, and the immutable condition comprises one or more of the following combinations: the resource preparation information of the target service is used for indicating that resources are not prepared for the target service, the service creation time of the target service is in a preset time interval, the service transfer path of the target service is an appointed transfer path, and the resource receiving object of the target service is an appointed object;
sequentially detecting whether the service attribute information of the target service meets the non-transferable condition corresponding to each configuration item in the n configuration items;
when at least one non-transferable condition is met by the service attribute information of the target service, determining that an expected transfer state of the target service is non-transferable, wherein the expected transfer state is used for indicating whether to allow a resource transfer process of the target service to be completed or not;
when the non-transferable condition that the service attribute information of the target service is not satisfied does not exist, determining that the expected transfer state of the target service is transferable;
and in response to that the expected transfer state of the target service is non-transferable, determining the resource transfer state of the target service as an accepted state, and completing the resource transfer process of the target service under the condition that the expected transfer state of the target service is switched from the non-transferable state to the transferable state.
2. The method of claim 1, wherein after detecting whether the service attribute information of the target service satisfies the non-transferable condition, the method further comprises:
and sending reminding information to the terminal, wherein the reminding information carries the non-transferable condition met by the service attribute information of the target service.
3. The method of claim 1, wherein after detecting whether the service attribute information of the target service satisfies the non-transferable condition, the method further comprises:
responding to that the service attribute information of the target service meets the non-transferable condition, and re-detecting whether the service attribute information of the target service meets the non-transferable condition at preset time intervals;
alternatively, the first and second electrodes may be,
responding to that the service attribute information of the target service meets the non-transferable condition, and detecting whether the updated service attribute information of the target service meets the non-transferable condition or not when the service attribute information of the target service is updated;
alternatively, the first and second electrodes may be,
and responding to that the service attribute information of the target service meets the non-transferable condition, and detecting whether the service attribute information of the target service meets the updated non-transferable condition or not when the non-transferable condition is updated.
4. An apparatus for resource transfer, the apparatus comprising:
a request receiving module, configured to receive a resource transfer request corresponding to a target service, where the resource transfer request carries a service identifier of the target service;
the first determining module is used for acquiring the service attribute information of the target service according to the service identifier; acquiring an immutable condition from a configuration file, wherein the configuration file comprises n configuration items, each configuration item in the n configuration items corresponds to one immutable condition, the immutable condition refers to a condition which is required to be met by a resource transfer process which does not complete the target service, and the immutable condition comprises one or more of the following combinations: the resource preparation information of the target service is used for indicating that resources are not prepared for the target service, the service creation time of the target service is in a preset time interval, the service transfer path of the target service is an appointed transfer path, and the resource receiving object of the target service is an appointed object; sequentially detecting whether the service attribute information of the target service meets the non-transferable condition corresponding to each configuration item in the n configuration items; when at least one non-transferable condition is met by the service attribute information of the target service, determining that an expected transfer state of the target service is non-transferable, wherein the expected transfer state is used for indicating whether to allow a resource transfer process of the target service to be completed or not; when the non-transferable condition that the service attribute information of the target service is not satisfied does not exist, determining that the expected transfer state of the target service is transferable;
the second determining module is used for determining the resource transfer state of the target service as an accepted state in response to the expected transfer state of the target service being non-transferable;
and the resource transfer module is used for completing the resource transfer process of the target service under the condition that the expected transfer state of the target service is switched from the non-transferable state to the transferable state.
5. An electronic device, comprising a processor and a memory, the memory storing at least one instruction that is loaded and executed by the processor to implement the resource transfer method of any of claims 1 to 3.
6. A computer-readable storage medium having stored therein at least one instruction, which is loaded and executed by a processor to implement the resource transfer method of any one of claims 1 to 3.
CN201911399459.2A 2019-12-30 2019-12-30 Resource transfer method, device, electronic equipment and storage medium Active CN111144777B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911399459.2A CN111144777B (en) 2019-12-30 2019-12-30 Resource transfer method, device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911399459.2A CN111144777B (en) 2019-12-30 2019-12-30 Resource transfer method, device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN111144777A CN111144777A (en) 2020-05-12
CN111144777B true CN111144777B (en) 2022-06-07

Family

ID=70522023

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911399459.2A Active CN111144777B (en) 2019-12-30 2019-12-30 Resource transfer method, device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111144777B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106656839A (en) * 2016-10-20 2017-05-10 财付通支付科技有限公司 Resource transfer method and apparatus
CN108182574A (en) * 2018-01-17 2018-06-19 维沃移动通信有限公司 A kind of resource transfers method and relevant device
CN110210732A (en) * 2019-05-20 2019-09-06 平安银行股份有限公司 Resource transfers method, apparatus, computer equipment and storage medium
CN110322612A (en) * 2018-03-29 2019-10-11 腾讯科技(深圳)有限公司 Business data processing method, calculates equipment and storage medium at device
CN110517032A (en) * 2019-08-29 2019-11-29 北京三快在线科技有限公司 Resource transfers method, system, device, server and storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105139200A (en) * 2015-07-31 2015-12-09 腾讯科技(深圳)有限公司 Electronic resource processing method and device and server

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106656839A (en) * 2016-10-20 2017-05-10 财付通支付科技有限公司 Resource transfer method and apparatus
CN108182574A (en) * 2018-01-17 2018-06-19 维沃移动通信有限公司 A kind of resource transfers method and relevant device
CN110322612A (en) * 2018-03-29 2019-10-11 腾讯科技(深圳)有限公司 Business data processing method, calculates equipment and storage medium at device
CN110210732A (en) * 2019-05-20 2019-09-06 平安银行股份有限公司 Resource transfers method, apparatus, computer equipment and storage medium
CN110517032A (en) * 2019-08-29 2019-11-29 北京三快在线科技有限公司 Resource transfers method, system, device, server and storage medium

Also Published As

Publication number Publication date
CN111144777A (en) 2020-05-12

Similar Documents

Publication Publication Date Title
Bajoudah et al. Toward a decentralized, trust-less marketplace for brokered IoT data trading using blockchain
US11030681B2 (en) Intermediate blockchain system for managing transactions
US11316690B2 (en) Blockchain token-based cloud orchestration architecture for discrete virtual network instances
CN110363665B (en) Credit right data processing method, device, equipment and medium
CN108229926B (en) Service settlement method and related device
US9934493B2 (en) Real-time transactions for a virtual account
JP2012053615A (en) Collective immediate transfer system with transfer destination account existence confirmation and method thereof
US11316933B2 (en) Service meshes and smart contracts for zero-trust systems
CN110289999A (en) A kind of data processing method, system and device
WO2023207146A1 (en) Service simulation method and apparatus for esop system, and device and storage medium
CN106096926B (en) Event processing method, device, electronic device and storage medium
CN110955724A (en) Data processing method and device based on block chain, node equipment and storage medium
CN110728445B (en) Information management method, information management apparatus, electronic device, and medium
CN110930257A (en) Data processing method, device, equipment and storage medium
CN112181628B (en) Resource transfer method, device, system and electronic equipment
CN110413918B (en) Data transmission method, device, equipment and storage medium
CN111144777B (en) Resource transfer method, device, electronic equipment and storage medium
CN111429092B (en) Method, apparatus, device and computer readable medium for paying an accumulation fund
CN113298574A (en) Block chain-based point management method and device and storage medium
CN113159935A (en) To-do service processing method and device based on block chain
CN111275557A (en) Method and device for controlling risk of resource management
JP6423491B1 (en) Method for providing service to customer by at least one operator using network and network thereof
EP3931780A1 (en) System and method for transferring an anonymized transaction between nodes of a computer network
CN111586157A (en) Information processing method, device and equipment
US20130013733A1 (en) Mobile terminal management server, and mobile terminal management program

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
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20221026

Address after: 1311, Floor 13, No. 27, Zhongguancun Street, Haidian District, Beijing 100080

Patentee after: QIANDAI (BEIJING) INFORMATION TECHNOLOGY CO.,LTD.

Patentee after: BEIJING SANKUAI ONLINE TECHNOLOGY Co.,Ltd.

Address before: 100080 2106-030, 9 North Fourth Ring Road, Haidian District, Beijing.

Patentee before: BEIJING SANKUAI ONLINE TECHNOLOGY Co.,Ltd.

TR01 Transfer of patent right