CN109274773B - Method, device and system for realizing remote service calling - Google Patents
Method, device and system for realizing remote service calling Download PDFInfo
- Publication number
- CN109274773B CN109274773B CN201811353782.1A CN201811353782A CN109274773B CN 109274773 B CN109274773 B CN 109274773B CN 201811353782 A CN201811353782 A CN 201811353782A CN 109274773 B CN109274773 B CN 109274773B
- Authority
- CN
- China
- Prior art keywords
- service
- information
- calling
- interface
- target server
- 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
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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- 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/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a method, a device and a system for realizing remote service calling, which are based on XML file configuration and solve the problem of code dispersion of remote service calling. The method for realizing the remote service call is applied to the client; the method comprises the following steps: configuring service calling information in an XML file form; reading an XML file, configuring, analyzing and converting the XML file into internal interface service metadata information of a system of a client; reading service metadata information, importing registration information, and converting the service metadata information into interface service information format data; reading interface service information format data, initiating a network connection request to a target server and sending service calling information, triggering the target server to call a service corresponding to the service calling information so as to obtain a calling result, and triggering the target server to return the calling result; and responding to the calling result. The method simplifies the remote service calling process.
Description
Technical Field
The present invention relates to the field of telecommunications, and in particular, to a method, an apparatus, and a system for implementing remote service invocation.
Background
The XML (eXtensible Markup language) is a simple, cross-platform, and extensible method for Markup data. Its main advantage is: complex data structures can be marked using simple text; formatted data can be conveniently obtained from xml through xslt; therefore, the definition (defined by xslt) and the display (displayed by xml) of the data type are separated, so that the service logic and the user interface can be relatively independent, and the service processing is convenient; xslt (extensible Stylesheet Language transformation) is a Language for converting xml data types, and different xml data types can be specified and defined by using an xslt processor according to different user terminals, so that the requirements of different display specifications of different terminals are met. xml is a markup language with simple operation, and an operator can customize a mark when writing xml without using a mark defined in advance in a rule like html language used by the traditional data mark, so that xml has high degree of freedom and is relatively simple to write and modify; the xml is matched with the xslt for use, so that data exchange among various different service data types can be better realized, and the data transmission is smoother. The Soap protocol uses XML statements to describe data content, and has the advantages of simplicity and easiness in reading, but the data redundancy is large, and a large number of description characters exist.
At present, the demand for data communication is increasing through network access. The trend of users to acquire information through networks is a big trend of communication development. The traditional method for analyzing the service data by utilizing the self-defined xml format document based on the http protocol to realize data transmission has the defects that the remote service calling process is complex, so that remote service calling codes are dispersed, and hard codes need to be configured in the remote service calling codes, so that the development efficiency is low.
Disclosure of Invention
The invention aims to provide a method, a device and a system for realizing remote service calling, which are used for solving one of the defects in the prior art.
In a first aspect of the embodiments of the present disclosure, a method for implementing remote service invocation is provided, which is applied to a client, where the client is configured with a plurality of connection endpoints, and each of the connection endpoints corresponds to a plurality of servers;
the method comprises the following steps:
configuring service calling information in an XML file form;
reading the XML file, checking the format, the node integrity and the data validity of the XML file, analyzing the service calling information configured by the XML file and converting the service calling information into the internal interface service metadata information of the system of the client;
reading the service metadata information, transmitting a service ID, searching a corresponding service according to the transmitted service ID, importing registration information, and converting the service metadata information into interface service information format data;
reading the interface service information format data, initiating a network connection request to a target server in a target connection endpoint according to target connection endpoint information in the imported registration information, sending the service calling information to the target server, positioning a registered remote service interface according to the service ID, transmitting request parameters, triggering the target server to call a service corresponding to the service calling information to obtain a calling result, and triggering the target server to return the calling result;
responding the calling result and converting the calling result into a uniform interface response format, or responding the calling result and configuring different response processing data.
Preferably, wherein the service invocation information is configured in the form of an XML file, comprising the steps of:
configuring interface information, Host endpoint information and Http request header information; and
defining system variables, defining token generation rules and defining interface parameter analysis rules.
Preferably, wherein the converting the service metadata information into interface service information format data comprises the steps of:
analyzing the URL parameter and the DATA parameter according to the configuration in the imported registration information and an interface parameter analysis rule, and merging the URL parameter and the DATA parameter into the input parameter;
and converting the input parameters into JSON objects.
Preferably, wherein the network connection request is initiated to the target server in the target connection endpoint according to the target connection endpoint information in the import registration information, the method includes the following steps:
determining a free target server among a plurality of said servers in said target connection endpoint using a polling algorithm.
Preferably, a network connection request is initiated to a target server in the target connection endpoint, wherein the network connection request is an HTTP connection request.
In a second aspect of the embodiments of the present disclosure, a device for implementing remote service invocation is provided, where the device is deployed at a client, and the client is configured with a plurality of connection endpoints, and each of the connection endpoints corresponds to a plurality of servers;
comprises that
A configuration module configured to configure the service invocation information in the form of an XML file;
the analysis module is configured to read the XML file, check the format, the node integrity and the data validity of the XML file, analyze the service calling information configured by the XML file and convert the service calling information into the internal interface service metadata information of the system of the client;
a service registration module configured to read the service metadata information, transmit a service ID, find a corresponding service according to the transmitted service ID, introduce registration information, and convert the service metadata information into interface service information format data;
the service calling module is configured to read the interface service information format data, initiate a network connection request to a target server in a target connection endpoint according to target connection endpoint information in the imported registration information, send the service calling information to the target server, locate a registered remote service interface according to the service ID, transmit request parameters, trigger the target server to call a service corresponding to the service calling information to obtain a calling result, and trigger the target server to return the calling result;
and the service response module is configured to respond to the calling result and convert the calling result into a uniform interface response format, or respond to the calling result and configure different response processing data.
Preferably, wherein the service invocation information is configured in the form of an XML file, comprising:
configuring interface information, Host endpoint information and Http request header information; and
defining system variables, defining token generation rules and defining interface parameter analysis rules.
Preferably, wherein converting the service metadata information into interface service information format data comprises:
analyzing the URL parameter and the DATA parameter according to the configuration in the imported registration information and an interface parameter analysis rule, and merging the URL parameter and the DATA parameter into the input parameter;
and converting the input parameters into JSON objects.
Preferably, initiating a network connection request to a target server in the target connection endpoint according to the target connection endpoint information in the import registration information, including:
determining a free target server among a plurality of said servers in said target connection endpoint using a polling algorithm.
Preferably, a network connection request is initiated to a target server in the target connection endpoint, wherein the network connection request is an HTTP connection request.
A third aspect of the embodiments of the present disclosure provides a remote service invocation system, including the above apparatus deployed at a client for implementing remote service invocation.
The invention has the beneficial effects that:
the remote interface is configured based on XML file configuration, a unified remote calling API is provided, and the problems that remote service calling codes are dispersed, configuration hard codes are in the codes, and development efficiency is low are solved. Compared with most of the remote service calling methods used at present, the method simplifies the remote service calling process, is flexible in configuration and greatly improves the development efficiency.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a logical block diagram of a first embodiment of the present invention;
FIG. 2 is a flow chart of a first embodiment of the present invention;
fig. 3 is a block diagram of a second embodiment of the present invention.
Detailed Description
In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present invention by illustrating examples thereof.
The technical solutions of the embodiments of the present invention will be described below with reference to the accompanying drawings.
As shown in fig. 1 and fig. 2, the present disclosure provides a method for implementing remote service invocation, which is applied to a client, where the client is configured with a plurality of connection endpoints, and each of the connection endpoints corresponds to a plurality of servers;
the method comprises the following steps:
s101, importing a remote interface service component, e.g.
And (3) introducing Maven engineering: xml file addition the following dependencies
S102, configuring service calling information in an XML file form; the method comprises the following steps:
configuring interface information, Host endpoint information and Http request header information; and defining system variables, defining token generation rules and defining interface parameter analysis rules. The XML file text of the example follows.
Description of configuration parameters:
http-endpoint node
Properties
ID, service address node ID, globally unique.
Service-addr is a path.
Type is Type.
Host sub-point:
properties
address: an address.
port: a port.
appKey: unique identification of applications
secreteKey: security code
livemode: mode(s)
scope: scope of action
http-header node
Properties
ID, service address node ID, globally unique.
charset: coding type.
Header sub-point:
properties
name: a header key.
An Import node: interface to be imported
Properties
Service-ID, globally unique.
Api is the interface name issued by the scoring system.
Endpoint-ref service address configuration reference ID.
Http request Header information configuration reference ID.
request-type is request mode (post, get), and the post is defaulted.
Child node
URL-param-a parameter configuration that needs to be added to the URL.
data-param-a parameter configuration that needs to be added to the request parameters.
Note that: the value supports the SpingEL expression and needs to be configured in the request parameter, such as
Key also supports the SpingEL expression: finding the corresponding node and adding the corresponding field according to the configured EL expression (the node to be added must exist)
Specifically, the following description is provided:
URL-param configuration of parameters that need to be added to the URL.
As in the example above:
<url-param name＝"accesstoken">#accessToken</url-param>
in the interface specification corresponding to the integral system release, the url part:
https://test.com/v1/integral/addaccessToken＝xxxxxxxxxxxx
wherein the value corresponding to the name attribute in the url-name node is accesstaken in the url (note that the case and the case are consistent with each other in the url).
And # accessoken indicates that a system variable accessoken is quoted, the system automatically identifies, and generates the accessoken according to host configuration (appKey, secret key, scope) in endpoint-ref quote configuration and the value of the current import node attribute api.
Data-param configuration of parameters that need to be added to the request parameters.
As in the example above:
<data-param name＝"appid">#appKey</data-param>
<data-param name＝"livemode">#livemode</data-param>
in the interface specification corresponding to the integral system release, the text part is as follows:
Appid,livemode
the parameters in the request parameters can be configured by the node, and after configuration, the calling program does not need to be configured.
And the value corresponding to the name attribute in the url-name node is the key in the interface specification request parameter.
3.url-param，data-param:
The value supports the SpingEL expression, and needs to be configured in the request parameter.
Such as:
<url-param name＝"token">['token']</url-param>
key EL expression
<data-param name＝"['tag']['userflag']">2</data-param>
4.Header-ref:
http request header information references ID, if not set using component defaults:
namely: Content-Type application/json, coded as UTF-8
In a detailed example, the remote service interface configuration file is configured according to the convention during configuration so as to import the score system related interface configuration file: xml is described as follows:
adding an integral interface: the interface specification issued by the scoring system is as follows:
POST (POST position transfer) request mode
| Openid | User ID |
| devOpenid | Device unique label |
| Appid | Service ID |
| Integral | Integration |
| remarks | Remarks for note |
| livemode | Version(s) |
| ordercode | Running water number |
S103, reading the XML file, checking the XML file format, the node integrity and the data validity, analyzing the service calling information configured by the XML file, converting the service calling information into the internal interface service metadata information of the system of the client, and storing the internal interface service metadata information in an internal memory for the next step.
S104, reading the service metadata information, transmitting a service ID, searching a corresponding service according to the transmitted service ID, importing registration information, and converting the service metadata information into interface service information format data; for example, the URL parameter and the DATA parameter are parsed according to the configuration in the imported registration information and the interface parameter parsing rule, and are merged into the input parameter, and the input parameter is converted into a JSON object. And the data is stored in the memory and used by the service calling module.
S105, reading the interface service information format data, initiating a network connection request to a target server in the target connection endpoint according to target connection endpoint information in the imported registration information, for example, using a polling algorithm, determining an idle target server in a plurality of servers in the target connection endpoint, for example, the network connection request is an HTTP connection request, sending the service invocation information to the target server, locating a registered remote service interface according to the service ID, importing a request parameter, triggering the target server to invoke a service corresponding to the service invocation information, so as to obtain an invocation result, and triggering the target server to return the invocation result. The method shields the differences of different service interfaces, request modes, parameter formats, protocol types and the like, and ensures that the use is simpler and the development efficiency is higher.
S106, responding to the calling result and converting the calling result into a uniform interface response format, or responding to the calling result and configuring different response processing data (expanding development), thereby shielding the difference of the response data format. Such as receiving the response of the target server's system and converting to a String object and returning the object to the application.
As shown in fig. 3, the present disclosure further provides a device for implementing remote service invocation, which is deployed at a client, where the client is configured with a plurality of connection endpoints, and each of the connection endpoints corresponds to a plurality of servers;
comprises that
A configuration module 001 configured to configure service invocation information in the form of an XML file;
the parsing module 002 is configured to read the XML file, check the format, the node integrity and the data validity of the XML file, parse the service invocation information configured by the XML file and convert the service invocation information into the internal interface service metadata information of the system of the client;
the service registration module 003 is configured to read the service metadata information, introduce a service ID, find a corresponding service according to the introduced service ID, introduce registration information, and convert the service metadata information into interface service information format data;
a service calling module 004 configured to read the interface service information format data, initiate a network connection request to a target server in a target connection endpoint according to target connection endpoint information in the imported registration information, send the service calling information to the target server, locate a registered remote service interface according to the service ID, transmit a request parameter, trigger the target server to call a service corresponding to the service calling information to obtain a calling result, and trigger the target server to return the calling result;
and a service response module 005 configured to respond to the call result and convert it into a uniform interface response format, or configure different response processing data in response to the call result.
For more detailed descriptions of the interaction among the modules, reference may be made to the description of the method embodiment, and those skilled in the art may easily and unambiguously deduce this description, and details are not described below.
The present disclosure also provides a remote service invoking system, which includes the above device deployed at the client for implementing remote service invoking.
The invention has the beneficial effects that:
the remote interface is configured based on XML file configuration, a unified remote calling API is provided, and the problems that remote service calling codes are dispersed, configuration hard codes are in the codes, and development efficiency is low are solved. Compared with most of the remote service calling methods used at present, the method simplifies the remote service calling process, is flexible in configuration and greatly improves the development efficiency.
Although the present invention has been described herein with reference to the illustrated embodiments thereof, which are intended to be preferred embodiments of the present invention, it is to be understood that the invention is not limited thereto, and that numerous other modifications and embodiments can be devised by those skilled in the art that will fall within the spirit and scope of the principles of this disclosure.
Claims (11)
1. A method for realizing remote service call is applied to a client, wherein the client is provided with a plurality of connection end points, and each connection end point corresponds to a plurality of servers;
characterized in that the method comprises the following steps:
configuring service calling information in an XML file form;
reading the XML file, checking the format, the node integrity and the data validity of the XML file, analyzing the service calling information configured by the XML file and converting the service calling information into the internal interface service metadata information of the system of the client;
reading the service metadata information, transmitting a service ID, searching a corresponding service according to the transmitted service ID, importing registration information, and converting the service metadata information into interface service information format data;
reading the interface service information format data, initiating a network connection request to a target server in a target connection endpoint according to target connection endpoint information in the imported registration information, sending the service calling information to the target server, positioning a registered remote service interface according to the service ID, transmitting request parameters, triggering the target server to call a service corresponding to the service calling information to obtain a calling result, and triggering the target server to return the calling result;
responding the calling result and converting the calling result into a uniform interface response format, or responding the calling result and configuring different response processing data.
2. The method of claim 1, wherein configuring the service invocation information in the form of an XML file comprises the steps of:
configuring interface information, Host endpoint information and Http request header information; and
defining system variables, defining token generation rules and defining interface parameter analysis rules.
3. The method of claim 2, wherein converting the service metadata information into interface service information format data comprises:
analyzing the URL parameter and the DATA parameter according to the configuration in the imported registration information and an interface parameter analysis rule, and merging the URL parameter and the DATA parameter into the input parameter;
and converting the input parameters into JSON objects.
4. The method of claim 1, wherein initiating a network connection request to a target server in the target connection endpoint according to the target connection endpoint information in the import registration information comprises:
determining a free target server among a plurality of said servers in said target connection endpoint using a polling algorithm.
5. The method of claim 4, wherein a network connection request is initiated to a target server in the target connection endpoint, wherein the network connection request is an HTTP connection request.
6. A device for realizing remote service call is distributed to a client, the client is provided with a plurality of connection end points, and each connection end point corresponds to a plurality of servers;
which is characterized by comprising
A configuration module configured to configure the service invocation information in the form of an XML file;
the analysis module is configured to read the XML file, check the format, the node integrity and the data validity of the XML file, analyze the service calling information configured by the XML file and convert the service calling information into the internal interface service metadata information of the system of the client;
a service registration module configured to read the service metadata information, transmit a service ID, find a corresponding service according to the transmitted service ID, introduce registration information, and convert the service metadata information into interface service information format data;
the service calling module is configured to read the interface service information format data, initiate a network connection request to a target server in a target connection endpoint according to target connection endpoint information in the imported registration information, send the service calling information to the target server, locate a registered remote service interface according to the service ID, transmit request parameters, trigger the target server to call a service corresponding to the service calling information to obtain a calling result, and trigger the target server to return the calling result;
and the service response module is configured to respond to the calling result and convert the calling result into a uniform interface response format, or respond to the calling result and configure different response processing data.
7. The apparatus for implementing remote service invocation according to claim 6, wherein the service invocation information is configured in the form of an XML file, including:
configuring interface information, Host endpoint information and Http request header information; and
defining system variables, defining token generation rules and defining interface parameter analysis rules.
8. The apparatus of claim 7, wherein converting the service metadata information into interface service information format data comprises:
analyzing the URL parameter and the DATA parameter according to the configuration in the imported registration information and an interface parameter analysis rule, and merging the URL parameter and the DATA parameter into the input parameter;
and converting the input parameters into JSON objects.
9. The apparatus for implementing remote service invocation according to claim 6, wherein the initiating a network connection request to a target server in a target connection endpoint according to the target connection endpoint information in the import registration information comprises:
determining a free target server among a plurality of said servers in said target connection endpoint using a polling algorithm.
10. The apparatus of claim 9, wherein a network connection request is initiated to a target server in the target connection endpoint, wherein the network connection request is an HTTP connection request.
11. A remote service invocation system, characterized in that it comprises means for implementing a remote service invocation according to any one of claims 6 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811353782.1A CN109274773B (en) | 2018-11-14 | 2018-11-14 | Method, device and system for realizing remote service calling |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811353782.1A CN109274773B (en) | 2018-11-14 | 2018-11-14 | Method, device and system for realizing remote service calling |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109274773A CN109274773A (en) | 2019-01-25 |
| CN109274773B true CN109274773B (en) | 2021-01-26 |
Family
ID=65189683
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811353782.1A Active CN109274773B (en) | 2018-11-14 | 2018-11-14 | Method, device and system for realizing remote service calling |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109274773B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109818959B (en) * | 2019-01-28 | 2021-05-28 | 心动网络股份有限公司 | Remote service communication method, server and system |
| CN111131414B (en) * | 2019-12-11 | 2022-05-24 | 拉扎斯网络科技（上海）有限公司 | Back-end platform, service calling method, first service module and server |
| CN111010438B (en) * | 2019-12-13 | 2022-11-11 | 北京达佳互联信息技术有限公司 | Remote procedure calling method, device, server and storage medium |
| CN112199219A (en) * | 2020-11-17 | 2021-01-08 | 南开大学 | Cross-language operation remote calling method |
| CN112416457A (en) * | 2020-11-19 | 2021-02-26 | 中国建设银行股份有限公司 | Interface configuration file generation method and device |
| CN112769812A (en) * | 2020-12-31 | 2021-05-07 | 天津浪淘科技股份有限公司 | Service architecture and method based on ESB |
| CN113190513A (en) * | 2021-05-14 | 2021-07-30 | 广联达科技股份有限公司 | Data integration system and method |
| CN114610416A (en) * | 2022-03-24 | 2022-06-10 | 中国银行股份有限公司 | Data processing method and device based on configuration parameters |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101556683A (en) * | 2009-05-21 | 2009-10-14 | 中国建设银行股份有限公司 | Financial service system and implementation method |
| CN101923465A (en) * | 2010-06-25 | 2010-12-22 | 深圳创维－Rgb电子有限公司 | Embedded application-oriented scalable web service system |
| CN102438048A (en) * | 2011-12-15 | 2012-05-02 | 北京新媒传信科技有限公司 | Method and system for calling remote service from Internet |
| CN102567026A (en) * | 2011-12-28 | 2012-07-11 | 用友软件股份有限公司 | Mobile application constructing system and method |
| CN103235718A (en) * | 2013-03-28 | 2013-08-07 | 迈普通信技术股份有限公司 | Method and device for generating remote procedure call (RPC) code |
| CN103294455A (en) * | 2012-02-27 | 2013-09-11 | 杭州勒卡斯广告策划有限公司 | Software service implementation method and system, as well as Java platform |
| CN104426871A (en) * | 2013-08-29 | 2015-03-18 | 中兴通讯股份有限公司 | Method and device for realizing remote calling |
| CN105307019A (en) * | 2015-10-28 | 2016-02-03 | 四川长虹电器股份有限公司 | Function scheduling method for digital television receiver |
| CN107346320A (en) * | 2016-05-06 | 2017-11-14 | 北京神州泰岳软件股份有限公司 | A kind of data calling method and device |
| CN107707644A (en) * | 2017-09-27 | 2018-02-16 | 北京趣拿软件科技有限公司 | Processing method, device, storage medium, processor and the terminal of request message |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8495204B2 (en) * | 2006-07-06 | 2013-07-23 | Visible Measures Corp. | Remote invocation mechanism for logging |
| US9515999B2 (en) * | 2011-12-21 | 2016-12-06 | Ssh Communications Security Oyj | Automated access, key, certificate, and credential management |
-
2018
- 2018-11-14 CN CN201811353782.1A patent/CN109274773B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101556683A (en) * | 2009-05-21 | 2009-10-14 | 中国建设银行股份有限公司 | Financial service system and implementation method |
| CN101923465A (en) * | 2010-06-25 | 2010-12-22 | 深圳创维－Rgb电子有限公司 | Embedded application-oriented scalable web service system |
| CN102438048A (en) * | 2011-12-15 | 2012-05-02 | 北京新媒传信科技有限公司 | Method and system for calling remote service from Internet |
| CN102567026A (en) * | 2011-12-28 | 2012-07-11 | 用友软件股份有限公司 | Mobile application constructing system and method |
| CN103294455A (en) * | 2012-02-27 | 2013-09-11 | 杭州勒卡斯广告策划有限公司 | Software service implementation method and system, as well as Java platform |
| CN103235718A (en) * | 2013-03-28 | 2013-08-07 | 迈普通信技术股份有限公司 | Method and device for generating remote procedure call (RPC) code |
| CN104426871A (en) * | 2013-08-29 | 2015-03-18 | 中兴通讯股份有限公司 | Method and device for realizing remote calling |
| CN105307019A (en) * | 2015-10-28 | 2016-02-03 | 四川长虹电器股份有限公司 | Function scheduling method for digital television receiver |
| CN107346320A (en) * | 2016-05-06 | 2017-11-14 | 北京神州泰岳软件股份有限公司 | A kind of data calling method and device |
| CN107707644A (en) * | 2017-09-27 | 2018-02-16 | 北京趣拿软件科技有限公司 | Processing method, device, storage medium, processor and the terminal of request message |
Non-Patent Citations (1)
| Title |
|---|
| 面向服务的远程方法调用中间件设计和实现;陈海山,文登敏;《成都信息工程学院学报》;20060228(第1期);第66-69页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109274773A (en) | 2019-01-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109274773B (en) | Method, device and system for realizing remote service calling | |
| CN107835178B (en) | Multi-protocol service communication method and device and electronic equipment | |
| US7584499B2 (en) | Policy algebra and compatibility model | |
| CN111600909A (en) | Data processing method, device, protocol conversion equipment and storage medium | |
| CN102694701B (en) | Message based method of testing and system | |
| US20180137184A1 (en) | Sql interceptor for use with third party data analytics packages | |
| CN108337236A (en) | A kind of gRPC call methods and device based on Protobuf and HTTP/1.1 | |
| US20120246334A1 (en) | Unified web service uri builder and verification | |
| CN114500690B (en) | Interface data processing method and device, electronic equipment and storage medium | |
| CN112187558A (en) | Data verification method and device and electronic equipment | |
| US11263542B2 (en) | Technologies for auto discover and connect to a rest interface | |
| CN115408169A (en) | Remote procedure calling method, device, equipment and readable storage medium | |
| CN110377273B (en) | Data processing method, device, medium and electronic equipment | |
| CN112417016B (en) | Data exchange method, system, equipment and storage medium | |
| CN115269228A (en) | Data adaptive transmission method, device, equipment and medium | |
| CN111783006B (en) | Page generation method and device, electronic equipment and computer readable medium | |
| CN113918245A (en) | Data calling method, device, equipment and computer readable storage medium | |
| CN113992641A (en) | Data processing method, device, equipment and storage medium | |
| CN107332891B (en) | HTTP request processing method, server and client | |
| CN113760343A (en) | Method and device for processing service request | |
| CN116483483B (en) | Data query method and device and electronic equipment | |
| CN112650601B (en) | Method, apparatus, device, storage medium, and program for opening applet across hosts | |
| US7523175B1 (en) | Programmatic interface to network device operating system | |
| CN115865898B (en) | Method, device, equipment and medium for processing data information among multiple service systems | |
| Moussa et al. | XML Schema-Based Minification for Communication of Security Information and Event Management (SIEM) Systems in Cloud Environments |
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 |