CN115086429B - Request integration system and request integration method - Google Patents

Abstract

The invention provides a request integration system and a request integration method. The request integration system includes a storage device and a processor. The storage device stores an inlet module, a throttling allocation module and a service distribution module. The processor is used for executing the entry module, the throttling allocation module and the service distribution module and receiving the request data. The entry module analyzes the message type of the request data to obtain a header and a message of the request data. The throttle allocation module establishes a plurality of channels corresponding to the maximum allowable value according to the maximum allowable value of the channel number, and carries out channel management processing according to the importance level and the receiving sequence of the request data. The service distribution module performs data processing on the request data according to the header and the message of the request data to generate a plurality of data objects. The service distribution module outputs the data object.

Description

Request integration system and request integration method

Technical field

The present invention relates to an integration system and a method thereof, and in particular to a request integration system and a method thereof.

Background technique

Enterprises today need to store and simultaneously transmit more and more requested data. At the same time, as more and more systems issue requests, the demand for concurrency in request data calls also increases, resulting in occupying the resources of the service execution system for request integration processing. As a result, the service execution system cannot respond to requests in real time, and client operations are delayed. If the integration server and application server are deployed separately, the load pressure will be transferred to the database server, so there is still a problem that the requested data cannot be effectively integrated and dispatched. In view of this, several embodiment solutions will be proposed below.

Contents of the invention

The invention is directed to a request integration system and a data integration method, which can provide high-efficiency and high-stability request integration and dispatch effects.

According to an embodiment of the present invention, the request of the present invention integrates a system storage device and a processor. The storage device stores the entry module, the throttling deployment module and the service distribution module executed by the processor. The entry module performs parsing and processing according to the message type of the request data to obtain the header and message of the request data. The throttling deployment module establishes multiple channels corresponding to the maximum allowed value of the number of channels, and performs channel management processing according to the importance level and reception order of the requested data. The business distribution module performs data processing on the request data according to the header and message of the request data to generate multiple data objects. The business distribution module outputs data objects.

According to the embodiment of the present invention, the request integration method of the present invention includes: performing parsing processing according to the message type of the request data to obtain the header and the message; establishing corresponding multiple channels according to the maximum allowable value of the number of channels; and according to the request data Perform channel management processing according to the importance level and reception order; perform data processing on the request data according to the header and message of the request data to generate multiple data objects; and output the data objects to the service processing system.

Based on the above, the request integration system and request integration method of the present invention can limit and queue requests through the throttle mechanism, so as to achieve a more timely response to service requests and a more stable service processing system.

In order to make the above-mentioned features and advantages of the present invention more obvious and easy to understand, embodiments are given below and described in detail with reference to the accompanying drawings.

Description of the drawings

Figure 1 is a schematic diagram of a request integration system according to an embodiment of the present invention;

Figure 2 is a flow chart of a request integration method according to an embodiment of the present invention;

Figure 3 is a schematic diagram of a request integration system and pending requests according to an embodiment of the present invention;

Figure 4 is a schematic diagram of the request integration system, third-party system, authorization center and application server according to an embodiment of the present invention.

Explanation of reference signs

100: Request integrated system;

110: Processor;

120: storage device;

121: Entry module;

122: Throttle deployment module;

123: Business distribution module;

300_R: Pending request;

300: Request integration system;

310: Entry module;

320: Throttle deployment module;

321: Queue management service module;

322: Channel group;

330: Business distribution module;

331: Service distributor;

332: Data serialization service;

333: Service content;

410: Request integration system;

411: Entry module;

412: Internal restful entrance service;

413: Request queue management unit;

414: Channel distribution unit;

4141: Channel counter;

415: terminal distribution unit;

4151: Business distribution unit;

416: Data processing unit;

417: Business service distribution unit;

418: Connect distributor;

419:Remote connector;

420: Third-party system;

430: Authorization center;

431:Controller

440: Application server;

441:Remote connector;

442: Connect distributor;

443: Service distributor;

444: Create/read/update/delete/query services;

445: Verification service;

446:Workflow service;

447:Reporting service;

448: Batch service;

S210～S250: steps.

Detailed ways

Reference will now be made in detail to the exemplary embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Whenever possible, the same component symbols are used in the drawings and descriptions to represent the same or similar parts.

Figure 1 is a schematic diagram of a request integration system according to an embodiment of the present invention. Referring to FIG. 1 , the request integration system 100 includes a processor 110 and a storage device 120 . The processor 110 is coupled to the storage device 120 . The storage device 120 stores an entry module 121, a throttling deployment module 122, and a service distribution module 123. In this embodiment, the request integration system 100 may be, for example, set up in a local system of an enterprise or a user, so that the user can send requests from a third-party system to the request integration system. Through the architecture and technology of the request integration system, requests are limited and queued, and then the requests are allocated to various Enterprise Resource Planning (ERP) systems to sort the requests according to their importance and order. Provide related business service functions in sequence (such as generating purchase orders, requisitions, quotations, and other such business services). The ERP system may be, for example, an application service system provided in an application server (AP server). Alternatively, in one embodiment, the request integration system 100 can be set up on a cloud server for users to connect and transmit request data and perform related business service functions. In another embodiment, the request integration system 100 can be applied to application scenarios of service grading. For example, the request integration system 100 can be applied to scenarios such as recording orders, printing reports, and exporting data in the ERP system to enable request integration through The system sorts according to the importance level of functions or business items (such as order recording > report printing > export data), and then allocates different numbers of channels.

In this embodiment, the processor 110 may include, for example, a central processing unit (CPU), or other programmable general-purpose or special-purpose microprocessor (Microprocessor) or digital signal processor (Digital Signal Processor). , DSP), Application Specific Integrated Circuits (ASIC), Programmable Logic Device (PLD), other similar processing circuits or a combination of these devices. The storage device 120 may include a memory (Memory) and/or a database (database), where the memory may be, for example, a non-volatile memory (Non-Volatile Memory, NVM). The storage device 120 may store relevant programs, modules, systems or algorithms for implementing various embodiments of the present invention, so that the processor 110 can access and execute them to realize the related functions and operations described in various embodiments of the present invention. In this embodiment, the entry module 121, the throttling deployment module 122 and the service distribution module 123 may be, for example, JSON (JavaScript Object Notation), Extensible Markup Language (Extensible Markup Language, XML) or YAML or the like. to achieve this, but the present invention is not limited to this.

In this embodiment, the user can execute the request integration system 100 through a personal computer device, for example, and input request data into the request integration system 100 to request execution of the corresponding business service function. The request integration system 100 can execute the entry module 121, the throttling deployment module 122 and the business distribution module 123 according to the request data to convert the request data into a data object that can be read/recognized by the ERP system or AP server, and according to the request importance level And sequentially transmitted to the ERP system or AP server through the channel to perform the corresponding business service functions, making the service response of the ERP system more real-time and the system more stable. In this embodiment, the user can input one or more requests into the request integration system 100 through a (specific) third-party system. The request is request data, and the request data is, for example, an enterprise work order or a service request. The request (request data) can be a request issued by a different third-party system or a request issued by the same system. The request integration system 100 performs request dispatch processing and channel management according to the priority and reception order of multiple requests, as well as the number of channels authorized by the user, so as to achieve rigid resource priority and leave it to the business processing of the EPR system, so that business services can be performed. The ERP system responds to services in a more timely manner, and reserves processing channels corresponding to requests based on the number of channels authorized by users or enterprises to ensure that no requests are missed.

Figure 2 is a flow chart of a request integration method according to an embodiment of the present invention. Figure 3 is a schematic diagram of a request integration system and pending requests according to an embodiment of the present invention. Referring to FIG. 2 and FIG. 3 , the request integration system 300 can perform the following steps S210 to S250 to sequentially distribute the request data to the corresponding application services in priority and order. As shown in Figure 3, the entry module 310 receives multiple pending requests 300_R. The pending requests 300_R are, for example, querying supplier information, creating supplier information, creating work orders, and reviewing sales orders.

In step S210, the processor performs parsing processing according to the message type of the request data through the entry module 310 to obtain the header and the message. In this embodiment, the entry module 310 can support multiple protocols, such as Web service (Webservice) protocol and representational state transfer (Representational State Transfer, restful) protocol, but the invention is not limited thereto. The entry module 310 uses a corresponding data processor to parse and read data according to the protocol type of the request data (request to be processed) to obtain the header and message of each request data, and then obtain (know) the header and message of each request data. Service content and importance level. In one embodiment, the entry module 310 reads the request data through a corresponding serializer according to the message type of the request data.

In step S220, the processor may establish multiple channels corresponding to the maximum allowed value according to the maximum allowed value of the number of channels through the throttling allocation module 320. In this embodiment, the throttling deployment module 320 establishes a channel group 322 with a corresponding number of channels according to the received or built-in maximum allowed value (number) of the number of channels. The number of channels is the number of concurrent connections (number of concurrencies) authorized by the enterprise or user. In one embodiment, the user can increase the number of authorized concurrencies through purchase according to the needs, so as to improve the user's planning flexibility for requesting data execution efficiency and economy.

In step S230, the processor may perform channel management processing according to the importance level of the request data and the reception order of the request data through the throttling allocation module 320. In this embodiment, the queue management service module 321 of the throttling deployment module 320 sorts the request data according to the importance level and acquisition (transmission) order of each request data, and the throttling deployment module 320 sorts the request data according to the order of importance in the channel group 322. The current idle channel passes the sorted request data through the current idle channel in order to complete the management of the channel and the request data. In this embodiment, each channel sends a request data (request service) at the same time, and whether the channel is in an idle state depends on whether the service sent by the channel has been completed. That is to say, after the request data is transmitted to the request integration system 300, through the assignment and sequence processing of the queue management service module 321, the currently idle channel in the channel group 322 receives the request data. Then, it is dispatched to the corresponding service processing system, such as ERP system. When the service requesting data is completed, the channel returns to the idle state and waits for the transmission of subsequent request data.

In step S240, the processor may perform data processing (data conversion processing) on the request data according to the header and message of the request data through the service distribution module 330 to generate a data object. In this embodiment, the service distribution module 330 obtains the protocol type and service content of the request data according to the header and message of the request data through the service distributor 331. Furthermore, the service distribution module 330 performs corresponding data conversion processing on the request data according to the service content 333 of the request data to generate a data object. Data conversion processing includes performing at least one of formula operations, band values, data verification, data conversion, creation, reading, updating and deletion (CRUD) operations. In this embodiment, the service distribution module 330 includes a data processing unit to perform data conversion processing. In one embodiment, the data processing unit may include a serializer to provide a data serialization service 322. The data serialization service is to serialize a message requesting data to generate a data object.

In this way, the serialized request data is a data object that can be recognized by the request integration system and/or the ERP system. The data object is the request data processed by data conversion. In this way, the request data that has been processed by data conversion is organized into more complete and effective data, and the converted request data is recognized and readable by the ERP system to improve the efficiency and efficiency of request data distribution and subsequent execution of business services. stability. In step S250, the processor may output the data object through the service distribution module 330. In this embodiment, the service distribution module 330 outputs the data object to the AP server or ERP system according to the service content 333 of the requested data.

In this way, the request integration system 300 and its method of the present invention can be sorted according to the priority and transmission order of the request data, and can establish the number of channels according to the number of concurrency purchased by the user, so as to make the distribution and management of the request data more stable. level is more efficient. At the same time, the ERP system service response is improved to be more timely.

Figure 4 is a schematic diagram of the request integration system, third-party system, authorization center and application server according to an embodiment of the present invention. Referring to FIG. 1 and FIG. 4 , the throttling deployment module 122 includes a request queue management unit 413 , a channel distribution unit 414 and a terminal distribution unit 415 . The service distribution module 123 includes a service distribution unit 4151, a business service distribution unit 417 and a data processing unit 416. The enterprise or user sends one or more request data to the entry module 411 of the request integration system 410 through the third-party system 420 . The third-party system 420 is, for example, an e-commerce system, a human resource management system, and a manufacturing execution system. The format of the requested data is, for example, JSON or XML format, and the protocol used for requesting the data is, for example, Restful or SOAP protocol. In this embodiment, the internal Restful portal service 412 receives the request data and transmits it to the request queue management unit 413 . The request list management unit 413 sorts multiple requests according to the importance level and sequence of the request data.

In this embodiment, the channel distribution unit 414 enables the same number of channels according to the maximum allowed value of the number of channels. In one embodiment, the terminal distribution unit 415 communicates with the controller 431 of the authorization center 430 to obtain the number of authorized channels for the user. The number of authorized channels is, for example, the number of channels purchased by the user. The terminal distribution unit transmits the authorized channel number to the channel distribution unit 414. The channel counter 4141 of the channel distribution unit 414 takes the number of authorized channels as the maximum allowed value of the number of channels. That is to say, when the authorized number of integrated concurrencies for this user is N, the channel distribution unit 414 establishes/activates N channels, where N is a positive integer. The request queue management unit 413 queues the request data according to the priority/ordering of the request data, and sequentially enters the currently idle channel in the channel group for processing, thereby achieving the effect of current limiting and queuing of the request data.

In this embodiment, the end point distribution unit 415 receives the request data through the channel distribution unit 414, and the end point distribution unit 415 establishes communication between each channel and the service distribution unit 4151 of the service distribution module 123, thereby establishing one-to-one communication. . The service distribution unit 4151 converts the request data and its messages into data objects through the serialization service. In this embodiment, the business service distribution unit 417 analyzes the header and message of the request data to generate the service name identifier and data identifier of the request data. In this way, the business service distribution unit 417 distributes the data-converted request data to the corresponding service process (ERP process) in the application server 440 according to the service name identifier and the data identifier.

In this embodiment, after the service distribution unit 4151 converts the request data into a data object through serialization processing, and before the service distribution unit 4151 distributes the request data to the application server 440, the business service distribution unit 417 may input the request data. to data processing unit 416. In this way, the data processing unit 416 performs data conversion processing on the request data or data objects to generate multiple data objects. In this way, through serialization processing, the request data is converted into system-recognized and readable data objects to increase data recognition and improve distribution efficiency. In one embodiment, the business service distribution unit 417 inputs the request data to the corresponding processing unit in the data processing unit 416 according to the header information of the request data to generate multiple data objects. The processing unit is, for example, a data conversion/exchange unit, a serializer, a data verification unit, a data band value unit and an arithmetic unit. Moreover, data conversion processing includes performing formula, band value, data verification, data conversion, creation, reading, updating and deleting (CRUD) operations on data.

In this embodiment, the data processing unit 416 outputs the processed data objects to the business service distribution unit 417. The business service distribution unit 417 distributes the data object to the processing system corresponding to the request data message. In this embodiment, the business service distribution unit 417 performs service distribution according to the protocol type of the requested data and the business service content. The business distribution includes the business service distribution unit 417 outputting data objects to the application server 440 to execute services corresponding to the business service content. The processing system is, for example, an ERP system. In one embodiment, the business service distribution unit 417 transmits the data objects to the connection distributor 418, and the connection distributor 418 then transmits the data objects to the remote connector 419. In this way, the service distributor 443 of the application server 440 receives the request data through the remote connector 419 and inputs the data object to the corresponding service module. The service module may be various services in the ERP system. In another embodiment, the business service distribution unit 417 can also transmit the data object to the remote connector 441 of the application server 440, so that the connection distributor 442 receives the data object through the remote connector 441 and outputs it to the application server 440. Service Distributor 443.

After the ERP system receives the request data (data object) that has been processed by data conversion and/or serialization, it performs service processing through multiple service modules. The service modules are, for example, create/read/update/delete/query service 444, verification service 445, workflow service 446, report service 447 and batch service 448. Service processing includes querying suppliers, adding/deleting work order data, confirming sales orders, querying/retrieving supplier data, etc. For example, the business service distribution unit 417 and the ERP system can learn that the requested service is a query provider based on the header of the request data, and learn the query conditions based on the message of the request data.

To sum up, the request integration system and request integration method of the present invention can realize current limiting and queuing of third-party integration requests to ensure that hardware resources are prioritized for business processing of the ERP product itself, making the service response of the ERP system more efficient. In a timely manner, the system will run more stably; in addition, corresponding processing channels can be reserved based on the concurrent number of third-party integrations evaluated before the system goes online to ensure timely response of third-party integration services. For parts beyond the evaluation, a queuing method will be used to ensure that requests The processing is not missed.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention, but not to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions described in the foregoing embodiments can still be modified, or some or all of the technical features can be equivalently replaced; and these modifications or substitutions do not deviate from the essence of the corresponding technical solutions from the technical solutions of the embodiments of the present invention. scope.

Claims (16)

1. A request integration system, comprising:

a storage device that stores a plurality of modules; and

a processor coupled to the storage device, executing the plurality of modules and receiving a plurality of request data, wherein the plurality of modules includes an entry module, a throttling deployment module, and a traffic distribution module,

wherein the entry module performs parsing processing according to the message types of the plurality of request data to obtain a header and a message of each request data,

wherein the throttle allocation module establishes a plurality of channels corresponding to the maximum allowable value according to the maximum allowable value of the channel number, and the throttle allocation module performs channel management processing according to the importance level of the plurality of request data and the receiving sequence of the plurality of request data,

and the service distribution module performs data processing on the plurality of request data according to the headers and the messages of the plurality of request data to generate a plurality of data objects, wherein the service distribution module outputs the plurality of data objects.

2. The request integration system of claim 1, wherein the service distribution module comprises:

a business service distribution unit for generating a plurality of service name identifications and a plurality of data identifications by analyzing the headers of the plurality of requests and the messages of the plurality of request data; and

and the data processing unit is used for carrying out data conversion processing on the plurality of request data so as to generate a plurality of object data.

3. The request integration system of claim 2, wherein the data processing unit includes a serializer that serializes the message of the request data to produce the data object.

4. The request integration system according to claim 2, wherein the business service distribution unit performs business distribution of the corresponding plurality of data objects according to the protocol type of the plurality of request data and business service content.

5. The request integration system of claim 4, wherein the business distribution includes the business service distribution unit outputting the plurality of data objects to an application server to perform a service corresponding to the business service content.

6. The request integration system of claim 1, wherein the throttling adaptation module comprises:

a request queue management unit for ordering the plurality of request data according to the importance levels and the sequence of the plurality of request data;

a channel distribution unit for enabling a corresponding number of the channels according to a maximum allowable value of the number of channels; and

an end point distribution unit that receives the plurality of request data through a channel distribution unit and establishes communication between each of the channels and a service distribution unit of the service distribution module,

and the channel distribution unit sequentially transmits the plurality of request data to the current idle channel in the channels according to the ordering of the plurality of request data.

7. The request integration system of claim 6, wherein the endpoint distribution unit communicates with an authorization center to obtain the number of channels authorized by the user,

wherein the channel distribution unit comprises a channel counter having the number of authorized channels as a maximum allowed value of the number of channels.

8. The request integration system of claim 1, wherein the entry module reads the plurality of request data via a corresponding serializer according to a message type of the plurality of request data.

9. A method of request integration, comprising:

receiving a plurality of request data, and analyzing according to message types of the plurality of request data to obtain a header and a message of each request data;

establishing a plurality of channels corresponding to the maximum allowable value according to the maximum allowable value of the channel number, and performing channel management processing according to the importance level of the plurality of request data and the receiving sequence of the plurality of request data;

according to the header and the message of the plurality of request data, carrying out data processing on the plurality of request data; and

a plurality of data objects is output.

10. The request integration method according to claim 9, wherein the step of performing data processing on the plurality of request data based on the header and the message of the plurality of request data includes:

generating a plurality of service name identifications and a plurality of data identifications by analyzing headers of the plurality of requests and messages of the plurality of request data; and

and performing data conversion processing on the plurality of request data to generate a plurality of object data.

11. The request integration method of claim 10, wherein the data transformation process includes serializing the message of the request data to generate the data object.

12. The request integration method of claim 10, wherein the outputting the plurality of data objects comprises: and distributing the corresponding data objects according to the protocol types of the request data and the business service content.

13. The request integration method of claim 12, wherein the service distribution includes outputting the plurality of data objects to an application server (AP server) to perform a service corresponding to the service content.

14. The request integration method according to claim 9, wherein the plurality of channels corresponding to the maximum allowable value are established according to the maximum allowable value of the channel number, and the step of performing channel management processing according to the importance level of the plurality of request data and the reception order of the plurality of request data includes:

sequencing the plurality of request data according to the importance levels and the sequence of the plurality of request data;

enabling a corresponding number of the channels according to a maximum allowable value of the number of the channels;

receiving the plurality of request data and establishing communication between each of the channels and a service distribution unit; and

and sequentially transmitting the plurality of request data to a current idle channel in the channels according to the ordering of the plurality of request data.

15. The request integration method of claim 14, wherein enabling a corresponding number of the channels according to a maximum allowable value of the number of channels comprises:

communicates with the authorization center to obtain the number of channels authorized by the user,

wherein the number of authorized channels is taken as the maximum allowed value of the number of channels.

16. The request integration method according to claim 9, wherein the step of parsing according to the message types of the plurality of request data includes:

and reading the plurality of request data through the corresponding serializer according to the message types of the plurality of request data.