A cross-system information transmission method, apparatus, device, medium and program product

Abstract

This disclosure provides a cross-system information transmission method, which can be applied to transmit upstream system information to obtain a field structure; calculate the field structure to obtain matching information; match the matching information with a preset matching value to obtain a preset conversion rule and a downstream system address; convert the upstream system information based on the preset conversion rule to obtain downstream system information; and transmit the downstream system information to a target downstream system based on the downstream system address. This disclosure also provides a cross-system information transmission device, equipment, storage medium, and program product.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, specifically the field of data transmission technology, and more specifically to a method, apparatus, device, medium, and program product for cross-system information transmission. Background Technology

[0002] Due to regulatory and standardization requirements, the intermediate layer system currently needs to interface with upstream and downstream systems. It receives data from upstream systems via interfaces, converts it according to standardized formats, and then calls downstream system interfaces for data transfer. Typically, the data format requirements of upstream and downstream systems are not consistent; therefore, appropriate data standardization operations need to be performed within the intermediate layer system.

[0003] In existing technologies, after the development interface receives formatted data from the upstream system, it parses and instantiates the data, then processes the instantiated data according to standardization requirements. In other words, this approach uses instantiation to map upstream and downstream system interfaces one-to-one, thereby enabling cross-system data transmission.

[0004] However, if either party needs to change the transmitted data content, the middleware system must re-encode it. Furthermore, since both data parsing and transmission are implemented using hard-coded methods, this results in drawbacks such as high development workload, high error probability, and low flexibility. Summary of the Invention

[0005] In view of the above problems, this disclosure provides cross-system information transmission methods, apparatus, devices, media and program products that improve the flexibility and accuracy of cross-system information transmission.

[0006] According to a first aspect of this disclosure, a cross-system information transmission method is provided, comprising: receiving upstream system information; parsing the upstream system information to obtain a field structure; calculating the field structure to obtain matching information; matching the matching information with a preset matching value to obtain a preset conversion rule and a downstream system address; converting the upstream system information based on the preset conversion rule to obtain downstream system information; and transmitting the downstream system information to a target downstream system based on the downstream system address.

[0007] According to an embodiment of this disclosure, parsing the upstream system information to obtain a field structure includes: segmenting the upstream system information based on preset characters to obtain multiple fields; and forming the field structure based on the multiple fields.

[0008] According to an embodiment of this disclosure, the step of calculating the field structure to obtain matching information includes: calculating the field structure based on a hash algorithm to obtain an upstream system hash encoding value.

[0009] According to an embodiment of this disclosure, the preset matching value is a pre-stored hash code, and the step of matching the preset matching value based on the matching information to obtain a preset conversion rule and a downstream system address includes: matching the pre-stored hash code value based on the upstream system hash code value to obtain an address mapping table, wherein the address mapping table includes a mapping relationship between upstream system addresses and downstream system addresses; and searching for the downstream system address based on the address mapping table.

[0010] According to embodiments of this disclosure, the mapping relationship between the upstream system address and the downstream system address is many-to-many. The method further includes: receiving a new downstream system address reported by the downstream system when the downstream system address changes; and adjusting the address mapping table based on the new downstream system address.

[0011] According to an embodiment of this disclosure, transmitting the downstream system information to the target downstream system based on the downstream system address includes: concatenating the downstream system address and the downstream system information to transmit the downstream system information to the target downstream system.

[0012] According to an embodiment of this disclosure, the upstream system information includes at least a header field, and the step of obtaining a field structure based on parsing the upstream system information includes: parsing the header field to obtain the field structure.

[0013] A second aspect of this disclosure provides a cross-system information transmission device, comprising: an information receiving module for receiving upstream system information; an information parsing module for parsing the upstream system information to obtain a field structure; a field calculation module for calculating the field structure to obtain matching information; a matching module for matching a preset matching value based on the matching information to obtain a preset conversion rule and a downstream system address; an information conversion module for converting the upstream system information based on the preset conversion rule to obtain downstream system information; and an information transmission module for transmitting the downstream system information to a target downstream system based on the downstream system address.

[0014] According to an embodiment of this disclosure, the information parsing module is further configured to segment the upstream system information based on preset characters to obtain multiple fields; and to form the field structure based on the multiple fields.

[0015] According to an embodiment of this disclosure, the field calculation module is further configured to calculate the field structure based on a hash algorithm to obtain the upstream system hash encoding value.

[0016] According to an embodiment of this disclosure, the matching module is further configured to match the pre-stored hash code value with the hash code value of the upstream system to obtain an address mapping table, wherein the address mapping table includes a mapping relationship between upstream system addresses and downstream system addresses; and to look up the downstream system address based on the address mapping table.

[0017] According to embodiments of this disclosure, the mapping relationship between the upstream system address and the downstream system address is many-to-many. The apparatus further includes: a registration center, configured to receive a new downstream system address reported by the downstream system when the downstream system address changes; and to adjust the address mapping table based on the new downstream system address.

[0018] According to an embodiment of this disclosure, the information transmission module is further configured to concatenate the downstream system address and the downstream system information to transmit the downstream system information to the target downstream system.

[0019] According to an embodiment of this disclosure, the information parsing module is further configured to parse the header field to obtain the field structure.

[0020] A third aspect of this disclosure provides an electronic device comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the aforementioned cross-system information transmission method.

[0021] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the aforementioned cross-system information transfer method.

[0022] A fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described cross-system information transmission method.

[0023] In the embodiments of this disclosure, the pre-defined conversion rules and addresses of multiple different downstream interfaces are integrated in the intermediate layer. Configuration can be implemented only in the intermediate layer system, eliminating the need for configuration in the upstream and downstream systems. By matching these pre-defined conversion rules and addresses with field structures, the pre-defined conversion rules of each downstream system interface can be accurately matched, achieving highly efficient data conversion. Furthermore, the entire processing method reduces the use of hard-coding, thus reducing the error rate. Attached Figure Description

[0024] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0025] Figure 1 This diagram illustrates an application scenario of the cross-system information transmission method according to an embodiment of the present disclosure.

[0026] Figure 2 A flowchart illustrating a cross-system information transmission method according to an embodiment of the present disclosure is shown schematically.

[0027] Figure 3 A schematic diagram illustrating a field structure according to an embodiment of the present disclosure is shown.

[0028] Figure 4 A schematic diagram illustrating the entire process of a cross-system information transmission method according to an embodiment of the present disclosure is provided.

[0029] Figure 5 A schematic block diagram of a cross-system information transmission apparatus according to an embodiment of the present disclosure is shown.

[0030] Figure 6 A block diagram of an electronic device suitable for implementing a cross-system information transmission method according to an embodiment of the present disclosure is shown schematically. Detailed Implementation

[0031] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0032] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0033] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0034] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0035] Embodiments of this disclosure provide a cross-system information transmission method, comprising: receiving upstream system information; parsing the upstream system information to obtain a field structure; calculating the field structure to obtain matching information; matching a preset matching value based on the matching information to obtain a preset conversion rule and a downstream system address; converting the upstream system information based on the preset conversion rule to obtain downstream system information; and transmitting the downstream system information to a target downstream system based on the downstream system address.

[0036] In the embodiments of this disclosure, the pre-defined conversion rules and addresses of multiple different downstream interfaces are integrated in the intermediate layer. Configuration can be implemented only in the intermediate layer system, eliminating the need for configuration in the upstream and downstream systems. By matching these pre-defined conversion rules and addresses with field structures, the pre-defined conversion rules of each downstream system interface can be accurately matched, achieving highly efficient data conversion. Furthermore, the entire processing method reduces the use of hard-coding, thus reducing the error rate.

[0037] Figure 1 The diagram illustrates an application scenario of the cross-system information transmission method according to an embodiment of the present disclosure.

