CN113364885A - Micro-service calling method and device, electronic equipment and readable storage medium - Google Patents
Micro-service calling method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN113364885A CN113364885A CN202110726509.4A CN202110726509A CN113364885A CN 113364885 A CN113364885 A CN 113364885A CN 202110726509 A CN202110726509 A CN 202110726509A CN 113364885 A CN113364885 A CN 113364885A
- Authority
- CN
- China
- Prior art keywords
- micro
- service
- node
- chain
- micro service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
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/51—Discovery or management thereof, e.g. service location protocol [SLP] or 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/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)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Hardware Redundancy (AREA)
Abstract
The disclosure provides a micro-service calling method and device, electronic equipment and a computer readable storage medium, and relates to the technical field of computers. The micro-service calling method comprises the following steps: responding to a calling request of a target micro service sent by a micro service calling end, and acquiring a micro service instance list matched with the calling request, wherein the micro service instance list is used for recording micro service information of all nodes on a micro service instance chain, and the micro service instance chain comprises at least one micro service node; and sending the micro-service instance list to a micro-service calling end, namely calling the target micro-service by the calling end based on the micro-service instance list. According to the technical scheme, the strong dependence on the registration center is eliminated, so that the calling fault caused by the fault of the registration center is avoided, and the reliability of micro-service calling can be improved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for invoking a micro service, an electronic device, and a computer-readable storage medium.
Background
The microservice architecture is a discovery function that provides microservices by introducing a registry. In the registration and calling process of the micro-service, the registration center serves as an integral server side to provide registration of the micro-service and discovery of a client side, and a micro-service caller and a micro-service provider are realized by the client side.
When an application starts, the microserver provider registers with the registry for microservices provided by itself and periodically sends a heartbeat to update the instance state.
The micro-service caller acquires a needed micro-service instance list from the micro-service registration center, caches the micro-service instance list to the local, periodically requests the registration center to update the state of the local cache, and acquires a specific micro-service instance and access information of the instance according to the name of the micro-service after acquiring the micro-service instance list so as to further determine the selected instance to implement and call according to a load balancing strategy.
As can be seen from the above, the registration and discovery mechanisms used by the current microservice architecture strongly depend on the registry, and if the registry fails, all microservices may not be invoked.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The present disclosure is directed to a method, an apparatus, an electronic device, and a computer-readable storage medium for invoking a micro service, which overcome, at least to some extent, the problem of strong dependency on a registry in the related art.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.
According to an aspect of the present disclosure, there is provided a micro service invoking method, including: responding to a calling request of a target micro service sent by a micro service calling end, and acquiring a micro service instance list matched with the calling request, wherein the micro service instance list is used for recording micro service information of all nodes on a micro service instance chain, and the micro service instance chain comprises at least one micro service node; and sending the micro-service instance list to the micro-service calling end, namely calling the target micro-service by the calling end based on the micro-service instance list.
In an embodiment of the present disclosure, before the obtaining, in response to a call request of a target micro service sent by a micro service call end, a micro service instance list matching the call request, the method further includes: constructing at least one of the microservice nodes as the microservice instance chain based on an IP segment scan operation; and generating the micro service instance list based on the micro service information transmission operation of the micro service nodes along the micro service instance chain.
In an embodiment of the present disclosure, the constructing at least one of the microservice nodes as the microservice instance chain based on the IP segment scan operation specifically includes: when registration information of a node to be registered is received, extracting IP section information of the node to be registered from the registration information, wherein the node to be registered is the micro service node to be registered; when the micro service instance chain is an empty chain, sequencing the nodes to be registered based on the IP section information to construct the micro service instance chain; and when the micro service instance chain is a non-empty chain, executing the IP section scanning on the micro service instance chain of the non-empty chain to determine an original front node and an original rear node of the node to be registered, inserting the node to be registered between the original front node and the original rear node, and marking as an insertion node, wherein the first IP section information of the original front node is the largest IP section in the micro service instance chain, which is smaller than the IP section information, and the second IP section information of the original rear node is the smallest IP section in the micro service instance chain, which is larger than the IP section information.
In one embodiment of the present disclosure, further comprising: and returning registration success information to the node to be registered.
In one embodiment of the present disclosure, the chain of microservice instances is a chain of looped instances.
In an embodiment of the present disclosure, the generating the micro service instance list based on the micro service information transfer operation of the micro service node performed along the micro service instance chain specifically includes: when the micro service instance chain is a null chain, keeping the micro service information of the node to be registered in the micro service instance list; and when the micro service instance chain is a non-empty chain, transmitting the micro service information of the inserted node to the original back node so that the original back node updates the micro service instance list, and transmitting the updated micro service instance list along the annular instance chain until the micro service instance list is transmitted to the inserted node, wherein the micro service information comprises at least one of node IP section information, a node port, a micro service name, an instance name and an instance detection interface.
In one embodiment of the present disclosure, further comprising: and detecting the node state in the micro service instance chain based on a preset detection frequency.
In an embodiment of the present disclosure, the detecting a node state in the microservice instance chain based on a preset detection frequency specifically includes: when the heartbeat of the previous micro service node is detected to be abnormal, setting the previous micro service node in the micro service instance list to be in an unavailable state, and updating the micro service instance list; and when detecting that the abnormal heartbeat frequency of the previous micro service node reaches an abnormal threshold value, deleting the previous micro service node from the micro service instance list, updating the micro service instance list, and reconstructing the micro service instance chain.
According to another aspect of the present disclosure, there is provided a micro service invocation method, including: sending a calling request of a target micro service to a micro service node; receiving a micro service instance list fed back by the micro service nodes based on the call request, wherein the micro service instance list is used for recording instance information of at least one micro service node, and the at least one micro service node forms a chain structure; selecting a target micro-service node from the micro-service instance list based on a load balancing strategy; and calling the target micro service based on the access information of the target micro service node.
According to still another aspect of the present disclosure, there is provided a micro service invocation apparatus, including: the acquiring module is used for responding to a calling request of a target micro service sent by a micro service calling end, and acquiring a micro service instance list matched with the calling request, wherein the micro service instance list is used for recording micro service information of all nodes on a micro service instance chain, and the micro service instance chain comprises at least one micro service node; and the first sending module is used for sending the micro-service instance list to the micro-service calling end, namely, the calling end calls the target micro-service based on the micro-service instance list.
According to still another aspect of the present disclosure, there is provided a micro service invocation apparatus, including: the second sending module is used for sending a calling request of the target micro service to the micro service node; a receiving module, configured to receive a micro service instance list fed back by the micro service node based on the invocation request, where the micro service instance list is used to record instance information of at least one micro service node, and the at least one micro service node forms a chain structure; the selection module is used for selecting a target micro-service node from the micro-service instance list based on a load balancing strategy; and the calling module is used for calling the target micro service based on the access information of the target micro service node.
According to yet another aspect of the present disclosure, there is provided an electronic device including: a processor; and a memory for storing executable instructions for the processor; wherein the processor is configured to execute the microservice calling method of any of the above first aspects via execution of executable instructions.
According to yet another aspect of the present disclosure, there is provided an electronic device including: a processor; and a memory for storing executable instructions for the processor; wherein the processor is configured to execute the microservice calling method of any of the second aspects above via execution of executable instructions.
According to yet another aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the microservice calling method of any one of the above.
According to the micro-service calling scheme provided by the embodiment of the disclosure, at least one micro-service providing terminal is used as a micro-service node to configure a micro-service instance chain, so that micro-service information of all nodes belonging to the micro-service instance chain is transmitted in a chain manner, and each micro-service node can store the latest component state of all the micro-service nodes in a micro-service information storage manner. Further, based on a random sending or polling sending mode, the micro-service providing terminal serving as a micro-service node directly receives a calling request of a target micro-service sent by the micro-service calling terminal, so that the micro-service providing terminal directly feeds back a micro-service instance list capable of realizing the target micro-service to the micro-service calling terminal, and the micro-service calling terminal realizes the calling of the target micro-service based on the micro-service instance list.
According to the micro-service calling scheme, on one hand, the request and calling process does not need participation of the registration center, namely strong dependence on the registration center is eliminated, so that calling faults caused by faults of the registration center are avoided, and therefore the reliability of micro-service calling can be improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.
FIG. 1 is a flow chart illustrating a method for invoking a microservice in an embodiment of the present disclosure;
FIG. 2 is a flow chart illustrating another method for invoking a microservice in an embodiment of the present disclosure;
FIG. 3 is a flow chart illustrating a method for invoking a microservice in an embodiment of the present disclosure;
FIG. 4 is a schematic diagram illustrating a chain of micro-service instances in an embodiment of the present disclosure;
FIG. 5 is a flow chart illustrating a method for invoking a microservice in an embodiment of the present disclosure;
FIG. 6 is a flow chart illustrating a method for invoking a microservice in an embodiment of the present disclosure;
FIG. 7 is a flow chart illustrating another method for invoking a microservice in an embodiment of the present disclosure;
FIG. 8 is a flow chart illustrating a method for invoking a microservice in an embodiment of the present disclosure;
FIG. 9 is a flow chart illustrating a method for invoking a microservice in accordance with yet another embodiment of the present disclosure;
FIG. 10 is a schematic diagram illustrating a microservice invocation system in an embodiment of the present disclosure;
FIG. 11 is a schematic diagram illustrating a micro-service invocation device in an embodiment of the present disclosure;
FIG. 12 is a schematic diagram of another apparatus for invoking a microservice in an embodiment of the present disclosure;
FIG. 13 shows a schematic view of an electronic device in an embodiment of the disclosure; and
FIG. 14 shows a schematic diagram of a computer-readable storage medium in an embodiment of the disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
Further, the drawings are merely schematic illustrations of the present disclosure, in which the same reference numerals denote the same or similar parts, and thus, a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The following detailed description of exemplary embodiments of the disclosure refers to the accompanying drawings.
As shown in fig. 1, the method for executing the micro service call by the micro service providing terminal includes the following steps:
step S102, responding to a calling request of a target micro service sent by a micro service calling end, and acquiring a micro service instance list matched with the calling request, wherein the micro service instance list is used for recording micro service information of all nodes on a micro service instance chain, and the micro service instance chain comprises at least one micro service node.
The micro-service calling terminal directly receives a calling request of a target micro-service sent by the micro-service calling terminal, and the micro-service calling terminal sends the calling request.
The micro service instance chain is used for sequencing a plurality of micro service nodes according to a specified sequencing mode so as to carry out information interaction among the micro service nodes, thereby realizing that each micro service node can store a micro service instance list comprising micro service information of all the micro service nodes in the micro service instance chain.
Those skilled in the art will also appreciate that a chain of microservice instances does not preclude the case of only one microservice node.
In addition, the micro-service instance chain may be an open chain structure or a closed chain structure.
And step S104, sending the micro-service instance list to a micro-service calling end, namely calling the target micro-service by the calling end based on the micro-service instance list.
In this embodiment, at least one microservice providing terminal is used as a microservice node to configure a microservice instance chain, so that microservice information of all nodes belonging to the microservice instance chain is transferred in a chain manner, and each microservice node can store the latest component state of all microservice nodes in a manner of storing microservice information. Furthermore, based on the random sending or polling sending mode, the micro-service providing terminal as the micro-service node directly receives the calling request of the target micro-service sent by the micro-service calling terminal, so that the micro-service providing terminal directly feeds back the micro-service instance list capable of realizing the target micro-service to the micro-service calling terminal, thereby the micro-service calling terminal realizes the calling of the target micro-service based on the micro-service instance list, on one hand, the request and calling process does not need the participation of the registration center, namely, the strong dependence on the registration center is eliminated, therefore, the calling fault caused by the fault of the registration center is avoided, thereby the reliability of micro-service calling is improved, on the other hand, when the micro-service instance chain comprises a plurality of micro-service nodes, because each micro-service node stores the micro-service instance list even if the fault node occurs, the example list can be fed back and the micro service can be executed through other normal nodes, so that the reliability of micro service calling can be further improved.
In addition, those skilled in the art can also understand that the micro-service providing terminal as the executing subject may be any one micro-service node in the micro-service instance chain, and may also be a micro-service node to be registered.
As shown in fig. 2, in an embodiment of the present disclosure, before the step S102, in response to a call request of a target micro service sent by a micro service call end, acquiring a micro service instance list matching the call request, the method further includes:
step S202, at least one micro service node is constructed as a micro service instance chain based on the IP section scanning operation.
When the node is started, only the address field of the node is needed to be configured without specifying a specific IP address, the IP address can be flexibly configured, other nodes which can belong to the same micro service instance chain are scanned with the IP field, and the scanning efficiency can be improved.
Step S204, a micro-service instance list is generated based on the micro-service information transmission operation of the micro-service nodes along the micro-service instance chain.
In the embodiment, an IP address field is configured for the started node, node address scanning is carried out based on the IP address field, and then the micro service nodes are sequenced based on the scanning structure to obtain a micro service instance chain, information transmission and list updating can be further carried out based on the micro service instance chain, and the micro service is guaranteed to be effectively called.
As shown in fig. 3, in an embodiment of the present disclosure, step S202, constructing at least one microservice node as a specific implementation of a microservice instance chain based on an IP segment scan operation includes:
step S302, when the registration information of the node to be registered is received, the IP section information of the node to be registered is extracted from the registration information, and the node to be registered is the micro service node to be registered.
The registration information of the node to be registered may be the same as the micro service information of the node.
And step S304, when the micro-service instance chain is an empty chain, sequencing the nodes to be registered based on the IP section information so as to construct the micro-service instance chain.
Step S306, when the micro service instance chain is a non-empty chain, the micro service instance chain of the non-empty chain is scanned by an IP section to determine an original front node and an original back node of the node to be registered, and the node to be registered is inserted between the original front node and the original back node and is marked as an insertion node.
The first IP section information of the original front node is a maximum IP section smaller than the IP section information in the micro service instance chain, and the second IP section information of the original rear node is a minimum IP section larger than the IP section information in the micro service instance chain.
As shown in fig. 3, in one embodiment of the present disclosure, the method further includes:
and step S308, returning registration success information to the node to be registered.
In this embodiment, microservice information can be passed between nodes with similar IP addresses by constructing a chain of microservice instances by node sorting based on the size of the IP segments.
In one embodiment of the present disclosure, the micro-service instance chain is a ring instance chain.
As shown in fig. 4, each microservice instance represents a microservice node, the microservice instances 1 to 8 form a ring-shaped instance chain, and the instance information of the microservice node is transferred in the ring in a chain manner, and simultaneously, each instance updates the states of all components currently stored in the local computer simultaneously in the transfer process. By constructing the annular instance chain, after one circle of the instance chain is transmitted in sequence, a complete instance list can be generated, further the instance list is transmitted in sequence, each micro-service node is enabled to store the micro-service instance list, and the instance list can be sent to the calling terminal no matter which micro-service node receives the calling request, so that the calling terminal can smoothly execute the calling operation.
Specifically, in the ring-shaped instance chain, the micro service nodes are ordered from small to large based on the sizes of the IP segments, that is, the IP segment of the previous adjacent node is smaller than that of the next node, so that when a node to be registered exists, the node to be registered determines the position in the ring-shaped instance chain based on the IP segment address of the node to be registered, and sends the registration information of the node to the next adjacent node, the next node updates the micro service instance list based on the registration information, and then transmits the updated micro service instance list to the previous node until all the nodes in the ring-shaped instance chain store the updated micro service instance list.
As shown in fig. 5, in an embodiment of the present disclosure, step S204, a specific implementation manner of generating a micro service instance list based on a micro service information transfer operation of a micro service node along a micro service instance chain includes:
step S502, when the micro service instance chain is an empty chain, the micro service information of the node to be registered is kept in the micro service instance list.
Step S504, when the micro-service instance chain is a non-empty chain, the micro-service information of the inserted node is transmitted to the original back node, so that the original back node updates the micro-service instance list, and the updated micro-service instance list is transmitted along the annular instance chain until the micro-service instance list is transmitted to the inserted node.
The micro service information comprises at least one of node IP section information, a node port, a micro service name, an instance name and an instance detection interface.
In this embodiment, when the micro-service instance chain is an empty chain, the node to be registered may be understood as an original node, that is, a node for constructing the micro-service instance list, and when the micro-service instance chain is a non-empty chain, the node to be registered may be understood as an insertion node, that is, the micro-service instance list is updated based on the micro-service information of the insertion node, thereby implementing the construction and the update of the micro-service instance list.
As shown in fig. 6, the registration process of the microservice node in the microservice calling scheme according to the present disclosure includes:
step S602, the node to be registered executes an IP segment scanning operation.
Step S604, detecting whether other microservice nodes in the instance chain are scanned, if the detection result is yes, the process proceeds to step S608, and if the detection result is no, the process proceeds to step S606.
And step S606, generating a micro-service instance list based on the micro-service information of the user.
Step S608, sending the micro service information of itself to the next adjacent micro service node to perform the registration operation.
Step S610, the latter microservice node registers the node to be registered based on the registration information, and returns registration success information to the node to be registered, and the node to be registered is changed into a registration node.
Step S612, the latter micro service node performs ring-type transmission on the registration information.
And step S614, the registered node receives the micro service instance list and selects the previous micro service node from the micro service instance list.
In step S616, the registration node updates the micro service instance list based on the selected previous micro service node to form a new ring-shaped instance chain.
Specifically, when a node starts up, it scans backwards according to the designated IP segment, which is called ring scan. When a back node with an IP section larger than the back node is scanned, stopping scanning, and including the micro-service instance information of the back node without limitation to the following information: and after receiving the registration success information, pulling the whole micro service instance list information of the target machine to the local and storing.
And acquiring the maximum IP smaller than the maximum IP as a front node of the registration list, and inserting the node between the front node and a back node to form a ring instance chain.
When no other available service can be found when the registration is circulated to the IP deployed by the user, the user component information is taken as a unique instance to be saved in a micro-service instance list, and the scanning is terminated.
When the component runs healthily and registration information of a new node is received, the registered node information is detected, if the node information is larger than the current node IP value, the node information is written into the micro-service instance list, and then success information is returned to the newly registered node.
Further, the registration information of the new node is sent to the original front node and the back node, the original front node pulls out the complete micro-service instance list once after receiving the information, and the back node of the original front node is adjusted.
And after receiving the new registration information, the back node in the original chain transmits the registration information to the back node of the back node, and the registration information is not updated to all the microservice nodes in the ring.
In one embodiment of the present disclosure, further comprising: and detecting the node state in the micro-service instance chain based on a preset detection frequency.
In this embodiment, availability and reachability of the microservices are ensured by a mutual detection mechanism, whose component state is more accurate than heartbeat updates.
As shown in fig. 7, in an embodiment of the present disclosure, detecting a node state in a microservice instance chain based on a preset detection frequency specifically includes:
step S702, when the heartbeat of the previous micro service node is detected to be abnormal, the previous micro service node is set to be in an unavailable state in the micro service instance list, and the micro service instance list is updated.
Step S704, when it is detected that the number of times of heartbeat abnormality of the previous micro service node reaches the abnormality threshold, deleting the previous micro service node from the micro service instance list, updating the micro service instance list, and reconstructing the micro service instance chain.
In this embodiment, the heartbeat detection is performed on the adjacent previous node by the next node in the chain, instead of reporting the heartbeat information of the previous node to the registration center in the related art, so that the real-time performance and reliability of exception handling when the node is abnormal can be improved.
As shown in fig. 8, in an embodiment of the present disclosure, detecting a node state in a microservice instance chain based on a preset detection frequency specifically includes:
step S802, any current node detects the heartbeat information of the previous node.
Step S804 detects whether the previous node heartbeat is normal based on the heartbeat information, and proceeds to step S806 if the detection result is yes, and proceeds to step S808 if the detection result is no.
Step S806, the detection time is recorded.
Step S808 detects whether the number of abnormal heartbeat times reaches an abnormal threshold value, and if the detection result is yes, the process proceeds to step S810, and if the detection result is no, the process proceeds to step S812.
And step S810, deleting the previous node from the micro service instance list.
In step S812, the state of the previous node is set to be unreachable, and the instance list is updated.
Step S814, the state information is transmitted to the back node.
In step S816, whether the node is reachable after the detection is performed is detected, and if the detection result is yes, the process proceeds to step S820, and if the detection result is no, the process proceeds to step S818.
In step S818, a node following the rear node is selected as a temporary rear node.
And step S820, carrying out ring-type transmission on the updated instance list.
Step S822, until the updated instance list is transferred to the current node.
Specifically, in the detection process of the component, that is, the node state, after the micro service component is successfully registered in the chain, the timing detection task is started, when the timing detection task occurs, the current node is required to detect the state of the previous node, and if the state of the previous node is not abnormal, the current node only records the health detection history of the current node, but does not need to synchronize data to the next node.
When the front node has a fault, namely heartbeat abnormity, if the configured heartbeat abnormity threshold value is not reached, the state of the front node in the micro service instance list is set as unavailable, and the front node is transmitted to the back node. And if the back node is unavailable at the moment, further taking the next node in the ring as a temporary back node to send the information synchronization signal until all new information is synchronized in the whole ring, and finishing the synchronization.
When the number of heartbeat abnormity of the front node is detected to be larger than or equal to an abnormity threshold value, the front node is removed from the micro service instance list and is transmitted to the back node until new information is synchronized to the whole ring, and meanwhile, a node which is just smaller than the front node is taken from the micro service instance list to form a new ring.
When a node receives the synchronization information and finds that the current back node information is not in the registration list, the back node takes the back information in the new ring in the new registration list information as the back node to form a new ring.
If a node has formed a new ring, but still receives the synchronous signal sent by the previous node, the refresh failure is returned.
When a node receives the failure information when synchronizing information backwards, the micro service instance list information of the local machine is used for re-executing the registration process.
As shown in fig. 9, an embodiment of a method for executing a micro service invocation by a micro service invocation terminal includes the following steps:
and step S902, sending a calling request of the target micro service to the micro service node.
Step S904, receiving a micro service instance list fed back by the micro service node based on the call request, where the micro service instance list is used to record instance information of at least one micro service node, and the at least one micro service node forms a chain structure.
And step S906, selecting a target micro service node from the micro service instance list based on the load balancing strategy.
Step S908, call the target microservice based on the access information of the target microservice node.
As shown in fig. 10, another embodiment of the method for executing the micro service invocation by the micro service invocation terminal includes the following steps:
step S1002, the micro-service calling terminal initiates a remote calling request.
Step S1004, acquiring a matched micro-service instance list based on the name of the micro-service.
In step S1006, it is detected whether the micro-service instance list has the required target micro-service, and if the detection result is "no", the process proceeds to step S1008, and if the detection result is "yes", the process proceeds to step S1010.
Step S1008 returns error information to the microservice-providing terminal.
Step S1010, obtaining an operating instance access address from the micro service instance list based on the load balancing policy.
In step S1012, a remote call operation is performed based on the instance access address.
In step S1014, whether the calling operation is successful or not is detected, and if the detection result is "no", the process proceeds to step S1016, and if the detection result is "yes", the process proceeds to step S1018.
In step S1016, it is detected whether there is another available instance address in the micro service instance list, and if the detection result is "no", the process proceeds to step S1020, and if the detection result is "yes", the process returns to step S1012.
Step S1018 returns the call result.
Step S1020 returns error information to the microservice-providing terminal.
Specifically, based on a ring transfer mechanism, the whole micro service instance list information is stored in each micro service point, and the nodes can be quickly synchronized into the ring no matter whether the nodes are unhealthy or newly added. Therefore, the name of the micro-service place is directly called as required to obtain the micro-service instance list with the micro-service state as available, and then the actual micro-service instance is selected for calling according to the low-to-high available strategy.
It is to be noted that the above-mentioned figures are only schematic illustrations of the processes involved in the method according to an exemplary embodiment of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
The micro-service invocation apparatus 1100 according to this embodiment of the present invention is described below with reference to fig. 11. The micro service invocation apparatus 1100 shown in fig. 11 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
The micro service invocation apparatus 1100 is represented in the form of a hardware module. The components of the microservice invocation apparatus 1100 may include, but are not limited to: the acquiring module 1102 is configured to acquire, in response to a call request of a target micro service sent by a micro service call end, a micro service instance list matched with the call request, where the micro service instance list is used to record micro service information of all nodes in a micro service instance chain, and the micro service instance chain includes at least one micro service node; a first sending module 1104, configured to send the micro-service instance list to the micro-service invoking end, that is, the invoking end invokes the target micro-service based on the micro-service instance list.
In one embodiment of the present disclosure, further comprising: a constructing module 1106 for constructing at least one microservice node as a microservice instance chain based on IP segment scan operations; a transferring module 1108, configured to generate a micro service instance list based on a transfer operation of the micro service information of the micro service node performed along the micro service instance chain.
In one embodiment of the present disclosure, the construction module 1106 is further configured to: when the registration information of the node to be registered is received, extracting the IP section information of the node to be registered from the registration information, wherein the node to be registered is the micro service node to be registered; when the micro-service instance chain is an empty chain, sequencing the nodes to be registered based on the IP section information to construct the micro-service instance chain; when the micro-service instance chain is a non-empty chain, performing IP section scanning on the micro-service instance chain of the non-empty chain to determine an original front node and an original back node of a node to be registered, inserting the node to be registered between the original front node and the original back node, and recording as an inserted node, wherein the first IP section information of the original front node is a maximum IP section smaller than the IP section information in the micro-service instance chain, and the second IP section information of the original back node is a minimum IP section larger than the IP section information in the micro-service instance chain.
In one embodiment of the present disclosure, further comprising: a returning module 1110, configured to return registration success information to the node to be registered.
In one embodiment of the present disclosure, the micro-service instance chain is a ring instance chain.
In one embodiment of the present disclosure, the passing module 1108 is further configured to: when the micro-service instance chain is an empty chain, keeping the micro-service information of the node to be registered in the micro-service instance list; and when the micro-service instance chain is a non-empty chain, transmitting the micro-service information of the inserted node to the original back node so that the original back node updates the micro-service instance list, and transmitting the updated micro-service instance list along the annular instance chain until the micro-service instance list is transmitted to the inserted node, wherein the micro-service information comprises at least one of node IP section information, a node port, a micro-service name, an instance name and an instance detection interface.
In one embodiment of the present disclosure, further comprising: a detecting module 1112, configured to detect a node state in the microservice instance chain based on a preset detection frequency.
In one embodiment of the present disclosure, the detection module 1112 is further configured to: when the heartbeat of the previous micro service node is detected to be abnormal, setting the previous micro service node in the micro service instance list to be in an unavailable state, and updating the micro service instance list; and when the abnormal heartbeat frequency of the previous micro service node reaches an abnormal threshold value, deleting the previous micro service node from the micro service instance list, updating the micro service instance list and reconstructing the micro service instance chain.
The micro-service invocation apparatus 1200 according to this embodiment of the present invention is described below with reference to fig. 12. The micro-service invocation apparatus 1200 shown in fig. 12 is only an example and should not bring any limitation to the function and the scope of use of the embodiments of the present invention.
The micro service invocation apparatus 1200 is represented in the form of a hardware module. The components of the microservice invocation apparatus 1200 may include, but are not limited to: a second sending module 1202, configured to send a call request of a target microservice to a microservice node; a receiving module 1204, configured to receive a micro service instance list fed back by the micro service node based on the call request, where the micro service instance list is used to record instance information of at least one micro service node, and the at least one micro service node forms a chain structure; a selecting module 1206, configured to select a target micro-service node from the micro-service instance list based on a load balancing policy; a calling module 1208, configured to call the target microservice based on the access information of the target microservice node.
An electronic device 1300 according to this embodiment of the invention is described below with reference to fig. 13. The electronic device 1300 shown in fig. 13 is only an example and should not bring any limitations to the function and scope of use of the embodiments of the present invention.
As shown in fig. 13, the electronic device 1300 is in the form of a general purpose computing device. The components of the electronic device 1300 may include, but are not limited to: the at least one processing unit 1310, the at least one memory unit 1320, and the bus 1330 connecting the various system components including the memory unit 1320 and the processing unit 1310.
Where the memory unit stores program code, the program code may be executed by the processing unit 1310 to cause the processing unit 1310 to perform steps according to various exemplary embodiments of the present invention as described in the above section "exemplary methods" of this specification. For example, the processing unit 1310 may perform steps S202, S204, S206, and S208 as shown in fig. 1, as well as other steps defined in the microservice invocation method of the present disclosure.
The storage 1320 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)13201 and/or a cache memory unit 13202, and may further include a read-only memory unit (ROM) 13203.
The electronic device 1300 may also communicate with one or more external devices 1370 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 1300 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 1350. Also, the electronic device 1300 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) through the network adapter 1360. As shown, the network adapter 1360 communicates with other modules of the electronic device 1300 via the bus 1330. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above-mentioned "exemplary methods" section of the present description, when the program product is run on the terminal device.
Referring to fig. 14, a program product 1400 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a 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.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (14)
1. A micro-service calling method is applied to a micro-service node and is characterized by comprising the following steps:
responding to a calling request of a target micro service sent by a micro service calling end, and acquiring a micro service instance list matched with the calling request, wherein the micro service instance list is used for recording micro service information of all nodes on a micro service instance chain, and the micro service instance chain comprises at least one micro service node;
and sending the micro-service instance list to the micro-service calling end, namely calling the target micro-service by the calling end based on the micro-service instance list.
2. The method for invoking micro-service according to claim 1, wherein before the obtaining the micro-service instance list matching with the invocation request in response to the invocation request of the target micro-service sent by the micro-service invocation terminal, further comprising:
constructing at least one of the microservice nodes as the microservice instance chain based on an IP segment scan operation; and
and generating the micro service instance list based on the micro service information transmission operation of the micro service nodes along the micro service instance chain.
3. The method for invoking micro-services according to claim 2, wherein the constructing at least one of the micro-service nodes as the chain of micro-service instances based on the IP segment scanning operation comprises:
when registration information of a node to be registered is received, extracting IP section information of the node to be registered from the registration information, wherein the node to be registered is the micro service node to be registered;
when the micro service instance chain is an empty chain, sequencing the nodes to be registered based on the IP section information to construct the micro service instance chain;
when the micro service instance chain is a non-empty chain, the IP section scanning is executed on the micro service instance chain of the non-empty chain so as to determine an original front node and an original back node of the node to be registered, the node to be registered is inserted between the original front node and the original back node and is marked as an insertion node,
the first IP section information of the original front node is the largest IP section in the micro service instance chain, which is smaller than the IP section information, and the second IP section information of the original rear node is the smallest IP section in the micro service instance chain, which is larger than the IP section information.
4. The micro-service invocation method according to claim 3, further comprising:
and returning registration success information to the node to be registered.
5. The microservice invocation method according to claim 3, wherein said microservice instance chain is a circular instance chain.
6. The method for invoking a micro-service according to claim 5, wherein the generating the micro-service instance list based on the transferring operation of the micro-service information of the micro-service node along the chain of micro-service instances comprises:
when the micro service instance chain is a null chain, keeping the micro service information of the node to be registered in the micro service instance list;
when the micro service instance chain is a non-empty chain, the micro service information of the insertion node is transmitted to the original back node so that the original back node updates the micro service instance list and transmits the updated micro service instance list along the annular instance chain until the micro service instance chain is transmitted to the insertion node,
the micro service information comprises at least one of node IP section information, a node port, a micro service name, an instance name and an instance detection interface.
7. The micro-service invocation method according to any of claims 3 to 6, further comprising:
and detecting the node state in the micro service instance chain based on a preset detection frequency.
8. The method for invoking micro-services according to claim 7, wherein the detecting the node state in the chain of micro-service instances based on a preset detection frequency specifically comprises:
when the heartbeat of the previous micro service node is detected to be abnormal, setting the previous micro service node in the micro service instance list to be in an unavailable state, and updating the micro service instance list;
and when detecting that the abnormal heartbeat frequency of the previous micro service node reaches an abnormal threshold value, deleting the previous micro service node from the micro service instance list, updating the micro service instance list, and reconstructing the micro service instance chain.
9. A micro-service calling method is applied to a micro-service calling terminal and is characterized by comprising the following steps:
sending a calling request of a target micro service to a micro service node;
receiving a micro service instance list fed back by the micro service nodes based on the call request, wherein the micro service instance list is used for recording instance information of at least one micro service node, and the at least one micro service node forms a chain structure;
selecting a target micro-service node from the micro-service instance list based on a load balancing strategy;
and calling the target micro service based on the access information of the target micro service node.
10. A micro-service calling device is applied to a micro-service node and is characterized by comprising:
the acquiring module is used for responding to a calling request of a target micro service sent by a micro service calling end, and acquiring a micro service instance list matched with the calling request, wherein the micro service instance list is used for recording micro service information of all nodes on a micro service instance chain, and the micro service instance chain comprises at least one micro service node;
and the first sending module is used for sending the micro-service instance list to the micro-service calling end, namely, the calling end calls the target micro-service based on the micro-service instance list.
11. A micro-service calling device is applied to a micro-service calling terminal and is characterized by comprising:
the second sending module is used for sending a calling request of the target micro service to the micro service node;
a receiving module, configured to receive a micro service instance list fed back by the micro service node based on the invocation request, where the micro service instance list is used to record instance information of at least one micro service node, and the at least one micro service node forms a chain structure;
the selection module is used for selecting a target micro-service node from the micro-service instance list based on a load balancing strategy;
and the calling module is used for calling the target micro service based on the access information of the target micro service node.
12. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to execute the microservice calling method of any of claims 1-8 via execution of the executable instructions.
13. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the microservice call method of claim 9 via execution of the executable instructions.
14. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the microservice calling method according to any one of claims 1 to 9.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110726509.4A CN113364885B (en) | 2021-06-29 | 2021-06-29 | Micro-service calling method and device, electronic equipment and readable storage medium |
| PCT/CN2021/140935 WO2023273240A1 (en) | 2021-06-29 | 2021-12-23 | Micro-service calling method and apparatus, electronic device, and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110726509.4A CN113364885B (en) | 2021-06-29 | 2021-06-29 | Micro-service calling method and device, electronic equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113364885A true CN113364885A (en) | 2021-09-07 |
| CN113364885B CN113364885B (en) | 2022-11-22 |
Family
ID=77537051
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110726509.4A Active CN113364885B (en) | 2021-06-29 | 2021-06-29 | Micro-service calling method and device, electronic equipment and readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113364885B (en) |
| WO (1) | WO2023273240A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023273240A1 (en) * | 2021-06-29 | 2023-01-05 | 天翼云科技有限公司 | Micro-service calling method and apparatus, electronic device, and readable storage medium |
| WO2024066503A1 (en) * | 2022-09-27 | 2024-04-04 | 华为云计算技术有限公司 | Service invocation method and apparatus |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109496420A (en) * | 2018-08-22 | 2019-03-19 | 袁振南 | Cyclic annular server set group managing means, device and computer storage medium |
| WO2020015838A1 (en) * | 2018-07-20 | 2020-01-23 | Nokia Solutions And Networks Oy | Zero trust perimeterization for microservices |
| CN111615066A (en) * | 2020-02-07 | 2020-09-01 | 中国海洋大学 | Distributed micro-service registration and calling method based on broadcast |
| CN112738339A (en) * | 2020-12-29 | 2021-04-30 | 杭州东信北邮信息技术有限公司 | Service instance lossless capacity expansion and reduction method under telecommunication domain micro-service architecture |
| CN112905364A (en) * | 2021-03-31 | 2021-06-04 | 重庆度小满优扬科技有限公司 | Calling method of micro service and electronic equipment |
| CN112968945A (en) * | 2021-02-01 | 2021-06-15 | 北京字跳网络技术有限公司 | Current limiting method and device, electronic equipment and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105515759B (en) * | 2015-11-27 | 2018-11-09 | 国网信息通信产业集团有限公司 | A kind of micro services register method and system |
| EP3543853A1 (en) * | 2018-03-20 | 2019-09-25 | Siemens Healthcare GmbH | Providing microservice information |
| CN113364885B (en) * | 2021-06-29 | 2022-11-22 | 天翼云科技有限公司 | Micro-service calling method and device, electronic equipment and readable storage medium |
-
2021
- 2021-06-29 CN CN202110726509.4A patent/CN113364885B/en active Active
- 2021-12-23 WO PCT/CN2021/140935 patent/WO2023273240A1/en active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020015838A1 (en) * | 2018-07-20 | 2020-01-23 | Nokia Solutions And Networks Oy | Zero trust perimeterization for microservices |
| CN109496420A (en) * | 2018-08-22 | 2019-03-19 | 袁振南 | Cyclic annular server set group managing means, device and computer storage medium |
| CN111615066A (en) * | 2020-02-07 | 2020-09-01 | 中国海洋大学 | Distributed micro-service registration and calling method based on broadcast |
| CN112738339A (en) * | 2020-12-29 | 2021-04-30 | 杭州东信北邮信息技术有限公司 | Service instance lossless capacity expansion and reduction method under telecommunication domain micro-service architecture |
| CN112968945A (en) * | 2021-02-01 | 2021-06-15 | 北京字跳网络技术有限公司 | Current limiting method and device, electronic equipment and storage medium |
| CN112905364A (en) * | 2021-03-31 | 2021-06-04 | 重庆度小满优扬科技有限公司 | Calling method of micro service and electronic equipment |
Non-Patent Citations (1)
| Title |
|---|
| 赵春扬等: "一致性协议在分布式数据库系统中的应用", 《华东师范大学学报（自然科学版）》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023273240A1 (en) * | 2021-06-29 | 2023-01-05 | 天翼云科技有限公司 | Micro-service calling method and apparatus, electronic device, and readable storage medium |
| WO2024066503A1 (en) * | 2022-09-27 | 2024-04-04 | 华为云计算技术有限公司 | Service invocation method and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113364885B (en) | 2022-11-22 |
| WO2023273240A1 (en) | 2023-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7362650B2 (en) | Task processing methods, devices and systems | |
| CN113364885B (en) | Micro-service calling method and device, electronic equipment and readable storage medium | |
| CN112181677B (en) | Service processing method and device, storage medium and electronic device | |
| CN109547524B (en) | User behavior storage method, device, equipment and storage medium based on Internet of things | |
| JP2007531096A (en) | Anomaly management method for multi-agent systems | |
| CN111917833B (en) | Application method, device and system of client program in cloud environment | |
| CN110740145A (en) | Message consumption method, device, storage medium and electronic equipment | |
| CN103001815A (en) | Method, device and system for acquiring test data | |
| CN111858083A (en) | Remote service calling method and device, electronic equipment and storage medium | |
| CN112769651A (en) | TCP connection detection method and device and electronic equipment | |
| CN107645476B (en) | Request processing method and device | |
| US10769174B2 (en) | Site-consolidated disaster-recovery with synchronous-to-asynchronous traffic conversion | |
| CN115039392A (en) | Message processing method, device and system and server | |
| EP4030776A1 (en) | Method and apparatus for triggering vomci function from olt to send omci messages | |
| US9178960B2 (en) | Recovering resource connections | |
| CN114297062A (en) | Service testing method and device, electronic equipment and storage medium | |
| CN111737028B (en) | Dubbo service detection method and device | |
| CN107657053A (en) | A kind of reptile implementation method and device | |
| CN114615248A (en) | Remote operation control method and device, electronic equipment and storage medium | |
| CN112416698B (en) | Expansion method and device of monitoring system, storage medium and electronic equipment | |
| CN114217911A (en) | Cross-chain transaction processing method, device, computing equipment and medium | |
| US8640143B2 (en) | Method and system for providing preemptive response routing | |
| CN113556392A (en) | Communication system, method, device and storage medium | |
| CN112766486A (en) | Searching method of neural network structure, terminal, server and readable storage medium | |
| JP5353891B2 (en) | Distributed processing system, distributed processing method and program |
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 |
Effective date of registration: 20220208 Address after: 100007 room 205-32, floor 2, building 2, No. 1 and No. 3, qinglonghutong a, Dongcheng District, Beijing Applicant after: Tianyiyun Technology Co.,Ltd. Address before: No.31, Financial Street, Xicheng District, Beijing, 100033 Applicant before: CHINA TELECOM Corp.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |