CN114077505A - Method and system for compensating delivery failure - Google Patents
Method and system for compensating delivery failure Download PDFInfo
- Publication number
- CN114077505A CN114077505A CN202111371782.6A CN202111371782A CN114077505A CN 114077505 A CN114077505 A CN 114077505A CN 202111371782 A CN202111371782 A CN 202111371782A CN 114077505 A CN114077505 A CN 114077505A
- Authority
- CN
- China
- Prior art keywords
- delivery
- notification
- event
- payment system
- failure
- 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
- 238000000034 method Methods 0.000 title claims abstract description 22
- 230000008520 organization Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- 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/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a method for compensating delivery failure, which comprises the following steps: step S1, the user pays for the payment system of the mall, and the payment system generates a notification event record by creating an event table; step S2, after receiving the user money, the payment system sends a notice of sending goods to the delivery system of the mall; step S3, judging whether the payment system successfully notifies the delivery system of delivery, if yes, the update event state is successful, and if not, the update event record is a failure state; step S4, judging whether the delivery system receives the delivery notice of the payment system, if yes, carrying out delivery operation on the user; if not, the delivery system starts a timing task and reads data of failure delivery notification in timing; step S5, the payment system sends failure data of the delivery notice to the delivery system; the invention can ensure that the delivery notice initiated by the payment service can be effectively transmitted to the delivery service, and ensure that the delivery service of the user can be realized.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a system for compensating delivery failure.
Background
In the mall system, the payment system and the delivery system are isolated from each other, and the payment service and the delivery service communicate in a micro-service mode. And after the user finishes order payment, the payment service informs the delivery service of successful payment, and the delivery service carries out delivery service after receiving the delivery notice. The databases between the two services are also independent, and the services are notified by using an http mode, so that the situations such as timeout, abnormality and the like may exist.
Disclosure of Invention
In order to overcome the problems, the invention aims to provide a method for ensuring that a delivery notice initiated by a payment service can be effectively transmitted to a delivery service and ensuring that the delivery service of a user can be realized.
The invention is realized by adopting the following scheme: a method of compensating for a failed delivery notification, the method comprising the steps of:
step S1, the user pays for the payment system of the mall, and the payment system generates a notification event record by creating an event table;
step S2, after receiving the user money, the payment system sends a notice of sending goods to the delivery system of the mall;
step S3, judging whether the payment system successfully notifies the delivery system of delivery, if yes, the update event state is successful, and if not, the update event record is a failure state;
step S4, judging whether the delivery system receives the delivery notice of the payment system, if yes, carrying out delivery operation on the user; if not, the delivery system starts a timing task and reads data of failure delivery notification in timing;
and step S5, the payment system sends the failure data of the delivery notice to the delivery system, so that the delivery notice can be timely notified, and the delivery notice can be ensured to arrive certainly.
Further, the step S1 is further specifically: after the user pays, a payment system of the mall creates an event table notify _ event _ tb, which comprises the following fields of a notice number notifyId, an order number orderNo, a user number userId, a commodity number goodsId, an event state, a failure frequency failCount and an event time addTime; after the user pays by the payment system, the payment system adds an event record in the database for recording the condition of delivery notice.
Further, the step S3 is further specifically: after the notification event is generated, the payment system of the mall initiates a first delivery notification to the delivery system, judges whether the delivery notification is successful, if so, actively notifies the payment system to update the event state to be successful, otherwise, performs a second notification retry at an interval of 10 minutes after the first notification fails, if the successful update event state is successful, performs a third notification retry at an interval of one hour after the second notification fails if the failure event fails, and if the failure frequency recorded by the notification event is 3 times, does not perform the active notification delivery and records the failure data of the notification event.
Further, the step S4 is further specifically: the payment system sends delivery notification for at most 3 times to the delivery system after the user successfully pays, whether the delivery system receives the delivery notification of the payment system is judged, and if yes, delivery operation is carried out on the user; if not, the delivery system starts a timing task and requests the payment system to acquire data notifying failure.
Further, the step S5 is further specifically: and the payment system receives a request that the delivery system acquires delivery notification failure data, sends the delivery notification failure data to the delivery system the next day, and the delivery system performs delivery operation again according to the failure data to ensure that delivery service can be completed.
The invention also provides a system for compensating delivery failure notification, which comprises a generation module, a notification module, a judgment module, a delivery module and a return data module; the generation module is used for enabling the user to pay for a payment system of the mall, and the payment system generates a notification event record by creating an event table; the notification module, namely the payment system, initiates a notification of sending the goods to a delivery system of the mall after receiving the payment of the user; the judging module is used for judging whether the notification that the payment system notifies the delivery system of delivery is successful or not, if so, the updating event state is successful, and if not, the updating event record is in a failure state; the delivery module judges whether the delivery system receives a delivery notice of the payment system, and if so, the delivery module carries out delivery operation on the user; if not, the delivery system starts a timing task and reads data of failure delivery notification in timing; the data return module, namely the payment system sends the failure data of the delivery notice to the delivery system, so that the delivery notice can be timely notified, and the delivery notice can be ensured to reach.
Further, the generating module is further specifically: after the user pays, a payment system of the mall creates an event table notify _ event _ tb, which comprises the following fields of a notice number notifyId, an order number orderNo, a user number userId, a commodity number goodsId, an event state, a failure frequency failCount and an event time addTime; after the user pays by the payment system, the payment system adds an event record in the database for recording the condition of delivery notice.
Further, the determining module is further specifically: after the notification event is generated, the payment system of the mall initiates a first delivery notification to the delivery system, judges whether the delivery notification is successful, if so, actively notifies the payment system to update the event state to be successful, otherwise, performs a second notification retry at an interval of 10 minutes after the first notification fails, if the successful update event state is successful, performs a third notification retry at an interval of one hour after the second notification fails if the failure event fails, and if the failure frequency recorded by the notification event is 3 times, does not perform the active notification delivery and records the failure data of the notification event.
Further, the delivery module is further specifically: the payment system sends delivery notification for at most 3 times to the delivery system after the user successfully pays, whether the delivery system receives the delivery notification of the payment system is judged, and if yes, delivery operation is carried out on the user; if not, the delivery system starts a timing task and requests the payment system to acquire data notifying failure.
Further, the data return module is further specifically: and the payment system receives a request that the delivery system acquires delivery notification failure data, sends the delivery notification failure data to the delivery system the next day, and the delivery system performs delivery operation again according to the failure data to ensure that delivery service can be completed.
The invention has the beneficial effects that: according to the invention, through the mutual cooperation of the payment system and the delivery system, if the first notification is successful, the delivery is realized in time; if not successful, a retry notification is made up to 3 times, further ensuring the communication of the notification; if the delivery notice is unsuccessful, the delivery system acquires the notice failure data through the compensation interface, so that missing notice data are supplemented, and the delivery notice can be ensured to reach.
Drawings
FIG. 1 is a schematic flow diagram of the process of the present invention.
Fig. 2 is a schematic block diagram of the system of the present invention.
Detailed Description
The invention is further described below with reference to the accompanying drawings.
Referring to fig. 1, a method for compensating after a delivery failure according to the present invention includes the following steps:
step S1, the user pays for the payment system of the mall, and the payment system generates a notification event record by creating an event table;
step S2, after receiving the user money, the payment system sends a notice of sending goods to the delivery system of the mall;
step S3, judging whether the payment system successfully notifies the delivery system of delivery, if yes, the update event state is successful, and if not, the update event record is a failure state;
step S4, judging whether the delivery system receives the delivery notice of the payment system, if yes, carrying out delivery operation on the user; if not, the delivery system starts a timing task and reads data of failure delivery notification in timing;
and step S5, the payment system sends the failure data of the delivery notice to the delivery system, so that the delivery notice can be timely notified, and the delivery notice can be ensured to arrive certainly.
The invention is further illustrated by the following specific examples:
step 1, paying by user, generating notice event record by payment system
An event table notify _ event _ tb is created that contains fields for notification number notifyId, order number orderNo, user number userld, commodity number goodsId, event status state, failure number failCount, and event time addTime. After the user pays by the payment system, the payment system adds an event record in the database for recording the condition of delivery notice. The data were generated as follows: the notification number notifyId is 1, the order number orderNo is 20211016201459xjfs, the user number userId is 9990, the product number goodsId is 201, the event status state is 0(0 represents no notification success, 1 represents notification failure and no retry is performed), the failure count is 0 (no notification will be performed if it is greater than or equal to 3), and the event time addTime is 2021-10-16.
Step 2, the payment system initiates delivery notice to the delivery system
After the notification event is generated, the payment system initiates a first delivery notification to the delivery system, and the notification request is as follows: https:// fahu. xxx. com/deliveryorderNo 20211016201459xjfs & userld 9990& sign 4b34292544a42e29465de6fe 52259389. The signature sign is used by the shipping system to verify that the request is legitimate, and the organization rule for the signature sign is (orderNo + userId + "fixed Key") MD 5. If the notification is successful, the process proceeds to step 4, and if the notification fails, the event record notification number notifyId is updated to 1, the failure number failCount is incremented by 1. The failure number failCount is 1.
Step 2.1, a second retry of notification is performed at an interval of 10 minutes after the first notification failure, and if the notification is successful, the process proceeds to step 4, and if the notification is failed, the number of failures fatcount is increased by 1, where the update event record notification number notifyId is 1. The failure number failCount is 2.
Step 2.2, after the second notification failure, a third notification retry is performed at an interval of 60 minutes, and if the notification is successful, the process proceeds to step 4, and if the notification fails, the event record notification number notifyId is updated by adding 1 to the failure frequency failCount of 1. The failure number failCount is 3.
Step 3, repeating the repeated retry to inform the failure updating event record as the failure state
If the failure times failCount of the event record is equal to 3, which indicates that the notification has been performed 3 times, and all of the 3 times have failed, then no active notification is performed, and the status state of the event record is updated to-1, which is to indicate that the delivery notification is event data that has failed 3 times and is no longer actively notified, and is used for actively reading the compensation data by the delivery system in step 5.
Step 4, actively notifying the successful update event state to be successful
If any notification from step 2 to step 2.2 is successful, the step is entered, and if the delivery system returns success character strings, the success is represented, and non-success is regarded as failure. After success, the state of the notification event is modified to 1, which indicates that the notification event delivery system has received the notification event.
Step 5, the delivery system receives the delivery notice of the payment system
The payment system notifies 3 times at most after the user pays successfully, the delivery system receives the delivery notification, obtains parameters such as order No 20211016201459xjfs & userId 9990& sign 4b34292544a42e29465de6fe52259389, checks the validity of the sign and other parameters according to the sign organization rule (order No + userId + "fixed key") MD5, and indicates the validity if the generated sign is consistent. The request contract may then ship the order 20211016201459xjfs to the user 9990.
Step 6, the delivery system reads the notification failure data at regular time
If the events from step 2 to step 2.2 failed in the notification would be recorded as failed by step 3, the shipping system would start a timed task requesting the payment system to obtain the data of the previous day's failures at 00:00 a.m. every morning, assuming that the next 2021-10-17 a.m. then the payment system interface https:// zhifu. xxx. com/getNotifyFailDatatime ═ 2021-10-16& sign ═ b705147c2a49dc66908512ea41365f2d, and the organization rule is (time + fixed key ") MD 5.
Step 7, the payment system returns the notice failure data to the delivery system
The payment system receives the request for obtaining the failure data, and the obtained parameters are as follows: time 2021-10-16& sign b705147c2a49dc66908512ea41365f2d, the validity of sign and other parameters is checked according to the sign organization rule (time + "fixed key") MD5, and if the generated sign is consistent, the validity is represented. Reading the failure data of the date according to the time parameter, wherein the query statement comprises the following steps: select from notify _ event _ tb word addTime ═ 2021-10-16' and state ═ 1. Then if the notification 3 fails, the shipping system may get the notification failure data from the payment system the next morning to ensure that the shipping service can be completed.
In short, the invention can realize that the delivery notice can not only inform in time, but also require a series of compensation mechanisms after the informing fails, and can ensure that the delivery notice can reach certainly through two security measures of retry informing of payment service and active obtaining of failure informing of delivery service under the condition of failure of the delivery notice.
Referring to fig. 2, the present invention further provides a system for compensating after a delivery notification fails, which includes a generation module, a notification module, a determination module, a delivery module, and a data return module; the generation module is used for enabling the user to pay for a payment system of the mall, and the payment system generates a notification event record by creating an event table; the notification module, namely the payment system, initiates a notification of sending the goods to a delivery system of the mall after receiving the payment of the user; the judging module is used for judging whether the notification that the payment system notifies the delivery system of delivery is successful or not, if so, the updating event state is successful, and if not, the updating event record is in a failure state; the delivery module judges whether the delivery system receives a delivery notice of the payment system, and if so, the delivery module carries out delivery operation on the user; if not, the delivery system starts a timing task and reads data of failure delivery notification in timing; the data return module, namely the payment system sends the failure data of the delivery notice to the delivery system, so that the delivery notice can be timely notified, and the delivery notice can be ensured to reach.
The generation module is further specifically: after the user pays, a payment system of the mall creates an event table notify _ event _ tb, which comprises the following fields of a notice number notifyId, an order number orderNo, a user number userId, a commodity number goodsId, an event state, a failure frequency failCount and an event time addTime; after the user pays by the payment system, the payment system adds an event record in the database for recording the condition of delivery notice.
The judging module is further specifically: after the notification event is generated, the payment system of the mall initiates a first delivery notification to the delivery system, judges whether the delivery notification is successful, if so, actively notifies the payment system to update the event state to be successful, otherwise, performs a second notification retry at an interval of 10 minutes after the first notification fails, if the successful update event state is successful, performs a third notification retry at an interval of one hour after the second notification fails if the failure event fails, and if the failure frequency recorded by the notification event is 3 times, does not perform the active notification delivery and records the failure data of the notification event.
The delivery module is further specifically: the payment system sends delivery notification for at most 3 times to the delivery system after the user successfully pays, whether the delivery system receives the delivery notification of the payment system is judged, and if yes, delivery operation is carried out on the user; if not, the delivery system starts a timing task and requests the payment system to acquire data notifying failure.
The data return module is further specifically: and the payment system receives a request that the delivery system acquires delivery notification failure data, sends the delivery notification failure data to the delivery system the next day, and the delivery system performs delivery operation again according to the failure data to ensure that delivery service can be completed.
The above description is only a preferred embodiment of the present invention, and all equivalent changes and modifications made in accordance with the claims of the present invention should be covered by the present invention.
Claims (10)
1. A method of compensating for a failed delivery notice, the method comprising the steps of:
step S1, the user pays for the payment system of the mall, and the payment system generates a notification event record by creating an event table;
step S2, after receiving the user money, the payment system sends a notice of sending goods to the delivery system of the mall;
step S3, judging whether the payment system successfully notifies the delivery system of delivery, if yes, the update event state is successful, and if not, the update event record is a failure state;
step S4, judging whether the delivery system receives the delivery notice of the payment system, if yes, carrying out delivery operation on the user; if not, the delivery system starts a timing task and reads data of failure delivery notification in timing;
and step S5, the payment system sends the failure data of the delivery notice to the delivery system, so that the delivery notice can be timely notified, and the delivery notice can be ensured to arrive certainly.
2. The method of claim 1, wherein the method of compensating for a failed delivery notice comprises: the step S1 further includes: after the user pays, a payment system of the mall creates an event table notify _ event _ tb, which comprises the following fields of a notice number notifyId, an order number orderNo, a user number userId, a commodity number goodsId, an event state, a failure frequency failCount and an event time addTime; after the user pays by the payment system, the payment system adds an event record in the database for recording the condition of delivery notice.
3. The method of claim 1, wherein the method of compensating for a failed delivery notice comprises: the step S3 further includes: after the notification event is generated, the payment system of the mall initiates a first delivery notification to the delivery system, judges whether the delivery notification is successful, if so, actively notifies the payment system to update the event state to be successful, otherwise, performs a second notification retry at an interval of 10 minutes after the first notification fails, if the successful update event state is successful, performs a third notification retry at an interval of one hour after the second notification fails if the failure event fails, and if the failure frequency recorded by the notification event is 3 times, does not perform the active notification delivery and records the failure data of the notification event.
4. The method of claim 1, wherein the method of compensating for a failed delivery notice comprises: the step S4 further includes: the payment system sends delivery notification for at most 3 times to the delivery system after the user successfully pays, whether the delivery system receives the delivery notification of the payment system is judged, and if yes, delivery operation is carried out on the user; if not, the delivery system starts a timing task and requests the payment system to acquire data notifying failure.
5. The method of claim 1, wherein the method of compensating for a failed delivery notice comprises: the step S5 further includes: and the payment system receives a request that the delivery system acquires delivery notification failure data, sends the delivery notification failure data to the delivery system the next day, and the delivery system performs delivery operation again according to the failure data to ensure that delivery service can be completed.
6. A system for compensating for a failed delivery notice, comprising: the system comprises a generation module, a notification module, a judgment module, a delivery module and a return data module; the generation module is used for enabling the user to pay for a payment system of the mall, and the payment system generates a notification event record by creating an event table; the notification module, namely the payment system, initiates a notification of sending the goods to a delivery system of the mall after receiving the payment of the user; the judging module is used for judging whether the notification that the payment system notifies the delivery system of delivery is successful or not, if so, the updating event state is successful, and if not, the updating event record is in a failure state; the delivery module judges whether the delivery system receives a delivery notice of the payment system, and if so, the delivery module carries out delivery operation on the user; if not, the delivery system starts a timing task and reads data of failure delivery notification in timing; the data return module, namely the payment system sends the failure data of the delivery notice to the delivery system, so that the delivery notice can be timely notified, and the delivery notice can be ensured to reach.
7. The system of claim 6, wherein the system compensates for failed delivery notifications by: the generation module is further specifically: after the user pays, a payment system of the mall creates an event table notify _ event _ tb, which comprises the following fields of a notice number notifyId, an order number orderNo, a user number userId, a commodity number goodsId, an event state, a failure frequency failCount and an event time addTime; after the user pays by the payment system, the payment system adds an event record in the database for recording the condition of delivery notice.
8. The system of claim 6, wherein the system compensates for failed delivery notifications by: the judging module is further specifically: after the notification event is generated, the payment system of the mall initiates a first delivery notification to the delivery system, judges whether the delivery notification is successful, if so, actively notifies the payment system to update the event state to be successful, otherwise, performs a second notification retry at an interval of 10 minutes after the first notification fails, if the successful update event state is successful, performs a third notification retry at an interval of one hour after the second notification fails if the failure event fails, and if the failure frequency recorded by the notification event is 3 times, does not perform the active notification delivery and records the failure data of the notification event.
9. The system of claim 6, wherein the system compensates for failed delivery notifications by: the delivery module is further specifically: the payment system sends delivery notification for at most 3 times to the delivery system after the user successfully pays, whether the delivery system receives the delivery notification of the payment system is judged, and if yes, delivery operation is carried out on the user; if not, the delivery system starts a timing task and requests the payment system to acquire data notifying failure.
10. The system of claim 6, wherein the system compensates for failed delivery notifications by: the data return module is further specifically: and the payment system receives a request that the delivery system acquires delivery notification failure data, sends the delivery notification failure data to the delivery system the next day, and the delivery system performs delivery operation again according to the failure data to ensure that delivery service can be completed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111371782.6A CN114077505A (en) | 2021-11-18 | 2021-11-18 | Method and system for compensating delivery failure |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111371782.6A CN114077505A (en) | 2021-11-18 | 2021-11-18 | Method and system for compensating delivery failure |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114077505A true CN114077505A (en) | 2022-02-22 |
Family
ID=80283978
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111371782.6A Pending CN114077505A (en) | 2021-11-18 | 2021-11-18 | Method and system for compensating delivery failure |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114077505A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109903458A (en) * | 2017-12-07 | 2019-06-18 | 鸿富锦精密工业(武汉)有限公司 | Transaction control system and method |
| CN111861502A (en) * | 2020-04-03 | 2020-10-30 | 上海寻梦信息技术有限公司 | Information processing method, system, electronic device and storage medium |
| CN113656200A (en) * | 2021-08-24 | 2021-11-16 | 福建天晴数码有限公司 | Method and system for realizing delivery notification by using delay queue |
-
2021
- 2021-11-18 CN CN202111371782.6A patent/CN114077505A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109903458A (en) * | 2017-12-07 | 2019-06-18 | 鸿富锦精密工业(武汉)有限公司 | Transaction control system and method |
| CN111861502A (en) * | 2020-04-03 | 2020-10-30 | 上海寻梦信息技术有限公司 | Information processing method, system, electronic device and storage medium |
| CN113656200A (en) * | 2021-08-24 | 2021-11-16 | 福建天晴数码有限公司 | Method and system for realizing delivery notification by using delay queue |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6584466B1 (en) | Internet document management system and methods | |
| US7792961B2 (en) | Apparatus and computer-readable media for recoverable workflow | |
| US6535855B1 (en) | Push banking system and method | |
| US8364953B2 (en) | System and method for providing secured electronic transactions | |
| US20060059230A1 (en) | System and method for transferring data between applications | |
| JP2006517697A (en) | Software license management system configurable for post-use payment business model | |
| WO2005020167A2 (en) | Electronic payment system | |
| US20020107811A1 (en) | Use of time-stamps and digital signatures | |
| CN111917915B (en) | Schedule processing method, device and equipment | |
| EP2098982A1 (en) | Distributed business process tracking | |
| US20030120777A1 (en) | Forms auditing systems and methods | |
| US11570168B2 (en) | Techniques for repeat authentication | |
| CN101388096A (en) | Multi-platform data standardization processing method and system | |
| CN110633970A (en) | Digital asset sorting method and device, computer equipment and storage medium | |
| CN112269829B (en) | Block chain data management method based on resource recovery system platform | |
| US20190318418A1 (en) | Systems and methods for automated advance order payment processing | |
| CN114077505A (en) | Method and system for compensating delivery failure | |
| CN113590354A (en) | Block chain-based information push method, apparatus, device, medium, and program product | |
| CN112561611B (en) | Electronic bill multi-channel delivery method and system | |
| CN111190754A (en) | Block chain event notification method and block chain system | |
| CN113778950B (en) | Method for acquiring trusted file, index server, query server and medium | |
| CN115544034A (en) | Data consistency method and service system | |
| CN113590715A (en) | Block chain-based information push method, apparatus, device, medium, and program product | |
| CN117575482B (en) | Drug data warehousing method, device, equipment and storage medium | |
| CN114760099B (en) | Data transmission method, device, equipment and storage medium |
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 |