CN115086429B - Request integration system and request integration method - Google Patents
Request integration system and request integration method Download PDFInfo
- Publication number
- CN115086429B CN115086429B CN202210530673.2A CN202210530673A CN115086429B CN 115086429 B CN115086429 B CN 115086429B CN 202210530673 A CN202210530673 A CN 202210530673A CN 115086429 B CN115086429 B CN 115086429B
- Authority
- CN
- China
- Prior art keywords
- data
- request
- request data
- channels
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000010354 integration Effects 0.000 title claims abstract description 59
- 238000000034 method Methods 0.000 title claims abstract description 27
- 238000009826 distribution Methods 0.000 claims abstract description 75
- 238000012545 processing Methods 0.000 claims abstract description 55
- 238000003860 storage Methods 0.000 claims abstract description 11
- 238000007726 management method Methods 0.000 claims description 19
- 238000006243 chemical reaction Methods 0.000 claims description 16
- 230000008569 process Effects 0.000 claims description 7
- 238000004891 communication Methods 0.000 claims description 4
- 230000006978 adaptation Effects 0.000 claims description 2
- 238000012163 sequencing technique Methods 0.000 claims description 2
- 238000013501 data transformation Methods 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 3
- 238000013524 data verification Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000007639 printing Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000007405 data analysis Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 239000000344 soap Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
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
Technical Field
The present invention relates to an integrated system and a method thereof, and more particularly, to a request integrated system and a method thereof.
Background
Current businesses need to store and transmit request data at the same time. Meanwhile, as more and more systems issue requests, the concurrency requirement of requesting data calls increases, resulting in occupying the resources of the service execution system to perform request integration processing. Resulting in situations where the service execution system cannot respond to the request in real time and where delays occur in client operations. If the integration server is deployed separately from the application server, the load pressure is transferred to the database server, and thus the problem of ineffective integration and dispatch of the requested data still remains. In view of this, several embodiments of the solution will be presented below.
Disclosure of Invention
The invention aims at a request integration system and a data integration method, which can provide request integration and dispatch effects with high efficiency and high stability.
According to an embodiment of the invention, the request integrates a system memory device and a processor. The storage device stores an entry module, a throttle deployment module, and a service distribution module executed by the processor. 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.
According to an embodiment of the present invention, a request integration method of the present invention includes: analyzing according to the message type of the request data to obtain a header and a message; establishing a plurality of corresponding channels according to the maximum allowable value of the channel number; carrying out channel management processing according to the importance level and the receiving sequence of the request data; according to the header and the message of the request data, carrying out data processing on the request data to generate a plurality of data objects; and outputting the data object to the service processing system.
Based on the above, the request integrating system and the request integrating method can limit and queue the request through the throttle valve mechanism so as to achieve more timely response of the service request and more stable service processing system.
In order to make the above features and advantages of the present invention more comprehensible, embodiments accompanied with figures are described in detail below.
Drawings
FIG. 1 is a schematic diagram of a request integration system according to an embodiment of the invention;
FIG. 2 is a flow chart of a request integration method of an embodiment of the present invention;
FIG. 3 is a schematic diagram of a request integration system and pending requests according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a request integration system, a third party system, an authorization center, and an application server according to an embodiment of the invention.
Description of the reference numerals
100, requesting an integrated system;
110, a processor;
120, a storage device;
121, an inlet module;
122, a throttle allocation module;
123, a service distribution module;
300_R, request to be processed;
300, requesting an integrated system;
310 an inlet module;
320, a throttle allocation module;
321, a pairing management service module;
322 channel group;
a service distribution module 330;
331, service distributor;
332 data serialization services;
333, service content;
410, requesting an integrated system;
411: an inlet module;
412 an internal restful entry service;
413 a request queue management unit;
a channel distribution unit 414;
4141 channel counter;
415, an end point distribution unit;
4151 a service distribution unit;
416 a data processing unit;
417, business service distribution unit;
418, connecting a distributor;
419 remote connector;
420 a third party system;
430, authorizing the center;
431 controller
440, application server;
441 remote connector;
442, connect to the distributor;
443, service distributor;
444 set up/read/update/delete/query services;
445, verifying the service;
446 workflow services;
447 reporting services;
448 batch service;
S210-S250, namely the steps.
Detailed Description
Reference will now be made in detail to the exemplary embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the description to refer to the same or like parts.
FIG. 1 is a schematic diagram of a request integration system according to an embodiment of the invention. Referring to fig. 1, a request integration system 100 includes a processor 110 and a storage 120. The processor 110 is coupled to the storage device 120. The storage device 120 stores an entry module 121, a throttle deployment module 122, and a service distribution module 123. In this embodiment, the request integration system 100 may be, for example, provided in a local end system of an enterprise or a user, so that the user may send a request from a third party system to the request integration system. The requests are limited and queued by the architecture and technology implementation of the request integration system, and then distributed into various enterprise resource planning (Enterprise Resource Planning, ERP) systems to provide related business service functions (e.g., generating purchase orders, offers, etc.) in sequence by ordering the requests according to importance levels and order. The ERP system may be, for example, an application service system provided in an application server (AP server). Alternatively, in an embodiment, the request integration system 100 may be disposed in a cloud server for users to connect and transmit request data and perform related Business service (Business) functions. In another embodiment, the request integration system 100 may be applied in service-level application scenarios, for example, the request integration system 100 may be applied in the scenarios of recording, report printing, export data, etc. of the ERP system, so as to allocate different numbers of channels by ordering the request integration system according to the importance level of the function or service item (e.g. recording > report printing > export data).
In this embodiment, the processor 110 may include, for example, a central processing unit (Central Processing Unit, CPU), or other programmable general purpose or special purpose Microprocessor (Microprocessor), digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuits, ASIC), programmable logic device (Programmable Logic Device, PLD), other similar processing circuit, or a combination of these devices. The storage 120 may include a Memory (Memory) and/or a database (database), where the Memory may be, for example, a Non-Volatile Memory (NVM). The storage device 120 may store relevant programs, modules, systems, or algorithms for implementing embodiments of the invention for access and execution by the processor 110 to implement the relevant functions and operations described by the embodiments of the invention. In the present embodiment, the entry module 121, the throttle deployment module 122, and the service distribution module 123 may be implemented in a program language such as JSON (JavaScript Object Notation), extensible markup language (Extensible Markup Language, XML), or YAML, for example, but the present invention is not limited thereto.
In the present embodiment, the user may execute the request integration system 100, for example, through a personal computer device, and input request data to the request integration system 100 to request execution of a corresponding business service function. The request integration system 100 may execute the entry module 121, the throttle allocation module 122, and the service distribution module 123 according to the request data to convert the request data into data objects readable/recognizable by the ERP system or the AP server, and correspondingly transmit the data to the ERP system or the AP server through channels according to the importance level and the order of the request to execute corresponding service functions, so that the service response of the ERP system is more real-time and the system is more stable. In this embodiment, a user may enter one or more requests into the requesting integrated 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 service request. The request (request data) may be a request issued by a different third party system or may be a request issued by the same system. The request integration system 100 performs the dispatch processing of the requests and the management of the channels according to the priority and the receiving sequence of the plurality of requests and the number of channels authorized by the user so as to achieve the business processing of reserving resources for the EPR system in priority, so that the ERP system performing business services responds more timely to the services, and reserves the processing channels corresponding to the requests according to the number of channels authorized by the user or the enterprise so as to ensure that the requests cannot be missed.
FIG. 2 is a flow chart of a request integration method of an embodiment of the present invention. FIG. 3 is a schematic diagram of a request integration system and pending requests according to an embodiment of the invention. Referring to fig. 2 and 3, the request integration system 300 may perform the following steps S210 to S250 to sequentially distribute the request data to the corresponding application services in priority and in order of precedence. As shown in fig. 3, the ingress module 310 receives a plurality of pending requests 300_r. The pending request 300_r is, for example, to query vendor information, create a work order, and review a sales order.
In step S210, the processor performs parsing processing according to the message type of the request data through the ingress module 310 to obtain a header and a message. In the present embodiment, the portal module 310 may support various protocols, such as a Web service (Web service) protocol and a representational state transfer (Representational State Transfer) protocol, but the present invention is not limited thereto. The entry module 310 performs data analysis and reading with a corresponding data processor according to the protocol type of the request data (to-be-processed request), so as to obtain the header and the message of each request data, and further obtain (know) the service content and the importance level of each request data. In one embodiment, the entry module 310 reads the request data through the corresponding serializer according to the message type of the request data.
In step S220, the processor may establish a plurality of channels corresponding to the maximum allowable value according to the maximum allowable value of the channel number through the throttle allocation module 320. In this embodiment, the throttle allocation module 320 establishes the channel group 322 with the corresponding channel number according to the received or built-in maximum allowable value (number) of channel numbers. The number of channels is the number of concurrent connections (concurrent number) authorized according to the enterprise or user. In one embodiment, the user can increase the authorized concurrency number by purchasing according to the requirement, so as to improve the execution efficiency of the user on the request data and the flexibility of the planning in the economy.
In step S230, the processor may perform channel management processing according to the importance level of the request data and the receiving order of the request data through the throttling allocation module 320. In this embodiment, the queue management service module 321 of the throttle allocation module 320 orders the request data according to the importance level and the acquisition (transmission) order of each request data, and the throttle allocation module 320 sequentially passes the ordered request data through the current idle channel according to the current idle channel in the channel group 322 to complete the management of the channel and the request data. In the present embodiment, each channel simultaneously dispatches one request data (request service), and whether the channel is in an idle state is based on whether the service dispatched by the channel is performed. That is, after the request data is transmitted to the request integration system 300, the request data is received by the current idle channel in the channel group 322 through the assignment and sequential processing of the column management service module 321. And then to a corresponding service processing system, such as an ERP system. When the service of the requested data is completed, the channel returns to the idle state and waits for the transmission of the subsequent requested data.
In step S240, the processor may perform data processing (data conversion processing) on the request data to generate a data object according to the header and the message of the request data through the service distribution module 330. In this embodiment, the service distribution module 330 obtains the protocol type and the service content of the request data according to the header and the message of the request data through the service distributor 331. And, the service distribution module 330 performs a corresponding data conversion process on the request data according to the service content 333 of the request data to generate a data object. The data conversion process includes performing at least one of a formula operation, a tape value, a data check, a data conversion, a create, a read, an update, and a delete (CRUD) operation. In the present 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 for providing a data serialization service 322 that serializes the message requesting the data to generate the data object.
As such, the serialized request data is a data object that is recognizable by the requesting integrated system and/or the ERP system. The data object is request data subjected to data conversion processing. Thus, the request data after the data conversion processing is organized into more complete and effective data, and the request data after the conversion processing is approved and readable data by the ERP system, so that the efficiency and the stability of the request data dispatch and the subsequent execution of business services are improved. 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 the ERP system according to the service content 333 of the requested data.
In this way, the request integration system 300 and the method thereof of the present invention can sort the request data according to the priority and the transmission sequence of the request data, and can establish the channel number according to the concurrency number purchased by the user, so that the distribution and management of the request data are more stable and more efficient. Meanwhile, service response of the ERP system is improved more timely.
FIG. 4 is a schematic diagram of a request integration system, a third party system, an authorization center, and an application server according to an embodiment of the invention. Referring to fig. 1 and 4, the throttle adaptation module 122 includes a request pairing management unit 413, a channel distribution unit 414, and an endpoint distribution unit 415. The service distribution module 123 includes a service distribution unit 4151, a service distribution unit 417, and a data processing unit 416. The enterprise or user sends one or more request data via the third party system 420 to the portal module 411 of the request integration system 410. The third party system 420 is, for example, an electronic commerce system, a personnel management system, and a manufacturing execution system. The format of the request data is, for example, JSON or XML format, and the protocol of the request data is, for example, restful or SOAP protocol. In this embodiment, the internal Restful entry service 412 receives the request data and transmits to the request queue management unit 413. The request queue management unit 413 sorts the plurality of requests according to the importance level and the order of the request data.
In the present embodiment, the channel distribution unit 414 enables the same number of channels according to the maximum allowable value of the number of channels. In one embodiment, endpoint distribution unit 415 communicates with controller 431 of rights issuer 430 to obtain the number of channels authorized by the user. The number of channels authorized is, for example, the number of channels purchased by the user. The endpoint distribution unit transmits the authorized number of channels 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 allowable value of the number of channels. That is, when the number of integrated concurrency for which the user is authorized is N, the channel distribution unit 414 establishes/enables N channels, N being a positive integer. The request queue management unit 413 queues the request data according to the priority/sequencing of the request data, and sequentially enters the current idle channels in the channel group for processing, thereby achieving the effects of request data flow restriction and queuing.
In the present embodiment, the destination distribution unit 415 receives the request data through the channel distribution unit 414, and the destination 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 the message thereof into data objects through the serialization service. In the present embodiment, the business service distribution unit 417 generates a service name identification of the request data and a data identification by analyzing a header and a message of the request data. As such, the business service distribution unit 417 distributes the request data subjected to the data conversion to the corresponding service flow (ERP flow) in the application server 440 according to the service name designation and the data designation.
In the present embodiment, after the service distribution unit 4151 converts the request data into the data object through the serialization process, and before the service distribution unit 4151 distributes the request data to the application server 440, the service distribution unit 417 may input the request data to the data processing unit 416. In this manner, the requested data or data objects are subjected to data conversion processing by the data processing unit 416 to generate a plurality of data objects. In this way, the request data is converted into the system-approved and readable data objects through the serialization process, so as to increase the data recognition degree and improve the distribution efficiency. In one embodiment, the business service distribution unit 417 inputs the request data to a corresponding one of the data processing units 416 according to header information of the request data to generate a plurality of data objects. The processing units are, for example, a data conversion/exchange unit, a serializer, a data verification unit, a data band value unit and an arithmetic unit. And, the data conversion process includes performing formula, tape value, data verification, data conversion, creation, reading, update, and deletion (CRUD) operations on the data.
In the present embodiment, the data processing unit 416 outputs the processed data object 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 the present embodiment, the business service distribution unit 417 performs business distribution according to the protocol type of the request data and the business service content. The service distribution includes the service distribution unit 417 outputting the data object to the application server 440 to perform a service corresponding to the 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. As such, the service distributor 443 of the application server 440 receives the request data through the remote connector 419 and inputs the data objects to the corresponding service modules. The service module may be various services in an ERP system. In another embodiment, the business service distribution unit 417 may also transmit the data object to the remote connector 441 of the application server 440, and further cause the connection distributor 442 to receive the data object through the remote connector 441 and output to the service distributor 443 of the application server 440.
After receiving the request data (data object) subjected to data conversion processing and/or serialization processing, the ERP system performs service processing through a plurality of service modules. Such as setup/read/update/delete/query services 444, verification services 445, workflow services 446, reporting services 447, and lot services 448. The service process is, for example, querying the vendor, adding/subtracting work order data, confirming sales orders, querying/retrieving vendor data, and the like. For example, the business service distribution unit 417 and the ERP system may learn that the requested service is a query provider according to the header of the request data, and learn the query condition according to the message of the request data.
In summary, the request integration system and the request integration method can realize the current limiting and queuing of the third-party integration request so as to ensure that the hardware resources are reserved for the business processing of the ERP product, so that the service response of the ERP system is more timely, and the system operation is more stable; in addition, corresponding processing channels can be reserved according to the concurrent number of third party integration evaluated before the system is online, so that timely response of third party integration service is guaranteed, a queuing mode is adopted for the part beyond evaluation, and the request processing is guaranteed not to be omitted.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.
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.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210530673.2A CN115086429B (en) | 2022-05-16 | 2022-05-16 | Request integration system and request integration method |
| TW111123917A TW202347195A (en) | 2022-05-16 | 2022-06-27 | Request integration system and request integration method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210530673.2A CN115086429B (en) | 2022-05-16 | 2022-05-16 | Request integration system and request integration method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115086429A CN115086429A (en) | 2022-09-20 |
| CN115086429B true CN115086429B (en) | 2024-02-13 |
Family
ID=83246622
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210530673.2A Active CN115086429B (en) | 2022-05-16 | 2022-05-16 | Request integration system and request integration method |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115086429B (en) |
| TW (1) | TW202347195A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106034157A (en) * | 2015-03-18 | 2016-10-19 | 国家计算机网络与信息安全管理中心 | HTTP transmission method in data exchange, server and storage device |
| CN108322488A (en) * | 2017-01-16 | 2018-07-24 | 广州市联奥信息科技有限公司 | The system that trust data is shared and distributes is realized in multiple car networkings |
| WO2019192103A1 (en) * | 2018-04-03 | 2019-10-10 | 平安科技（深圳）有限公司 | Concurrent access control method and apparatus, terminal device, and medium |
| CN112887360A (en) * | 2015-03-16 | 2021-06-01 | 利维帕尔森有限公司 | Prioritization of resources and establishment of communication channels |
| WO2021218018A1 (en) * | 2020-04-28 | 2021-11-04 | 平安科技（深圳）有限公司 | Data processing method and apparatus for implementing cross-domain request at webpage end, and related device |
| CN114500542A (en) * | 2020-11-12 | 2022-05-13 | 中移信息技术有限公司 | Service flow distribution method, device, equipment and computer storage medium |
-
2022
- 2022-05-16 CN CN202210530673.2A patent/CN115086429B/en active Active
- 2022-06-27 TW TW111123917A patent/TW202347195A/en unknown
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112887360A (en) * | 2015-03-16 | 2021-06-01 | 利维帕尔森有限公司 | Prioritization of resources and establishment of communication channels |
| CN106034157A (en) * | 2015-03-18 | 2016-10-19 | 国家计算机网络与信息安全管理中心 | HTTP transmission method in data exchange, server and storage device |
| CN108322488A (en) * | 2017-01-16 | 2018-07-24 | 广州市联奥信息科技有限公司 | The system that trust data is shared and distributes is realized in multiple car networkings |
| WO2019192103A1 (en) * | 2018-04-03 | 2019-10-10 | 平安科技（深圳）有限公司 | Concurrent access control method and apparatus, terminal device, and medium |
| WO2021218018A1 (en) * | 2020-04-28 | 2021-11-04 | 平安科技（深圳）有限公司 | Data processing method and apparatus for implementing cross-domain request at webpage end, and related device |
| CN114500542A (en) * | 2020-11-12 | 2022-05-13 | 中移信息技术有限公司 | Service flow distribution method, device, equipment and computer storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| TW202347195A (en) | 2023-12-01 |
| CN115086429A (en) | 2022-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9742614B2 (en) | Data-type definition driven dynamic business component instantiation and execution framework | |
| CN110740103A (en) | Service request processing method and device, computer equipment and storage medium | |
| US8805938B2 (en) | Enterprise service bus and message processing method thereof | |
| US6836892B2 (en) | Apparatus and method for use in distributed computing environment for converting data format between program language-specific format used in respective computers and stream format used for communication among computers | |
| CN112511218B (en) | Satellite ground station monitoring system based on microservice | |
| CN105376111B (en) | Resource allocation methods and device | |
| CN111800434A (en) | Multi-channel asset docking platform and working method thereof | |
| CN110688828A (en) | File processing method and device, file processing system and computer equipment | |
| CN111240862A (en) | Universal interface platform and data conversion method | |
| US20060136602A1 (en) | Electronic data interchange apparatus | |
| CN112288577A (en) | Transaction processing method and device for distributed service, electronic equipment and medium | |
| CN113486629A (en) | Application method and system for enterprise service bus of docking third-party system | |
| US8387070B2 (en) | Object request broker | |
| CN111913784B (en) | Task scheduling method and device, network element and storage medium | |
| CN105224594B (en) | Service-oriented architecture data interconnection query system and query method | |
| CN112181628B (en) | Resource transfer method, device, system and electronic equipment | |
| US20090132582A1 (en) | Processor-server hybrid system for processing data | |
| CN115086429B (en) | Request integration system and request integration method | |
| CN110442464A (en) | Method for processing business, business processing device, electronic equipment and medium | |
| CN111901384B (en) | System, method, electronic device and readable storage medium for processing message | |
| JP4516594B2 (en) | Message transmission control method, message transmission control device, and message transmission control program | |
| KR20140013892A (en) | Method of comparing output in a plurality of information systems | |
| CN114189476A (en) | Multi-interface shunting calling method and terminal | |
| CN114461230A (en) | Gray scale publishing method, device, equipment and medium | |
| CN113392093A (en) | Service processing method and device, electronic equipment and computer readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |