WO2016130825A1 - Procédé et appareil de modification de configurations - Google Patents

Procédé et appareil de modification de configurations Download PDF

Info

Publication number
WO2016130825A1
WO2016130825A1 PCT/US2016/017580 US2016017580W WO2016130825A1 WO 2016130825 A1 WO2016130825 A1 WO 2016130825A1 US 2016017580 W US2016017580 W US 2016017580W WO 2016130825 A1 WO2016130825 A1 WO 2016130825A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
change code
configuration change
network device
code
Prior art date
Application number
PCT/US2016/017580
Other languages
English (en)
Inventor
Bangjie JIANG
Chenghao SUAN
Shunmin ZHU
Han XIAO
Original Assignee
Alibaba Group Holding Limited
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
Priority claimed from CN201510079495.6A external-priority patent/CN105991720B/zh
Application filed by Alibaba Group Holding Limited filed Critical Alibaba Group Holding Limited
Publication of WO2016130825A1 publication Critical patent/WO2016130825A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings

Definitions

  • Embodiments according to the present disclosure relate generally to communication and computer technologies and, more particularly, to a method and apparatus for changing configurations.
  • the client-server model of computing is a distributed application structure that partitions tasks or workloads between the providers of a resource or service, often called servers, and service requesters, often called clients.
  • clients and servers communicate over a computer network on separate hardware, but both the client and the server may reside in the same system.
  • a server host runs one or more server programs that share their resources with clients.
  • Systems constructed with clients and servers enjoy widespread application on the Internet.
  • One or more clients may interact with the server-side by connecting to it in order to obtain services to satisfy the clients' needs.
  • a client frequently needs to synchronize its configuration with a server. When a configuration changes, the client needs to be notified in some way to update its configuration.
  • a server proactively pushes configuration information.
  • the server when the configuration associated with a client changes, the server proactively pushes configuration information to the client-side.
  • the server-side in this solution requires the installation of an additional module for maintaining clients' information that is registered in the system.
  • a client and a server maintain a long transmission control protocol (TCP) connection.
  • TCP transmission control protocol
  • This solution is actually a variant of solution 2 above, where a list of clients registered in the system needs to be maintained.
  • a long TCP connection itself is not reliable because the long connection can be interrupted by timeouts generated by intermediate equipment on the network.
  • An object of the present disclosure is to provide a method and apparatus for synchronizing configurations rapidly without adding or maintaining additional maintaining modules at the client or server sides.
  • the embodiments of the present invention provide a client-device-end-configuration-change method wherein the configuration change method comprises: a) sending a heartbeat request message to a network device over a network, wherein the heartbeat request message carries a current first configuration change code of a client device; b) receiving from the network device a heartbeat response message in accordance with the first configuration change code, wherein the heartbeat response message carries a current second configuration change code of the network device; c) sending, in accordance with the first configuration change code and the second configuration change code, a request message to the network device for synchronizing configurations; and d) obtaining configuration synchronization information sent from the network, synchronizing configurations of associated services according to the configuration synchronization information, and updating the first configuration change code in accordance with the results of the configuration synchronization.
  • the present invention provides a client-device-end- configuration-change method wherein the configuration change method comprises the following: a) sending a heartbeat request message to network equipment, wherein the heartbeat request message carries a current first configuration change code of the client device; b) obtaining a heartbeat response message sent back by the network equipment in accordance with the first configuration change code, the heartbeat response message carrying a current second
  • the method also comprises updating the first configuration change code in accordance with the results of the configuration synchronization. Additionally, the configuration code of the current second configuration change code carried by the heartbeat response message is identical to the configuration code of the first configuration change code.
  • sending the configuration synchronizing request message to the network equipment in accordance with the first configuration change code and the second configuration change code comprises the following: a) when the configuration version of the first configuration change code of the client device is "uncreated," sending a configuration creation request for relevant services to the network equipment; b) when the configuration version of the second configuration change code is newer than the configuration version of the first configuration change code, sending a request for configuration updating for relevant services to the network equipment; c) when the configuration version of the second configuration change code is "to be deleted,” sending a configuration deletion request for relevant services to the network equipment; or d) when a timestamp of the configuration version of the first
  • configuration change code of the client device is different than a timestamp of the configuration version of the second configuration change code, sending a request for configuration
  • Obtaining the configuration synchronization information sent back by the network equipment comprises obtaining a configuration synchronizing response message sent back by the network equipment, the configuration synchronizing response message carrying configuration information for relevant services.
  • configuration synchronizing response message comprises one of the following information: configuration information for the creation of services configuration, configuration information for the updating of services configuration, configuration information for the deletion of services configuration, or configuration information for the reconstruction of services configuration.
  • Updating the first configuration change code in accordance with the results of configuration synchronization comprises the following: a) after performing the creation of services configuration, creation of a configuration version and timestamp of the first configuration change code; b) after updating the services configuration, updating the configuration version of the first configuration change code; c) after deleting the services configuration, designating the configuration version of the first configuration change code as "to be deleted;" or, d) after reconstructing the services configuration, updating the timestamp of the first configuration change code.
  • the configuration code of the first configuration change code or the second configuration change code comprises a cyclic redundancy code obtained in accordance with a services name of the relevant configurations.
  • the configuration version of the configuration code of the first or second configuration change code comprises version information for the relevant services configuration.
  • the timestamp of the configuration code of the first or second configuration change code comprises the time of configuration creation for the relevant services configuration.
  • the embodiments of the present invention provide a configuration change method for a network equipment end, wherein the configuration change method comprises the following: a) obtaining a heartbeat request message sent by a client device, the heartbeat request message carrying a current first configuration change code of the client device; b) searching for a current second configuration change code of the client device for relevant services in accordance with the first configuration change code; c) sending a heartbeat response message back to the client device, the heartbeat response message carrying the second configuration change code; d) obtaining the heartbeat response message and, in accordance with a configuration
  • the configuration change method further comprises the following: when the configuration version of the first configuration change code is larger (or more recent) than the configuration version of the current second configuration change code of the network equipment, performing
  • Searching for a current second configuration change code of the client device for relevant services in accordance with the first configuration change code comprises obtaining, in accordance with the configuration code of the current first configuration change code of the client device, a current second configuration code of the network equipment having an identical configuration code.
  • the configuration synchronization information comprises a configuration synchronizing response message, the configuration synchronizing response message carrying configuration information for relevant services.
  • the configuration code comprises a cyclic redundancy code obtained in accordance with a services name of relevant configurations.
  • the configuration version comprises version information of the relevant services configuration, and the timestamp comprises the configuration creation time for the relevant services configuration.
  • the embodiments of the present invention provide a client device for changing configuration, wherein the client device comprises the following: a) a first component or "apparatus" configured for sending a heartbeat request message to a network device, wherein the heartbeat request message carries a current first configuration change code of the client device; b) a third component configured for obtaining a heartbeat response message sent from the network device in accordance with the first configuration change code, wherein the heartbeat response message comprises a current second configuration change code; c) a fifth component configured for sending a configuration synchronizing request message to the network device in accordance with the first and second configuration change codes; d) and a seventh component configured for obtaining configuration synchronization information sent from the network device to synchronize a configuration of the associated service and for updating the first configuration change code in accordance with the results of the configuration synchronization.
  • a first component or "apparatus” configured for sending a heartbeat request message to a network device, wherein the heartbeat request message carries a current first configuration change code of
  • the configuration code of the current second configuration code of the network device carried by the heartbeat response message is identical to the configuration code of the first configuration change code.
  • the fifth component comprises a first module configured for the following: a) sending a request to create a configuration for the associated service to the network device when a configuration version of the first configuration change code of the client device is marked as uncreated; b) sending a request to update a configuration for the associated service to the network device when a configuration version of the second configuration change code is marked as updated in comparison to the configuration version of the first configuration change code of the client device; c) sending a request to delete a configuration of the associated service to the network device when a configuration version of the second configuration change code is marked as awaiting to be deleted; or d) sending a request to reconstruct a configuration of the associated service to the network device when a timestamp of the configuration version of the first configuration change code of the client device is different from the timestamp of the second configuration change code.
  • the seventh component comprises a second module configured for obtaining a configuration synchronizing response message sent from the network device, wherein the configuration synchronizing response message comprises configuration information of the associated service.
  • the seventh component further comprises a third module configured for the following: a) generating a configuration version and a timestamp of the first configuration change code after an associated service is generated; b) updating the configuration version of the first configuration change code after the associated service is updated; c) labeling the configuration version of the first configuration change code as deleted after the associated service is deleted; or d) updating the timestamp of the first configuration change code after the associated service is reconstructed.
  • a third module configured for the following: a) generating a configuration version and a timestamp of the first configuration change code after an associated service is generated; b) updating the configuration version of the first configuration change code after the associated service is updated; c) labeling the configuration version of the first configuration change code as deleted after the associated service is deleted; or d) updating the timestamp of the first configuration change code after the associated service is reconstructed.
  • the configuration code comprises a cyclic redundancy code obtained in accordance with the services name of the relevant configurations.
  • the configuration version comprises version information of the relevant services configuration, and the timestamp comprises the configuration creation time for the relevant services configuration.
  • Embodiments of the present invention provide a network device for configuration changing, wherein the network device comprises the following: a) a second component configured for obtaining a heartbeat request message sent from a client device, wherein the heartbeat request message comprises a current first configuration change code of the client device; b) a fourth component configured for searching for a current second configuration code of the network device in accordance with the first configuration change code; c) a sixth component configured for sending to the client device a heartbeat response message, wherein the heartbeat response message comprises the second configuration change code; and d) an eighth component configured for obtaining a configuration synchronizing request sent from the client device and then sending configuration synchronization information in accordance with the configuration synchronizing request.
  • the network device further comprises a tenth component configured for synchronizing a configuration of the associated service when a configuration version of the first configuration change code is greater than the configuration version of the current second configuration change code of the network device.
  • the fourth component comprises a fourth module configured for obtaining the second present configuration change code of the network device having an identical
  • configuration code to the configuration code of first configuration change code in accordance with a configuration code of the current first configuration change code of the client device.
  • the configuration synchronizing information comprises a configuration synchronizing message which carries configuration information for relevant services.
  • the configuration code of the first or second configuration change code comprises a cyclic redundancy code obtained in accordance with the services name of the relevant configurations.
  • the configuration version comprises version information of a relevant services configuration, and the timestamp comprises a configuration creation time for the relevant services configuration.
  • An embodiment of the present disclosure provides a system for changing configurations, wherein the system comprises the above-described client device and network device.
  • synchronizing configurations in the present disclosure uses a heartbeat request message that carries a present first configuration change code of a local service to obtain a present second configuration change code of the network device associated with the same local service.
  • the client device detects differences between the first configuration change code and the second configuration change code to determine that information needs an update, where the second configuration change code is carried by a heartbeat response message sent from a network device.
  • the client device then synchronizes and updates, by sending a configuration
  • a majority of client sides have integrated the mechanism of sending and receiving heartbeat messages, including heartbeat request messages and heartbeat response messages, in signal processing; therefore, there is no need to add additional modules that require maintenance, thereby reducing the burdens of both the client device and the network device.
  • the network device does not require the provision of additional modules to maintain clients' statuses, thereby reducing workload demands on the server.
  • a relatively lesser amount of data needs to be introduced when using the configuration change codes to cover all of the configuration change matters, which is beneficial for lightweight cluster architecture systems.
  • FIG. 1 illustrates a block diagram of a device for changing configurations according to an embodiment of the present disclosure.
  • FIG. 2 shows a schematic diagram of either the first or second configuration change code according to an embodiment of the present disclosure.
  • FIG. 3 illustrates a block diagram of a network device for changing configurations according to an embodiment of the present disclosure.
  • FIG. 4 illustrates a block diagram of a network device according to the present disclosure.
  • FIG. 5 illustrates a block diagram of a system integrating a client device and a network device according to an embodiment of the present disclosure.
  • FIG. 6 illustrates a flowchart of an exemplary method for changing configurations, where a client device and a network device cooperate with each other according to an embodiment of the present disclosure.
  • FIG. 7 shows an exemplary method for changing configurations at the client device according to an embodiment of the present disclosure.
  • FIG. 8 shows a flowchart of an exemplary method for changing
  • FIG. 9 illustrates another exemplary method for changing configurations at the network device according to an embodiment of the present disclosure.
  • FIG. 10 is a block diagram of a client device for changing configurations in accordance with an embodiment of the present disclosure.
  • FIG. 11 is a block diagram of a client device for changing configurations in accordance with an embodiment of the present disclosure.
  • FIG. 12 is a block diagram of a network device for changing configurations in accordance with an embodiment of the present disclosure.
  • a terminal, a device-serving network, and a trusted party all include one or multiple CPUs ("processors"), input/output ports, network ports, and memories.
  • Memories can include computer-readable mediums such as a volatile memory, a random-access-memory (RAM), and/or a non-volatile memory, e.g. readonly-memory (ROM) or a flash RAM.
  • RAM random-access-memory
  • ROM readonly-memory
  • flash RAM e.g. readonly-memory
  • a memory is an example of computer-readable medium.
  • Computer-readable mediums include volatile, non-volatile, portable, and non-portable mediums. They can be used in any method or technique to implement information storage. The information can be computer-readable commands, data structures, program modules, or other data.
  • the readable mediums disclosed include, but are not limited to, phase-change memory (PRAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), other types of the random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash RAM and other memory technologies, compact disc read-only memory (CD-ROM), digital video disc (DVD) and other optical storage, magnetic tape, magnetic disc and other magnetic storage, and any other non-transition media.
  • PRAM phase-change memory
  • SRAM static random-access memory
  • DRAM dynamic random-access memory
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash RAM and other memory technologies
  • compact disc read-only memory (CD-ROM), digital video disc (DVD) and other optical storage magnetic tape, magnetic disc and other magnetic storage, and any other non-transition media.
  • computer-readable mediums do not include transitory media, such as the modulate
  • One object of an embodiment of the present disclosure is that using a heartbeat message to issue notifications of configuration changes to multiple client sides and/or client devices and server sides and/or network devices while minimizing configuration modules and configuration controllers to implement the synchronizations of the configurations.
  • the present disclosure introduces the concept of configuration change codes where variants of such codes represent variant changing situations to cover substantially all of the possible situations in which configuration changes occur.
  • the concept of configuration change codes involves reusing the heartbeat message between the clients and the servers and providing the notifications of configuration changes between the client sides and the server sides by embedding configuration change codes in the heartbeat message.
  • FIG. 1 illustrates a block diagram of a device for changing configurations according to an embodiment of the present disclosure.
  • Client device 1 includes first apparatus (or component) 11, third apparatus 13, fifth apparatus 15, and seventh apparatus 17.
  • Client device 1 can be any kind of electrical product that interacts with users through a keyboard, a mouse, a touch pad, a touch screen, a handwriting device, a remote or a voice control device, e.g., a computer, a mobile phone, a PDA, a handheld computer, and a tablet computer.
  • client device 1 includes an electrical device that computes data and processes information according to a series of preset or stored commands or instructions.
  • the hardware of such electrical device includes, but is not limited to, micro-processors, application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), digital signal processors (DSP), embedded devices, and the like.
  • ASIC application-specific integrated circuits
  • FPGA field-programmable gate arrays
  • DSP digital signal processors
  • First apparatus 11 is used for sending a heartbeat request message to the network device.
  • the heartbeat request message includes a present first configuration change code of the client device.
  • Third apparatus 13 is used for obtaining a heartbeat response message sent from the network device in accordance with the first configuration change code.
  • the heartbeat response message includes a present second configuration change code of the network device.
  • Fifth apparatus 15 is used for sending a configuration synchronizing request message in accordance with the first and second configuration change codes.
  • Seventh apparatus 17 is used for obtaining configuration synchronization information sent from the network device to synchronize associated configurations and for updating the first configuration change code according to the results of the configuration synchronization.
  • FIG. 2 shows a schematic diagram of either the first or second configuration change code according to an embodiment of the present disclosure.
  • the first and second configuration change codes mainly include three parts: configuration codes (Config_code), configuration versions (Config_version), and timestamps.
  • each of the three parts is encoded in 4 bytes during programming.
  • the configuration code is a cyclic redundancy code calculated in accordance with a corresponding service name, which marks the service configuration exclusively.
  • the configuration code of the first configuration change code at the client device and the configuration code of the second configuration change code at the network device of the same service are identical.
  • the configuration version is used to identify the updated status of a service; each time the associated configuration of a service is updated, the configuration version of this service is increased accordingly. Therefore, the updated statuses of the services can be monitored by their configuration versions.
  • the lower version of the configuration generally must be updated in order to keep the configuration versions identical of both configuration change codes.
  • the timestamp is mainly used for recording the time at which a service configuration is generated.
  • the first configuration change code and the second configuration change code include configuration codes, configuration versions, and timestamps.
  • first apparatus 1 1 sends a heartbeat request message to a network device, wherein the heartbeat request message includes a present first configuration change code of the client device.
  • this step can be embodied by a series of the following steps.
  • the heartbeat request message sent by first apparatus 11 includes a first configuration change code.
  • the network device obtains that first configuration change code and searches for a second configuration change code which has a configuration code identical to the configuration code of the first configuration change code, where that second configuration change code reflects or displays present configuration states or situations of the associated services in the network device.
  • third apparatus 13 obtains a heartbeat response message sent from the network device, including a present second configuration change code of the network device.
  • fifth apparatus 15 sends a configuration
  • first module 151 incorporated in fifth apparatus 15 (as shown in FIG. 10) used for sending, according to the specific differences between the first configuration change code and the second configuration change code, different configuration synchronizing request messages to the network device.
  • first module 151 is used for sending a create request to the network device to create a configuration of an associated service when the configuration version of the first configuration change code of the client device is labeled as "uncreated.”
  • First module 51 is also used for sending an update request when the configuration version of the second configuration change code is an updated version compared to that of the first configuration change code of the client device, meaning that the second configuration change code is in a more advanced, updated version than the first configuration change code.
  • the update request is sent to the network device to update a configuration of the associated service.
  • First module 151 is also used for sending a delete request for deleting configurations of the associated services to the network when the configuration version of the second configuration change code is labeled as "awaiting to be deleted" or for sending a rebuild request for rebuilding configurations of associated services to the network when the timestamp of the configuration version of the first configuration change code is different from the timestamp of the second configuration change code.
  • fifth apparatus 15 updating configurations according to the differences between the first configuration change code and the second configuration change code is only one of the implementation models of first module 151. Once there are specific settings for all of the variants of the configuration and the specific application scenarios, all of the possible configuration changing situations appear according to the configuration change codes. Moreover, all of the specific implementation models selected when updating the configurations according to the configuration change code can be included within the scope of the present disclosure.
  • seventh apparatus 17 obtains configuration synchronization information sent from the network device to synchronize configurations of the corresponding services accordingly and updates the first configuration change code according to the results of the configuration synchronization.
  • second module 172 is incorporated in seventh apparatus 17 (as shown in FIG. 1 1).
  • Second module 172 is used for obtaining a configuration synchronizing response message, including configuration information of the associated services sent from the network device.
  • the configuration information of the associated services carried by this configuration synchronizing response message may include configuration data of the associated services, etc.
  • Client device 1 can directly update the configurations according to the configuration information of the associated services.
  • the configuration information of the associated services carried by the aforementioned configuration synchronizing response message includes configuration information of the service configuration when the service configuration is created, updated, deleted, or rebuilt.
  • seventh apparatus 17 can also include third module 173 in another embodiment according to the present disclosure (as shown in FIG. 1 1).
  • Third module 173 is used for updating the first configuration change code after the related configuration is synchronized.
  • third module 173 is used for generating a configuration version and a timestamp for the first configuration change code after the generation of the service
  • Third module 173 is also used for updating the configuration version of the first configuration change code after the service configuration is updated. Additionally, after the service configuration is deleted, third module 173 is used for labeling the configuration version of the first configuration change code as "deleted.” The third module is also used for updating the timestamp of the first configuration change code after the service configuration is reconstructed.
  • the series of apparatuses incorporated in client device 1 operate constantly in a cooperative manner.
  • First apparatus 11 constantly sends the heartbeat request message
  • third apparatus 13 constantly obtains the heartbeat response message sent from the network device
  • fifth apparatus 15 constantly monitors changes in the first and second configuration change codes; once a change is observed, a configuration synchronizing request message including a selected specific request according to the attribute of the change would be sent to the network device.
  • Seventh apparatus 17 updates associated configurations upon receiving such a configuration synchronizing request message.
  • “constantly" means different apparatuses in client device 1 keep sending and receiving the heartbeat request message periodically and the heartbeat response message respectively, conduct required actions, and operate in a cooperative manner.
  • the client device used for updating configurations in the embodiment according to the present disclosure uses the heartbeat request message to communicate.
  • the heartbeat request message carries a present first configuration change code of a local service.
  • the client device obtains a present second configuration change code of the network device associated with the same local service as the first configuration change code through the heartbeat request message.
  • the second configuration change code is then sent back to the client device through a heartbeat response message.
  • information regarding configurations needing to be updated is obtained.
  • information may be obtained by sending a configuration synchronizing request message to the network device to request to synchronize configurations of the associated service and to update the first configuration change code.
  • the configuration codes can embed a relatively smaller amount of data to substantially cover all items of the configuration changes, which is beneficial to designing a lightweight cluster system.
  • FIG. 3 illustrates a block diagram of a network device for changing configurations according to an embodiment of the present disclosure.
  • Network device 3 includes second apparatus 32, fourth apparatus 34, sixth apparatus 36, and eighth apparatus 38.
  • Second apparatus 32 is used to receive a heartbeat request message from a client device, including a present first configuration change code of the client device.
  • Fourth apparatus 34 is used for searching for, in accordance with the first configuration change code, a present second configuration change code of the network device.
  • sixth apparatus 36 is used for sending a heartbeat response message to the client device, including the second configuration change code.
  • Eighth apparatus 38 is used for obtaining a configuration synchronizing request message requesting to synchronize configurations of associated services and then retiming configuration synchronization information, according to the configuration synchronizing request message, to the client device.
  • Network device 3 can be embodied by a cloud comprising a network mainframe, a separate network server, a set of multiple network servers, or multiple network servers, for instance.
  • a cloud is constructed by a large number of mainframes or network servers based on cloud computing.
  • Cloud computing is a type of distributed computing which is also a group of loosely coupled computers constituting a virtual supercomputer.
  • the network device includes an electrical device, which computes data and processes information according to a series of preset or stored commands.
  • the hardware of such electrical device includes, but is not limited to, micro-processors, application-specific integrated circuits (ASIC), field- programmable gate arrays (FPGA), digital signal processors (DSP), embedded devices, and the like.
  • the first configuration change code and the second configuration change code mainly include three parts: configuration codes (Config_code), configuration versions (Config_version), and timestamps.
  • the configuration code is the cyclic redundancy code calculated in accordance with a service name having a corresponding configuration, which marks the service configuration exclusively.
  • the configuration codes of the first configuration change code of the client device and the second configuration change code of the network device of the same service are identical.
  • the configuration version is used for identifying the updated status of a service. Each time the associated configuration of a service is updated, the configuration version of this service will be increased accordingly. Therefore, the updated statuses of the services can be monitored by reading their configuration versions.
  • the timestamp is mainly used for recording the time of the generation of a service configuration.
  • the first and the second configuration change codes mainly include configuration codes, configuration versions, and timestamps.
  • Fourth apparatus 34 in network device 3 includes fourth module 344 (as shown in FIG. 12) that obtains a present second configuration change code of the network device having an identical configuration code to that of the present first
  • the configuration synchronization information includes the configuration synchronizing response message that carries configuration information of associated services.
  • second apparatus 32 in network device 3 constantly obtains the heartbeat request message sent from the client device.
  • the other apparatuses in network device 3 constantly send relevant information according to the heartbeat request messages and the subsequent configuration synchronizing request message. Therefore, the client device can obtain the most updated configuration synchronization information of associated services in a timely manner.
  • FIG. 4 illustrates a block diagram of a network device according to the present disclosure.
  • Network device 3 includes second apparatus 32", fourth apparatus 34", sixth apparatus 36", eighth apparatus 38", and tenth apparatus 39".
  • the functions and purposes of second apparatus 32", fourth apparatus 34", sixth apparatus 36", and eighth apparatus 38" are substantially similar to those of second apparatus 32, fourth apparatus 34, sixth apparatus 36, and eighth apparatus 38 in the network device described in FIG. 3, referenced in the foregoing, which do not need to be described in detail herein.
  • Tenth apparatus 39" in FIG. 4 is used for synchronizing the associated services at the network device when the configuration version of the first configuration change code is greater than the configuration version of the present second configuration change code of the network device. More specifically, this can occur when the first configuration change code is more advanced in update version or has a later update version compared to the second configuration change code of the network device. In other words, when the first configuration change code has a more advanced update or a later update in comparison to the second configuration change code of the network device, the tenth apparatus can be used for synchronizing the associated services at the network device.
  • Network device 3 not only can cooperate with the client device to implement the updates of the configurations of the client device, but also can implement the updates of the configurations of the network device itself with the assistance of the client device by setting up tenth apparatus 39".
  • the network device If, due to certain special reasons, there is a reconfiguration in one of a group of network devices providing services and the timestamp of the first configuration change code shows an earlier time than the timestamp of the second configuration change code of the network device at the time when the client device is sending a first configuration change code to the network device, then the network device first sends a heartbeat response message which includes a present second configuration change code and is sent to the client device. And then the network device conducts a configuration synchronization of associated services on the network device on itself (as needed).
  • the configuration synchronization of the associated services includes, but is not limited to, sending configuration synchronizing requests to the management systems of several network devices and updating the second configuration change code of each of the network devices respectively.
  • the corresponding client devices can choose not to update the configurations if they find that the timestamp of the present first configuration change code of the client device shows an earlier time than the obtained timestamp of the present second configuration change code of the network device after comparing the second configuration change code with the present first configuration change code.
  • FIG. 5 illustrates a block diagram of a system integrating a client device and a network device according to an embodiment of the present disclosure.
  • the system includes client device 1 and network device 3, where client device 1 includes first apparatus 1 1 ", third apparatus 13", fifth apparatus 15", and seventh apparatus 17"; the network device 3 includes second apparatus 32", fourth apparatus 34", sixth apparatus 36", and eighth apparatus 38".
  • First apparatus 11 ", third apparatus 13", fifth apparatus 15”, and seventh apparatus 17” have substantially similar functions as first apparatus 11 , third apparatus 13, fifth apparatus 15, and seventh apparatus 17, respectively, as described in FIG. 1.
  • Second apparatus 32", fourth apparatus 34", sixth apparatus 36", and eighth apparatus 38" have substantially similar functions as second apparatus 32, fourth apparatus 34, sixth apparatus 36, and eighth apparatus 38 of network device 3 respectively, as described in FIG. 3, which can be cross- referenced and are not going to be described in detail herein.
  • FIG. 6 illustrates a flowchart of an exemplary method for changing configurations, where a client device and a network device cooperate with each other according to an embodiment of the present disclosure.
  • client device 1 sends a heartbeat request message, including a present first configuration change code of the client device.
  • network device 3 searches for, in accordance with the first configuration change code, a present second configuration code of the network device associated with a relevant service.
  • network device 3 sends a heartbeat response message including a present second configuration change code of the network device.
  • client device 1 sends a configuration synchronizing request message to the network device according to the first and second configuration change codes.
  • Step S38 network device 3 sends the configuration synchronization information back to client device 1.
  • Step S 17 client device 1 synchronizes configurations of corresponding services and updates the first configuration change code according to the results of the configuration synchronizing; thus, the configuration update of client device 1 is complete.
  • the system integrating the client device and the network device in accordance with embodiments of the present invention embodies a method of changing configurations using the mechanism of communicating through heartbeat messages.
  • the system uses heartbeat messages repeatedly and sends the notifications of changing configurations by embedding associated configuration change codes in the heartbeat messages.
  • the present disclosure is suitable for systems originally having the mechanism of
  • FIG. 7 shows a method for changing configurations at the client device according to an embodiment of the present disclosure.
  • the method includes Step SI 1, Step SI 3, Step S 15, and Step S17.
  • Step S l l the client device sends a heartbeat request message to a network device, including a present first configuration change code of the network device.
  • Step SI 3 the client device obtains a heartbeat response message sent from the network device according to the first configuration change code.
  • the heartbeat response message includes a present second configuration change code of the network device.
  • Step SI 5 the client device sends a configuration synchronizing request message to the network device according to the first and second configuration change codes.
  • Step SI 7 the client device obtains configuration synchronization information sent from the network device to synchronize configurations of associated services and to update the first configuration change code according to the results of the configuration synchronizations.
  • the first and the second configuration change codes mainly include three parts: configuration codes (Config_code), configuration versions (Config version), and timestamps.
  • each of the three parts is encoded in 4 bytes.
  • the configuration code is a cyclic redundancy code calculated in accordance with a service name having a corresponding configuration that marks the service configuration exclusively.
  • the first configuration change code of the client device and the second configuration change code of the network device of the same service are identical.
  • the configuration version is used for identifying the updated status of a service. Each time the associated configuration of a service is updated, the configuration version of this service will be increased accordingly. Therefore, the updated statuses of the services can be monitored by their configuration versions.
  • the timestamp is mainly used for recording the time of the generation of a service configuration.
  • first configuration change code and the second configuration change code mainly include configuration codes, configuration versions, and timestamps
  • an embodiment of the method for changing configurations related to FIG. 7 is further described in detail hereinafter.
  • Step S I 1 the client sends a heartbeat request message to a network device, including a present first configuration change code of the client device.
  • the heartbeat request message sent in Step S I 1 includes a first configuration change code; after the network device obtains the first configuration change code, the network device searches for a second configuration change code having an identical configuration code to the configuration code of the first configuration change code where the second configuration change code reflects or reveals the present configuration states and situations of the associated services in the network device.
  • Step SI 3 the client device obtains a heartbeat response message sent from the network device according to the first configuration change code.
  • the heartbeat response message includes a present second configuration change code of the network device.
  • Step S15 the client device sends a configuration synchronizing request message to the network device according to the first and second configuration change codes.
  • Step S 15 further includes the following: sending, according to the specific differences between the first configuration change code and the second configuration change code, different configuration synchronizing request messages to the network device.
  • the client device would send a create request to the network device to create a configuration of an associated service.
  • the configuration version of the second configuration change code is a more updated version compared to that of the first configuration change code of the client device (meaning that the second configuration change code is a more advanced, updated version than the first
  • Step S15 also includes sending a delete request to delete configurations of the associated services to the network when the configuration version of the second configuration change code is labeled as "awaiting to be deleted” or sending a rebuild request to rebuild configurations of associated services to the network when the timestamp of the configuration version of the first configuration change code is different from the timestamp of the second configuration change code.
  • fifth apparatus 15 updating configurations according to the differences between the first and the second configuration change codes is only one of the implementation models of the first module.
  • Step SI 7 the client device obtains configuration synchronization information returned from the network device to synchronize configurations of associated services and to update the first configuration change code according to the results of the configuration synchronization.
  • Step S17 includes obtaining a configuration synchronizing response message including configuration information of associated services.
  • the configuration information of an associated service carried by the configuration synchronizing response message can include configuration data of associated services, which enables the client device to directly update the configuration according to such configuration information.
  • the configuration information of the associated service carried by the configuration synchronizing response message includes configuration information of the service configuration when it is created, updated, deleted, or reconstructed or rebuilt.
  • Step SI 7 Another step is also included in Step SI 7, which involves updating the first configuration change code after the synchronization of the configurations.
  • a configuration version and a timestamp of the first configuration change code are generated after the generation of the service configuration.
  • the configuration version of the first configuration change code is updated after the service configuration is updated, the configuration version of the first configuration change code will be labeled as "deleted" after the service configuration is deleted, or the timestamp of the first configuration change code is updated after the service configuration is reconstructed.
  • Step Sl l a heartbeat request message is sent out constantly.
  • Step SI 3 a heartbeat response message sent from the network device in response to heartbeat request message is obtained constantly.
  • Step S15 changes in the first and the second configuration change codes are constantly monitored. Once a change is observed, a configuration
  • Step SI 7 associated configurations upon receiving such configuration synchronizing request messages are updated.
  • Constantly may be interpreted differently in different steps of the method, but generally means a mechanism of regularly sending and receiving the heartbeat request message and the heartbeat response message respectively, conducting required actions, and overall working in a cooperative manner.
  • the configuration in the embodiment of the present disclosure uses the heartbeat request message to communicate.
  • the heartbeat request message carries a present first configuration change code of a local service.
  • the client device obtains a present second configuration change code of the network device associated with the same local service as the first configuration change code through the heartbeat request message; the second configuration change code is then sent back to the client device by a heartbeat response message.
  • the configuration information needing to be updated is obtained.
  • By sending a configuration synchronizing request message to the network device configurations of the associated service will be synchronized and the first configuration change code will be updated.
  • the configuration codes can embed a relatively smaller amount of data to substantially cover all of the items in the configuration changes, and this attribute is beneficial to designing a lightweight cluster system.
  • FIG. 8 shows a flowchart of an exemplary method for changing
  • the method includes Step S32, Step S34, Step S36, and Step S38.
  • Step S32 a network device obtains a heartbeat request message sent from a client device, including a present first configuration change code of the client device.
  • Step S34 the network device searches for a present second configuration change code of the network device associated with relevant services according to the first configuration change code.
  • Step S36 the network device sends a heartbeat response message to the client device, including the second configuration change code.
  • the network device sends configuration synchronization information according to a configuration synchronizing request message sent from the client device.
  • the first and the second configuration change codes mainly include three parts: configuration codes (Config_code), configuration versions (Config_version), and timestamps.
  • configuration code is the cyclic redundancy code calculated in accordance with a service name having a corresponding configuration, which marks the service configuration exclusively.
  • the first configuration change code at the client device and the second configuration change code at the network device of the same service are identical.
  • the configuration version is used for identifying the updated status of a service. Each time the associated configuration of a service is updated, the configuration version of this service will be increased accordingly. Therefore, the updated statuses of the services can be monitored by reading their configuration versions.
  • the timestamp is mainly used for recording the time of the generation of a service configuration.
  • Step S34 further includes obtaining a present second configuration change code of the network device having the same configuration code as the configuration code of the first configuration change code.
  • the configuration synchronization information includes a configuration synchronizing response message including configuration information of the associated service.
  • Step S32 of the method for changing configurations of a network device the network device constantly obtains heartbeat request messages sent from the client device. And the other steps also constantly send required information according to the heartbeat request message and other related messages. Therefore, the client device can receive the more updated configuration synchronization information in a timely manner.
  • FIG. 9 illustrates another exemplary method for changing configurations at the network device according to an embodiment of the present disclosure.
  • the method includes Step S32", Step S34", Step S36", Step S38", and Step S39".
  • Step S32", Step S34", Step S36", and Step S38" have substantially similar functions to Step S32, Step S34, Step S36, and Step S38 described in FIG. 7, which can be cross-referenced and are not discussed in detail herein.
  • Step S39 when the configuration version of the first configuration change code is more updated compared to the second configuration change code, the configurations of the associated services will be updated at the network device.
  • the method for changing configurations at the network device not only can cooperate with the client device to implement the update of the configurations of the client device, but also can implement the update of the network device with assistance from the client device.
  • the network device sends a heartbeat response message including a present second configuration change code to the client device first and then conducts a configuration synchronization of associated services on the network device itself.
  • the configuration synchronization of the associated services include, but are not limited to, sending configuration synchronizing requests to the management systems of several network devices and updating the second configuration change codes of the network devices respectively.
  • the corresponding client devices can choose not to update the configurations if they find that the timestamp of the present first configuration change code of the client device shows an earlier time than the obtained timestamp of the present second configuration change code of the network device after comparing the second configuration change code obtained with the present first configuration change code.
  • configuration change code or the specific application scenarios therefore, the possible data- transmitting formats that can be considered as configuration change codes and that can embody the change in configurations which may appear in the future can all be included in the scope of the present disclosure.
  • the present disclosure can be embodied in a combination of hardware and software.
  • an application-specific integrated circuit, a general purpose computer, or any other similar hardware device can be adopted to embody the embodiments described in the foregoing according to the present disclosure.
  • the software of the present disclosure can be embodied by a processor executing the steps of the functions in the foregoing.
  • the software of the present disclosure including related data structures, can also be stored in computer-readable mediums, e.g., a RAM, a magnetic disk, a CD or a soft disc, and similar devices.
  • certain steps of the present disclosure can also be embodied in certain hardware, e.g., a circuit cooperating with a processor to execute each of the steps or functions.
  • part of the present disclosure can be applied as a computer- programmable product.
  • a computer program command can be one of such computer-programmable products that, when executed by a computer, allocates or provides the methods or devices described in the present disclosure through the operation of the computer.
  • the commands to allocate any of the methods of the present disclosure may be stored in fixed or portable recording mediums, and/or transmitted through dataflow in broadcast or other signal carrying medias, and/or stored in working memory of the computer operating according to the commands.
  • the device includes a storage that stores computer program commands and a processor that executes program commands; when the computer program commands are executed by the processor, this device would be triggered to execute multiple methods and/or devices according to embodiments of the present disclosure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Des modes de réalisation de la présente invention concernent un procédé de modification de configurations au niveau d'un dispositif client. Le procédé de modification de configurations comprend les étapes suivantes : a) envoyer un message de demande de battement de cœur à un dispositif de réseau sur un réseau, le message de demande de battement de cœur comportant un premier code de modification de configuration actuel d'un dispositif client ; b) recevoir à partir du dispositif de réseau un message de réponse de battement de cœur en accord avec le premier code de modification de configuration, le message de réponse de battement de cœur comportant un second code de modification de configuration actuel du dispositif de réseau ; c) envoyer, conformément au premier code de modification de configuration et au second code de modification de configuration, un message de demande au dispositif de réseau pour synchroniser des configurations ; d) obtenir des informations de synchronisation de configuration envoyées par le réseau, synchroniser des configurations de services associés en fonction des informations de synchronisation de configuration, et mettre à jour le premier code de modification de configuration en fonction des résultats de la synchronisation de configuration.
PCT/US2016/017580 2015-02-13 2016-02-11 Procédé et appareil de modification de configurations WO2016130825A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201510079495.6A CN105991720B (zh) 2015-02-13 2015-02-13 配置变更方法、设备及系统
CN201510079495.6 2015-02-13
US15/018,003 2016-02-08
US15/018,003 US10069942B2 (en) 2015-02-13 2016-02-08 Method and apparatus for changing configurations

Publications (1)

Publication Number Publication Date
WO2016130825A1 true WO2016130825A1 (fr) 2016-08-18

Family

ID=56615566

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/017580 WO2016130825A1 (fr) 2015-02-13 2016-02-11 Procédé et appareil de modification de configurations

Country Status (1)

Country Link
WO (1) WO2016130825A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113542408A (zh) * 2021-07-14 2021-10-22 首约科技(北京)有限公司 一种司机和乘客交互消息的方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100131633A1 (en) * 2007-04-04 2010-05-27 Thomson Licensing Device group control
US20100131630A1 (en) * 2008-11-25 2010-05-27 Ravi Kondamuru Systems and methods for gslb auto synchronization
US20120032945A1 (en) * 2008-12-19 2012-02-09 Openpeak Inc. Portable computing device and method of operation of same

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100131633A1 (en) * 2007-04-04 2010-05-27 Thomson Licensing Device group control
US20100131630A1 (en) * 2008-11-25 2010-05-27 Ravi Kondamuru Systems and methods for gslb auto synchronization
US20120032945A1 (en) * 2008-12-19 2012-02-09 Openpeak Inc. Portable computing device and method of operation of same

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113542408A (zh) * 2021-07-14 2021-10-22 首约科技(北京)有限公司 一种司机和乘客交互消息的方法
CN113542408B (zh) * 2021-07-14 2024-04-19 首约科技(北京)有限公司 一种司机和乘客交互消息的方法

Similar Documents

Publication Publication Date Title
US10069942B2 (en) Method and apparatus for changing configurations
KR102430869B1 (ko) 컨테이너화된 환경에서 클러스터의 라이브 마이그레이션
CN110311983B (zh) 服务请求的处理方法、装置、系统、电子设备及存储介质
US11635990B2 (en) Scalable centralized manager including examples of data pipeline deployment to an edge system
EP2954403B1 (fr) Récepteur et dispositif de persistance de données de flux continu basées sur un nuage
CN111090699A (zh) 业务数据的同步方法和装置、存储介质、电子装置
US20130238552A1 (en) Systems and methods for synchronizing files in a networked communication system
US9229701B2 (en) Local store data versioning
US20100161550A1 (en) File synchronization based on intercepting file system calls
WO2021051747A1 (fr) Procédé, système et dispositif de mise à jour de données, dispositif électronique, et support de stockage informatique
US9602614B1 (en) Distributed caching cluster client configuration
US20210382870A1 (en) Methods and system of tracking transactions for distributed ledger
TW201246103A (en) Category information transmission method, system and apparatus
US10826812B2 (en) Multiple quorum witness
US9529772B1 (en) Distributed caching cluster configuration
WO2012151993A1 (fr) Procédé et dispositif de poussée de service
CN111064626B (zh) 配置更新方法、装置、服务器及可读存储介质
CN112804289A (zh) 一种资源同步方法、装置、设备及存储介质
US8937562B1 (en) Shared data de-duplication method and system
CN112882738A (zh) 一种微服务架构下的配置信息更新方法、装置及电子设备
CN111212135A (zh) 消息订阅方法、装置、系统、电子设备及存储介质
CN111510480A (zh) 一种请求发送方法、装置以及第一服务器
US9405816B2 (en) Reconciliation of geo-replicated database clusters
CN110798358B (zh) 分布式服务标识方法、装置、计算机可读介质及电子设备
CN109992447B (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: 16749894

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16749894

Country of ref document: EP

Kind code of ref document: A1