Bitmap-based service cross-system interaction method, architecture, equipment and medium

Abstract

The embodiment of the invention relates to the technical field of financial science and technology, and discloses a business cross-system interaction method based on a bitmap, an architecture, equipment and a medium. The method is executed by a subsystem end in a service cross-system interaction architecture, and comprises the following steps: when a service interaction message is sent to a main system end in the service cross-system interaction architecture, generating a bitmap field according to an element field in the service interaction message; wherein the bitmap field records the starting state of each element field in the service interaction message; and adding the bitmap field into the service interaction message, and sending the service interaction message to the main system end, so that the main system end performs service processing according to the bitmap field. By adding the bitmap field in the message, whether the element field is started or not can be determined, the reasonability of whether the element field is started or not does not need to be analyzed in service processing, the communication cost during service cross-system interaction is reduced, and the service processing efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of financial technology, and in particular to a bitmap-based cross-system business interaction method, architecture, device and medium. Background Art

[0002] In the financial sector, multiple systems often manage the same business data. Due to the diverse product content maintained by these systems, cross-system interactions rely on numerous fields.

[0003] To ensure consistency across multiple systems, a significant amount of code must be added to determine whether element fields need to be transmitted during system interactions, as well as the rationality of transmitting these elements. For example, during business interactions, the main system must determine why the subsystem did not transmit element field A. If element field A is not transmitted, further determination must be made based on other element fields to determine how to proceed within the current business. This results in cumbersome business interaction and communication, and inefficient business processing. Summary of the Invention

[0004] The present invention provides a bitmap-based business cross-system interaction method, architecture, device and medium, which can clarify the activation status of element fields through bitmap fields, reduce business communication costs and improve business processing efficiency.

[0005] According to one aspect of the present invention, a bitmap-based cross-system business interaction method is provided. The method is executed by a subsystem end in a cross-system business interaction architecture, and the method includes:

[0006] When sending a service interaction message to the main system end in the service cross-system interaction architecture, generating a bitmap field according to the element field in the service interaction message;

[0007] The bitmap field records the enabled status of each element field in the service interaction message;

[0008] The bitmap field is added to the service interaction message, and the service interaction message is sent to the main system end, so that the main system end performs service processing according to the bitmap field.

[0009] According to one aspect of the present invention, a bitmap-based cross-system business interaction method is provided. The method is executed by a master system in a cross-system business interaction architecture, and the method includes:

[0010] Obtaining a service interaction message sent by a subsystem end in a service cross-system interaction architecture, and extracting a bitmap field in the service interaction message;

[0011] Business processing is performed according to the bitmap field.

[0012] According to one aspect of the present invention, a bitmap-based cross-system business interaction architecture is provided, the cross-system business interaction architecture comprising a main system end and at least one subsystem end; wherein:

[0013] The subsystem end is used to generate a bitmap field according to the element field in the business interaction message when sending the business interaction message to the main system end in the business cross-system interaction architecture;

[0014] The bitmap field records the enabled status of each element field in the service interaction message;

[0015] The subsystem end is configured to add the bitmap field to the service interaction message and send the service interaction message to the main system end;

[0016] The main system end is used to obtain the service interaction message sent by the subsystem end in the service cross-system interaction architecture, and extract the bitmap field in the service interaction message;

[0017] The main system end is used to perform service processing according to the bitmap field.

[0018] According to another aspect of the present invention, a bitmap-based cross-system business interaction device is provided. The device can be set at a subsystem end in a cross-system business interaction architecture. The device includes:

[0019] A bitmap field generation module is used to generate a bitmap field according to the element fields in the business interaction message when sending the business interaction message to the main system end in the business cross-system interaction architecture;

[0020] The bitmap field records the enabled status of each element field in the service interaction message;

[0021] The service interaction message sending module is used to add the bitmap field to the service interaction message and send the service interaction message to the main system end, so that the main system end performs service processing according to the bitmap field.

[0022] According to another aspect of the present invention, a bitmap-based cross-system business interaction device is provided. The device can be set at a main system end in a cross-system business interaction architecture. The device includes:

[0023] A bitmap field extraction module is used to obtain a service interaction message sent by a subsystem end in a service cross-system interaction architecture, and extract a bitmap field in the service interaction message;

[0024] A service processing module is used to perform service processing according to the bitmap field.

[0025] According to another aspect of the present invention, an electronic device is provided, comprising:

[0026] at least one processor; and

[0027] a memory communicatively connected to the at least one processor; wherein,

[0028] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute the bitmap-based cross-system business interaction method described in any embodiment of the present invention.

[0029] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the bitmap-based cross-system business interaction method described in any embodiment of the present invention when executed.

[0030] According to another aspect of the present invention, a computer program product is provided, comprising a computer program, wherein when executed by a processor, the computer program implements the bitmap-based cross-system service interaction method according to any embodiment of the present invention.

[0031] The technical solution of the embodiment of the present invention generates a bitmap field according to the element field in the business interaction message when sending a business interaction message to the main system end in the business cross-system interaction architecture; wherein the bitmap field records the enabled status of each element field in the business interaction message; the bitmap field is added to the business interaction message, and the business interaction message is sent to the main system end, so that the main system end performs business processing according to the bitmap field, thereby solving the problem of cumbersome business processing during business cross-system interaction. By adding the bitmap field to the message, it can be clearly stated whether the element field is enabled, and there is no need to analyze the rationality of whether the element field is enabled or not during business processing, thereby reducing the communication cost during business cross-system interaction and improving business processing efficiency.

[0032] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0034] Figure 1 This is a flowchart of a bitmap-based cross-system business interaction method provided according to the first embodiment of the present invention;

[0035] Figure 2 A schematic diagram of a service interaction message with an added bitmap field is shown;

[0036] Figure 3 This is a flowchart of a bitmap-based cross-system business interaction method provided according to the second embodiment of the present invention;

[0037] Figure 4 This is a schematic diagram of the structure of a bitmap-based cross-system business interaction architecture provided according to the third embodiment of the present invention;

[0038] Figure 5 This is a schematic diagram of the structure of a bitmap-based cross-system business interaction device provided according to a fourth embodiment of the present invention;

[0039] Figure 6 This is a schematic diagram of the structure of a bitmap-based cross-system business interaction device provided according to a fifth embodiment of the present invention;

[0040] Figure 7 It is a structural diagram of an electronic device for implementing the bitmap-based cross-system business interaction method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0041] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0042] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0043] Example 1

[0044] Figure 1 This is a flowchart of a bitmap-based cross-system business interaction method provided according to the first embodiment of the present invention. This embodiment is applicable to situations where multiple systems jointly manage business. The method can be executed by a subsystem end in the cross-system business interaction architecture. The subsystem end can be implemented in the form of hardware and / or software. The subsystem end can be configured in an electronic device such as a computer, server or controller. Figure 1 As shown, the method includes:

[0045] Step 110: When sending a service interaction message to the main system end in the service cross-system interaction architecture, a bitmap field is generated according to the element field in the service interaction message.

[0046] The cross-system business interaction architecture can include a main system end and at least one subsystem end. The main system end and the subsystem end jointly manage the business. Multiple subsystem ends can be set up in different areas. For example, in loan business processing, the main system end can be the device end where the primary data source is located, and the subsystem end can be the device end where the secondary data source is located. The secondary data source can obtain more comprehensive and rich loan business data. The main data source can conduct a business review based on the loan business data reported by the secondary data source to determine whether to make a loan, and then return to the secondary data source to execute the loan operation.

[0047] When business interactions occur between the main system and subsystems, the uploaded element fields are summarized and combined with business data to generate business interaction messages. Business interactions involve many element fields. For example, in loan transactions, business interactions can involve 200 to 300 element fields. Furthermore, different subsystems have their own unique interaction elements. For example, element A must be entered in subsystem 1, but not in subsystem 2. Consequently, the main system must analyze whether the corresponding subsystem should upload element A. This judgment on the rationality of this element upload increases the complexity of interactions between multiple systems.

[0048] Furthermore, business interactions between the main system and subsystems may occur multiple times. A subsystem might upload elements once and then, when it does, re-upload them. At this point, the subsystem might deem some elements unnecessary and thus omit them. However, the main system might consider these unuploaded elements essential and perform extensive code logic to evaluate whether the uploaded data is sufficient for effective business processing. This process of assessing the validity of these element uploads increases the complexity of interactions between multiple systems.

[0049] To ensure consistent element upload and reduce inconsistency in logic when interacting between the main system and subsystem, an embodiment of the present invention generates a bitmap field based on the element fields in the service interaction message. The bitmap field records the enabled status of each element field in the service interaction message, eliminating the need for the main system to determine whether an element should be uploaded and allowing it to directly process the service based on the bitmap field.

[0050] Among them, a bitmap, also known as a dot map, is an image storage format that represents an image in the form of a pixel grid. Each pixel has its specific position and color value, and these pixels are combined to form a complete image. However, in an embodiment of the present invention, a bitmap is used as a data structure for efficient bit-level operations. For example, a bitmap can be used to represent the Boolean value of the enabled state of each element field, so as to quickly determine whether each element field is enabled for business processing. In a bitmap data structure, it can be stored in the form of a byte or integer array in memory, and each bit can correspond to the enabled state of an element field.

[0051] Optionally, a bitmap field is generated based on the element fields in the business interaction message, including: obtaining a first element field set when conducting business interaction with the main system end, and extracting the element fields existing in the business interaction message to form a second element field set; taking the intersection of the first element field set and the second element field set as the third element field set, and marking the enabled status of the element fields in the third element field set as enabled; taking the complement of the first element field set relative to the third element field set as the fourth element field set, and marking the enabled status of the element fields in the fourth element field set as not enabled; generating a bitmap field based on the enabled status of the element fields in the third element field set and the element fields in the fourth element field set.

[0052] The first element field set can be a set of all element fields involved in a business interaction. The second element field set can be a set of element fields reported by the subsystem in this business interaction. By marking the element fields in the intersection of the first and second element field sets as enabled, the main system can directly know the element fields reported by the subsystem, eliminating the need to determine whether the element fields should be reported. This reduces communication costs during cross-system business interactions and improves business processing efficiency.

[0053] By marking the element fields that are not sent by the subsystem side, that is, the element fields in the complement of the first element field set relative to the third element field set, as not enabled, the main system side can directly determine that the subsystem side has not sent the element field without having to judge whether the element field should be sent, thereby reducing the communication cost during cross-system interaction of business and improving business processing efficiency.

[0054] By generating bitmap fields, the subsystem can perform analysis on the element fields to be sent up. The subsystem can clearly identify the element fields to be sent up and the element fields not to be sent up. The main system only needs to process business based on the sent results, reducing the main system's judgment work on the element fields to be sent up.

[0055] In a bitmap field, each element field can be marked with a flag to indicate its enabled state. For example, if an element field is enabled, it can be marked with a 1; if it is disabled, it can be marked with a 0. The bitmap field is generated based on the order of the element fields in the first element field set and the enabled state of each element field.

[0056] Step 120: Add the bitmap field to the service interaction message, and send the service interaction message to the main system end, so that the main system end performs service processing according to the bitmap field.

[0057] The bitmap field may be added at the end of the service interaction message. Figure 2 A schematic diagram of a service interaction message with an added bitmap field is shown. Figure 2 As shown in the figure, a bitmap field is added after the element is uploaded to indicate the elements uploaded by the subsystem. When the service interaction message is sent to the main system, the main system can directly extract the bitmap field from the service interaction message and determine the element fields reported by the subsystem and the element fields not reported based on the bitmap field. The main system then directly processes the service based on the uploaded result without having to determine the rationality of the uploaded element fields.

[0058] Optionally, adding the bitmap field to the service interaction message includes: verifying the bitmap field according to the service type; and adding the bitmap field to the service interaction message when the bitmap field verification passes.

[0059] The subsystem determines the rationality of the uploaded element fields. The subsystem can verify the bitmap fields based on the service type to determine whether the uploaded element fields are consistent with the expected upload. If they are consistent, the bitmap field verification is considered passed.

[0060] For example, in a loan transaction, Subsystem 1 at Location A can determine, based on the loan transaction, that Element A must be uploaded. Therefore, it checks the bitmap field to determine whether Element A is in the uploaded state. In another example, in a loan transaction, Subsystem 2 at Location B can determine, based on the loan transaction, that Element A cannot be uploaded. Therefore, it checks the bitmap field to determine whether Element A is in the unuploaded state. In another example, Subsystem 3 can determine, based on the transaction type, that the current upload is occurring after an element field has already been uploaded. Therefore, it determines that Element Field B does not need to be uploaded. Therefore, Subsystem 3 can check the bitmap field to determine whether Element B is in the unuploaded state.

[0061] When the bitmap field is verified, the subsystem side can add the bitmap field to the business interaction message, and then send the business interaction message to the main system side in the business cross-system interaction architecture.

[0062] The technical solution of this embodiment generates a bitmap field according to the element field in the business interaction message when sending a business interaction message to the main system end in the business cross-system interaction architecture; wherein the bitmap field records the enabled status of each element field in the business interaction message; the bitmap field is added to the business interaction message, and the business interaction message is sent to the main system end, so that the main system end performs business processing according to the bitmap field, thereby solving the problem of cumbersome business processing during business cross-system interaction. By adding the bitmap field to the message, it can be clearly stated whether the element field is enabled, and there is no need to analyze the rationality of whether the element field is enabled or not during business processing, thereby reducing the communication cost during business cross-system interaction and improving business processing efficiency.

[0063] Example 2

[0064] Figure 3 This is a flowchart of a bitmap-based cross-system business interaction method provided in accordance with the second embodiment of the present invention. This embodiment is applicable to situations where multiple systems jointly manage business. The method can be executed by the main system end in the cross-system business interaction architecture. The main system end can be implemented in the form of hardware and / or software. The main system end can be configured in an electronic device such as a computer, server or controller. The technical solution in this embodiment can be combined with the various optional solutions in one or more of the above embodiments. Figure 3 As shown, the method includes:

[0065] Step 310: Obtain a service interaction message sent by a subsystem end in the service cross-system interaction architecture, and extract a bitmap field in the service interaction message.

[0066] The main system end in the business cross-system interaction architecture can obtain the bitmap field at the end of the business interaction message.

[0067] Step 320: Perform business processing according to the bitmap field.

[0068] The main system can determine the activation status of each element field based on the bitmap field and perform business processing based on the activation status of each element field. When performing business processing based on the activation status of each element field, it can be processed directly based on the activation status of the element field, without having to determine the rationality of whether the element field is enabled or not. By performing business processing based on the bitmap field, business processing efficiency can be improved, business processing procedures on the main system can be standardized and simplified, and communication costs during business interactions can be reduced.

[0069] When the main system performs business processing, it can perform unified data legitimacy verification based on the enabled status of each element field in the bitmap field, thereby avoiding complex judgments and business processing scattered across multiple programs.

[0070] For example, the main system end can perform a basic legitimacy check on the element field, that is, the main system end verifies the attributes and input values ​​of the element field. Exemplarily, the main system end determines whether element A is enabled based on the bitmap field. If element A is enabled, a data check is performed on element A, such as determining whether the input value of element A meets the verification of the data dictionary. If element A is not enabled, the input of the value of element A is not allowed. The main system end determines whether element B is enabled based on the bitmap field. If element B is enabled, a data check is performed on element B, such as determining whether the input value of element B meets the verification of the data dictionary. If element B is not enabled, the input of the value of element B is not allowed. Similarly, the main system end can perform a basic legitimacy check on each element field one by one. Through basic legitimacy verification, the correctness of business processing can be guaranteed.

[0071] After the basic legitimacy check, business processing can be performed, or a difference feature check can be performed on the element fields. Optionally, business processing can be performed based on the bitmap field, including: obtaining the difference feature check conditions for the corresponding region based on the region to which the subsystem end belongs; determining whether the business interaction message sent by the subsystem end meets the difference feature check conditions based on the enabled status of each element field in the bitmap field; and performing business processing when the business interaction message meets the difference feature check conditions.

[0072] Subsystems in different regions are unique when handling business. Differential feature verification conditions are the conditions for performing element uniqueness verification on subsystems in different regions. For example, in the first region, the differential feature verification condition is that the first associated element field must be entered, such as element fields X, Y, and Z must be entered; in the second region, the differential feature verification condition is that the first element field cannot be entered, such as element field A cannot be entered; in the third region, the differential feature verification condition is that the second element field must be entered, such as element field A must be entered; and in the fourth region, the differential feature verification condition is that the third element field, such as element field D, is optional.

