CN113114757A

CN113114757A - File transmission method, device and equipment

Info

Publication number: CN113114757A
Application number: CN202110381040.5A
Authority: CN
Inventors: 朱江; 徐壮; 严祖洋; 甘文翠
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-04-09
Filing date: 2021-04-09
Publication date: 2021-07-13
Anticipated expiration: 2041-04-09
Also published as: CN113114757B

Abstract

The embodiment of the specification provides a file transmission method, a file transmission device and file transmission equipment, and relates to the technical field of big data, wherein the method comprises the following steps: acquiring registration information of a plurality of service files to be sent; creating at least one sending file queue by using the registration information of each service file to be sent; acquiring file configuration information of a target interface corresponding to each target service file to be sent; the target business file to be sent is a business file with sending conditions in a sending file queue, and the target interface is an interface corresponding to a receiver of the target business file to be sent; converting the target service file to be sent into a target interface file matched with a target interface based on the file configuration information of the target interface; and transmitting the target interface file to the target interface. In the embodiment of the present specification, queuing management can be performed on the service files to be sent, so that the sending efficiency of the files is effectively improved, and differentiated requirements of different mechanisms can be flexibly met.

Description

File transmission method, device and equipment

Technical Field

The embodiment of the specification relates to the technical field of big data, in particular to a file transmission method, device and equipment.

Background

In the field of big data, various business functions in a bank system are gradually developed in the direction of file interface interaction and automation processing. However, since each organization related to each business function performs business development on its own based on the national standard standards issued by the ministry of human society, there is a difference in the configuration of interface files among the organizations.

In the prior art, a file timing scanning task is usually performed to convert a data file by using a single point of a database server, so as to convert service data into interface data meeting the requirements of an interface file. When the amount of files to be transmitted is large, it takes a lot of time to process data, and thus data transmission cannot be performed in time. Therefore, by adopting the technical scheme in the prior art, the differentiation requirements of different mechanisms on interface files cannot be efficiently met during data transmission.

In view of the above problems, no effective solution has been proposed.

Disclosure of Invention

The embodiment of the specification provides a file transmission method, a file transmission device and file transmission equipment, and aims to solve the problem that the differential requirements of different mechanisms on interface files cannot be met efficiently during data transmission in the prior art.

An embodiment of the present specification provides a file transmission method, including: acquiring registration information of a plurality of service files to be sent; creating at least one sending file queue by using the registration information of each service file to be sent; acquiring file configuration information of a target interface corresponding to each target service file to be sent; the target to-be-sent service file is a service file with sending conditions in the at least one sending file queue, and the target interface is an interface corresponding to a receiver of the target to-be-sent service file; converting the target to-be-sent service file into a target interface file matched with the target interface based on the file configuration information of the target interface; and transmitting the target interface file to the target interface.

An embodiment of the present specification further provides a file transfer apparatus, including: the first acquisition module is used for acquiring registration information of a plurality of service files to be sent; the creating module is used for creating at least one sending file queue by utilizing the registration information of each service file to be sent; the second acquisition module is used for acquiring file configuration information of a target interface corresponding to each target service file to be sent; the target to-be-sent service file is a service file with sending conditions in the at least one sending file queue, and the target interface is an interface corresponding to a receiver of the target to-be-sent service file; the conversion module is used for converting the target service file to be sent into a target interface file matched with the target interface based on the file configuration information of the target interface; and the transmission module is used for transmitting the target interface file to the target interface.

The embodiment of the specification also provides a file transmission device which comprises a processor and a memory for storing processor executable instructions, wherein the processor executes the instructions to realize the steps of the file transmission method.

The present specification also provides a computer readable storage medium, on which computer instructions are stored, and when executed, the instructions implement the steps of the file transmission method.

The embodiment of the present specification provides a file transmission method, which can create at least one sending file queue based on acquired registration information of a plurality of service files to be sent. The file configuration information of a target interface corresponding to a target to-be-sent service file with sending conditions in a file sending queue can be acquired, wherein the target interface is an interface corresponding to a receiver of the target to-be-sent service file. Therefore, the target to-be-sent service file can be converted into a target interface file matched with the target interface based on the file configuration information of the target interface, and the target interface file is transmitted to the target interface. The method can effectively improve the file sending efficiency and reduce the coupling of the system by carrying out queuing management on the service files to be sent. Furthermore, the file configuration information of the interface is formed by parameterizing the requirement information of the interface of each mechanism for the file, so that the differential requirements of different mechanisms can be flexibly met.

Drawings

The accompanying drawings, which are included to provide a further understanding of the embodiments of the disclosure, are incorporated in and constitute a part of this specification, and are not intended to limit the embodiments of the disclosure. In the drawings:

FIG. 1 is a schematic diagram illustrating steps of a file transfer method according to an embodiment of the present disclosure;

FIG. 2 is a schematic diagram of an annuity fund operation system according to an embodiment of the present disclosure;

FIG. 3 is a schematic structural diagram of a file transfer device provided in an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of a file transfer device provided in an embodiment of the present specification.

Detailed Description

