CN111831611A - Cross-border data exchange method, device and system - Google Patents
Cross-border data exchange method, device and system Download PDFInfo
- Publication number
- CN111831611A CN111831611A CN202010659674.8A CN202010659674A CN111831611A CN 111831611 A CN111831611 A CN 111831611A CN 202010659674 A CN202010659674 A CN 202010659674A CN 111831611 A CN111831611 A CN 111831611A
- Authority
- CN
- China
- Prior art keywords
- data
- source data
- file
- overseas
- source
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/178—Techniques for file synchronisation in file systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/35—Switches specially adapted for specific applications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Library & Information Science (AREA)
- Human Computer Interaction (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the specification provides a cross-border data exchange method, a device and a system, wherein the system comprises: the system comprises an overseas data conversion device, an intraenvironment data conversion device and an extraenvironment data conversion device, wherein the overseas data conversion device is used for receiving first source data provided by an extraenvironment upstream application, processing the first source data, providing the processed data to the extraenvironment downstream application and providing the first source data to the intraenvironment data conversion device; and the domestic data conversion device is used for receiving the first source data and second source data provided by the domestic upstream application, processing the first source data and the second source data and providing the processed data to the domestic downstream application, and providing the processed data of the second source data to the overseas application. The embodiment of the specification can improve timeliness and reliability of the overseas data processing.
Description
Technical Field
The present disclosure relates to the field of data exchange processing technologies, and in particular, to a cross-border data exchange method, device, and system.
Background
With the high-speed development of modern information technology, large-scale enterprises emerge various application systems with fine and definite division of labor, and accordingly, a data exchange system for meeting the requirement of data exchange among multiple application systems is developed. Meanwhile, with the increasingly expansion of the enterprise in the overseas business, the ever-increasing data of the overseas application system is transmitted back to the domestic data exchange system for processing, and the timeliness and the reliability of the overseas data processing are difficult to guarantee.
Disclosure of Invention
An object of the embodiments of the present specification is to provide a cross-border data exchange method, apparatus and system to improve timeliness and reliability of overseas data processing.
To achieve the above object, in one aspect, the present specification provides a cross-border data exchange system, including:
the system comprises an overseas data conversion device, an intraenvironment data conversion device and an extraenvironment data conversion device, wherein the overseas data conversion device is used for receiving first source data provided by an extraenvironment upstream application, processing the first source data, providing the processed data to the extraenvironment downstream application and providing the first source data to the intraenvironment data conversion device;
and the domestic data conversion device is used for receiving the first source data and second source data provided by the domestic upstream application, processing the first source data and the second source data and providing the processed data to the domestic downstream application, and providing the processed data of the second source data to the overseas application.
In another aspect, embodiments of the present specification further provide a cross-border data exchange method, including:
receiving first source data provided by an outbound upstream application;
processing the first source data;
providing the processed data to an overseas downstream application;
providing said first source data to an inbound data translation device to facilitate said inbound data translation device processing said first source data into target data and providing to an inbound downstream application.
In another aspect, embodiments of the present specification further provide a cross-border data exchange method, including:
receiving first source data and second source data; the first source data is provided by an overseas data conversion device, and the second source data is provided by an intradomestic upstream application;
processing the first source data and the second source data;
providing the processed data to the domestic downstream application;
providing the processed data of the second source data to an overseas application.
In another aspect, an embodiment of the present specification further provides an overseas data conversion apparatus, including:
the data receiving module is used for receiving first source data provided by the overseas upstream application;
the data processing module is used for processing the first source data;
a first data providing module for providing the processed data to an overseas downstream application;
a second data providing module, configured to provide the first source data to an intra-environment data transformation device, so that the intra-environment data transformation device processes the first source data into target data and provides the target data to an intra-environment downstream application.
In another aspect, embodiments of the present specification further provide an intra-environment data conversion apparatus, including:
the receiving module is used for receiving first source data and second source data; the first source data is provided by an overseas data conversion device, and the second source data is provided by an intradomestic upstream application;
a processing module for processing the first source data and the second source data;
a first providing module for providing the processed data to the domestic downstream application;
and the second providing module is used for providing the data processed by the second source data to the overseas application.
As apparent from the above technical solutions provided by the embodiments of the present specification, in the embodiments of the present specification, since the overseas data exchange device can apply the provided source data to the upstream outside the overseas processing environment without returning the source data to the domestic data exchange device for processing, as in the prior art, the time efficiency of the overseas data processing can be greatly improved by the cross-border data exchange system according to the embodiments of the present specification. Furthermore, since the overseas data exchange device can provide the obtained source data to the domestic data exchange device for processing, the reliability of the overseas data processing is improved.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the specification, and other drawings can be obtained by those skilled in the art without inventive labor. In the drawings:
FIG. 1 is a schematic cross-border data exchange system architecture in an embodiment provided herein;
fig. 2 is a flowchart of a cross-border data exchange method on the side of an outbound data exchange device in an embodiment provided in the present specification;
FIG. 3 is a flow diagram of a method for cross-border data exchange at a data exchange device side in an embodiment provided herein;
fig. 4 is a flow chart of data distribution control on the side of the outbound data exchange apparatus in the embodiment provided in the present specification;
fig. 5 is a block diagram of the structure of an overseas data exchange apparatus in an embodiment provided in the present specification;
fig. 6 is a block diagram of a data exchange device side in an implementation provided in this specification.
Detailed Description
In order to make the technical solutions in the present specification better understood, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is apparent that the described embodiments are only a part of the embodiments of the present specification, but not all of the embodiments. All other embodiments obtained by a person skilled in the art without making creative efforts based on the embodiments in the present specification shall fall within the protection scope of the present specification.
Referring to fig. 1, a cross-border data exchange system in some embodiments of the present description may include an outbound data fitting and an inbound data fitting. The outbound data conversion device may receive first source data provided by an outbound upstream application, process the first source data and provide the processed data to an outbound downstream application, and provide the first source data to the inbound data conversion device. The inbound data conversion device may receive the first source data and second source data provided by an inbound upstream application, process the first source data and the second source data and provide the processed data to an inbound downstream application, and provide the processed data to an outbound application.
After the cross-border data exchange system of the embodiment of the present specification is deployed, the source data provided by the overseas data exchange device can be applied to the upstream outside the overseas processing environment, and does not need to be remotely returned to the domestic data exchange device for processing as in the prior art, so that the time efficiency of the overseas data processing can be greatly improved by the cross-border data exchange system of the embodiment of the present specification. Furthermore, since the overseas data exchange device can provide the obtained source data to the domestic data exchange device for processing, the reliability of the overseas data processing is improved.
In some embodiments of the present description, the overseas data exchange device may be extended on an inbound data exchange device basis. Namely, the oversea data exchange device can reuse the domestic data exchange device, and realizes the oversea data exchange device which accords with the oversea data exchange requirement and the operation and maintenance capability by adding data configuration management and data distribution control. And because the overseas data exchange device reuses the domestic data exchange device, the overseas data exchange device has the characteristics of simple realization, low construction cost and easy maintenance in later period.
In some embodiments of the present description, the first source data may be business data (e.g., transaction data, etc.) generated by an outbound upstream application. The service data needs to be processed at the overseas data conversion device side according to preset service logic so as to be provided for downstream application. The overseas upstream applications and the overseas downstream applications mentioned in the embodiments of the present specification are referred to with respect to the overseas data transfer apparatus. When the overseas application needs to provide the source data to the overseas data conversion device for processing, the overseas application forms the overseas upstream application of the overseas data conversion device. When the overseas data conversion apparatus needs to provide the processed data to other overseas applications, the other overseas applications form the overseas downstream applications of the overseas data conversion apparatus. In the embodiments of the present specification, reference is made to the second source data, the domestic upstream application, and the domestic downstream application, which may be explained with reference to this section, and this description is not repeated here.
Referring to fig. 1, in some embodiments of the present disclosure, in consideration of the scale of the overseas Data processing and the construction cost, the overseas upstream application may send the first source Data to the overseas Data conversion device based on a General Data Transfer Platform (GTP) Protocol, a File Transfer Protocol (FTP) Protocol, or the like. Also, the outbound data transfer may be directed to outbound downstream applications based on the GTP protocol.
For the situation that domestic application needs to use a large amount of data processed by an overseas data switching device, the characteristics of the cross-border data exchange system in the embodiment of the specification are considered as follows: the processed data volume and transmission task are expanded by times according to the processed downstream number, and the processed overseas data is transmitted back to the environment and cannot meet the aging requirement easily. In view of the high data throughput capability of the intra-device data transfer devices, there is generally a large performance margin; therefore, the source data before being processed by the overseas data conversion device can be transmitted to the domestic data conversion device for processing, and the original transmission mode of the domestic data conversion device can be transmitted to domestic downstream applications after being processed, so as to meet the domestic requirements on the overseas data. In an embodiment of this specification, the source data provided by the overseas data conversion device to the domestic data conversion device may be full source data or partial source data, and may be specifically selected according to actual service needs. In one embodiment of the present description, the outbound data fitting device may provide source data to the inbound data fitting device based on the timed task. In one embodiment of the present description, the outbound data fitting may provide source data to the inbound data fitting based on the GTP protocol.
For the requirement of the data processed by the intra-environment data conversion device outside the environment, the fact that the actual intra-environment data volume is huge, the transmission rate of the cross-environment network is low, and the number of the intra-environment data files actually used outside the environment is usually small is considered, and the fact that the full-volume intra-environment source data is directly transmitted outside the environment is neither practical nor necessary. Accordingly, the inbound data arrangement may provide the processed data for the second source data to the outbound application (where the outbound application may include the outbound upstream application and/or the outbound downstream application described above) as needed.
In one embodiment of the present specification, the inbound source data (i.e., the second source data) that may be provided to the inbound data conversion device by the inbound upstream application may be based on the GTP protocol, the FTP protocol, or a shared disk. The inbound data conversion device may provide the processed data to the inbound downstream application based on the GTP protocol, the FTP protocol, or the shared disk.
For ease of understanding, the following description will be made on an implementation process in which the outbound data conversion device provides the first source data to the inbound data conversion device (i.e., data distribution control of the outbound data conversion device). Referring to fig. 4, the overseas data transfer device providing the first source data to the inbound data transfer device may include the steps of:
s401, creating symbol links corresponding to the data files in the first source data in a sending directory.
In the embodiment of the present specification, establishing a corresponding symbolic link for each data file in the first source data may facilitate consistency between inbound data and outbound data, and at the same time, avoid file hard copy and reduce resource waste. For example, in an exemplary embodiment, the path/snfs 1/midle stores the source data received by the outbound data conversion device, and creates a corresponding symbolic link for each data file in the source data that needs to be sent to the inbound data conversion device under the sending directory (the corresponding path is/snfs 3/source). It should be noted that when symbolic links are created for files under/snfs 1/midle, the files under this directory should be system-defined processable to avoid creating a large number of invalid file symbolic links. In the embodiments of the present specification, the data file is a file that the overseas data transfer device actually needs to process.
S402, respectively creating symbolic links corresponding to the list file, the control file and the field closing file corresponding to the first source data in the temporary directory.
In an embodiment of the present specification, the symbolic link corresponding to the manifest file, the control file and the session closure file corresponding to the first source data is not created directly in the sending directory, but is created in the temporary directory for the purpose of following: data file → manifest file → control file and the sequence of data transmission of the session close-up file control data transmission to provide the basis. And the data transmission is controlled according to the data transmission sequence, so that the processing failure condition possibly caused by the fact that the data file is processed by the system before the data file is completely received can be avoided.
In the embodiment of the present specification, the manifest file is also called a chk file, and mainly records the number, name and file size of data files for the overseas data conversion apparatus to check before processing. The control file is also called ctl file, and mainly records whether the files in the directory where the data files are located are all in order, so that the overseas data conversion device can start processing. The session closing-up file is used for recording whether the files under a group of directories corresponding to the session are all in order to facilitate the overseas data conversion device to start the processing of multiple directories.
S403, sending the symbolic link of each data file in the sending directory to the domestic data conversion device, so that the domestic data conversion device can obtain each data file accordingly.
In the embodiments of the present specification, since symbolic links are similar to shortcuts in the window system, what is stored inside is a path of the source file, pointing to the source file entity, i.e. the symbolic links point to data files written to the target system (i.e. the native data device). Therefore, when the intraenvironment data conversion device performs read/write operation on the symbolic link, the read/write operation on the symbolic link can be automatically converted into operation on the source file, so that the overseas data conversion device can provide the overseas source data to the intraenvironment data conversion device.
S404, whether the data files are transmitted successfully or not is confirmed.
In one embodiment of the present description, the oversea data removal device may traverse the temporary directory to check whether a symbolic link of the manifest file exists in the temporary directory. When the symbolic link of the manifest file exists in the temporary directory, the symbolic link of the manifest file can be located to the manifest file, and the sending record table can be queried according to the file name or the identifier in the manifest file to determine whether each data file in the manifest file is sent successfully. Wherein, the sending state of the file is recorded in the sending record table; and when the file is successfully transmitted, updating the transmission state of the file into a transmission success state in the transmission record table. In another embodiment of this specification, the transmission record table may be further split into a transmission success record table and a transmission failure record table, and further, whether each data file in the manifest file is successfully transmitted may be determined by querying the transmission success record table.
In an embodiment of this specification, after it is confirmed that each data file is successfully transmitted, the symbolic link corresponding to the data file in the transmission directory may be migrated to the backup directory, so as to facilitate subsequent transmission of the manifest file.
S405, when each data file is successfully transmitted, transferring the symbolic link of the list file in the temporary directory to the transmission directory, and transmitting the symbolic link to the domestic data conversion device, so that the domestic data conversion device can conveniently acquire the list file according to the symbolic link.
S406, whether the sending of the manifest file is successful is confirmed.
In an embodiment of this specification, after the sending of the manifest file is confirmed to be successful, the symbolic link corresponding to the manifest file in the sending directory may also be migrated to the backup directory, so as to facilitate the subsequent sending of the control file and the session close-up file.
And S407, when the sending of the manifest file is successful, migrating the symbolic link of the control file in the temporary directory and the symbolic link of the field close-up file to the sending directory, and sending the symbolic link to the domestic data conversion device, so that the domestic data conversion device can obtain the control file and the field close-up file accordingly.
In an embodiment of this specification, after the control file and the field closing-in file are confirmed to be successfully sent, the symbolic link corresponding to the control file and the field closing-in file in the sending directory may also be migrated to the backup directory, so as to perform the data distribution control of the next round.
In the embodiments of the present specification, the data exchange in the cross-border data exchange system is beneficial to the consistency between the overseas source data received indoors and the overseas local, and in order to ensure that the domestic data conversion devices can process the overseas source data correctly and the processed data can be consistent with the overseas data, the cross-border data exchange system needs to be subjected to data configuration management. Taking the internal data conversion device as an example, first, the upstream application needs to unify the basic information of the metadata management platform level data in the enterprise (including the belonging application, the interface, the file structure, the processing mode, and the downstream application, i.e., the system which needs to receive the processed data). And the information can be assembled into a data configuration import internal data conversion device according to the part of information to generate a specific data processing and distributing mode. After the data arrives at the data exchange device in the environment, the data is processed and distributed according to a predefined mode to achieve the purpose of data exchange. Therefore, both the domestic data conversion device and the overseas data conversion device need to synchronously install newly added and modified data configuration information to ensure the consistency of processing results.
The provision of cross-border data exchange system collaboration capabilities deployed across borders depends in large part on GTP data transmission between the inbound and outbound data transfer devices. In order to make the overseas data have corresponding GTP tasks transmitted back to the insides, the existing configuration information needs to add the document internal and external identifiers, for example, the internal and external documents may be identified and distinguished based on the application interface in the transmission information. And automatically generating relevant GTP transmission information for the newly added foreign identification file so as to carry out foreign data synchronization. In addition, the interface internal and external identification in the data configuration information can also assist the internal data conversion device to process, and for the external file, only the internal target interface is processed when the internal data conversion device processes, so that the waste of processing capacity can be reduced.
In some embodiments of the present description, the cross-border data exchange method shown in fig. 2 may be applied to the side of the overseas data conversion device, which may include the following steps:
s201, receiving first source data provided by an overseas upstream application.
S202, processing the first source data.
S203, providing the processed data to the overseas downstream application.
And S204, providing the first source data to an intra-environment data conversion device so that the intra-environment data conversion device can process the first source data into target data and provide the target data to an intra-environment downstream application.
In the cross-border data exchange method according to some embodiments of the present specification, the providing the first source data to the intra-border data conversion device may include:
creating a symbolic link corresponding to each data file in the first source data in a sending directory;
respectively creating symbolic links corresponding to the list file, the control file and the field closing-up file corresponding to the first source data in a temporary directory;
sending the symbolic link of each data file in the sending directory to the domestic data conversion device, so that the domestic data conversion device can obtain each data file according to the symbolic link;
confirming whether each data file is successfully sent;
when each data file is successfully sent, transferring the symbolic link of the list file in the temporary directory to the sending directory, and sending the symbolic link to the domestic data conversion device, so that the domestic data conversion device can obtain the list file according to the symbolic link;
confirming whether the manifest file is successfully sent;
and when the sending of the list file is successful, transferring the symbolic link of the control file in the temporary directory and the symbolic link of the field closing-up file to the sending directory, and sending the symbolic link to the in-environment data conversion device, so that the in-environment data conversion device can obtain the control file and the field closing-up file according to the symbolic link of the control file and the symbolic link of the field closing-up file.
In the cross-border data exchange method according to some embodiments of the present description, the cross-border data exchange method may further include:
the transmission status of the file is updated in the transmission record table.
In the cross-border data exchange method according to some embodiments of the present description, the cross-border data exchange method may further include:
and migrating the symbol link which is successfully sent in the sending directory to a backup directory.
In the cross-border data exchange method of some embodiments of the present description, the first source data carries an outbound identification.
In some embodiments of the present description, the cross-border data exchange method shown in fig. 3 may be applied to the inbound data device side, which may include the following steps:
s301, receiving first source data and second source data; the first source data is provided by an overseas data conversion device and the second source data is provided by an intradomestic upstream application.
S302, processing the first source data and the second source data.
And S303, providing the processed data to domestic downstream application.
S304, providing the data processed by the second source data to the overseas application.
In a cross-border data exchange method according to some embodiments of the present specification, the first source data carries an outbound identifier, and the second source data carries an inbound identifier.
While the process flows described above include 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. 5, corresponding to the cross-border data exchange method shown in fig. 2, the present specification provides an overseas data conversion apparatus, which may include:
a data receiving module 51 operable to receive first source data provided by an outbound upstream application;
a data processing module 52 operable to process the first source data;
a first data providing module 53, which may be used to provide the processed data to an overseas downstream application;
a second data providing module 54 may be configured to provide the first source data to an intra-environment data transformation device, so that the intra-environment data transformation device processes the first source data into target data and provides the target data to an intra-environment downstream application.
Referring to fig. 6, corresponding to the cross-border data exchange method shown in fig. 3, the present specification provides an intra-border data conversion apparatus, which may include:
a receiving module 61, which may be configured to receive first source data and second source data; the first source data is provided by an overseas data conversion device, and the second source data is provided by an intradomestic upstream application;
a processing module 62, which may be used to process the first source data and the second source data;
a first providing module 63 operable to provide the processed data to the domestic downstream application;
a second providing module 64 may be configured to provide the processed data of the second source data to the overseas application.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more of software and hardware in practicing the present description.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
Memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM), and non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The described embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the method embodiments, since they are substantially similar to the system embodiments, the description is relatively simple, and reference may be made to the partial description of the system embodiments for the relevant points.
In the description of the specification, reference to the description of the term "one embodiment", "some embodiments", "an example", "a specific example", or "some examples", etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the embodiments of the specification. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the various embodiments or examples and features of the various embodiments or examples described in this specification can be combined and combined by those skilled in the art without contradiction.
The above description is only an embodiment of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A cross-border data exchange system, comprising:
the system comprises an overseas data conversion device, an intraenvironment data conversion device and an extraenvironment data conversion device, wherein the overseas data conversion device is used for receiving first source data provided by an extraenvironment upstream application, processing the first source data, providing the processed data to the extraenvironment downstream application and providing the first source data to the intraenvironment data conversion device;
and the domestic data conversion device is used for receiving the first source data and second source data provided by the domestic upstream application, processing the first source data and the second source data and providing the processed data to the domestic downstream application, and providing the processed data of the second source data to the overseas application.
2. A method for cross-border data exchange, comprising:
receiving first source data provided by an outbound upstream application;
processing the first source data;
providing the processed data to an overseas downstream application;
providing said first source data to an inbound data translation device to facilitate said inbound data translation device processing said first source data into target data and providing to an inbound downstream application.
3. The cross-border data exchange method of claim 2, wherein said providing the first source data to an intra-border data translation device comprises:
creating a symbolic link corresponding to each data file in the first source data in a sending directory;
respectively creating symbolic links corresponding to the list file, the control file and the field closing-up file corresponding to the first source data in a temporary directory;
sending the symbolic link of each data file in the sending directory to the domestic data conversion device, so that the domestic data conversion device can obtain each data file according to the symbolic link;
confirming whether each data file is successfully sent;
when each data file is successfully sent, transferring the symbolic link of the list file in the temporary directory to the sending directory, and sending the symbolic link to the domestic data conversion device, so that the domestic data conversion device can obtain the list file according to the symbolic link;
confirming whether the manifest file is successfully sent;
and when the sending of the list file is successful, transferring the symbolic link of the control file in the temporary directory and the symbolic link of the field closing-up file to the sending directory, and sending the symbolic link to the in-environment data conversion device, so that the in-environment data conversion device can obtain the control file and the field closing-up file according to the symbolic link of the control file and the symbolic link of the field closing-up file.
4. The cross-border data exchange method of claim 3, further comprising:
the transmission status of the file is updated in the transmission record table.
5. The cross-border data exchange method of claim 3, further comprising:
and migrating the symbol link which is successfully sent in the sending directory to a backup directory.
6. The cross-border data exchange method of claim 2, wherein the first source data carries an outbound identification.
7. A method for cross-border data exchange, comprising:
receiving first source data and second source data; the first source data is provided by an overseas data conversion device, and the second source data is provided by an intradomestic upstream application;
processing the first source data and the second source data;
providing the processed data to the domestic downstream application;
providing the processed data of the second source data to an overseas application.
8. The method of claim 7, wherein the first source data carries an outbound identifier and the second source data carries an inbound identifier.
9. An overseas data conversion apparatus, comprising:
the data receiving module is used for receiving first source data provided by the overseas upstream application;
the data processing module is used for processing the first source data;
a first data providing module for providing the processed data to an overseas downstream application;
a second data providing module, configured to provide the first source data to an intra-environment data transformation device, so that the intra-environment data transformation device processes the first source data into target data and provides the target data to an intra-environment downstream application.
10. An intra-environment data translation apparatus, comprising:
the receiving module is used for receiving first source data and second source data; the first source data is provided by an overseas data conversion device, and the second source data is provided by an intradomestic upstream application;
a processing module for processing the first source data and the second source data;
a first providing module for providing the processed data to the domestic downstream application;
and the second providing module is used for providing the data processed by the second source data to the overseas application.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010659674.8A CN111831611B (en) | 2020-07-09 | 2020-07-09 | Cross-border data exchange method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010659674.8A CN111831611B (en) | 2020-07-09 | 2020-07-09 | Cross-border data exchange method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111831611A true CN111831611A (en) | 2020-10-27 |
| CN111831611B CN111831611B (en) | 2023-08-25 |
Family
ID=72901000
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010659674.8A Active CN111831611B (en) | 2020-07-09 | 2020-07-09 | Cross-border data exchange method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111831611B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101706936A (en) * | 2009-12-01 | 2010-05-12 | 中国建设银行股份有限公司 | Domestic and foreign ledger-combining processing method and processing system |
| US20150149356A1 (en) * | 2013-11-22 | 2015-05-28 | Mastercard International Incorporated | Method and system for authenticating cross-border financial card transactions |
| CN106548333A (en) * | 2016-11-14 | 2017-03-29 | 唐红祥 | A kind of cross-border interactive financial payment terminal |
| CN106789755A (en) * | 2016-11-30 | 2017-05-31 | 中国电子科技集团公司第五十四研究所 | Inter-network data interchange platform |
| CN106803836A (en) * | 2016-12-27 | 2017-06-06 | 中国银联股份有限公司 | A kind of multicenter file method for processing forwarding and device |
| CN106921703A (en) * | 2015-12-25 | 2017-07-04 | 阿里巴巴集团控股有限公司 | The method of cross-border data syn-chronization, system, and domestic and overseas data center |
| CN111179061A (en) * | 2019-12-30 | 2020-05-19 | 支付宝实验室(新加坡)有限公司 | Resource transfer processing method, device and equipment |
-
2020
- 2020-07-09 CN CN202010659674.8A patent/CN111831611B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101706936A (en) * | 2009-12-01 | 2010-05-12 | 中国建设银行股份有限公司 | Domestic and foreign ledger-combining processing method and processing system |
| US20150149356A1 (en) * | 2013-11-22 | 2015-05-28 | Mastercard International Incorporated | Method and system for authenticating cross-border financial card transactions |
| CN106921703A (en) * | 2015-12-25 | 2017-07-04 | 阿里巴巴集团控股有限公司 | The method of cross-border data syn-chronization, system, and domestic and overseas data center |
| CN106548333A (en) * | 2016-11-14 | 2017-03-29 | 唐红祥 | A kind of cross-border interactive financial payment terminal |
| CN106789755A (en) * | 2016-11-30 | 2017-05-31 | 中国电子科技集团公司第五十四研究所 | Inter-network data interchange platform |
| CN106803836A (en) * | 2016-12-27 | 2017-06-06 | 中国银联股份有限公司 | A kind of multicenter file method for processing forwarding and device |
| CN111179061A (en) * | 2019-12-30 | 2020-05-19 | 支付宝实验室(新加坡)有限公司 | Resource transfer processing method, device and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111831611B (en) | 2023-08-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108280080B (en) | Data synchronization method and device and electronic equipment | |
| CN106155775B (en) | Message processing method, device and system | |
| CN111339192A (en) | Distributed edge computing data storage system | |
| CN111143093B (en) | Asynchronous message distributed processing method, device, equipment and storage medium | |
| CN108345617B (en) | Data synchronization method and device and electronic equipment | |
| KR102248386B1 (en) | Database data modification request processing method and device | |
| CN111399764B (en) | Data storage method, data reading device, data storage equipment and data storage medium | |
| CN111225012A (en) | Transaction processing method, device and equipment | |
| CN115277727B (en) | Data disaster recovery method, system, device and storage medium | |
| CN106897345B (en) | Data storage method and device | |
| CN115517009B (en) | Cluster management method, cluster management device, storage medium and electronic equipment | |
| US11416312B1 (en) | Near-real-time data processing with partition files | |
| CN111831611B (en) | Cross-border data exchange method, device and system | |
| CN113297316A (en) | Method, device and system for realizing data synchronization | |
| CN116303789A (en) | Parallel synchronization method and device for multi-fragment multi-copy database and readable medium | |
| CN116016492A (en) | Information cross-network transmission method, equipment and medium | |
| CN115455121A (en) | Real-time reliable data synchronous transmission method, equipment and medium | |
| CN113535477B (en) | Method and equipment for data disaster recovery | |
| CN104915362A (en) | Fast intelligent ERP system data migration scheme based on time slices, increment analysis and random disorganizing technology | |
| CN110059075A (en) | A kind of method, apparatus of database migration, equipment and computer-readable medium | |
| CN108694102A (en) | A kind of data manipulation method, equipment, system and medium based on Nexus services | |
| CN115374090A (en) | Data migration method and device, electronic equipment and computer readable storage medium | |
| KR20130105031A (en) | Real time data migration system and method therefor | |
| CN116248646A (en) | Cross-cloud application migration method and device, electronic equipment and storage medium | |
| CN114625084A (en) | Control system-based node information acquisition 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 |