A business invoice data interaction method and device, electronic equipment and storage medium

Abstract

The present application relates to a kind of enterprise invoice data interaction method, device, electronic equipment and storage medium, the enterprise invoice data interaction method is by obtaining the current parallel sending and receiving volume of enterprise server, the multiple target interaction servers of enterprise server, based on current parallel sending and receiving volume, the total sending and receiving volume of enterprise server next time is estimated, if total sending and receiving volume is greater than or equal to preset sending and receiving volume threshold, enterprise server sends first target invoice data interaction request to one of target interaction servers, if the first target invoice data obtained by request is all invoice data corresponding to demand information, the interaction process between enterprise server ends;The present application can avoid enterprise server simultaneously with multiple target interaction servers to carry out data interaction, leading to the load of enterprise server to surge under the condition that total sending and receiving volume is greater than or equal to preset sending and receiving volume threshold.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, electronic device and storage medium for interacting with enterprise invoice data. Background Art

[0002] When an enterprise conducts purchase and sales activities with upstream or downstream companies, it needs to synchronize invoice data with upstream and downstream companies or the tax system to complete reconciliation between enterprises and tax settlement between enterprises and the tax system.

[0003] When the business volume of an enterprise surges, the enterprise server interacts with multiple upstream or downstream companies in a centralized manner to exchange enterprise invoice data. At this time, the load on the enterprise server will also increase sharply, and the synchronization process of invoice data will experience delays, packet loss, and even cause the service system to crash, making it impossible to provide normal data interaction services.

[0004] Therefore, it is particularly important to avoid a surge in the load on enterprise servers through reasonable invoice data interaction without affecting the demand for invoice data usage between enterprises. Summary of the Invention

[0005] In view of the shortcomings of the prior art described above, the present application provides a method, device, electronic device and storage medium for interacting with enterprise invoice data to solve the above technical problems.

[0006] The present invention provides a method for interacting with invoice data of an enterprise, the method comprising: obtaining the current parallel receiving and sending volume of an enterprise server and a plurality of target interaction servers of the enterprise server, the plurality of target interaction servers being determined by the demand information of the enterprise, the demand information comprising a plurality of information parts, the plurality of target interaction servers corresponding one to one with the plurality of information parts, each of the target interaction servers generating different target invoice data according to the corresponding information part, and each of the target interaction servers storing the target invoice data generated by other target interaction servers; estimating the total receiving and sending volume of the enterprise server at the next moment based on the current parallel receiving and sending volume and the amount of interaction requests to be sent, the amount of interaction requests to be sent corresponding to the number of the plurality of target interaction servers; if the total receiving and sending volume is greater than or equal to a preset receiving and sending volume threshold, the enterprise server The server sends a first target invoice data interaction request to one of the target interaction servers. If the first target invoice data obtained by the request is all the invoice data corresponding to the demand information, the interaction process between the enterprise servers ends; if the first target invoice data obtained by the request is part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interaction server that has not interacted, until all the invoice data obtained by the request are all the invoice data corresponding to the demand information, then the interaction process between the enterprise servers ends, and the first target invoice data interaction request includes the demand information; if the total sending and receiving volume is less than the preset sending and receiving volume threshold, the enterprise server sends the first target invoice data interaction request to the multiple target interaction servers to obtain all the invoice data corresponding to the demand information.

[0007] In one embodiment of the present invention, based on the current parallel sending and receiving volume and the amount of interaction requests to be sent, estimating the total sending and receiving volume of the enterprise server includes: obtaining the amount of interaction requests received by the enterprise server at the next moment and the amount of interaction requests to be ended at the enterprise server at the current moment, the amount of interaction requests to be ended is determined according to the expected end time of the interaction request, and the amount of received interaction requests is determined according to the agreed start time of the interaction request; adding the current parallel sending and receiving volume, the amount of interaction requests to be sent and the amount of received interaction requests to obtain a first sending and receiving volume; calculating the difference between the first sending and receiving volume and the amount of interaction requests to be ended to obtain the total sending and receiving volume.

[0008] In one embodiment of the present invention, if the first target invoice data interaction request includes the address of the enterprise server, after the enterprise server sends the first target invoice data interaction request to one of the target interaction servers, the method further includes: the target interaction server authenticates the address of the enterprise server; if the identity authentication is successful, the target interaction server performs permission verification on the enterprise server, and if the permission verification is successful, the successful verification is used as the first access verification result; if the identity authentication is unsuccessful or the permission verification is unsuccessful, the failed verification is used as the first access verification result.

[0009] In one embodiment of the present invention, after obtaining the first access verification result, the method also includes: if the first access verification result is successful verification, the target interactive server generates target invoice data according to the corresponding information part in the demand information, reads the external target invoice data stored in the target interactive server, and the external target invoice data is generated by other target interactive servers; if the external target invoice data exists in the invoice data corresponding to the demand information, the target interactive server forwards the first target invoice data interaction request to the target interactive server that generates the external target invoice data, and performs a second access verification on the first target invoice data interaction request through the target interactive server that generates the external target invoice data, and sends the first target invoice data to the enterprise server according to the second access verification result; if the external target invoice data does not exist in the demand information, the target invoice data is used as the first target invoice data; if the first access verification result is verification failure, the first target invoice data interaction request is discarded.

[0010] In one embodiment of the present invention, the process of sending the first target invoice data to the enterprise server based on the second access verification result includes: if the second access verification result is successful verification, the target interactive server that generates the external target invoice data sends the verification success information to the target interactive server, and the target interactive server combines the target invoice data and the external target invoice data and sends it to the enterprise server as the first target invoice data; if the second access verification result is failed verification, the target interactive server that generates the external target invoice data sends the verification failure information to the target interactive server, and the target interactive server sends the first target invoice data to the enterprise server.

[0011] In one embodiment of the present invention, the enterprise server sends a second target invoice data interaction request to a non-interacted target interaction server until all the invoice data obtained by the request are all the invoice data corresponding to the demand information. The process includes: deleting the demand information corresponding to the first target invoice data from the demand information to obtain updated demand information; determining the first target interaction server based on the updated demand information, and using the first target interaction server as the non-interacted target interaction server; the enterprise server sends a second target invoice data interaction request to one of the non-interacted target interaction servers until all the second target invoice data obtained by the request are all the invoice data corresponding to the updated demand information, and the second target invoice data interaction request includes the updated demand information.

[0012] In one embodiment of the present invention, the process of the enterprise server sending the first target invoice data interaction request to one of the target interactive servers includes: using the address of the enterprise server as the source address; using the address of the target interactive server as the destination address; using the demand information as the request content; encapsulating the source address, destination address and request content according to a predetermined message format to obtain the first target invoice data interaction request; and the enterprise server sending the first target invoice data interaction request to the target interactive server.

[0013] According to one aspect of an embodiment of the present invention, an enterprise invoice data interaction device is provided, including: a transceiver volume acquisition module, used to obtain the current parallel transceiver volume of the enterprise server and multiple target interaction servers of the enterprise server, the multiple target interaction servers are determined by the enterprise's demand information, the demand information includes multiple information parts, the multiple target interaction servers correspond one-to-one to the multiple information parts, each of the target interaction servers generates different target invoice data according to the corresponding information part, and each of the target interaction servers stores the target invoice data generated by other target interaction servers; a transceiver volume estimation module, used to estimate the total transceiver volume of the enterprise server at the next moment based on the current parallel transceiver volume and the amount of interaction requests to be sent, the amount of interaction requests to be sent corresponds to the number of the multiple target interaction servers; an invoice data interaction module, used to estimate the total transceiver volume of the enterprise server at the next moment if the total transceiver volume is greater than or equal to A preset sending and receiving volume threshold is set, and the enterprise server sends a first target invoice data interaction request to one of the target interactive servers. If the first target invoice data obtained by the request is all the invoice data corresponding to the demand information, the interaction process between the enterprise servers ends; if the first target invoice data obtained by the request is part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interactive server that has not interacted, until all the invoice data obtained by the request are all the invoice data corresponding to the demand information, then the interaction process between the enterprise servers ends, and the first target invoice data interaction request contains the demand information; a sending and receiving volume comparison module is used for, if the total sending and receiving volume is less than the preset sending and receiving volume threshold, the enterprise server sends the first target invoice data interaction request to the multiple target interactive servers to obtain all the invoice data corresponding to the demand information.

[0014] According to one aspect of an embodiment of the present invention, an electronic device is provided, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device implements the enterprise invoice data interaction method as described above.

[0015] According to one aspect of an embodiment of the present invention, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer executes the above-mentioned enterprise invoice data interaction method.

[0016] Advantageous Effects of the Present Invention: The present invention obtains the current parallel transceiver volume of an enterprise server and multiple target interactive servers of the enterprise server, and estimates the total transceiver volume of the enterprise server at the next moment based on the current parallel transceiver volume and the number of pending interactive requests. If the total transceiver volume is greater than or equal to a preset transceiver volume threshold, the enterprise server sends a first target invoice data interaction request to one of the target interactive servers, thereby avoiding the enterprise server from interacting with multiple target interactive servers simultaneously, which would cause a surge in the load on the enterprise server. If the first target invoice data obtained in the request is all of the invoice data corresponding to the demand information, the interaction process between the enterprise servers ends. If the first target invoice data obtained in the request is only part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interactive server that has not interacted, and the interaction process between the enterprise servers ends until all of the invoice data obtained in the request is all of the invoice data corresponding to the demand information. Therefore, if the total transceiver volume is greater than or equal to the preset transceiver volume threshold, the enterprise server can obtain all of the required invoice data through a number of interactions less than the number of target interactive servers, thereby reducing the load on the enterprise server without affecting the demand for invoice data between enterprises.

[0017] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings are incorporated into and constitute a part of the specification, illustrating embodiments consistent with the present application and, together with the specification, serving to explain the principles of the present application. It is obvious that the drawings described below are merely some embodiments of the present application, and a person of ordinary skill in the art can derive other drawings based on these drawings without inventive effort. In the drawings:

[0019] Figure 1 is a schematic diagram of an exemplary system architecture shown in an exemplary embodiment of the present application;

[0020] Figure 2 This is a flow chart of a method for interacting with enterprise invoice data, shown in an exemplary embodiment of the present application;

[0021] Figure 3 A block diagram of a device for interacting with corporate invoice data suitable for implementing an embodiment of the present application is shown;

[0022] Figure 4 A schematic diagram of the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0023] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. When the following description refers to the drawings, identical numerals in different figures represent identical or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0024] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0025] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0026] In this application, "plurality" refers to two or more. "And / or" describes the relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0027] The technical solutions of the embodiments of this application involve computer, communication and other related technologies, and are specifically described through the following embodiments:

[0028] Figure 1 It is a schematic diagram of an exemplary system architecture shown in an exemplary embodiment of the present application.

[0029] Reference Figure 1As shown, the system architecture may include a monitoring device 101 and a computer device 102. The computer device 102 may be at least one of a desktop graphics processing unit (GPU) computer, a GPU computing cluster, a neural network computer, and the like. Relevant technicians can use the computer device 102 to obtain the current parallel transceiver volume of the enterprise server and multiple target interactive servers of the enterprise server. Based on the current parallel transceiver volume and the number of pending interactive requests, the total transceiver volume of the enterprise server at the next moment is estimated. If the total transceiver volume is greater than or equal to a preset transceiver volume threshold, the enterprise server sends a first target invoice data interaction request to one of the target interactive servers. If the first target invoice data obtained in the request is all of the invoice data corresponding to the demand information, the interaction process between the enterprise servers ends. If the first target invoice data obtained in the request is only part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interactive server that has not interacted with the enterprise server. This process ends until all of the invoice data obtained in the request is all of the invoice data corresponding to the demand information. The first target invoice data interaction request contains the demand information. If the total transceiver volume is less than the preset transceiver volume threshold, the enterprise server sends the first target invoice data interaction request to multiple target interactive servers to obtain all of the invoice data corresponding to the demand information. The monitoring device 101 is used to monitor the current parallel transceiver volume of the enterprise server and the enterprise's demand information, and provide it to the computer device 102 for processing.

[0030] Illustratively, after obtaining the current parallel transceiver volume of the enterprise server of the monitoring device 101 and the enterprise's demand information, the computer device 102 estimates the total transceiver volume of the enterprise server at the next moment based on the current parallel transceiver volume and the number of interaction requests to be sent. If the total transceiver volume is greater than or equal to a preset transceiver volume threshold, the enterprise server sends a first target invoice data interaction request to one of the target interaction servers, thereby avoiding the enterprise server from interacting with multiple target interaction servers at the same time, which would cause a surge in the load on the enterprise server. If the first target invoice data obtained in the request is all of the invoice data corresponding to the demand information, the interaction process between the enterprise servers ends. If the first target invoice data obtained in the request is only part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interaction server that has not interacted. The interaction process between the enterprise servers ends until all of the invoice data obtained in the request is all of the invoice data corresponding to the demand information. Therefore, if the total transceiver volume is greater than or equal to the preset transceiver volume threshold, the enterprise server can obtain all of the required invoice data through a number of interactions less than the number of target interaction servers, thereby reducing the load on the enterprise server without affecting the invoice data usage needs between enterprises.

[0031] It should be noted that the enterprise invoice data interaction method provided in the embodiment of the present application is generally executed by the computer device 102, and accordingly, the enterprise invoice data interaction device is generally set in the computer device 102.

[0032] The following is a detailed description of the implementation details of the technical solution of the embodiment of the present application:

[0033] Figure 2 This is a flowchart of an exemplary embodiment of the present invention showing a method for interacting with enterprise invoice data. The method for interacting with enterprise invoice data can be executed by a computing and processing device. The computing and processing device can be Figure 1 The computer device 102 shown in FIG. Figure 2 As shown, the enterprise invoice data interaction method includes at least steps S210 to S240, which are described in detail as follows:

[0034] In step S210, the current parallel sending and receiving volume of the enterprise server and multiple target interactive servers of the enterprise server are obtained.

[0035] In one embodiment of the present application, multiple target interactive servers are determined by the enterprise's demand information, the demand information includes multiple information parts, and the multiple target interactive servers correspond one-to-one to the multiple information parts. Each target interactive server generates different target invoice data based on the corresponding information part, and each target interactive server stores the target invoice data generated by other target interactive servers.

[0036] In step S220, the total sending and receiving volume of the enterprise server at the next moment is estimated based on the current parallel sending and receiving volume and the number of interaction requests to be sent.

[0037] In this embodiment, the current number of concurrent transmissions and receptions can be obtained by monitoring the interface occupancy of the enterprise server using a monitoring device, or by monitoring the number of threads being processed by the enterprise server using a monitoring device. The monitoring device can be an existing product or an application developed to monitor interface occupancy and the number of threads being processed by the enterprise server, and is not limited here. The number of pending interaction requests corresponds to the number of target interaction servers.

[0038] In step S230, if the total sending and receiving volume is greater than or equal to the preset sending and receiving volume threshold, the enterprise server sends a first target invoice data interaction request to one of the target interactive servers. If the first target invoice data obtained by the request is all the invoice data corresponding to the demand information, the interaction process between the enterprise servers ends; if the first target invoice data obtained by the request is part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interactive server that has not interacted, until all the invoice data obtained by the request is all the invoice data corresponding to the demand information, then the interaction process between the enterprise servers ends, and the first target invoice data interaction request contains the demand information.

[0039] In this embodiment, the preset sending and receiving volume threshold can be set according to demand conditions and is not limited here. The target interaction server can not only generate target invoice data based on the corresponding information part in the demand information, but also store target invoice data generated by other target interaction servers.

[0040] In this embodiment, if the total sending and receiving volume is greater than or equal to the preset sending and receiving volume threshold, the enterprise server sends a first target invoice data interaction request to one of the target interaction servers to avoid the enterprise server from interacting with multiple target interaction servers at the same time, resulting in a surge in the load on the enterprise server.

[0041] In this embodiment, after the enterprise server sends a first target invoice data interaction request to one of the target interaction servers, the target interaction server authenticates the address of the enterprise server and performs permission verification on the enterprise server. If the identity authentication and permission verification are successful, the target interaction server generates target invoice data according to the corresponding information part in the demand information, reads the external target invoice data stored in the target interaction server, and if the external target invoice data exists in the invoice data corresponding to the demand information, the target interaction server forwards the first target invoice data interaction request to the target interaction server that generates the external target invoice data, and performs a second access verification on the first target invoice data interaction request through the target interaction server that generates the external target invoice data, and if the second access verification result is successful, the invoice data and the external target invoice data are combined and used as the first The target invoice data is sent to the enterprise server. At this time, the enterprise server can obtain the target invoice data and external target invoice data from the target interactive server. If the first target invoice data requested is all the invoice data corresponding to the demand information, the interaction process between the enterprise servers ends. If the first target invoice data requested is part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interactive server that has not interacted, until all the invoice data requested is all the invoice data corresponding to the demand information, then the interaction process between the enterprise servers ends. Therefore, when the total sending and receiving volume is greater than or equal to the preset sending and receiving volume threshold, the enterprise server can obtain all the required invoice data through a number of interactions less than the number of target interactive servers, thereby reducing the load on the enterprise server without affecting the demand for invoice data use between enterprises.

[0042] In step S240, if the total sending and receiving volume is less than the preset sending and receiving volume threshold, the enterprise server sends a first target invoice data interaction request to multiple target interaction servers to obtain all invoice data corresponding to the demand information.

[0043] In this embodiment, if the total sending and receiving volume is less than the preset sending and receiving volume threshold, the enterprise server simultaneously sends the first target invoice data interaction request to multiple target interaction servers, thereby increasing the rate of obtaining all invoice data.

[0044] In one embodiment of the present application, the total amount of transactions received and sent by the enterprise server is estimated based on the current amount of parallel transactions received and sent and the amount of interaction requests to be sent.

[0045] Obtain the number of interaction requests received by the enterprise server at the next moment and the number of interaction requests to be completed by the enterprise server at the current moment.

[0046] In this embodiment, the number of pending interaction requests is determined based on the expected end time of the interaction requests. The expected end time of the interaction requests is determined based on the trigger time, the memory size occupied by the interaction requests, and the transmission rate of the interaction requests. For example, the transmission time of the interaction requests is estimated by the ratio of the memory size occupied by the interaction requests to the transmission rate of the interaction requests, and the sum of the trigger time and the transmission time is used as the expected end time. The number of pending interaction requests is the number of all interaction requests with an expected end time greater than the current time and less than the next time.

[0047] In this embodiment, for scheduled tasks, the number of received interaction requests is determined based on the scheduled start time of the interaction requests. The number of received interaction requests is defined as all interaction requests with the scheduled start time within the next time interval. For non-scheduled tasks, the number of received interaction requests can be determined based on the number of interaction requests triggered within the next time interval. The time interval between the current moment and the next moment is the current time interval, and the time interval between the next moment and the moment after the next moment is the next time interval.

[0048] The current parallel sending and receiving amount, the amount of interaction requests to be sent, and the amount of received interaction requests are added together to obtain a first sending and receiving amount.

[0049] In this embodiment, the current parallel sending and receiving amount, the amount of interaction requests to be sent, and the amount of received interaction requests are dynamically changing amounts and need to be counted at each time interval or at each moment to improve the accuracy of the first sending and receiving amount.

[0050] The difference between the first sending and receiving volume and the number of interaction requests to be ended is calculated to obtain the total sending and receiving volume.

[0051] In this embodiment, the total transceiver volume takes into account the current parallel transceiver volume, the interaction request volume to be sent, the interaction request volume received, and the interaction request volume to be terminated, thereby improving the accuracy of the estimation of the total transceiver volume.

[0052] In one embodiment of the present application, if the first target invoice data interaction request includes the address of the enterprise server, after the enterprise server sends the first target invoice data interaction request to one of the target interaction servers, the enterprise invoice data interaction method further includes:

[0053] The target interaction server authenticates the address of the enterprise server.

[0054] In this embodiment, the target interactive server can send the address of the enterprise server to a third-party authentication center, which will authenticate the address of the enterprise server and feedback the identity information and authentication results of the enterprise server to the target interactive server.

[0055] If the identity authentication is successful, the target interaction server performs permission verification on the enterprise server, and if the permission verification is successful, the successful verification is taken as the first access verification result.

[0056] In this embodiment, the target interaction server verifies the permission of the enterprise server according to the identity information of the enterprise server, and if the permission verification is successful, it indicates that the enterprise server has the permission to interact with the target interaction server for invoice data, thereby improving the security of the invoice data in the target interaction server.

[0057] If the identity authentication is not successful or the permission verification is not successful, the failed verification is taken as the first access verification result.

[0058] In this embodiment, if the identity authentication is not successful or the permission verification is not successful, it indicates that the enterprise server does not have the permission to interact with the target interaction server for invoice data, and the target interaction server does not provide the invoice data to the enterprise server.

[0059] In an embodiment of the present application, after obtaining the first access verification result, the enterprise invoice data interaction method further comprises:

[0060] If the first access verification result is successful verification, the target interaction server generates target invoice data according to the corresponding information part in the demand information, reads external target invoice data stored in the target interaction server, and the external target invoice data is generated by another target interaction server; if the demand information corresponding invoice data contains external target invoice data, the target interaction server forwards the first target invoice data interaction request to the target interaction server generating the external target invoice data, and performs second access verification on the first target invoice data interaction request through the target interaction server generating the external target invoice data, and sends the first target invoice data to the enterprise server according to the second access verification result; if there is no external target invoice data in the demand information, the target invoice data is taken as the first target invoice data.

[0061] In this embodiment, if the demand information corresponding invoice data contains external target invoice data, the target interaction server forwards the first target invoice data interaction request to the target interaction server generating the external target invoice data, and performs second access verification on the first target invoice data interaction request through the target interaction server generating the external target invoice data, and if the access verification is successful, it indicates that the enterprise server has the permission to interact with the target interaction server generating the external target invoice data for invoice data, and the external target invoice data is sent to the enterprise server by the target interaction server, which on the one hand avoids the enterprise server from sending the first target invoice data interaction request to the target interaction server generating the external target invoice data again, and on the other hand improves the security of the invoice data in the target interaction server generating the external target invoice data by performing access verification on the enterprise server.

[0062] In this embodiment, the process of the target interactive server that generates the external target invoice data performing the second access verification on the first target invoice data interaction request is the same as the process of the target interactive server performing access verification on the first target invoice data interaction request, that is, the target interactive server that generates the external target invoice data authenticates the address of the enterprise server; if the identity authentication is successful, the target interactive server that generates the external target invoice data performs permission verification on the enterprise server, and if the permission verification is successful, the successful verification is used as the second access verification result; if the identity authentication is unsuccessful or the permission verification is unsuccessful, the failed verification is used as the second access verification result.

[0063] In this embodiment, the target interaction server stores external target invoice data, indicating that the target interaction server and the target interaction server that generates the external target invoice data have mutual access rights. Therefore, the process of the target interaction server sending a first target invoice data interaction request to the target interaction service that generates the external target invoice data, and the process of the target interaction service that generates the external target invoice data sending a second access verification result to the target interaction server can ensure the security of data interaction.

[0064] If the first access verification result is verification failure, the first target invoice data interaction request is discarded.

[0065] In this embodiment, the first access verification result is verification failure, which means that the enterprise server does not have the authority to interact with the target interaction server for invoice data, and the first target invoice data interaction request is discarded.

[0066] In one embodiment of the present application, the process of sending the first target invoice data to the enterprise server according to the second access verification result includes:

[0067] If the second access verification result is successful, the target interactive server that generates the external target invoice data will send the verification success information to the target interactive server, and the target interactive server will combine the target invoice data and the external target invoice data and send it as the first target invoice data to the enterprise server.

[0068] In this embodiment, if the invoice data corresponding to the demand information is completely identical to the external target invoice data, the target invoice data and the external target invoice data are all combined and used as the first target invoice data. If the invoice data corresponding to the demand information is partially identical to the external target invoice data, the target invoice data and the external target invoice data are partially combined and used as the first target invoice data.

[0069] In this embodiment, if the second access verification result is successful verification, the target interactive server combines the target invoice data and the external target invoice data and uses them as the first target invoice data. The enterprise server can obtain the target invoice data and the external target invoice data from the target interactive server through a single interactive request. If the first target invoice data obtained in the request is all the invoice data corresponding to the demand information, the interaction process between the enterprise servers ends. If the first target invoice data obtained in the request is part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interactive server that has not interacted, until all the invoice data obtained in the request is all the invoice data corresponding to the demand information, and the interaction process between the enterprise servers ends. Therefore, when the total sending and receiving volume is greater than or equal to the preset sending and receiving volume threshold, the enterprise server can obtain all the required invoice data through a number of interactions less than the number of target interactive servers, thereby reducing the load on the enterprise server without affecting the demand for invoice data use between enterprises.

[0070] If the second access verification result is a verification failure, the target interactive server that generates the external target invoice data sends a verification failure message to the target interactive server, and the target interactive server sends the first target invoice data to the enterprise server.

[0071] In this embodiment, the second access verification result is verification failure, indicating that the enterprise server does not have the authority to interact with the target interactive server that generates the external target invoice data for invoice data. The target interactive server only sends the first target invoice data to the enterprise server.

[0072] In one embodiment of the present application, the process of the enterprise server sending a second target invoice data interaction request to the target interaction server with which the enterprise server has not interacted until all the invoice data obtained by the request are all the invoice data corresponding to the required information includes:

[0073] The demand information corresponding to the first target invoice data is deleted from the demand information to obtain updated demand information.

[0074] In this embodiment, after obtaining the first target invoice data, the demand information corresponding to the first target invoice data is deleted from the demand information, reducing the data volume of the demand information, facilitating the improvement of the processing rate of the demand information, and subsequently improving the comparison rate between the invoice data corresponding to the demand information and the external target invoice data, thereby improving the interaction rate of the invoice data.

[0075] A first target interactive server is determined according to the update requirement information, and the first target interactive server is used as a non-interactive target interactive server.

[0076] In this embodiment, the first target interactive server is determined by the update requirement information, which includes multiple information parts. Each first target interactive server generates different target invoice data according to the corresponding information part, and each first target interactive server stores the target invoice data generated by other first target interactive servers.

[0077] The enterprise server sends a second target invoice data interaction request to one of the non-interacting target interaction servers until all the second target invoice data obtained through the request are all the invoice data corresponding to the update requirement information.

[0078] In this embodiment, the second target invoice data interaction request includes update requirement information. The enterprise server sends the second target invoice data interaction request to one of the non-interacted target interaction servers. If the second target invoice data obtained in the request is all the invoice data corresponding to the update requirement information, the interaction process between the enterprise servers ends; if the second target invoice data obtained in the request is part of the invoice data corresponding to the update requirement information, the requirement information corresponding to the second target invoice data is deleted from the update requirement information to obtain the first update requirement information. According to the first update requirement information, the first target interaction server is determined, and the first target interaction server is used as the non-interacted target interaction server. The enterprise server sends the second target invoice data interaction request to one of the non-interacted target interaction servers until all the second target invoice data obtained in the request are all the invoice data corresponding to the update requirement information.

