CN112738834A - MESH networking network emergency management method and electronic equipment - Google Patents
MESH networking network emergency management method and electronic equipment Download PDFInfo
- Publication number
- CN112738834A CN112738834A CN202110004978.5A CN202110004978A CN112738834A CN 112738834 A CN112738834 A CN 112738834A CN 202110004978 A CN202110004978 A CN 202110004978A CN 112738834 A CN112738834 A CN 112738834A
- Authority
- CN
- China
- Prior art keywords
- sub
- route
- state
- controller
- main
- 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.)
- Pending
Links
- 230000006855 networking Effects 0.000 title claims abstract description 32
- 238000007726 management method Methods 0.000 title claims abstract description 25
- 238000000034 method Methods 0.000 claims abstract description 12
- 230000002159 abnormal effect Effects 0.000 claims abstract description 5
- 238000012544 monitoring process Methods 0.000 claims description 3
- 239000000126 substance Substances 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000006872 improvement Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
Abstract
The invention discloses an emergency management method for a MESH networking network, which comprises the following steps: adding Unconconfigured state to AP service type based on Controller and Agent for identifying networking state after losing connection with Controller; and when the main route fails to detect the main route, the sub-route is changed from the Agent state to the Unconconfigured state, and after the sub-route determines that the surrounding sub-routes are all in the Unconconfigured state, the sub-route with the largest or smallest MAC address in the sub-route is determined to enter an emergency mode. By the method, the user can normally access and manage the WEB when the sub-route cannot detect the main route due to the fault of the main route in the MESH networking environment, and the manageability and the maintainability of the networking equipment in abnormal are improved. The invention also provides corresponding electronic equipment.
Description
Technical Field
The invention belongs to the technical field of wireless communication, and particularly relates to an emergency management method for a MESH networking network and electronic equipment.
Background
In the MESH networking environment, when a main route is powered down, removed or a DHCP (Dynamic Host Configuration Protocol) service fails, a user does not know a management IP (Internet Protocol) after a sub-route is changed and a terminal device connected under the sub-route cannot normally acquire the IP, and at this time, the terminal device cannot access the sub-route management WEB, the sub-route device is out of management, and user perception and experience are not good.
Disclosure of Invention
Aiming at the defects or the improvement requirements of the prior art, the invention provides an MESH networking network emergency management method and electronic equipment, wherein after the failure and the loss of connection of a main route are detected, a certain sub-route in a networking environment enters an emergency mode to temporarily start a DHCP service to distribute IP to other sub-routes.
In order to achieve the above object, according to an aspect of the present invention, there is provided a MESH networking network emergency management method, including:
adding Unconconfigured state to AP service type based on Controller and Agent for identifying networking state after losing connection with Controller; when the sub-route cannot detect the main route due to the failure of the main route, the sub-route is changed from the Agent state to the unonfigured state, and after the sub-route determines that the surrounding sub-routes are all in the unonfigured state, the sub-route with the largest or smallest MAC (Media Access Control) address in the sub-route as the network enters an emergency mode.
In one embodiment of the invention, the state of the sub-route in the emergency mode is changed from the Unconconfigured state to the Controller state, and the DHCP service is opened emergently.
In an embodiment of the present invention, after the sub-router in the emergency mode starts the DHCP service, the other sub-routers are informed that the sub-router enters the Controller state.
In one embodiment of the invention, after receiving the Controller message, the state of other sub-routes is changed from Unconconfigured state to Agent state, and then the other sub-routes are networked with the sub-routes in emergency mode.
In an embodiment of the present invention, when a terminal device obtains an address through DHCP, a sub-route connected to the terminal device sets a field indicating that the sub-route has a terminal device to be hung down in a message as a preset value after receiving a DHCP message, wherein the reported message is sent through a main sub-route networking management channel.
In an embodiment of the invention, after receiving the message, the emergency mode sub-router analyzes and identifies which sub-router has the connection terminal device, and then informs the routers to restart the physical network connection directly connected with the drop terminal device so as to obtain the address from the normal DHCP server again.
In an embodiment of the present invention, after the abnormal main route is recovered to normal, the sub-route in the emergency mode sends a notification to other sub-routes after knowing that the main route is recovered, so that the sub-route is disconnected from the sub-route in the emergency mode and then connected to the recovered main route.
In one embodiment of the invention, the sub-route in the emergency mode closes the DHCP service of the sub-route, the state of the sub-route is changed from the Controller state to the Agent state and then the sub-route is connected with the recovered main route, and finally the sub-route connected with the terminal equipment restarts the physical network connection to resend the DHCP access request.
In an embodiment of the present invention, the sub-route obtains the state of the surrounding sub-route by automatically configuring the search message through the IEEE1905 AP carrying the SupportedService TLV and the SearchedService TLV, and simultaneously monitoring the other IEEE1905 AP automatic configuration search messages in the network.
According to another aspect of the present invention, there is also provided an electronic apparatus including:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the MESH networking network emergency management method.
Generally, compared with the prior art, the technical scheme of the invention has the following beneficial effects:
by the method, the user can normally access and manage the WEB when the sub-route cannot detect the main route due to the fault of the main route in the MESH networking environment, and the manageability and the maintainability of the networking equipment in abnormal are improved.
Drawings
Fig. 1-1 is a schematic diagram illustrating AP service type definition in the prior art (Multi-AP _ Specification _ v2.0.pdf), where in Supported service TLV format, 0 in Supported service field is Controller to represent main route state, and 1 is Agent to represent sub-route state;
fig. 1-2 are schematic diagrams illustrating AP service type definition in the present invention, wherein in a supportservice TLV format, a Supported service field is added with 2 to a unonfigured value indicating a state of losing a main route;
FIG. 2 shows that the state of a child route (Agent) becomes Unconconfigured after "dropping" from the master route (Controller);
fig. 3 is a schematic diagram showing a process that after a main router (Controller) is "disconnected", a sub-router changes its state into unonfigured, then the decided state of the sub-router entering the emergency mode changes into the Controller and starts the DHCP service, and the state of other sub-routers changes into Agent, and then re-networking is performed;
FIG. 4 is a (Multi-AP _ Specification _ v2.0.pdf)1905AP-Autoconfiguration Search message format, which may carry a Supportedservice TLV and a Searcchedservice TLV;
FIG. 5 is a (Multi-AP _ Specification _ v2.0.pdf)1905AP-Autoconfiguration Response message format, which may carry a SupportedService TLV;
fig. 6 shows that the emergency mode sub-route after being re-networked notifies the sub-route with the terminal device to restart the connection through the networking management channel of the main sub-route.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. In addition, the technical features involved in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
As shown in fig. 1-1, the AP service type includes a Controller and an Agent, and specifically, in the supportservice TLV format, a Supported service field with 0 being the Controller represents a main route state and 1 being the Agent represents a sub-route state. As shown in fig. 1-2, unonfigured is added on the basis of fig. 1-1 for identifying the networking state after the Controller is "disconnected". Specifically, in the Supported service TLV format, adding 2 to the Supported service field to unonfigured indicates a state of losing the master route (of course, other values in 3 to 0xFF may be used).
As shown in fig. 3, when the master router (Controller) is "disconnected", the state of the sub-router becomes unonfigured, then the decided state of the sub-router entering the emergency mode becomes Controller and starts the DHCP service, and the state of the other sub-routers becomes Agent, and then the network is re-established. Specifically, the method comprises the following steps:
as shown in fig. 2, when the sub-route cannot detect the main route due to the failure of the main route, the sub-route Agent state (1) changes to the unonfigured state (2).
At this time, the sub-route enters the emergency mode through an IEEE1905 AP auto-configuration Search (1905 AP-auto-configuration Search, as shown in fig. 4, 1905 AP-auto-configuration Search message, which may carry a SupportedService TLV and a searchendservice message, while monitoring other IEEE1905 AP auto-configuration Search messages in the network, and after determining that the surrounding sub-routes are all in the unonfigured state, deciding that the MAC address in the sub-route is the largest or smallest in the network (for example, comparing sequentially from high to low, D4:58:00:69: FA:20> D4:58:00:69:3A:20> D4:58:00:60:3B: 20).
The state of the sub-router in the emergency mode is changed from the unonfigured state (2) to the Controller state (0), and the DHCP service is urgently started, and the other sub-routers are informed of entering the Controller state urgently through an IEEE1905 AP auto-configuration reply (1905 AP-auto-configuration reply, as shown in fig. 5, 1905 AP-auto-configuration reply message, which may carry a supportservice TLV) message carrying a SupportedService TLV.
After receiving the Controller message, the state of other sub-routes is changed from Unconconfigured state (2) to Agent state (1) and then the other sub-routes are networked with the sub-routes in emergency mode.
Further, as shown in fig. 6, when the terminal device obtains the address through the DHCP, the sub-router connected to the terminal device receives the DHCP message, and then sets a field indicating that the sub-router has the under-hung terminal device in the message (which is a private application layer management channel for transferring data through the main sub-router) to a preset value (for example, 1) to indicate that the terminal device is connected, and after receiving the message, the emergency mode sub-router analyzes and identifies which sub-router has the connected terminal device, and then notifies (through the main sub-router networking management channel) the routers to restart the physical network connection directly connected to the under-hung terminal device to obtain the address from the normal DHCP server again, so that the under-hung terminal device can normally access the managed WEB of the networking network through the domain name.
When the abnormal main route is recovered to be normal, an IEEE1905 AP automatic configuration search message carrying a SupportedService TLV and a SearcchedService TLV is sent, the sub-route in the emergency mode sends a notice to other sub-routes through a main sub-route networking management channel after knowing that the main route is recovered, so that the sub-route is disconnected from the sub-route in the emergency mode and then connected with the recovered main route, the sub-route in the emergency mode closes the DHCP service of the sub-route and the state of the sub-route is changed from a Controller state (0) to an Agent state (1) and then connected with the recovered main route, and finally the sub-route connected with the terminal equipment restarts the physical network connection to resend the DHCP access request.
It should be noted that, in the embodiment of the present invention, networking is implemented by 1905, and heartbeat and data interaction are implemented by a main sub-routing networking management channel (chinese: the main sub-routing networking management channel, which is an application layer management channel implemented privately and used for transmitting data).
Further, the present invention also provides an electronic device, comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the MESH networking network emergency management method.
It will be understood by those skilled in the art that the foregoing is only a preferred embodiment of the present invention, and is not intended to limit the invention, and that any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. An emergency management method for a MESH networking network is characterized by comprising the following steps:
adding Unconconfigured state to AP service type based on Controller and Agent for identifying networking state after losing connection with Controller; and when the main route fails to detect the main route, the sub-route is changed from the Agent state to the Unconconfigured state, and after the sub-route determines that the surrounding sub-routes are all in the Unconconfigured state, the sub-route with the largest or smallest MAC address in the sub-route is determined to enter an emergency mode.
2. The method of claim 1, wherein the sub-routing state in the emergency mode is changed from a unonfigured state to a Controller state and DHCP service is urgently opened.
3. The method of emergency management for MESH networking network of claim 2, wherein the sub-route in emergency mode informs other sub-routes that the route enters Controller state after starting DHCP service.
4. The method of claim 3, wherein other sub-routes are configured to change state from Unconfigured state to Agent state after receiving Controller message and then to be networked with sub-routes in emergency mode.
5. The method according to any of claims 1 to 4, wherein when the terminal device obtains the address through DHCP, the sub-route connected to the terminal device sets a field indicating that the sub-route has a terminal device to be hung down in the report as a preset value after receiving the DHCP message, wherein the report is sent through the main sub-route networking management channel.
6. The method of claim 5, wherein the emergency mode sub-routes, after receiving the message, resolve and identify which sub-route has the connected terminal device, and then notify the routers to restart the physical network connection directly connecting the off-hook terminal device and re-acquire the address from the normal DHCP server.
7. An emergency management method for a MESH networking network according to claim 1 or 2, wherein after the abnormal main route is recovered to normal, the sub-route in emergency mode sends a notification to other sub-routes after learning that the main route is recovered, so that the sub-route is disconnected from the sub-route in emergency mode and then connected to the recovered main route.
8. The method of claim 7, wherein the sub-route in the emergency mode closes its DHCP service and changes its state from Controller state to Agent state and connects to the restored main route, and the sub-route connected with the terminal device restarts the physical network connection to resend the DHCP access request.
9. The method of emergency management for MESH networking network of claim 1 or 2, wherein the sub-route obtains the state of the surrounding sub-route by automatically configuring the search message through IEEE1905 AP carrying Supportedservice TLV and Searcchedservice TLV, and simultaneously monitoring the other IEEE1905 AP automatically configuring search messages in the network.
10. An electronic device, comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of MESH networking network emergency management of any of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110004978.5A CN112738834A (en) | 2021-01-04 | 2021-01-04 | MESH networking network emergency management method and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110004978.5A CN112738834A (en) | 2021-01-04 | 2021-01-04 | MESH networking network emergency management method and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112738834A true CN112738834A (en) | 2021-04-30 |
Family
ID=75591171
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110004978.5A Pending CN112738834A (en) | 2021-01-04 | 2021-01-04 | MESH networking network emergency management method and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112738834A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113518134A (en) * | 2021-07-09 | 2021-10-19 | 烽火通信科技股份有限公司 | Method and device for accessing main router through domain name under MESH networking |
| CN113613274A (en) * | 2021-09-01 | 2021-11-05 | 四川九州电子科技股份有限公司 | Intelligent access configuration method based on Mesh networking |
| CN113692028A (en) * | 2021-08-25 | 2021-11-23 | 成都长虹网络科技有限责任公司 | Master-slave switching method for AP (Access Point) equipment in Mesh network |
| CN113872864A (en) * | 2021-09-26 | 2021-12-31 | 烽火通信科技股份有限公司 | Method and device for realizing sub-route web management under mesh networking mode |
| CN114465947A (en) * | 2022-02-15 | 2022-05-10 | 青岛海信宽带多媒体技术有限公司 | Router and automatic role selection method of router in Mesh networking |
| WO2022096019A1 (en) * | 2021-06-21 | 2022-05-12 | 之江实验室 | Lightweight wired mesh networking design method |
| CN114745763A (en) * | 2022-03-08 | 2022-07-12 | 深圳市欣博跃电子有限公司 | Method and system for updating optimal network topology |
| CN114945192A (en) * | 2022-07-25 | 2022-08-26 | 深圳市亿联无限科技有限公司 | EasyMesh network rapid networking method and system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060198346A1 (en) * | 2005-03-04 | 2006-09-07 | Yu-Jih Liu | Method and apparatus for dynamic neighbor discovery within wireless networks using time division multiple access (TDMA) |
| CN101217402A (en) * | 2008-01-15 | 2008-07-09 | 杭州华三通信技术有限公司 | A method to enhance the reliability of the cluster and a high reliability communication node |
| CN103129750A (en) * | 2013-01-25 | 2013-06-05 | 航天东方红卫星有限公司 | Separated module spacecraft system based on state perception and self-networking method |
| EP2884777A1 (en) * | 2013-12-10 | 2015-06-17 | Life Safety Distribution AG | Wireless fire system with idle mode and gateway redundancy |
| CN109005045A (en) * | 2017-06-06 | 2018-12-14 | 北京金山云网络技术有限公司 | Active and standby service system and host node fault recovery method |
| CN111431774A (en) * | 2020-03-10 | 2020-07-17 | 华为技术有限公司 | Communication method and communication system based on master router and slave router networking |
| CN111970725A (en) * | 2020-08-21 | 2020-11-20 | 广东博智林机器人有限公司 | Network fault self-recovery method and system |
-
2021
- 2021-01-04 CN CN202110004978.5A patent/CN112738834A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060198346A1 (en) * | 2005-03-04 | 2006-09-07 | Yu-Jih Liu | Method and apparatus for dynamic neighbor discovery within wireless networks using time division multiple access (TDMA) |
| CN101217402A (en) * | 2008-01-15 | 2008-07-09 | 杭州华三通信技术有限公司 | A method to enhance the reliability of the cluster and a high reliability communication node |
| CN103129750A (en) * | 2013-01-25 | 2013-06-05 | 航天东方红卫星有限公司 | Separated module spacecraft system based on state perception and self-networking method |
| EP2884777A1 (en) * | 2013-12-10 | 2015-06-17 | Life Safety Distribution AG | Wireless fire system with idle mode and gateway redundancy |
| CN109005045A (en) * | 2017-06-06 | 2018-12-14 | 北京金山云网络技术有限公司 | Active and standby service system and host node fault recovery method |
| CN111431774A (en) * | 2020-03-10 | 2020-07-17 | 华为技术有限公司 | Communication method and communication system based on master router and slave router networking |
| CN111970725A (en) * | 2020-08-21 | 2020-11-20 | 广东博智林机器人有限公司 | Network fault self-recovery method and system |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022096019A1 (en) * | 2021-06-21 | 2022-05-12 | 之江实验室 | Lightweight wired mesh networking design method |
| CN113518134B (en) * | 2021-07-09 | 2022-06-17 | 烽火通信科技股份有限公司 | Method and device for accessing main router through domain name under MESH networking |
| CN113518134A (en) * | 2021-07-09 | 2021-10-19 | 烽火通信科技股份有限公司 | Method and device for accessing main router through domain name under MESH networking |
| CN113692028A (en) * | 2021-08-25 | 2021-11-23 | 成都长虹网络科技有限责任公司 | Master-slave switching method for AP (Access Point) equipment in Mesh network |
| CN113613274A (en) * | 2021-09-01 | 2021-11-05 | 四川九州电子科技股份有限公司 | Intelligent access configuration method based on Mesh networking |
| CN113613274B (en) * | 2021-09-01 | 2023-08-18 | 四川九州电子科技股份有限公司 | Intelligent access configuration method based on Mesh networking |
| CN113872864A (en) * | 2021-09-26 | 2021-12-31 | 烽火通信科技股份有限公司 | Method and device for realizing sub-route web management under mesh networking mode |
| CN113872864B (en) * | 2021-09-26 | 2023-02-03 | 烽火通信科技股份有限公司 | Method and device for realizing sub-route web management under mesh networking mode |
| CN114465947A (en) * | 2022-02-15 | 2022-05-10 | 青岛海信宽带多媒体技术有限公司 | Router and automatic role selection method of router in Mesh networking |
| CN114465947B (en) * | 2022-02-15 | 2024-02-27 | 青岛海信宽带多媒体技术有限公司 | Router and automatic role selection method for router in Mesh networking |
| CN114745763A (en) * | 2022-03-08 | 2022-07-12 | 深圳市欣博跃电子有限公司 | Method and system for updating optimal network topology |
| CN114745763B (en) * | 2022-03-08 | 2023-08-22 | 深圳市欣博跃电子有限公司 | Method and system for updating optimal network topology |
| CN114945192A (en) * | 2022-07-25 | 2022-08-26 | 深圳市亿联无限科技有限公司 | EasyMesh network rapid networking method and system |
| CN114945192B (en) * | 2022-07-25 | 2023-11-10 | 深圳市亿联无限科技有限公司 | Easymesh network rapid networking method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112738834A (en) | MESH networking network emergency management method and electronic equipment | |
| US7380025B1 (en) | Method and apparatus providing role-based configuration of a port of a network element | |
| JP5093598B2 (en) | Control relay program, control relay device, and control relay method | |
| US8432833B2 (en) | Auto MEP ID assignment within CFM maintenance association | |
| CN108259215B (en) | Equipment management method and device | |
| US10917289B2 (en) | Handling network failures in networks with redundant servers | |
| WO2021135419A1 (en) | Method and apparatus for updating routing information, computer device, and storage medium | |
| CN110351141B (en) | Flexe interface management method, device and network element | |
| JP2006086718A (en) | Access router and terminal equipment | |
| US20120269092A1 (en) | Auto-configuration of network devices | |
| US20210377125A1 (en) | Network Topology Discovery Method, Device, and System | |
| JP2011044955A (en) | Setting change method by network manager equipment and program, control method and program of network equipment, network manager equipment, and network equipment | |
| JP2006033613A (en) | Network apparatus | |
| CN111918306B (en) | Method and system for realizing network element communication under IP unreachable scene | |
| CN107786441B (en) | Communication method, OpenFlow switch and communication system | |
| CN107528788B (en) | Method and device for realizing automatic stacking between network devices | |
| CN102064956A (en) | Method for regulating aging time, system and modulator-demodulator | |
| CN107995644B (en) | Method, switch, system and storage medium for automatic recovery of wireless access point | |
| CN115514719B (en) | Message sending method, device, switch and readable storage medium | |
| CN109286575B (en) | Message priority configuration method, device and network equipment | |
| WO2016065925A1 (en) | Controller replacing method and device | |
| CN115174528A (en) | Equipment address control method, device and system | |
| CN113824595B (en) | Link switching control method and device and gateway equipment | |
| CN111225080B (en) | Method for acquiring gateway down-hanging equipment information | |
| CN113194115A (en) | Method for automatically deploying client, network equipment and storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210430 |