CN109714218B - Internet of things server configuration information synchronization method - Google Patents
Internet of things server configuration information synchronization method Download PDFInfo
- Publication number
- CN109714218B CN109714218B CN201910165479.7A CN201910165479A CN109714218B CN 109714218 B CN109714218 B CN 109714218B CN 201910165479 A CN201910165479 A CN 201910165479A CN 109714218 B CN109714218 B CN 109714218B
- Authority
- CN
- China
- Prior art keywords
- hardware
- server
- attribute
- gateway
- configuration
- 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
Abstract
The invention provides a method for synchronizing configuration information of an Internet of things server, which is characterized in that main configuration and a collected data list are configured synchronously, wherein the main configuration comprises a collection period, serial port configuration and a collection protocol; the method and the device can realize the synchronous configuration of the Internet of things platform and the terminal information, reduce the error probability of operators, reduce the maintenance cost and reduce the threshold of the terminal connected with the Internet of things platform.
Description
Technical Field
The invention relates to a network information processing method, in particular to a synchronous processing method for configuration information of an Internet of things server.
Background
With the continuous development of the internet of things, the development of various industries is influenced and changed at an unprecedented speed in the age of the internet of things, the number of corresponding terminals of the internet of things is increased, and the mode of configuration information of an internet of things platform and the terminals is very important. In the prior art, before using the terminals of the internet of things, configuration information of each terminal of the internet of things needs to be manually acquired and correspondingly configured in the platform of the internet of things. Therefore, each operator needs to know the configuration information of each internet of things terminal in advance to configure the internet of things terminal. The mode of the terminal configuration information of the Internet of things not only increases the error probability of an operator in configuring the terminal of the Internet of things. Meanwhile, the terminal of the internet of things is reset when being repaired or replaced, so that the maintenance cost is increased, and the threshold of the terminal for connecting the internet of things platform is increased.
Disclosure of Invention
The invention aims to provide a method for synchronizing configuration information of an Internet of things server, aiming at the defects of the prior art.
In order to achieve the purpose, the technical scheme of the invention is as follows: a method for synchronizing configuration information of an Internet of things server is characterized in that a main configuration and a collected data list are required to be configured synchronously, wherein the main configuration comprises a collection period, a serial port configuration and a collection protocol; the specific implementation steps are as follows:
the method comprises the following steps: a gateway is newly built on a server, main configuration and a data list needing to be collected are input into the gateway, and the input attribute is set as WA and is stored in a database of the server;
step two: connecting the hardware to the server, wherein the hardware gateway can actively send a hardware registration identifier to the server, and the whole connection process can be encrypted;
step three: when the server receives the hardware registration identifier, registering the hardware, and judging whether the hardware is bound, if not, entering a fourth step, and if so, entering an eighth step;
step four: entering a gateway configuration interface on the server, inputting the hardware registration identifier and the password in the step 2, clicking a determination button, binding the server and the hardware, setting all attribute states in the gateway to be WA after binding, modifying the gateway state to be Need Clear, and entering the step five;
step five: after the server is bound with the hardware, sending a hardware configuration information clearing request to the hardware, modifying the state of the gateway into Clear Sent in the server, and waiting for the response of the hardware;
step six: after receiving a hardware configuration information clearing request sent by a server, the hardware clears the configuration information data of the hardware, and after the clearing operation is completed, a response of successful clearing is sent to the server;
step seven: after receiving the response of clearing the hardware configuration information, the server modifies the gateway state into clear, and enters step eight;
step eight: the server judges the configuration state of the gateway:
a. if the gateway state is Need Clear or Clear Sent, it indicates that the server has Sent an emptying request, but the hardware is not emptied successfully, and in the process of hardware emptying data, an error occurs, and if the situation is met, the server will adjust and return to step five;
b. if the gateway state is clear or Main Config set, it indicates that the hardware has not completed any configuration at present, and enters step nine;
c. if the gateway state is Property Need Config, it indicates that the attribute list has not completed configuration synchronization, and enters step twelve;
d. if the gateway state is Running, the hardware is proved to finish all configuration synchronization, and the method directly enters the twenty-two step;
step nine: the server sends a write master configuration request to the hardware, identifies the gateway state as a Main Config Sent, and waits for the response of the hardware;
step ten: the hardware writes the main configuration sent by the server into the Flash chip, and if the main configuration is successfully written, a response that the main configuration is successfully written is sent to the server;
step eleven: the server receives the response that the main configuration of the hardware is successfully written, identifies the state of the gateway as Property Need Config, and enters a step twelve;
step twelve: in a server database, according to a gateway identifier, inquiring an attribute of which the first state is not R:
a. if the state which cannot be inquired is not the R attribute, all the configuration is finished, and the operation enters twenty-two step;
b. if one state is not the R attribute, executing corresponding operation according to the state of the attribute;
c. if the attribute state is WA or AS, it indicates that the attribute has not been successfully added to the hardware, and enters step thirteen;
d. if the attribute state is WU or US, it indicates that the attribute has not been successfully modified on hardware, and step sixteen is entered;
e. if the attribute state is WD or DS, the attribute is not successfully deleted on hardware, and the method enters nineteen steps;
step thirteen: the server sends a new attribute request to the hardware, sets the corresponding attribute state AS AS, and waits for the hardware to respond;
fourteen steps: the hardware receives an attribute adding request sent by the server, adds the attribute to Flash, and sends a response of successful addition to the server;
step fifteen: the server receives the response that the newly added attribute of the hardware is successful, identifies the attribute in the server as R, and returns to the step twelve;
sixthly, the steps are as follows: the server sends an attribute modification request to the hardware, sets the corresponding attribute state as US, and waits for the hardware to respond;
seventeen steps: the hardware receives an attribute modification request sent by the server, modifies the corresponding attribute in Flash, and sends a response of successful modification to the server;
eighteen steps: the server receives the response that the attribute modification of the hardware is successful, identifies the attribute in the server as R, and returns to the step twelve;
nineteen steps: the server sends a request for deleting the attribute to the hardware, sets the corresponding attribute state as DS, and waits for the response of the hardware;
twenty steps: the hardware receives an attribute deletion request sent by the server, deletes the corresponding attribute in Flash, and sends a response of successful deletion to the server;
twenty one: the server receives the response of successful attribute deletion sent by the hardware, really deletes the corresponding attribute on the server, and returns to the step twelve;
step twenty-two: and all the configurations are synchronized, the server modifies the identification of the gateway into Running, and all the synchronization operations are completed.
Further, the additional triggers are as follows:
when the user modifies the main configuration at the server, the gateway identifier is set to be clear, and the step eight is carried out;
when the user adds an attribute at the server, the attribute state is modified to WA, the corresponding gateway identification is set to Property Need Config, and then the step eight is directly entered;
when the user modifies an attribute at the server, modifying the attribute state into WU, setting the corresponding gateway identifier as Property Need Config, and then directly entering step eight;
when the user deletes one attribute at the server, the attribute state is modified to WD, the corresponding gateway identifier is set to Property Need Config, and then the step eight is directly entered;
when the user releases the association between the gateway and the hardware, the server does not perform any operation;
and when the user finds that the hardware is damaged or needs to be replaced, the binding operation is executed again, the server can remove the old binding, directly use the new binding, set the gateway state to Need Clear, and then enter the step eight.
Further, when an error occurs in the configuration process of the hardware, the process returns to step eight, and in step eight, the synchronous configuration is continued by judging the configuration state identifier of the hardware gateway.
Further, the Need Clear is that the hardware configuration needs to be cleared; the Clear Sent is a Clear request Sent; the Cleared is non-configuration data; the Main Config set is a write master configuration request Sent; the Property Need Config is a list of properties which Need to be synchronized by hardware; the Running is synchronized for configuration and is in operation; the R is that the attribute is synchronized; the AS is sent for the new attribute request; the WU is used for waiting for synchronous modification of attributes; WA is waiting for hardware to be synchronously newly added; the US is sent for modifying the attribute request; the WD is the synchronous deletion of the waiting attribute; the DS is sent for deleting the attribute request.
The invention has the beneficial effects that: the method and the device can realize the synchronous configuration of the Internet of things platform and the terminal information, reduce the error probability of operators, reduce the maintenance cost and reduce the threshold of the terminal connected with the Internet of things platform.
Drawings
Fig. 1 is a schematic diagram of a method for synchronously processing configuration information of an internet of things server according to the present invention.
Detailed Description
Referring to fig. 1, a method for synchronizing configuration information of an internet of things server and a hardware terminal includes configuring a main configuration and a data list to be acquired synchronously, where the main configuration includes an acquisition period, a serial port configuration and an acquisition protocol; the specific implementation steps are as follows:
the method comprises the following steps: a gateway is newly built on a server, main configuration and a data list needing to be collected are input into the gateway, and the input attribute is set as WA and is stored in a database of the server;
step two: connecting the hardware to the server, wherein the hardware gateway can actively send a hardware registration identifier to the server, and the whole connection process can be encrypted;
step three: when the server receives the hardware registration identifier, registering the hardware, and judging whether the hardware is bound, if not, entering a fourth step, and if so, entering an eighth step;
step four: entering a gateway configuration interface on the server, inputting the hardware registration identifier and the password in the step 2, clicking a determination button, binding the server and the hardware, setting all attribute states in the gateway to be WA after binding, modifying the gateway state to be Need Clear, and entering the step five;
step five: after the server is bound with the hardware, sending a hardware configuration information clearing request to the hardware, modifying the state of the gateway into Clear Sent in the server, and waiting for the response of the hardware;
step six: after receiving a hardware configuration information clearing request sent by a server, the hardware clears the configuration information data of the hardware, and after the clearing operation is completed, a response of successful clearing is sent to the server;
step seven: after receiving the response of clearing the hardware configuration information, the server modifies the gateway state into clear, and enters step eight;
step eight: the server judges the configuration state of the gateway:
a. if the gateway state is Need Clear or Clear Sent, it indicates that the server has Sent an emptying request, but the hardware is not emptied successfully, and in the process of hardware emptying data, an error occurs, and if the situation is met, the server will adjust and return to step five;
b. if the gateway state is clear or Main Config set, it indicates that the hardware has not completed any configuration at present, and enters step nine;
c. if the gateway state is Property Need Config, it indicates that the attribute list has not completed configuration synchronization, and enters step twelve;
d. if the gateway state is Running, the hardware is proved to finish all configuration synchronization, and the method directly enters the twenty-two step;
step nine: the server sends a write master configuration request to the hardware, identifies the gateway state as a Main Config Sent, and waits for the response of the hardware;
step ten: the hardware writes the main configuration sent by the server into the Flash chip, and if the main configuration is successfully written, a response that the main configuration is successfully written is sent to the server;
step eleven: the server receives the response that the main configuration of the hardware is successfully written, identifies the state of the gateway as Property Need Config, and enters a step twelve;
step twelve: in a server database, according to a gateway identifier, inquiring an attribute of which the first state is not R:
a. if the state which cannot be inquired is not the R attribute, all the configuration is finished, and the operation enters twenty-two step;
b. if one state is not the R attribute, executing corresponding operation according to the state of the attribute;
c. if the attribute state is WA or AS, it indicates that the attribute has not been successfully added to the hardware, and enters step thirteen;
d. if the attribute state is WU or US, it indicates that the attribute has not been successfully modified on hardware, and step sixteen is entered;
e. if the attribute state is WD or DS, the attribute is not successfully deleted on hardware, and the method enters nineteen steps;
step thirteen: the server sends a new attribute request to the hardware, sets the corresponding attribute state AS AS, and waits for the hardware to respond;
fourteen steps: the hardware receives an attribute adding request sent by the server, adds the attribute to Flash, and sends a response of successful addition to the server;
step fifteen: the server receives the response that the newly added attribute of the hardware is successful, identifies the attribute in the server as R, and returns to the step twelve;
sixthly, the steps are as follows: the server sends an attribute modification request to the hardware, sets the corresponding attribute state as US, and waits for the hardware to respond;
seventeen steps: the hardware receives an attribute modification request sent by the server, modifies the corresponding attribute in Flash, and sends a response of successful modification to the server;
eighteen steps: the server receives the response that the attribute modification of the hardware is successful, identifies the attribute in the server as R, and returns to the step twelve;
nineteen steps: the server sends a request for deleting the attribute to the hardware, sets the corresponding attribute state as DS, and waits for the response of the hardware;
twenty steps: the hardware receives an attribute deletion request sent by the server, deletes the corresponding attribute in Flash, and sends a response of successful deletion to the server;
twenty one: the server receives the response of successful attribute deletion sent by the hardware, really deletes the corresponding attribute on the server, and returns to the step twelve;
step twenty-two: and all the configurations are synchronized, the server modifies the identification of the gateway into Running, and all the synchronization operations are completed.
Further, the additional triggers are as follows:
when the user modifies the main configuration at the server, the gateway identifier is set to clear, and step eight is entered.
When the user adds an attribute at the server, the attribute state is modified to WA, the corresponding gateway identification is set to Property Need Config, and then the step eight is directly entered;
when the user modifies an attribute at the server, modifying the attribute state into WU, setting the corresponding gateway identifier as Property Need Config, and then directly entering step eight;
when the user deletes one attribute at the server, the attribute state is modified to WD, the corresponding gateway identifier is set to Property Need Config, and then the step eight is directly entered;
when the user releases the association between the gateway and the hardware, the server does not perform any operation;
and when the user finds that the hardware is damaged or needs to be replaced, the binding operation is executed again, the server can remove the old binding, directly use the new binding, set the gateway state to Need Clear, and then enter the step eight.
Further, when an error occurs in the configuration process of the hardware, the process returns to step eight, and in step eight, the synchronous configuration is continued by judging the configuration state identifier of the hardware gateway.
Further, the Need Clear is that the hardware configuration needs to be cleared; the Clear Sent is a Clear request Sent; the Cleared is non-configuration data; the Main Config set is a write master configuration request Sent; the Property Need Config is a list of properties which Need to be synchronized by hardware; the Running is synchronized for configuration and is in operation; the R is that the attribute is synchronized; the AS is sent for the new attribute request; the WU is used for waiting for synchronous modification of attributes; WA is waiting for hardware to be synchronously newly added; the US is sent for modifying the attribute request; the WD is the synchronous deletion of the waiting attribute; the DS is sent for deleting the attribute request.
The method and the device can realize the synchronous configuration of the Internet of things platform and the terminal information, reduce the error probability of operators, reduce the maintenance cost and reduce the threshold of the terminal connected with the Internet of things platform.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Claims (3)
1. A method for synchronizing configuration information of an Internet of things server is characterized in that a main configuration and a collected data list are configured to be synchronized, wherein the main configuration comprises a collection period, a serial port configuration and a collection protocol; the specific implementation steps are as follows:
the method comprises the following steps: a gateway is newly built on a server, main configuration and a data list needing to be collected are input into the gateway, and the input attribute is set as WA and is stored in a database of the server;
step two: connecting the hardware to the server, wherein the hardware gateway can actively send a hardware registration identifier to the server, and the whole connection process can be encrypted;
step three: when the server receives the hardware registration identifier, registering the hardware, and judging whether the hardware is bound, if not, entering a fourth step, and if so, entering an eighth step;
step four: entering a gateway configuration interface on the server, inputting the hardware registration identifier and the password in the step 2, clicking a determination button, binding the server and the hardware, setting all attribute states in the gateway to be WA after binding, modifying the gateway state to be Need Clear, and entering the step five;
step five: after the server is bound with the hardware, sending a hardware configuration information clearing request to the hardware, modifying the state of the gateway into Clear Sent in the server, and waiting for the response of the hardware;
step six: after receiving a hardware configuration information clearing request sent by a server, the hardware clears the configuration information data of the hardware, and after the clearing operation is completed, a response of successful clearing is sent to the server;
step seven: after receiving the response of clearing the hardware configuration information, the server modifies the gateway state into clear, and enters step eight;
step eight: the server judges the configuration state of the gateway:
a. if the gateway state is Need Clear or Clear Sent, it indicates that the server has Sent an emptying request, but the hardware is not emptied successfully, and in the process of hardware emptying data, an error occurs, and if the situation is met, the server will adjust and return to step five;
b. if the gateway state is clear or Main Config set, it indicates that the hardware has not completed any configuration at present, and enters step nine;
c. if the gateway state is Property Need Config, it indicates that the attribute list has not completed configuration synchronization, and enters step twelve;
d. if the gateway state is Running, the hardware is proved to finish all configuration synchronization, and the method directly enters the twenty-two step;
step nine: the server sends a write master configuration request to the hardware, identifies the gateway state as a Main Config Sent, and waits for the response of the hardware;
step ten: the hardware writes the main configuration sent by the server into the Flash chip, and if the main configuration is successfully written, a response that the main configuration is successfully written is sent to the server;
step eleven: the server receives the response that the main configuration of the hardware is successfully written, identifies the state of the gateway as Property Need Config, and enters a step twelve;
step twelve: in a server database, according to a gateway identifier, inquiring an attribute of which the first state is not R:
a. if the state which cannot be inquired is not the R attribute, all the configuration is finished, and the operation enters twenty-two step;
b. if one state is not the R attribute, executing corresponding operation according to the state of the attribute;
c. if the attribute state is WA or AS, it indicates that the attribute has not been successfully added to the hardware, and enters step thirteen;
d. if the attribute state is WU or US, it indicates that the attribute has not been successfully modified on hardware, and step sixteen is entered;
e. if the attribute state is WD or DS, the attribute is not successfully deleted on hardware, and the method enters nineteen steps;
step thirteen: the server sends a new attribute request to the hardware, sets the corresponding attribute state AS AS, and waits for the hardware to respond;
fourteen steps: the hardware receives an attribute adding request sent by the server, adds the attribute to Flash, and sends a response of successful addition to the server;
step fifteen: the server receives the response that the newly added attribute of the hardware is successful, identifies the attribute in the server as R, and returns to the step twelve;
sixthly, the steps are as follows: the server sends an attribute modification request to the hardware, sets the corresponding attribute state as US, and waits for the hardware to respond;
seventeen steps: the hardware receives an attribute modification request sent by the server, modifies the corresponding attribute in Flash, and sends a response of successful modification to the server;
eighteen steps: the server receives the response that the attribute modification of the hardware is successful, identifies the attribute in the server as R, and returns to the step twelve;
nineteen steps: the server sends a request for deleting the attribute to the hardware, sets the corresponding attribute state as DS, and waits for the response of the hardware;
twenty steps: the hardware receives an attribute deletion request sent by the server, deletes the corresponding attribute in Flash, and sends a response of successful deletion to the server;
twenty one: the server receives the response of successful attribute deletion sent by the hardware, really deletes the corresponding attribute on the server, and returns to the step twelve;
step twenty-two: all the configurations are synchronized, the server modifies the identification of the gateway into Running, and all the synchronization operations are completed;
the Need Clear is the Need to Clear the hardware configuration; the Clear Sent is a Clear request Sent; the Cleared is non-configuration data; the Main Config set is a write master configuration request Sent; the Property Need Config is a list of properties which Need to be synchronized by hardware; the Running is synchronized for configuration and is in operation; the R is that the attribute is synchronized; the AS is sent for the new attribute request; the WU is used for waiting for synchronous modification of attributes; WA is waiting for hardware to be synchronously newly added; the US is sent for modifying the attribute request; the WD is the synchronous deletion of the waiting attribute; the DS is sent for deleting the attribute request.
2. The method for synchronizing the configuration information of the servers in the internet of things according to claim 1, wherein the additional triggers are as follows:
when the user modifies the main configuration at the server, the gateway identifier is set to be clear, and the step eight is carried out;
when the user adds an attribute at the server, the attribute state is modified to WA, the corresponding gateway identification is set to Property Need Config, and then the step eight is directly entered;
when the user modifies an attribute at the server, modifying the attribute state into WU, setting the corresponding gateway identifier as Property Need Config, and then directly entering step eight;
when the user deletes one attribute at the server, the attribute state is modified to WD, the corresponding gateway identifier is set to Property Need Config, and then the step eight is directly entered;
when the user releases the association between the gateway and the hardware, the server does not perform any operation;
and when the user finds that the hardware is damaged or needs to be replaced, the binding operation is executed again, the server can remove the old binding, directly use the new binding, set the gateway state to Need Clear, and then enter the step eight.
3. The method for synchronizing the configuration information of the servers of the internet of things according to claim 1, wherein the method comprises the following steps: and when the hardware has errors in the configuration process, returning to the step eight, and in the step eight, continuing synchronous configuration by judging the configuration state identifier of the hardware gateway.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910165479.7A CN109714218B (en) | 2019-03-05 | 2019-03-05 | Internet of things server configuration information synchronization method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910165479.7A CN109714218B (en) | 2019-03-05 | 2019-03-05 | Internet of things server configuration information synchronization method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109714218A CN109714218A (en) | 2019-05-03 |
| CN109714218B true CN109714218B (en) | 2021-11-23 |
Family
ID=66266249
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910165479.7A Active CN109714218B (en) | 2019-03-05 | 2019-03-05 | Internet of things server configuration information synchronization method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109714218B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112506704B (en) * | 2020-12-05 | 2022-01-18 | 广州技象科技有限公司 | Configuration information backup method and device for gateway of Internet of things |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101465732A (en) * | 2007-12-19 | 2009-06-24 | 联想(北京)有限公司 | Method and terminal for ensuring digital certificate safety |
| CN102355360A (en) * | 2011-06-29 | 2012-02-15 | 北京天地互连信息技术有限公司 | Binding system of equipment object, gateway and database and binding method |
| EP1042877B1 (en) * | 1997-12-23 | 2013-11-27 | Comcast MO Group, Inc. | Method and system for automatic allocation of resources in a network |
| CN103888257A (en) * | 2013-11-03 | 2014-06-25 | 北京工业大学 | Network camera identity authentication method based on TPCM |
| CN105897571A (en) * | 2016-04-07 | 2016-08-24 | 周文奇 | Industrial communication security gateway |
| CN109040224A (en) * | 2018-07-27 | 2018-12-18 | 佛山点度物联科技有限公司 | A kind of Internet of things hardware data actively acquire analysis system and method |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080126617A1 (en) * | 2006-08-28 | 2008-05-29 | Sean Thomas Brownlow | Message Signaled Interrupt Management for a Computer Input/Output Fabric Incorporating Dynamic Binding |
-
2019
- 2019-03-05 CN CN201910165479.7A patent/CN109714218B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1042877B1 (en) * | 1997-12-23 | 2013-11-27 | Comcast MO Group, Inc. | Method and system for automatic allocation of resources in a network |
| CN101465732A (en) * | 2007-12-19 | 2009-06-24 | 联想(北京)有限公司 | Method and terminal for ensuring digital certificate safety |
| CN102355360A (en) * | 2011-06-29 | 2012-02-15 | 北京天地互连信息技术有限公司 | Binding system of equipment object, gateway and database and binding method |
| CN103888257A (en) * | 2013-11-03 | 2014-06-25 | 北京工业大学 | Network camera identity authentication method based on TPCM |
| CN105897571A (en) * | 2016-04-07 | 2016-08-24 | 周文奇 | Industrial communication security gateway |
| CN109040224A (en) * | 2018-07-27 | 2018-12-18 | 佛山点度物联科技有限公司 | A kind of Internet of things hardware data actively acquire analysis system and method |
Non-Patent Citations (2)
| Title |
|---|
| Topical issues of application of time-frequency synchronization equipment on the communication network of Russia;M.N.Koltunov，M.L.Schwartz;《SYNCHROINFO》;20180910;全文 * |
| 基于Struts和Hibernate的购物系统后台机器安全的研究与实现;赵彦超;《中国优秀硕士论文数据库》;20131231;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109714218A (en) | 2019-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108549580B (en) | Method for automatically deploying Kubernets slave nodes and terminal equipment | |
| CN109582588B (en) | Test case generation method and device and electronic equipment | |
| CN106528871B (en) | A kind of method of online updating industrial control system project data point information | |
| CN110401662B (en) | Industrial control equipment fingerprint identification method and storage medium | |
| CN105653630B (en) | Data migration method and device for distributed database | |
| CN109344053B (en) | Interface coverage test method, system, computer device and storage medium | |
| CN105808273B (en) | Method for upgrading software and software updating apparatus | |
| CN107347017A (en) | The method, apparatus and configuration point device of a kind of device upgrade | |
| CN109714218B (en) | Internet of things server configuration information synchronization method | |
| CN113312336A (en) | Data processing method, data processing apparatus, electronic device, storage medium, and program product | |
| CN112698640B (en) | ECU upgrading test system | |
| CN103645922B (en) | It is a kind of that the method, apparatus and system for carrying out software cleaning are inquired about based on cloud | |
| CN104580425A (en) | Client data synchronization method and system | |
| CN114362983A (en) | Firewall policy management method and device, computer equipment and storage medium | |
| CN106126634A (en) | A kind of master data duplicate removal treatment method based on live industry and system | |
| CN110059077A (en) | A kind of verification of data method, apparatus, equipment and storage medium | |
| CN110807000B (en) | File repair method and device, electronic equipment and storage medium | |
| JP2014035595A (en) | Testing device for communication system, testing program for communication system, and testing method for communication system | |
| CN109144989B (en) | Data cleaning method and device | |
| CN111638939A (en) | Management system and method for application life cycle of Kubernetes container platform | |
| CN111198698A (en) | EtherCAT-based multi-device firmware program parallel downloading method and system | |
| CN112416557B (en) | Method and device for determining call relation, storage medium and electronic device | |
| CN105389253B (en) | The method and system of NE management are performed based on multithreading simulant-client | |
| CN109814871B (en) | Node management method and system based on DDS bus | |
| CN104753659A (en) | Method, device and system for multiple network element data synchronized load |
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 |