[0079] In this embodiment, the processing process after the non-interactive target interactive server receives the second target invoice data interactive request is the same as the processing process after the target interactive server receives the first target invoice data interactive request.

[0080] In one embodiment of the present application, the process of the enterprise server sending a first target invoice data interaction request to one of the target interaction servers includes:

[0081] Use the address of the enterprise server as the source address.

[0082] In this embodiment, the address of the enterprise server may be a physical address or an Internet Protocol address. Since the physical address and the Internet Protocol address are unique, the physical address and the Internet Protocol address serve as identity identifiers.

[0083] Use the target interactive server's address as the destination address.

[0084] In this embodiment, the address of the target interactive server may be a physical address or an Internet Protocol address.

[0085] The required information is used as the request content.

[0086] In this embodiment, the demand information may be recorded and stored in the form of files or the like.

[0087] The source address, destination address and request content are encapsulated according to a predetermined message format to obtain a first target invoice data interaction request.

[0088] In this embodiment, the predetermined message format may be a TCP (Transmission Control Protocol) message format or the like.

[0089] The enterprise server sends the first target invoice data interaction request to the target interaction server.

[0090] In this embodiment, the enterprise server sends the first target invoice data interaction request to the target interaction server through the TCP protocol or the like.

[0091] In this embodiment, the process of the enterprise server sending the second target invoice data interaction request to the non-interactive target interaction server includes: (1) using the address of the enterprise server as the source address; using the address of the non-interactive target interaction server as the destination address; using the update requirement information as the request content; encapsulating the source address, the destination address and the request content according to a predetermined message format to obtain the second target invoice data interaction request; the enterprise server sends the second target invoice data interaction request to the non-interactive target interaction server.

[0092] The following describes an embodiment of the device of the present application, which can be used to execute the enterprise invoice data interaction method in the above embodiment of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the enterprise invoice data interaction method in the above embodiment of the present application.

[0093] Figure 3 This is a block diagram of an enterprise invoice data interaction device shown in an exemplary embodiment of the present application. The device can be applied to Figure 1 The implementation environment shown is specifically configured in the computer device 102. The apparatus may also be applicable to other exemplary implementation environments and specifically configured in other devices. This embodiment does not limit the implementation environment to which the apparatus is applicable.

[0094] like Figure 3 As shown, the exemplary enterprise invoice data interaction device includes:

[0095] The transceiver volume acquisition module 301 is used to acquire the current parallel transceiver volume of the enterprise server and multiple target interactive servers of the enterprise server.

[0096] The transceiver volume estimation module 302 is used to estimate the total transceiver volume of the enterprise server at the next moment based on the current parallel transceiver volume and the amount of interaction requests to be sent.

[0097] The invoice data interaction module 303 is used to send a first target invoice data interaction request to one of the target interaction servers if the total sending and receiving volume is greater than or equal to the preset sending and receiving volume threshold. If the first target invoice data obtained in the request is all the invoice data corresponding to the demand information, the interaction process between the enterprise servers ends; if the first target invoice data obtained in the request is part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interaction server that has not interacted, until all the invoice data obtained in the request is all the invoice data corresponding to the demand information, then the interaction process between the enterprise servers ends, and the first target invoice data interaction request contains the demand information.

[0098] The transceiver volume comparison module 304 is used to, if the total transceiver volume is less than a preset transceiver volume threshold, cause the enterprise server to send a first target invoice data interaction request to multiple target interaction servers to obtain all invoice data corresponding to the demand information.

[0099] In one embodiment of the present application, multiple target interactive servers are determined by the enterprise's demand information, the demand information includes multiple information parts, and the multiple target interactive servers correspond one-to-one to the multiple information parts. Each target interactive server generates different target invoice data according to the corresponding information part, and each target interactive server stores the target invoice data generated by other target interactive servers.

[0100] In this embodiment, the current number of concurrent transmissions and receptions can be obtained by monitoring the interface occupancy of the enterprise server using a monitoring device, or by monitoring the number of threads being processed by the enterprise server using a monitoring device. The monitoring device can be an existing product or an application developed to monitor interface occupancy and the number of threads being processed by the enterprise server, and is not limited here. The number of pending interaction requests corresponds to the number of target interaction servers.

[0101] In this embodiment, the preset sending and receiving volume threshold can be set according to demand conditions and is not limited here. The target interaction server can not only generate target invoice data based on the corresponding information part in the demand information, but also store target invoice data generated by other target interaction servers.

[0102] In this embodiment, if the total sending and receiving volume is greater than or equal to the preset sending and receiving volume threshold, the enterprise server sends a first target invoice data interaction request to one of the target interaction servers to avoid the enterprise server from interacting with multiple target interaction servers at the same time, resulting in a surge in the load on the enterprise server.