[0038] like Figure 1 As shown, application scenario 100 according to this embodiment may include terminal devices 101, 102, and 103, network 104, and server 105. Network 104 is used as a medium to provide a communication link between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0039] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0040] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0041] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using terminal devices 101, 102, and 103 (for example only). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0042] It should be noted that the cross-system information transmission method provided in this disclosure embodiment can generally be executed by server 105. Correspondingly, the cross-system information transmission device provided in this disclosure embodiment can generally be located in server 105. The cross-system information transmission method provided in this disclosure embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105. Correspondingly, the cross-system information transmission device provided in this disclosure embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105.

[0043] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0044] The following will be based on Figure 1 The described scene, through Figures 2-4 The cross-system information transmission method of the disclosed embodiments will be described in detail.

[0045] Figure 2 A flowchart illustrating a cross-system information transmission method according to an embodiment of the present disclosure is shown schematically.

[0046] Figure 3 A schematic diagram of a field structure according to an embodiment of the present disclosure is shown.

[0047] like Figure 2 As shown, the cross-system information transmission method of this embodiment includes operations S210 to S260, and the cross-system information transmission method can be executed by server 105.

[0048] In operation S210, information from the upstream system is received.

[0049] In operation S220, the upstream system information is parsed to obtain the field structure.

[0050] The upstream system refers to the sender of information, and the downstream system refers to the receiver of information. Both upstream and downstream systems have their own requirements for information format. To ensure that the downstream system can directly use the information sent from the upstream system, the intermediate layer system needs to modify the format of the information sent from the upstream system to meet the downstream system's format requirements. The method in the embodiments of this disclosure is applied to the intermediate layer system for information format modification and forwarding.

[0051] In the embodiments of this disclosure, the intermediate layer system connects to multiple different upstream systems through multiple different interfaces, and simultaneously connects to multiple different downstream systems through multiple different interfaces. Generally, the format requirements for information sent by the same upstream system are consistent, while the format requirements for information sent by different upstream systems are inconsistent. Similarly, the format requirements for information sent by the same downstream system are consistent, while the format requirements for information sent by different downstream systems are inconsistent. These format requirements are generally reflected in the field structure. The field structure typically includes specific fields, the number of fields, and the field length, etc.

[0052] like Figure 3 As shown, a message typically includes multiple fields, such as "S1", "S2", "S3", and "S4". Different fields have different lengths. Of course, in specific business scenarios, different fields carry different information. For example, "S1" can be a username, an identifier, or a date.

[0053] When obtaining the field structure, certain specific fields can be used as the field structure described above. For example, when field "S1" is an address identifier, only field "S1" can be used as the field structure. Alternatively, feature data from multiple fields can be used as the field structure. For example, select several specific fields, "S1", "S2", and "S3", and use the contents of fields "S1", "S2", and "S3" (e.g., address identifier, date, and business data, respectively) as the field structure. Alternatively, the field lengths of fields "S1", "S2", and "S3" can be used as the field structure. For example, the field structure could record "S1" = 3, "S2" = 4, and "S3" = 2. Further details will not be elaborated upon here.

[0054] According to an embodiment of this disclosure, parsing the upstream system information to obtain a field structure includes: segmenting the upstream system information based on preset characters to obtain multiple fields; and forming the field structure based on the multiple fields.

[0055] like Figure 3 As shown, different fields require special characters as separators, namely the preset characters mentioned above. These preset characters can be common characters used to identify different fields, such as spaces and / or newlines. These characters can be used to distinguish fields "S1", "S2", "S3", and "S4", etc.

[0056] According to an embodiment of this disclosure, the upstream system information includes at least a header field, and the step of obtaining a field structure based on parsing the upstream system information includes: parsing the header field to obtain the field structure.

[0057] Specifically, upstream system information can be propagated based on XML and / or JSON, and similarly, downstream system information can also be propagated based on XML and / or JSON. For JSON, it includes key values ​​(i.e., header fields) and value values. By applying the above parsing method only to the key values ​​in the JSON to extract the field structure, the number of fields and the length of individual fields can be reduced to some extent, thus speeding up parsing efficiency.

