WO2017012383A1 - 一种服务注册方法、使用方法及相关装置 - Google Patents

一种服务注册方法、使用方法及相关装置 Download PDF

Info

Publication number
WO2017012383A1
WO2017012383A1 PCT/CN2016/080408 CN2016080408W WO2017012383A1 WO 2017012383 A1 WO2017012383 A1 WO 2017012383A1 CN 2016080408 W CN2016080408 W CN 2016080408W WO 2017012383 A1 WO2017012383 A1 WO 2017012383A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
node
service providing
registration
providing node
Prior art date
Application number
PCT/CN2016/080408
Other languages
English (en)
French (fr)
Inventor
周海锋
李龙
袁健清
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP16827074.2A priority Critical patent/EP3319270B1/en
Publication of WO2017012383A1 publication Critical patent/WO2017012383A1/zh
Priority to US15/876,202 priority patent/US10979317B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/08—Allotting numbers to messages; Counting characters, words or messages
    • 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/10—Protocols in which an application is distributed across nodes in the network

Definitions

  • the present invention relates to the field of distributed network technologies, and in particular, to a service registration method, a usage method, and related devices.
  • Service Registry is a basic function and an important basis for service mediation and management.
  • the registration service function entity provides a registration service and a discovery interface
  • the service provider Service Provider
  • the service consumer Service Consumer
  • the service discovery interface provided by the registration service function entity queries the registration service function entity for the information of the requested service provider, and the service consumer binds to the service provider according to the information provided by the registration service function entity and invokes the required service.
  • the registration service function entity In order to avoid single point of failure, the registration service function entity is usually implemented in a distributed cluster, and due to the size of the service, some services need to deploy multiple instances, which have reliability and availability requirements.
  • a distributed system has three characteristics, namely Consistency (C), Availability (A), and Partition Tolerance (P), any network-based data sharing system. At most two of the three characteristics of data consistency, availability, and partition tolerance.
  • Embodiments of the present invention provide a service registration method, a usage method, and related devices, where a registration service function entity can perform service registration and use according to a distributed feature of a service, so as to reduce risks arising from registration and service provision, and improve a network system. performance.
  • a service registration method including:
  • the registration service node obtains network partition information, and receives a registration request of the service providing node, where the registration request carries a distributed feature of the service providing node, and the distributed feature satisfies both consistency and partition tolerance, or simultaneously Availability and partition tolerance;
  • the registration service node determines whether to permit registration of the service provided by the service providing node according to the network partition information and the distributed feature of the service providing node.
  • the registration service node determines, according to the network partition information and the distributed feature of the service providing node, whether to allow registration of the service provided by the service providing node, including :
  • the registration service node determines, according to the network partition information and the distributed feature of the service providing node, whether to allow registration of the service provided by the service providing node, including :
  • the registration service node determines, according to the network partition information and the distributed feature of the service providing node, the distributed feature of the service providing node, while satisfying consistency and partition tolerance, and the service to which the service providing node belongs Providing a node cluster with a network partition, determining to prohibit registration of the service provided by the service providing node; if it is determined that the distributed feature of the service providing node satisfies availability and partition tolerance, it is determined to allow registration of the service provided by the service providing node.
  • the registration service node acquires network partition information, including:
  • the registration service node receives the network partition information reported by the service providing node, and the network partition information is reported by the service providing node when the communication between the service providing nodes of the service provider node cluster is interrupted.
  • a method of using the service including:
  • the registration service node obtains network partition information, and receives a query request of the service use node, where the query request carries an identifier of the service used for the request;
  • the registration service node determines a service providing node that provides a service indicated by the identity of the service, and a distributed feature of the service providing node, the distributed feature simultaneously satisfies consistency and partition tolerance, or simultaneously satisfies availability And partition tolerance;
  • the registration service node determines whether to permit use of the service provided by the service providing node according to the network partition information and the distributed feature of the service providing node.
  • the registration service node determines, according to the network partition information and the distributed feature of the service providing node, whether to allow the service provided by the service providing node, including :
  • the service provided by the node is provided using the service; if the distributed feature of the service providing node is determined while satisfying availability and partition tolerance, it is determined that the service provided by the service providing node is allowed to be used.
  • the registration service node determines, according to the network partition information and the distributed feature of the service providing node, whether to allow the service provided by the service providing node, including :
  • the registration service node determines, according to the network partition information and the distributed feature of the service providing node, the distributed feature of the service providing node, while satisfying consistency and partition tolerance, and the service to which the service providing node belongs Provide a network partition in the node cluster, and determine that the network is prohibited.
  • the service provided by the node is provided by the service; if the distributed feature of the service providing node is determined while satisfying availability and partition tolerance, it is determined that the service provided by the service providing node is allowed to be used.
  • the registration service node acquires network partition information, including:
  • the registration service node receives the network partition information reported by the service providing node, and the network partition information is reported by the service providing node when the communication between the service providing nodes in the service providing node cluster belongs to the service interruption.
  • a registration service node device including:
  • An acquiring module configured to obtain network partition information, and receive a registration request of a service providing node, where the registration request carries a distributed feature of the service providing node, where the distributed feature satisfies consistency and partition tolerance, or Satisfy both availability and partition tolerance;
  • a processing module configured to determine, according to the network partition information and the distributed feature of the service providing node, whether to permit registration of the service provided by the service providing node.
  • the processing module is specifically configured to:
  • Determining when determining that the distributed feature of the service providing node satisfies consistency and partition tolerance, determining that the service provider is prohibited from registering, according to the network partition information, that the registered service node cluster belongs to the network partition.
  • a service provided by a node if it is determined that the distributed feature of the service providing node satisfies both availability and partition tolerance, it is determined to permit registration of the service provided by the service providing node.
  • the processing module is specifically configured to:
  • the partitioning determines that the service provided by the service providing node is prohibited from being registered; if it is determined that the distributed feature of the service providing node satisfies both availability and partition tolerance, it is determined to permit registration of the service provided by the service providing node.
  • the acquiring module is specifically configured to:
  • the network partition information reported by the service providing node is received, and the network partition information is reported by the service providing node when the communication between the service providing nodes of the service provider node cluster is interrupted.
  • a registration service node device including:
  • An obtaining module configured to obtain network partition information, and receive a query request of a service using node, where the query request carries an identifier of a service used by the request;
  • a determining module configured to determine a service providing node that provides a service indicated by the identifier of the service, and a distributed feature of the service providing node, the distributed feature simultaneously satisfying consistency and partition tolerance, or simultaneously satisfying Availability and partition tolerance;
  • a decision module configured to determine, according to the network partition information and the distributed feature of the service providing node, whether to use the service provided by the service providing node.
  • the determining module is specifically configured to:
  • Determining when determining that the distributed feature of the service providing node satisfies consistency and partition tolerance, determining that the service providing is provided by the service provider node according to the network partition information. A service provided by a node; if it is determined that the distributed feature of the service providing node satisfies both availability and partition tolerance, it is determined that the service provided by the service providing node is allowed to be used.
  • the determining module is specifically configured to:
  • the partitioning determines that the service provided by the service providing node is prohibited; if it is determined that the distributed feature of the service providing node satisfies both availability and partition tolerance, it is determined that the service provided by the service providing node is allowed to be used.
  • the acquiring module is specifically configured to:
  • the registration service node when the registration service node registers the service provided by the service providing node, the distributed feature of the service providing node and the network partition information are obtained, according to the network partition information and the distributed of the service providing node.
  • the service providing nodes of different distributed features can be separately processed, and the distributed features of the service providing nodes are not distinguished in the network partitioning scenario, and the services of the AP service providing nodes cannot be registered, and the CP services are provided.
  • the problem of the node providing the service to generate the risk reduces the risk of the registration service node registering and providing the service, and improves the performance of the network system.
  • Figure 1 is a schematic diagram of a service-oriented architecture and a service architecture
  • FIG. 2 is a schematic diagram of a CP class registration service partition scenario
  • FIG. 3 is a schematic diagram of a scenario 2 of a CP class service registration partition
  • FIG. 4 is a schematic diagram of a scenario of an AP class service registration partition
  • FIG. 5 is a schematic flowchart of a method for registering a service node to perform service registration according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of service registration and use according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a service system according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of another service system according to an embodiment of the present invention.
  • FIG. 9 is a schematic flowchart of a method for a service provided by a registration service node according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a device for registering a service node according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of another registration service node device according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of another registration service node device according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of another registration service node device according to an embodiment of the present invention.
  • CAP theory the consistency of distributed systems means that all nodes have the same data at the same time; availability means that each request responds with success or failure; partition tolerance refers to the case of network partitions. Separate systems are each capable of functioning properly. Due to hardware limitations, the current network will certainly have problems such as delays and packet loss, so partition tolerance must be guaranteed. Therefore, services under the High Availability (HA) architecture emphasize consistent CP-type services, or AP-class services that emphasize usability, where CP-type services are defined to satisfy C and P characteristics and are not required to satisfy A-features. Service, AP class service is defined as a service that satisfies the A and P characteristics and does not require the C feature to be satisfied.
  • HA High Availability
  • Registration services with C and P characteristics (for example, zookeeper, etcd, doozer, etc.), referred to as CP registration services, emphasize data consistency, and the service provider guarantees registration of the service cluster after requesting registration from a registered service node in the registration service cluster.
  • the service data registered on each registered service node is consistent.
  • the CP class registration service generally uses the paxos, zab or raft protocol to achieve strong consistency of data.
  • the protocol principle can be summarized as: a registration service node acting as a leader in the registration service cluster, and determining any registered service node in the cluster. When a data change occurs, other registered service nodes in the cluster are instructed to perform corresponding data updates to ensure the consistency of the service data held by each registered service node in the cluster.
  • the CP-type registration service clusters have the following two partition scenarios when performing network partitioning.
  • Partition scenario 1 if the registration service node acting as the Leader role is located in the arbitration On the quorum side, the service providing node in the arbitration partition may perform service registration at the registration service node in the arbitration partition, and the service use node in the arbitration partition may query the service at the registration service node in the arbitration partition. Since the registration service node that does not play the role of the leader in the non-quorum side cannot maintain the consistency between the registered service nodes in the non-arbitrated partition, the service providing node in the non-arbitrated partition cannot perform the service. Registration service, service use node can not perform service query.
  • the arbitration partition refers to the partition with the largest number of registered service nodes, and the other partitions except the arbitration partition are called non-arbitrated partitions.
  • Partition scenario 2 as shown in FIG. 3, if the registration service node acting as the Leader role is located in the non-arbitration partition, the registration service node loses the arbitration function, so that the service providing node cannot register the service on the registration service node in the non-arbitration partition, but The service usage node can still query the service at the registration service node in the non-arbitrated partition. Selecting a new Leader role from each of the registered service nodes in the arbitration partition can maintain consistency between the registered service nodes in the arbitration partition. Therefore, the service providing node in the arbitration partition can perform registration service and service use. Nodes can also perform service queries.
  • the CP service provider node and the AP service provider node are not distinguished, and the AP service provider node cannot perform service registration and provide external services.
  • 2 and the AP class service in the non-arbitrated partition in FIG. 3 provides the node B.
  • AP class registration services emphasize the availability at the expense of consistency. There is no consistency protocol. There is no complicated process that requires the role of the leader to initiate a vote to determine whether to refresh the data.
  • the AP class registration service The node can receive a registration request to process the service providing node, and process the query request of the service using node.
  • the AP class registration service node still supports the CP class service providing node in each partition.
  • the registration service nodes in the respective groups perform service registration, which will result in inconsistency of data held by each partition, so that the CP service providing node is at risk of providing external services.
  • the CP class service provides node A, and the CP class service provider node A is divided into different partitions. Since the AP class registration service node in each partition emphasizes the availability, the CP class service provides the node A in the partition where it is located.
  • the registration service node registers and provides services, which may cause the service data provided by the CP class service providing nodes in different partitions to be inconsistent, posing a risk.
  • the detailed method flow of the registration service node for service registration is as follows:
  • Step 501 The registration service node acquires network partition information, and receives a registration request of the service providing node, where the registration request carries a distributed feature of the service providing node.
  • the distributed feature is a CP feature that satisfies both the consistency C and the partition tolerance P, or an AP feature that satisfies both the availability A and the partition tolerance P.
  • a parameter type is added to the registration interface of the registration service node, and the value of the parameter type is an AP or a CP;
  • the service providing node carries its own distributed feature, that is, an AP, in the registration request sent to the registration service node.
  • the distributed feature is determined according to a design goal formulated by the designer;
  • the registration service node receives the registration request of the service providing node through the registration interface, and determines the value of the parameter type according to the distributed feature carried in the registration request.
  • the AP-type service providing node carries the distributed feature AP in the registration request
  • the CP-type service providing node carries the distributed feature CP in the registration request
  • the distributed feature of the service providing node is obtained by registering the type parameter of the interface. Passed to the registration service node.
  • Step 502 The registration service node determines, according to the network partition information and the distributed feature of the service providing node, whether to permit registration of the service provided by the service providing node.
  • the registration service node has the following two methods for determining whether to allow the service provided by the service providing node to be registered according to different network partition information, as follows:
  • a first mode when the registration service node determines, according to the network partition information, that the registered service node cluster to which the registration service node belongs has a network partition, if it is determined that the distributed feature of the service providing node is a CP feature, determining that the registration is prohibited Said service provides the services provided by the node;
  • the distributed feature of the service providing node is an AP feature, and it is determined that the service provided by the service providing node is allowed to be registered.
  • each registered service node in the cluster of registered service nodes monitors whether communication between the connected registered service nodes is interrupted, and if the registration service node in the registered service node cluster is interrupted, the registration is determined.
  • the service node cluster has a network partition, and each registered service node in the registered service node cluster obtains network partition information, which is used to indicate that the registered service node cluster has a network partition.
  • the registration service node detects a communication interruption with another registered service node in the cluster of registered service nodes to generate the network partition information; or the registration service node receives another registration in the cluster of registered service nodes to which it belongs.
  • the network partition information sent by the service node the network partition information being generated when the other registration service node detects that communication is interrupted between the connected service registration node.
  • a registration interface is set on each registration service node in the registration service node cluster, and host 1, host 2, and host 3 form an AP class service provider node cluster, and host 4, host 5, and host 6 constitute a CP class service provider node cluster.
  • the AP class service providing node carries the parameter AP in the sent registration request, and the parameter is passed to the registration service node by using the type parameter of the registration interface.
  • the CP service providing node carries the parameter CP in the sent registration request, and the parameter is passed to the registration service node by the type parameter of the registration interface.
  • the registration service node 1, the registration service node 2, and the registration service node 3 are sequentially connected, and each registration service node monitors whether communication with the connected registration service node is interrupted, and if one of the registration service nodes detects the connection with the connection If the communication between the service nodes is interrupted, it is determined that the registered service node cluster has a network partition, and the registered service node in each partition allows registration of the service provided by the AP class service providing node, prohibits registration of the service provided by the CP class service providing node, and prohibits Use the CP class service to provide the services provided by the node.
  • the registration service node determines, according to the network partition information and the distributed feature of the service providing node, a distributed feature of the service providing node as a CP feature and a service to which the service providing node belongs.
  • Providing a network cluster of the node cluster determining that registration of the service provided by the service providing node is prohibited; and determining that the distributed feature of the service providing node is an AP
  • the levy determines that the service provided by the service providing node is allowed to be registered.
  • the registration service node receives the network partition information reported by the service providing node, and the network partition information is determined by the service providing node to determine a service providing node of the service providing node cluster where the service providing node is located. Reported when communication is interrupted.
  • each service providing node sets a registration service proxy function, and the service providing nodes belonging to the same cluster are sequentially connected, for example, the host 1, the host 2, and the host 3 form an AP class service providing node.
  • the cluster, the host 1, the host 2, and the registration service agent on the host 3 are connected in turn.
  • the host 4, the host 5, and the host 6 form a CP-type service providing node cluster, and the host 4, the host 5, and the registration service agent on the host 6 are sequentially connected.
  • the service providing node monitors whether the communication between the connected service providing nodes is interrupted by the registration service proxy function, and if a service providing node monitors the communication interruption between the connected service providing node through the registration service proxy function, Then determine that the cluster where the service provider node is located has a network partition.
  • the service providing node reports the identity of the service providing node of the network partition and the distributed feature to the registration service node by using the registration service proxy function.
  • the registration service node determines that the distributed feature of the service providing node of the network partition is a CP feature, it refuses to register the service provided by the service providing node, and prohibits the use of the service provided by the service providing node.
  • the detailed method flow for the registration service node to provide the requested service for the service using node is as follows:
  • Step 901 The registration service node acquires network partition information, and receives a query request of the service use node, where the query request carries an identifier of the service used for the request.
  • the registration service node stores a correspondence between the identifier of the service and the service provider that provides the service and the distributed feature.
  • Step 902 The registration service node determines a service providing node that provides the service indicated by the identity of the service, and a distributed feature of the service providing node.
  • the distributed feature is a CP feature that satisfies both the consistency C and the partition tolerance P, or an AP feature that satisfies both the availability A and the partition tolerance P.
  • Step 903 The registration service node is configured according to the network partition information and the service providing node.
  • the distributed feature determines whether the service provided by the service providing node is allowed to be used.
  • the registration service node has the following two methods for determining whether to allow the service provided by the service providing node according to different network partition information, as follows:
  • the registration service node determines, according to the network partition information, that a network partition of a registered service node cluster to which the registration service node belongs is determined to be prohibited if the distributed feature of the service providing node is a CP feature.
  • the service provides a service provided by the node; if it is determined that the distributed feature of the service providing node is an AP feature, it is determined that the service provided by the service providing node is allowed to be used.
  • each of the registered service node clusters monitors whether communication between the registered service nodes is interrupted, and if the communication between the registered service nodes in the registered service node cluster is interrupted, the registration is determined.
  • the service node cluster has a network partition, and each registered service node in the registered service node cluster obtains network partition information, which is used to indicate that the registered service node cluster has a network partition.
  • the registration service node detects a communication interruption with another registered service node in the cluster of registered service nodes to generate the network partition information; or the registration service node receives another registration in the cluster of registered service nodes to which it belongs.
  • the network partition information sent by the service node the network partition information being generated when the other registration service node detects that communication is interrupted between the connected service registration node.
  • the registration service node determines, according to the network partition information and the distributed feature of the service providing node, that the distributed feature of the service providing node is a CP feature and the service provided by the service providing node belongs to
  • the node cluster has a network partition, and it is determined that the service provided by the service providing node is prohibited. If it is determined that the distributed feature of the service providing node is an AP feature, it is determined that the service provided by the service providing node is allowed to be used.
  • the registration service node receives the network partition information reported by the service providing node, where the network partition information is determined by the service providing node to be between service providing nodes in a cluster of service providing nodes Reported when communication is interrupted.
  • the registration service node device mainly includes:
  • the obtaining module 1001 is configured to obtain network partition information, and receive a registration request of the service providing node, where the registration request carries a distributed feature of the service providing node, where the distributed feature satisfies both consistency C and partition tolerance CP characteristics of sexual P, or AP characteristics that satisfy both availability A and partition tolerance P;
  • the processing module 1002 is configured to determine, according to the network partition information and the distributed feature of the service providing node, whether to permit registration of the service provided by the service providing node.
  • processing module 1002 is specifically configured to:
  • the acquiring module detects that the communication interruption with the other registered service nodes in the cluster of registered service nodes belongs to generate the network partition information; or receives the information sent by other registered service nodes in the cluster of registered service node
  • the network partition information is generated when the other registration service node detects that communication is interrupted with the connected service registration node.
  • processing module 1002 is specifically configured to:
  • Determining registration prohibition if it is determined that the distributed feature of the service providing node is a CP feature and the service providing node cluster to which the service providing node belongs has a network partition according to the network partition information and the distributed feature of the service providing node.
  • the service provides a service provided by the node; if it is determined that the distributed feature of the service providing node is an AP feature, it is determined to permit registration of the service provided by the service providing node.
  • the obtaining module 1001 is specifically configured to:
  • the network partition information reported by the service providing node is received, and the network partition information is reported by the service providing node when the communication between the service providing nodes of the service provider node cluster is interrupted.
  • a registration service node device is provided in the embodiment of the present invention.
  • the registration service node device mainly includes a processor 1101, a memory 1102, and a communication interface 1103.
  • the memory 1102 stores a preset program
  • the processor 1101 reads a program stored in the memory 1102, and executes the following according to the program. process:
  • the network partition information is obtained through the communication interface 1103, and the registration request of the service providing node is received through the communication interface 1103, where the registration request carries the distributed feature of the service providing node, and the distributed feature satisfies the consistency C and The CP feature of the partition tolerant P, or the AP feature that satisfies both the availability A and the partition tolerance P;
  • the processor 1101 determines, according to the network partition information, that the registered service node cluster to which the registration service node belongs has a network partition, and if it is determined that the distributed feature of the service providing node is a CP feature, determining that registration is prohibited The service provides a service provided by the node; if it is determined that the distributed feature of the service providing node is an AP feature, it is determined to permit registration of the service provided by the service providing node.
  • the processor detects a communication interruption with another registered service node in the cluster of registered service nodes to generate the network partition information; or receives other registered service nodes in the cluster of registered service nodes through the communication interface.
  • the network partition information sent, the network partition information being generated when the other registration service node detects that communication is interrupted with the connected service registration node.
  • the processor 1101 determines, according to the network partition information and the distributed feature of the service providing node, that the distributed feature of the service providing node is a CP feature and the service provides a service to which the node belongs. Providing a network cluster of the node cluster, determining that the service provided by the service providing node is prohibited from being registered; and determining that the distributed feature of the service providing node is an AP feature, determining to allow registration of the service provided by the service providing node.
  • the processor 1101 receives, by using the communication interface 1103, the report reported by the service providing node.
  • the network partition information is reported by the service providing node when the communication between the service providing nodes of the service provider node cluster to which the service is provided is interrupted.
  • a registration service node device is provided in the embodiment of the present invention.
  • the registration service node device mainly includes:
  • the obtaining module 1201 is configured to obtain network partition information, and receive a query request of the service using node, where the query request carries an identifier of the service used for the request;
  • a determining module 1202 configured to determine a service providing node that provides a service indicated by the identifier of the service, and a distributed feature of the service providing node, wherein the distributed feature satisfies both the consistency C and the partition tolerance P CP characteristics, or AP characteristics that satisfy both the availability A and the partition tolerance P;
  • the decision module 1203 is configured to determine, according to the network partition information and the distributed feature of the service providing node, whether to use the service provided by the service providing node.
  • the decision module 1203 is specifically configured to:
  • the acquiring module detects that the communication interruption with the other registered service nodes in the cluster of registered service nodes belongs to generate the network partition information; or receives the information sent by other registered service nodes in the cluster of registered service node
  • the network partition information is generated when the other registration service node detects that communication is interrupted with the connected service registration node.
  • the decision module 1203 is specifically configured to:
  • the network partition information and the distributed feature of the service providing node if it is determined that the distributed feature of the service providing node is a CP feature and the service providing node belongs to the service providing node cluster, the network partition is determined, and the use is determined to be prohibited.
  • the service provides a service provided by the node; Determining that the distributed feature of the service providing node is an AP feature, and determining to allow use of the service provided by the service providing node.
  • the obtaining module 1201 is specifically configured to:
  • the network partition information reported by the service providing node is received, and the network partition information is reported by the service providing node when the communication between the service providing nodes in the service providing node cluster belongs to the service interruption.
  • the registration service node device mainly includes a processor 1301, a memory 1302, and a communication interface 1303.
  • the memory 1302 stores a preset program
  • the processor 1301 reads the program saved in the memory 1302, and executes the following according to the program. process:
  • the processor 1301 determines, according to the network partition information, that the registered service node cluster to which the registration service node belongs has a network partition, and if it is determined that the distributed feature of the service providing node is a CP feature, determining that the use of the service is prohibited The service provides a service provided by the node; if it is determined that the distributed feature of the service providing node is an AP feature, it is determined that the service provided by the service providing node is allowed to be used.
  • the processor detects a communication interruption with another registered service node in the cluster of registered service nodes to generate the network partition information; or receives other registered service nodes in the cluster of registered service nodes through the communication interface.
  • the network partition information sent, the network partition information being detected by the other registration service node and being connected to the connected service registration node Generated when the letter is interrupted.
  • the processor 1301 determines, according to the network partition information and the distributed feature of the service providing node, that the distributed feature of the service providing node is a CP feature and the service provided by the service providing node belongs to The node cluster has a network partition, and it is determined that the service provided by the service providing node is prohibited. If it is determined that the distributed feature of the service providing node is an AP feature, it is determined that the service provided by the service providing node is allowed to be used.
  • the processor 1301 receives, by using the communication interface 1303, the network partition information reported by the service providing node, where the network partition information is determined by the service providing node to determine that the service providing node in the service providing node cluster belongs to the communication interruption. Reported at the time.
  • the registration service node when the registration service node registers the service provided by the service providing node, the distributed feature of the service providing node and the network partition information are obtained, according to the network partition information and the distributed of the service providing node.
  • the service providing nodes of different distributed features can be separately processed, and the distributed features of the service providing nodes are not distinguished in the network partitioning scenario, and the services of the AP service providing nodes cannot be registered, and the CP services are provided.
  • the problem of the node providing the service to generate the risk reduces the risk of the registration service node registering and providing the service, and improves the performance of the network system.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种服务注册方法、使用方法及相关装置，用以降低在网络分区场景中，不区分服务提供节点的分布式特征，导致AP类服务提供节点的服务无法注册，以及导致CP类服务提供节点提供服务产生风险。该方法为：注册服务节点获取网络分区信息，并接收服务提供节点的注册请求，所述注册请求中携带所述服务提供节点的分布式特征，所述分布式特征同时满足一致性和分区容忍性，或者同时满足可用性和分区容忍性；所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务。

Description

一种服务注册方法、使用方法及相关装置
本申请要求在2015年07月22日提交中国专利局、申请号为201510435586.9、发明名称为“一种服务注册方法、使用方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及分布式网络技术领域，尤其涉及一种服务注册方法、使用方法及相关装置。
背景技术
面向服务的架构(service-oriented architecture，SOA)以及服务化架构中，注册服务(Service Registry)是基本的功能，是实现服务中介及管理的重要基础。如图1所示，注册服务功能实体提供注册服务与发现接口，服务提供者(Service Provider)通过注册服务功能实体提供的注册服务接口在注册服务功能实体进行服务注册，服务使用者(Service Consumer)通过注册服务功能实体提供的服务发现接口向注册服务功能实体查询请求的服务提供者的信息，服务使用者根据注册服务功能实体提供的信息与服务提供者绑定并调用所需的服务。
为了避免单点故障，通常注册服务功能实体采用分布式集群实现，并且，由于服务规模的要求，有些服务需要部署多个实例，存在可靠性以及可用性方面的要求。
根据CAP理论，分布式系统具有三个特性，分别为一致性(Consistency，简称C)、可用性(Availability，简称A)以及分区容忍性(Partition Tolerance，简称P)，任何基于网络的数据共享系统，最多只能满足数据一致性、可用性、分区容忍性三个特征中的两个。
目前，注册服务功能实体如何根据服务的分布式特征进行服务注册以及使用，以降低注册及提供服务产生的风险，并提高网络系统性能，是需要解决的问题。
发明内容
本发明实施例提供一种服务注册方法、使用方法及相关装置，用以注册服务功能实体能够根据服务的分布式特征进行服务注册以及使用，以降低注册及提供服务产生的风险，并提高网络系统性能。
本发明实施例提供的具体技术方案如下：
第一方面，提供了一种服务注册方法，包括：
注册服务节点获取网络分区信息，并接收服务提供节点的注册请求，所述注册请求中携带所述服务提供节点的分布式特征，所述分布式特征同时满足一致性和分区容忍性，或者同时满足可用性和分区容忍性；
所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务。
结合第一方面，在第一种可能的实现方式中，所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务，包括：
所述注册服务节点根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许注册所述服务提供节点提供的服务。
结合第一方面，在第二种可能的实现方式中，所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务，包括：
所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许注册所述服务提供节点提供的服务。
结合第一方面的第二种可能的实现方式，在第三种可能的实现方式中，所述注册服务节点获取网络分区信息，包括：
所述注册服务节点接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群的服务提供节点之间通信中断时上报。
第二方面，提供了一种服务使用方法，包括：
注册服务节点获取网络分区信息，并接收服务使用节点的查询请求，所述查询请求中携带请求使用的服务的标识；
所述注册服务节点确定提供所述服务的标识所指的服务的服务提供节点，以及所述服务提供节点的分布式特征，所述分布式特征同时满足一致性和分区容忍性，或者同时满足可用性和分区容忍性；
所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许使用所述服务提供节点提供的服务。
结合第二方面，在第一种可能的实现方式中，所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许使用所述服务提供节点提供的服务，包括：
所述注册服务节点根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许使用所述服务提供节点提供的服务。
结合第二方面，在第二种可能的实现方式中，所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许使用所述服务提供节点提供的服务，包括：
所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止使 用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许使用所述服务提供节点提供的服务。
结合第二方面的第二种可能的实现方式，在第三种可能的实现方式中，所述注册服务节点获取网络分区信息，包括：
所述注册服务节点接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群中的服务提供节点之间通信中断时上报。
第三方面，提供了一种注册服务节点设备，包括：
获取模块，用于获取网络分区信息，并接收服务提供节点的注册请求，所述注册请求中携带所述服务提供节点的分布式特征，所述分布式特征同时满足一致性和分区容忍性，或者同时满足可用性和分区容忍性；
处理模块，用于根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务。
结合第三方面，在第一种可能的实现方式中，所述处理模块具体用于：
根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许注册所述服务提供节点提供的服务。
结合第三方面，在第二种可能的实现方式中，所述处理模块具体用于：
根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许注册所述服务提供节点提供的服务。
结合第三方面的第二种可能的实现方式，在第三种可能的实现方式中，所述获取模块具体用于：
接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群的服务提供节点之间通信中断时上报。
第四方面，提供了一种注册服务节点设备，包括：
获取模块，用于获取网络分区信息，并接收服务使用节点的查询请求，所述查询请求中携带请求使用的服务的标识；
确定模块，用于确定提供所述服务的标识所指的服务的服务提供节点，以及所述服务提供节点的分布式特征，所述分布式特征同时满足一致性和分区容忍性，或者为同时满足可用性和分区容忍性；
决策模块，用于根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许使用所述服务提供节点提供的服务。
结合第四方面，在第一种可能的实现方式中，所述决策模块具体用于：
根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许使用所述服务提供节点提供的服务。
结合第四方面，在第二种可能的实现方式中，所述决策模块具体用于：
根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许使用所述服务提供节点提供的服务。
结合第四方面的第二种可能的实现方式，在第三种可能的实现方式中，所述获取模块具体用于：
接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群中的服务提供节点之间通信 中断时上报。
基于上述技术方案，本发明实施例中，注册服务节点为服务提供节点提供的服务进行注册时，获取该服务提供节点的分布式特征以及网络分区信息，根据网络分区信息以及服务提供节点的分布式特征，判断是否允许注册该服务提供节点提供的服务，或者，判断是否允许使用该服务提供节点所提供的服务，使得注册服务节点能够区分AP类服务提供节点和CP类服务提供节点，在存在网络分区时，能够分别处理不同分布式特征的服务提供节点，降低了在网络分区场景中，不区分服务提供节点的分布式特征，导致AP类服务提供节点的服务无法注册，以及导致CP类服务提供节点提供服务产生风险的问题，降低了注册服务节点注册及提供服务产生的风险，提高了网络系统性能。
附图说明
图1为面向服务的架构以及服务化架构示意图；
图2为CP类注册服务分区场景一示意图；
图3为CP类服务注册分区场景二示意图；
图4为AP类服务注册分区场景示意图；
图5为本发明实施例中注册服务节点进行服务注册的方法流程示意图；
图6为本发明实施例中服务注册及使用示意图；
图7为本发明实施例中服务系统架构示意图；
图8为本发明实施例中另一服务系统架构示意图；
图9为本发明实施例中注册服务节点提供服务的方法流程示意图；
图10为本发明实施例中注册服务节点设备的结构示意图；
图11为本发明实施例中另一注册服务节点设备的结构示意图；
图12为本发明实施例中另一注册服务节点设备的结构示意图；
图13为本发明实施例中另一注册服务节点设备的结构示意图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明作进一步地详细描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。
CAP理论中，分布式系统的一致性是指所有节点在同一时间具有相同的数据；可用性是指保证每个请求不管成功或者失败都有响应；分区容忍性是指在出现网络分区的情况下，分离的系统各自能够正常运行。由于受到硬件限制，当前网络肯定会出现延迟、丢包等问题，所以分区容忍性是必须要保证的。因此，高可用性集群(High Available，HA)架构下的服务强调一致性的CP类服务，或者强调可用性的AP类服务，其中，CP类服务定义为满足C和P特征且不要求满足A特征的服务，AP类服务定义为满足A和P特征且不要求满足C特征的服务。
第一方案：
具有C和P特征的注册服务(例如，zookeeper、etcd、doozer等)，简称CP类注册服务强调数据一致性，服务提供者向注册服务集群中某个注册服务节点请求注册后，保证注册服务集群中的每个注册服务节点上注册的服务数据是一致的。CP类注册服务一般使用paxos、zab或raft协议实现数据的强一致性，协议原理可概括为：注册服务集群中担当领导(Leader)角色的注册服务节点，在确定集群中的任意一个注册服务节点发生数据变更时，指示集群中的其它注册服务节点进行相应的数据更新，保证集群中的每个注册服务节点所保存的服务数据的一致性。
对于集群，网络分区是必然存在的，CP类注册服务集群在进行网络分区时存在以下两种分区场景。
分区场景一，如图2所示，若担当Leader角色的注册服务节点位于仲裁 分区(quorum side)，仲裁分区中的服务提供节点可以在仲裁分区中的注册服务节点进行服务注册，并且仲裁分区中的服务使用节点可以在仲裁分区中的注册服务节点查询服务。由于在非仲裁分区(non-quorum side)中没有担当Leader角色的注册服务节点，无法保持非仲裁分区中的各注册服务节点之间的一致性，因此，非仲裁分区中的服务提供节点无法进行注册服务，服务使用节点也不能进行服务查询。其中，仲裁分区是指包含的注册服务节点数目最多的分区，除仲裁分区之外的其它分区称为非仲裁分区。
分区场景二，如图3所示，若担当Leader角色的注册服务节点位于非仲裁分区，该注册服务节点失去仲裁功能，使得服务提供节点无法在非仲裁分区中的注册服务节点上注册服务，但是服务使用节点仍可以在非仲裁分区中的注册服务节点查询服务。从仲裁分区中的各注册服务节点中选择一个担当新的Leader角色，可以保持仲裁分区中的各注册服务节点之间的一致性，因此，仲裁分区中的服务提供节点可以进行注册服务，服务使用节点也可以进行服务查询。
发明人发现，网络分区场景一或场景二中，在CP类注册服务集群分区的场景下，非仲裁分区中的注册服务节点由于无法保证CP特性，因此，CP类服务提供节点无法进行注册，但是AP类服务提供节点是牺牲一致性而优先考虑可用性，在该场景下不区分CP类服务提供节点和AP类服务提供节点，导致AP类服务提供节点无法进行服务注册并对外提供服务，例如，图2和图3中非仲裁分区中的AP类服务提供节点B。
第二方案：
AP类注册服务(例如，eureaka、serf等)是牺牲一致性强调可用性，没有使用一致性协议，不存在需要Leader角色发起投票决定是否刷新数据的复杂流程，在网络分区场景下，AP类注册服务节点可以接收处理服务提供节点的注册请求，以及处理服务使用节点的查询请求。
发明人发现，在网络分区场景下，如果CP类服务提供节点集群被划分在不同的分区，AP类注册服务节点仍支持每个分区中的CP类服务提供节点在 各自分组中的注册服务节点进行服务注册，这将导致各分区所保存的数据不一致，使得CP类服务提供节点对外提供服务存在风险。如图4中的CP类服务提供节点A，CP类服务提供节点A被划分在不同的分区，由于每个分区中的AP类注册服务节点强调可用性，则CP类服务提供节点A能够在所在分区的注册服务节点注册并提供服务，可能使得不同分区中的CP类服务提供节点的提供的服务数据不一致，产生风险。
基于以上分析，本发明实施例中，如图5所示，注册服务节点进行服务注册的详细方法流程如下：
步骤501：注册服务节点获取网络分区信息，并接收服务提供节点的注册请求，所述注册请求中携带所述服务提供节点的分布式特征。
其中，所述分布式特征为同时满足一致性C和分区容忍性P的CP特征，或者为同时满足可用性A和分区容忍性P的AP特征。
本发明实施例中，注册服务节点的注册接口中增设参数type，该参数type的取值为AP或CP；服务提供节点在发送给注册服务节点的注册请求中携带自身的分布式特征，即AP或CP，该分布式特征根据设计人员制定的设计目标确定；注册服务节点通过注册接口接收服务提供节点的注册请求，根据该注册请求中携带的分布式特征确定参数type的取值。
如图6所示，AP类服务提供节点在注册请求中携带分布式特征AP，CP类服务提供节点在注册请求中携带分布式特征CP，通过注册接口的type参数将服务提供节点的分布式特征传递给注册服务节点。
步骤502：注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务。
具体实施中，注册服务节点根据网络分区信息的不同，有以下两种判断是否允许注册服务提供节点提供的服务的方式，具体如下：
第一种方式，注册服务节点根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征为CP特征，判定禁止注册所述服务提供节点提供的服务；若确定所 述服务提供节点的分布式特征为AP特征，判定允许注册所述服务提供节点提供的服务。
该第一种方式中，注册服务节点集群中的每个注册服务节点监测与相连接的其他注册服务节点之间的通信是否中断，若注册服务节点集群中的注册服务节点通信中断，则确定注册服务节点集群存在网络分区，注册服务节点集群中的每个注册服务节点分别获得网络分区信息，该网络分区信息用于指示注册服务节点集群存在网络分区。具体地，注册服务节点检测到与所属的注册服务节点集群中的其它注册服务节点之间的通信中断，生成所述网络分区信息；或者，注册服务节点接收所属的注册服务节点集群中的其它注册服务节点发送的所述网络分区信息，所述网络分区信息由所述其它注册服务节点检测到与相连接的服务注册节点之间通信中断时生成。
一个具体实施中，如图7所示，注册服务节点集群中的每个注册服务节点上设置注册接口，主机1、主机2和主机3组成AP类服务提供节点集群，主机4、主机5和主机6组成CP类服务提供节点集群。AP类服务提供节点在发送的注册请求中携带参数AP，该参数通过注册接口的type参数传递给注册服务节点。CP类服务提供节点在发送的注册请求中携带参数CP，该参数通过注册接口的type参数传递给注册服务节点。注册服务节点1、注册服务节点2以及注册服务节点3依次连接，每个注册服务节点监测与相连接的注册服务节点之间的通信是否中断，若有一个注册服务节点检测到与相连接的注册服务节点之间的通信中断，则确定注册服务节点集群存在网络分区，则每个分区中的注册服务节点允许注册AP类服务提供节点提供的服务，禁止注册CP类服务提供节点提供的服务以及禁止使用CP类服务提供节点提供的服务。
第二种方式，所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征为CP特征且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征为AP特 征，判定允许注册所述服务提供节点提供的服务。
该第二种方式中，注册服务节点接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定该服务提供节点所在服务提供节点集群的服务提供节点之间通信中断时上报。
一个具体实施中，如图8所示，每个服务提供节点上设置注册服务代理功能，属于同一集群的服务提供节点之间依次连接，如主机1、主机2和主机3组成AP类服务提供节点集群，主机1、主机2和主机3上的注册服务代理依次连接，主机4、主机5和主机6组成CP类服务提供节点集群，主机4、主机5和主机6上的注册服务代理依次连接。服务提供节点通过注册服务代理功能监测与相连接的其他服务提供节点之间的通信是否中断，若有一个服务提供节点通过注册服务代理功能监测到与相连接的服务提供节点之间的通信中断，则确定该服务提供节点所在的集群存在网络分区。服务提供节点通过注册服务代理功能将存在网络分区的服务提供节点的标识以及分布式特征上报给注册服务节点。注册服务节点确定存在网络分区的服务提供节点的分布式特征为CP特征时，拒绝注册该服务提供节点所提供的服务，以及禁止使用该服务提供节点所提供的服务。
基于同一原理，本发明实施例中，如图9所示，注册服务节点为服务使用节点提供所请求的服务的详细方法流程如下：
步骤901：注册服务节点获取网络分区信息，并接收服务使用节点的查询请求，所述查询请求中携带请求使用的服务的标识。
其中，注册服务节点中保存有服务的标识与提供该服务的服务提供者以及分布式特征之间的对应关系。
步骤902：注册服务节点确定提供所述服务的标识所指的服务的服务提供节点，以及所述服务提供节点的分布式特征。
其中，分布式特征为同时满足一致性C和分区容忍性P的CP特征，或者为同时满足可用性A和分区容忍性P的AP特征。
步骤903：注册服务节点根据所述网络分区信息以及所述服务提供节点的 分布式特征判断是否允许使用所述服务提供节点提供的服务。
具体实施中，注册服务节点根据网络分区信息的不同，有以下两种判断是否允许使用服务提供节点提供的服务的方式，具体如下：
第一方式，所述注册服务节点根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征为CP特征，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征为AP特征，判定允许使用所述服务提供节点提供的服务。
该第一方式中，注册服务节点集群中的每个注册服务节点监测与相连接的其他注册服务节点之间的通信是否中断，若注册服务节点集群中的注册服务节点间通信中断，则确定注册服务节点集群存在网络分区，注册服务节点集群中的每个注册服务节点分别获得网络分区信息，该网络分区信息用于指示注册服务节点集群存在网络分区。具体地，注册服务节点检测到与所属的注册服务节点集群中的其它注册服务节点之间的通信中断，生成所述网络分区信息；或者，注册服务节点接收所属的注册服务节点集群中的其它注册服务节点发送的所述网络分区信息，所述网络分区信息由所述其它注册服务节点检测到与相连接的服务注册节点之间通信中断时生成。
第二方式，所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征为CP特征且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征为AP特征，判定允许使用所述服务提供节点提供的服务。
该第二方式中，所述注册服务节点接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群中的服务提供节点之间通信中断时上报。
基于同一发明构思，本发明实施例中提供了一种注册服务节点设备，该注册服务节点设备的具体实施参见上述方法实施例中关于注册服务节点的描 述，重复之处不再赘述，如图10所示，该注册服务节点设备主要包括：
获取模块1001，用于获取网络分区信息，并接收服务提供节点的注册请求，所述注册请求中携带所述服务提供节点的分布式特征，所述分布式特征为同时满足一致性C和分区容忍性P的CP特征，或者为同时满足可用性A和分区容忍性P的AP特征；
处理模块1002，用于根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务。
在一个具体实施中，所述处理模块1002具体用于：
根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征为CP特征，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征为AP特征，判定允许注册所述服务提供节点提供的服务。
其中，获取模块检测到与所属的注册服务节点集群中的其它注册服务节点之间的通信中断，生成所述网络分区信息；或者，接收所属的注册服务节点集群中的其它注册服务节点发送的所述网络分区信息，所述网络分区信息由所述其它注册服务节点检测到与相连接的服务注册节点之间通信中断时生成。
在另一个具体实施中，所述处理模块1002具体用于：
根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征为CP特征且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征为AP特征，判定允许注册所述服务提供节点提供的服务。
其中，所述获取模块1001具体用于：
接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群的服务提供节点之间通信中断时上报。
基于同一发明构思，本发明实施例中提供了一种注册服务节点设备，该注册服务节点设备的具体实施参见上述方法实施例中关于注册服务节点的描述，重复之处不再赘述，如图11所示，该注册服务节点设备主要包括处理器1101、存储器1102和通信接口1103，其中，存储器1102中保存有预设的程序，处理器1101读取存储器1102中保存的程序，按照该程序执行以下过程：
通过通信接口1103获取网络分区信息，并通过通信接口1103接收服务提供节点的注册请求，所述注册请求中携带所述服务提供节点的分布式特征，所述分布式特征为同时满足一致性C和分区容忍性P的CP特征，或者为同时满足可用性A和分区容忍性P的AP特征；
根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务。
在一个具体实施中，处理器1101根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征为CP特征，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征为AP特征，判定允许注册所述服务提供节点提供的服务。
其中，处理器检测到与所属的注册服务节点集群中的其它注册服务节点之间的通信中断，生成所述网络分区信息；或者，通过通信接口接收所属的注册服务节点集群中的其它注册服务节点发送的所述网络分区信息，所述网络分区信息由所述其它注册服务节点检测到与相连接的服务注册节点之间通信中断时生成。
在另一个具体实施中，处理器1101根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征为CP特征且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征为AP特征，判定允许注册所述服务提供节点提供的服务。
其中，处理器1101通过通信接口1103接收所述服务提供节点上报的所 述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群的服务提供节点之间通信中断时上报。
基于同一发明构思，本发明实施例中提供了一种注册服务节点设备，该注册服务节点设备的具体实施参见上述方法实施例中关于注册服务节点的描述，重复之处不再赘述，如图12所示，该注册服务节点设备主要包括：
获取模块1201，用于获取网络分区信息，并接收服务使用节点的查询请求，所述查询请求中携带请求使用的服务的标识；
确定模块1202，用于确定提供所述服务的标识所指的服务的服务提供节点，以及所述服务提供节点的分布式特征，所述分布式特征为同时满足一致性C和分区容忍性P的CP特征，或者为同时满足可用性A和分区容忍性P的AP特征；
决策模块1203，用于根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许使用所述服务提供节点提供的服务。
一个具体实施中，所述决策模块1203具体用于：
根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征为CP特征，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征为AP特征，判定允许使用所述服务提供节点提供的服务。
其中，获取模块检测到与所属的注册服务节点集群中的其它注册服务节点之间的通信中断，生成所述网络分区信息；或者，接收所属的注册服务节点集群中的其它注册服务节点发送的所述网络分区信息，所述网络分区信息由所述其它注册服务节点检测到与相连接的服务注册节点之间通信中断时生成。
另一个具体实施中，所述决策模块1203具体用于：
根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征为CP特征且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止使用所述服务提供节点提供的服务；若 确定所述服务提供节点的分布式特征为AP特征，判定允许使用所述服务提供节点提供的服务。
其中，所述获取模块1201具体用于：
接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群中的服务提供节点之间通信中断时上报。
基于同一发明构思，本发明实施例中提供了一种注册服务节点设备，该注册服务节点设备的具体实施参见上述方法实施例中关于注册服务节点的描述，重复之处不再赘述，如图13所示，该注册服务节点设备主要包括处理器1301、存储器1302和通信接口1303，其中，存储器1302中保存有预设的程序，处理器1301读取存储器1302中保存的程序，按照该程序执行以下过程：
通过通信接口1303获取网络分区信息，并接收服务使用节点的查询请求，所述查询请求中携带请求使用的服务的标识；
确定提供所述服务的标识所指的服务的服务提供节点，以及所述服务提供节点的分布式特征，所述分布式特征为同时满足一致性C和分区容忍性P的CP特征，或者为同时满足可用性A和分区容忍性P的AP特征；
根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许使用所述服务提供节点提供的服务。
一个具体实施中，处理器1301根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征为CP特征，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征为AP特征，判定允许使用所述服务提供节点提供的服务。
其中，处理器检测到与所属的注册服务节点集群中的其它注册服务节点之间的通信中断，生成所述网络分区信息；或者，通过通信接口接收所属的注册服务节点集群中的其它注册服务节点发送的所述网络分区信息，所述网络分区信息由所述其它注册服务节点检测到与相连接的服务注册节点之间通 信中断时生成。
另一个具体实施中，处理器1301根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征为CP特征且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征为AP特征，判定允许使用所述服务提供节点提供的服务。
其中，处理器1301通过通信接口1303接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群中的服务提供节点之间通信中断时上报。
基于上述技术方案，本发明实施例中，注册服务节点为服务提供节点提供的服务进行注册时，获取该服务提供节点的分布式特征以及网络分区信息，根据网络分区信息以及服务提供节点的分布式特征，判断是否允许注册该服务提供节点提供的服务，或者，判断是否允许使用该服务提供节点所提供的服务，使得注册服务节点能够区分AP类服务提供节点和CP类服务提供节点，在存在网络分区时，能够分别处理不同分布式特征的服务提供节点，降低了在网络分区场景中，不区分服务提供节点的分布式特征，导致AP类服务提供节点的服务无法注册，以及导致CP类服务提供节点提供服务产生风险的问题，降低了注册服务节点注册及提供服务产生的风险，提高了网络系统性能。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (16)

  1. 一种服务注册方法，其特征在于，包括：
    注册服务节点获取网络分区信息，并接收服务提供节点的注册请求，所述注册请求中携带所述服务提供节点的分布式特征，所述分布式特征同时满足一致性和分区容忍性，或者同时满足可用性和分区容忍性；
    所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务。
  2. 如权利要求1所述的方法，其特征在于，所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务，包括：
    所述注册服务节点根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许注册所述服务提供节点提供的服务。
  3. 如权利要求1所述的方法，其特征在于，所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务，包括：
    所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许注册所述服务提供节点提供的服务。
  4. 如权利要求3所述的方法，其特征在于，所述注册服务节点获取网络分区信息，包括：
    所述注册服务节点接收所述服务提供节点上报的所述网络分区信息，所 述网络分区信息由所述服务提供节点确定所属的服务提供节点集群的服务提供节点之间通信中断时上报。
  5. 一种服务使用方法，其特征在于，包括：
    注册服务节点获取网络分区信息，并接收服务使用节点的查询请求，所述查询请求中携带请求使用的服务的标识；
    所述注册服务节点确定提供所述服务的标识所指的服务的服务提供节点，以及所述服务提供节点的分布式特征，所述分布式特征同时满足一致性和分区容忍性，或者同时满足可用性和分区容忍性；
    所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许使用所述服务提供节点提供的服务。
  6. 如权利要求5所述的方法，其特征在于，所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许使用所述服务提供节点提供的服务，包括：
    所述注册服务节点根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许使用所述服务提供节点提供的服务。
  7. 如权利要求5所述的方法，其特征在于，所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许使用所述服务提供节点提供的服务，包括：
    所述注册服务节点根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许使用所述服务提供节点提供的服务。
  8. 如权利要求7所述的方法，其特征在于，所述注册服务节点获取网络 分区信息，包括：
    所述注册服务节点接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群中的服务提供节点之间通信中断时上报。
  9. 一种注册服务节点设备，其特征在于，包括：
    获取模块，用于获取网络分区信息，并接收服务提供节点的注册请求，所述注册请求中携带所述服务提供节点的分布式特征，所述分布式特征同时满足一致性和分区容忍性，或者同时满足可用性和分区容忍性；
    处理模块，用于根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许注册所述服务提供节点提供的服务。
  10. 如权利要求9所述的设备，其特征在于，所述处理模块具体用于：
    根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许注册所述服务提供节点提供的服务。
  11. 如权利要求9所述的设备，其特征在于，所述处理模块具体用于：
    根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止注册所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许注册所述服务提供节点提供的服务。
  12. 如权利要求11所述的设备，其特征在于，所述获取模块具体用于：
    接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群的服务提供节点之间通信中断时上报。
  13. 一种注册服务节点设备，其特征在于，包括：
    获取模块，用于获取网络分区信息，并接收服务使用节点的查询请求，所述查询请求中携带请求使用的服务的标识；
    确定模块，用于确定提供所述服务的标识所指的服务的服务提供节点，以及所述服务提供节点的分布式特征，所述分布式特征同时满足一致性和分区容忍性，或者为同时满足可用性和分区容忍性；
    决策模块，用于根据所述网络分区信息以及所述服务提供节点的分布式特征判断是否允许使用所述服务提供节点提供的服务。
  14. 如权利要求13所述的设备，其特征在于，所述决策模块具体用于：
    根据所述网络分区信息确定所述注册服务节点所属的注册服务节点集群存在网络分区时，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许使用所述服务提供节点提供的服务。
  15. 如权利要求13所述的设备，其特征在于，所述决策模块具体用于：
    根据所述网络分区信息以及所述服务提供节点的分布式特征，若确定所述服务提供节点的分布式特征同时满足一致性和分区容忍性且所述服务提供节点所属的服务提供节点集群存在网络分区，判定禁止使用所述服务提供节点提供的服务；若确定所述服务提供节点的分布式特征同时满足可用性和分区容忍性，判定允许使用所述服务提供节点提供的服务。
  16. 如权利要求15所述的设备，其特征在于，所述获取模块具体用于：
    接收所述服务提供节点上报的所述网络分区信息，所述网络分区信息由所述服务提供节点确定所属的服务提供节点集群中的服务提供节点之间通信中断时上报。
PCT/CN2016/080408 2015-07-22 2016-04-27 一种服务注册方法、使用方法及相关装置 WO2017012383A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16827074.2A EP3319270B1 (en) 2015-07-22 2016-04-27 Service registration method, usage method and relevant apparatus
US15/876,202 US10979317B2 (en) 2015-07-22 2018-01-22 Service registration method and usage method, and related apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510435586.9A CN106375102B (zh) 2015-07-22 2015-07-22 一种服务注册方法、使用方法及相关装置
CN201510435586.9 2015-07-22

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/876,202 Continuation US10979317B2 (en) 2015-07-22 2018-01-22 Service registration method and usage method, and related apparatus

Publications (1)

Publication Number Publication Date
WO2017012383A1 true WO2017012383A1 (zh) 2017-01-26

Family

ID=57833584

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/080408 WO2017012383A1 (zh) 2015-07-22 2016-04-27 一种服务注册方法、使用方法及相关装置

Country Status (4)

Country Link
US (1) US10979317B2 (zh)
EP (1) EP3319270B1 (zh)
CN (1) CN106375102B (zh)
WO (1) WO2017012383A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108390766A (zh) * 2017-10-25 2018-08-10 国云科技股份有限公司 一种适用于微服务的服务注册与发现方法
CN115914403A (zh) * 2022-11-16 2023-04-04 中国工商银行股份有限公司 分布式服务注册处理方法及装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107612727B (zh) * 2017-09-14 2019-01-25 掌阅科技股份有限公司 分布式健康检查方法、计算设备及计算机存储介质
CN109842637B (zh) * 2017-11-24 2021-09-07 武汉斗鱼网络科技有限公司 一种分布式服务注册方法及装置
CN108366086A (zh) * 2017-12-25 2018-08-03 聚好看科技股份有限公司 一种控制业务处理的方法及装置
CN113726902B (zh) * 2021-09-02 2023-05-23 马上消费金融股份有限公司 微服务的调用方法、系统、服务器、设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103297493A (zh) * 2012-02-15 2013-09-11 国际商业机器公司 有分区意识服务质量特征
CN103703464A (zh) * 2011-06-23 2014-04-02 森普利维蒂公司 用于分布式配置管理的方法及装置
US20140095813A1 (en) * 2012-10-03 2014-04-03 Microsoft Corporation Configurable and tunable data store tradeoffs
US20150117274A1 (en) * 2013-05-14 2015-04-30 Telefonaktiebolaget L M Ericsson (Publ) Network Node and Method Therein for HARQ Processes in a D2D Communication