The principles and spirit of the embodiments of the present specification will be described with reference to a number of exemplary embodiments. It should be understood that these embodiments are presented merely to enable those skilled in the art to better understand and to implement the embodiments of the present description, and are not intended to limit the scope of the embodiments of the present description in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

As will be appreciated by one skilled in the art, implementations of the embodiments of the present description may be embodied as a system, an apparatus, a method, or a computer program product. Therefore, the disclosure of the embodiments of the present specification can be embodied in the following forms: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

Although the flow described below includes operations that occur in a particular order, it should be appreciated that the processes may include more or less operations that are performed sequentially or in parallel (e.g., using parallel processors or a multi-threaded environment).

Referring to fig. 1, the present embodiment can provide a file transmission method. The file transmission method can be used for efficiently transmitting files among different mechanisms. The above file transfer method may include the following steps.

S101: and acquiring registration information of a plurality of service files to be sent.

In this embodiment, a plurality of service file registration information to be sent can be obtained. After the service personnel complete the relevant service in the service operation system, the system can trigger the registration of the sending file. The registration information may include a plurality of parameters that may identify a service file to be sent, and a sender and a receiver of the plurality of service files to be sent may be different entities.

In the embodiment, the data file registration can be realized in an asynchronous service mode, so that the process of an operation system can not be blocked, and the system coupling is reduced. The parameter fields included in the above-described registration information may be as shown in table 1.

TABLE 1

In this embodiment, the extended information field in table 1 may be a field reserved during file registration, so that the file information extended field may be extended by rewriting the file registration method in the following process to meet different scene needs. It is understood that table 1 is only one example of registration information, which may also contain other parameters, such as: the transmission state, the transmission time, the file version, and the like may be determined according to actual conditions, and this is not limited in this embodiment of the present specification.

In this embodiment, the manner of acquiring the registration information of the multiple service files to be sent may include: and pulling the data from a preset database, or inquiring according to a preset path. It is to be understood that, the registration information of the service file to be sent may also be obtained in other possible manners, for example, the registration information of the service file to be sent input by a service person is received, which may be determined according to actual situations, and this is not limited in this description embodiment.

S102: and creating at least one sending file queue by using the registration information of each service file to be sent.

In this embodiment, at least one sending file queue may be created by using the registration information of each service file to be sent. Therefore, each service file to be sent can be managed in a queue mode, and system coupling is reduced. The sending file queues can be independent from each other, so that the service files to be sent in the sending file queues can be processed simultaneously in parallel, and the file sending efficiency is improved.

In this embodiment, the dependency relationship between the service files to be sent can be determined according to the registration information of each service file to be sent, the service files to be sent without the dependency relationship can be placed in different file sending queues, and the service files to be sent with the dependency relationship can be placed in the same file queue. In some cases, limited by the number of file queues, service files to be sent without dependency relationship may also be placed in the same file sending queue, which may be determined according to actual situations, and this is not limited in this description embodiment.

In this embodiment, the sending priority of each service file to be sent in the same sending file queue may be determined according to the registration information of each service file to be sent. In some embodiments, the file sending priority may be set according to the file date, sending file sequence number ascending order; priorities may also be set according to the business nature of the file, for example: higher priority can be set for the batch processing with higher requirement on the real-time performance, and lower priority can be set for the batch processing at the end of the day. Of course, the manner of setting the priority is not limited to the above examples, and other modifications may be made by those skilled in the art within the spirit of the embodiments of the present disclosure, but the function and effect of the embodiments of the present disclosure are also within the scope of the embodiments of the present disclosure.

In this embodiment, the file sending queue may only record identification information of the service file to be sent, where the identification information may be used to uniquely identify the service file to be sent, and other information of the service file to be sent may be queried from a preset database according to the identification information. The service file identification information to be sent can be a sending file serial number generated during registration, and the sending file serial number can be used for representing the registration sequence of the service file to be sent and has uniqueness, so that the sending file serial number can be used as a unique identification during the file sending process, and a higher sending priority can be allocated to the sending file serial number in the first place.

In this embodiment, other redundant information of the service file to be sent may also be recorded in the file sending queue, so as to perform operations such as querying the service file to be sent subsequently. The other redundant information of the service file to be transmitted may include at least one of the following: sending organization, receiving organization, file date, business name, etc. It is understood that the above-mentioned other redundant information of the service file to be sent may also include other information, for example: the specific details of the annual fund authority code, plan, and the like may be determined according to actual conditions, and the embodiments of the present specification do not limit this.

S103: acquiring file configuration information of a target interface corresponding to each target service file to be sent; the target to-be-sent service file is a service file with sending conditions in at least one sending file queue, and the target interface is an interface corresponding to a receiver of the target to-be-sent service file.

In this embodiment, file configuration information of a target interface corresponding to each target to-be-sent service file can be obtained; the target to-be-sent service file is a service file with sending conditions in at least one sending file queue, and the target interface is an interface corresponding to a receiver of the target to-be-sent service file.

In this embodiment, since the transmission and reception of the file between the two mechanisms need to be realized through the interface, different interfaces have different requirements for the format of the file, the parameter information included therein, and the like. Therefore, the requirement information of the interface of each mechanism for the file can be parameterized to form the file configuration information of each interface. Furthermore, the file configuration information of each interface can be stored in a preset database so as to be obtained in time.

In this embodiment, the file configuration information may include two pieces of configuration information: configuration information of a technical layer and configuration information of a service layer. Because the data file can relate to different encryption modes and different verification processes, technical parameters can be configured for ensuring the safety and the integrity of the data file; to convert a file into data that can be recognized by an interface, file configuration parameters may be set.

In this embodiment, the file configuration parameters may include: file information configuration and file field configuration. In some embodiments, the file information configuration and the file field configuration may be as shown in tables 2 and 3, respectively.

TABLE 2

file_id	File id
		status_type	Qualification type
agency_code	Organization code
		oam_tran_id	Type of transaction
forward_type	Direction of transmission
		file_version	Version type
file_type	File form
		deal_time	Processing time point
status_own	I go to role
		send_level	Interface transmit granularity
extend	Extension field

TABLE 3

file_id	File id
		field_name	Name of field
field_seq	Order of fields
		field_desc	Description of Chinese
field_type	Type (B)
		field_leng	Length of
field_memo	Remarks for note
		field_need	Whether or not it is necessary to
rule	Specific rule content
		extend	Extension field

In this embodiment, tables 2 and 3 are only examples of the configuration of the file information and the configuration of the file field in a specific scenario, and the configuration of the file information and the configuration of the file field may further include other parameters, such as: the interface type and the like can be determined according to actual situations, and the embodiment of the present specification does not limit this.

In this embodiment, whether a currently transmittable target service file to be transmitted exists in the transmission file queue may be determined according to a preset time interval, and file configuration information of a target interface corresponding to the target service files to be transmitted may be obtained in a case that the currently transmittable target service file exists. The number of the target service files to be sent may be one or multiple, and may be determined according to actual conditions, which is not limited in the embodiments of the present specification.

In this embodiment, when there are a plurality of target to-be-sent service files, it indicates that there are a plurality of file sending tasks, and at this time, the file configuration information of the target interface corresponding to each target to-be-sent service file can be respectively obtained in parallel by using a plurality of distributed nodes, so that the file sending efficiency can be improved.

S104: and converting the target service file to be sent into a target interface file matched with the target interface based on the file configuration information of the target interface.

In this embodiment, the target to-be-sent service file can be converted into a target interface file matched with the target interface based on the file configuration information of the target interface, so that the converted file can meet the requirement of a receiver.

In this embodiment, since the service data corresponding to the target service file to be sent is not recorded in the transmission file queue, the service data corresponding to the target service file to be sent can be queried from the preset database according to the identification information of the target service file to be sent recorded in the transmission file queue, so that the conversion from the service data to the interface data is completed, and the target interface file is generated.

S105: and transmitting the target interface file to the target interface.

In this embodiment, the target interface file obtained by conversion may be transmitted to the target interface, so as to complete the transmission of the target to-be-transmitted service file.

In this embodiment, since data transmission between different organizations is performed by means of interaction with a file transmission platform of a third party, the transmitting and receiving parties agree on a file transmission rule, and set up on the file transmission platform of the third party to specify respective transmitting and receiving paths. The target interface file can be pushed to a sending directory specified by the transmission platform, and the transmission platform can transmit the target interface file to a corresponding directory of a receiver mechanism at regular time according to an agreed transmission rule.

From the above description, it can be seen that the embodiments of the present specification achieve the following technical effects: at least one sending file queue can be created based on the acquired registration information of a plurality of service files to be sent. The file configuration information of the target interface corresponding to the target to-be-sent service file with the sending condition in the file sending queue can be obtained, wherein the target interface is an interface corresponding to a receiver of the target to-be-sent service file. Therefore, the target to-be-sent service file can be converted into a target interface file matched with the target interface based on the file configuration information of the target interface, and the target interface file is transmitted to the target interface. The method can effectively improve the file sending efficiency and reduce the coupling of the system by carrying out queuing management on the service files to be sent. Furthermore, the file configuration information of the interface is formed by parameterizing the requirement information of the interface of each mechanism for the file, so that the differential requirements of different mechanisms can be flexibly met.

In an embodiment, creating at least one transmission file queue according to the registration information of each service file to be transmitted may include: determining the number of a transmission file queue and the corresponding relation between the service file to be transmitted and the transmission file queue according to the registration information of each service file to be transmitted; wherein, the registration information at least comprises: the file sequence number is sent. The characteristic information of each service file to be sent can be obtained according to the registration information of each service file to be sent. And determining the transmission priority of each service file to be transmitted according to the characteristic information of each service file to be transmitted and the corresponding relation between the service file to be transmitted and the transmission file queue. Furthermore, at least one sending file queue can be created according to the determined number and the corresponding relation of the sending file queues and the sending priority of each service file to be sent; each transmission file queue comprises at least one transmission file serial number of the service file to be transmitted, which is arranged according to the ascending order of the transmission priority.

In this embodiment, the feature information of each service file to be sent can be obtained according to the registration information of each service file to be sent, and the feature information can be information for representing features such as attributes of the service file to be sent. Furthermore, the dependency relationship between the service files to be sent can be determined according to the characteristic information of the service files to be sent, and then the number of the sending file queues and the corresponding relationship between the service files to be sent and the sending file queues can be determined, so that the sending file queues can be divided according to the characteristic information of the service files to be sent.

