CN108833135B - Mesh networking management method, management equipment and extender - Google Patents

Mesh networking management method, management equipment and extender Download PDF

Info

Publication number
CN108833135B
CN108833135B CN201810421348.6A CN201810421348A CN108833135B CN 108833135 B CN108833135 B CN 108833135B CN 201810421348 A CN201810421348 A CN 201810421348A CN 108833135 B CN108833135 B CN 108833135B
Authority
CN
China
Prior art keywords
extender
data packet
soap
packet
address
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
Application number
CN201810421348.6A
Other languages
Chinese (zh)
Other versions
CN108833135A (en
Inventor
刘乘驰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Gongjin Electronics Co Ltd
Original Assignee
Shenzhen Gongjin Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Gongjin Electronics Co Ltd filed Critical Shenzhen Gongjin Electronics Co Ltd
Priority to CN201810421348.6A priority Critical patent/CN108833135B/en
Publication of CN108833135A publication Critical patent/CN108833135A/en
Application granted granted Critical
Publication of CN108833135B publication Critical patent/CN108833135B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • 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/22—Parsing or analysis of headers
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses a Mesh networking management method, which comprises the following steps: receiving a Simple Object Access Protocol (SOAP) data packet sent by a user terminal; analyzing the SOAP data packet, and determining a target extender according to the message header of the SOAP data packet; acquiring a message body of the SOAP data packet; encapsulating the message body of the SOAP data packet into a hypertext transfer protocol (HTTP) packet according to the target extender; sending the HTTP packet to the target extender; the receiving the target extender is based on receiving a response to the HTTP packet. In addition, the invention also discloses a management device and an extender. In this way, the Mesh networking management method provided by the invention can determine the target extender according to the message header of the SOAP data packet, send the HTTP packet comprising the message body of the SOAP data packet to the target extender, and receive the response of the target extender based on the received HTTP packet, thereby being convenient for the management equipment to manage the extender.

Description

Mesh networking management method, management equipment and extender
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a Mesh networking management method, a management device, and an extender.
Background
With the continuous development of electronic technology, mobile terminals (such as smartphones, tablet computers, etc.) have more and more powerful functions, and play an increasingly important role in the work and life of people. Meanwhile, people have stronger dependence on networks, particularly wireless networks, and nowadays, the wireless networks almost extend over any range of activities of people, such as offices, families, hotels and the like, so that users can connect the wireless networks anytime and anywhere and experience convenience and happiness brought by mobile life.
In the prior art, a Mesh (wireless Mesh network or multi-hop network) networking mode of a plurality of devices is widely applied to wireless networks requiring large-scale coverage by a flexible network structure, however, in the prior art, a management device in Mesh networking can only send messages to all other devices in Mesh networking, and cannot acquire responses of other devices in Mesh networking to the messages, so that other devices in Mesh networking cannot be effectively managed, and the stability of Mesh networking is lower. In addition, when only a message needs to be sent to a part of devices, the management device in the Mesh networking can also send the message to all the devices, so that the waste of communication resources is caused.
In the prior art, the management device in the Mesh networking has low management efficiency on other devices in the networking, and is easy to cause waste of communication resources.
Disclosure of Invention
In view of the above, the present invention provides a Mesh networking management method, a management device and an extender to solve the above technical problems.
Firstly, in order to achieve the above objective, the present invention proposes a Mesh networking management method, applied to a management device, the method comprising:
receiving a Simple Object Access Protocol (SOAP) data packet sent by a user terminal;
analyzing the SOAP data packet, and determining a target extender according to the message header of the SOAP data packet;
acquiring a message body of the SOAP data packet;
encapsulating the message body of the SOAP data packet into a hypertext transfer protocol (HTTP) packet according to the target extender;
sending the HTTP packet to the target extender;
the receiving the target extender is based on receiving a response to the HTTP packet.
Optionally, the parsing the SOAP data packet, determining a target extender according to a header of the SOAP data packet, includes:
analyzing the SOAP data packet and judging whether the SOAP data packet comprises a message header or not;
if the SOAP data packet comprises a message header, determining a target extender according to the message header of the SOAP data packet.
Optionally, the determining the target extender according to the header of the SOAP data packet includes:
acquiring the number information of destination addresses in a message header of the SOAP data packet;
judging whether the destination address quantity information is a preset value or not;
if the number information of the destination addresses is a preset value, determining that all the extenders in the Mesh networking are target extenders;
if the destination address quantity information is not a preset value, determining that an extender corresponding to the destination address information in the message header of the SOAP data packet is a target extender.
Optionally, the determining the target extender according to the header of the SOAP data packet includes:
determining the IP address of the target extender according to the message header of the SOAP data packet;
the encapsulating, according to the target extender, the message body of the SOAP data packet into a hypertext transfer protocol HTTP packet, including:
and packaging the IP address of the target extender and the message body of the SOAP data packet into a hypertext transfer protocol (HTTP) packet.
Optionally, the determining the IP address of the target extender according to the header of the SOAP data packet includes:
acquiring a Media Access Control (MAC) address of a target extender carried in a message header of a SOAP data packet;
and acquiring the IP address corresponding to the MAC address from a corresponding relation table according to the MAC address of the target extender, wherein the corresponding relation table stores the corresponding relation between the MAC addresses and the IP addresses of a plurality of extenders.
Optionally, before the receiving the simple object access protocol SOAP data packet sent by the user terminal, the method further includes:
sending an information acquisition request to all the extenders in the Mesh networking;
receiving the MAC address and the IP address of the extender sent by the extender based on the information acquisition request;
and establishing or updating the corresponding relation table according to the received MAC address and IP address of each extender.
Optionally, the sending an information acquisition request to all the extenders in the Mesh networking includes:
and sending an information acquisition request to all devices in the Mesh networking in a broadcasting mode.
Optionally, the method further comprises:
if the information acquisition requests are continuously sent to all the extenders in the Mesh networking for preset times, the MAC address and the IP address sent by the first extender are not received, and the corresponding relation between the MAC address and the IP address of the first extender is deleted from the corresponding relation table.
Optionally, after receiving the response of the target extender based on receiving the HTTP packet, the method further includes:
judging whether all target extenders receive responses based on the HTTP packets;
and if all the target extenders are received, sending a notification message to the user terminal based on the response of receiving the HTTP packet.
Further, to achieve the above object, the present invention further provides a Mesh networking management method, applied to an extender, the method comprising:
receiving an HTTP packet sent by management equipment;
and sending a response of the HTTP packet to the management equipment based on the HTTP packet.
Optionally, the method further comprises:
receiving an information acquisition request sent by the management equipment;
and sending the MAC address and the IP address of the extender to the management equipment in response to the information acquisition request.
Further, to achieve the above object, the present invention also provides a management apparatus including a memory, at least one processor, and at least one program stored on the memory and executable by the at least one processor, the at least one program implementing the steps performed by the management apparatus in the method of any one of the above claims when executed by the at least one processor.
Further, to achieve the above object, the present invention also provides an extender, the extender including a memory, at least one processor, and at least one program stored on the memory and executable by the at least one processor, the at least one program when executed by the at least one processor implementing the steps performed by the extender in the method of any one of the above.
Compared with the prior art, the Mesh group management method provided by the invention receives the Simple Object Access Protocol (SOAP) data packet sent by the user terminal; analyzing the SOAP data packet, and determining a target extender according to the message header of the SOAP data packet; acquiring a message body of the SOAP data packet; encapsulating the message body of the SOAP data packet into a hypertext transfer protocol (HTTP) packet according to the target extender; sending the HTTP packet to the target extender; the receiving the target extender is based on receiving a response to the HTTP packet. The Mesh networking management method provided by the invention can determine the target extender according to the message header of the SOAP data packet, send the HTTP packet comprising the SOAP data packet body to the target extender, and receive the response of the target extender based on the received HTTP packet, thereby being convenient for the management equipment to manage the extender.
Drawings
Fig. 1 is a schematic diagram of Mesh networking according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a management device according to an embodiment of the present invention;
FIG. 3 is a schematic view of an extender according to an embodiment of the present invention;
fig. 4 is a schematic flow chart of a Mesh group management method according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a protocol according to an embodiment of the present invention;
fig. 6 is a flow chart of another Mesh group management method according to an embodiment of the present invention;
fig. 7 is a schematic flow chart of another Mesh group management method according to an embodiment of the present invention;
the achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
In the following description, suffixes such as "module", "component", or "unit" for representing elements are used only for facilitating the description of the present invention, and have no specific meaning per se. Thus, "module," "component," or "unit" may be used in combination.
The terminal may be implemented in various forms. For example, the terminals described in the present invention may include mobile terminals such as cell phones, tablet computers, notebook computers, palm computers, personal digital assistants (Personal Digital Assistant, PDA), portable media players (Portable Media Player, PMP), navigation devices, wearable devices, smart bracelets, pedometers, and fixed terminals such as digital TVs, desktop computers, and the like.
The following description will be given taking a mobile terminal as an example, and those skilled in the art will understand that the configuration according to the embodiment of the present invention can be applied to a fixed type terminal in addition to elements particularly used for a moving purpose.
Referring to fig. 1, fig. 1 is a schematic diagram of a Mesh networking provided in an embodiment of the present invention, and as shown in fig. 1, a Mesh networking 100 includes a management device 101 and a plurality of extenders 102, where the management device 101 and the plurality of extenders 102 are connected wirelessly with each other. It will be appreciated that in the embodiment of the present invention, the management device 101 and the extender 102 may be devices with the same hardware structure, but devices that implement different functions when executed.
Referring to fig. 2, fig. 2 is a schematic hardware structure of a management device according to an embodiment of the present invention, as shown in fig. 2, the management device 200 includes: a processor 201, a memory 202, a user interface 203, a transceiver 204 and a bus interface 205, said processor 201 being arranged to read a program in the memory 202. In fig. 2, bus interface 205 may include any number of interconnected buses and bridges, with one or more processors, represented in particular by processor 201, and various circuits of memory, represented by memory 202, coupled together. The bus architecture may also connect together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further herein. Bus interface provides an interface, and transceiver 204 may be a number of elements, including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 203 may also be an interface capable of interfacing with an inscribed desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc. The processor 201 is responsible for managing the bus architecture and general processing, and the memory 202 may store data used by the processor 201 in performing operations.
Referring to fig. 3, fig. 3 is a schematic hardware structure of an extender according to an embodiment of the present invention, and as shown in fig. 3, the extender 300 includes: a processor 301, a memory 302, a user interface 303, a transceiver 304 and a bus interface 305, said processor 301 being arranged to read a program in the memory 302. In fig. 3, bus interface 305 may include any number of interconnected buses and bridges, with one or more processors, represented by processor 301, and various circuits of memory, represented by memory 302, coupled together. The bus architecture may also connect together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further herein. Bus interface provides an interface, and transceiver 304 may be a number of elements, including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 303 may also be an interface capable of interfacing with an inscribed desired device for a different user device, including but not limited to a keypad, display, speaker, microphone, joystick, etc. The processor 301 is responsible for managing the bus architecture and general processing, and the memory 302 may store data used by the processor 301 in performing operations.
Based on the Mesh networking schematic diagram, the management device and the extender structure schematic diagram, various embodiments of the method are provided.
Referring to fig. 4, fig. 4 is a step flowchart of a Mesh networking management method provided by an embodiment of the present invention, where the method is applied to a mobile terminal, as shown in fig. 4, and the method includes:
step 401, receiving a simple object access protocol SOAP data packet sent by a user terminal.
In this step, the method receives a SOAP (Simple Object Access Protocol ) packet sent by the user terminal. Specifically, when a user performs an operation on a WEB GUI (World Wide Web Graphical User Interface, global wide area network graphical user interface) of a user terminal, the WEB GUI of the user terminal generates a SOAP data packet in response to the user operation, and transmits the SOAP data packet to a management device in Mesh networking. The management device receives the SOAP data packet sent by the user terminal, specifically, may be a WEB CGI (World Wide Web Common Gateway Interface, global wide area network universal gateway interface) of the management device receives the SOAP data packet sent by the user terminal.
In the embodiment of the present invention, the format of the SOAP data packet may be the following format:
Figure BDA0001650782780000071
the method comprises the steps that in a leader node, a specific request and a destination to which data in a Body are required to be sent are stored in the current leader;
the Header/SetDest/count tag currently needs to forward this information to several extenders (extensions);
the leader/SetDest/Dest/Target marks the MAC (Media Access Control ) address of the extender that currently needs to be forwarded.
Step 402, analyzing the SOAP data packet, and determining a target extender according to the message header of the SOAP data packet.
In this step, the method parses the SOAP data packet and determines a target extender based on a header of the SOAP data packet.
In some embodiments of the present invention, the method may parse the SOAP data packet, determine whether the SOAP data packet includes a Header (i.e., the SOAP: header node described above), and if the SOAP data packet includes a Header, determine a target extender according to the Header of the data packet; conversely, if the SOAP packet does not include a header, the data indicating the body of the SOAP packet may be processed by only the device that receives the packet, and the method may not perform any processing.
The method for determining the target extender according to the message Header of the SOAP data packet specifically comprises the steps of obtaining the destination address quantity information (namely, the SOAP: header/SetDest/count node) in the message Header of the SOAP data packet, then judging whether the destination address quantity information is a preset value, and if the destination address quantity information is the preset value, determining all the extenders in the Mesh networking as the target extender; if the destination address number information is not the preset value, the method determines that an extender corresponding to the destination address information (i.e. the above-mentioned SOAP: header/SetDest/Dest/Target node) in the Header of the SOAP data packet is a Target extender. In some embodiments of the present invention, the preset value may be 0, specifically, when the destination address number information is 0, the method determines that all the extenders in the Mesh networking are target extenders; when the destination address number information is not 0, the method determines that the destination address number information is the number of the target extender.
Step 403, obtaining a message body of the SOAP data packet.
In this step, the method obtains a message body of the SOAP data packet.
In the management device, it may be that the WEB CGI of the management device determines whether the destination address number information is a preset value, and if the destination address number information is a preset value, the WEB CGI sends the message body of the SOAP to the HNAPAgent module of the management device through ubus (socket, a message sending module of an operating system is a communication mode between processes), where the ubus carries the MAC address of the target extender.
Step 404, encapsulating the message body of the SOAP data packet into a hypertext transfer protocol HTTP packet according to the target extender.
In this step, the method encapsulates the message body of the SOAP data packet into HTTP (Hyper Text Transfer Protocol ) packets according to the target extender. Specifically, the method may obtain the IP address of the target extender, and encapsulate the IP (Internet Protocol, protocol of interconnection between networks) address of the target extender and the packet body of the SOAP packet into an HTTP packet, for example, encapsulate the IP address in a header of the HTTP packet.
In this embodiment, the method may obtain, from a correspondence table, an IP address corresponding to the MAC address as the IP address of the target extender according to the MAC address of the target extender carried in the header of the SOAP packet, where the correspondence table stores correspondence between MAC addresses and IP addresses of a plurality of extenders. The method may further comprise: sending an information acquisition request to all the extenders in the Mesh networking; receiving the MAC address and the IP address of the extender sent by the extender based on the information acquisition request; and establishing or updating the corresponding relation table according to the received MAC address and IP address of each extender. If the information acquisition requests are continuously sent to all the extenders in the Mesh networking for preset times, the MAC address and the IP address sent by the first extender are not received, and the corresponding relation between the MAC address and the IP address of the first extender is deleted from the corresponding relation table.
In this embodiment, the management device may customize a two-layer protocol, for example, 0x1EE3, and send an information acquisition request to all devices in the Mesh network through a two-layer broadcast frame. The format of the 0x1EE3 two-layer protocol may be the format shown in fig. 5, and as shown in fig. 5, the protocol includes:
source MAC address (src MAC): 6 bytes;
destination MAC address (dst MAC): 6 bytes;
protocol number (Type): 2 bytes, in this embodiment, protocol number 0x1EE3;
message Type (Agent Type): 4 bytes, which is used to indicate that the message is a query message or a response message, in this embodiment, "0" may be used to indicate the query message, and "1" may be used to indicate the response message;
message sender type (Agent mode): 4 bytes for indicating the type of the message sender, for example, a "0" may be used to indicate that the message sender is a management device, and a "1" indicates that the message sender is an extender;
message node type (Option): 2 bytes for indicating the message node type, for example, a "0" may be used to indicate that the message is of the MAC address type, and a "1" may be used to indicate that the message is of the IP address type;
message node variable length (Option len): 4 bytes for indicating the length of the message node value;
the message node Value (Option Value), the number of bytes, may be extended to carry the Value of a particular message node, such as a MAC address or IP address.
Step 405, sending the HTTP packet to the target extender.
In this step, the management apparatus transmits the HTTP packet to the target extender.
Step 406, receiving a response from the target extender based on receiving the HTTP packet.
In this step, the method receives a response from the target extender based on receiving the HTTP packet. Specifically, in the embodiment of the present invention, after receiving the HTTP packet, the target extender sends a response of the HTTP packet to the management device based on the received HTTP packet.
For example, when an application needs online upgrade, a user may execute online upgrade triggering operation on a WEB GUI of a user terminal, where the WEB GUI of the user terminal responds to the online upgrade triggering operation and sends a SOAP data packet indicated by a start program download (startfirmware download) to a WEB CGI of the management device, after the WEB CGI of the management device receives the SOAP data packet, parse the SOAP data packet to determine a target extender, and send the "start program download" indication to a HNAPAgent module of the management device through ubus, where the HNAPAgent module of the management device encapsulates a corresponding HTTP packet and sends the HTTP packet to the target extender, and at the same time, the target extender starts downloading a corresponding mirror image, and after receiving the HTTP packet, sends a corresponding response to the management device, the target extender further parses the message body of the HTTP packet and starts downloading the corresponding mirror image.
Furthermore, the method can also acquire the downloading progress of each device in the Mesh network in the same way, for example, by sending a SOAP data packet carrying "poll firmware download" in a message body. The transmission process is the same as the transmission process of starting the program download, and will not be described here again. The management equipment receives the downloading progress sent by the extender; the management device may determine the downloading progress of the entire Mesh networking device according to the downloading progress sent by the extender, for example, may determine the minimum downloading progress as the downloading progress of the entire Mesh networking device, or may determine the average downloading progress as the downloading progress of the entire Mesh networking device. And the management equipment sends the determined downloading progress to the user terminal, so that the user can conveniently dismiss the downloading progress. It can be understood that when all devices have been downloaded, the upgrade can be started uniformly.
In this embodiment, the Mesh group management method receives a simple object access protocol SOAP data packet sent by a user terminal; analyzing the SOAP data packet, and determining a target extender according to the message header of the SOAP data packet; acquiring a message body of the SOAP data packet; encapsulating the message body of the SOAP data packet into a hypertext transfer protocol (HTTP) packet according to the target extender; sending the HTTP packet to the target extender; the receiving the target extender is based on receiving a response to the HTTP packet. The Mesh networking management method provided by the invention can determine the target extender according to the message header of the SOAP data packet, send the HTTP packet comprising the SOAP data packet body to the target extender, and receive the response of the target extender based on the received HTTP packet, thereby being convenient for the management equipment to manage the extender.
Optionally, the parsing the SOAP data packet, determining a target extender according to a header of the SOAP data packet, includes:
analyzing the SOAP data packet and judging whether the SOAP data packet comprises a message header or not;
if the SOAP data packet comprises a message header, determining a target extender according to the message header of the SOAP data packet.
Optionally, the determining the target extender according to the header of the SOAP data packet includes:
acquiring the number information of destination addresses in a message header of the SOAP data packet;
judging whether the destination address quantity information is a preset value or not;
if the number information of the destination addresses is a preset value, determining that all the extenders in the Mesh networking are target extenders;
if the destination address quantity information is not a preset value, determining that an extender corresponding to the destination address information in the message header of the SOAP data packet is a target extender.
Optionally, after receiving the response of the target extender based on receiving the HTTP packet, the method further includes:
judging whether all target extenders receive responses based on the HTTP packets;
and if all the target extenders are received, sending a notification message to the user terminal based on the response of receiving the HTTP packet.
In this embodiment, after receiving the response of the target extender based on receiving the HTTP packet, the method further determines whether all the target extender responses based on receiving the HTTP packet are received; and if all the target extenders are received, sending a notification message to the user terminal based on the response of receiving the HTTP packet.
Referring to fig. 6, fig. 6 is a flow chart of another Mesh networking management method provided by the embodiment of the present invention, as shown in fig. 6, where the method includes:
step 601, receiving a simple object access protocol SOAP data packet sent by a user terminal.
This step 601 is the same as step 401 in the embodiment of the present invention shown in fig. 4, and will not be described here again.
Step 602, analyzing the SOAP data packet, and determining the IP address of the target extender according to the message header of the SOAP data packet.
In this step, the method parses the SOAP data packet, and determines the IP address of the target extender according to the header of the SOAP data packet. Specifically, the method can obtain the Media Access Control (MAC) address of the target extender carried in the message header of the SOAP data packet; and then, acquiring the IP address corresponding to the MAC address from a corresponding relation table according to the MAC address of the target extender, wherein the corresponding relation table stores the corresponding relation between the MAC addresses and the IP addresses of a plurality of extenders.
Step 603, obtaining a message body of the SOAP data packet.
This step 603 is the same as step 403 in the embodiment of the present invention shown in fig. 4, and will not be described here again.
Step 604, encapsulating the IP address of the target extender and the message body of the SOAP packet into a HTTP packet.
In this step, the method encapsulates the IP address of the target extender and the message body of the SOAP packet into a hypertext transfer protocol HTTP packet.
Step 605, sending the HTTP packet to the target extender.
Step 606, receiving the response of the target extender based on receiving the HTTP packet.
The steps 605 and 606 are the same as the steps 405 and 406 in the embodiment of fig. 4, and are not repeated here.
Optionally, the determining the IP address of the target extender according to the header of the SOAP data packet includes:
acquiring a Media Access Control (MAC) address of a target extender carried in a message header of a SOAP data packet;
and acquiring the IP address corresponding to the MAC address from a corresponding relation table according to the MAC address of the target extender, wherein the corresponding relation table stores the corresponding relation between the MAC addresses and the IP addresses of a plurality of extenders.
Optionally, before the receiving the simple object access protocol SOAP data packet sent by the user terminal, the method further includes:
sending an information acquisition request to all the extenders in the Mesh networking;
receiving the MAC address and the IP address of the extender sent by the extender based on the information acquisition request;
and establishing or updating the corresponding relation table according to the received MAC address and IP address of each extender.
Optionally, the sending an information acquisition request to all the extenders in the Mesh networking includes:
and sending an information acquisition request to all devices in the Mesh networking in a broadcasting mode.
Optionally, the method further comprises:
if the information acquisition requests are continuously sent to all the extenders in the Mesh networking for preset times, the MAC address and the IP address sent by the first extender are not received, and the corresponding relation between the MAC address and the IP address of the first extender is deleted from the corresponding relation table.
Referring to fig. 7, fig. 7 is a flowchart of another Mesh networking management method provided by an embodiment of the present invention, where the method is applied to an extender, as shown in fig. 7, and the method includes:
step 701, receiving an HTTP packet sent by a management device.
Step 702, based on the HTTP packet, sending a response of the HTTP packet to the management device.
The embodiment is an embodiment corresponding to the extender side in the Mesh networking management method shown in fig. 4 and fig. 6, which can implement the same function as in the Mesh networking management method shown in fig. 4 and fig. 6, and will not be described here again.
Optionally, the method further comprises:
receiving an information acquisition request sent by the management equipment;
and sending the MAC address and the IP address of the extender to the management equipment in response to the information acquisition request.
Those of ordinary skill in the art will appreciate that all or part of the steps of implementing the method of the above embodiments may be implemented by at least one program instruction related hardware, where the at least one program may be stored in the memory 202 of the mobile terminal as shown in fig. 2 and executed by the processor 201, where the at least one program when executed by the processor 201 implements the steps of:
receiving a Simple Object Access Protocol (SOAP) data packet sent by a user terminal;
analyzing the SOAP data packet, and determining a target extender according to the message header of the SOAP data packet;
acquiring a message body of the SOAP data packet;
encapsulating the message body of the SOAP data packet into a hypertext transfer protocol (HTTP) packet according to the target extender;
sending the HTTP packet to the target extender;
the receiving the target extender is based on receiving a response to the HTTP packet.
Optionally, the parsing the SOAP data packet, determining a target extender according to a header of the SOAP data packet, includes:
analyzing the SOAP data packet and judging whether the SOAP data packet comprises a message header or not;
if the SOAP data packet comprises a message header, determining a target extender according to the message header of the SOAP data packet.
Optionally, the determining the target extender according to the header of the SOAP data packet includes:
acquiring the number information of destination addresses in a message header of the SOAP data packet;
judging whether the destination address quantity information is a preset value or not;
if the number information of the destination addresses is a preset value, determining that all the extenders in the Mesh networking are target extenders;
if the destination address quantity information is not a preset value, determining that an extender corresponding to the destination address information in the message header of the SOAP data packet is a target extender.
Optionally, the determining the target extender according to the header of the SOAP data packet includes:
determining the IP address of the target extender according to the message header of the SOAP data packet;
the encapsulating, according to the target extender, the message body of the SOAP data packet into a hypertext transfer protocol HTTP packet, including:
and packaging the IP address of the target extender and the message body of the SOAP data packet into a hypertext transfer protocol (HTTP) packet.
Optionally, the determining the IP address of the target extender according to the header of the SOAP data packet includes:
acquiring a Media Access Control (MAC) address of a target extender carried in a message header of a SOAP data packet;
and acquiring the IP address corresponding to the MAC address from a corresponding relation table according to the MAC address of the target extender, wherein the corresponding relation table stores the corresponding relation between the MAC addresses and the IP addresses of a plurality of extenders.
Optionally, before the processor 201 executes the simple object access protocol SOAP packet sent by the receiving user terminal, the following steps may be implemented:
sending an information acquisition request to all the extenders in the Mesh networking;
receiving the MAC address and the IP address of the extender sent by the extender based on the information acquisition request;
and establishing or updating the corresponding relation table according to the received MAC address and IP address of each extender.
Optionally, the sending an information acquisition request to all the extenders in the Mesh networking includes:
and sending an information acquisition request to all devices in the Mesh networking in a broadcasting mode.
Optionally, the processor 201 may further implement the following steps when executing:
if the information acquisition requests are continuously sent to all the extenders in the Mesh networking for preset times, the MAC address and the IP address sent by the first extender are not received, and the corresponding relation between the MAC address and the IP address of the first extender is deleted from the corresponding relation table.
Optionally, after the processor 201 executes the response of receiving the HTTP packet from the target extender, the following steps may be further implemented:
judging whether all target extenders receive responses based on the HTTP packets;
and if all the target extenders are received, sending a notification message to the user terminal based on the response of receiving the HTTP packet.
Those of ordinary skill in the art will appreciate that all or part of the steps of implementing the method of the above embodiments may be implemented by at least one program instruction related hardware, where the at least one program may be stored in the memory 302 of the mobile terminal as shown in fig. 3 and be executed by the processor 301, where the at least one program when executed by the processor 301 implements the steps of:
receiving an HTTP packet sent by management equipment;
and sending a response of the HTTP packet to the management equipment based on the HTTP packet.
Optionally, the processor 301 may further implement the following steps when executing:
receiving an information acquisition request sent by the management equipment;
and sending the MAC address and the IP address of the extender to the management equipment in response to the information acquisition request.
Those of ordinary skill in the art will appreciate that all or a portion of the steps implementing the methods of the above embodiments may be implemented by at least one program instruction-dependent hardware, and the at least one program may be stored on a computer-readable storage medium, the at least one program when executed comprising the steps of:
receiving a Simple Object Access Protocol (SOAP) data packet sent by a user terminal;
analyzing the SOAP data packet, and determining a target extender according to the message header of the SOAP data packet;
acquiring a message body of the SOAP data packet;
encapsulating the message body of the SOAP data packet into a hypertext transfer protocol (HTTP) packet according to the target extender;
sending the HTTP packet to the target extender;
the receiving the target extender is based on receiving a response to the HTTP packet.
Optionally, the parsing the SOAP data packet, determining a target extender according to a header of the SOAP data packet, includes:
analyzing the SOAP data packet and judging whether the SOAP data packet comprises a message header or not;
if the SOAP data packet comprises a message header, determining a target extender according to the message header of the SOAP data packet.
Optionally, the determining the target extender according to the header of the SOAP data packet includes:
acquiring the number information of destination addresses in a message header of the SOAP data packet;
judging whether the destination address quantity information is a preset value or not;
if the number information of the destination addresses is a preset value, determining that all the extenders in the Mesh networking are target extenders;
if the destination address quantity information is not a preset value, determining that an extender corresponding to the destination address information in the message header of the SOAP data packet is a target extender.
Optionally, the determining the target extender according to the header of the SOAP data packet includes:
determining the IP address of the target extender according to the message header of the SOAP data packet;
the encapsulating, according to the target extender, the message body of the SOAP data packet into a hypertext transfer protocol HTTP packet, including:
and packaging the IP address of the target extender and the message body of the SOAP data packet into a hypertext transfer protocol (HTTP) packet.
Optionally, the determining the IP address of the target extender according to the header of the SOAP data packet includes:
acquiring a Media Access Control (MAC) address of a target extender carried in a message header of a SOAP data packet;
and acquiring the IP address corresponding to the MAC address from a corresponding relation table according to the MAC address of the target extender, wherein the corresponding relation table stores the corresponding relation between the MAC addresses and the IP addresses of a plurality of extenders.
Optionally, before implementing receiving the simple object access protocol SOAP data packet sent by the user terminal when the at least one program is executed, the following steps may be implemented:
sending an information acquisition request to all the extenders in the Mesh networking;
receiving the MAC address and the IP address of the extender sent by the extender based on the information acquisition request;
and establishing or updating the corresponding relation table according to the received MAC address and IP address of each extender.
Optionally, the sending an information acquisition request to all the extenders in the Mesh networking includes:
and sending an information acquisition request to all devices in the Mesh networking in a broadcasting mode.
Optionally, the at least one program may further implement the following steps when executed:
if the information acquisition requests are continuously sent to all the extenders in the Mesh networking for preset times, the MAC address and the IP address sent by the first extender are not received, and the corresponding relation between the MAC address and the IP address of the first extender is deleted from the corresponding relation table.
Optionally, after the at least one program is executed to implement receiving a response from the target extender based on receiving the HTTP packet, the following steps may be implemented:
judging whether all target extenders receive responses based on the HTTP packets;
and if all the target extenders are received, sending a notification message to the user terminal based on the response of receiving the HTTP packet.
In some embodiments of the present invention, the at least one program may implement the following steps when executed:
receiving an HTTP packet sent by management equipment;
and sending a response of the HTTP packet to the management equipment based on the HTTP packet.
Optionally, the at least one program may further implement the following steps when executed:
receiving an information acquisition request sent by the management equipment;
and sending the MAC address and the IP address of the extender to the management equipment in response to the information acquisition request.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims (10)

1. A Mesh networking management method applied to management equipment, the method comprising:
receiving a Simple Object Access Protocol (SOAP) data packet sent by a user terminal;
analyzing the SOAP data packet, and determining a target extender according to the message header of the SOAP data packet;
acquiring a message body of the SOAP data packet;
encapsulating the message body of the SOAP data packet into a hypertext transfer protocol (HTTP) packet according to the target extender;
sending the HTTP packet to the target extender;
the receiving the target extender is based on receiving a response to the HTTP packet.
2. The Mesh networking management method of claim 1, wherein the parsing the SOAP packet and determining a target extender from a header of the SOAP packet comprises:
analyzing the SOAP data packet and judging whether the SOAP data packet comprises a message header or not;
if the SOAP data packet comprises a message header, determining a target extender according to the message header of the SOAP data packet.
3. The Mesh networking management method according to claim 1 or 2, wherein the determining the target extender according to the header of the SOAP packet includes:
acquiring the number information of destination addresses in a message header of the SOAP data packet;
judging whether the destination address quantity information is a preset value or not;
if the number information of the destination addresses is a preset value, determining that all the extenders in the Mesh networking are target extenders;
if the destination address quantity information is not a preset value, determining that an extender corresponding to the destination address information in the message header of the SOAP data packet is a target extender.
4. The Mesh networking management method of claim 1, wherein the determining the target extender from the header of the SOAP packet comprises:
determining the IP address of the target extender according to the message header of the SOAP data packet;
the encapsulating, according to the target extender, the message body of the SOAP data packet into a hypertext transfer protocol HTTP packet, including:
and packaging the IP address of the target extender and the message body of the SOAP data packet into a hypertext transfer protocol (HTTP) packet.
5. The Mesh networking management method of claim 4, wherein before receiving the simple object access protocol SOAP packet sent by the user terminal, the method further comprises:
sending an information acquisition request to all the extenders in the Mesh networking;
receiving the MAC address and the IP address of the extender sent by the extender based on the information acquisition request;
establishing or updating a corresponding relation table according to the received MAC address and IP address of each extender;
the determining the IP address of the target extender according to the message header of the SOAP data packet comprises the following steps:
acquiring a Media Access Control (MAC) address of a target extender carried in a message header of a SOAP data packet;
and acquiring the IP address corresponding to the MAC address from a corresponding relation table according to the MAC address of the target extender, wherein the IP address is the IP address of the target extender.
6. The Mesh networking management method of claim 5, wherein the method further comprises:
if the information acquisition requests are continuously sent to all the extenders in the Mesh networking for preset times, the MAC address and the IP address sent by the first extender are not received, and the corresponding relation between the MAC address and the IP address of the first extender is deleted from the corresponding relation table.
7. A Mesh networking management method applied to an extender, the method comprising:
the management equipment receives a Simple Object Access Protocol (SOAP) data packet sent by the user terminal;
analyzing the SOAP data packet, and determining the extender according to the message header of the SOAP data packet;
acquiring a message body of the SOAP data packet;
encapsulating the message body of the SOAP data packet into a HTTP packet according to the extender;
receiving an HTTP packet sent by the management equipment;
and sending a response of the HTTP packet to the management equipment based on the HTTP packet.
8. The Mesh networking management method of claim 7, wherein the method further comprises:
receiving an information acquisition request sent by the management equipment;
and sending the MAC address and the IP address of the extender to the management equipment in response to the information acquisition request.
9. A management device comprising a memory, at least one processor and at least one program stored on the memory and executable by the at least one processor, the at least one program, when executed by the at least one processor, implementing the steps in the method of any one of the preceding claims 1 to 6.
10. An extender comprising a memory, at least one processor and at least one program stored on the memory and executable by the at least one processor, the at least one program when executed by the at least one processor implementing the steps in the method of any of claims 8 or 9.
CN201810421348.6A 2018-05-04 2018-05-04 Mesh networking management method, management equipment and extender Active CN108833135B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810421348.6A CN108833135B (en) 2018-05-04 2018-05-04 Mesh networking management method, management equipment and extender

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810421348.6A CN108833135B (en) 2018-05-04 2018-05-04 Mesh networking management method, management equipment and extender

Publications (2)

Publication Number Publication Date
CN108833135A CN108833135A (en) 2018-11-16
CN108833135B true CN108833135B (en) 2023-06-06

Family

ID=64147460

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810421348.6A Active CN108833135B (en) 2018-05-04 2018-05-04 Mesh networking management method, management equipment and extender

Country Status (1)

Country Link
CN (1) CN108833135B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112887756B (en) * 2021-01-11 2023-02-07 上海七牛信息技术有限公司 Multi-input multi-output communication system and method for multimedia micro-service
CN112910909B (en) * 2021-02-08 2022-05-17 北京交通大学 Data packet processing method based on conversion of CoAP protocol and HTTP protocol

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101174983A (en) * 2006-07-19 2008-05-07 软件股份公司 System and method for managing a plurality of web services
CN101312404A (en) * 2007-05-24 2008-11-26 杭州华三通信技术有限公司 SNMP message processing method and apparatus
CN101854566A (en) * 2009-04-02 2010-10-06 华为技术有限公司 Passive optical network protection method and active/standby switch device and system
CN104579418A (en) * 2013-10-23 2015-04-29 西安洛灵杰电子通讯科技有限公司 Network extender based on LRE (Long- Reacher Ethernet) technique

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7136913B2 (en) * 2000-05-31 2006-11-14 Lab 7 Networks, Inc. Object oriented communication among platform independent systems across a firewall over the internet using HTTP-SOAP

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101174983A (en) * 2006-07-19 2008-05-07 软件股份公司 System and method for managing a plurality of web services
CN101312404A (en) * 2007-05-24 2008-11-26 杭州华三通信技术有限公司 SNMP message processing method and apparatus
CN101854566A (en) * 2009-04-02 2010-10-06 华为技术有限公司 Passive optical network protection method and active/standby switch device and system
CN104579418A (en) * 2013-10-23 2015-04-29 西安洛灵杰电子通讯科技有限公司 Network extender based on LRE (Long- Reacher Ethernet) technique

Also Published As

Publication number Publication date
CN108833135A (en) 2018-11-16

Similar Documents

Publication Publication Date Title
JP4921363B2 (en) Software program synchronization method
CN103069755B (en) Use the method and system that the instant message of multiple client instance transmits
EP1166575B1 (en) Radio handset
KR20100126433A (en) Techniques for discovering services provided in a wireless network
WO2020147030A1 (en) Cell registration method and terminal device
CN103260257A (en) Method and system capable of automatically building Wi-Fi Display connection to achieve screen sharing
CN103905981B (en) Position information sharing method and system
CN103974376A (en) Network connection assisting system and method
CN106293738B (en) Expression image updating method and device
CN108833135B (en) Mesh networking management method, management equipment and extender
US20090156162A1 (en) Communication system, communication terminal, server, communication method to be used therein and program therefor
JP2005196271A (en) Communication terminal and program
CN104113620A (en) Contact list updating method, updating device and user terminal
JP2005529550A5 (en)
CN111373709B (en) Terminal pairing method, server and terminal
EP3015990B1 (en) Information processing device, and destination information updating method and program
CN111756817A (en) Device discovery method, device and computer-readable storage medium
JP2009288863A (en) Communication system, information holding device, management device and terminal device
CN109165197B (en) File processing method, terminal and server
CN113825123A (en) Communication method, communication device, electronic equipment and computer storage medium
US20090216864A1 (en) Methods, apparatuses, and computer program products, for automatically finding configuration settings for services
WO2017142019A1 (en) Communication apparatus, router, server, system, and setting method
CN110896405A (en) Method, device, equipment and storage medium for remote control interaction
JP2005184278A (en) Terminal management method, terminal management apparatus, and portable communication terminal
JP2005339149A (en) Data processor, data processing method and data processing program

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