CN111901389B - Data updating method, device, server and storage medium - Google Patents
Data updating method, device, server and storage medium Download PDFInfo
- Publication number
- CN111901389B CN111901389B CN202010630554.5A CN202010630554A CN111901389B CN 111901389 B CN111901389 B CN 111901389B CN 202010630554 A CN202010630554 A CN 202010630554A CN 111901389 B CN111901389 B CN 111901389B
- Authority
- CN
- China
- Prior art keywords
- server
- data
- node server
- node
- updated
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
-
- 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
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The present disclosure relates to a data updating method, device, server and storage medium, the method comprising: acquiring data to be updated; transmitting the data to be updated to a first node server which maintains lease with the server; the first node server is used for updating the data to be updated; the server and the first node server belong to the same server cluster; and when the server and the first node server update the data to be updated, generating data updating success information. By adopting the method, the consistency of the updated data is improved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a data updating method, device, server, and storage medium.
Background
With the development of computer technology, the requirements on data consistency are higher and higher; to maintain data consistency, data of each server in a server cluster needs to be updated synchronously or asynchronously.
In the related art, the current data updating method generally waits until the central server has updated the data or the servers in the server cluster have updated the data exceeds a certain proportion, and then returns the successful data updating information to the data updating request terminal; however, if the data update request end accesses the server cluster after receiving the data update success information, the old data may still be read, resulting in lower consistency of the updated data.
Disclosure of Invention
The disclosure provides a data updating method, a device, a server and a storage medium, so as to at least solve the problem of low consistency of updated data in the related art. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a data updating method, including:
acquiring data to be updated;
transmitting the data to be updated to a first node server which maintains lease with the server; the first node server is used for updating the data to be updated; the server and the first node server belong to the same server cluster;
and when the server and the first node server update the data to be updated, generating data updating success information.
In an exemplary embodiment, the sending the data to be updated to the first node server maintaining lease with the server includes:
inquiring a current first node server list to obtain a first node server identifier which is kept leased with the server in the server cluster; a plurality of first node server identifiers which keep leases with the server are marked in the current first node server list;
Acquiring a first node server address corresponding to a first node server identifier of the server holding lease;
and sending the data to be updated to a first node server corresponding to the first node server address in the server cluster.
In an exemplary embodiment, before querying the current first node server list to obtain the first node server identifier of the server cluster that is leased from the server, the method further includes:
acquiring lease validity of a node server in the server cluster;
acquiring a server identifier corresponding to a node server with the lease validity period in a current period as a first node server identifier which keeps leasing with the server;
and updating the historical first node server list according to the first node server identifier which keeps leases with the server to obtain the current first node server list.
In an exemplary embodiment, when the server and the first node server update the data to be updated, generating data update success information includes:
acquiring a first data updating result of the server on the data to be updated and a second data updating result of the first node server on the data to be updated;
Correspondingly extracting a data update identifier of the server and a data update identifier of the first node server from the first data update result and the second data update result respectively;
if the data updating identification of the server and the data updating identification of the first node server are both successful identifications of data updating, confirming that the server and the first node server update the data to be updated;
and when the server and the first node server update the data to be updated, generating data updating success information according to a preset data updating success information template.
In an exemplary embodiment, after acquiring the data to be updated, further includes:
inquiring a current second node server list to obtain a second node server identifier which is not leased by the server in the server cluster; a plurality of second node server identifiers which are not leased with the server are marked in the current second node server list;
acquiring a second node server address corresponding to the second node server identifier;
sending a preset closing instruction to a second node server corresponding to the second node server address in the server cluster; the preset closing instruction is used for triggering the second node server to enter a closing state.
In an exemplary embodiment, when the server and the first node server update the data to be updated, generating data update success information further includes:
and when the server and the first node server update the data to be updated, and the second node server enters a closed state, generating data updating success information.
In an exemplary embodiment, the method further comprises:
acquiring a server address corresponding to the server;
transmitting the server address, the first node server address and the data updating success information to a data request terminal; the data request terminal is used for accessing a corresponding server or a first node server through the server address or the first node server address based on the data updating success information to obtain updated data.
According to a second aspect of the embodiments of the present disclosure, there is provided a data updating apparatus including:
a data acquisition unit configured to perform acquisition of data to be updated;
a data transmission unit configured to perform transmission of the data to be updated to a first node server that maintains lease with the server; the first node server is used for updating the data to be updated; the server and the first node server belong to the same server cluster;
And the information generation unit is configured to generate data updating success information when the server and the first node server update the data to be updated.
In an exemplary embodiment, the data sending unit is further configured to perform querying a current first node server list to obtain a first node server identifier of the server cluster, which is leased to the server; a plurality of first node server identifiers which keep leases with the server are marked in the current first node server list; acquiring a first node server address corresponding to a first node server identifier of the server holding lease; and sending the data to be updated to a first node server corresponding to the first node server address in the server cluster.
In an exemplary embodiment, the data updating apparatus further includes a list updating unit configured to perform acquiring lease validity periods of node servers in the server cluster; acquiring a server identifier corresponding to a node server with the lease validity period in a current period as a first node server identifier which keeps leasing with the server; and updating the historical first node server list according to the first node server identifier which keeps leases with the server to obtain the current first node server list.
In an exemplary embodiment, the information generating unit is further configured to perform obtaining a first data update result of the server on the data to be updated and a second data update result of the first node server on the data to be updated; correspondingly extracting a data update identifier of the server and a data update identifier of the first node server from the first data update result and the second data update result respectively; if the data updating identification of the server and the data updating identification of the first node server are both successful identifications of data updating, confirming that the server and the first node server update the data to be updated; and when the server and the first node server update the data to be updated, generating data updating success information according to a preset data updating success information template.
In an exemplary embodiment, the data updating apparatus further includes an instruction sending unit configured to perform querying a current second node server list to obtain a second node server identifier in the server cluster, which is not leased by the server; a plurality of second node server identifiers which are not leased with the server are marked in the current second node server list; acquiring a second node server address corresponding to the second node server identifier; sending a preset closing instruction to a second node server corresponding to the second node server address in the server cluster; the preset closing instruction is used for triggering the second node server to enter a closing state.
In an exemplary embodiment, the information generating unit is further configured to generate data update success information when the server and the first node server update the data to be updated, and the second node server enters a closed state.
In an exemplary embodiment, the data updating apparatus further includes an information transmitting unit configured to perform acquisition of a server address corresponding to the server; transmitting the server address, the first node server address and the data updating success information to a data request terminal; the data request terminal is used for accessing a corresponding server or a first node server through the server address or the first node server address based on the data updating success information to obtain updated data.
According to a third aspect of embodiments of the present disclosure, there is provided a server comprising: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the data update method as described in any of the embodiments of the first aspect.
According to a fourth aspect of embodiments of the present disclosure, there is provided a storage medium comprising: the instructions in the storage medium, when executed by a processor of a server, enable the server to perform the data update method as described in any one of the embodiments of the first aspect.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising a computer program stored in a readable storage medium, from which at least one processor of a device reads and executes the computer program, causing the device to perform the data updating method as described in any one of the embodiments of the first aspect.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
the method comprises the steps of obtaining data to be updated, and then sending the data to be updated to a first node server which keeps leases with the server; the first node server is used for updating the data to be updated; the server and the first node server belong to the same server cluster; finally, when the server and the first node server update the data to be updated, generating successful data update information; the aim of generating the successful data update information under the condition that the server and the first node server update the data to be updated is achieved, the server cluster is accessed after the data request terminal receives the successful data update information, old data cannot be read, and therefore the data consistency after updating is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
Fig. 1 is an application environment diagram illustrating a data update method according to an exemplary embodiment.
Fig. 2 is a flow chart illustrating a method of data update according to an exemplary embodiment.
Fig. 3 is a flowchart illustrating steps for sending data to be updated to a first node server maintaining a lease with the server, according to an exemplary embodiment.
Fig. 4 is a flow chart illustrating another data update method according to an exemplary embodiment.
Fig. 5 is a block diagram illustrating a data updating apparatus according to an exemplary embodiment.
Fig. 6 is an internal structural diagram of a server shown according to an exemplary embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
The data updating method provided by the disclosure can be applied to an application environment as shown in fig. 1. Referring to fig. 1, the application environment diagram includes a server cluster 110, where the server cluster 110 is a server cluster composed of a plurality of servers, and specifically includes a server 111 and a first node server 112 (e.g., 112a, 112b, 112c, etc.), the server 111 is a central server, and the first node server 112 is a node server that maintains leases with the server 111. Referring to fig. 1, a server 111 acquires data to be updated; sending the data to be updated to a first node server 112 that maintains lease with the server 111; the first node server 112 is configured to update data to be updated; when the server 111 and the first node server 112 update the data to be updated, data update success information is generated. In addition, the server 111 may further send data update success information to a data request terminal, where the data request terminal is configured to access servers in the server cluster according to the received data update success information, and obtain updated data. In an actual scenario, the data updating method of the present disclosure may be applied to a scenario with a high data consistency requirement, for example, a certain anchor user is blocked, and after the blocking operation is completed, no user can see the relevant information of the anchor any more.
Fig. 2 is a flowchart illustrating a data update method according to an exemplary embodiment, as shown in fig. 2, for use in the server 111 shown in fig. 1, comprising the steps of:
in step S210, data to be updated is acquired.
The data to be updated is data with higher data consistency requirements, such as time of a red packet in spring and evening, related information of a certain blocked anchor user, and the like. In addition, the data to be updated may originate from a terminal, or may originate from a server in another server cluster, and the disclosure is not limited specifically.
Specifically, a data update request end responds to triggering operation of data to be updated, and the data to be updated is obtained; generating a data update request according to the data to be updated, and sending the data update request to a server (such as a central server) in the server cluster; the server analyzes the data updating request to obtain data to be updated, which is sent by the data updating request terminal, and updates the data to be updated. The data update request end refers to a terminal capable of triggering a data update request, such as a user management terminal, an information management terminal, and the like.
For example, when data (such as user permission, trigger time of a certain action, etc.) stored by a server in the server cluster needs to be changed, the corresponding data to be updated is obtained through the data update request end, and the data to be updated is sent to the server cluster, so as to request the server in the server cluster to update the data to be updated.
In an exemplary scenario of blocking a certain anchor user, the data update request end responds to a blocking operation of the certain anchor user, takes relevant information of the anchor user as data to be updated, sends the data to be updated to the server cluster, and updates the data to be updated through a server in the server cluster, so that other users cannot see relevant information of the anchor user, and old data is prevented from being read.
In step S220, the data to be updated is sent to the first node server which maintains lease with the server; the first node server is used for updating the data to be updated; the server and the first node server belong to the same server cluster.
The first node server refers to a node server which is leased with a server in the same server cluster and can timely keep the state of synchronizing data with the server.
It should be noted that, the server maintains a lease mechanism with other node servers in the same server cluster, and the server is responsible for issuing lease to other node servers in the same server cluster; before the lease expires, other node servers in the server cluster must interact with the lease-issuing server to continue the lease, and the lease-issuing server records the node servers currently in the lease validity period; and if the node server which cannot acquire lease renewal exceeds a timeout time T, the service is immediately stopped and the process is closed, and the node server cannot respond to read data requests sent by other devices.
Specifically, the server determines a node server which is still leased with the server currently in the server cluster in advance as a first node server, and sends data to be updated to the first node server which is still leased with the server currently, so as to request the first node server to update the data to be updated.
For example, the server updates the data to be updated, and after the data to be updated is updated, the data to be updated is sent to a first node server which is in the server cluster and keeps leasing with the server currently, and the first node server updates the data to be updated; for another example, the server and the first node server update the data to be updated at the same time; of course, the updating process of the data to be updated may also be other implementations, and the disclosure is not limited in particular.
In step S230, when the server and the first node server update the data to be updated, data update success information is generated.
The data updating success information is used for identifying that the server in the server cluster and the first node server are updated with the data to be updated, and indicates that the data request terminal can read the data stored by the server in the server cluster or the first node server and cannot read old data.
Specifically, the server acquires data updating results of data to be updated of the server and the first node server, analyzes the data updating results of the data to be updated of the server and the first node server, and judges whether the data to be updated of the server and the first node server are updated or not, so that analysis results are obtained; and according to the analysis result, the server and the first node server are identified to update the data to be updated, and then data updating success information is generated. Therefore, the data updating success information is generated only when the server and the first node server update the data to be updated, and the defect that old data can be read by accessing the server cluster after the data updating success information is generated under other conditions is overcome.
For example, the server obtains the data updating result of the server as the data updating result of the data to be updated; acquiring a preset data updating result query instruction, and sending the preset data updating result query instruction to a first node server; the method comprises the steps that a first node server obtains a data updating result of data to be updated of the first node server according to a preset data updating result query instruction, and sends the data updating result of the data to be updated to the server, so that the data updating results of the server and the first node server are obtained; analyzing and processing data updating results of the data to be updated by the server and the first node server, and generating data updating success information when the data to be updated by the server and the first node server are updated.
Further, the server may also send data update success information to the corresponding data request terminal (such as a user terminal) to remind the data request terminal to access the data in the server cluster. For example, the server acquires address information of the data request terminal, and sends successful data update information to the corresponding data request terminal according to the address information of the data request terminal; the data request terminal receives the successful data updating information, which indicates that the server in the server cluster and the first node server update the data to be updated, and the server cluster is accessed at the moment, so that the old data cannot be read. Therefore, under the condition that the server and the first node server update the data to be updated, the data updating success information is sent to the data request terminal, the data request terminal is ensured to access the server cluster, the old data cannot be read, and accordingly the updated data consistency in the server cluster is improved.
In the data updating method, the data to be updated is obtained and then sent to a first node server which keeps leasing with the server; the first node server is used for updating the data to be updated; the server and the first node server belong to the same server cluster; finally, when the server and the first node server update the data to be updated, generating successful data update information; the aim of generating the successful data update information under the condition that the server and the first node server update the data to be updated is achieved, the server cluster is accessed after the data request terminal receives the successful data update information, old data cannot be read, and therefore the data consistency after updating is improved.
In an exemplary embodiment, as shown in fig. 3, in step S220, the data to be updated is sent to the first node server that maintains lease with the server, which may be implemented specifically by the following steps:
in step S310, a current list of first node servers is queried to obtain a first node server identifier which is kept leased with a server in a server cluster; the current list of first node servers is marked with a plurality of first node server identities that remain leased with the server.
The current first node server list refers to a server list formed by the first node server identifiers which are still leased with the server, and the first node server identifiers which are marked and kept leased with the server are different in different periods; the first node server identification refers to identification information of the first node server, such as a server name, a server number, a server port number, etc.
Specifically, the server queries a current first node server list, and extracts a first node server identifier which is kept leased with the server in the server cluster from the current first node server list.
It should be noted that, the node server that fails to maintain lease with the server in time immediately stops service and closes the process when it determines that a timeout period T is exceeded, so the server does not need to send the data to be updated to the node server that fails to maintain lease with the server.
In step S320, a first node server address corresponding to the first node server identity of the server holding lease is obtained.
The first node server address may refer to an IP (Internet Protocol ) address, and the first node server identifiers and the first node server addresses have a one-to-one correspondence, and the first node server addresses corresponding to different first node server identifiers are different.
Specifically, the server queries a preset corresponding relation between the first node server identifier and the first node server address according to the first node server identifier, and obtains the first node server address corresponding to the first node server identifier.
In step S330, the data to be updated is sent to a first node server corresponding to the first node server address in the server cluster.
Specifically, the server establishes communication connection with the corresponding first node server according to the address of the first node server, and after establishing communication connection with the corresponding first node server, sends the data to be updated to the corresponding first node server.
According to the technical scheme provided by the embodiment of the disclosure, according to the current first node server list, the data to be updated is only sent to the first node server which is kept leased with the server in the server cluster, so that the defect that the data updating efficiency of the server cluster is lower due to the fact that the data to be updated is sent to the node server which is unable to keep leased with the server in the server cluster is avoided.
In an exemplary embodiment, in step S310, before querying the current first node server list to obtain the identity of the first node server that is leased from the server in the server cluster, the method further includes: acquiring lease validity of a node server in a server cluster; obtaining a server identifier corresponding to a node server with lease validity period in a current period as a first node server identifier for maintaining lease with the server; updating the historical first node server list according to the first node server identifier which keeps leases with the server, and obtaining a current first node server list.
Wherein, the lease validity period refers to a period of time for maintaining lease with the server; the server identification refers to identification information of node servers, such as server names, server numbers, server port numbers, and the like, and the server identifications carried by different node servers are different.
Specifically, a server acquires a preset lease validity period acquisition instruction, and acquires the lease validity period of a node server in a server cluster according to the preset lease validity period acquisition instruction; screening out node servers with lease validity period in the current period from the node servers contained in the server cluster; acquiring a server identifier carried by a node server with lease validity period in a current period as a first node server identifier for maintaining lease with the server; and updating the historical first node server list by using the first node server identifier which is kept leased with the server and covers the first node server identifier marked in the historical first node server list, so as to obtain the current first node server list.
According to the technical scheme provided by the embodiment of the disclosure, the lease validity period of the node servers in the server cluster is identified, so that the current first node server list is determined accurately, the data to be updated is sent to all the first node servers which keep leases with the servers in the server cluster according to the current first node server list, the defect of low updated data consistency caused by inconsistent data update among different servers due to omission is avoided, and the updated data consistency is further improved.
In an exemplary embodiment, in step S230, when the server and the first node server update the data to be updated, data update success information is generated, which specifically includes the following contents: acquiring a first data updating result of data to be updated of a server and a second data updating result of the data to be updated of a first node server; respectively extracting a data update identifier of a server and a data update identifier of a first node server from the first data update result and the second data update result; if the data updating identification of the server and the data updating identification of the first node server are both successful identifications of data updating, confirming that the server and the first node server update the data to be updated; when the server and the first node server update the data to be updated, generating data updating success information according to a preset data updating success information template.
The first data updating result and the second data updating result refer to updating conditions of the data to be updated, such as updated data, not updated data, and the like. The data update identifier is used for identifying the data update result of the server, and can be a data update success identifier or a data update failure identifier. The preset data update success information template refers to an information template for generating data update success information.
Specifically, the server acquires a first data updating result of data to be updated by the server and a second data updating result of the data to be updated by the first node server; respectively extracting information corresponding to a preset data update identifier from a first data update result and a second data update result, wherein the information corresponds to a data update identifier serving as a server and a data update identifier of a first node server; comparing the data updating identification of the server with the data updating identification of the first node server with the data updating success identification, and if the data updating identification of the server and the data updating identification of the first node server are both data updating success identifications, confirming that the data to be updated of the server and the first node server are updated; when the server and the first node server update the data to be updated, a preset data updating success information template is obtained, and data updating success information is generated according to the preset data updating success information template.
According to the technical scheme provided by the embodiment of the disclosure, the data updating success information is generated under the condition that the server and the first node server update the data to be updated, so that the defect that the data request terminal can still read old data by accessing the server cluster after the data updating success information is generated under other conditions is avoided, and the consistency of the updated data is further improved.
In an exemplary embodiment, in step S210, after the data to be updated is acquired, the following is further included: inquiring a current second node server list to obtain a second node server identifier which is not leased with a server in the server cluster; a plurality of second node server identifiers which are not leased with the server are marked in the current second node server list; acquiring a second node server address corresponding to the second node server identifier; transmitting a preset closing instruction to a second node server corresponding to a second node server address in the server cluster; the preset closing instruction is used for triggering the second node server to enter a closing state.
The current second node server list refers to a server list formed by second node server identifiers which are not currently leased with the server, and the second node server identifiers which are not leased with the server are marked in different periods; the second node server identification refers to identification information of the second node server, such as a server name, a server number, a server port number, and the like.
The second node server addresses may refer to IP addresses, and the second node server identifiers and the second node server addresses have a one-to-one correspondence, and the second node server addresses corresponding to different second node server identifiers are different.
The preset closing instruction is an instruction for triggering the second node server to enter a closing state. When the second node server is in the off state, the second node server cannot provide service, which means that other devices cannot access the second node server, that is, cannot read the data stored in the second node server.
Specifically, the server acquires lease validity periods of node servers in the server cluster; acquiring a server identifier corresponding to a node server with lease validity not in the current period, and taking the server identifier as a second node server identifier which does not keep lease with the server; and updating the historical second node server list according to the second node server identification which is not kept leased with the server, so as to obtain the current second node server list. Then, the server queries a current second node server list, and extracts a second node server identifier which is not leased with the server in the server cluster from the current second node server list; inquiring the corresponding relation between the preset second node server identifier and the second node server address according to the second node server identifier to obtain the second node server address corresponding to the second node server identifier; establishing communication connection with a corresponding second node server according to the address of the second node server, and sending a preset closing instruction to the corresponding second node server after establishing communication connection with the corresponding second node server; and the second node server enters a closed state according to the received preset closing instruction, and temporarily stops providing the service.
According to the technical scheme provided by the embodiment of the disclosure, the second node server which is not leased with the server at present is actively triggered to enter the closed state through the preset closing instruction, so that the defect that the updated data consistency is lower due to the fact that the second node server cannot smoothly enter the closed state as the second node server immediately stops the service and closes the process is avoided if the second node server judges that the second node server exceeds a timeout time T is overcome.
In an exemplary embodiment, in step S230, when the server and the first node server update the data to be updated, data update success information is generated, which further includes the following contents: and when the server and the first node server update the data to be updated, and the second node server enters a closed state, generating data update success information.
Specifically, the server acquires a first data updating result of data to be updated by the server, a second data updating result of the data to be updated by the first node server and running state information of the second node server according to a preset time interval; the method comprises the steps of respectively extracting a data updating identifier of a server and a data updating identifier of a first node server from a first data updating result and a second data updating result, and extracting an operation state identifier of a second node server from operation state information of the second node server; if the data updating identification of the server and the data updating identification of the first node server are both successful identifications of data updating and the running state identification of the second node server is a closing state identification, confirming that the data to be updated of the server and the first node server are both updated, and the second node server enters a closing state; when the server and the first node server update the data to be updated, and the second node server enters a closed state, data update success information is generated according to a preset data update success information template.
The running state information is used for identifying the running state of the second node server, such as a working state, a closing state and the like. The running state identifier is used for identifying running state information of the second node server, and can be a closing state identifier or a working state identifier.
The method includes the steps that a server obtains a first data updating result of data to be updated by the server and a second data updating result of the data to be updated by the first node server; meanwhile, the server acquires a preset network connection instruction, sends the preset network connection instruction to the second node server, confirms that the second node server is in a working state if response information returned by the second node server according to the preset network connection instruction is received, and confirms that the second node server is in a closing state if response information returned by the second node server according to the preset network connection instruction is not received, so that running state information of the second node server is obtained; then, the server acquires a preset data update identifier, and extracts information corresponding to the preset data update identifier from the first data update result and the second data update result respectively, wherein the information corresponds to the data update identifier as a data update identifier of the server and a data update identifier of the first node server; the server acquires a preset running state identifier, and extracts information corresponding to the preset running state identifier from the running state information of the second node server to serve as the running state identifier of the second node server; and identifying the data updating identifier of the server, the data updating identifier of the first node server and the running state identifier of the second node server, and if the data updating identifiers of the server and the first node server are both identified as successful data updating identifiers and the running state identifier of the second node server is a closing state identifier, confirming that the server and the first node server update the data to be updated and the second node server is in a closing state, and generating data updating success information according to a preset data updating success information template.
According to the technical scheme provided by the embodiment of the disclosure, when the server and the first node server update the data to be updated, and the second node server is in the closed state, the data update success information is generated, so that the defect that the data request terminal can still read old data by accessing the server cluster after the data update success information is generated under other conditions is avoided, and the updated data consistency is further improved.
In an exemplary embodiment, after obtaining the first data update result of the data to be updated by the server, the second data update result of the data to be updated by the first node server, and the operation state information of the second node server, the method further includes: if the first node server fails to update the data to be updated according to the second data updating result of the data to be updated, the data to be updated is sent to the first node server again until the first node server finishes updating the data to be updated.
Specifically, the server extracts information corresponding to a preset data update identifier from a second data update result of the first node server, and the information is used as a data update identifier of the first node server; and matching the data updating identification of the first node server with the data updating success identification, if the data updating identification of the first node server is failed to match with the data updating success identification, indicating that the data updating identification of the first node server is the data updating failure identification, confirming that the data updating to be updated of the first node server fails, and sending the data to be updated to the first node server again until the data updating to be updated of the first node server is completed.
According to the technical scheme provided by the embodiment of the disclosure, under the condition that the first node server fails to update the data to be updated, the data to be updated is sent to the first node server again until the first node server finishes updating the data to be updated; the updated data consistency between the server and all the first node servers currently maintaining leases is ensured, and the updated data consistency is further improved.
In an exemplary embodiment, the data updating method provided by the present disclosure further includes the following: obtaining a server address corresponding to a server; the server address, the first node server address and the data updating success information are sent to a data request terminal; the data request terminal is used for accessing a corresponding server or a first node server through a server address or a first node server address based on the data updating success information to obtain updated data.
Specifically, the server acquires a corresponding server address, combines the server address, the first node server address and the data updating success information according to a preset combination sequence, and generates combined information; transmitting the combined information to a data request terminal; therefore, after the data request terminal receives the successful data updating information, the corresponding server or the first node server can be accessed according to the server address or the first node server address, the updated data can be read, the old data cannot be read, and the defect that the data request terminal reads the old data is further avoided.
In an exemplary embodiment, as shown in fig. 4, another data updating method is provided, which specifically includes the following steps:
in step S410, data to be updated is acquired.
In step S420, a lease validity period of a node server in the server cluster is acquired; obtaining a server identifier corresponding to a node server with lease validity period in a current period as a first node server identifier for maintaining lease with the server; updating the historical first node server list according to the first node server identifier which keeps leases with the server, and obtaining a current first node server list.
In step S430, querying a current first node server list to obtain a first node server identifier of the server cluster, which is leased from the server; acquiring a first node server address corresponding to a first node server identifier of which the server keeps leases; and sending the data to be updated to a first node server corresponding to the first node server address in the server cluster.
In step S440, querying a current second node server list to obtain a second node server identifier in the server cluster, which is not leased by the server; acquiring a second node server address corresponding to the second node server identifier; transmitting a preset closing instruction to a second node server corresponding to a second node server address in the server cluster; the preset closing instruction is used for triggering the second node server to enter a closing state.
In step S450, a first data update result of the data to be updated by the server, a second data update result of the data to be updated by the first node server, and operation status information of the second node server are obtained.
In step S460, the data update identifier of the server and the data update identifier of the first node server are correspondingly extracted from the first data update result and the second data update result, respectively, and the operation state identifier of the second node server is extracted from the operation state information of the second node server.
In step S470, if the data update identifier of the server and the data update identifier of the first node server are both successful identifiers for data update and the running state identifier of the second node server is the off state identifier, the server and the first node server are confirmed to update the data to be updated, and the second node server enters the off state.
In step S480, when the server and the first node server update the data to be updated, and the second node server enters the closed state, data update success information is generated according to the preset data update success information template.
In step S490, a server address corresponding to the server is obtained; the server address, the first node server address and the data updating success information are sent to a data request terminal; the data request terminal is used for accessing a corresponding server or a first node server through a server address or a first node server address based on the data updating success information to obtain updated data.
The data updating method achieves the purpose that the data updating success information is sent to the data request terminal only when the server and the first node server update the data to be updated and the second node server is in the closed state, ensures that the data request terminal accesses the server cluster after receiving the data updating success information, and cannot read old data, thereby improving the updated data consistency.
It should be understood that, although the steps in the flowcharts of fig. 2-4 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in fig. 2-4 may include multiple steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the steps or stages are performed necessarily performed in sequence, but may be performed alternately or alternately with at least a portion of the steps or stages in other steps or other steps.
Fig. 5 is a block diagram illustrating a data updating apparatus according to an exemplary embodiment. Referring to fig. 5, the apparatus includes a data acquisition unit 510, a data transmission unit 520, and an information generation unit 530.
The data acquisition unit 510 is configured to perform acquisition of data to be updated.
A data transmitting unit 520 configured to perform transmission of data to be updated to a first node server maintaining lease with the server; the first node server is used for updating the data to be updated; the server and the first node server belong to the same server cluster.
The information generating unit 530 is configured to generate data update success information when the server and the first node server are both updated with the data to be updated.
In an exemplary embodiment, the data sending unit 520 is further configured to perform querying the current first node server list to obtain a first node server identifier of the server cluster that is leased from the server; a plurality of first node server identifiers which keep leases with the server are marked in the current first node server list; acquiring a first node server address corresponding to a first node server identifier of which the server keeps leases; and sending the data to be updated to a first node server corresponding to the first node server address in the server cluster.
In an exemplary embodiment, the data updating apparatus further includes a list updating unit configured to perform lease validity period of a node server in the acquisition server cluster; obtaining a server identifier corresponding to a node server with lease validity period in a current period as a first node server identifier for maintaining lease with the server; updating the historical first node server list according to the first node server identifier which keeps leases with the server, and obtaining a current first node server list.
In an exemplary embodiment, the information generating unit is further configured to perform obtaining a first data update result of the data to be updated by the server and a second data update result of the data to be updated by the first node server; respectively extracting a data update identifier of a server and a data update identifier of a first node server from the first data update result and the second data update result; if the data updating identification of the server and the data updating identification of the first node server are both successful identifications of data updating, confirming that the server and the first node server update the data to be updated; when the server and the first node server update the data to be updated, generating data updating success information according to a preset data updating success information template.
In an exemplary embodiment, the data updating apparatus further includes an instruction sending unit configured to perform querying a current second node server list to obtain a second node server identifier of the server cluster, which is not leased by the server; a plurality of second node server identifiers which are not leased with the server are marked in the current second node server list; acquiring a second node server address corresponding to the second node server identifier; transmitting a preset closing instruction to a second node server corresponding to a second node server address in the server cluster; the preset closing instruction is used for triggering the second node server to enter a closing state.
In an exemplary embodiment, the information generating unit 530 is further configured to generate the data update success information when the server and the first node server are both updated with the data to be updated, and the second node server enters the off state.
In an exemplary embodiment, the data updating apparatus further includes an information transmitting unit configured to perform acquisition of a server address corresponding to the server; the server address, the first node server address and the data updating success information are sent to a data request terminal; the data request terminal is used for accessing a corresponding server or a first node server through a server address or a first node server address based on the data updating success information to obtain updated data.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
Fig. 6 is a block diagram illustrating an apparatus 600 for performing the above-described data update method according to an exemplary embodiment. For example, device 600 may be a server. Referring to fig. 6, device 600 includes a processing component 620 that further includes one or more processors and memory resources represented by memory 622 for storing instructions, such as applications, executable by processing component 620. The application program stored in memory 622 may include one or more modules each corresponding to a set of instructions. Further, the processing component 620 is configured to execute instructions to perform the data update method described above.
The device 600 may also include a power component 624 configured to perform power management of the device 600, a wired or wireless network interface 626 configured to connect the device 600 to a network, and an input/output (I/O) interface 628. The device 600 may operate based on an operating system stored in memory 622, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, or the like.
In an exemplary embodiment, a storage medium is also provided, such as memory 622, including instructions executable by a processor of device 600 to perform the above-described method. The storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
In an exemplary embodiment, a computer program product is also provided, the program product comprising a computer program stored in a readable storage medium, from which at least one processor of the device reads and executes the computer program, causing the device to perform the data update method described in any one of the embodiments of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (16)
1. A data updating method, applied to a server, comprising:
acquiring data to be updated;
transmitting the data to be updated to a first node server which maintains lease with the server; the first node server is used for updating the data to be updated; the server and the first node server belong to the same server cluster; the server is a central server, and the first node server is a node server which is currently kept leased with the server in a server cluster where the server is located;
and when the server and the first node server update the data to be updated, generating data updating success information.
2. The data updating method according to claim 1, wherein the sending the data to be updated to the first node server that maintains lease with the server includes:
Inquiring a current first node server list to obtain a first node server identifier which is kept leased with the server in the server cluster; a plurality of first node server identifiers which keep leases with the server are marked in the current first node server list;
acquiring a first node server address corresponding to a first node server identifier of the server holding lease;
and sending the data to be updated to a first node server corresponding to the first node server address in the server cluster.
3. The method of claim 2, further comprising, prior to querying a current first list of node servers to obtain a first node server identification of the server cluster that remains leased with the server:
acquiring lease validity of a node server in the server cluster;
acquiring a server identifier corresponding to a node server with the lease validity period in a current period as a first node server identifier which keeps leasing with the server;
and updating the historical first node server list according to the first node server identifier which keeps leases with the server to obtain the current first node server list.
4. The method for updating data according to claim 1, wherein the generating data update success information when the server and the first node server update the data to be updated, comprises:
acquiring a first data updating result of the server on the data to be updated and a second data updating result of the first node server on the data to be updated;
correspondingly extracting a data update identifier of the server and a data update identifier of the first node server from the first data update result and the second data update result respectively;
if the data updating identification of the server and the data updating identification of the first node server are both successful identifications of data updating, confirming that the server and the first node server update the data to be updated;
and when the server and the first node server update the data to be updated, generating data updating success information according to a preset data updating success information template.
5. The data updating method according to claim 1, characterized by further comprising, after acquiring the data to be updated:
Inquiring a current second node server list to obtain a second node server identifier which is not leased by the server in the server cluster; a plurality of second node server identifiers which are not leased with the server are marked in the current second node server list;
acquiring a second node server address corresponding to the second node server identifier;
sending a preset closing instruction to a second node server corresponding to the second node server address in the server cluster; the preset closing instruction is used for triggering the second node server to enter a closing state.
6. The method for updating data according to claim 5, wherein when the server and the first node server update the data to be updated, generating data update success information further comprises:
and when the server and the first node server update the data to be updated, and the second node server enters a closed state, generating data updating success information.
7. The data updating method according to claim 2, characterized in that the method further comprises:
Acquiring a server address corresponding to the server;
transmitting the server address, the first node server address and the data updating success information to a data request terminal; the data request terminal is used for accessing a corresponding server or a first node server through the server address or the first node server address based on the data updating success information to obtain updated data.
8. A data updating apparatus, characterized by being applied to a server, comprising:
a data acquisition unit configured to perform acquisition of data to be updated;
a data transmission unit configured to perform transmission of the data to be updated to a first node server that maintains lease with the server; the first node server is used for updating the data to be updated; the server and the first node server belong to the same server cluster; the server is a central server, and the first node server is a node server which is currently kept leased with the server in a server cluster where the server is located;
and the information generation unit is configured to generate data updating success information when the server and the first node server update the data to be updated.
9. The data updating apparatus according to claim 8, wherein the data transmitting unit is further configured to perform a query of a current first node server list to obtain a first node server identification of the server cluster that is kept leased from the server; a plurality of first node server identifiers which keep leases with the server are marked in the current first node server list; acquiring a first node server address corresponding to a first node server identifier of the server holding lease; and sending the data to be updated to a first node server corresponding to the first node server address in the server cluster.
10. The data updating apparatus according to claim 9, further comprising a list updating unit configured to perform lease validity period acquisition of node servers in the server cluster; acquiring a server identifier corresponding to a node server with the lease validity period in a current period as a first node server identifier which keeps leasing with the server; and updating the historical first node server list according to the first node server identifier which keeps leases with the server to obtain the current first node server list.
11. The data updating apparatus according to claim 8, wherein the information generating unit is further configured to perform acquisition of a first data update result of the server for the data to be updated and a second data update result of the first node server for the data to be updated; correspondingly extracting a data update identifier of the server and a data update identifier of the first node server from the first data update result and the second data update result respectively; if the data updating identification of the server and the data updating identification of the first node server are both successful identifications of data updating, confirming that the server and the first node server update the data to be updated; and when the server and the first node server update the data to be updated, generating data updating success information according to a preset data updating success information template.
12. The data updating apparatus according to claim 8, further comprising an instruction sending unit configured to perform querying a current second node server list to obtain a second node server identifier in the server cluster that is not leased with the server; a plurality of second node server identifiers which are not leased with the server are marked in the current second node server list; acquiring a second node server address corresponding to the second node server identifier; sending a preset closing instruction to a second node server corresponding to the second node server address in the server cluster; the preset closing instruction is used for triggering the second node server to enter a closing state.
13. The apparatus according to claim 12, wherein the information generating unit is further configured to generate data update success information when the server and the first node server have both updated the data to be updated, and the second node server enters a closed state.
14. The apparatus according to claim 9, further comprising an information transmitting unit configured to perform acquisition of a server address corresponding to the server; transmitting the server address, the first node server address and the data updating success information to a data request terminal; the data request terminal is used for accessing a corresponding server or a first node server through the server address or the first node server address based on the data updating success information to obtain updated data.
15. A server, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the data update method of any one of claims 1 to 7.
16. A storage medium, which when executed by a processor of a server, causes the server to perform the data updating method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010630554.5A CN111901389B (en) | 2020-07-03 | 2020-07-03 | Data updating method, device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010630554.5A CN111901389B (en) | 2020-07-03 | 2020-07-03 | Data updating method, device, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111901389A CN111901389A (en) | 2020-11-06 |
| CN111901389B true CN111901389B (en) | 2023-07-04 |
Family
ID=73192962
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010630554.5A Active CN111901389B (en) | 2020-07-03 | 2020-07-03 | Data updating method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111901389B (en) |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104158911A (en) * | 2014-09-01 | 2014-11-19 | 青岛海信电器股份有限公司 | Server cluster-oriented control method and system |
| CN104980307A (en) * | 2015-06-29 | 2015-10-14 | 小米科技有限责任公司 | Processing method of data access requests, processing device of data access requests and database server |
| CN105338007A (en) * | 2014-05-30 | 2016-02-17 | 北京金山网络科技有限公司 | Service document obtaining method and providing method in server cluster, document server and center server |
| CN106202437A (en) * | 2016-07-14 | 2016-12-07 | 上海超橙科技有限公司 | A kind of data managing method and equipment |
| CN106888245A (en) * | 2016-06-07 | 2017-06-23 | 阿里巴巴集团控股有限公司 | A kind of data processing method, apparatus and system |
| CN106933547A (en) * | 2015-12-29 | 2017-07-07 | 阿里巴巴集团控股有限公司 | Method, device and more new system that global information is obtained and processed |
| CN108512877A (en) * | 2017-02-28 | 2018-09-07 | 腾讯科技（北京）有限公司 | The method and apparatus of sharing data in a kind of server cluster |
| CN108881379A (en) * | 2018-05-03 | 2018-11-23 | 网宿科技股份有限公司 | The synchronous method and apparatus of data between a kind of server cluster |
| CN109451088A (en) * | 2018-10-30 | 2019-03-08 | 新华三大数据技术有限公司 | A kind of data access method and device |
| CN109842497A (en) * | 2017-11-24 | 2019-06-04 | 贵州白山云科技股份有限公司 | Method and device, terminal device and the configuration more new system that the configuration of dns server updates |
| CN110245194A (en) * | 2019-06-24 | 2019-09-17 | 北京奇艺世纪科技有限公司 | Service data updating method, server and server cluster |
| CN110572451A (en) * | 2019-09-04 | 2019-12-13 | 腾讯科技（深圳）有限公司 | Data processing method, device and storage medium |
| CN111343277A (en) * | 2020-03-04 | 2020-06-26 | 腾讯科技（深圳）有限公司 | Distributed data storage method, system, computer device and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9043311B1 (en) * | 2011-10-20 | 2015-05-26 | Amazon Technologies, Inc. | Indexing data updates associated with an electronic catalog system |
| US9213642B2 (en) * | 2014-01-20 | 2015-12-15 | International Business Machines Corporation | High availability cache in server cluster |
-
2020
- 2020-07-03 CN CN202010630554.5A patent/CN111901389B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105338007A (en) * | 2014-05-30 | 2016-02-17 | 北京金山网络科技有限公司 | Service document obtaining method and providing method in server cluster, document server and center server |
| CN104158911A (en) * | 2014-09-01 | 2014-11-19 | 青岛海信电器股份有限公司 | Server cluster-oriented control method and system |
| CN104980307A (en) * | 2015-06-29 | 2015-10-14 | 小米科技有限责任公司 | Processing method of data access requests, processing device of data access requests and database server |
| CN106933547A (en) * | 2015-12-29 | 2017-07-07 | 阿里巴巴集团控股有限公司 | Method, device and more new system that global information is obtained and processed |
| CN106888245A (en) * | 2016-06-07 | 2017-06-23 | 阿里巴巴集团控股有限公司 | A kind of data processing method, apparatus and system |
| CN106202437A (en) * | 2016-07-14 | 2016-12-07 | 上海超橙科技有限公司 | A kind of data managing method and equipment |
| CN108512877A (en) * | 2017-02-28 | 2018-09-07 | 腾讯科技（北京）有限公司 | The method and apparatus of sharing data in a kind of server cluster |
| CN109842497A (en) * | 2017-11-24 | 2019-06-04 | 贵州白山云科技股份有限公司 | Method and device, terminal device and the configuration more new system that the configuration of dns server updates |
| CN108881379A (en) * | 2018-05-03 | 2018-11-23 | 网宿科技股份有限公司 | The synchronous method and apparatus of data between a kind of server cluster |
| CN109451088A (en) * | 2018-10-30 | 2019-03-08 | 新华三大数据技术有限公司 | A kind of data access method and device |
| CN110245194A (en) * | 2019-06-24 | 2019-09-17 | 北京奇艺世纪科技有限公司 | Service data updating method, server and server cluster |
| CN110572451A (en) * | 2019-09-04 | 2019-12-13 | 腾讯科技（深圳）有限公司 | Data processing method, device and storage medium |
| CN111343277A (en) * | 2020-03-04 | 2020-06-26 | 腾讯科技（深圳）有限公司 | Distributed data storage method, system, computer device and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| "Concurrent Updates on Striped Data Streams in Clustered Server Systems";Peter Sobe;《Proceedings 15th International Parallel and Distributed Processing Symposium. IPDPS 2001》;20020807;全文 * |
| "基于网络数据同步机制的分布内容管理系统设计与实现";徐澄宇;《中国优秀硕士学位论文全文数据库 信息科技辑》;20150815;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111901389A (en) | 2020-11-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10447793B2 (en) | Detecting shared access | |
| CN107169094B (en) | Information aggregation method and device | |
| CN107864143B (en) | Self-evolution efficient proxy resource supply system and method | |
| CN104601702B (en) | Cluster remote procedure calling (PRC) method and system | |
| CN111510325B (en) | Alarm information pushing method, server, client and system | |
| US20120246215A1 (en) | Identying users of remote sessions | |
| US20060071684A1 (en) | Active storage area network discovery system and method | |
| CN111901389B (en) | Data updating method, device, server and storage medium | |
| CN107249050B (en) | Method and device for managing resources in cloud platform | |
| CN107425994B (en) | Method, terminal and server for realizing remote parameter management | |
| CN112702441B (en) | Container-based access data processing method, device, system and storage medium | |
| US20150282121A1 (en) | Local resource sharing method of machine to machine component and apparatus thereof | |
| CN110209474B (en) | Task processing method and device | |
| EP4042280A1 (en) | Systems and methods for implementing soft locking in a stateless microservice environment | |
| CN111010690B (en) | Internet of things MME network element signaling tracking method and device | |
| CN110708208B (en) | Monitoring data acquisition method and device, storage medium and terminal | |
| CN110855785B (en) | Data processing method and device | |
| CN113727330B (en) | User information processing method and device based on TD-LTE mobile communication system | |
| CN111865639B (en) | Method and device for collecting information of snmp service equipment and electronic equipment | |
| US20230064688A1 (en) | Method for operations of virtual machines in monitoring cloud activities, system, and device applying the method | |
| CN117061410A (en) | IP address access method, internet of things platform, equipment, system and electronic equipment | |
| CN109639849B (en) | Address query processing method and service discovery device | |
| CN114363902A (en) | Method, device, equipment and storage medium for guaranteeing 5G private network service safety | |
| CN113709210A (en) | Device discovery method, device, system, electronic device and storage medium | |
| CN117014219A (en) | User safety control method and system based on domain name white list and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |