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

Abstract

The present disclosure 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 entry module, a throttling adjustment module, a business service dispatching module. The processor is configured to execute the entry module, the throttling adjustment module, and the business service dispatching module, and receive request data. The entry module performs an analytical processing according to a message type of the request data to require a message and a header of the request data. The throttling adjustment module establishes multiple channels according to the maximum allowable number of channels, and executes a channel management processing according to an importance level and a receive sequence. The business service dispatching module processes the request data according to the header and the message of the request data, and generates a plurality of data object. The business service dispatching module outputs the data object.

Description

Request integration system and request integration method

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

In smart warehouses, enterprises currently need to store and transmit more and more requested data at the same time. 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 immediately, and user-side operations are delayed. If the integration server and the 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 distributed. In view of this, several embodiment solutions will be proposed below.

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 present invention requests an integrated 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 processing according to the message type of the requested data to obtain the header (for example, title) and the message (for example, message, packet) of the requested data. The throttling deployment module establishes multiple channels corresponding to the maximum allowable 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.

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

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 entrance 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 the 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 priority. 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 installed in an application server (AP server). 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 may be applied in a service hierarchical application scenario. For example, the request integration system 100 can be applied to scenarios such as order recording, report printing, and data export in the ERP system, so that the request integration system can be used to sort according to the importance level of functions or business projects (such as order recording > report printing). >Export data), and then allocate 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). 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 and/or a database, where the memory may be, for example, a non-volatile memory (NVM). The storage device 120 may store related programs, modules, systems or algorithms for implementing various embodiments of the present invention, for the processor 110 to access and execute to implement related functions and operations described in various embodiments of the present invention. In this embodiment, the entrance module 121, the throttling deployment module 122 and the service distribution module 123 can be, for example, JSON (JavaScript Object Notation), Extensible Markup Language (Extensible Markup Language, XML) or YAML, or the like. programming language, but the present invention is not limited thereto.

In this embodiment, the user can, for example, execute the request integration system 100 through a personal computer device, and log the 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 portal module 121, the throttling deployment module 122 and the business distribution module 123 according to the request data to convert the request data into data objects that can be read/approved by the ERP system or AP server, and According to the request importance level and sequence, it is transmitted to the ERP system or AP server through the channel to execute the corresponding business service function, making the ERP system's service response more immediate and the system more stable. In this embodiment, the user can input one or more requests into the request integration system 100 through the (specific) third-party system. The request is request data, and the request data is, for example, an enterprise work order or a service request. Requests (request data) can be requests made by different third-party systems, or requests made by the same system. The request integration system 100 performs request dispatch processing and channel management based on 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 the business can be executed. The service's ERP system responds more promptly to services, and reserves processing channels for corresponding requests based on the number of channels authorized by the user or enterprise to ensure that no request is 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 order and sequence. 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 110 performs parsing processing according to the message type of the requested data through the entry module 310 to obtain the header and the message. In this embodiment, the portal module 310 can support multiple protocols, such as a Web service protocol and a Representational State Transfer (restful) protocol, but the invention is not limited thereto. The entrance module 310 uses the corresponding data processor 110 to parse and read the data according to the protocol type of the requested data (request to be processed) to obtain the header and message of each requested data, and then obtain (know) each request. The service content and importance level of the data. 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 110 may establish multiple channels corresponding to the maximum allowable value according to the maximum allowable value of the number of channels through the throttling allocation module 320. In this embodiment, the throttling deployment module 320 creates 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 by purchasing 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 110 may perform channel management processing according to the importance level of the requested data and the receiving order of the requested 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 channel group. The current idle channel in 322 passes the sorted request data through the current idle channel in order to complete the management of the channel and request data. In this embodiment, each channel dispatches a request data (request service) at the same time, and whether the channel is in an idle state depends on whether the service dispatched 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 continuous 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 110 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 333 of the requested data through the service distributor 331 according to the header and message of the requested data. 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 data objects. Data conversion processing includes performing at least one of formula operations, band values, data verification, data conversion, create, read, update and delete (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 332. The data serialization service 332 serializes messages requesting data to generate data objects.

In this way, the serialized request data is a data object recognized by the request integration system and/or the ERP system. The data object is the request data that has been 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 data 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 110 may output the data object through the service distribution module 330. In this embodiment, the business 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 efficient. Stable levels are 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 an end point distribution unit 415 . The business distribution module 123 includes a business 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 of the requested 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 queue management unit 413 sorts multiple requests according to the importance level and sequence of the requested 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 415 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/enables N channels, where N is a positive integer. The request queue management unit 413 queues the requested data according to the priority/ordering of the requested data, and sequentially enters the currently idle channel in the channel group 322 for processing, thereby achieving the effect of current limiting and queuing of the requested 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 a one-to-one Communication. The business distribution unit 4151 converts the request data and its message into data objects through the serialization service. In this embodiment, the business service distribution unit 417 generates a service name identifier and a data identifier of the requested data by analyzing the header and message of the requested 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 business distribution unit 4151 converts the request data into data objects through serialization processing, and before the business distribution unit 4151 distributes the request data to the application server 440, the business service distribution unit 417 may convert the request data to the application server 440. Log in to the 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 logs the request data into 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, the data conversion processing includes performing formula, band value, data verification, data conversion, creation, reading, updating and deletion (CRUD) operations on the 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 objects to the processing system corresponding to the requested data packet. In this embodiment, the business service distribution unit 417 performs service distribution according to the agreement 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 into 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. Service distributor 443 of program server 440.

After the ERP system receives the requested data (data objects) that have 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.

In summary, 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 given priority to the business processing of the ERP product itself, so that the service response of the ERP system More timely, the system runs more stably; in addition, corresponding processing channels can be reserved based on the number of concurrent third-party integrations evaluated before the system goes online to ensure timely response from third-party integration services. The queuing method will also be used for parts exceeding the evaluation to ensure Requests are handled without missing a beat.

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.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present disclosure, but not to limit it; although the present disclosure 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 disclosure. Scope.

100:Request integrated system 110: Processor 120:Storage device 121: Entrance module 122: Throttle deployment module 123:Business distribution module 300_R: Pending request 300: Request integrated system 310: Entrance 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: Entrance 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 service 445:Verification service 446:Workflow services 447:Reporting Services 448:Batch service S210~S250: steps

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.

100:Request integrated system

110: Processor

120:Storage device

121: Entrance module

122: Throttle deployment module

123:Business distribution module

Claims (16)

A request integration system including: a storage device to store multiple 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 include an entry module, a throttling deployment module, and a service distribution module, wherein the entry module performs parsing processing according to the message types of the multiple request data to obtain the header and message of each request data, The throttling deployment module establishes multiple channels corresponding to the maximum allowable value according to the maximum allowable value of the number of channels, and the throttling deployment module establishes multiple channels corresponding to the maximum allowable value according to the importance levels of the multiple request data and the multiple The order in which the requested data is received is processed through channel management. The business distribution module performs data processing on the multiple request data according to the headers and messages of the multiple request data to generate multiple data objects, and the business distribution module outputs the multiple Data objects. The request integration system as described in claim 1, wherein the service distribution module includes: The business service distribution unit generates multiple service name identifiers and multiple data identifiers by analyzing the headers of the multiple requests and the messages of the multiple request data; and The data processing unit performs data conversion processing on the multiple request data to generate multiple object data. The request integration system according to claim 2, wherein the data processing unit includes a serializer, and the serializer serializes the message requesting data to generate the plurality of data objects. The request integration system according to claim 2, wherein the business service distribution unit performs business distribution on the corresponding plurality of data objects according to the agreement types and business service contents of the plurality of request materials. The request integration system according to claim 4, wherein the business distribution includes the business service distribution unit outputting the plurality of data objects to an application server to execute services corresponding to the business service content. The request integration system as described in claim 1, wherein the throttling deployment module includes: The request queue management unit sorts the plurality of request materials according to the importance level and order of the plurality of request materials; A channel distribution unit that enables a corresponding number of channels according to the maximum allowed value of the number of channels; and The terminal distribution unit receives the plurality of request data through the channel distribution unit, and establishes communication between each of the channels and the service distribution unit of the service distribution module, The channel distribution unit sequentially transmits the plurality of request data to the currently idle channel in the channel according to the ordering of the plurality of request data. The request integration system as described in claim 6, wherein the terminal distribution unit communicates with the authorization center to obtain the number of authorized channels for the user, The channel distribution unit includes a channel counter, and the channel counter uses the number of authorized channels as the maximum allowed value of the number of channels. The request integration system according to claim 1, wherein the entry module reads the plurality of request data through a corresponding serializer according to the message type of the plurality of request data. A request integration method that includes: Receive multiple request data, and perform parsing processing according to the message types of the multiple request data to obtain the header and message of each request data; Establish multiple channels corresponding to the maximum allowed value according to the maximum allowed value of the number of channels, and perform channel management processing according to the importance levels of the multiple requested materials and the reception order of the multiple requested materials; Perform data processing on the multiple request data according to the headers and messages of the multiple request data; and Output the plurality of data objects. The request integration method as described in claim 9, wherein the step of processing the plurality of request materials according to the headers and the messages of the plurality of request materials includes: Generate multiple service name identifiers and multiple data identifiers by analyzing the headers of the multiple requests and the messages of the multiple request data; and Perform data conversion processing on the multiple request data to generate multiple object data. The request integration method according to claim 10, wherein the data conversion processing includes serializing the message requesting data to generate the plurality of data objects. The request integration method as described in claim 10, wherein the step of outputting the plurality of data objects includes: processing the corresponding plurality of data objects according to the agreement type and business service content of the plurality of request data. Business distribution. The request integration method according to claim 12, wherein the service distribution includes outputting the plurality of data objects to an application server (AP server) to execute services corresponding to the business service content. The request integration method according to claim 10, wherein the plurality of channels corresponding to the maximum allowable value are established according to the maximum allowable value of the number of channels, and the plurality of channels corresponding to the maximum allowable value are established according to the importance of the plurality of request materials. The steps of performing channel management processing based on the level and the receiving sequence of the plurality of request materials include: Sort the multiple request materials according to the importance level and order of the multiple request materials; Enable the corresponding number of channels according to the maximum allowed value of the number of channels; Receive the plurality of request data, and establish communication between each of the channels and the service distribution unit; and According to the ordering of the plurality of request data, the plurality of request data are sequentially transmitted to the currently idle channel in the channel. The request integration method as described in request item 14, wherein the step of enabling a corresponding number of channels according to the maximum allowed value of the number of channels includes: Communicate with the authorization center to obtain the number of authorized channels for users, The number of authorized channels is taken as the maximum allowed value of the number of channels. The request integration method as described in claim 9, wherein the step of parsing and processing according to the message types of the plurality of request materials includes: The plurality of request data are read through a corresponding serializer according to the message types of the plurality of request data.

Images