[0103] In this embodiment, after the enterprise server sends a first target invoice data interaction request to one of the target interaction servers, the target interaction server authenticates the address of the enterprise server and performs permission verification on the enterprise server. If the identity authentication and permission verification are successful, the target interaction server generates target invoice data according to the corresponding information part in the demand information, reads the external target invoice data stored in the target interaction server, and if the external target invoice data exists in the invoice data corresponding to the demand information, the target interaction server forwards the first target invoice data interaction request to the target interaction server that generates the external target invoice data, and performs a second access verification on the first target invoice data interaction request through the target interaction server that generates the external target invoice data, and if the second access verification result is successful, the invoice data and the external target invoice data are combined and used as the first The target invoice data is sent to the enterprise server. At this time, the enterprise server can obtain the target invoice data and external target invoice data from the target interactive server. If the first target invoice data requested is all the invoice data corresponding to the demand information, the interaction process between the enterprise servers ends. If the first target invoice data requested is part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interactive server that has not interacted, until all the invoice data requested is all the invoice data corresponding to the demand information, then the interaction process between the enterprise servers ends. Therefore, when the total sending and receiving volume is greater than or equal to the preset sending and receiving volume threshold, the enterprise server can obtain all the required invoice data through a number of interactions less than the number of target interactive servers, thereby reducing the load on the enterprise server without affecting the demand for invoice data use between enterprises.

[0104] In this embodiment, if the total sending and receiving volume is less than the preset sending and receiving volume threshold, the enterprise server simultaneously sends the first target invoice data interaction request to multiple target interaction servers, thereby increasing the rate of obtaining all invoice data.

[0105] It should be noted that the enterprise invoice data interaction device provided in the above-mentioned embodiment and the enterprise invoice data interaction method provided in the above-mentioned embodiment are based on the same concept. The specific manner in which each module and unit performs operations has been described in detail in the method embodiment and will not be repeated here. In actual applications, the enterprise invoice data interaction device provided in the above-mentioned embodiment can, as needed, allocate the above-mentioned functions to different functional modules, i.e., divide the internal structure of the device into different functional modules to complete all or part of the functions described above, and this is not limited here.

[0106] An embodiment of the present application also provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by one or more processors, the electronic device implements the enterprise invoice data interaction method provided in the above-mentioned embodiments.

[0107] Figure 4 The following is a schematic diagram showing the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application. Figure 4 The computer system 400 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0108] like Figure 4 As shown, computer system 400 includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes according to programs stored in read-only memory (ROM) 402 or programs loaded from storage unit 408 into random access memory (RAM) 403, such as executing the methods in the above embodiments. Various programs and data required for system operation are also stored in RAM 403. CPU 401, ROM 402, and RAM 403 are connected to each other via bus 404. Input / output (I / O) interface 405 is also connected to bus 404.

[0109] The following components are connected to the I / O interface 405: an input section 406 including a keyboard, a mouse, and the like; an output section 407 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 408 including a hard disk and the like; and a communication section 409 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 405 as needed. Removable media 411, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 410 as needed, so that computer programs read therefrom can be installed into the storage section 408 as needed.

[0110] In particular, the processes described above with reference to the flow charts can be implemented as computer software programs in accordance with embodiments of the present application. For example, embodiments of the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program comprising computer programs for performing the methods illustrated by the flow charts. In such embodiments, the computer program can be downloaded and installed from a network via the communication section 409 and / or installed from the removable media 411. When the computer program is executed by the central processing unit (CPU) 401, various functions defined in the system of the present application are performed.

[0111] It should be noted that the computer readable medium shown in the embodiments of the present application can be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium may, for example, be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination of the above. More specific examples of the computer readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer readable signal medium can include a data signal propagated in a baseband or propagated as a carrier wave in a propagated data signal, in which the computer readable computer program is carried. Such a propagated data signal can take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium can also be any computer readable medium other than the computer readable storage medium that can send, propagate or transfer the program for use by or in connection with the instruction execution system, apparatus or device. The computer program contained in the computer readable medium can be transmitted by any suitable medium, including but not limited to wireless, wired, or the like, or any suitable combination of the above.

[0112] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0113] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. In some cases, the names of these units do not constitute limitations on the units themselves.

[0114] Another aspect of the present application provides a computer-readable storage medium storing a computer program. When executed by a computer processor, the computer program causes the computer to perform the aforementioned method for interacting with corporate invoice data. The computer-readable storage medium may be included in the electronic device described in the above embodiments, or may exist independently and not be incorporated into the electronic device.

[0115] Another aspect of the present application provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the enterprise invoice data interaction method provided in each of the above embodiments.

[0116] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the present invention. Anyone skilled in the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, any equivalent modifications or alterations made by one of ordinary skill in the art without departing from the spirit and technical principles disclosed herein are intended to be covered by the claims of the present invention.

Claims

1. A method for interacting with enterprise invoice data, characterized in that: include: Obtaining a current parallel transceiver volume of the enterprise server and multiple target interactive servers of the enterprise server, wherein the multiple target interactive servers are determined by the enterprise's demand information, the demand information comprising multiple information parts, the multiple target interactive servers corresponding one-to-one to the multiple information parts, each of the target interactive servers generating different target invoice data according to the corresponding information part, and each of the target interactive servers storing the target invoice data generated by other target interactive servers; estimating the total receiving and sending volume of the enterprise server at a next moment based on the current parallel receiving and sending volume and the number of interaction requests to be sent, where the number of interaction requests to be sent corresponds to the number of the multiple target interaction servers; If the total sending and receiving volume is greater than or equal to the preset sending and receiving volume threshold, the enterprise server sends a first target invoice data interaction request to one of the target interaction servers. If the first target invoice data obtained by the request is all the invoice data corresponding to the demand information, the interaction process between the enterprise servers ends; If the first target invoice data obtained by the request is part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interaction server with which the interaction has not occurred. This process ends until all the invoice data obtained by the request is all the invoice data corresponding to the demand information. The first target invoice data interaction request includes the demand information. If the total sending and receiving volume is less than the preset sending and receiving volume threshold, the enterprise server sends a first target invoice data interaction request to the multiple target interaction servers to obtain all invoice data corresponding to the demand information.

2. The enterprise invoice data interaction method according to claim 1, characterized in that: The total amount of transmission and reception of the enterprise server is estimated based on the current parallel transmission and reception amount and the amount of interaction requests to be sent: Obtaining the number of interaction requests received by the enterprise server at the next moment and the number of interaction requests to be terminated by the enterprise server at the current moment, wherein the number of interaction requests to be terminated is determined based on the expected end time of the interaction requests, and the number of interaction requests received is determined based on the agreed start time of the interaction requests; Adding the current parallel transceiver volume, the to-be-sent interactive request volume, and the received interactive request volume to obtain a first transceiver volume; The difference between the first sending and receiving volume and the to-be-ended interaction request volume is calculated to obtain the total sending and receiving volume.

3. The enterprise invoice data interaction method according to claim 1, characterized in that: If the first target invoice data interaction request includes the address of the enterprise server, after the enterprise server sends the first target invoice data interaction request to one of the target interaction servers, the method further includes: The target interactive server authenticates the address of the enterprise server; If the identity authentication is successful, the target interactive server performs authority verification on the enterprise server, and if the authority verification is successful, the successful verification is used as the first access verification result; If the identity verification fails or the permission verification fails, the verification failure is taken as the first access verification result.

4. The enterprise invoice data interaction method according to claim 3, characterized in that: After obtaining the first access verification result, the method further includes: If the first access verification result is successful, the target interactive server generates target invoice data according to the corresponding information in the demand information, and reads the external target invoice data stored in the target interactive server, where the external target invoice data is generated by other target interactive servers; if the external target invoice data exists in the invoice data corresponding to the demand information, the target interactive server forwards the first target invoice data interaction request to the target interactive server that generated the external target invoice data, and performs a second access verification on the first target invoice data interaction request through the target interactive server that generated the external target invoice data, and sends the first target invoice data to the enterprise server according to the second access verification result; if the external target invoice data does not exist in the demand information, the target invoice data is used as the first target invoice data; If the first access verification result is verification failure, the first target invoice data interaction request is discarded.

5. The enterprise invoice data interaction method according to claim 4 is characterized in that: The process of sending the first target invoice data to the enterprise server according to the second access verification result includes: If the second access verification result is successful, the target interactive server that generates the external target invoice data sends the verification success information to the target interactive server, and the target interactive server combines the target invoice data and the external target invoice data as the first target invoice data and sends it to the enterprise server; If the second access verification result is a verification failure, the target interactive server that generates the external target invoice data sends the verification failure information to the target interactive server, and the target interactive server sends the first target invoice data to the enterprise server.

6. The enterprise invoice data interaction method according to any one of claims 1 to 5, characterized in that: The process of the enterprise server sending a second target invoice data interaction request to the target interaction server with which the enterprise server has not interacted until all the invoice data obtained by the request are all the invoice data corresponding to the demand information includes: Deleting the demand information corresponding to the first target invoice data from the demand information to obtain updated demand information; determining a first target interactive server according to the update requirement information, and using the first target interactive server as a non-interactive target interactive server; The enterprise server sends a second target invoice data interaction request to one of the non-interacted target interaction servers until all the second target invoice data obtained in the request are all the invoice data corresponding to the update requirement information, and the second target invoice data interaction request includes the update requirement information.

7. The enterprise invoice data interaction method according to any one of claims 1 to 5, characterized in that: The process of the enterprise server sending a first target invoice data interaction request to one of the target interaction servers includes: Using the address of the enterprise server as the source address; Using the address of the target interactive server as the destination address; Using the demand information as request content; Encapsulating the source address, destination address, and request content according to a predetermined message format to obtain the first target invoice data interaction request; The enterprise server sends the first target invoice data interaction request to the target interaction server.

8. An enterprise invoice data interaction device, characterized in that: include: a transceiver volume acquisition module, configured to acquire the current parallel transceiver volume of the enterprise server and multiple target interactive servers of the enterprise server, wherein the multiple target interactive servers are determined by the enterprise's demand information, the demand information comprising multiple information parts, the multiple target interactive servers corresponding one-to-one to the multiple information parts, each of the target interactive servers generating different target invoice data based on the corresponding information part, and each of the target interactive servers storing the target invoice data generated by other target interactive servers; a transceiver volume estimation module, configured to estimate a total transceiver volume of the enterprise server at a next moment based on the current parallel transceiver volume and the number of pending interactive requests, wherein the number of pending interactive requests corresponds to the number of the plurality of target interactive servers; an invoice data interaction module, configured to cause the enterprise server to send a first target invoice data interaction request to one of the target interaction servers if the total sending and receiving volume is greater than or equal to a preset sending and receiving volume threshold, and terminate the interaction process between the enterprise servers if the first target invoice data obtained in the request is all the invoice data corresponding to the demand information; If the first target invoice data obtained by the request is part of the invoice data corresponding to the demand information, the enterprise server sends a second target invoice data interaction request to the target interaction server with which the interaction has not occurred. This process ends until all the invoice data obtained by the request is all the invoice data corresponding to the demand information. The first target invoice data interaction request includes the demand information. The transceiver volume comparison module is used to, if the total transceiver volume is less than the preset transceiver volume threshold, cause the enterprise server to send a first target invoice data interaction request to the multiple target interaction servers to obtain all invoice data corresponding to the demand information.

9. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the enterprise invoice data interaction method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the enterprise invoice data interaction method according to any one of claims 1 to 7.

Images