Family Cites Families (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5790785A (en) * 1995-12-11 1998-08-04 Customer Communications Group, Inc. World Wide Web registration information processing system
JP4567469B2 (ja) * 2005-01-07 2010-10-20 富士通株式会社 ネットワークに於ける情報共有システム
AU6410699A (en) * 1998-10-13 2000-05-01 Chris Cheah Method and system for controlled distribution of information over a network
GB2368692B (en) * 1999-06-25 2003-02-12 Jacobs Rimell Ltd Automated provisioning system
US6363065B1 (en) * 1999-11-10 2002-03-26 Quintum Technologies, Inc. okApparatus for a voice over IP (voIP) telephony gateway and methods for use therein
US8843617B2 (en) * 2000-03-01 2014-09-23 Printeron Inc. Multi-stage polling mechanism and system for the transmission and processing control of network resource data
CA2299824C (en) * 2000-03-01 2012-02-21 Spicer Corporation Network resource control system
JP2004519024A (ja) * 2000-09-08 2004-06-24 ゴー アヘッド ソフトウェア インコーポレイテッド 多数のノードを含むクラスタを管理するためのシステム及び方法
WO2002039356A1 (en) * 2000-11-01 2002-05-16 Mark Landesmann System and method for granting deposit-contingent e-mailing rights
US20030074206A1 (en) * 2001-03-23 2003-04-17 Restaurant Services, Inc. System, method and computer program product for utilizing market demand information for generating revenue
US7660887B2 (en) * 2001-09-07 2010-02-09 Sun Microsystems, Inc. Systems and methods for providing dynamic quality of service for a distributed system
US7756969B1 (en) * 2001-09-07 2010-07-13 Oracle America, Inc. Dynamic provisioning of identification services in a distributed system
US7818409B2 (en) * 2002-01-22 2010-10-19 Alcatel-Lucent Usa Inc. Dynamic virtual private network system and methods
US7702726B1 (en) * 2002-04-10 2010-04-20 3Com Corporation System and methods for providing presence services in IP network
JP2004118327A (ja) * 2002-09-24 2004-04-15 Sony Corp コンテンツ使用制御装置及びコンテンツ使用制御方法、並びにコンピュータ・プログラム
EP1705829B2 (en) * 2003-12-05 2016-09-28 ZTE Corporation System for realizing softswitch allopatric disaster recovery based on packet network
US7908313B2 (en) * 2004-07-21 2011-03-15 The Mathworks, Inc. Instrument-based distributed computing systems
CN1852136A (zh) * 2005-07-19 2006-10-25 华为技术有限公司 一种注册/注销系统和注册/注销方法
US8296413B2 (en) * 2006-05-31 2012-10-23 Sap Ag Device registration in a hierarchical monitor service
WO2008144772A1 (en) * 2007-05-24 2008-11-27 Arpu, Inc. Subscription promotion and management system and method
JP2011170804A (ja) * 2010-02-22 2011-09-01 Canon Inc ネットワークプリントシステム、ネットワークプリントシステム制御方法、およびそのプログラム
MX2012010363A (es) * 2010-03-09 2012-11-30 Interdigital Patent Holdings Metodo y aparato para soportar comunicaciones de maquina a maquina.
US9015126B2 (en) * 2010-05-22 2015-04-21 Nokia Corporation Method and apparatus for eventually consistent delete in a distributed data store
US8447909B2 (en) * 2010-07-19 2013-05-21 International Business Machines Corporation Register access in distributed virtual bridge environment
US8589515B2 (en) * 2010-07-21 2013-11-19 International Business Machines Corporation Aggregated widget request processing
US9806965B2 (en) * 2010-09-29 2017-10-31 Avaya Inc. Automatic user redundancy determination
CN102025550A (zh) * 2010-12-20 2011-04-20 中兴通讯股份有限公司 一种分布式集群中数据管理的系统和方法
US8572290B1 (en) * 2011-05-02 2013-10-29 Board Of Supervisors Of Louisiana State University And Agricultural And Mechanical College System and architecture for robust management of resources in a wide-area network
ES2723781T3 (es) * 2011-08-03 2019-09-02 Amadeus Sas Método y sistema para mantener consistencia fuerte de contenidos replicados distribuidos en un sistema de cliente/servidor
CN103188326A (zh) * 2011-12-29 2013-07-03 张亮 一种增强soa可生存性的降级服务替换验证技术
US20140101298A1 (en) * 2012-10-05 2014-04-10 Microsoft Corporation Service level agreements for a configurable distributed storage system
US20140280595A1 (en) * 2013-03-15 2014-09-18 Polycom, Inc. Cloud Based Elastic Load Allocation for Multi-media Conferencing
CN103183326A (zh) 2013-04-18 2013-07-03 枣庄市鑫泰水处理技术有限公司 化学废渣生产亚磷酸晶体的生产工艺
US9237074B1 (en) * 2013-05-08 2016-01-12 Amazon Technologies, Inc. Distributed identifier generation system
US9686121B2 (en) * 2013-09-23 2017-06-20 Amazon Technologies, Inc. Client-premise resource control via provider-defined interfaces
US10594794B2 (en) * 2013-10-08 2020-03-17 Iotic Labs Limited Method and apparatus for synthesizing data feeds for internet of things
US20150120473A1 (en) * 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Vendor-facilitated guaranty provisioning
US11127030B2 (en) * 2013-12-04 2021-09-21 Cameron Torabi Systems and methods for collecting and distributing products information
US20170230350A1 (en) * 2014-05-29 2017-08-10 Tecteco Security Systems, S.L. Network element and method for improved user authentication in communication networks
US9646022B2 (en) * 2014-06-06 2017-05-09 Panzura, Inc. Distributed change notifications for a distributed filesystem
US9805056B2 (en) * 2014-06-24 2017-10-31 Panzura, Inc. Synchronizing file updates between two cloud controllers of a distributed filesystem
US10021186B2 (en) * 2014-12-19 2018-07-10 Microsoft Technology Licensing, Llc Guaranteed delivery of replication message
US9729480B2 (en) * 2015-02-04 2017-08-08 Kno2 Llc Interoperable clinical document-exchange system
US10252145B2 (en) * 2016-05-02 2019-04-09 Bao Tran Smart device
US10516756B1 (en) * 2016-06-09 2019-12-24 Amazon Technologies, Inc. Selection of a distributed network service
DE102016215917A1 (de) * 2016-08-24 2018-03-01 Siemens Aktiengesellschaft Gesichertes Verarbeiten einer Berechtigungsnachweisanfrage

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103703464A (zh) * 2011-06-23 2014-04-02 森普利维蒂公司 用于分布式配置管理的方法及装置
CN103297493A (zh) * 2012-02-15 2013-09-11 国际商业机器公司 有分区意识服务质量特征
US20140095813A1 (en) * 2012-10-03 2014-04-03 Microsoft Corporation Configurable and tunable data store tradeoffs
US20150117274A1 (en) * 2013-05-14 2015-04-30 Telefonaktiebolaget L M Ericsson (Publ) Network Node and Method Therein for HARQ Processes in a D2D Communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3319270A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108390766A (zh) * 2017-10-25 2018-08-10 国云科技股份有限公司 一种适用于微服务的服务注册与发现方法
CN115914403A (zh) * 2022-11-16 2023-04-04 中国工商银行股份有限公司 分布式服务注册处理方法及装置

Also Published As

Publication number Publication date
US20180145890A1 (en) 2018-05-24
CN106375102A (zh) 2017-02-01
EP3319270A4 (en) 2018-07-25
EP3319270B1 (en) 2019-12-04
EP3319270A1 (en) 2018-05-09
US10979317B2 (en) 2021-04-13
CN106375102B (zh) 2019-08-27

Similar Documents

Publication Publication Date Title
WO2017012383A1 (zh) 一种服务注册方法、使用方法及相关装置
US11463316B2 (en) Topology explorer
US11252060B2 (en) Data center traffic analytics synchronization
US10574513B2 (en) Handling controller and node failure scenarios during data collection
US10411951B2 (en) Network policy conflict detection and resolution
US9307017B2 (en) Member-oriented hybrid cloud operating system architecture and communication method thereof
US10657119B1 (en) Fleet node management system
WO2018036103A1 (zh) 虚拟机创建方法、系统以及主机
WO2016192408A1 (zh) 集群系统中节点的故障检测方法和装置
US20170163478A1 (en) Method,electronic device and system for updating client configuration in key-value pair database
JP6888078B2 (ja) ネットワーク機能ｎｆ管理方法及びｎｆ管理装置
WO2017152860A1 (zh) 一种心跳信息发送方法、装置及心跳发送节点
CN110710160A (zh) 生成用于网络策略分析的全网络逻辑模型
US20200125453A1 (en) Systems and methods for cross-regional back up of distributed databases on a cloud service
WO2019154175A1 (zh) 一种访问资源服务的方法及系统
CN111030932B (zh) 一种数据报文锚定的方法、装置及系统
US20160112288A1 (en) Providing a data set for tracking and diagnosing datacenter issues
WO2017206562A1 (zh) 一种数据表的处理方法、装置及系统
US11263184B1 (en) Partition splitting in a distributed database
US20220405104A1 (en) Cross platform and platform agnostic accelerator remoting service
CN107615872B (zh) 一种释放连接的方法、装置及系统
US9798633B2 (en) Access point controller failover system
US11178150B1 (en) Methods for enforcing access control list based on managed application and devices thereof
CN107317880B (zh) 一种实现负载均衡的方法及装置
WO2018099301A1 (zh) 一种数据分析方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16827074

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016827074

Country of ref document: EP