CN112437144B - Method and system for increasing access number of single edge server iot equipment - Google Patents
Method and system for increasing access number of single edge server iot equipment Download PDFInfo
- Publication number
- CN112437144B CN112437144B CN202011281228.4A CN202011281228A CN112437144B CN 112437144 B CN112437144 B CN 112437144B CN 202011281228 A CN202011281228 A CN 202011281228A CN 112437144 B CN112437144 B CN 112437144B
- Authority
- CN
- China
- Prior art keywords
- edge server
- iot
- alive
- retry
- plug
- 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/14—Session management
- H04L67/141—Setup of application sessions
-
- 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/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
-
- 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/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a method for increasing the access number of a single edge server iot device, which comprises the following steps: s1, presetting an edge server registration rule, identifying an edge server according to the edge server registration rule, if the identification is successful, registering the edge server for the first time, and if the identification is failed, entering the step S2; s2, judging the network condition, if the network condition is stable, re-registering the edge server, if the network condition is unstable, waiting for the network condition to be stable, and then re-registering the edge server; s3, conducting heartbeat keep-alive through UDP; s4, reverse triggering iot the device and connecting iot the device to the card center to obtain card center data. The invention also discloses a system for increasing the access number of the single edge server iot device, which comprises an edge server unit, a network unit, a heartbeat keep-alive unit and a data acquisition unit.
Description
Technical Field
The invention relates to the field of iot equipment, in particular to a method and a system for increasing the access number of single edge server iot equipment.
Background
Remotely controlling iot devices with lower aging requirements and receiving iot messages pushed by devices in real time if a connection is established to maintain communication with the edge server. If the tcp is used alone to maintain the connection, the following problems can exist: 1. iot devices have high power consumption, maintaining tcp long connections consumes a lot of built-in battery power; 2. one device and one tcp connection are communicated with the server, and the method of the tape count of a single edge server is few.
Disclosure of Invention
In order to solve the above problems, the present invention provides a method and a system for increasing the access number of a single edge server iot device, which can optimize the power consumption of iot device for maintaining connection with the server, and also increase the number of devices in the single edge server.
In order to solve the above technical problem, the present invention provides a method for increasing the access number of a single edge server iot device, comprising the following steps:
s1, presetting an edge server registration rule, identifying an edge server according to the edge server registration rule, if the identification is successful, registering the edge server for the first time, and if the identification is failed, entering the step S2;
s2, judging the network condition, if the network condition is stable, re-registering the edge server, if the network condition is unstable, waiting for the network condition to be stable, and then re-registering the edge server;
s3, conducting heartbeat keep-alive through UDP;
s4, reverse triggering iot the device and connecting iot the device to the card center to obtain card center data.
The working principle of the technical scheme is as follows: the method comprises the steps that the edge server is registered for the first time through an identification rule, after the registration for the first time fails, iot equipment conducts security verification and registration for the edge server again, after the security verification is passed, the registration for the second time can be successful, heartbeat keep-alive is conducted through UDP, TCP is used in the heartbeat keep-alive process, but the TCP is only used for establishing and transmitting data when the data is transmitted, and the TCP is closed after the data is transmitted, so that the low power consumption of the equipment is guaranteed, UDP provides a method for an application program to send an encapsulated IP data packet without establishing connection, the method is used for receiving and sending heartbeat keep-alive messages, finally the data is stored in a plug-in center, and the device is connected to the plug-in center to obtain the data through reverse triggering iot.
In a further technical solution, the edge registration rule in step S1 includes:
judging whether the edge server responds or returns to a preset value, if so, circularly selecting all server IP addresses in the DNS analysis result and retrying, wherein the retrying interval is 60 seconds;
if the retry fails for 5 times, the terminal should randomly silence 10 to 60 retry intervals and then re-analyze the DNS of the edge server and repeat the above registration and retry processes;
if registration and retry in consecutive 3 resolution DNS cycles fail, the IOT device should re-register with the distributing edge server.
In the technical scheme, when iot equipment registers to an edge server for the first time, preset return bytes such as 0, -1 and challenge code are provided, when a preset 0 is returned, the edge server simultaneously returns challenge code for next step to authenticate iot equipment, if no response of the edge server is received or the edge server returns preset-1, all server IP addresses in DNS resolution results should be selected circularly for retry, the retry interval is 60 seconds, if 5 retries fail, the terminal should randomly silence 10 to 60 retry intervals and then re-resolve DNS of the edge server and repeat the above registration and retry processes, and if registration and retry in DNS cycle are all failed for three consecutive times, iot equipment should re-register to a distribution edge server.
In a further technical solution, the step S2 of determining the network status includes:
and judging whether the edge server responds or not, presetting the response time to be 10 seconds, retrying by using the same server port by the terminal, presetting the first retrying interval to be 60 seconds, and repeating for three times, and if the third retrying does not receive a reply, judging that the network state is not good.
In the technical scheme, when the step S1 is successful, a challangecode is obtained, the challangecode is spliced with a device ID, an ID value is calculated, the edge server finds the device ID of the device in the database through the address in the step S1, the ID value is calculated by the same method and then compared, if the ID value is the same, authentication is successful, then whether the ID value is the same as the ID of the iot device previously stored by the edge server is judged, if the ID value is the same as the ID previously stored by the edge server, a preset value is returned, the preset value is set to be 2 and carries a heartbeat server address parameter, if the ID is null, the heartbeat server is the same as a registration server address parameter, when the edge server finds that the ID of the iot device does not exist or is not the same, the edge server stores a new ID and returns the preset value, the preset value is set to be 3 and carries the heartbeat server address parameter, and similarly, if the ID is null, the heartbeat server is the same as the registration server address parameter, if the preset value is not matched and returned, the preset value is set to be-2, after the preset value is returned to be-2, the operation is carried out for 150 minutes in a silent mode, the operation of registering the edge server by the iot equipment is carried out again, the preset corresponding time is 10 seconds, if the edge server does not respond in the 10 seconds, the terminal applies the same server port to retry, the retry interval is 60 seconds for the first time, and the retransmission is carried out for 3 times; if no reply is received for 3 retries. The registration of the device with the edge server is resumed iot.
In a further technical solution, the re-registering the edge server after the network state is stabilized in step S2 includes:
presetting an updated parameter field and reporting the updated parameter field to an edge server, and performing compatibility processing on the parameter field by the edge server;
if the edge server does not receive the parameter field, the edge server refreshes and judges that the network state is not stable;
if the edge server receives the parameter field, the edge server does not need to refresh, and judges that the network state is stable and registers the edge server again.
In the technical scheme, a return information field is preset, and if the return information has the preset field, a new heartbeat interval is needed for working; iot the device should update the parameter and report to the edge server; the edge server should perform compatibility processing on it, if the edge server receives this field, the edge server should refresh the value, if not, the edge server should not refresh.
In a further technical solution, the performing heartbeat keep-alive through UDP in step S3 includes:
presetting a heartbeat keep-alive time interval, wherein the heartbeat keep-alive time interval is 60 seconds, and the heartbeat keep-alive is reported every 60 seconds;
presetting a retry time interval, wherein the retry time interval is 30 seconds;
if the edge server does not receive a heartbeat keep alive report, retry is initiated, and if a reply is not received after three retry intervals, the device registers with the edge server back iot.
In the technical scheme, a first heartbeat FLAG is preset, and when iot equipment is registered and a heartbeat message is sent to an edge server for the first time, the FLAG is preset to be 1; if the result in the message returned by the edge server is a preset value of 0, the iot equipment sends a heartbeat message to the edge server later, and the mark is set to be 0 for a month; when FLAG is 1, the message should carry a preset IPAddr field; when FLAG is 0, the message should not carry an IPAddr field; reported every 60 seconds: if the reply is not received within 30 seconds, the retry is started, and the retry interval is 30 seconds; the reason why the retry interval is 30 seconds is that 30 seconds is half of the retry interval, and the reason for reducing the retry interval is that an accidental packet drop may cause aging of the intermediate device; if the reply is not received after 3 times of retries, the device returns to iot to register with the edge server, when the reply is received, the positive edge server is kept, if the preset value-3 is returned, the device needs to iot to register with the edge server again, namely, the device returns to iot to register with the edge server, and if the returned information has a preset Interval, the device needs to work with a new heartbeat Interval.
In a further aspect, the step S4 of triggering iot devices in a reverse direction and connecting iot devices to the card center to obtain card center data includes:
if iot the device is processing the reverse trigger connection flow, after receiving the reverse trigger connection, it should wait to process the reverse trigger connection flow and then perform the reverse trigger connection;
if iot equipment is connected to the plug-in center, it receives reverse trigger connection, when the domain name and port number in the message are the same as those stored in iot equipment, it processes neglect, otherwise it needs to disconnect the current connection with the plug-in center actively, and register and connect new plug-in center again.
In the technical scheme, the device iot is triggered reversely, the iot device splices the device ID with the DevRND value sent to the edge server last time, and calculates an MD5 value, and compares the MD5 value with the Key in the request, so that the iot device should follow the following policy: iot after receiving the request, the device should first determine whether the key is the same as the previous one, if so, the edge server retransmits the message and replies the current DevRND and result code; otherwise, splicing the device ID by using the current DevRND value, calculating the MD5 value, comparing with the Key in the request, and if the values are the same, connecting the iot device with the specified plug-in center server, wherein the protocol is shown in the plug-in center protocol. And iot the device responds with a preset value of 0 and the next use of DevrRND. The edge server receives the new DevRND and returns to 1. If no results are received, the iot device should retry three times for a timeout of 5 seconds. If still failing, go back to iot where the device registers with the edge server; if not, iot device should return to preset value-1, and iot device should restart to register with the edge server; if the edge server responds-1, iot the device should resume iot the device's registration with the edge server; if the iot device is processing the reverse trigger connection flow, the iot device receives the reverse trigger connection again, the reverse trigger connection of the edge server should be the message retransmission of the edge server, and the message should be processed according to the above strategy after the reverse trigger flow is completed. If IOT equipment is connected to the plug-in center, it receives the reverse trigger connection, when the domain name and port number in the message are the same as that stored by IOT equipment, it ignores, otherwise it needs to disconnect the current connection with the plug-in center actively, and re-register and connect the new plug-in center. When the edge server receives the reverse trigger request again in the process of processing the reverse trigger connection flow, the edge server should filter out the reverse trigger request. When the message suggests that the edge server interacts with iot equipment, a retransmission mechanism is adopted, so that the edge server retransmits a reverse trigger message to iot equipment, if iot equipment receives a plurality of reverse trigger messages and keys are the same, the result messages should be sequentially returned to the edge server, and if the result messages are simultaneously returned to the same 'DevRND' edge server and a plurality of result values are received, and if the DevRND is the same, the result messages should be sequentially fed back to iot equipment, and after iot equipment receives one of the result messages, the DevRND takes effect.
The invention also provides a system for increasing the access number of the single edge server iot, which comprises: edge server unit, network element, heartbeat keep alive unit and data acquisition unit, wherein:
the edge server unit is used for presetting an edge server registration rule, identifying the edge server according to the edge server registration rule, registering the edge server for the first time if the identification is successful, and entering the network unit if the identification is failed;
the network unit is used for judging the network condition, if the network condition is stable, the edge server is registered again, and if the network condition is unstable, the edge server is registered again after the network condition is stable;
the heartbeat keep-alive unit is used for keeping heartbeat keep-alive through UDP;
a data acquisition unit for triggering iot the device in reverse and connecting iot the device to the plug-in center to acquire plug-in center data.
The invention has the beneficial effects that:
1. optimizing iot power consumption of the device and the server maintaining the connection;
2. and the number of the belt machines of the single edge server is increased.
Drawings
Fig. 1 is a flowchart of a method for increasing the access number of a single edge server iot according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a system for increasing the access number of a single edge server iot according to an embodiment of the present invention.
Description of reference numerals:
10. an edge server unit; 11. a network unit; 12. a heartbeat keep-alive unit; 13. a data acquisition unit.
Detailed Description
The embodiments of the present invention will be further described with reference to the accompanying drawings.
Example (b):
as shown in fig. 1, a method for increasing the access number of a single edge server iot device includes the following steps:
s1, presetting an edge server registration rule, identifying an edge server according to the edge server registration rule, if the identification is successful, registering the edge server for the first time, and if the identification is failed, entering the step S2;
s2, judging the network condition, if the network condition is stable, re-registering the edge server, if the network condition is unstable, waiting for the network condition to be stable, and then re-registering the edge server;
s3, conducting heartbeat keep-alive through UDP;
s4, reverse triggering iot the device and connecting iot the device to the card center to obtain card center data.
The working principle of the above embodiment is as follows: the method comprises the steps that the edge server is registered for the first time through an identification rule, after the registration for the first time fails, iot equipment conducts security verification and registration for the edge server again, after the security verification is passed, the registration for the second time can be successful, heartbeat keep-alive is conducted through UDP, TCP is used in the heartbeat keep-alive process, but the TCP is only used for establishing and transmitting data when the data is transmitted, and the TCP is closed after the data is transmitted, so that the low power consumption of the equipment is guaranteed, UDP provides a method for an application program to send an encapsulated IP data packet without establishing connection, the method is used for receiving and sending heartbeat keep-alive messages, finally the data is stored in a plug-in center, and the device is connected to the plug-in center to obtain the data through reverse triggering iot.
In another embodiment, the edge registration rule in step S1 includes:
judging whether the edge server responds or returns to a preset value, if so, circularly selecting all server IP addresses in the DNS analysis result and retrying, wherein the retrying interval is 60 seconds;
if the retry fails for 5 times, the terminal should randomly silence 10 to 60 retry intervals and then re-analyze the DNS of the edge server and repeat the above registration and retry processes;
if registration and retry in consecutive 3 resolution DNS cycles fail, the IOT device should re-register with the distributing edge server.
In this embodiment, iot apparatus registers to the edge server for the first time, preset return bytes such as 0, -1 and challenge code, when returning to preset 0, the edge server returns challenge code at the same time, which is used for verifying iot apparatus in the next step, if no response is received from the edge server or the edge server returns preset-1, all server IP addresses in the DNS resolution result should be selected in a loop for retry, the retry interval is 60 seconds, if 5 retries fail, the terminal should randomly silence 10 to 60 retry intervals and then re-resolve the DNS of the edge server and repeat the above registration and retry process, if registration and retry in three consecutive resolution cycles all fail, the iot apparatus should re-register to the distributing edge server.
In another embodiment, the step S2 of determining the network condition includes:
and judging whether the edge server responds or not, presetting the response time to be 10 seconds, retrying by using the same server port by the terminal, presetting the first retrying interval to be 60 seconds, and repeating for three times, and if the third retrying does not receive a reply, judging that the network state is not good.
In this embodiment, when step S1 succeeds, a challangecode is obtained, the challangecode is concatenated with a device ID, an ID value is calculated, the edge server finds the device ID of the device in the database through the address in step S1, the ID value is calculated by the same method and then compared, if the ID value is the same, authentication succeeds, then it is determined whether the ID value is the same as the ID of the iot device previously stored by the edge server, if the ID value is the same, a preset value is returned, the preset value is set to 2, and the address parameter of the heartbeat server is carried, if the ID value is null, the heartbeat server is the same as the address parameter of the registration server, when the edge server finds that the ID of the iot device is not present or not the same, the edge server stores a new ID and returns the preset value, the preset value is set to 3, and the address parameter of the heartbeat server is carried, and similarly, if the ID is null, the heartbeat server is the address parameter of the registration server is the same as the address parameter of the registration server, if the preset value is not matched and returned, the preset value is set to be-2, after the preset value is returned to be-2, the operation is carried out for 150 minutes in a silent mode, the operation of registering the edge server by the iot equipment is carried out again, the preset corresponding time is 10 seconds, if the edge server does not respond in the 10 seconds, the terminal applies the same server port to retry, the retry interval is 60 seconds for the first time, and the retransmission is carried out for 3 times; if no reply is received for 3 retries. The registration of the device with the edge server is resumed iot.
In another embodiment, the re-registering the edge server after the network status is stabilized in step S2 includes:
presetting an updated parameter field and reporting the updated parameter field to an edge server, and performing compatibility processing on the parameter field by the edge server;
if the edge server does not receive the parameter field, the edge server refreshes and judges that the network state is not stable;
if the edge server receives the parameter field, the edge server does not need to refresh, and judges that the network state is stable and registers the edge server again.
In this embodiment, a return information field is preset, and if the return information has the preset field, a new heartbeat interval is needed for working; iot the device should update the parameter and report to the edge server; the edge server should perform compatibility processing on it, if the edge server receives this field, the edge server should refresh the value, if not, the edge server should not refresh.
In another embodiment, the keeping alive of the heartbeat over UDP in step S3 includes:
presetting a heartbeat keep-alive time interval, wherein the heartbeat keep-alive time interval is 60 seconds, and the heartbeat keep-alive is reported every 60 seconds;
presetting a retry time interval, wherein the retry time interval is 30 seconds;
if the edge server does not receive a heartbeat keep alive report, retry is initiated, and if a reply is not received after three retry intervals, the device registers with the edge server back iot.
In this embodiment, a first heartbeat FLAG is preset, and when iot equipment is registered and a heartbeat message is sent to an edge server for the first time, the FLAG is preset to be 1; if the result in the message returned by the edge server is a preset value of 0, the iot equipment sends a heartbeat message to the edge server later, and the mark is set to be 0 for a month; when FLAG is 1, the message should carry a preset IPAddr field; when FLAG is 0, the message should not carry an IPAddr field; reported every 60 seconds: if the reply is not received within 30 seconds, the retry is started, and the retry interval is 30 seconds; the reason why the retry interval is 30 seconds is that 30 seconds is half of the retry interval, and the reason for reducing the retry interval is that an accidental packet drop may cause aging of the intermediate device; if the reply is not received after 3 times of retries, the device returns to iot to register with the edge server, when the reply is received, the positive edge server is kept, if the preset value-3 is returned, the device needs to iot to register with the edge server again, namely, the device returns to iot to register with the edge server, and if the returned information has a preset Interval, the device needs to work with a new heartbeat Interval.
The UDP in this embodiment is used to transmit heartbeat keep-alive information to confirm whether the device is alive at the heartbeat, if the server does not receive the UDP, it will identify that no data is transmitted to the iot device for further hibernation, and if the server receives the UDP, the TCP is connected to the server.
In another embodiment, the step of back triggering iot the device and connecting iot the device to the card center to obtain card center data in S4 includes:
if iot the device is processing the reverse trigger connection flow, after receiving the reverse trigger connection, it should wait to process the reverse trigger connection flow and then perform the reverse trigger connection;
if iot equipment is connected to the plug-in center, it receives reverse trigger connection, when the domain name and port number in the message are the same as those stored in iot equipment, it processes neglect, otherwise it needs to disconnect the current connection with the plug-in center actively, and register and connect new plug-in center again.
In this embodiment, when the iot device is triggered reversely, the iot device concatenates the device ID with the DevRND value sent to the edge server last time, and calculates an MD5 value, and compares with the Key in the request, the iot device should follow the following policy: iot after receiving the request, the device should first determine whether the key is the same as the previous one, if so, the edge server retransmits the message and replies the current DevRND and result code; otherwise, splicing the device ID by using the current DevRND value, calculating the MD5 value, comparing with the Key in the request, and if the values are the same, connecting the iot device with the specified plug-in center server, wherein the protocol is shown in the plug-in center protocol. And iot the device responds with a preset value of 0 and the next use of DevrRND. The edge server receives the new DevRND and returns to 1. If no results are received, the iot device should retry three times for a timeout of 5 seconds. If still failing, go back to iot where the device registers with the edge server; if not, iot device should return to preset value-1, and iot device should restart to register with the edge server; if the edge server responds-1, iot the device should resume iot the device's registration with the edge server; if the iot device is processing the reverse trigger connection flow, the iot device receives the reverse trigger connection again, the reverse trigger connection of the edge server should be the message retransmission of the edge server, and the message should be processed according to the above strategy after the reverse trigger flow is completed. If IOT equipment is connected to the plug-in center, it receives the reverse trigger connection, when the domain name and port number in the message are the same as that stored by IOT equipment, it ignores, otherwise it needs to disconnect the current connection with the plug-in center actively, and re-register and connect the new plug-in center. When the edge server receives the reverse trigger request again in the process of processing the reverse trigger connection flow, the edge server should filter out the reverse trigger request. When the message suggests that the edge server interacts with iot equipment, a retransmission mechanism is adopted, so that the edge server retransmits a reverse trigger message to iot equipment, if iot equipment receives a plurality of reverse trigger messages and keys are the same, the result messages should be sequentially returned to the edge server, and if the result messages are simultaneously returned to the same 'DevRND' edge server and a plurality of result values are received, and if the DevRND is the same, the result messages should be sequentially fed back to iot equipment, and after iot equipment receives one of the result messages, the DevRND takes effect.
In another embodiment, as shown in fig. 2, this embodiment discloses a system for increasing the access number of a single edge server iot, including: edge server unit, network element, heartbeat keep alive unit and data acquisition unit, wherein:
the edge server unit is used for presetting an edge server registration rule, identifying the edge server according to the edge server registration rule, registering the edge server for the first time if the identification is successful, and entering the network unit if the identification is failed;
the network unit is used for judging the network condition, if the network condition is stable, the edge server is registered again, and if the network condition is unstable, the edge server is registered again after the network condition is stable;
the heartbeat keep-alive unit is used for keeping heartbeat keep-alive through UDP;
a data acquisition unit for triggering iot the device in reverse and connecting iot the device to the plug-in center to acquire plug-in center data.
The above examples only express the specific embodiments of the present invention, and the description thereof is more specific and detailed, but not to be construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention.
Claims (2)
1. A method for increasing the access number of a single edge server iot, the method comprising the steps of:
s1, presetting an edge server registration rule, identifying an edge server according to the edge server registration rule, if the identification is successful, registering the edge server for the first time, and if the identification is failed, entering the step S2;
judging whether the edge server responds or returns to a preset value, if so, registering the edge server for the first time;
if the retry fails for 5 times, the terminal should randomly silence 10 to 60 retry intervals and then re-analyze the DNS of the edge server and repeat the above registration and retry processes;
if the registration and retry in the DNS period are failed to be analyzed for 3 times continuously, the IOT equipment should register to the distribution edge server again;
s2, judging the network condition, if the network condition is stable, re-registering the edge server, if the network condition is unstable, waiting for the network condition to be stable, and then re-registering the edge server;
presetting an updated parameter field and reporting the updated parameter field to an edge server, and performing compatibility processing on the parameter field by the edge server;
if the edge server does not receive the parameter field, the edge server refreshes and judges that the network state is not stable;
if the edge server receives the parameter field, the edge server does not need to be refreshed, and judges that the network state is stable and registers the edge server again;
s3, conducting heartbeat keep-alive through UDP;
presetting a heartbeat keep-alive time interval, wherein the heartbeat keep-alive time interval is 60 seconds, and the heartbeat keep-alive is reported every 60 seconds;
presetting a retry time interval, wherein the retry time interval is 30 seconds;
if the edge server does not receive the heartbeat keep-alive report, retry is started, and if the reply is not received after the time interval of three retries, the device returns to iot to register with the edge server;
s4, reversely triggering iot equipment and connecting iot equipment to the plug-in center to obtain data of the plug-in center;
if iot the device is processing the reverse trigger connection flow, after receiving the reverse trigger connection, it should wait to process the reverse trigger connection flow and then perform the reverse trigger connection;
if iot equipment is connected to the plug-in center, it receives reverse trigger connection, when the domain name and port number in the message are the same as those stored in iot equipment, it processes neglect, otherwise it needs to disconnect the current connection with the plug-in center actively, and register and connect new plug-in center again.
2. A system for increasing the access number of a single edge server iot device, the system comprising an edge server unit, a network unit, a heartbeat keep alive unit and a data acquisition unit, wherein:
the edge server unit is used for presetting an edge server registration rule, identifying the edge server according to the edge server registration rule, judging whether the edge server responds or returns to the preset value if the edge server is successfully identified, and registering the edge server for the first time if the edge server responds or returns to the preset value;
if the identification fails, 5 times of retries fail, the terminal should randomly silence for 10 to 60 retries intervals, then re-analyze the DNS of the edge server and repeat the registration and retries process, and enter a network unit;
the network unit is used for judging the network condition, and if the network condition is stable, the edge server is registered again;
if the network state is unstable, presetting an updated parameter field and reporting the updated parameter field as an edge server, and carrying out compatibility processing on the parameter field by the edge server; if the edge server does not receive the parameter field, the edge server refreshes, judges that the network state is not stable, and registers the edge server again after waiting for the network state to be stable;
the heartbeat keep-alive unit is used for carrying out heartbeat keep-alive through UDP (user Datagram protocol), presetting heartbeat keep-alive time intervals, wherein the heartbeat keep-alive time intervals are 60 seconds, and the heartbeat keep-alive is reported every 60 seconds; presetting a retry time interval, wherein the retry time interval is 30 seconds; if the edge server does not receive the heartbeat keep-alive report, retry is started, and if the reply is not received after the time interval of three retries, the device returns to iot to register with the edge server;
a data obtaining unit, configured to reversely trigger iot a device and connect iot the device to a plug-in center to obtain data of the plug-in center, if the iot device is processing a reverse trigger connection procedure, after receiving the reverse trigger connection, the data obtaining unit should wait for processing to complete the reverse trigger connection procedure and then perform the reverse trigger connection; if iot equipment is connected to the plug-in center, it receives reverse trigger connection, when the domain name and port number in the message are the same as those stored in iot equipment, it processes neglect, otherwise it needs to disconnect the current connection with the plug-in center actively, and register and connect new plug-in center again.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011281228.4A CN112437144B (en) | 2020-11-16 | 2020-11-16 | Method and system for increasing access number of single edge server iot equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011281228.4A CN112437144B (en) | 2020-11-16 | 2020-11-16 | Method and system for increasing access number of single edge server iot equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112437144A CN112437144A (en) | 2021-03-02 |
| CN112437144B true CN112437144B (en) | 2021-10-08 |
Family
ID=74700146
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011281228.4A Active CN112437144B (en) | 2020-11-16 | 2020-11-16 | Method and system for increasing access number of single edge server iot equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112437144B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109756450A (en) * | 2017-11-03 | 2019-05-14 | 华为技术有限公司 | A kind of methods, devices and systems of Internet of Things Network Communication |
| CN111629401A (en) * | 2019-02-27 | 2020-09-04 | 大唐移动通信设备有限公司 | Data distribution method and system for edge application |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102404378B (en) * | 2010-09-07 | 2014-11-05 | 成都索贝数码科技股份有限公司 | Streaming media distribution and transmission network system |
| CN101964806B (en) * | 2010-11-02 | 2013-05-22 | 深圳市共进电子股份有限公司 | Method for switching servers of SIP (Session Initiation Protocol) communication terminal |
| CN103929441A (en) * | 2014-05-09 | 2014-07-16 | 中国银行股份有限公司 | Task allocation method and device |
| CN110365803B (en) * | 2019-08-26 | 2021-11-02 | 四川艾贝斯科技发展有限公司 | Network channel maintaining method based on UDP protocol |
-
2020
- 2020-11-16 CN CN202011281228.4A patent/CN112437144B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109756450A (en) * | 2017-11-03 | 2019-05-14 | 华为技术有限公司 | A kind of methods, devices and systems of Internet of Things Network Communication |
| CN111629401A (en) * | 2019-02-27 | 2020-09-04 | 大唐移动通信设备有限公司 | Data distribution method and system for edge application |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112437144A (en) | 2021-03-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8166163B2 (en) | Server checking using health probe chaining | |
| KR100560752B1 (en) | System for managing socket connection and method for checking of socket connection state | |
| US20050259634A1 (en) | Method and apparatus for low-overhead service availability and performance monitoring | |
| CN102075508B (en) | Vulnerability disclosure system and method aiming at network protocol | |
| US20100268947A1 (en) | Systems and methods for registering a client device in a data communication system | |
| RU2008125171A (en) | METHOD FOR DELIVERY NOTIFICATION OF UPDATING THE SOFTWARE TO DEVICES IN COMMUNICATION SYSTEMS | |
| CN106330483B (en) | Information acquisition method, client device and server device | |
| CN112165447B (en) | WAF equipment-based network security monitoring method, system and electronic device | |
| CN108134713A (en) | A kind of communication means and device | |
| CN112437144B (en) | Method and system for increasing access number of single edge server iot equipment | |
| US20080181215A1 (en) | System for remotely distinguishing an operating system | |
| WO2007147031A2 (en) | Push type communications system | |
| CN117061384A (en) | Fuzzy test method, device, equipment and medium | |
| CN108769210A (en) | Method, apparatus, terminal, server and the storage medium of attendance tracking | |
| CN107819599B (en) | Message processing method and device | |
| CN113794620B (en) | Message sending method, device, equipment, system and storage medium | |
| CN109861999B (en) | Data transmission control method, device and storage medium | |
| CN109286665B (en) | Real-time mobile game long link processing method and device | |
| CN105991370B (en) | UDP channel detection method and device | |
| CN113872949B (en) | Address resolution protocol response method and related device | |
| US20040199579A1 (en) | Collaboration bus apparatus and method | |
| CN115334066A (en) | Distributed cluster system and method for processing synchronous request response | |
| CN110071901A (en) | Register method, device, system and the storage medium of internet of things equipment | |
| CN113542052A (en) | Node fault determination method and device and server | |
| CN114205248A (en) | Analog timeout response method, apparatus, device, storage medium and program product |
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 |