CN110708362B - Call relation determining method and device, storage medium and electronic equipment - Google Patents
Call relation determining method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN110708362B CN110708362B CN201910885680.2A CN201910885680A CN110708362B CN 110708362 B CN110708362 B CN 110708362B CN 201910885680 A CN201910885680 A CN 201910885680A CN 110708362 B CN110708362 B CN 110708362B
- Authority
- CN
- China
- Prior art keywords
- application
- service
- registration information
- information
- subscription
- 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/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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- 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/133—Protocols for remote procedure calls [RPC]
-
- 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/56—Provisioning of proxy services
- H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/544—Remote
Abstract
The application discloses a call relation determining method, a call relation determining device, a storage medium and electronic equipment, and relates to a distributed scheduling technology. The specific scheme comprises the following steps: acquiring communication information between a registration center and at least one server connected with the registration center; for each registration information, determining subscription information for subscribing the registration information; determining the application name of a service provider sending the registration information according to the registration information, and determining the application name of a service consumer subscribing the registration information according to subscription information subscribing the registration information; determining and recording a calling relation according to a subscription relation between registration information and the subscription information; and issuing the calling relation to the registry so that the registry provides a calling interface capable of acquiring the calling relation. The method and the system can determine the calling relationship between the service consumption end and the service providing end, and enable the registry to provide a calling interface capable of acquiring the calling relationship.
Description
Technical Field
The present application relates to a distributed scheduling technology, and in particular, to a method, an apparatus, a storage medium, and an electronic device for determining a call relationship.
Background
In the distributed technology, the dispatch between the service provider at the downstream and the service consumer at the upstream is completed through the registry. The service provider sends registration information to the registration center, the service consumer sends subscription information to the new registration center, and the registration center schedules the subscription behavior of the service consumer to the service provider.
In practical application, the call relationship between the service consumption end and the service providing end is often required to be obtained, and in the prior art, the registration center cannot directly provide the call relationship between the service consumption end and the service providing end.
Disclosure of Invention
In view of the above, a primary object of the present application is to provide a call relation determining method, which can determine a call relation between a service consumer and a service provider, and enable a registry to provide a call interface capable of obtaining the call relation.
In order to achieve the purpose, the technical scheme provided by the application is as follows:
in a first aspect, an embodiment of the present application provides a method for determining a call relation, including the following steps:
acquiring communication information between a registration center and at least one server connected with the registration center; the communication information comprises registration information sent by a service provider and subscription information sent by a service consumer;
for at least one piece of the registration information, determining subscription information for subscribing the registration information; the subscription information is used for describing a subscription relationship between the registration information and the subscription information;
determining the application name of a service provider sending the registration information according to the registration information, and determining the application name of a service consumer subscribing the registration information according to subscription information subscribing the registration information;
determining a calling relationship between service provider application and service consumer application according to the subscription relationship between the registration information and the subscription information, and recording the calling relationship by using the application name of the service provider and the application name of the service consumer;
and issuing the calling relation to the registry so that the registry provides a calling interface capable of acquiring the calling relation.
In one possible embodiment, the registration information includes: the server address of the service provider, the call interface of the service provider and the application name of the service provider.
In one possible embodiment, the subscription information includes: the server address of the service consumption end and the application name of the service consumption end.
In a second aspect, an embodiment of the present application further provides a call relation determining apparatus, including:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring communication information between a registration center and at least one server connected with the registration center; the communication information comprises registration information sent by a service provider and subscription information sent by a service consumer;
a subscription determining module, configured to determine, for at least one piece of registration information, subscription information for subscribing to the registration information; the subscription information is used for describing a subscription relationship between the registration information and the subscription information;
a name determining module, configured to determine, according to the registration information, an application name of a service provider that sends the registration information, and determine, according to subscription information that subscribes to the registration information, an application name of a service consumer that subscribes to the registration information;
the relation determining module is used for determining a calling relation between service provider application and service consumer application according to the subscription relation between the registration information and the subscription information, and recording the calling relation by using the application name of the service provider and the application name of the service consumer;
and the interface module is used for issuing the calling relationship to the registration center so that the registration center provides a calling interface capable of acquiring the calling relationship.
In a possible implementation manner, the registration information includes a server address of the service provider, a call interface of the service provider, and an application name of the service.
In one possible embodiment, the subscription information includes: the server address of the service consumption end and the application name of the service consumption end.
In a third aspect, an embodiment of the present application further provides a computer-readable storage medium. The specific scheme is as follows:
a computer readable storage medium storing computer instructions which, when executed by a processor, may implement the steps of any one of the possible embodiments of the first aspect and the first aspect.
In a fourth aspect, an embodiment of the present application further provides an electronic device. The specific scheme is as follows:
an electronic device comprising the computer-readable storage medium described above, further comprising a processor that can execute the computer-readable storage medium.
In summary, the present application provides a call relation determining method, an apparatus, a storage medium, and an electronic device. According to the application method and the application system, the application name of the service provider sending the registration information is determined according to the communication information between the registration center and each server connected with the registration center, and the application name of the service consumer subscribing the registration information is determined, so that the call relation is determined, the registration center provides a call interface capable of obtaining the call relation, developers can directly obtain the call relation between the service consumers and the service providers, the workload of the developers for determining the call relation between the service consumers and the service providers is reduced, and the development and test efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
Fig. 1 is a schematic flowchart of a call relation determining method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a distributed system;
fig. 3 is a schematic structural diagram of a call relation determining apparatus according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements explicitly listed, but may include other steps or elements not explicitly listed or inherent to such process, method, article, or apparatus.
The core invention points of the application are as follows: according to the communication information between the registration center and each server connected with the registration center, the application name of the service providing end sending the registration information is determined, the application name of the service consuming end subscribing the registration information is determined, the call relation is determined, the registration center provides a call interface capable of obtaining the call relation, a developer can directly obtain the call relation between the service consuming end and the service providing end, the workload of the developer for determining the call relation between the service consuming end and the service providing end is reduced, and the development and test efficiency is improved.
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions of the present invention are described in detail below with specific embodiments. Several of the following embodiments may be combined with each other and some details of the same or similar concepts or processes may not be repeated in some embodiments.
Example one
Fig. 1 is a schematic flowchart of a call relation determining method provided in an embodiment of the present application, and as shown in fig. 1, the embodiment mainly includes:
s101: acquiring communication information between a registration center and at least one server connected with the registration center; the communication information comprises registration information sent by the service provider and subscription information sent by the service consumer.
The registry is a scheduling device in the distributed system and is used for scheduling among at least one server, the server connected with the registry is the server in the distributed system, the server connected with the registry can be divided into a service providing end and a service consuming end according to the upstream and downstream calling relation, the service providing end is the server providing the service, and the service consuming end is the server calling the service.
The information interaction among the registry, the service provider and the service consumer is shown in fig. 2. The service providing end sends registration information to the registration center, and the service consuming end sends subscription information to the registration center. And the registration center allocates the service provider meeting the subscription requirement of the service consumer to the service consumer according to the registration information and the subscription information, sends notification information to the service consumer and notifies the service consumer to the allocated service provider. And the service consumption end establishes connection with the service providing end according to the notification information and calls the service providing end to execute subsequent operation. Illustratively, the registry may be implemented using a Remote Procedure Call (RPC) framework in zookeeper, for example, using an open source distributed service framework Dubbo.
In one possible implementation, to complete the distributed system shown in fig. 2, the registration information sent by the service provider to the registry includes: the server address of the service provider, the call interface of the service provider and the application name of the service provider. The subscription information sent by the service consumer to the registry comprises: the server address of the service consumption end and the application name of the service consumption end. Here, the server address of the service provider and the server address of the service consumer are typically IP addresses.
Therefore, in order to determine the call relationship between the service provider and the service consumer, it is necessary to first obtain communication information between the registry and each server connected to the registry, where the communication information includes registration information sent by the service provider and subscription information sent by the service consumer.
S102: and determining subscription information subscribed to the registration information aiming at least one piece of registration information.
When determining the calling relationship, the determination is carried out by taking the service consumption end as a starting point. Therefore, at least one registration information is first acquired from the communication information, and for each registration information, subscription information that subscribes to the registration information is determined. Here, the subscription information is used to describe a subscription relationship between the registration information and the subscription information.
S103: and determining the application name of the service provider sending the registration information according to the registration information, and determining the application name of the service consumer subscribing the registration information according to the subscription information subscribing the registration information.
The determination of the call relation needs to determine the application name of the actual implementation call relation, the application is a specific application program, the steps for realizing the functions in the distributed system are split, and the application programs in different servers complete different steps. In a specific implementation, the specific application program may be implemented using any program language, for example, JAVA, C + +, C #, JavaScript, HTML, CSS, and other program languages. In addition, a distributed system can be adopted to realize the test function of the application program, the upstream service consumption end is a server for starting test excitation, collecting and analyzing the test result, the application program on the upstream service consumption end is an application program for performing test scheduling and result analysis, and the downstream service providing end is an application program for actually running the function to be tested. Therefore, after the registration information and the subscription information are obtained and the subscription relationship between the registration information and the subscription information is clarified, the application name of the service provider sending the registration information needs to be determined according to the registration information, and the application name of the service consumer subscribing the registration information needs to be determined according to the subscription information subscribing the registration information. For example, when the grayscale platform is used for application testing, when the grayscale platform issues a grayscale rule, a caller of the grayscale application needs to be determined, that is, a process of determining a service consumer application subscribing to the registration information according to the service provider application in the registration information.
S104: and determining a call relation between service provider application and service consumer application according to the subscription relation between the registration information and the subscription information, and recording the call relation by using the application name of the service provider and the application name of the service consumer.
And determining the calling relationship between the service provider application and the service consumer application according to the subscription relationship between the subscription information and the registration information. Specifically, between subscription information and registration information having a subscription relationship, a service consumer application that sends the subscription information invokes a service provider application that sends the registration information. Further, between the service provider application and the service consumer application having the call relationship, the call relationship is recorded by using the application name of the service provider and the application name of the service consumer. The application name of the service provider is the name of the application of the service provider, and the application name of the service consumer is the name of the application of the service consumer.
In specific implementation, a table, a list or a chart including the application name of the service provider and the application name of the service consumer of each service provider application and service consumer application having a calling relationship may be generated, and the calling relationship between the service provider application and the service consumer application may be recorded.
S105: and issuing the calling relation to the registry so that the registry provides a calling interface capable of acquiring the calling relation.
Specifically, the registry may be configured by Apollo, and the table, list or chart including the application name of each service provider having the calling relationship service provider application and the service consumer application, the application name of the service consumer, and the calling relationship thereof is issued to the registry, that is, the scheduling relationship is stored in the registry. In addition, a call Interface capable of directly obtaining the call relationship is provided in the registry, for example, an Application Programming Interface (API) is provided. The service side can automatically load and directly obtain the call relation between each service provider application and each service consumer application registered in the registry, namely the upstream and downstream relation of the applications, by calling the API interface.
Further, the service side may send an application name of the service provider applied by the specific service provider to the API interface, so as to obtain an application name of the service consumer applied by the service provider.
Based on the same design concept, the embodiment of the application also provides a call relation determining device, a storage medium and an electronic device.
Example two
As shown in fig. 3, a call relation determining apparatus 300 provided in the embodiment of the present application includes:
an obtaining module 301, configured to obtain communication information between a registry and at least one server connected to the registry; the communication information comprises registration information sent by a service provider and subscription information sent by a service consumer;
a subscription determining module 302, configured to determine, for at least one piece of the registration information, subscription information for subscribing to the registration information; the subscription information is used for describing a subscription relationship between the registration information and the subscription information;
a name determining module 303, configured to determine, according to the registration information, an application name of a service provider that sends the registration information, and determine, according to subscription information that subscribes to the registration information, an application name of a service consumer that subscribes to the registration information;
a relationship determining module 304, configured to determine, according to the subscription relationship between the registration information and the subscription information, a call relationship between a service provider application and a service consumer application, and record the call relationship by using an application name of the service provider and an application name of the service consumer;
an interface module 305, configured to issue the call relationship to the registry, so that the registry provides a call interface capable of obtaining the call relationship.
In a possible implementation manner, the registration information includes a server address of the service provider, a call interface of the service provider, and an application name of the service.
In one possible embodiment, the subscription information includes: the server address of the service consumption end and the application name of the service consumption end.
Example four
A computer readable storage medium storing instructions that, when executed by a processor, cause the processor to perform the steps of any of the call relation determination methods provided by embodiments of the present application. In practical applications, the computer readable medium may be included in the apparatus/device/system described in the above embodiments, or may exist alone without being assembled into the apparatus/device/system. The computer readable storage medium carries one or more programs which, when executed, implement the steps of performing any of the call relation determination methods provided by the embodiments of the present application according to any of the call relation determination apparatuses provided by referring to the embodiments of the present application.
According to embodiments disclosed herein, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example and without limitation: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing, without limiting the scope of the present disclosure. In the embodiments disclosed herein, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The method steps described herein may be implemented in hardware, for example, logic gates, switches, Application Specific Integrated Circuits (ASICs), programmable logic controllers, embedded microcontrollers, etc., in addition to data processing programs. Such hardware capable of implementing the methods described herein may also constitute the present application.
EXAMPLE five
The embodiment of the present application further provides an electronic device, which may be a computer or a server, and any one of the call relation determining apparatuses provided in the embodiments of the present application may be integrated therein. As shown in fig. 4, an electronic device 400 provided by the embodiment of the present application is shown.
The electronic device may include a processor 401 of one or more processing cores, one or more computer-readable storage media 402. The electronic device may further include a power supply 403 and an input-output unit 404. Those skilled in the art will appreciate that fig. 4 does not constitute a limitation of the electronic device and may include more or fewer components than illustrated, or some components may be combined, or a different arrangement of components.
Wherein:
the processor 401 is a control portion of the electronic device, connects the various portions by using various interfaces and lines, and executes the steps of any of the call relation determination methods provided by the embodiments of the present application by running or executing a software program stored in the computer-readable storage medium 402.
The computer-readable storage medium 402 can be used for storing a software program, namely, a program involved in any call relation determination method provided by the embodiment of the application.
The processor 401 executes various functional applications and data processing by executing software programs stored in the computer-readable storage medium 402. The computer-readable storage medium 402 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data or the like used according to the needs of the electronic device. Further, the computer-readable storage medium 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the computer-readable storage medium 402 may also include a memory controller to provide the processor 401 access to the computer-readable storage medium 402.
The electronic device further comprises a power supply 403 for supplying power to the various components, and preferably, the power supply 403 is logically connected to the processor 401 through a power management system, so that functions of managing charging, discharging, and power consumption are realized through the power management system. The power supply 403 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.
The server may also include an input-output unit 404, such as may be used to receive entered numeric or character information, and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control; such as various graphical user interfaces that may be used to display information entered by or provided to the user, as well as the server, which may be composed of graphics, text, icons, video, and any combination thereof.
Any calling relation determining method, device, storage medium and electronic equipment provided by the embodiments of the present application are based on the same design concept, and the technical means in any embodiment of the present application can be freely combined, and the combined technical means is still within the protection scope of the present application.
The flowchart and block diagrams in the figures of the present application illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments disclosed herein. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
It will be appreciated by a person skilled in the art that various combinations and/or combinations of features described in the various embodiments and/or claims of the present application are possible, even if such combinations or combinations are not explicitly described in the present application. In particular, the features recited in the various embodiments and/or claims of the present application may be combined and/or coupled in various ways, all of which fall within the scope of the present disclosure, without departing from the spirit and teachings of the present application.
The principle and implementation of the present application are explained by applying specific embodiments in the present application, and the above description of the embodiments is only used to help understanding the method and the core idea of the present application, and is not used to limit the present application. It will be appreciated by those skilled in the art that changes may be made in this embodiment and its broader aspects and without departing from the principles, spirit and scope of the invention, and that all such modifications, equivalents, improvements and equivalents as may be included within the scope of the invention are intended to be protected by the claims.
Claims (8)
1. A method for determining calling relation is suitable for realizing a test function of an application program by adopting a distributed system, and when a gray-scale platform is used for carrying out application test, the application is the application program, and the method is characterized by comprising the following steps:
acquiring communication information between a registration center and at least one server connected with the registration center; the registry is realized by using a remote call control (RPC) framework in the zookeeper, and the communication information comprises registration information sent by a service providing end and subscription information sent by a service consuming end; the registration center is scheduling equipment in the distributed system; the application program of the service providing end is an application program for running a function to be tested, and the application program of the service consuming end is an application program for performing test scheduling and result analysis;
for at least one piece of the registration information, determining subscription information for subscribing the registration information; the subscription information is used for describing a subscription relationship between the registration information and the subscription information;
determining the application name of a service provider sending the registration information according to the registration information, and determining the application name of a service consumer subscribing the registration information according to subscription information subscribing the registration information; the process of determining the application name of the service consumer subscribing the registration information is to determine a calling party of gray scale application when the gray scale platform issues a gray scale rule when the gray scale platform performs application test;
determining a calling relationship between service provider application and service consumer application according to the subscription relationship between the registration information and the subscription information, wherein the service consumer application sending the subscription information calls the service provider application sending the registration information; recording the calling relation by using the application name of the service providing end and the application name of the service consuming end; the application name of the service provider is the name of the application of the service provider, and the application name of the service consumer is the name of the application of the service consumer;
and issuing the calling relation to the registry so that the registry provides a calling interface capable of acquiring the calling relation.
2. The method of claim 1, wherein the registration information comprises: the server address of the service provider, the call interface of the service provider and the application name of the service provider.
3. The method of claim 1, wherein the subscription information comprises: the server address of the service consumption end and the application name of the service consumption end.
4. A call relation determining apparatus adapted to implement a test function for an application program by using a distributed system, the application being the application program when an application test is performed using a grayscale platform, the call relation determining apparatus comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring communication information between a registration center and at least one server connected with the registration center; the registry is realized by using a remote call control (RPC) framework in the zookeeper, and the communication information comprises registration information sent by a service providing end and subscription information sent by a service consuming end; the registration center is scheduling equipment in the distributed system; the application program of the service providing end is an application program for running a function to be tested, and the application program of the service consuming end is an application program for performing test scheduling and result analysis;
a subscription determining module, configured to determine, for at least one piece of registration information, subscription information for subscribing to the registration information; the subscription information is used for describing a subscription relationship between the registration information and the subscription information;
a name determining module, configured to determine, according to the registration information, an application name of a service provider that sends the registration information, and determine, according to subscription information that subscribes to the registration information, an application name of a service consumer that subscribes to the registration information; the process of determining the application name of the service consumer subscribing the registration information is to determine a calling party of gray scale application when the gray scale platform issues a gray scale rule when the gray scale platform is used for application test;
the relation determining module is used for determining the calling relation between the service provider application and the service consumer application according to the subscription relation between the registration information and the subscription information, and the service consumer application sending the subscription information calls the service provider application sending the registration information; recording the calling relation by using the application name of the service providing end and the application name of the service consuming end; the application name of the service provider is the name of the application of the service provider, and the application name of the service consumer is the name of the application of the service consumer;
and the interface module is used for issuing the calling relationship to the registration center so that the registration center provides a calling interface capable of acquiring the calling relationship.
5. The apparatus of claim 4, wherein the registration information comprises a server address of the service provider, a calling interface of the service provider, and an application name of the service.
6. The apparatus of claim 4, wherein the subscription information comprises: the server address of the service consumption end and the application name of the service consumption end.
7. A computer readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 3.
8. An electronic device comprising the computer-readable storage medium of claim 7, and further comprising a processor that can execute the computer-readable storage medium.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910885680.2A CN110708362B (en) | 2019-09-19 | 2019-09-19 | Call relation determining method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910885680.2A CN110708362B (en) | 2019-09-19 | 2019-09-19 | Call relation determining method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110708362A CN110708362A (en) | 2020-01-17 |
| CN110708362B true CN110708362B (en) | 2021-02-05 |
Family
ID=69194678
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910885680.2A Active CN110708362B (en) | 2019-09-19 | 2019-09-19 | Call relation determining method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110708362B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111431745A (en) * | 2020-03-18 | 2020-07-17 | 浩云科技股份有限公司 | Method for establishing automatically configured communication link |
| CN111708589B (en) * | 2020-06-17 | 2024-04-16 | 中国银行股份有限公司 | Information processing system, method, device and readable storage medium |
| CN112202605A (en) * | 2020-09-27 | 2021-01-08 | 中国建设银行股份有限公司 | Service configuration method, device, equipment and storage medium |
| CN112328413B (en) * | 2020-11-25 | 2023-09-26 | 中国工商银行股份有限公司 | Application service calling method, device and system |
| CN113542217B (en) * | 2021-06-07 | 2023-05-26 | 广发银行股份有限公司 | Service subscription system |
| CN115102749B (en) * | 2022-06-16 | 2024-03-19 | 上海商汤阡誓科技有限公司 | Resource interaction method, device, equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105791341A (en) * | 2014-12-22 | 2016-07-20 | 华为软件技术有限公司 | Method, device and system for processing application release |
| CN105933444A (en) * | 2016-06-27 | 2016-09-07 | 焦点科技股份有限公司 | Service discovering method based on cooperation of registration center and caching mechanism |
| CN107438107A (en) * | 2017-09-05 | 2017-12-05 | 深圳乐信软件技术有限公司 | The call method and device of background service in a kind of micro services framework |
| CN107888551A (en) * | 2016-09-30 | 2018-04-06 | 北京神州泰岳软件股份有限公司 | A kind of remote service calling method, device and system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102710593B (en) * | 2012-03-19 | 2015-05-27 | 北京邮电大学 | Method, device and system for publishing message in graph mashup |
| CN104426871A (en) * | 2013-08-29 | 2015-03-18 | 中兴通讯股份有限公司 | Method and device for realizing remote calling |
| CN105721473B (en) * | 2016-02-24 | 2019-07-09 | 锐达互动科技股份有限公司 | A kind of method and system of WEB terminal far call optimization |
| US10320603B1 (en) * | 2016-12-02 | 2019-06-11 | Worldpay, Llc | Systems and methods for registering computer server event notifications |
| CN107918673B (en) * | 2017-12-12 | 2022-11-04 | 腾讯科技（深圳）有限公司 | Subscription data processing method and device, storage medium and computer equipment |
-
2019
- 2019-09-19 CN CN201910885680.2A patent/CN110708362B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105791341A (en) * | 2014-12-22 | 2016-07-20 | 华为软件技术有限公司 | Method, device and system for processing application release |
| CN105933444A (en) * | 2016-06-27 | 2016-09-07 | 焦点科技股份有限公司 | Service discovering method based on cooperation of registration center and caching mechanism |
| CN107888551A (en) * | 2016-09-30 | 2018-04-06 | 北京神州泰岳软件股份有限公司 | A kind of remote service calling method, device and system |
| CN107438107A (en) * | 2017-09-05 | 2017-12-05 | 深圳乐信软件技术有限公司 | The call method and device of background service in a kind of micro services framework |
Non-Patent Citations (1)
| Title |
|---|
| 基于微服务架构的开放平台消息系统的设计与实现;谢伟;《中国优秀硕士学位论文全文数据库(电子期刊)》;20190515;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110708362A (en) | 2020-01-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110708362B (en) | Call relation determining method and device, storage medium and electronic equipment | |
| US8843943B2 (en) | Generating a service definition in view of service activity events | |
| US20200356237A1 (en) | Graphical chatbot interface facilitating user-chatbot interaction | |
| CN111796860B (en) | Micro front end scheme implementation method and device | |
| US10552812B2 (en) | Scenario based logging | |
| CN114647519A (en) | Data transmission method and device between native platform and Flutter platform and storage medium | |
| CN113742228B (en) | Test, data playback and recording methods, systems, devices, equipment and media | |
| CN112835617B (en) | Gray release method, device, server and readable medium | |
| CN112306529A (en) | System upgrading method, device, equipment and storage medium | |
| CN117314139A (en) | Modeling method and device for business process, terminal equipment and storage medium | |
| CN113282444A (en) | Visualization method and device for business process debugging | |
| CN111435328A (en) | Application testing method and device, electronic equipment and readable storage medium | |
| CN113157439A (en) | Resource statistical method, device and terminal | |
| US11526828B2 (en) | Calculating developer time during development process | |
| CN109871226B (en) | Configuration method, device and medium of downloader and electronic equipment | |
| US20140244538A1 (en) | Business process management, configuration and execution | |
| CN111967769A (en) | Risk identification method, device, equipment and medium | |
| CN112101718A (en) | Multi-user cooperation structured data processing method and device based on Internet | |
| CN110597587A (en) | User interface generation method and device, electronic equipment and storage medium | |
| US8756649B2 (en) | Language-agnostic policy management | |
| CN104268205A (en) | Method and device for obtaining information of installed applications in IOS system | |
| CN111026376B (en) | Function configuration method and device, storage medium and electronic equipment | |
| CN111026366B (en) | User interface implementation method and device, storage medium and electronic equipment | |
| CN105320523A (en) | Data processing method and apparatus | |
| US10656986B2 (en) | Dynamically controlling runtime system logging based on end-user reviews |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200310 Address after: 100085 Floor 102-1, Building No. 35, West Second Banner Road, Haidian District, Beijing Applicant after: Seashell Housing (Beijing) Technology Co., Ltd. Address before: 300 280 Tianjin Economic and Technological Development Zone Nangang Industrial Zone Office Building C Block 1, Room 112, Unit 05 Applicant before: Shell Technology Co., Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |