CN114793232A - Service processing method and device, electronic equipment and storage medium - Google Patents
Service processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114793232A CN114793232A CN202210352860.6A CN202210352860A CN114793232A CN 114793232 A CN114793232 A CN 114793232A CN 202210352860 A CN202210352860 A CN 202210352860A CN 114793232 A CN114793232 A CN 114793232A
- Authority
- CN
- China
- Prior art keywords
- file
- service
- partner terminal
- directory
- path information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 21
- 238000000034 method Methods 0.000 claims abstract description 67
- 238000004891 communication Methods 0.000 claims abstract description 58
- 238000012545 processing Methods 0.000 claims abstract description 39
- 230000005540 biological transmission Effects 0.000 claims abstract description 38
- 238000004590 computer program Methods 0.000 claims description 24
- 230000015654 memory Effects 0.000 claims description 11
- 230000008569 process Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 6
- 238000012546 transfer Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 3
- 108010001267 Protein Subunits Proteins 0.000 description 2
- 230000009471 action Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 239000000758 substrate Substances 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present disclosure provides a service processing method, which can be applied to the technical field of communication, the financial field or other fields. The method comprises the following steps: based on a preset communication protocol, sending a first service file to a first target directory of a first partner terminal; acquiring a file transmission state identifier configured in a preset communication protocol; and sending a first notification message to the first partner terminal under the condition that the file transmission state identifier shows that the file transmission state identifier is successfully sent. In addition, the disclosure also provides a business processing device, an electronic device and a storage medium.
Description
Technical Field
The present disclosure relates to the field of communication technologies and the field of finance, and more particularly, to a service processing method, a service processing apparatus, an electronic device, a storage medium, and a program product.
Background
With the expansion of business scale of enterprises, more and more businesses need to be processed in a multi-party cooperation mode. When a plurality of partners interact and cooperate, file transfer between each other is inevitably performed.
In implementing the disclosed concept, the inventors found that there are at least the following problems in the related art: after a file sender sends a file, whether the file is sent or not cannot be sensed, so that the continuity of the service is poor.
Disclosure of Invention
In view of the above, the present disclosure provides a service processing method, apparatus, electronic device, storage medium, and computer program product.
One aspect of the present disclosure provides a service processing method, including: based on a preset communication protocol, sending a first service file to a first target directory of a first partner terminal; acquiring a file transmission state identifier configured in the preset communication protocol; and sending a first notification message to the first partner terminal when the file transmission state identifier indicates that the file transmission state identifier is successfully sent.
According to an embodiment of the present disclosure, the method further includes: receiving a first feedback message from the first partner terminal, wherein the first feedback message is generated by the first partner terminal according to the first notification message; and sending the first service file to a first target directory of the first partner terminal under the condition that the first feedback message carries feedback information indicating that the first service file is not received.
According to the embodiment of the present disclosure, the first feedback message further carries first directory path information; the method further comprises the following steps: comparing the first directory path information with the path information represented by the first target directory to obtain a first comparison result; determining a second target directory based on the first directory path information when the first comparison result indicates that the first directory path information does not match the path information indicated by the first target directory; and sending the first service file to a second target directory of the first partner terminal.
According to an embodiment of the present disclosure, the method further includes: receiving a second notification message from a second partner terminal; and pulling a second service file from a third target directory of the second partner terminal based on the preset communication protocol under the condition that the second notification message carries information indicating that the file is ready.
According to an embodiment of the present disclosure, the method further includes: responding to a trigger preset event, and determining a receiving state of the second service file, wherein the preset event comprises that the time length after the second notification message is received reaches a preset time length, or a third notification message from the second partner terminal is received; and sending a second feedback message generated based on the receiving state of the second service file to the second partner terminal.
According to an embodiment of the present disclosure, the method further includes: and pulling the second service file from a third target directory of the second partner terminal when the reception status of the second service file indicates that the reception is not completed.
According to an embodiment of the present disclosure, the second notification message further carries second directory path information; the method further comprises the following steps: comparing the second directory path information with the path information represented by the third target directory to obtain a second comparison result; determining a fourth target directory based on the second directory path information when the second comparison result indicates that the second directory path information does not match the path information indicated by the third target directory; and pulling the second service file from a fourth target directory of the second partner terminal.
Another aspect of the present disclosure provides a service processing apparatus, including: the first sending module is used for sending a first service file to a first target directory of a first partner terminal based on a preset communication protocol; the acquisition module is used for acquiring the file transmission state identification configured in the preset communication protocol; and a second sending module, configured to send a first notification message to the first partner terminal when the file transmission status flag indicates that the file transmission status flag is successfully sent.
Another aspect of the present disclosure provides an electronic device including: one or more processors; a memory for storing one or more instructions, wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement a method as described above.
Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.
Another aspect of the disclosure provides a computer program product comprising computer executable instructions for implementing the method as described above when executed.
According to the embodiment of the disclosure, after the first service file is sent by using the preset communication protocol, because the preset communication protocol is internally provided with the file transmission state identifier for indicating whether the file is sent outwards, whether the first service file is sent can be analyzed according to the state of the identifier, and when the file is determined to be sent, a notification message is sent to the target terminal to notify the target terminal that the file is sent. By the technical means, the technical problem that whether the file is sent or not cannot be sensed after the file is sent by a file sender in the related technology so that the continuity of the service is poor is at least partially solved, the processing efficiency of the file is effectively improved, and the overall continuity of the service is improved.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:
fig. 1 schematically illustrates an exemplary system architecture to which the traffic processing method and apparatus may be applied, according to an embodiment of the present disclosure.
Fig. 2 schematically shows a flowchart of a file sending method in a business process according to an embodiment of the present disclosure.
Fig. 3 schematically shows a flowchart of a file sending method in a business process according to another embodiment of the present disclosure.
Fig. 4 schematically shows a flowchart of a file receiving method in a business process according to an embodiment of the present disclosure.
Fig. 5 schematically shows a flowchart of a file receiving method in a business process according to another embodiment of the present disclosure.
FIG. 6A schematically illustrates an architecture diagram of a business processing system in accordance with an embodiment of the disclosure.
FIG. 6B schematically shows a workflow diagram of a business processing system according to an embodiment of the disclosure.
FIG. 6C schematically shows an architecture diagram of a business processing system in accordance with another embodiment of the present disclosure.
Fig. 7 schematically shows a block diagram of a traffic processing device according to an embodiment of the present disclosure.
Fig. 8 schematically shows a block diagram of an electronic device adapted to implement a traffic processing method according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs, unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
In a scenario of interconnection of multiple partners, if a document transmission between the partner systems is involved, in order to ensure the security and reliability of the document transmission, SFTP (secure File Transfer Protocol) commands are often used in the related art to establish connection and then perform the document transmission.
In some scenarios, there are often some drawbacks to using only SFTP for file transfer. For example, the file provider sends a service file to the partner, but the partner may not process the service file in time because the service file is not received or the partner does not find that the file is delivered in time. For another example, the file receiving party does not know when the service file provided by the file providing party is ready, and a way of trying to actively acquire the service file by frequently establishing a connection consumes more resources, but reducing the frequency results in too high cost of waiting for being pulled after the service file is ready, thereby reducing the overall efficiency of service processing.
In view of this, embodiments of the present disclosure provide a file transmission method based on an online notification, which enables a file provider to notify a file receiver of a file identifier sent this time through an online notification mechanism after sending a file, and the file receiver checks whether the file is ready in real time after receiving the online notification and processes the file in time.
Specifically, embodiments of the present disclosure provide a service processing method, apparatus, electronic device, storage medium, and computer program product. The method comprises the following steps: based on a preset communication protocol, sending a first service file to a first target directory of a first partner terminal; acquiring a file transmission state identifier configured in a preset communication protocol; and sending a first notification message to the first partner terminal under the condition that the file transmission state identifier shows that the file transmission state identifier is successfully sent.
It should be noted that the service processing method and apparatus determined in the embodiments of the present disclosure may be used in the field of communication technology or the field of finance, for example, the service processing method may be applied to fund service of a bank, so as to improve service processing efficiency of a bank party and a fund party. The service processing method and apparatus determined in the embodiments of the present disclosure may also be used in any fields other than the communication technology field and the financial field, and the application fields of the service processing method and apparatus determined in the embodiments of the present disclosure are not limited.
Fig. 1 schematically illustrates an exemplary system architecture to which the traffic processing method and apparatus may be applied, according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, 104.
The terminal devices 101, 102, 103, 104 may be various electronic devices supporting data communication, including but not limited to servers, smart phones, tablets, computers, and the like.
Various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, and/or social platform software, etc., may be installed on the terminal devices 101, 102, 103, 104.
The terminal devices 101, 102, 103, 104 may communicate information therebetween via various connection-type communication links, including, but not limited to, wired and/or wireless communication links, and the like. The communication link may be established based on various communication protocols.
It should be noted that the service processing method provided by the embodiment of the present disclosure may be generally executed by the terminal device 101, 102, 103, or 104. Accordingly, the service processing apparatus provided by the embodiment of the present disclosure may be generally disposed in the terminal device 101, 102, 103, or 104.
For example, a collaboration service has one leader and three partners, where terminal device 101 is an electronic device associated with the leader and terminal devices 102, 103, and 104 are electronic devices associated with the three partners, respectively. In the process of the cooperative service, the terminal device 101 needs to send a service file to any one of the terminal devices 102, 103, and 104 (for example, the terminal device 102), and at this time, the terminal device 101 may locally execute the service processing method provided by the embodiment of the present disclosure.
It should be understood that the number of terminal devices in fig. 1 is merely illustrative. There may be any number of terminal devices, as desired for implementation.
Fig. 2 schematically shows a flowchart of a file sending method in a business process according to an embodiment of the present disclosure.
As shown in fig. 2, the method includes operations S201 to S203.
In operation S201, a first service file is sent to a first target directory of a first partner terminal based on a preset communication protocol.
In operation S202, a file transmission status identifier configured in a preset communication protocol is acquired.
In operation S203, in case that the file transmission status flag indicates that the transmission has been successful, a first notification message is transmitted to the first partner terminal.
According to the embodiment of the present disclosure, the preset communication protocol may be a protocol for file transfer, which is agreed in advance between the service leader and each partner, and the specific reference protocol of the preset communication protocol is not limited, and includes but is not limited to SFTP, HTTPS, and the like.
According to the embodiment of the disclosure, a communication link between the service leader and the first partner terminal may be established based on a preset communication protocol, and then the service leader may send the service file to the first partner terminal through the communication link.
According to an embodiment of the present disclosure, the first target directory may be a folder for receiving the service file in the first partner terminal. The specific path of the first target directory may be agreed upon in advance among the partners.
According to the embodiment of the present disclosure, the file transmission status identifier may be an identifier in a preset communication protocol for indicating whether a file has been successfully transmitted.
According to the embodiment of the disclosure, the first notification message may include an identifier of the first service file, where the identifier may be a file name, a unique identification code, and the like of the first service file. By means of the identification, the first partner may check in a first destination directory of the first partner terminal whether the first service file has been acquired.
According to the embodiment of the disclosure, the first notification message may be sent through a communication link that transmits a first service file; the first notification message can also be sent through a communication link established based on other communication protocols; alternatively, in the case where the IP address of the first partner terminal is determined, the first notification message may also be transmitted through the internet. The transmission route of the first notification message is not limited herein.
According to the embodiment of the disclosure, after the first service file is sent by using the preset communication protocol, because the preset communication protocol is internally provided with the file transmission state identifier for indicating whether the file is sent outwards, whether the first service file is sent or not can be analyzed according to the state of the identifier, and when the file is determined to be sent, a notification message is sent to the target terminal to inform the target terminal that the file is sent. By the technical means, the technical problem that whether the file is sent or not cannot be sensed after the file is sent by a file sender in the related technology so that the continuity of the service is poor is at least partially solved, the processing efficiency of the file is effectively improved, and the overall continuity of the service is improved.
The method shown in fig. 2 is further described with reference to fig. 3 to 6C in conjunction with specific embodiments.
Fig. 3 schematically shows a flowchart of a file sending method in a business process according to another embodiment of the present disclosure.
As shown in fig. 3, the method includes operations S301 to S310.
It should be noted that, unless explicitly stated that a sequence of execution exists between different operations or a sequence of execution exists in technical implementation of different operations, an execution sequence between multiple operations may not be sequential, and multiple operations may also be executed at the same time in the flowchart in the embodiment of the present disclosure.
In operation S301, a first service file is sent to a first target directory of a first partner terminal based on a preset communication protocol.
In operation S302, a file transmission status flag configured in a preset communication protocol is acquired.
In operation S303, in case that the file transmission status flag indicates that the transmission has been successful, a first notification message is sent to the first partner terminal.
In operation S304, a first feedback packet from a first partner terminal is received.
In operation S305, it is determined whether the first feedback packet indicates that the first service file is received. Executing operation S306 when it is determined that the first feedback message carries feedback information indicating that the first service file is received; if it is determined that the first feedback message carries feedback information indicating that the first service file is not received, operation S307 is performed.
In operation S306, the file transmission flow is ended.
In operation S307, first directory path information carried in the first feedback packet is obtained.
In operation S308, it is determined whether the first directory path information coincides with the path information indicated by the first target directory. Returning to perform operation S301 if it is determined that the first directory path information is consistent with the path information represented by the first target directory; in a case where it is determined that the first directory path information does not coincide with the path information represented by the first target directory, operation S309 is performed.
In operation S309, a second target directory is determined based on the first directory path information.
In operation S310, a first service file is transmitted to a second target directory of the first partner terminal. After operation S310 is completed, execution returns to operation S302.
According to the embodiment of the present disclosure, operations S301 to S303 have the same or similar technical features as operations S201 to S203, and are not described herein again.
According to an embodiment of the present disclosure, the first feedback message may be generated by the first partner terminal according to the first notification message. The feedback information carried in the first feedback message may be used to indicate whether the first partner terminal receives the first service file.
According to the embodiment of the disclosure, when the first partner terminal performs system upgrade, repair and other processes, the first target directory for receiving the service file may be changed, and such a change is not perceivable to the service master. After the first target directory is changed, the first service file sent to the directory by the service master may not be received by the first partner terminal. Therefore, the directory with the changed service leading direction can be informed to send the first service file in a manner that the first feedback message carries the first directory path information.
In some embodiments, the first feedback message may not include the first directory path information, and at this time, when it is determined that the first feedback message carries the feedback information indicating that the first service file is not received, the method of operation S301 may be executed in a return manner, so as to send the first service file to the first target directory of the first partner terminal again.
According to an embodiment of the present disclosure, the path information may be composed of disk information and multi-level folder information, and may be represented as "C: \\ Users \ ABC \ share. For example, the first directory path information and the path information indicated by the first target directory may be sequentially compared in the order from the last-stage folder information to the disk information, and the determination may be made based on the obtained comparison result.
Fig. 4 schematically shows a flowchart of a file receiving method in a service processing process according to an embodiment of the present disclosure.
As shown in fig. 4, the method includes operations S401 to S403.
In operation S401, a second notification message from the second partner terminal is received.
In operation S402, it is determined whether the second notification message indicates file readiness. In a case where it is determined that the information indicating that the file is ready is carried in the second notification message, performing operation S403; in a case where it is determined that the information indicated as file ready is not carried in the second notification message, return is made to perform operation S401.
In operation S403, a second service file is pulled from a third target directory of the second partner terminal based on a preset communication protocol.
According to the embodiment of the present disclosure, the second notification message may be a heartbeat message that the second partner terminal sends to the service master terminal at regular time. The second notification message may carry a preparation status of the service file, where the preparation status may include ready, not ready, and the like.
According to the embodiment of the present disclosure, the second notification message may carry an identifier of the second service file, where the identifier may be a file name, a unique identifier, and the like of the second service file. Through the identifier, the second service file can be actively pulled from the second partner terminal.
According to an embodiment of the present disclosure, the third target directory may be a folder in the second partner terminal for being pulled by the service leader terminal to the service file. The specific path of the third target directory may be agreed upon in advance among the partners.
According to the embodiment of the present disclosure, the folder for receiving the service file in the partner terminal and the folder for pulling the service file by the service leader terminal may be the same or different, and are not limited herein.
According to the embodiment of the disclosure, the message is used for confirming the file preparation condition, and after the file is ready, the communication link is established again for pulling the service file, so that the technical problem of high communication cost caused by pulling the file in different SFTP communication modes in the related art is at least partially overcome, and the communication cost and the resource consumption are effectively reduced.
Fig. 5 schematically shows a flowchart of a file receiving method in a business process according to another embodiment of the present disclosure.
As shown in fig. 5, the method includes operations S501 to S507.
In operation S501, a second notification message from a second partner terminal is received.
In operation S502, it is determined whether the second notification packet indicates file readiness. In a case where it is determined that the information indicating that the file is ready is carried in the second notification message, operation S503 is performed; in a case where it is determined that the information indicating that the file is ready is not carried in the second notification message, the operation returns to be performed in operation S501.
In operation S503, second directory path information carried in the second notification message is obtained.
In operation S504, it is determined whether the second directory path information coincides with the path information indicated by the third target directory. Returning to perform operation S505 if it is determined that the second directory path information is consistent with the path information indicated by the third target directory; in a case where it is determined that the second directory path information does not coincide with the path information indicated by the third target directory, operation S506 is returned to be performed.
In operation S505, a second service file is pulled from a third target directory of the second partner terminal based on a preset communication protocol.
In operation S506, a fourth target directory is determined based on the second directory path information.
In operation S507, the second service file is pulled from the fourth target directory of the second partner terminal based on the preset communication protocol.
According to the embodiment of the present disclosure, operations S501 to S502 have the same or similar technical features as operations S401 to S402, and are not described herein again.
According to an embodiment of the present disclosure, the second directory path information may be path information of a folder for a pulled service file in the second partner terminal.
According to the embodiment of the present disclosure, determining whether the second directory path information is consistent with the path information represented by the third target directory may, for example, compare the second directory path information with the path information represented by the third target directory in order from the last-level folder information to the disk information, and perform the determination according to the obtained comparison result.
In some embodiments, after actively pulling the second service file, the following operations may be further included: responding to a trigger preset event, and determining the receiving state of the second service file, wherein the preset event comprises that the time length after the second notification message is received reaches a preset time length, or receiving a third notification message from a second partner terminal; and sending a second feedback message generated based on the receiving state of the second service file to the second partner terminal.
According to an embodiment of the present disclosure, the receiving status of the second service file may include receiving completed, receiving station, not receiving, and the like. For example, when the second service file does not exist in the second target directory, the reception state of the second service file may be represented as not received.
According to the embodiment of the present disclosure, the third notification message may be a heartbeat message that the second partner terminal sends to the service master terminal at regular time. Before the second partner terminal receives the feedback message indicating that the file is received completely, the heartbeat message can be sent to the service master terminal at regular time.
According to the embodiment of the present disclosure, when the receiving status of the second service file indicates that the receiving is not completed, the second service file may be pulled again from the third target directory of the second partner terminal. In some embodiments, the path information of the folder used by the second partner terminal for the pulled service file is changed to a fourth target directory, and at this time, the second service file may be pulled again from the fourth target directory of the second partner terminal.
FIG. 6A schematically illustrates an architecture diagram of a business processing system in accordance with an embodiment of the disclosure.
As shown in fig. 6A, the service processing system includes an interaction front-end system 610 and a partner system 620, and the service leader may interact with the partner system 620 through the interaction front-end system 610 to send or actively pull the service file.
The interactive front-end system 610 includes a handling layer 611 and a front-end layer 612.
The processing layer 611 may generate various service files to be processed by the partner according to the service scenario requirements, and submit the service files to the front layer 612.
The front tier 612 includes file sending logic 6121, file receiving logic 6122, online notification logic 6123, and file resending logic 6124.
The file sending logic unit 6121 may identify various service files generated by the service processing layer 611 and send the service files to the partner system 620.
The file receiving logic unit 6122 may pull the required service file from each partner terminal of the partner system 620, and transfer the service file to the service processing layer 611 for subsequent processing.
The online notification logic unit 6123 may send a notification message to the corresponding partner terminal after the file sending logic unit 6121 sends the service file, or after the file receiving logic unit 6122 completes receiving the service file.
The file retransmission logic unit 6124 may retransmit the corresponding service file to the partner terminal after receiving the instruction of the online notification logic unit 6123.
The partner system 620 is provided with a reception directory 621, a transmission directory 622, and an online notification unit 623.
Receiving directory 621 may be a folder in partner system 620 for receiving service files.
Send directory 622 may be a folder in partner system 620 for pulled business files.
The online notification unit 623 may feed back the notification sent by the online notification logic unit 6123, or may actively send the notification to the online notification logic unit 6123.
Fig. 6B schematically illustrates a workflow diagram of a business processing system according to an embodiment of the disclosure.
As shown in fig. 6B, the work flow of the business processing system includes a file sending flow and a file receiving flow.
In the file sending process, after sending the service file to the partner system 620, the front layer 612 notifies the partner to process the service file through an online notification mechanism. The method specifically comprises the following operations:
first, the file sending logic unit 6121 sends the service file to the receiving directory 621 of the partner system 620, and invokes the online notification logic unit 6123 to send a notification message to the partner system 620, so as to notify that the partner file has been sent completely.
Then, the online notification logic unit 6123 sends "file sent notification" to the partner system 620 after receiving the instruction of the file sending logic unit 6121, so as to notify the partner to process the service file as soon as possible. If the online notification unit 623 of the partner system 620 returns that the file has been received, the file sending process is ended; if the online notification unit 623 of the partner system 620 returns that the file is not valid, the file retransmission logic unit 6124 is invoked to retransmit the file.
Then, the file resending logic unit 6124 receives the instruction of the online notification logic unit 6123, resends the service file to the receiving directory 621 of the partner system 620, and invokes the online notification logic unit 6123 to send a notification message to the partner system 620 to notify that the partner file has been sent.
In the file receiving process, the front layer 612 actively pulls the service file after receiving the file ready notification, and performs subsequent processing. The method specifically comprises the following operations:
first, the online notification logic unit 6123 determines whether the service file is received after receiving the "file ready notification" from the online notification unit 623 of the partner system 620. If the service file is received, the file receiving completion is returned to the online notification unit 623, and the file receiving process is ended; if the service file is not received, the file receiving logic unit 6122 is called to pull the file.
Then, the file receiving logic unit 6122 actively establishes a link with the partner system 620 according to the instruction of the online notification logic unit 6123, and pulls the service file from the sending directory 622 of the partner system 620. And after the service file is pulled, the online notification logic unit 6123 is called.
Then, the online notification logic unit 6123 sends "notification that the file is accepted" to the online notification unit 623 of the partner system 620, and ends the file reception flow.
FIG. 6C schematically illustrates an architecture diagram of a business processing system in accordance with another embodiment of the disclosure.
As shown in fig. 6C, in another embodiment of the present disclosure, the interactive front-end processor system 610 further includes a rule definition layer 613.
In the rule definition layer 613, it is possible to configure the workflow of the business processing system in a customized manner, whether each logical unit of the front layer 612 is effective. For example, it may be defined whether "file sent notification" needs to be sent, whether file resending needs to be supported, whether "file ready notification" needs to be received, whether "file received notification" needs to be sent, and the like.
Fig. 7 schematically shows a block diagram of a traffic processing device according to an embodiment of the present disclosure.
As shown in fig. 7, the service processing apparatus 700 includes a first sending module 710, an obtaining module 720, and a second sending module 730.
The first sending module 710 is configured to send a first service file to a first target directory of a first partner terminal based on a preset communication protocol.
The obtaining module 720 is configured to obtain a file transmission status identifier configured in a preset communication protocol.
The second sending module 730 is configured to send the first notification packet to the first partner terminal when the file transmission status identifier indicates that the file transmission status identifier has been successfully sent.
According to the embodiment of the disclosure, after the first service file is sent by using the preset communication protocol, because the preset communication protocol is internally provided with the file transmission state identifier for indicating whether the file is sent outwards, whether the first service file is sent or not can be analyzed according to the state of the identifier, and when the file is determined to be sent, a notification message is sent to the target terminal to inform the target terminal that the file is sent. By the technical means, the technical problem that whether the file is sent or not cannot be sensed after a file sender sends the file in the related technology, so that the continuity of the service is poor is solved, the processing efficiency of the file is effectively improved, and the overall continuity of the service is improved.
According to the embodiment of the present disclosure, the service processing apparatus 700 further includes a first receiving module and a third sending module.
The first receiving module is configured to receive a first feedback packet from a first partner terminal, where the first feedback packet is generated by the first partner terminal according to a first notification packet.
And the third sending module is configured to send the first service file to the first target directory of the first partner terminal under the condition that the first feedback packet carries feedback information indicating that the first service file is not received.
According to the embodiment of the present disclosure, the first feedback packet further carries first directory path information.
According to the embodiment of the present disclosure, the service processing apparatus 700 further includes a first comparing module, a first determining module, and a fourth sending module.
And the first comparison module is used for comparing the first directory path information with the path information represented by the first target directory to obtain a first comparison result.
And the first determining module is used for determining the second target directory based on the first directory path information under the condition that the first comparison result shows that the first directory path information is inconsistent with the path information shown by the first target directory.
And the fourth sending module is used for sending the first service file to the second target directory of the first partner terminal.
According to an embodiment of the present disclosure, the service processing apparatus 700 further includes a second receiving module and a first pulling module.
And the second receiving module is used for receiving a second notification message from the second partner terminal.
And the first pulling module is used for pulling the second service file from a third target directory of the second partner terminal based on a preset communication protocol under the condition that the second notification message carries information indicating that the file is ready.
According to the embodiment of the present disclosure, the service processing apparatus 700 further includes a second determining module and a fifth sending module.
And the second determining module is used for determining the receiving state of the second service file in response to a preset event triggered, wherein the preset event comprises that the time length after the second notification message is received reaches the preset time length, or a third notification message from the second partner terminal is received.
And the fifth sending module is used for sending a second feedback message generated based on the receiving state of the second service file to the second partner terminal.
According to an embodiment of the present disclosure, the service processing apparatus 700 further includes a second pulling module.
And the second pulling module is used for pulling the second service file from the third target directory of the second partner terminal under the condition that the receiving state of the second service file is indicated as not received completely.
According to the embodiment of the present disclosure, the second notification message further carries second directory path information.
According to the embodiment of the present disclosure, the service processing apparatus 700 further includes a second comparing module, a third determining module, and a third pulling module.
And the second comparison module is used for comparing the second directory path information with the path information represented by the third target directory to obtain a second comparison result.
And the third determining module is used for determining a fourth target directory based on the second directory path information under the condition that the second comparison result shows that the second directory path information is inconsistent with the path information shown by the third target directory.
And the third pulling module is used for pulling the second service file from a fourth target directory of the second partner terminal.
Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.
For example, any plurality of the first sending module 710, the obtaining module 720 and the second sending module 730 may be combined and implemented in one module/unit/sub-unit, or any one of the modules/units/sub-units may be split into a plurality of modules/units/sub-units. Alternatively, at least part of the functionality of one or more of these modules/units/sub-units may be combined with at least part of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to an embodiment of the present disclosure, at least one of the first sending module 710, the obtaining module 720 and the second sending module 730 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware and firmware, or in a suitable combination of any of them. Alternatively, at least one of the first sending module 710, the obtaining module 720 and the second sending module 730 may be at least partially implemented as a computer program module, which when executed, may perform a corresponding function.
It should be noted that, in the embodiment of the present disclosure, the service processing apparatus portion corresponds to the service processing method portion in the embodiment of the present disclosure, and the description of the service processing apparatus portion specifically refers to the service processing method portion, which is not described herein again.
Fig. 8 schematically shows a block diagram of an electronic device adapted to implement a traffic processing method according to an embodiment of the present disclosure. The electronic device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 8, a computer electronic device 800 according to an embodiment of the present disclosure includes a processor 801 which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. The processor 801 may include, for example, a general purpose microprocessor (e.g., CPU), an instruction set processor and/or related chip sets and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 801 may also include on-board memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flows according to embodiments of the present disclosure.
In the RAM 803, various programs and data necessary for the operation of the electronic apparatus 800 are stored. The processor 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. The processor 801 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 802 and/or the RAM 803. Note that the programs may also be stored in one or more memories other than the ROM 802 and RAM 803. The processor 801 may also perform various operations of method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.
According to an embodiment of the present disclosure, the method flow according to an embodiment of the present disclosure may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer-readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program, when executed by the processor 801, performs the above-described functions defined in the system of the embodiments of the present disclosure. The above described systems, devices, apparatuses, modules, units, etc. may be implemented by computer program modules according to embodiments of the present disclosure.
The present disclosure also provides a computer-readable storage medium, which may be embodied in the device/apparatus/system described in the above embodiments; or may exist alone without being assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to an embodiment of the present disclosure, the computer readable storage medium may be a non-volatile computer readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 802 and/or RAM 803 described above and/or one or more memories other than the ROM 802 and RAM 803.
Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method provided by the embodiments of the present disclosure, when the computer program product is run on an electronic device, the program code being configured to cause the electronic device to implement the business processing method provided by the embodiments of the present disclosure.
The computer program, when executed by the processor 801, performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure. The above described systems, devices, modules, units, etc. may be implemented by computer program modules according to embodiments of the present disclosure.
In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted in the form of a signal on a network medium, distributed, downloaded and installed via communication section 809, and/or installed from removable media 811. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.
Claims (11)
1. A service processing method comprises the following steps:
based on a preset communication protocol, sending a first service file to a first target directory of a first partner terminal;
acquiring a file transmission state identifier configured in the preset communication protocol; and
and sending a first notification message to the first partner terminal under the condition that the file transmission state identifier shows that the file transmission state identifier is successfully sent.
2. The method of claim 1, further comprising:
receiving a first feedback message from the first partner terminal, wherein the first feedback message is generated by the first partner terminal according to the first notification message; and
and sending the first service file to a first target directory of the first partner terminal under the condition that the first feedback message carries feedback information indicating that the first service file is not received.
3. The method according to claim 2, wherein the first feedback message further carries first directory path information;
the method further comprises the following steps:
comparing the first directory path information with the path information represented by the first target directory to obtain a first comparison result;
determining a second target directory based on the first directory path information when the first comparison result indicates that the first directory path information is inconsistent with the path information indicated by the first target directory; and
and sending the first service file to a second target directory of the first partner terminal.
4. The method of claim 1, further comprising:
receiving a second notification message from a second partner terminal; and
and pulling a second service file from a third target directory of the second partner terminal based on the preset communication protocol under the condition that the second notification message carries information indicating that the file is ready.
5. The method of claim 4, further comprising:
responding to a trigger preset event, and determining a receiving state of the second service file, wherein the preset event comprises that the time length after the second notification message is received reaches a preset time length, or a third notification message from the second partner terminal is received; and
and sending a second feedback message generated based on the receiving state of the second service file to the second partner terminal.
6. The method of claim 5, further comprising:
and pulling the second service file from a third target directory of the second partner terminal under the condition that the receiving state of the second service file indicates that the second service file is not received completely.
7. The method according to claim 4, wherein the second notification message further carries second directory path information;
the method further comprises the following steps:
comparing the second directory path information with the path information represented by the third target directory to obtain a second comparison result;
determining a fourth target directory based on the second directory path information when the second comparison result indicates that the second directory path information is inconsistent with the path information indicated by the third target directory; and
and pulling the second service file from a fourth target directory of the second partner terminal.
8. A traffic processing apparatus, comprising:
the first sending module is used for sending a first service file to a first target directory of a first partner terminal based on a preset communication protocol;
the acquisition module is used for acquiring a file transmission state identifier configured in the preset communication protocol; and
and the second sending module is used for sending a first notification message to the first partner terminal under the condition that the file transmission state identifier shows that the file transmission state identifier is successfully sent.
9. An electronic device, comprising:
one or more processors;
a memory to store one or more instructions that,
wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 7.
11. A computer program product comprising computer executable instructions for implementing the method of any one of claims 1 to 7 when executed.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210352860.6A CN114793232B (en) | 2022-04-01 | 2022-04-01 | Service processing method, device, electronic equipment and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210352860.6A CN114793232B (en) | 2022-04-01 | 2022-04-01 | Service processing method, device, electronic equipment and storage medium |
Publications (2)
Publication Number | Publication Date |
---|---|
CN114793232A true CN114793232A (en) | 2022-07-26 |
CN114793232B CN114793232B (en) | 2024-02-06 |
Family
ID=82462565
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202210352860.6A Active CN114793232B (en) | 2022-04-01 | 2022-04-01 | Service processing method, device, electronic equipment and storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114793232B (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN116192672A (en) * | 2022-12-16 | 2023-05-30 | 中国联合网络通信集团有限公司 | Script viewing method and related equipment |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110060789A1 (en) * | 2009-09-04 | 2011-03-10 | Hong Fu Jin Precision Industry (Shenzhen) Co., Ltd | File transfer security system and method |
CN102082809A (en) * | 2009-11-26 | 2011-06-01 | 中国移动通信集团公司 | Document transmission method, server and control system |
CN104333583A (en) * | 2014-10-27 | 2015-02-04 | 广州酷狗计算机科技有限公司 | Document transmission method and device |
CN108984560A (en) * | 2017-06-01 | 2018-12-11 | 杭州海康威视数字技术股份有限公司 | File memory method and device |
CN111371898A (en) * | 2020-03-13 | 2020-07-03 | 北京锐安科技有限公司 | Message monitoring method, device, equipment and storage medium |
CN114168549A (en) * | 2021-12-10 | 2022-03-11 | 中国建设银行股份有限公司 | File processing method and device |
-
2022
- 2022-04-01 CN CN202210352860.6A patent/CN114793232B/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110060789A1 (en) * | 2009-09-04 | 2011-03-10 | Hong Fu Jin Precision Industry (Shenzhen) Co., Ltd | File transfer security system and method |
CN102082809A (en) * | 2009-11-26 | 2011-06-01 | 中国移动通信集团公司 | Document transmission method, server and control system |
CN104333583A (en) * | 2014-10-27 | 2015-02-04 | 广州酷狗计算机科技有限公司 | Document transmission method and device |
CN108984560A (en) * | 2017-06-01 | 2018-12-11 | 杭州海康威视数字技术股份有限公司 | File memory method and device |
CN111371898A (en) * | 2020-03-13 | 2020-07-03 | 北京锐安科技有限公司 | Message monitoring method, device, equipment and storage medium |
CN114168549A (en) * | 2021-12-10 | 2022-03-11 | 中国建设银行股份有限公司 | File processing method and device |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN116192672A (en) * | 2022-12-16 | 2023-05-30 | 中国联合网络通信集团有限公司 | Script viewing method and related equipment |
Also Published As
Publication number | Publication date |
---|---|
CN114793232B (en) | 2024-02-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10915384B2 (en) | Information processing method and device | |
US20230362122A1 (en) | Watermark-based message queue | |
CN112953769B (en) | Data transmission method, device, computer system and readable storage medium | |
CN113297163B (en) | Inquiry transfer system, method, device, equipment and medium based on block chain | |
JP2020198636A (en) | System and method for efficient call processing | |
CN111950249B (en) | Message generation method and device, electronic equipment and storage medium | |
US10425778B2 (en) | Distributed transactions on mobile devices via a messaging service provided by a mobile network operator | |
CN110618768B (en) | Information presentation method and device | |
CN114793232B (en) | Service processing method, device, electronic equipment and storage medium | |
CN113132400B (en) | Business processing method, device, computer system and storage medium | |
WO2023246480A1 (en) | Identity authentication method and apparatus, device, medium and product | |
US9130881B2 (en) | Direct return to source (DRS) routing of customer information control systems (CICS) transactions | |
CN114257632B (en) | Method and device for reconnecting broken wire, electronic equipment and readable storage medium | |
CN115934378A (en) | Service data processing method and device, electronic equipment and storage medium | |
CN113079085B (en) | Business service interaction method, business service interaction device, business service interaction equipment and storage medium | |
CN113783666A (en) | Method and device for processing service | |
CN113157461A (en) | Method and device for transmitting message in process of executing task list | |
CN110430256B (en) | Method, device and computer system for pushing transaction message | |
US8738049B1 (en) | Converged dialog in hybrid mobile applications | |
CN115174588B (en) | Bandwidth control method, device, apparatus, storage medium and program product | |
US20240152504A1 (en) | Data interaction method, apparatus, and electronic device | |
CN115203334A (en) | Data processing method and device, electronic equipment and storage medium | |
CN114090134A (en) | Data interaction method and device, storage medium and electronic equipment | |
CN115842691A (en) | Message sequence guarantee method, device and equipment for distributed group communication | |
CN114513548A (en) | Directional call information processing method and device |
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 |