[0073] Based on the enabled status of each element field in the bitmap field sent by the subsystem end of the first region, it is determined whether the service interaction message sent by the subsystem end of the first region meets the corresponding difference feature verification condition, that is, the first associated element field must be entered. If element fields X, Y, and Z are not all enabled, an error is reported. Based on the enabled status of each element field in the bitmap field sent by the subsystem end of the second region, it is determined whether the service interaction message sent by the subsystem end of the second region meets the corresponding difference feature verification condition, that is, the first element field cannot be entered. If element field A is enabled, an error is reported. Based on the enabled status of each element field in the bitmap field sent by the subsystem end of the third region, it is determined whether the service interaction message sent by the subsystem end of the third region meets the corresponding difference feature verification condition, that is, the second element field must be entered. If element field A is not enabled, an error is reported. Based on the enabled status of each element field in the bitmap field sent by the subsystem end of the fourth region, it is determined whether the service interaction message sent by the subsystem end of the fourth region meets the corresponding difference feature verification condition, that is, the third element field is optional. If element field D is not required, verification is performed. Through the difference feature inspection, each subsystem end can be specifically checked to ensure that the business of each subsystem end is accurately processed.

[0074] After the difference feature verification, business processing can be performed, or business logic legitimacy can be determined. Business logic legitimacy determination can refer to the linkage between multiple element fields in the business processing. If the element fields in the business interaction message sent by the subsystem meet the linkage, further business processing can be performed.

[0075] Optionally, business processing is performed based on the bitmap field, including: in the linkage business, judging whether the elements of the linkage business meet the integrity based on the bitmap field; when the elements of the linkage business meet the integrity, obtaining the values ​​of each element corresponding to the linkage business in the business interaction message; judging whether the values ​​of each element of the linkage business meet the rationality of the business logic, and performing business processing when the values ​​of each element meet the business logic.

[0076] Integrity can be a requirement for multiple element fields within the same linkage business, requiring linkage checks on the main system. For example, if element fields A, B, C, and D are elements within the same business scenario and only A, B, and C are enabled, but D is not, the upstream subsystem can perform a linkage check and error reporting. Integrity checks ensure that linkage business elements are sent completely and accurately.

[0077] Business logic rationality can be defined as the linkage between the input values ​​of business logic rationality factor fields. For example, after the upstream subsystem has submitted all the factor fields, the specific values ​​submitted by factor fields A, B, C, and D are verified. For example, in business logic rationality, when factor field A is equal to 1, factor field B can only be equal to 3. If factor fields A and B do not meet this business logic rationality, an error is reported. By verifying the relationship between factor fields in the linkage business and the relationship between the factor field input values, the correctness of the linkage business processing can be guaranteed.

[0078] After the business logic legitimacy is judged, business processing can be performed, or business data can be updated in multiple scenarios. Optionally, business processing is performed based on the bitmap field, including: in a single element scenario, when the target element field associated with the single element scenario is enabled according to the bitmap field, the data table associated with the single element scenario is updated; in a joint element scenario, the enabled status of each element field in the joint element field is determined according to the bitmap field, and when at least one element field in the joint element field is enabled, the data table associated with the joint element scenario is updated.

[0079] For example, in a single-factor scenario, a bitmap field can be used to determine whether field A is enabled. If the business logic legitimacy determines that it is enabled, the data table associated with the single-factor scenario is updated. Alternatively, in a combined-factor scenario, a bitmap field can be used to determine whether fields B, C, and D are enabled. If any of these fields is enabled, the data table associated with the combined-factor scenario is updated. By using business logic judgment across multiple scenarios, the rationality of business processing can be ensured.

[0080] By combining the bitmap field to perform basic legality verification, difference feature inspection, business logic legality judgment, and business data updates in multiple scenarios, the code for business processing on the main system side can be greatly simplified, and input errors, regional difference errors, and business logic errors can be clarified, making data verification concise, accurate, complete, and easy to maintain. Finally, the business logic processing of multiple core programs is accurately guided to avoid erroneous update processing of non-value content. The method provided by the embodiment of the present invention can solve the problem of whether the element field should be sent when the main system side and the subsystem side interact with each other for business, simplify the communication between the main system side and the subsystem side, simplify the element field processing program when the main system side processes business, and unify the element field verification of multiple subsystem sides, greatly improving the feasibility and maintainability of the code, reducing the number of lines of code, and improving business processing efficiency.

[0081] The method provided by the embodiment of the present invention can improve the code readability of the main system side, simplify the logic, and reduce production problems. For example, before the method of the present invention is implemented, the main system side needs to determine that this is the specific business of the subsystem side, and in this business, the target element field needs to be uploaded. If the target element field is uploaded, the main system side needs to determine the content of the target element field and continue the relevant functions. If the target element field is not entered, the main system side needs to analyze whether the target element field should be entered, and analyze it in combination with other element fields, and combine various upstream and downstream processes to determine whether the target element field should be uploaded, or report an error, or supplement the default value to continue processing.

