CN115086429A - Request integration system and request integration method - Google Patents
Request integration system and request integration method Download PDFInfo
- Publication number
- CN115086429A CN115086429A CN202210530673.2A CN202210530673A CN115086429A CN 115086429 A CN115086429 A CN 115086429A CN 202210530673 A CN202210530673 A CN 202210530673A CN 115086429 A CN115086429 A CN 115086429A
- 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.)
- Granted
Links
- 230000010354 integration Effects 0.000 title claims abstract description 67
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000009826 distribution Methods 0.000 claims abstract description 70
- 238000012545 processing Methods 0.000 claims abstract description 55
- 238000003860 storage Methods 0.000 claims abstract description 12
- 230000008569 process Effects 0.000 claims abstract description 11
- 238000007726 management method Methods 0.000 claims description 19
- 238000006243 chemical reaction Methods 0.000 claims description 12
- 238000004891 communication Methods 0.000 claims description 5
- 238000013501 data transformation Methods 0.000 claims description 3
- 238000012163 sequencing technique Methods 0.000 claims 2
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000007639 printing Methods 0.000 description 2
- 238000013524 data verification Methods 0.000 description 1
- 230000003111 delayed effect 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
- 238000012546 transfer Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
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 comprises a storage device and a processor. The storage device stores an entrance module, a throttling allocation module and a service distribution module. The processor is used for executing the entrance module, the throttling deployment module and the service distribution module and receiving the request data. And the entry module analyzes and processes the message type of the request data to obtain the header and the message of the request data. The throttling deployment module establishes a plurality of channels corresponding to the maximum allowable value according to the maximum allowable value of the number of the channels, and performs channel management processing according to the importance level and the receiving sequence of the request data. And 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. And the service distribution module outputs the data object.
Description
Technical Field
The present invention relates to an integration system and a method thereof, and more particularly, to a request integration system and a method thereof.
Background
More and more requested data are currently being stored and simultaneously transmitted by enterprises. Meanwhile, as more and more systems issue requests, the concurrent amount of request data calls also increases, resulting in occupying resources of the service execution system to perform request integration processing. Leading to the situation that the service execution system cannot respond to the request in real time and the operation of the client terminal is delayed. If the integration server is deployed separately from the application server, the load is shifted to the database server, and thus the problem of inefficient integration and distribution of the requested data still remains. In view of this, several embodiments of solutions will be presented below.
Disclosure of Invention
The invention aims at a request integration system and a data integration method, and can provide high-efficiency and high-stability request integration and dispatch effects.
According to an embodiment of the invention, the request integration system storage device and the processor are provided. The storage device stores an entry module, a throttle deployment module, and a traffic distribution module that are executed by the processor. And the entry module analyzes and processes the message type of the request data to obtain the header and the message of the request data. The throttling deployment module establishes a plurality of channels corresponding to the maximum allowable value according to the maximum allowable value of the number of the channels, and performs channel management processing according to the importance level and the receiving sequence of the request data. And 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. And 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 number of the channels; performing 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, performing 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 integration system and the request integration method of the invention can limit the flow and queue the requests through the throttle valve mechanism, so as to achieve the purposes of more timely response of the service request and more stable service processing system.
In order to make the aforementioned and other features and advantages of the invention more comprehensible, embodiments accompanied with figures are described in detail below.
Drawings
FIG. 1 is a schematic diagram of a request integration system of an embodiment of the present invention;
FIG. 2 is a flow diagram of a request integration method of an embodiment of the invention;
FIG. 3 is a schematic diagram of a request integration system and pending requests according to an embodiment of the 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 present invention.
Description of the reference numerals
100, requesting an integrated system;
110, a processor;
120, a storage device;
121: an inlet module;
122, a throttling and allocating module;
123, a service distribution module;
300_ R is a request to be processed;
requesting an integrated system 300;
310, an entrance module;
320, a throttling and allocating module;
321, a queue management service module;
322, a channel group;
330, a service distribution module;
331 a service distributor;
332, data serialization services;
333, service content;
requesting an integration system 410;
411, an inlet module;
internal restful entry service 412;
413, request queue management unit;
414 channel distribution unit;
4141 channel counter;
415, a destination distribution unit;
4151 a service distribution unit;
416, a data processing unit;
417 a traffic service distribution unit;
418, connecting the distributor;
419 remote connector;
420, a third party system;
430, an authorization center;
431 controller
440, application server;
441, a remote connector;
442, connecting the distributor;
443 a service distributor;
444, create/read/update/delete/query service;
445, authentication service;
446: workflow services;
447 reporting service;
448, batch service;
S210-S250.
Detailed Description
Reference will now be made in detail to exemplary embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings and the description to refer to the same or like parts.
FIG. 1 is a schematic diagram of a request integration system of an embodiment of the present invention. Referring to fig. 1, a request integration system 100 includes a processor 110 and a storage 120. The processor 110 is coupled to a storage device 120. The storage device 120 stores an entry module 121, a throttle deployment module 122, and a traffic distribution module 123. In this embodiment, the request integration system 100 may be, for example, a local system of an enterprise or a user, for the user to send a request from a third-party system to the request integration system. The current limitation and queuing of the requests are realized through the architecture and technology of the request integration system, and then the requests are distributed to various Enterprise Resource Planning (ERP) systems, so that the requests are sequenced according to the importance level and the sequence, and related business service functions (such as business services of generating purchase orders, purchase requisition orders, quotation and the like) are provided in sequence. 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, so that the user can connect to the cloud server and transmit the request data and execute a Business service (Business service) function. In another embodiment, the request integration system 100 can be applied to the application scenario of service classification, for example, the request integration system 100 can be applied to the scenario of entry, report printing, export data, etc. of the ERP system, so as to allocate different numbers of channels by requesting the integration system to sort according to the importance level of the function or business item (e.g. entry > report printing > export data).
In the present embodiment, the Processor 110 may include, for example, a Central Processing Unit (CPU), or other Programmable general purpose or special purpose Microprocessor (Microprocessor), Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC), Programmable Logic Device (PLD), other similar Processing Circuits, or a combination thereof. The storage device 120 may include a Memory (Memory) and/or a database (database), wherein the Memory may be, for example, a Non-Volatile Memory (NVM). The storage device 120 may store the relevant programs, modules, systems or algorithms for implementing the embodiments of the present invention, so as to be accessed and executed by the processor 110 to implement the relevant functions and operations described in the embodiments of the present invention. In the embodiment, the entry module 121, the throttle deployment module 122 and the service distribution module 123 may be implemented by a program Language such as json (javascript Object notification), Extensible Markup Language (XML), YAML, or the like, but the invention is not limited thereto.
In the embodiment, the user may execute the request integration system 100 through a personal computer device, for example, and input the request data to the request integration system 100 to request to execute the corresponding business service function. The request integration system 100 may execute the entry module 121, the throttling deployment module 122 and the service distribution module 123 according to the request data, so as to convert the request data into a data object that can be read/approved by the ERP system or the AP server, and correspondingly transmit the data object to the ERP system or the AP server through a channel according to the request importance level and the order, so as to execute a corresponding service function, so that the service response of the ERP system is more real-time and the system is more stable. In this embodiment, the user may enter one or more requests into the requesting integrated system 100 through a (particular) 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) 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 executes the dispatch processing and channel management of the requests according to the priorities and receiving orders of the requests and the number of authorized channels of the users so as to achieve the business processing that the rigid resources are preferentially reserved for the EPR system, so that the ERP system executing the business service can respond to the service more timely, and reserves the processing channels corresponding to the requests according to the number of authorized channels of the users or enterprises so as to ensure that the requests are not missed.
FIG. 2 is a flow diagram of a request integration method of an embodiment of the invention. FIG. 3 is a 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 according to the priority and the sequence. As shown in FIG. 3, the entry module 310 receives a plurality of pending requests 300_ R. The pending request 300_ R is, for example, to query for supplier 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 entry module 310 to obtain a header and a message. In this embodiment, the entry module 310 may support multiple protocols, such as a Web service (Web service) protocol and a Representational State Transfer (restful) protocol, but the invention is not limited thereto. The entry module 310 performs data parsing and reading by the corresponding data processor according to the protocol type of the request data (to-be-processed request) to obtain the header and the packet 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 packet 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 number of channels through the throttle scheduling module 320. In this embodiment, the throttle assignment module 320 establishes a channel group 322 with a corresponding channel number according to the received or built-in maximum allowable number (number) of channels. The channel number is the number of concurrent connections (concurrency number) according to which the enterprise or user is authorized. In one embodiment, the user can increase the authorized number of concurrent transactions by purchasing according to the requirement, so as to improve the flexibility of the user in executing the requested data and the planning between economy.
In step S230, the processor may perform a channel management process according to the importance level of the request data and the receiving order of the request data through the throttle scheduling 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 the obtaining (transmission) order of each request data, and the throttling deployment module 320 sequentially passes the sorted 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 this embodiment, each channel simultaneously dispatches a request (service request) and whether the channel is idle depends on whether the service dispatched by the channel has been performed. That is, after the request data is transmitted into the request integration system 300, the request data is received by the currently idle channel in the channel group 322 through the assignment and sequential processing of the column management service module 321. And then sent 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 through the service distribution module 330 according to the header of the request data and the message to generate a data object. In this embodiment, the service distribution module 330 obtains the protocol type and the service content of the request data through the service distributor 331 according to the header and the packet of the request data. And, the service distribution module 330 performs a corresponding data conversion process on the request data according to the service contents 333 of the request data to generate a data object. The data transformation process includes performing at least one of a formula operation, a tape value, a data check, a data transformation, 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 sequencer to provide a data serialization service 322 that serializes a message requesting data to produce a data object.
Thus, the serialized requested data is a data object that is approved by the request integration system and/or the ERP system. The data object is request data subjected to data conversion processing. Therefore, the request data subjected to the data conversion processing is organized into more complete and effective data, and the converted request data is data approved and readable by the ERP system, so that the efficiency and stability of the request data dispatching and the subsequent execution of business services are improved. At 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 according to the present invention can sort the request data according to the priority and transmission order of the request data, and can establish the channel number according to the number of concurrent requests purchased by the user, so that the dispatch and management of the request data are more stable and more efficient. Meanwhile, the 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 present invention. Referring to fig. 1 and 4, the throttle deployment module 122 includes a request queue management unit 413, a channel distribution unit 414, and an endpoint distribution unit 415. The traffic distribution module 123 comprises a traffic distribution unit 4151, a traffic service distribution unit 417 and a data processing unit 416. The enterprise or user sends one or more request data to the portal module 411 of the requesting integration system 410 through the third-party system 420. The third party systems 420 are, for example, electronic commerce systems, people management systems, and manufacturing execution systems. 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 pair column 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, the destination distribution unit 415 communicates with the controller 431 of the rights issuer 430 to obtain the number of channels that the user is authorized to have. The number of authorized channels is, for example, the number of channels purchased by the user. The destination 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 authorized channel number as the maximum allowable value of the channel number. That is, when the number of integrated concurrencies for which the user is authorized 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 request data according to the priority/sequence of the request data, and sequentially enters the current idle channel in the channel group for processing, so as to achieve the effects of requesting data current limiting and queuing.
In this embodiment, the destination distributing unit 415 receives the request data through the channel distributing unit 414, and the destination distributing unit 415 establishes communication between each channel and the service distributing unit 4151 of the service distributing module 123, thereby establishing one-to-one communication. The service distribution unit 4151 converts the request data and its message into a data object through the serialization service. In this embodiment, the business service distribution unit 417 generates the service name identifier and the data identifier of the request data by analyzing the header and the packet of the request data. In this way, the business service distribution unit 417 distributes the data-converted request data to a corresponding service process (ERP process) in the application server 440 according to the service name identifier and the data identifier.
In the present embodiment, the business service distribution unit 417 may input the request data to the data processing unit 416 after the business distribution unit 4151 converts the request data into the data object through the serialization process and before the business distribution unit 4151 distributes the request data to the application server 440. As such, the request data or data object is subjected to data conversion processing by the data processing unit 416 to generate a plurality of data objects. Therefore, through the serialization processing, the request data is converted into the data object which is approved and readable by the system, so that the data identification degree is increased and the distribution efficiency is improved. In one embodiment, the business service distribution unit 417 inputs the request data to a corresponding processing unit among 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 sequencer, a data verification unit, a data band value unit, and an arithmetic unit. And, the data conversion process includes performing formula, band value, data check, 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 service distribution unit 417 distributes the data object to the processing system corresponding to the request data packet. In this embodiment, the service distribution unit 417 performs service distribution according to the protocol type of the request data and the 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 an embodiment, the business service distribution unit 417 transmits the data object to the connection distributor 418, and the connection distributor 418 then transmits the data object to the remote connector 419. As such, the service dispatcher 443 of the application server 440 receives the requested data through the remote connector 419 and inputs the data objects to the corresponding service modules. The service modules may be 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, thereby causing the connection distributor 442 to receive the data object through the remote connector 441 and output it to the service distributor 443 of the application server 440.
After receiving the request data (data object) subjected to the data conversion processing and/or the serialization processing, the ERP system performs service processing through a plurality of service modules. Such as create/read/update/delete/query services 444, validation services 445, workflow services 446, reporting services 447, and batch services 448. The service processes are, for example, querying suppliers, adding/deleting work order data, confirming sales orders, querying/recalling supplier data, etc. For example, the business service distribution unit 417 and the ERP system may know that the requested service is a query provider according to the header of the request data, and know the query condition according to the message of the request data.
In conclusion, 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 preferentially reserved for the business processing of the ERP product, so that the service response of the ERP system is more timely, and the system runs more stably; in addition, a corresponding processing channel can be reserved according to the concurrency number of the third-party integration evaluated before the system is on line, so that the timely response of the third-party integration service is ensured, a queuing mode is adopted when the third-party integration service exceeds the evaluation part, and the processing of the request is not missed.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (16)
1. A request integration system, comprising:
a storage device storing 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 according to the packet types of the plurality of request data to obtain a header and a packet of each request data,
wherein the throttle allocating module establishes a plurality of channels corresponding to the maximum allowable value according to the maximum allowable value of the number of channels, and the throttle allocating module performs channel management processing according to the importance levels of the plurality of request data and the receiving order of the plurality of request data,
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:
the business service distribution unit is used for generating a plurality of service name identifications and a plurality of data identifications by analyzing the headers of the requests and the messages of the request data; and
and the data processing unit is used for performing data conversion processing on the plurality of request data to generate a plurality of object data.
3. The request integration system of claim 2, wherein the data processing unit comprises a sequencer that serializes the message of the requested data to produce the data object.
4. The request integration system of claim 2, wherein the business service distribution unit distributes the corresponding data objects according to the protocol types of the request data and the business service contents.
5. The request integration system of claim 4, wherein the business distribution comprises the business service distribution unit outputting the plurality of data objects to an application server to execute a service corresponding to the business service content.
6. The request integration system of claim 1, wherein the throttle deployment module comprises:
the request queue management unit is used for sequencing the plurality of request data according to the importance levels and the sequence of the plurality of request data;
the channel distribution unit enables the corresponding number of channels according to the maximum allowable value of the number of the channels; and
a destination 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,
the channel distribution unit transmits the plurality of request data to a current idle channel in the channels in sequence according to the sequence of the plurality of request data.
7. The request integration system of claim 6, wherein the destination distribution unit is in communication with an authorization center to obtain a number of channels authorized by a user,
wherein the channel distribution unit comprises a channel counter that takes 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 portal module reads the plurality of request data through the corresponding serializers according to message types of the plurality of request data.
9. A request integration method, comprising:
receiving a plurality of request data, and carrying out analysis processing 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 number of channels, and performing channel management processing according to the importance levels of the plurality of request data and the receiving sequence of the plurality of request data;
performing data processing on the plurality of request data according to the headers and the messages of the plurality of request data; and
outputting the plurality of data objects.
10. The request integration method according to claim 9, wherein the step of performing data processing on the plurality of request data according to the header and the packet of the plurality of request data comprises:
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 comprises serializing the message of the request data to produce the data object.
12. The request integration method of claim 10, wherein the step of outputting the plurality of data objects comprises: and performing service distribution on the corresponding data objects according to the protocol types of the request data and the service content.
13. The request integration method of claim 12, wherein the service distribution comprises outputting the plurality of data objects to an application server (AP server) to execute a service corresponding to the service content.
14. The request integration method according to claim 9, wherein the step of establishing the plurality of channels corresponding to the maximum allowable value according to the maximum allowable value of the number of channels, and performing channel management processing according to the importance levels of the plurality of request data and the reception order of the plurality of request data comprises:
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 the maximum allowable value of the number of the channels;
receiving said plurality of request data and establishing communication between each of said 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 sequence of the plurality of request data.
15. The request integration method of claim 14, wherein the step of enabling a corresponding number of the channels according to the maximum allowable value of the number of the channels comprises:
communicating 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 performing parsing processing according to the packet types of the plurality of request data comprises:
and reading the plurality of request data through corresponding serializers 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 true CN115086429A (en) | 2022-09-20 |
| CN115086429B 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 |
| CN115086429B (en) | 2024-02-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7725577B2 (en) | Method and system to adaptively manage the quality of service of interactions between smart item networks and enterprise applications | |
| CN101917385B (en) | Dispatch server and distributed system for multimedia trans-coding | |
| CN100477602C (en) | A method for realizing the multi-task polling in the network management monitoring system | |
| US20090080432A1 (en) | System and method for message sequencing in a broadband gateway | |
| US8805938B2 (en) | Enterprise service bus and message processing method thereof | |
| CN102025650A (en) | Message processing system and message processing method of enterprise service bus | |
| TW200532480A (en) | Dynamic late binding of third party on demand services in an on-demand infrastructure | |
| CN106294472A (en) | The querying method of a kind of Hadoop data base HBase and device | |
| CN104811475A (en) | Enterprise service bus middleware based on Restful technology | |
| CN111800434A (en) | Multi-channel asset docking platform and working method thereof | |
| CN112055078B (en) | Data transmission method, device, computer equipment and storage medium | |
| CN110688828A (en) | File processing method and device, file processing system and computer equipment | |
| CN111427694A (en) | Task execution method, device, system and server | |
| US8078666B1 (en) | Distributed report processing system and methods | |
| WO2011150601A1 (en) | Transaction processing system | |
| CN114710571B (en) | Data packet processing system | |
| CN110515741A (en) | A kind of degradation processing method and device based on local task queue | |
| US20090132582A1 (en) | Processor-server hybrid system for processing data | |
| CN113890891A (en) | Data sharing interaction method and device of energy cloud network | |
| CN111901384B (en) | System, method, electronic device and readable storage medium for processing message | |
| CN115086429B (en) | Request integration system and request integration method | |
| CN113095936A (en) | Entrusted order processing method, entrusted order processing device, computer equipment and storage medium | |
| CN111913784B (en) | Task scheduling method and device, network element and storage medium | |
| CN110636073A (en) | Distributed asynchronous remote service arranging and calling technology | |
| CN111401819B (en) | Intersystem data pushing method and system |
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 |