In this embodiment, the to-be-sent service files without dependency relationship may be placed in different file sending queues, and the to-be-sent service files with dependency relationship may be placed in the same file queue. In some cases, limited by the number of file queues, service files to be sent without dependency relationship may also be placed in the same file sending queue, which may be determined according to actual situations, and this is not limited in this description embodiment. In one embodiment, 4 service files to be sent are received: 1-a01_ T06_20210326_01_ planA _ coc.zip; 2-a01_ T06_20210326_02_ planA _ cod. zip; 3-C01_ T06_20210326_01_ plana. zip; 4-C01_ T06_20210326_02_ planA. zip, since there is a dependency between file 3 and file 4, they can be put into 3 queues respectively: A-File 1; B-File 2; C-File 3, File 4. Files 1, 2, and 3 may be processed by the consuming nodes at the same time, and file 4 needs to be distributed after file 3 is processed.

In the present embodiment, the characteristic information may be as shown in table 4.

TABLE 4

id	File code
		fund_code	Annuity fund management organization code
file_date	Date of document
		file_seq	File serial number
file_version	Version number: 1, v 1.0; 2, v2.0
		file_type	File type
if_type	Interface type (1 personage, 2 plan, 3 enterprise)
		if_id	Personalised, planned, enterprise coding
insert_time	Insertion time
		insert_user	Plug-in user
update_time	Update time
		update_user	Updating a user

In this embodiment, table 4 is only an example of feature information in a specific scenario, and the feature information may further include other parameters, for example: the generation date and the like may be determined in accordance with actual circumstances, and the present embodiment is not limited thereto.

In this embodiment, only the transmission priority between the service files to be sent in the same transmission file queue may be set, and there is no need to set the transmission priority between the service files to be sent in different transmission file queues. The sending priority can be set according to the ascending order of the file date and the serial number of the sent file so as to ensure the order of the business process. In some special scenarios, the setting rule of the priority may be specifically set according to the service requirement, and may be specifically determined according to the actual situation, which is not limited in this description embodiment.

In this embodiment, the file name of each service file to be sent may be recorded according to a preset format, for example: the name is named according to file source + annuity fund management mechanism + interface type + persona + plan + enterprise code, or the name is named according to sending mechanism _ receiving mechanism _ file date _ sending file serial number _ assignee annuity plan code _ enterprise name, which can be determined according to actual conditions, and is not limited in the embodiments of the present specification. Thus, in some embodiments, priority may also be determined by sorting file names in ascending order.

In this embodiment, the actual service data corresponding to the service file to be sent may not be stored in the transmission file queue, and only the transmission file sequence number of at least one service file to be sent, which is arranged in ascending order according to the transmission priority, may be recorded. When the service data or other information of the service file to be sent needs to be used subsequently, the service data or other information of the service file to be sent can be inquired from the preset database according to the serial number of the service file to be sent.

In this embodiment, related rules can be customized and extended according to specific needs, and if needed, in the same queue, the sending of the next data file can be triggered only after the previous file sent receives the feedback from the opposite mechanism, and the implementation can be realized by updating the "sending state" of the service file to be sent in the queue at regular time.

In one embodiment, the registration information may further include: the at least one extension field, after creating the at least one send file queue, may further include: and generating a sending file queue view according to at least one sending file queue. Further, when it is determined that the target service file to be sent in the transmission file queue needs to be adjusted according to the transmission file queue view, the registration information of the target service file to be sent can be rewritten based on the extension field in the registration information.

In the embodiment, the queue view can be displayed to the service personnel, so that the current state of each service file to be sent can be visually seen. Therefore, business personnel can inquire and adjust based on the queue view, manual adjustment of the queue sequence can be supported, system coupling is effectively reduced, and the requirements of various scenes are better met.

In this embodiment, when it is determined that the target service file to be sent in the file sending queue needs to be adjusted, the registration information of the target service file to be sent may be rewritten based on the extension field in the registration information. In some embodiments, the method can also support the self-defining of the sending queue creation and priority adjustment rule by rewriting the isend qservice.

In one embodiment, the sending file queue may include a sending file serial number, a sending priority, and a sending status of a service file to be sent, and the obtaining of the file configuration information of the target interface corresponding to each target service file to be sent may include: screening a target service file to be sent with sending conditions from at least one file sending queue by using a structured query statement; and the sending condition is that the sending state is to be sent and the sending priority is highest in the queue. Further, a target interface corresponding to the target service file to be sent can be determined based on the serial number of the transmission file of the target service file to be sent, and file configuration information of the target interface can be obtained.

In this embodiment, the consuming node of the sending file queue may determine, by using the timing task, a target to-be-sent service file that can be currently sent in each sending file queue. The service file with the current transmission condition can be determined by combining the transmission state and the transmission priority recorded in the transmission file queue, the service file with the transmission state to be transmitted and the transmission priority being the highest in the queue can be used as a target service file to be transmitted, and one target service file to be transmitted can be used as a transmission task. When the target service file to be sent is consumed, the file state can be updated to be in processing, the sending state is recorded and updated at regular time, and the file can be effectively prevented from being repeatedly consumed.

In this embodiment, how to have no dependency relationship between two service files with adjacent priorities in the same queue, an asynchronous method may be used for processing. If the service file has the dependency relationship, the sending can be executed after waiting for the feedback result of the last service file.

In an embodiment, converting the target to-be-sent service file into a target interface file matched with the target interface based on the file configuration information of the target interface may include: and acquiring service data corresponding to the target service file to be sent by utilizing the distributed nodes according to the sending file serial number of each target service file to be sent. And converting the service data corresponding to the target to-be-sent service file into interface data matched with the target interface by using the file configuration information of the target interface based on the plurality of distributed nodes. Furthermore, a plurality of distributed nodes can be utilized to preprocess interface data to obtain a target interface file; wherein the pretreatment comprises: and (5) encrypting and compressing.

In this embodiment, in order to improve the processing efficiency, a plurality of distributed nodes may be used to process and send different target service files to be sent, respectively. Because actual service data are not stored in the transmission file queue, the service data corresponding to the target service file to be transmitted can be inquired and obtained from a preset database according to the transmission file serial number of the target service file to be transmitted.

In this embodiment, the interface data obtained by conversion may be further encrypted, compressed, and the like, so as to ensure the security and integrity of the data file in the process of transmitting the target interface file to the receiving party. The encryption mode may be determined according to the standard requirement of the docking, and this is not limited in this embodiment of the specification.

In one embodiment, transferring the target interface file to the target interface may include: and pushing the target interface file to a preset sending directory, and pushing the target interface file in the sending directory to a target directory corresponding to the target interface by utilizing a timing task.

In this embodiment, since data transmission between different organizations is performed by means of interaction with a file transmission platform of a third party, the transmitting and receiving parties agree on a file transmission rule, and set up on the file transmission platform of the third party to specify respective transmitting and receiving paths. The target interface file can be pushed to a sending directory specified by the transmission platform, and the transmission platform can transmit the target interface file to a target directory corresponding to an interface of a receiver mechanism at regular time according to an agreed transmission rule.

In one embodiment, after transferring the target interface file to the target interface, the method may further include: and traversing the target directory corresponding to the target interface according to a preset time interval to obtain a plurality of files to be processed. Acquiring the characteristic information of a plurality of files to be processed, and creating at least one file queue to be processed according to the characteristic information of the plurality of files to be processed; the file queue to be processed comprises the processing priority and the processing state of the file to be processed. Further, a target file to be processed with processing conditions can be screened from at least one file queue to be processed by using a structured query statement; wherein the processing condition is that the processing state is pending and the processing priority is highest in the queue. The file configuration information of the interface corresponding to the target file to be processed can be acquired, the target file to be processed is converted into corresponding service data based on the file configuration information of the interface corresponding to the target file to be processed, and the service processing can be performed by utilizing the service data corresponding to the target file to be processed.

In this embodiment, the received target interface files may be collectively stored in the target directory by using distributed file sharing storage. Specifically, file sharing of the distributed system can be achieved by means of hanging the disk, and each distributed node can perform read-write operation on the disk.

In this embodiment, the timing task may traverse the target directory corresponding to the target interface at preset time intervals to obtain a plurality of received files, which may be used as files to be processed, and may move the plurality of files to be processed to the directory to be processed. The preset time interval may be 0.5 second, or 1 second, 2 seconds, or the like, and may be determined according to actual conditions, which is not limited in the embodiments of the present specification.

In the embodiment, the to-be-processed files newly added into the to-be-processed file queue can be labeled, mapped to information such as character persons, plans, enterprises and the like in the system according to the characteristic information of the to-be-processed files, and subjected to preliminary analysis and verification, so that the to-be-processed files are preliminarily screened and sorted, and the organization work of the queue processing sequence is completed. Specifically, the dependency relationship between the files to be processed can be determined according to the characteristic information of the files to be processed, and then the number of the file queues to be processed and the corresponding relationship between the files to be processed and the file queues to be processed can be determined, so that the file queues to be processed can be divided according to the characteristic information of the files to be processed.

In this embodiment, the pending files without dependency relationship may be placed in different pending file queues, and the pending files with dependency relationship may be placed in the same pending file queue. In some cases, limited by the number of file queues, files to be processed without dependency relationship may also be placed in the same file sending queue, which may be determined according to actual situations, and this is not limited in this specification.

In this embodiment, the sending priority may be set according to the ascending order of the file date and the file sequence number to ensure the order of the business process. In some special scenarios, the setting rule of the priority may be specifically set according to the service requirement, and may be specifically determined according to the actual situation, which is not limited in this description embodiment. The file sequence number may be a transmission file sequence number in some embodiments, which may be determined according to actual situations, and the embodiment of the present disclosure does not limit this.

In this embodiment, when the queue to be processed needs to be adjusted, it may be supported to customize the queue creation and priority adjustment rule by rewriting the irevservice. In some special scenes, the extension field in the registration information can be expanded by rewriting the method of opmdtlerevqueueinf. In some embodiments, the front-end page may provide a related interface to query queue information, may present a queue view to business personnel, and supports manual update of file states and priorities to adjust the order of file processing, thereby more flexibly meeting the needs of different scenarios.

In this embodiment, the pending file queue may not store actual service data, and may record a file serial number of each pending file, so as to query other related data according to the file serial number.

In this embodiment, the consumption node of the file queue to be processed may determine, by using the timing task, a target file to be processed that can be currently processed in each file queue to be processed through the structured query statement. The file to be processed with the processing condition currently can be determined by combining the processing state and the processing priority recorded in the file queue to be processed, the file with the processing state to be processed and the highest processing priority in the queue to which the processing priority belongs can be used as a target file to be processed, and one target file to be processed can be used as a sending task.

In this embodiment, since the received file to be processed is an interface file, the format conversion from the interface file to the service data required for the service program processing can be completed based on the file configuration information of the interface corresponding to the target file to be processed. Furthermore, the service access work can be completed by calling the corresponding service interface, and various forms such as synchronous calling and asynchronous calling can be supported, so that the functional coupling is reduced.

In an embodiment, the file configuration information may include technical parameters and file configuration parameters, and convert the target file to be processed into corresponding service data based on the file configuration information of the interface corresponding to the target file to be processed, and may further include: preprocessing the target file to be processed based on technical parameters in the file configuration information of the interface corresponding to the target file to be processed; wherein the pretreatment comprises: decryption, decompression and parsing. Furthermore, the preprocessed target file to be processed can be converted into corresponding service data according to the file configuration parameters in the file configuration information of the interface corresponding to the target file to be processed.

In this embodiment, the decryption and decompression may be performed by configuring an algorithm type according to actual requirements, the corresponding password and key required for decryption may be read through configuration, and the parsing may be performed by obtaining a defined file field and length, and reading and parsing the content of the data file to form service data for storage.

In the embodiment, after the corresponding service data is converted, technical class verification can be performed on the service data, and if the technical class verification is correct, subsequent services can be further called to perform service processing, so that service access work is completed. The content of the technical class check may include: the file configuration can execute the type, length, dictionary and the like of data, and check are needed after the data is disassembled to ensure the validity of the data. For example: the fields of the numbers must not appear non-numeric and the date fields need to be legal.

In one scenario example, this may be applied to the transmission of an annuity trusted debit file. The annuity refers to a supplementary endowment insurance system established on the basis of basic endowment, and is mainly divided into two types, namely professional annuity of workers of organ and public institution and enterprise annuity established by enterprise workers voluntarily. The aim of annuity operation management is to realize the value preservation and increment of fund assets and provide endowment guarantee for beneficiaries, and a trustee undertakes the responsibility of managing and managing fund assets, needs to be linked with daily business with external mechanisms such as a trustee, an account manager, a cast manager and the like, and is the core of the whole annuity fund operation. Wherein the annuity fund operating system may be as shown in fig. 2.

In the present scenario example, the couple cases for each institution in the annuity fund operation system may be as shown in table 5.

TABLE 5

In this scenario example, the requirement information of each mechanism interface file in the system may be parameterized in advance to form a data file information base for subsequent query. Four roles can be included in the file transfer process: a pending file queue producer, a pending file queue consumer, a sending file queue producer, and a sending file queue consumer. The file queue producer node to be processed is used for traversing the target directory by using a timing task, moving the file to be processed to the directory to be processed, and creating a file queue to be processed according to characteristic information such as a file path, a file name and the like or adding the file queue to be processed to an existing queue.

In this scenario example, the to-be-processed file queue consumer is configured to utilize each service node to obtain a file processing task from the file receiving queue, decrypt, check, decompress, and analyze the received to-be-processed file according to file configuration information in the file information base, complete a form conversion operation from an interface file to service file stream data required by service program processing, and complete a service access operation (supporting multiple forms such as synchronous and asynchronous calls) by calling a corresponding service interface.

In this scenario example, the sending file queue producer is configured to, after triggering file receiving and sending registration in service operation, create at least one sending file queue for a file to be sent by a sending file queue producer node according to feature information of a service type, a receiving mechanism, a plan, an enterprise, and the like. In some scenes, a file before the queue can be controlled to obtain processing feedback of a receiving mechanism, and then a sending process of a next file is triggered, so that services are processed in order.

In this scenario, the sending file queue consumer node may obtain a file sending task from the sending file queue at regular time, and perform generation, assembly, compression, encryption, and signature verification of a data file according to file configuration information in the file information base, and finally push an interface file obtained by conversion to a corresponding directory and provide the interface file to an external mechanism.

In the scene example, the data files are managed in a queue mode, so that the system coupling is reduced; a queue view is provided, manual intervention adjustment is supported, and the requirements of various special scenes are better met; the self-defining of the queue rule is supported, and good queue expansibility can be provided; the characteristics of distributed service are fully utilized, the file queue processing can support transverse capacity expansion, and the interface processing efficiency is improved.

Based on the same inventive concept, the embodiment of the present specification further provides a file transmission device, such as the following embodiments. Because the principle of solving the problems of the file transmission device is similar to the file transmission method, the implementation of the file transmission device can refer to the implementation of the file transmission method, and repeated parts are not described again. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated. Fig. 3 is a block diagram of a structure of a file transfer device according to an embodiment of the present disclosure, and as shown in fig. 3, the file transfer device may include: a first obtaining module 301, a creating module 302, a second obtaining module 303, a converting module 304, and a transmitting module 305, and the structure will be described below.

A first obtaining module 301, configured to obtain registration information of a plurality of service files to be sent;

a creating module 302, configured to create at least one sending file queue by using registration information of each service file to be sent;

the second obtaining module 303 may be configured to obtain file configuration information of a target interface corresponding to each target to-be-sent service file; the target to-be-sent service file is a service file with sending conditions in at least one sending file queue, and the target interface is an interface corresponding to a receiver of the target to-be-sent service file;

the conversion module 304 may be configured to convert the target to-be-sent service file into a target interface file matched with the target interface based on the file configuration information of the target interface;

the transfer module 305 may be configured to transfer the destination interface file to the destination interface.

The embodiment of the present specification further provides an electronic device, which may specifically refer to a schematic structural diagram of an electronic device based on the file transmission method provided in the embodiment of the present specification, shown in fig. 4, where the electronic device may specifically include an input device 41, a processor 42, and a memory 43. The input device 41 may be specifically configured to input registration information of a plurality of service files to be sent. The processor 42 may be specifically configured to obtain registration information of a plurality of service files to be sent; creating at least one sending file queue by using the registration information of each service file to be sent; acquiring file configuration information of a target interface corresponding to each target service file to be sent; the target to-be-sent service file is a service file with sending conditions in at least one sending file queue, and the target interface is an interface corresponding to a receiver of the target to-be-sent service file; converting a target to-be-sent service file into a target interface file matched with a target interface based on the file configuration information of the target interface; and transmitting the target interface file to the target interface. The memory 43 may be specifically used for storing data such as a target interface file.

In this embodiment, the input device may be one of the main apparatuses for information exchange between a user and a computer system. The input devices may include a keyboard, mouse, camera, scanner, light pen, handwriting input panel, voice input device, etc.; the input device is used to input raw data and a program for processing the data into the computer. The input device can also acquire and receive data transmitted by other modules, units and devices. The processor may be implemented in any suitable way. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth. The memory may in particular be a memory device used in modern information technology for storing information. The memory may include multiple levels, and in a digital system, memory may be used as long as binary data can be stored; in an integrated circuit, a circuit without a physical form and with a storage function is also called a memory, such as a RAM, a FIFO and the like; in the system, the storage device in physical form is also called a memory, such as a memory bank, a TF card and the like.

In this embodiment, the functions and effects specifically realized by the electronic device can be explained by comparing with other embodiments, and are not described herein again.

Embodiments of the present specification further provide a computer storage medium based on a file transmission method, where the computer storage medium stores computer program instructions, and when the computer program instructions are executed, the computer storage medium may implement: acquiring registration information of a plurality of service files to be sent; creating at least one sending file queue by using the registration information of each service file to be sent; acquiring file configuration information of a target interface corresponding to each target service file to be sent; the target to-be-sent service file is a service file with sending conditions in at least one sending file queue, and the target interface is an interface corresponding to a receiver of the target to-be-sent service file; converting a target to-be-sent service file into a target interface file matched with a target interface based on the file configuration information of the target interface; and transmitting the target interface file to the target interface.

In this embodiment, the storage medium includes, but is not limited to, a Random Access Memory (RAM), a Read-Only Memory (ROM), a Cache (Cache), a Hard Disk Drive (HDD), or a Memory Card (Memory Card). The memory may be used to store computer program instructions. The network communication unit may be an interface for performing network connection communication, which is set in accordance with a standard prescribed by a communication protocol.

In this embodiment, the functions and effects specifically realized by the program instructions stored in the computer storage medium can be explained by comparing with other embodiments, and are not described herein again.

It will be apparent to those skilled in the art that the modules or steps of the embodiments of the present specification described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed over a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different from that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, embodiments of the present description are not limited to any specific combination of hardware and software.

Although the embodiments herein provide the method steps as described in the above embodiments or flowcharts, more or fewer steps may be included in the method based on conventional or non-inventive efforts. In the case of steps where no causal relationship is logically necessary, the order of execution of the steps is not limited to that provided by the embodiments of the present description. When the method is executed in an actual device or end product, the method can be executed sequentially or in parallel according to the embodiment or the method shown in the figure (for example, in the environment of a parallel processor or a multi-thread processing).

It is to be understood that the above description is intended to be illustrative, and not restrictive. Many embodiments and many applications other than the examples provided will be apparent to those of skill in the art upon reading the above description. The scope of embodiments of the present specification should, therefore, be determined not with reference to the above description, but should instead be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

The above description is only a preferred embodiment of the embodiments of the present disclosure, and is not intended to limit the embodiments of the present disclosure, and it will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present disclosure. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the embodiments of the present disclosure should be included in the protection scope of the embodiments of the present disclosure.

Claims

1. A method for file transfer, comprising:

acquiring registration information of a plurality of service files to be sent;

creating at least one sending file queue by using the registration information of each service file to be sent;

acquiring file configuration information of a target interface corresponding to each target service file to be sent; the target to-be-sent service file is a service file with sending conditions in the at least one sending file queue, and the target interface is an interface corresponding to a receiver of the target to-be-sent service file;

converting the target to-be-sent service file into a target interface file matched with the target interface based on the file configuration information of the target interface;

and transmitting the target interface file to the target interface.

2. The method of claim 1, wherein creating at least one transmission file queue according to the registration information of each service file to be transmitted comprises:

determining the number of a transmission file queue and the corresponding relation between the service file to be transmitted and the transmission file queue according to the registration information of each service file to be transmitted; wherein, the registration information at least comprises: sending a file serial number;

acquiring characteristic information of each service file to be sent according to the registration information of each service file to be sent;

determining the transmission priority of each service file to be transmitted according to the characteristic information of each service file to be transmitted and the corresponding relation between the service file to be transmitted and the transmission file queue;

creating at least one transmission file queue according to the determined number of the transmission file queues, the corresponding relation and the transmission priority of each service file to be transmitted; each transmission file queue comprises at least one transmission file serial number of the service file to be transmitted, which is arranged according to the ascending order of the transmission priority.

3. The method of claim 2, wherein the registration information further comprises: at least one extension field, after creating at least one send file queue, further comprising:

generating a sending file queue view according to the at least one sending file queue;

and when determining that the target service file to be sent in the transmission file queue needs to be adjusted according to the transmission file queue view, rewriting the registration information of the target service file to be sent based on the extension field in the registration information.

4. The method according to claim 1, wherein the sending file queue includes a sending file serial number, a sending priority and a sending status of a service file to be sent, and the obtaining of file configuration information of a target interface corresponding to each target service file to be sent includes:

screening a target service file to be sent with sending conditions from the at least one sending file queue by using a structured query statement; the sending condition is that the sending state is to be sent and the sending priority in the queue is highest;

determining a target interface corresponding to the target service file to be sent based on the serial number of the transmission file of the target service file to be sent;

and acquiring the file configuration information of the target interface.

5. The method according to claim 4, wherein converting the target service file to be sent into a target interface file matched with the target interface based on the file configuration information of the target interface comprises:

acquiring service data corresponding to each target service file to be sent by using a plurality of distributed nodes according to the serial number of the transmission file of each target service file to be sent;

converting the service data corresponding to the target to-be-sent service file into interface data matched with the target interface by using the plurality of distributed nodes based on the file configuration information of the target interface;

preprocessing the interface data by utilizing the plurality of distributed nodes to obtain the target interface file; wherein the pre-processing comprises: and (5) encrypting and compressing.

6. The method of claim 1, wherein transferring the target interface file to the target interface comprises:

pushing the target interface file to a preset sending directory;

and pushing the target interface file in the sending directory to a target directory corresponding to the target interface by using a timing task.

7. The method of claim 6, after transferring the target interface file to the target interface, further comprising:

traversing the target directory corresponding to the target interface according to a preset time interval to obtain a plurality of files to be processed;

acquiring characteristic information of the files to be processed;

creating at least one file queue to be processed according to the characteristic information of the files to be processed; the file queue to be processed comprises the processing priority and the processing state of the file to be processed;

screening a target file to be processed with a processing condition from the at least one file queue to be processed by using a structured query statement; wherein the processing condition is that the processing state is to be processed and the processing priority is highest in the queue;

acquiring file configuration information of an interface corresponding to the target file to be processed;

converting the target file to be processed into corresponding service data based on the file configuration information of the interface corresponding to the target file to be processed;

and performing service processing by using the service data corresponding to the target file to be processed.

8. The method according to claim 7, wherein the file configuration information includes technical parameters and file configuration parameters, and the target file to be processed is converted into corresponding service data based on the file configuration information of the interface corresponding to the target file to be processed, further comprising:

preprocessing the target file to be processed based on technical parameters in file configuration information of an interface corresponding to the target file to be processed; wherein the pre-processing comprises: decrypting, decompressing and analyzing;

and converting the preprocessed target file to be processed into corresponding service data according to the file configuration parameters in the file configuration information of the interface corresponding to the target file to be processed.

9. A file transfer apparatus, comprising:

the first acquisition module is used for acquiring registration information of a plurality of service files to be sent;

the creating module is used for creating at least one sending file queue by utilizing the registration information of each service file to be sent;

the second acquisition module is used for acquiring file configuration information of a target interface corresponding to each target service file to be sent; the target to-be-sent service file is a service file with sending conditions in the at least one sending file queue, and the target interface is an interface corresponding to a receiver of the target to-be-sent service file;

the conversion module is used for converting the target service file to be sent into a target interface file matched with the target interface based on the file configuration information of the target interface;

and the transmission module is used for transmitting the target interface file to the target interface.

10. A file transfer device comprising a processor and a memory for storing processor-executable instructions which, when executed by the processor, implement the steps of the method of any one of claims 1 to 8.

11. A computer-readable storage medium having stored thereon computer instructions which, when executed, implement the steps of the method of any one of claims 1 to 8.