[0082] After implementing the method of the present invention, the main system can completely eliminate the logic used to maintain compatibility in business interactions for the sake of clarity. Specifically, when processing the target element field, the main system can directly process it based on the target element field's enable flag in the bitmap field, eliminating the need to determine whether the target element field should be sent. This makes the processing on the main system simple and clear. The method of the present invention reduces and lowers the communication costs between the main system and subsystems, increasing the operability and accuracy of development, troubleshooting, and program modifications.

[0083] Example 3

[0084] Figure 4 Schematic diagram of a bitmap-based cross-system interaction architecture according to the third embodiment of the present invention. Figure 4 As shown, the cross-system business interaction architecture 400 includes a main system end 410 and at least one subsystem end 420.

[0085] The subsystem side is used to generate a bitmap field according to the element field in the business interaction message when sending the business interaction message to the main system side in the business cross-system interaction architecture;

[0086] Among them, the bitmap field records the activation status of each element field in the service interaction message;

[0087] The subsystem side is used to add the bitmap field to the service interaction message and send the service interaction message to the main system side;

[0088] The main system end is used to obtain the business interaction message sent by the subsystem end in the business cross-system interaction architecture and extract the bitmap field in the business interaction message;

[0089] The main system side is used to perform business processing based on the bitmap fields.

[0090] Optional, subsystem side, specifically used for:

[0091] Acquire a first element field set during business interaction with the main system end, and extract element fields present in the business interaction message to form a second element field set;

[0092] The intersection of the first feature field set and the second feature field set is used as the third feature field set, and the enabled state of the feature fields in the third feature field set is marked as enabled;

[0093] The complement of the first feature field set relative to the third feature field set is used as the fourth feature field set, and the enabled state of the feature fields in the fourth feature field set is marked as disabled;

[0094] Generates a bitmap field based on the enabled status of the feature fields in the third feature field set and the feature fields in the fourth feature field set.

[0095] Optionally, the subsystem side is also used for:

[0096] Check the bitmap field according to the business type;

[0097] When the bitmap field passes the verification, the bitmap field is added to the service interaction message.

[0098] Optional, main system side, specifically used for:

[0099] In the linkage business, the integrity of the elements of the linkage business is determined based on the bitmap field;

[0100] When the elements of the linkage service meet the requirements of integrity, the values ​​of the elements corresponding to the linkage service are obtained in the service interaction message;

[0101] Determine whether the values ​​of each element of the linkage business meet the rationality of the business logic, and perform business processing when the values ​​of each element meet the business logic.

[0102] Optional, main system side, specifically used for:

[0103] According to the region to which the subsystem end belongs, obtain the differential characteristic inspection conditions of the corresponding region;

[0104] According to the enabled state of each element field in the bitmap field, determine whether the service interaction message sent by the subsystem side meets the difference feature inspection conditions;

[0105] When the service interaction message meets the difference feature inspection conditions, service processing is performed.

[0106] Optional, main system side, specifically used for:

[0107] In a single feature scenario, when the target feature field associated with the single feature scenario is enabled based on the bitmap field, the data table associated with the business of the single feature scenario is updated;

[0108] In the joint feature scenario, the enabled status of each feature field in the joint feature field is determined according to the bitmap field. When at least one feature field in the joint feature field is enabled, the data table associated with the joint feature scenario is updated.

[0109] The bitmap-based cross-system business interaction architecture provided by the embodiment of the present invention can execute the bitmap-based cross-system business interaction method provided by any embodiment of the present invention, and has the corresponding functional structure and beneficial effects of the execution method.

[0110] Example 4

[0111] Figure 5 This is a schematic diagram of the structure of a bitmap-based cross-system interaction device according to the fourth embodiment of the present invention. The device can be set at the subsystem end in the cross-system interaction architecture of the business. Figure 5 As shown, the device includes: a bitmap field generating module 510 and a service interaction message sending module 520. Among them:

[0112] The bitmap field generation module 510 is used to generate a bitmap field according to the element fields in the business interaction message when sending the business interaction message to the main system end in the business cross-system interaction architecture;

[0113] Among them, the bitmap field records the activation status of each element field in the service interaction message;

[0114] The service interaction message sending module 520 is configured to add a bitmap field to the service interaction message and send the service interaction message to the main system end so that the main system end performs service processing according to the bitmap field.

[0115] Optionally, the bitmap field generating module 510 is specifically configured to:

[0116] Acquire a first element field set during business interaction with the main system end, and extract element fields present in the business interaction message to form a second element field set;

[0117] The intersection of the first feature field set and the second feature field set is used as the third feature field set, and the enabled state of the feature fields in the third feature field set is marked as enabled;

[0118] The complement of the first feature field set relative to the third feature field set is used as the fourth feature field set, and the enabled state of the feature fields in the fourth feature field set is marked as disabled;

[0119] Generates a bitmap field based on the enabled status of the feature fields in the third feature field set and the feature fields in the fourth feature field set.

[0120] Optionally, the service interaction message sending module 520 is specifically configured to:

[0121] Check the bitmap field according to the business type;

[0122] When the bitmap field passes the verification, the bitmap field is added to the service interaction message.

[0123] The bitmap-based cross-system business interaction device provided in the embodiment of the present invention can execute the bitmap-based cross-system business interaction method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0124] Example 5

[0125] Figure 6 Schematic diagram of a bitmap-based cross-system interaction device according to the fifth embodiment of the present invention. Figure 6 As shown, the device includes: a bitmap field extraction module 610 and a service processing module 620. Among them:

[0126] The bitmap field extraction module 610 is used to obtain the service interaction message sent by the subsystem end in the service cross-system interaction architecture and extract the bitmap field in the service interaction message;

[0127] The service processing module 620 is configured to perform service processing according to the bitmap field.

[0128] Optionally, the business processing module 620 includes:

[0129] An element integrity judgment unit is used to judge whether the elements of the linkage business meet the integrity requirements according to the bitmap field in the linkage business;

[0130] An element value acquisition unit, configured to acquire the element values ​​corresponding to the linkage service in the service interaction message when the elements of the linkage service meet the integrity requirements;

[0131] The first business processing unit is used to determine whether each element value of the linkage business meets the business logic rationality, and perform business processing when each element value meets the business logic.

[0132] Optionally, the business processing module 620 includes:

[0133] The inspection condition acquisition unit is used to obtain the differential and characteristic inspection conditions of the corresponding area according to the area to which the subsystem end belongs;

[0134] A test condition judgment unit, configured to determine whether a service interaction message sent by the subsystem side meets a difference feature test condition based on the enabled state of each element field in the bitmap field;

[0135] The second service processing unit is configured to perform service processing when the service interaction message meets the difference feature inspection condition.

[0136] Optionally, the business processing module 620 is specifically configured to:

[0137] A single element scenario update unit is used to update a data table of a business associated with a single element scenario when, in a single element scenario, the target element field associated with the single element scenario is determined to be enabled based on the bitmap field;

[0138] The joint feature scenario update unit is used to determine the enabled status of each feature field in the joint feature field according to the bitmap field in the joint feature scenario, and when at least one feature field in the joint feature field is enabled, update the data table of the business associated with the joint feature scenario.

[0139] The bitmap-based cross-system business interaction device provided in the embodiment of the present invention can execute the bitmap-based cross-system business interaction method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0140] The information collected is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with the relevant laws, regulations and standards of relevant countries and regions, take necessary confidentiality measures, do not violate public order and good customs, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0141] Example 6

[0142] Figure 7 A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or claimed herein.

[0143] like Figure 7As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., which is communicatively connected to the at least one processor 11. The memory stores a computer program that can be executed by the at least one processor. The processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 into the random access memory (RAM) 13. Various programs and data required for the operation of the electronic device 10 can also be stored in the RAM 13. The processor 11, ROM 12, and RAM 13 are connected to each other via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0144] Multiple components in the electronic device 10 are connected to the I / O interface 15, including an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0145] The processor 11 can be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various processors that run machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the bitmap-based cross-system business interaction method.

[0146] In some embodiments, the bitmap-based cross-system business interaction method can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the bitmap-based cross-system business interaction method described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to execute the bitmap-based cross-system business interaction method in any other appropriate manner (for example, by means of firmware).

[0147] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0148] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the computer program is executed by the processor, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The computer program may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0149] In the context of the present invention, computer-readable storage media can be tangible media that can contain or store a computer program for use with an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. Computer-readable storage media can include but are not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, computer-readable storage media can be machine-readable signal media. More specific examples of machine-readable storage media can include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0150] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0151] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0152] A computing system may include clients and servers. The clients and servers are typically remote from each other and typically interact via a communication network. This client-server relationship arises through computer programs running on the respective computers, creating a client-server relationship. The server may be a cloud server, also known as a cloud computing server or cloud host. This server is a hosting product within the cloud computing service ecosystem that addresses the management difficulties and limited scalability of traditional physical hosting and VPS services.

[0153] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the present invention can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved. This is not limited herein.

[0154] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. A bitmap-based cross-system business interaction method, characterized in that: The method is executed by a subsystem end in a business cross-system interaction architecture, and includes: When sending a service interaction message to the main system end in the service cross-system interaction architecture, generating a bitmap field according to the element field in the service interaction message; The bitmap field records the enabled status of each element field in the service interaction message; The bitmap field is added to the service interaction message, and the service interaction message is sent to the main system end, so that the main system end performs service processing according to the bitmap field.

2. The method according to claim 1, characterized in that Generating a bitmap field according to the element field in the service interaction message includes: Acquire a first element field set during business interaction with the primary system end, and extract element fields present in the business interaction message to form a second element field set; Taking the intersection of the first feature field set and the second feature field set as a third feature field set, and marking the enabled state of the feature fields in the third feature field set as enabled; Using the complement of the first element field set relative to the third element field set as a fourth element field set, and marking the enabled status of the element fields in the fourth element field set as disabled; A bitmap field is generated according to the enabled states of the element fields in the third element field set and the element fields in the fourth element field set.

3. The method according to claim 1, characterized in that Adding the bitmap field to the service interaction message includes: Checking the bitmap field according to the service type; When the bitmap field passes the verification, the bitmap field is added to the service interaction message.

4. A bitmap-based cross-system business interaction method, characterized in that: The method is executed by a main system end in a business cross-system interaction architecture, and includes: Obtaining a service interaction message sent by a subsystem end in a service cross-system interaction architecture, and extracting a bitmap field in the service interaction message; Business processing is performed according to the bitmap field.

5. The method according to claim 4, characterized in that Performing service processing according to the bitmap field includes: In the linkage service, judging whether the elements of the linkage service meet the integrity requirements according to the bitmap field; When the elements of the linkage service meet the integrity, obtaining the values ​​of each element corresponding to the linkage service in the service interaction message; It is determined whether the values ​​of each element of the linkage business meet the rationality of business logic, and when the values ​​of each element meet the rationality of business logic, business processing is performed.

6. The method according to claim 4, characterized in that Performing service processing according to the bitmap field includes: According to the region to which the subsystem terminal belongs, obtaining the difference characteristic inspection conditions of the corresponding region; determining, based on the enabled state of each element field in the bitmap field, whether the service interaction message sent by the subsystem side meets the difference feature verification condition; When the service interaction message meets the difference feature inspection condition, service processing is performed.

7. The method according to claim 4, characterized in that Performing service processing according to the bitmap field includes: In a single-element scenario, when the target element field associated with the single-element scenario is determined to be enabled according to the bitmap field, a data table of the service associated with the single-element scenario is updated; In the joint element scenario, the activation status of each element field in the joint element field is determined according to the bitmap field. When at least one element field in the joint element field is enabled, the data table of the business associated with the joint element scenario is updated.

8. A bitmap-based cross-system business interaction architecture, comprising a main system end and at least one subsystem end; wherein: The subsystem end is used to generate a bitmap field according to the element field in the business interaction message when sending the business interaction message to the main system end in the business cross-system interaction architecture; The bitmap field records the enabled status of each element field in the service interaction message; The subsystem end is configured to add the bitmap field to the service interaction message and send the service interaction message to the main system end; The main system end is used to obtain the service interaction message sent by the subsystem end in the service cross-system interaction architecture, and extract the bitmap field in the service interaction message; The main system end is used to perform service processing according to the bitmap field.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute the bitmap-based cross-system business interaction method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the bitmap-based cross-system business interaction method according to any one of claims 1 to 7 when executed.

11. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements the bitmap-based cross-system business interaction method according to any one of claims 1 to 7.

Images