[0058] In operation S230, the field structure is calculated to obtain matching information.

[0059] Matching information can be generated directly from the field structure, or by combining the field structure with other field-related information, or by combining the field structure with other information related to the upstream system interface. Alternatively, matching information can be calculated using a specific algorithm based on the field structure, or by combining the field structure with other field-related information, or by combining the field structure with other information related to the upstream system interface and then using a specific algorithm to obtain matching information.

[0060] It is understandable that the matching information is used to retrieve the corresponding preset conversion rules pre-stored in the intermediate layer system.

[0061] According to an embodiment of this disclosure, the step of calculating the field structure to obtain matching information includes: calculating the field structure based on a hash algorithm to obtain an upstream system hash encoding value.

[0062] Specifically, the aforementioned algorithm can employ a hash algorithm to calculate the hash code value through the field structure. This serves to encrypt upstream information and ensure its uniqueness, greatly guaranteeing the uniqueness of the matching information.

[0063] In operation S240, a preset matching value is matched based on the matching information to obtain a preset conversion rule and downstream system address.

[0064] The preset conversion rules refer to format conversions to conform to the specified format. For example, preset conversion rules include adding or removing content from fields, or concatenating multiple fields to form a single field. It is understood that the preset conversion rules and downstream system addresses are pre-configured in the middleware system by developers and / or operations personnel.

[0065] According to an embodiment of this disclosure, the preset matching value is a pre-stored hash code, and the step of matching the preset matching value based on the matching information to obtain a preset conversion rule and a downstream system address includes: matching the pre-stored hash code value based on the upstream system hash code value to obtain an address mapping table, wherein the address mapping table includes a mapping relationship between upstream system addresses and downstream system addresses; and searching for the downstream system address based on the address mapping table.

[0066] Specifically, the matching information uses hash-encoded values, and the preset matching values ​​also use hash-encoded values ​​for direct matching. It's understandable that different downstream systems have uniform requirements for information format; therefore, the preset conversion rules and addresses have a one-to-one correspondence. That is, matching a downstream system address will successfully obtain the corresponding preset conversion rule, or matching a preset conversion rule will also successfully obtain the corresponding downstream address; this will not be elaborated further here.

[0067] In operation S250, the upstream system information is transformed based on the preset transformation rules to obtain the downstream system information.

[0068] In operation S260, the downstream system information is transmitted to the target downstream system based on the downstream system address.

[0069] According to an embodiment of this disclosure, transmitting the downstream system information to the target downstream system based on the downstream system address includes: concatenating the downstream system address and the downstream system information to transmit the downstream system information to the target downstream system.

[0070] For example, when the downstream system address exists in the form of a URL, data transmission is achieved by concatenating the URL and the downstream system information.

[0071] In the embodiments of this disclosure, the pre-defined conversion rules and addresses of multiple different downstream interfaces are integrated in the intermediate layer. Configuration can be implemented only in the intermediate layer system, eliminating the need for configuration in the upstream and downstream systems. By matching these pre-defined conversion rules and addresses with field structures, the pre-defined conversion rules of each downstream system interface can be accurately matched, achieving highly efficient data conversion. Furthermore, the entire processing method reduces the use of hard-coding, thus reducing the error rate.

[0072] According to embodiments of this disclosure, the mapping relationship between the upstream system address and the downstream system address is many-to-many. The method further includes: receiving a new downstream system address reported by the downstream system when the downstream system address changes; and adjusting the address mapping table based on the new downstream system address.

[0073] For example, when the middleware layer is a financial regulatory system, when a user inputs their relevant data through the upstream system to conduct certain financial transactions, the regulatory system receives this data. Typically, at this point, the regulatory system will call downstream systems from third parties to check if the user meets the relevant transaction requirements. However, the format of the information input by the user through the upstream system may not be directly usable by the downstream systems. Therefore, the middleware layer needs to perform relevant format conversion operations. Furthermore, for certain specific transactions, the upstream system may need to query multiple downstream systems corresponding to relevant departments. Conversely, for some specific transactions, the upstream system may only need to call a few downstream systems due to its simpler business complexity. Therefore, the mapping relationship between upstream and downstream systems is often many-to-many.

[0074] This system establishes an address change registration mechanism. A registration center is set up in the intermediate system, where the address mapping table is stored. When a downstream system's address changes, the intermediate system registers the new address of the downstream system, thereby updating the address mapping table accordingly. This integrated mapping effectively handles many-to-many address mapping relationships and enables rapid response to address changes.

[0075] Figure 4 A schematic diagram illustrating the full flow of a cross-system information transmission method according to an embodiment of the present disclosure is provided.

[0076] like Figure 4 As shown, the cross-system information transmission in this embodiment includes operations S401 to S412, and this cross-system information transmission method can be executed by server 105.

[0077] In operation S401, add or modify the mapping relationship table.

[0078] The comparison table refers to the comparison relationship of the transformation rules.

[0079] In operation S402, add or modify the interface number, receiver number, and interface address.

[0080] Specifically, operations and maintenance personnel define the calling interface and maintain its parameters in the interface configuration interface. They then remove spaces and newline characters from the interface parameters, convert them into hash-encoded values, and store them in the database using a template matching system.

[0081] It is understandable that the above operations S401 to S402 are used to reflect the process of operation and maintenance personnel configuring relevant rules, and centrally configuring the corresponding address mapping relationship and conversion rules.

[0082] In operating S403, business data is received through external interfaces.

[0083] The caller invokes the service to provide an interface. The upstream system information is in JSON format, containing the recipient's interface ID and corresponding business information. For example, the key of the received JSON is: {"AccID": "111123", "YWH": "A100121", "DIZHI": "XX Community"}, which includes three fields.

[0084] In operation S404, the string is parsed and the key is converted into a hash code.

[0085] In operation S405, the corresponding configuration is queried through hash encoding.

[0086] In operation S406, the corresponding configuration is returned.

[0087] After receiving the call information, the service converts the JSON string, extracts its format information, removes special characters such as newlines, and converts it into a hash value. A specific field can be used as the field structure to retrieve the corresponding downstream system address and conversion rules. For example, using the first field, "AccID": "111123", after removing the corresponding special characters, we get "AccID111123", which can be used as the field structure.

[0088] In operation S407, the information converter is invoked.

[0089] In operation S408, service data is sent.

[0090] In operation S409, the converted data is returned.

[0091] The service calls the database query function to retrieve the interface mapping information (i.e., the preset conversion relationship) configured by the operations and maintenance personnel through the hash encoded value. For example, the conversion rule is: {"YWH"->"ywbm", "DIZHI"->"jtzz"}.

[0092] The service invokes a business data transformation function to convert upstream JSON format information using a converter. For example, the converted downstream system information might be: {"ywbm":"A100121","jtzz","XX Community"}

[0093] In operating S410, obtain the sending interface address.

[0094] In operation S411, the receiver number is queried by the interface number.

[0095] In operation S412, the receiver number is queried by the interface number.

[0096] The service calls the database, passing the AccID parameter to query the corresponding recipient URL and API request type. Alternatively, it can be based on converting "AccID111123" into a hash value to query the recipient's URL.

[0097] The call information is sent to the corresponding recipient and the interface request type to achieve information forwarding. Upon receiving the return information from the recipient, the service transforms the return information through steps S403-S412 and returns it to the caller, completing the entire interface call process.

[0098] It is understandable that the cross-system information transmission process from "downstream system to upstream system" is basically the same as that from "upstream system to downstream system", so it will not be elaborated here.

[0099] In the embodiments of this disclosure, the pre-defined conversion rules and addresses of multiple different downstream interfaces are integrated in the intermediate layer. Configuration can be implemented only in the intermediate layer system, eliminating the need for configuration in the upstream and downstream systems. By matching these pre-defined conversion rules and addresses with field structures, the pre-defined conversion rules of each downstream system interface can be accurately matched, achieving highly efficient data conversion. Furthermore, the entire processing method reduces the use of hard-coding, thus reducing the error rate.

[0100] Based on the above-described cross-system information transmission method, this disclosure also provides a cross-system information transmission device. The following will be combined with... Figure 5 The device is described in detail.

[0101] Figure 5 A schematic block diagram of a cross-system information transmission device according to an embodiment of the present disclosure is shown.

[0102] like Figure 5 As shown, the cross-system information transmission device 500 of this embodiment includes an information receiving module 510, an information parsing module 520, a field calculation module 530, a matching module 540, an information conversion module 550, and an information transmission module 560.

[0103] The information receiving module 510 is used to receive information from the upstream system. In one embodiment, the information receiving module 510 can be used to perform the operation S210 described above, which will not be repeated here.

[0104] The information parsing module 520 is used to parse the upstream system information to obtain the field structure. In one embodiment, the information parsing module 520 can be used to perform the operation S220 described above, which will not be repeated here.

[0105] The field calculation module 530 is used to calculate the field structure to obtain matching information. In one embodiment, the field calculation module 530 can be used to perform the operation S230 described above, which will not be repeated here.

[0106] The matching module 540 is used to match a preset matching value based on the matching information to obtain a preset conversion rule and a downstream system address. In one embodiment, the matching module 540 can be used to perform the operation S240 described above, which will not be repeated here.

[0107] The information conversion module 550 is used to convert the upstream system information to obtain downstream system information based on the preset conversion rules. In one embodiment, the information conversion module 550 can be used to perform the operation S250 described above, which will not be repeated here.

[0108] The information transmission module 560 is used to transmit downstream system information to a target downstream system based on the downstream system address. In one embodiment, the information transmission module 560 can be used to perform the operation S260 described above, which will not be repeated here.

[0109] According to an embodiment of this disclosure, the information parsing module 520 is further configured to segment the upstream system information based on preset characters to obtain multiple fields; and to form the field structure based on the multiple fields.

[0110] According to an embodiment of this disclosure, the field calculation module 530 is further configured to calculate the field structure based on a hash algorithm to obtain the upstream system hash encoding value.

[0111] According to an embodiment of this disclosure, the matching module 540 is further configured to match the pre-stored hash code value with the hash code value of the upstream system to obtain an address mapping table, wherein the address mapping table includes a mapping relationship between the upstream system address and the downstream system address; and to look up the downstream system address based on the address mapping table.

[0112] According to embodiments of this disclosure, the mapping relationship between the upstream system address and the downstream system address is many-to-many. The apparatus further includes: a registration center, configured to receive a new downstream system address reported by the downstream system when the downstream system address changes; and to adjust the address mapping table based on the new downstream system address.

[0113] According to an embodiment of this disclosure, the information transmission module 560 is further configured to concatenate the downstream system address and the downstream system information to transmit the downstream system information to the target downstream system.

[0114] According to an embodiment of this disclosure, the information parsing module 520 is further configured to parse the header field to obtain the field structure.

[0115] In the embodiments of this disclosure, the pre-defined conversion rules and addresses of multiple different downstream interfaces are integrated in the intermediate layer. Configuration can be implemented only in the intermediate layer system, eliminating the need for configuration in the upstream and downstream systems. By matching these pre-defined conversion rules and addresses with field structures, the pre-defined conversion rules of each downstream system interface can be accurately matched, achieving highly efficient data conversion. Furthermore, the entire processing method reduces the use of hard-coding, thus reducing the error rate.

[0116] According to embodiments of this disclosure, any multiple modules among the information receiving module 510, information parsing module 520, field calculation module 530, matching module 540, information conversion module 550, and information transmission module 560 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least some of the functions of one or more of these modules can be combined with at least some of the functions of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the information receiving module 510, information parsing module 520, field calculation module 530, matching module 540, information conversion module 550, and information transmission module 560 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in a suitable combination of any of these. Alternatively, at least one of the information receiving module 510, information parsing module 520, field calculation module 530, matching module 540, information conversion module 550, and information transmission module 560 may be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0117] Figure 6 A block diagram of an electronic device suitable for implementing a cross-system information transmission method according to an embodiment of the present disclosure is shown schematically.

[0118] like Figure 6As shown, an electronic device 600 according to an embodiment of this disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage portion 608 into a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of this disclosure.

[0119] RAM 603 stores various programs and data required for the operation of electronic device 600. Processor 601, ROM 602, and RAM 603 are interconnected via bus 604. Processor 601 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 602 and / or RAM 603. It should be noted that the programs may also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0120] According to embodiments of this disclosure, the electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to a bus 604. The electronic device 600 may also include one or more of the following components connected to the I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 610 as needed so that computer programs read from it can be installed into the storage section 608 as needed.

[0121] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0122] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 602 and / or RAM 603 and / or one or more memories other than ROM 602 and RAM 603 described above.

[0123] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of this disclosure.

[0124] When the computer program is executed by the processor 601, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0125] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 609, and / or installed from the removable medium 611. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0126] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 609, and / or installed from the removable medium 611. When the computer program is executed by the processor 601, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0127] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0128] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0129] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0130] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A cross-system information transmission method, comprising: receiving upstream system information; parsing the upstream system information to obtain a field structure; calculating the field structure to obtain matching information; matching a preset matching value based on the matching information to obtain a preset conversion rule and a downstream system address; converting the upstream system information based on the preset conversion rule to obtain downstream system information; and transmitting the downstream system information to a target downstream system based on the downstream system address. The calculation of the field structure to obtain matching information comprises calculating the field structure based on a hash algorithm to obtain an upstream system hash code value. The preset matching value is a pre-stored hash code, and the matching of the preset matching value based on the matching information comprises matching the pre-stored hash code value based on the upstream system hash code value to obtain an address mapping table, wherein the address mapping table comprises a mapping relationship between an upstream system address and a downstream system address; and the downstream system address is found based on the address mapping table. The parsing of the upstream system information to obtain a field structure comprises:

2. The method of claim 1, wherein, segmenting based on a preset character in the upstream system information to obtain a plurality of fields; and forming the field structure based on the plurality of fields. The mapping relationship between the upstream system address and the downstream system address is many-to-many.

3. The method of claim 1, wherein, The method further comprises: in the case where the downstream system address changes, receiving a new downstream system address reported from the downstream system; and adjusting the address mapping table based on the new downstream system address. The transmission of the downstream system information to a target downstream system based on the downstream system address comprises:

4. The method of claim 1, wherein, concatenating the downstream system address and the downstream system information to transmit the downstream system information to a target downstream system. The upstream system information at least comprises a header field.

5. The method of any one of claims 1, 2, 3, or 4, wherein, The parsing of the upstream system information to obtain a field structure comprises: parsing the header field to obtain a field structure. 6.A cross-system information transmission device, comprising: an information receiving module configured to receive upstream system information; an information parsing module configured to parse the upstream system information to obtain a field structure; a field calculation module configured to calculate the field structure to obtain matching information; a matching module configured to match a preset matching value based on the matching information to obtain a preset conversion rule and a downstream system address; an information conversion module configured to convert the upstream system information based on the preset conversion rule to obtain downstream system information; and an information transmission module configured to transmit the downstream system information to a target downstream system based on the downstream system address. The calculation of the field structure to obtain matching information comprises calculating the field structure based on a hash algorithm to obtain an upstream system hash code value. ​ ​ The preset matching value is a pre-stored hash code. The matching of the preset matching value based on the matching information, the preset conversion rule and the downstream system address are obtained, including: matching the pre-stored hash code value based on the upstream system hash code value, to obtain an address mapping table, wherein the address mapping table includes a mapping relationship between the upstream system address and the downstream system address; and searching the downstream system address based on the address mapping table. 7.An electronic device, comprising: one or more processors; a memory device for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, enable the one or more processors to perform the method according to any one of claims 1-5. 8.A computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the method according to any one of claims 1-5. 9.A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-5.

Images