CN117234757A - Method and device for calling bottom layer service - Google Patents
Method and device for calling bottom layer service Download PDFInfo
- Publication number
- CN117234757A CN117234757A CN202311258877.6A CN202311258877A CN117234757A CN 117234757 A CN117234757 A CN 117234757A CN 202311258877 A CN202311258877 A CN 202311258877A CN 117234757 A CN117234757 A CN 117234757A
- Authority
- CN
- China
- Prior art keywords
- service
- bottom layer
- target
- layer service
- request message
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000012545 processing Methods 0.000 claims abstract description 33
- 230000004044 response Effects 0.000 claims description 34
- 238000004590 computer program Methods 0.000 claims description 14
- 238000011161 development Methods 0.000 description 16
- 238000005538 encapsulation Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 238000004806 packaging method and process Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Landscapes
- Exchange Systems With Centralized Control (AREA)
Abstract
The application provides a method and a device for calling bottom layer service, and relates to the technical field of computers. The method comprises the following steps: acquiring a first request message sent by a target business service; the first request message comprises a bottom layer service identifier; the middleware adapts to different business services and performs unified call processing on scheduling requests of the different business services; sending a second request message to a target bottom layer service corresponding to the bottom layer service identifier; the second request message is used for calling the data content required by the target business service from the target bottom layer service. The method and the device for calling the bottom layer service can improve the calling efficiency of the bottom layer service.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for calling a bottom layer service.
Background
Multi-platform development refers to the development of applications on different operating systems and devices to ensure that applications run well on multiple platforms. Multi-platform development aims to minimize repetitive development efforts and provide a consistent user experience by sharing code and resources. It can help the developer to reduce development costs and time while covering multiple markets and user groups simultaneously.
In actual project development, the business service platform acquires required data content from a corresponding underlying service (third party service) by calling methods of various third party interfaces. And calling each business service platform, and mutually independent.
However, if many items call these same third party interfaces, then the response of these interfaces must be adapted in each item, resulting in code redundancy and poor maintenance.
Disclosure of Invention
The application provides a method and a device for calling bottom services, which are used for solving the defect of complex calling of the bottom services in the prior art and realizing efficient calling of the bottom services.
In a first aspect, an embodiment of the present application provides a method for calling an underlying service, including:
acquiring a first request message sent by a target business service; the first request message comprises a bottom layer service identifier; the middleware adapts to different business services and performs unified call processing on scheduling requests of the different business services;
sending a second request message to a target bottom layer service corresponding to the bottom layer service identifier; the second request message is used for calling the data content required by the target business service from the target bottom layer service.
In one embodiment, the underlying service invocation method further comprises:
acquiring data content synchronously returned by the target bottom layer service;
and sending the data content to the target business service.
In one embodiment, the underlying service invocation method further comprises:
acquiring a first response message sent by the target bottom layer service; the first response message is used for representing that the target bottom layer service accepts the asynchronous call request of the target business service and provides data content required by the target business service in an asynchronous return mode;
and sending the first response message to the target business service.
In one embodiment, the first request message further includes a callback address parameter;
the bottom layer service calling method further comprises the following steps:
acquiring data content asynchronously returned by the target bottom layer service;
and transmitting the data content to the target business service based on the callback address parameter.
In one embodiment, the underlying service invocation method further comprises:
acquiring a second response message sent by the target bottom layer service; the second response message comprises a task identifier;
sending a third response message to the target business service; the third response message is used for representing that the target bottom layer service accepts the timing pull call request of the target business service and provides the data content required by the target business service in a timing pull mode.
In one embodiment, the first request message further includes a callback address parameter;
the bottom layer service calling method further comprises the following steps:
and sending the task identifier and the callback address parameter to a distributed task scheduling platform, wherein the distributed task scheduling platform is used for scheduling data content required by the target business service from the target bottom layer service based on the task identifier and sending the data content to the target business service based on the callback address parameter.
In a second aspect, an embodiment of the present application provides an underlying service calling device, including:
the acquisition module is used for acquiring a first request message sent by the target business service; the first request message comprises a bottom layer service identifier; the middleware adapts to different business services and performs unified call processing on scheduling requests of the different business services;
the sending module is used for sending a second request message to the target bottom layer service corresponding to the bottom layer service identifier; the second request message is used for calling the data content required by the target business service from the target bottom layer service.
In a third aspect, the application also provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of the first aspect when executing the program.
In a fourth aspect, the application also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method according to the first aspect.
In a fifth aspect, the application also provides a computer program product comprising a computer program which, when executed by a processor, implements the method of the first aspect.
According to the method and the device for calling the bottom layer service, different business service dispatching requests are uniformly dispatched in a mode of adding the middleware between business service and the bottom layer service, the return of the calling result of the third-party interface can be efficiently adapted, the business service calling can normally receive the request result, the development amount of codes can be reduced in multi-platform development, uniform calling processing is completed, the platform business service only needs to be concerned about entering and exiting, and other processing is given to the middleware for processing, so that the calling efficiency of the bottom layer service is improved.
Drawings
In order to more clearly illustrate the application or the technical solutions of the prior art, the following description will briefly explain the drawings used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are some embodiments of the application, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow diagram of an underlying service invocation method provided by the present application;
FIG. 2 is a schematic flow chart of the synchronous call method provided by the application;
FIG. 3 is a flow diagram of an asynchronous call method provided by the present application;
FIG. 4 is a schematic flow chart of a timing pull calling method provided by the application;
FIG. 5 is a schematic diagram of the structure of the underlying service invocation apparatus provided by the present application;
fig. 6 is a schematic structural diagram of an electronic device provided by the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Fig. 1 is a flow chart of a method for invoking an underlying service according to an embodiment of the present application. Referring to fig. 1, an embodiment of the present application provides a method for invoking an underlying service, where an execution body of the method may be an electronic device, for example, may be an invoker, and the method is applied to middleware, and may include:
step 110, obtaining a first request message sent by a target business service; the first request message contains a bottom layer service identifier; the middleware adapts to different business services and performs unified call processing on scheduling requests of the different business services;
step 120, sending a second request message to the target bottom layer service corresponding to the bottom layer service identifier; the second request message is used for calling the data content required by the target business service from the target bottom layer service.
As shown in fig. 2, the bottom layer call is made based on three layers, namely, business service layer (each platform), intermediate encapsulation layer (middleware), and bottom layer service layer (third party service layer). In step 110, when the business service layer issues a call instruction, the caller may acquire the call instruction (first request message) issued by the target business service. The first request message includes an underlying service identification that may be used to direct calls to the underlying service layer. The invoker contains middleware, can adapt to different types of business services, and performs unified invocation processing on the scheduling requests of the various types of business services.
In step 120, the middleware dispatches the first request message sent by the target business service, and sends calling information (second request message) to the corresponding target bottom layer service according to the bottom layer service identifier in the first request message. The second request message, which may be the same as the first request message or may be different, may be used to invoke the data content required by the target underlying service to the target business service.
According to the method for calling the bottom layer service, different business service dispatching requests are uniformly dispatched in a mode of adding middleware between business service and the bottom layer service, the return of a third party interface calling result can be efficiently adapted, the business service calling can normally receive the request result, the development amount of codes can be reduced in multi-platform development, uniform calling processing is completed, platform business service only needs to be concerned about entering and exiting, and other processing is given to the middleware for processing, so that the calling efficiency of the bottom layer service is improved.
In one embodiment, the underlying service invocation method further comprises:
acquiring data content synchronously returned by a target bottom layer service;
the data content is sent to the target business service.
After the caller sends a call request to the target bottom layer service based on the middleware, the caller can acquire the data content synchronously returned by the target bottom layer service based on the call request, and then sends the data content to the target business service, so that timely request return is completed.
As shown in fig. 2, the service platform firstly calls the middle packaging layer through the first request information, then calls the bottom layer service (third party service) through the second request information, the bottom layer service returns call result data to the middle packaging layer, and the middle packaging layer finally returns a result to the service platform.
According to the bottom layer service calling method provided by the embodiment of the application, the synchronous calling condition is uniformly scheduled in a mode of adding the middleware between the business service and the bottom layer service, the return of the calling result of the third party interface can be efficiently adapted, and the business service calling can be ensured to normally receive the request result.
In one embodiment, the underlying service invocation method further comprises:
acquiring a first response message sent by a target bottom layer service; the first response message is used for representing that the target bottom layer service receives an asynchronous call request of the target business service and providing data content required by the target business service in an asynchronous return mode;
the first response message is sent to the target business service.
For service calls with longer processing times, call result data may not be returned instantaneously. The target underlying service may first send a first response message to the middleware after obtaining the second request message. The first response message may be used to indicate that the target underlying service has accepted the asynchronous call request for the target business service, and then may provide the data content required by the target business service by means of asynchronous return. The middleware may obtain a first response message sent by the target underlying service and then send the first response message to the target business service.
According to the method for calling the bottom layer service, provided by the embodiment of the application, the asynchronous calling condition is uniformly scheduled in a mode of adding the middleware between the service and the bottom layer service, so that when the calling data cannot be returned immediately, the receiving request message can be returned first, and the smooth implementation of the calling step of the bottom layer service is ensured.
In one embodiment, the first request message further includes a callback address parameter;
the bottom layer service calling method further comprises the following steps:
acquiring data content asynchronously returned by a target bottom layer service;
and transmitting the data content to the target business service based on the callback address parameter.
When the call result data cannot be returned immediately, the first request message sent by the target business service can also comprise a callback address parameter. After the target bottom layer service data processing is completed, the caller can acquire the data content asynchronously returned by the target bottom layer service and send the data content to the target business service based on the callback address parameter.
As shown in fig. 3, the business service platform may call an encapsulation middle layer (middleware) based on the first request information, the encapsulation middle layer may call an underlying service (third party service) based on the second request information, the underlying service responds to the encapsulation middle layer based on the first response information, and the encapsulation middle layer responds to the business service platform based on the first response information. After the data processing of the bottom layer service layer is completed, the caller can call back the data result to the business service platform according to the callback address callback.
According to the method for calling the bottom layer service, provided by the embodiment of the application, the asynchronous calling condition is uniformly scheduled in a mode of adding the middleware between the service and the bottom layer service, when the calling data cannot be returned immediately, the request receiving message is returned first, and then the processing result is returned through the callback address parameter after the data processing is completed, so that the smooth implementation of the calling step of the bottom layer service is ensured, the development quantity of codes can be reduced in multi-platform development, the uniform calling processing is completed, the platform service only needs to care about the entering and the exiting of the calling, and other processing is submitted to the middleware for processing, so that the calling efficiency of the bottom layer service is improved.
In one embodiment, the underlying service invocation method further comprises:
acquiring a second response message sent by the target bottom layer service; the second response message comprises a task identifier;
sending a third response message to the target business service; the third response message is used for representing that the target bottom layer service receives the timing pull call request of the target business service and providing the data content required by the target business service in a timing pull mode.
In the process of calling the bottom layer service, interfaces with similar task properties exist, and the result is not returned by the horse. The middleware may first obtain a second response message sent by the target underlying service. The second response message contains a task identity.
The middleware may send a third response message to the target traffic service, which may be determined based on the second response message. The third response message may indicate that the target bottom layer accepts the timing pull call request of the target business service, and may provide the data content required by the target business service in a timing pull manner.
According to the method for calling the bottom layer service, provided by the embodiment of the application, the condition of timing pull calling is uniformly scheduled in a mode of adding the middleware between the service and the bottom layer service, so that when the calling data cannot be returned immediately, the task identifier is generated first, and the receiving request message is returned, thereby ensuring the smooth implementation of the calling step of the bottom layer service.
In one embodiment, the first request message further includes a callback address parameter;
the bottom layer service calling method further comprises the following steps:
and sending the task identifier and the callback address parameter to a distributed task scheduling platform, wherein the distributed task scheduling platform is used for scheduling data content required by the target business service from the target bottom layer service based on the task identifier and sending the data content to the target business service based on the callback address parameter.
The first request information sent by the target service may further include a callback address parameter, which is used to obtain the data content processed by the target underlying service. And when the middleware sends a third response message to the target business service, the task identifier is added to the task monitoring at the same time, and the callback address parameter is sent to the distributed task scheduling platform. The distributed task scheduling platform may schedule the queued tasks, for example, retrieving data content required for the target business service from the target underlying service based on the task identification, and then sending the data content to the target business service based on the callback address parameters.
As shown in fig. 4, the service platform firstly sends a first request message to call the middle encapsulation layer (middleware), the middle encapsulation layer calls the bottom layer service based on a second request message, the bottom layer service returns a task identifier taskId to the middle encapsulation layer, and the middle encapsulation layer responds to the service layer and simultaneously puts the taskId into job monitoring, and then queues up for processing. After executing the distributed task scheduling platform (e.g., xxl-job) timing tasks, the caller invokes the underlying service according to the taskId, which returns the task processing results to the xxl-job caller. If xxl-job obtains the result, the caller can push the result to the business service through callback address parameter callback, if no result exists, the caller can continue waiting for the next time of timing task scheduling, and the bottom service pulling result is called again.
According to the method for calling the bottom layer service, provided by the embodiment of the application, the condition of timing pull calling is uniformly scheduled in a mode of adding the middleware between the service and the bottom layer service, the task identifier is generated first when the calling data cannot be returned immediately, and then the task result is processed through the distributed task scheduling platform, so that smooth implementation of the calling step of the bottom layer service is ensured, the development quantity of codes can be reduced in multi-platform development, uniform calling processing is completed, the platform service only needs to care about the entering and the exiting of the parameters, and other processing is submitted to the middleware for processing, so that the calling efficiency of the bottom layer service is improved.
The following describes the bottom service calling device provided by the present application, and the bottom service calling device described below and the bottom service calling method described above can be referred to correspondingly.
Fig. 5 is a schematic structural diagram of an underlying service calling device according to an embodiment of the present application. Referring to fig. 5, an apparatus for invoking an underlying service provided in an embodiment of the present application may include:
an obtaining module 510, configured to obtain a first request message sent by a target service; the first request message comprises a bottom layer service identifier; the middleware adapts to different business services and performs unified call processing on scheduling requests of the different business services;
a sending module 520, configured to send a second request message to a target underlying service corresponding to the underlying service identifier; the second request message is used for calling the data content required by the target business service from the target bottom layer service.
According to the bottom layer service calling device provided by the embodiment of the application, different business service scheduling requests are uniformly scheduled in a mode of adding the middleware between the business service and the bottom layer service, the return of the calling result of the third party interface can be efficiently adapted, the business service calling can normally receive the request result, the development amount of codes can be reduced in multi-platform development, uniform calling processing is completed, the platform business service only needs to be concerned about entering and exiting, and other processing is given to the middleware for processing, so that the bottom layer service calling efficiency is improved.
Fig. 6 illustrates a physical schematic diagram of an electronic device, as shown in fig. 6, which may include: processor 610, communication interface (Communications Interface) 620, memory 630, and communication bus 640, wherein processor 610, communication interface 620, and memory 630 communicate with each other via communication bus 640. The processor 610 may call logic instructions in the memory 630 to perform underlying service invocation methods including, for example:
acquiring a first request message sent by a target business service; the first request message comprises a bottom layer service identifier; the middleware adapts to different business services and performs unified call processing on scheduling requests of the different business services;
sending a second request message to a target bottom layer service corresponding to the bottom layer service identifier; the second request message is used for calling the data content required by the target business service from the target bottom layer service.
Further, the logic instructions in the memory 630 may be implemented in the form of software functional units and stored in a computer-readable storage medium when sold or used as a stand-alone product. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In another aspect, the present application also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements steps for performing the underlying service invocation method provided by the above methods, for example, including:
acquiring a first request message sent by a target business service; the first request message comprises a bottom layer service identifier; the middleware adapts to different business services and performs unified call processing on scheduling requests of the different business services;
sending a second request message to a target bottom layer service corresponding to the bottom layer service identifier; the second request message is used for calling the data content required by the target business service from the target bottom layer service.
In yet another aspect, the present application also provides a computer program product, where the computer program product includes a computer program, where the computer program can be stored on a non-transitory computer readable storage medium, where the computer program when executed by a processor can perform the steps of the underlying service invocation method provided by the above methods, for example, including:
acquiring a first request message sent by a target business service; the first request message comprises a bottom layer service identifier; the middleware adapts to different business services and performs unified call processing on scheduling requests of the different business services;
sending a second request message to a target bottom layer service corresponding to the bottom layer service identifier; the second request message is used for calling the data content required by the target business service from the target bottom layer service.
The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present application without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.
In addition, it should be noted that: the terms "first," "second," and the like in embodiments of the present application are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the "first" and "second" distinguishing between objects generally are not limited in number to the extent that the first object may, for example, be one or more.
In the embodiment of the application, the term "and/or" describes the association relation of the association objects, which means that three relations can exist, for example, a and/or B can be expressed as follows: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
In the embodiment of the application, the "determining B based on a" means that a is considered when determining B. Not limited to "B can be determined based on A alone", it should also include: "B based on A and C", "B based on A, C and E", "C based on A, further B based on C", etc. Additionally, a may be included as a condition for determining B, for example, "when a satisfies a first condition, B is determined using a first method"; for another example, "when a satisfies the second condition, B" is determined, etc.; for another example, "when a satisfies the third condition, B" is determined based on the first parameter, and the like. Of course, a may be a condition in which a is a factor for determining B, for example, "when a satisfies the first condition, C is determined using the first method, and B is further determined based on C", or the like.
The term "plurality" in embodiments of the present application means two or more, and other adjectives are similar.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the application 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 technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims (10)
1. An underlying service calling method, which is applied to middleware, comprises the following steps:
acquiring a first request message sent by a target business service; the first request message comprises a bottom layer service identifier; the middleware adapts to different business services and performs unified call processing on scheduling requests of the different business services;
sending a second request message to a target bottom layer service corresponding to the bottom layer service identifier; the second request message is used for calling the data content required by the target business service from the target bottom layer service.
2. The underlying service invocation method of claim 1, wherein the method further comprises:
acquiring data content synchronously returned by the target bottom layer service;
and sending the data content to the target business service.
3. The underlying service invocation method of claim 1, wherein the method further comprises:
acquiring a first response message sent by the target bottom layer service; the first response message is used for representing that the target bottom layer service accepts the asynchronous call request of the target business service and provides data content required by the target business service in an asynchronous return mode;
and sending the first response message to the target business service.
4. The method according to claim 3, wherein the first request message further includes a callback address parameter;
the method further comprises the steps of:
acquiring data content asynchronously returned by the target bottom layer service;
and transmitting the data content to the target business service based on the callback address parameter.
5. The underlying service invocation method of claim 1, wherein the method further comprises:
acquiring a second response message sent by the target bottom layer service; the second response message comprises a task identifier;
sending a third response message to the target business service; the third response message is used for representing that the target bottom layer service accepts the timing pull call request of the target business service and provides the data content required by the target business service in a timing pull mode.
6. The method according to claim 5, wherein the first request message further includes a callback address parameter;
the method further comprises the steps of:
and sending the task identifier and the callback address parameter to a distributed task scheduling platform, wherein the distributed task scheduling platform is used for scheduling data content required by the target business service from the target bottom layer service based on the task identifier and sending the data content to the target business service based on the callback address parameter.
7. A middleware apparatus, comprising:
the acquisition module is used for acquiring a first request message sent by the target business service; the first request message comprises a bottom layer service identifier; the middleware adapts to different business services and performs unified call processing on scheduling requests of the different business services;
the sending module is used for sending a second request message to the target bottom layer service corresponding to the bottom layer service identifier; the second request message is used for calling the data content required by the target business service from the target bottom layer service.
8. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the underlying service invocation method of any of claims 1-6 when the program is executed by the processor.
9. A non-transitory computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the underlying service invocation method of any of claims 1 to 6.
10. A computer program product comprising a computer program which, when executed by a processor, implements the underlying service invocation method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311258877.6A CN117234757A (en) | 2023-09-26 | 2023-09-26 | Method and device for calling bottom layer service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311258877.6A CN117234757A (en) | 2023-09-26 | 2023-09-26 | Method and device for calling bottom layer service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117234757A true CN117234757A (en) | 2023-12-15 |
Family
ID=89087672
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311258877.6A Pending CN117234757A (en) | 2023-09-26 | 2023-09-26 | Method and device for calling bottom layer service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117234757A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118964067A (en) * | 2024-10-15 | 2024-11-15 | 数字广东网络建设有限公司 | Content page and native controller interaction method, device, equipment and medium |
-
2023
- 2023-09-26 CN CN202311258877.6A patent/CN117234757A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118964067A (en) * | 2024-10-15 | 2024-11-15 | 数字广东网络建设有限公司 | Content page and native controller interaction method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111694640B (en) | Data processing method, device, electronic equipment and storage medium | |
| CN111258741B (en) | Warehouse task execution method, distributed server cluster and computer equipment | |
| CN113703997A (en) | Bidirectional asynchronous communication middleware system integrating multiple message agents and implementation method | |
| CN111090532A (en) | Application service calling method and device, electronic equipment and computer storage medium | |
| CN113946389A (en) | Federated learning process execution optimization method, device, storage medium and program product | |
| CN111200606A (en) | Deep learning model task processing method, system, server and storage medium | |
| CN117234757A (en) | Method and device for calling bottom layer service | |
| CN114610404A (en) | Component calling method and device based on application framework and computer equipment | |
| CN108564345B (en) | Insurance platform data processing method, electronic device and computer readable storage medium | |
| WO2025139864A1 (en) | Processor resource scheduling method, device and system | |
| CN111835809B (en) | Work order message distribution method, work order message distribution device, server and storage medium | |
| CN107045452B (en) | Virtual machine scheduling method and device | |
| CN116107778B (en) | Front-end event response realization method, device, terminal equipment and readable storage medium | |
| CN107819855A (en) | A kind of message distributing method and device | |
| CN109840073B (en) | Method and device for realizing business process | |
| CN108521524B (en) | Agent collaborative task management method and device, computer equipment and storage medium | |
| CN116627615A (en) | Task processing method and device, electronic equipment and storage medium | |
| US8549537B2 (en) | Middleware bridge system and method | |
| CN115361382A (en) | Data processing method, device, equipment and storage medium based on data group | |
| CN107247621B (en) | Scheduling method and device for batch processing tasks | |
| CN119149253B (en) | Client application development platform and method based on multi-process framework | |
| CN113850466B (en) | Task dispatching method, storage medium and program product | |
| CN114115858B (en) | Transaction request forwarding processing method and device | |
| CN112463257B (en) | Application mode determining method, computing device and computer storage medium | |
| CN113127163B (en) | Model verification method, device and electronic equipment |
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 |