Network entity management method and network entity management system

Abstract

The invention provides a network entity management method and a network entity management system, the method is applied to a management network entity, the management network entity provides a management configuration interface, and the method comprises the following steps: monitoring a management configuration message sent by the management configuration interface; and sending the monitored management configuration message to a registered network entity, so that the registered network entity performs management configuration processing based on the management configuration message. In the embodiment of the invention, the management configuration message is monitored through the management configuration interface provided by the management network entity, and the monitored management configuration message is sent to the registration network entity, so that the registration network entity performs management configuration processing, uniform configuration and management of the network entity are realized, and the efficiency of managing the Mesh network is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a network entity management method and a network entity management system. BACKGROUND

[0002] With the rapid popularization of wireless fidelity (WiFi) technology and 5th generation wireless systems (5G) technology, users have higher and higher requirements for network latency and network coverage. In the use scenario of realizing network coverage, the experience of WiFi network is generally improved by deploying a wireless mesh network (Mesh).

[0003] A plurality of network entities are usually deployed in a Mesh network, and the plurality of network entities cannot be uniformly configured and managed. Therefore, there is an urgent need for a method for uniformly managing and configuring the plurality of network entities in the Mesh network, so as to improve the management efficiency of the Mesh network. SUMMARY

[0004] Therefore, the embodiments of the present application aim to provide a network entity management method and a network entity management system to solve the problem that the network entities in the Mesh network cannot be uniformly managed and configured in the prior art, resulting in low management efficiency of the Mesh network.

[0005] In a first aspect, a network entity management method is provided, which is applied to a management network entity. The management network entity provides a management configuration interface. The method comprises: listening to a management configuration message sent by the management configuration interface; and sending the listened management configuration message to a registered network entity, so that the registered network entity performs management configuration processing based on the management configuration message.

[0006] According to the first aspect, the method of sending the listened management configuration message to the registered network entity comprises: determining a management configuration target based on the management configuration message; and sending the management configuration message to the registered network entity in the case that the management configuration target is the registered network entity.

[0007] According to the first aspect or any one of the implementation manners of the first aspect, after determining the management configuration target based on the management configuration message, the method further comprises: performing management configuration processing based on the management configuration message in the case that the management configuration target is the management network entity.

[0008] According to the first aspect, or any one of the implementations of the first aspect, the management network entity comprises at least one terminal device; the method further comprises collecting device information of the terminal device and monitoring traffic data, so as to perform management configuration processing based on the device information and the traffic data of the terminal device.

[0009] According to the first aspect, or any one of the implementations of the first aspect, the method of listening to the management configuration message sent by the management configuration interface comprises: listening to the transmission message, identifying whether the message source of the transmission message is the management configuration interface; if the message source of the transmission message is the management configuration interface, determining that the transmission message is the management configuration message; if the message source of the transmission message is not the management configuration interface, determining that the transmission message is the response configuration message.

[0010] According to the first aspect, or any one of the implementations of the first aspect, the method of identifying whether the message source of the transmission message is the management configuration interface comprises: identifying whether the management configuration message is the first setting configuration message and / or the first query configuration message; if the message source of the transmission message is the management configuration interface, determining that the transmission message is the management configuration message, comprising: if the management configuration message is the first setting configuration message and / or the first query configuration message, determining that the transmission message is the management configuration message.

[0011] According to the first aspect, or any one of the implementations of the first aspect, before sending the listened management configuration message to the registered network entity, the method further comprises: identifying whether the management configuration message conforms to the message specification; if yes, performing the step of sending the listened management configuration message to the registered network entity.

[0012] According to the first aspect, or any one of the implementations of the first aspect, before identifying whether the management configuration message conforms to the message specification, the method further comprises: identifying whether the management configuration message is the second setting configuration message; if yes, performing the step of identifying whether the management configuration message conforms to the message specification, wherein the message specification comprises a setting node specification.

[0013] According to the first aspect, or any one of the implementations of the first aspect, after identifying whether the management configuration message is the second setting configuration message, the method further comprises: if the management configuration message is not the second setting configuration message, identifying whether the management configuration message is the second query configuration message; if yes, performing the step of identifying whether the management configuration message conforms to the message specification, wherein the message specification comprises a query node specification.

[0014] According to the first aspect, or any one of the implementations of the first aspect, the management configuration message comprises one or more of the following: a terminal device access restriction configuration message; a terminal device information query message; a network entity configuration information synchronization message.

[0015] According to the first aspect, or any one of the implementations of the above first aspect, the management network entity comprises a message transfer module, a message processing module, a message collection module and a message management module; the method further comprises: listening to the management configuration message sent by the management configuration interface through the message transfer module, and sending the management configuration message to the message processing module; analyzing and filtering the management configuration message through the message processing module, and sending the analyzed and filtered management configuration message to the message collection module; sending the management configuration message to the message management module through the message collection module; and sending the management configuration message to the registered network entity through the message management module.

[0016] The second aspect provides a network entity management method, which is applied to a registered network entity, and comprises: listening to the management configuration message sent by a management network entity; and performing management configuration processing based on the management configuration message.

[0017] The third aspect provides a network entity management system, which comprises a management network entity and a registered network entity; the management network entity is configured to provide a management configuration interface, listen to the management configuration message sent by the management configuration interface, and send the listened management configuration message to the registered network entity; and the registered network entity is configured to perform management configuration processing based on the management configuration message.

[0018] In the present application, the management configuration message is listened to through the management configuration interface provided by the management network entity, and the listened management configuration message is sent to the registered network entity, so that the registered network entity performs management configuration processing, thereby realizing unified configuration and management of the network entity and improving the efficiency of managing the Mesh network. BRIEF DESCRIPTION OF DRAWINGS

[0019] Figure 1 FIG. 1 is a schematic flowchart of a network entity management method provided by an embodiment of the present application.

[0020] Figure 2 FIG. 2 is a schematic flowchart of another network entity management method provided by an embodiment of the present application.

[0021] Figure 3 FIG. 3 is a schematic diagram of a processing procedure of a network entity management method provided by an embodiment of the present application.

[0022] Figure 4 FIG. 4 is a schematic diagram of an execution procedure of a management network entity in a network entity management method provided by an embodiment of the present application.

[0023] Figure 5 FIG. 5 is a schematic diagram of an interaction procedure between network entities in a network entity management method provided by an embodiment of the present application.

[0024] Figure 6 is a framework diagram of a network entity management system provided by an embodiment of the present application.

[0025] Figure 7 is an IEEE 1905 protocol message format schematic diagram provided by an embodiment of the present application. DETAILED DESCRIPTION

[0026] The technical solutions in the embodiments of the present application will be clearly and completely described with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of the present application.

[0027] The term "and / or" in the present application is only used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the three cases of A alone, A and B together, and B alone.

[0028] The terms "first" and "second" and the like in the specification and claims of the embodiments of the present application are used to distinguish different objects, and are not used to describe the specific order of the objects. For example, the first target object and the second target object are used to distinguish different target objects, and are not used to describe the specific order of the target objects.

[0029] In the embodiments of the present application, the words such as "exemplary" or "for example" are used to mean an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the words such as "exemplary" or "for example" are intended to present the relevant concept in a specific manner.

[0030] It should be understood that the specific embodiments described herein are only used to explain the present application, and are not used to limit the present application.

[0031] First, the noun terms related to one or more embodiments of the present application are explained.

[0032] Wireless Fidelity (WiFi) technology: also known as mobile hotspot, is a wireless local area network communication technology based on IEEE 802.11 standard, which uses 2.4GHz or 5GHz wireless frequency band to enable electronic devices (such as mobile phones, computers, tablets, etc.) to realize wireless access to the Internet within a certain range.

[0033] 5th Generation Wireless Systems (5G): A new generation of broadband mobile communication technology with high speed, low latency and large connection characteristics. 5G communication facilities are the network infrastructure for realizing man-machine and Internet of Things.

[0034] Wireless Mesh Network (Mesh): A network topology in which nodes such as routers, access points, etc. are connected to each other through multiple paths to form a network with a variable topology, such as chain topology, star topology and mesh topology.

[0035] EasyMesh network: A standardized application of Mesh network technology in home and small office scenarios, which is a subset of Mesh network.

[0036] IEEE1905 protocol: Full name is IEEE Std 1905.1, which is an important standard for home network, providing a unified interface and common structure for multiple network technologies to achieve efficient communication and cooperation between devices.

[0037] With the rapid popularization of WiFi technology and 5G technology, users have higher and higher demands for network latency and network coverage. In the implementation of network coverage scenarios, the use of Mesh is generally used to improve the experience of WiFi network.

[0038] The mainstream EasyMesh network only configures the WiFi-related information of each network entity in the Mesh network based on the demand for WiFi-related information configuration when deploying the Mesh network, realizes the configuration synchronization of the WiFi-related information of each network entity in the Mesh network, and cannot meet the flexible synchronization configuration between each network entity in the Mesh network during the operation of the Mesh network, which is not conducive to the unified configuration and management of the Mesh network, resulting in low efficiency of managing the Mesh network.

[0039] In order to solve the above problems, in the present application, the management configuration interface provided by the management network entity is used to listen to the management configuration message, and the management configuration message is sent to the registered network entity to make the registered network entity perform management configuration processing, so as to realize the unified configuration and management of the network entity and improve the efficiency of managing the Mesh network.

[0040] The embodiments of the present application will be described in detail below. Figure 1 The embodiments of the present application will be described in detail below.

[0041] Figure 1 is a schematic flowchart of a network entity management method provided by an embodiment of the present application, which is applied to a management network entity. The management network entity provides a management configuration interface to solve the above problems.

[0042] Figure 1 The network entity management method shown includes steps S110 to S120.

[0043] In step S110, a management configuration message sent by a management configuration interface is listened to.

[0044] In some embodiments, the management network entity refers to a network entity in a Mesh network that manages itself and other network entities, the management network entity is a network entity connected to the Internet, and the other network entities are connected to the management network entity and the other network entities through a connection mode not limited to WiFi or Ethernet, and through the connection, all network entities in the Mesh network can be connected to the Internet for communication, for example, the management network entity can be a CAP, and the other network entities can be referred to as a registered network entity RE. The network entity can be connected to one or more terminal devices, for example, the network entity can be a router, and the terminal device is a device connected to the router to access the network.

[0045] The management configuration interface refers to an interface for receiving and generating management configuration information, and the management configuration interface can be an interface webpage through which a user can input corresponding configuration information. The management configuration interface generates management configuration information based on the input configuration information and sends the generated management configuration information to the management network entity. The management configuration interface can provide configuration options, such as configuring the limit of the number of access devices, configuring the query of traffic, configuring the query of device load, and the like. The configuration options can also include network entity configuration selection, such as the need to configure and manage the registered network entity RE1, and the selection of RE1 in the network entity configuration selection.

[0046] Optionally, the management configuration interface can be opened by clicking the official webpage of the network entity, or by opening the configuration website recorded in the network entity, or by scanning the configuration two-dimensional code recorded in the network entity.

[0047] For example, a user has a demand for limiting the access of the registered network entity RE to 6 devices, scans the two-dimensional code at the bottom of the router with a mobile phone, opens the interface webpage, and determines the network entity configuration selection as RE2 and the limit of the number of access devices as 6 in the interface webpage. The user clicks the confirm button or the enter button to make the management configuration interface generate the management configuration information.

[0048] After the management configuration interface generates the management configuration message, it is transmitted to the management network entity through a fixed communication transmission channel. The management network entity listens to the transmitted message and listens to the management configuration message sent by the management configuration interface.

[0049] In some embodiments, the management network entity monitors the message data of the reference protocol, and rejects to receive or monitor other data except the message data of the reference protocol, or receives, monitors, etc. according to the requirement of other types of message settings. For example, the message of the reference protocol can be a protocol type that is set in advance to receive the management configuration type message, and the reference protocol can be the IEEE1905 protocol.

[0050] In step S120, the monitored management configuration message is sent to the registered network entity, so that the registered network entity performs management configuration processing based on the management configuration message.

[0051] In some embodiments, the management network entity monitors the management configuration message sent by the management configuration interface, sends the management configuration message to the registered network entity, so that the registered network entity performs management configuration processing, and realizes unified configuration and management of all network entities through the management configuration interface provided by the management network entity.

[0052] In an optional embodiment of the present application, after the management network entity monitors the management configuration message sent by the management configuration interface, the management network entity can determine a management configuration target based on the management configuration message, and in the case that the management configuration target is the registered network entity, the management network entity sends the management configuration message to the registered network entity.

[0053] In some embodiments, determining the management configuration target based on the management configuration message can be parsing the management configuration message, reading the identifier of the network entity from the parsing result, and determining the management configuration target based on the read identifier; or extracting an identifier keyword from the management configuration message, and determining the management configuration target based on the extracted identifier keyword.

[0054] In the case of determining the management configuration target, the management configuration message is sent to the corresponding network entity, so that the corresponding network entity performs management configuration processing based on the management configuration message, which can accurately send the management configuration message to the corresponding network entity, realize precise configuration of the network entity, and improve the user's perception and operation convenience of the Mesh network.

[0055] In an optional embodiment of the present application, the management configuration target can also be the management network entity, and in the case that the management configuration target is the management network entity, the management network entity performs management configuration processing based on the management configuration message, realizes accurate and unified configuration and management of all network entities in the Mesh network, and improves the user's perception and operation convenience of the Mesh network.

[0056] Exemplarily, the management network entity parses the management configuration message, reads the network entity identifier as RE3, determines RE3 as the management configuration target, and sends the management configuration message to RE3 to enable RE3 to perform management configuration processing based on the management configuration message.

[0057] In the prior art, the Mesh network cannot flexibly configure and read the access restriction and information collection of the terminal devices included in each network entity, which is not conducive to unified configuration and management of the Mesh network, resulting in poor user perception and operation convenience of the Mesh network. In an optional embodiment of the present application, the management network entity includes at least one terminal device; the management network entity collects device information of each terminal device and monitors traffic data, and performs management configuration processing based on the collected device information and the monitored traffic data in the case of the management configuration target being the management network entity.

[0058] Optionally, after the management network entity collects the device information and monitors the traffic data, the device information and the traffic data can be stored in a management database, and the device information and / or the traffic data can be extracted from the management database for management configuration processing when needed.

[0059] Exemplarily, the collected device information can be device model, MARK address, 2G address, and the like of the access terminal device, and the monitored traffic data can be uplink rate and downlink rate of the network connection, and the like.

[0060] Exemplarily, when a user connects the management network entity through a terminal device to obtain an interconnection relationship, the user sends a connection request to the management network entity, which can include a connection password and device information of the terminal device, so as to facilitate the management network entity to determine whether to connect the terminal device based on the connection password and record the device information of the terminal device.

[0061] The management network entity collects and monitors the device information and traffic data of the included terminal devices, which facilitates subsequent collection based on the device information and the traffic data, and avoids temporary collection and monitoring when there is management configuration processing, thereby improving the efficiency of management configuration processing and solving the problem in the prior art that the access restriction and information of the terminal devices included in each network entity in the Mesh network cannot be uniformly configured and managed.

[0062] In step S110, in an optional embodiment of the present application, the management configuration message sent by the management configuration interface can be a transmission message, and the message source of the transmission message is identified. If the message source of the transmission message is the management configuration interface, it is determined that the transmission message is the management configuration message.

[0063] In some embodiments, the transmission message is a message transmitted to the management network entity, the transmission message can be in the form of a message conforming to a reference protocol, and the source of the transmission message can be the management configuration interface or a response configuration message generated based on a management configuration message response returned by the registration network entity.

[0064] After listening to the transmission message, the source of the transmission message is identified. If the source is the management configuration interface, it is determined that the transmission message is the management configuration interface. If the source is not the management configuration interface, it is determined that the transmission message is the response configuration message returned by the registration network entity.

[0065] Optionally, in the case where it is determined that the transmission message is the response configuration message generated by the registration network entity based on the management configuration message, the management network entity stores the response configuration message in the management database.

[0066] There are many ways to identify the source of the transmission message, which are not limited in the present application. For example, it can be identified whether the message type of the transmission message is the first setting configuration message and / or the first query configuration message. If it is identified that the transmission message is the first setting configuration message and / or the first query configuration message, it is determined that the source is the management configuration interface. If not, it is determined that the transmission message is the response configuration message. It can also be identified the source identification carried by the transmission message, and the source is determined based on the source identification. If the source identification is the identification of the management configuration interface, it is determined that the transmission message is the management configuration message. If the source identification is the registration network entity, it is determined that the transmission message is the response configuration message, etc.

[0067] The first setting configuration message and the first query configuration message are message types of the management configuration message. The first setting configuration message is used to perform setting configuration, and the first query configuration message is used to perform query configuration. For example, the first setting configuration message can be to set the access device limit of the registration network entity to 7, and the networking speed of the terminal device included in the registration network entity. The first query configuration message can be to query the device model of the terminal device included in the management network entity, and the uplink rate of the terminal device included in the registration network entity, etc.

[0068] The messages listened to by the management network entity generally cannot only include the management configuration messages sent by the management configuration interface. By identifying the source of the transmission message, it can be accurately identified whether the transmission message is the management configuration message from the transmission message listened to, so as to facilitate sending the identified management configuration message to the registration network entity for management configuration processing.

[0069] In an optional embodiment of the present application, before sending the monitored management configuration message to the registered network entity, it is identified whether the management configuration message conforms to the message specification. If yes, the monitored management configuration message is sent to the registered network entity.

[0070] In some embodiments, the message specification is defined by the standard of the reference protocol, for ensuring that the message format, content, timing, etc. conforms to the processing requirement of the network entity, so that the management configuration message conforming to the message specification can be correctly parsed and processed by the registered network entity.

[0071] The message specification is different according to the message type. For example, if the message type is a set configuration message, the message specification is a set node specification, which can be a TR-181 node specification including Set, AddObject, DelObject, etc. If the message type is a query message type, the message specification is a query node specification, which can be a TR-181X node specification including Get, devList and ACLList, etc.

[0072] Before sending the monitored management configuration message to the registered network entity, it is identified whether the management configuration message conforms to the message specification. Only if the management configuration message conforms to the message specification, it is sent to the registered network entity, so that the management configuration message sent to the registered network entity can be correctly parsed and processed by the registered network entity, improving the success rate of management configuration and the convenience of user operation on the Mesh network.

[0073] In an optional embodiment of the present application, the message type of the management configuration message is different, and the corresponding message specification required to be conformed is also different. It is identified whether the management configuration message is a second set configuration message. If yes, it is identified whether the management configuration message conforms to the set node specification. If yes, the management configuration message is sent to the registered network entity.

[0074] If it is identified that the management configuration message does not conform to the set node specification, it is returned to step S110 to monitor the management configuration message sent by the management configuration interface.

[0075] If it is identified that the management configuration message does not conform to the set node specification in the case that the management configuration message is determined to be a second set configuration message, it is determined that the management configuration message is a problem message and the information contained therein cannot be extracted, so it is returned to monitor the management configuration message sent by the management configuration interface.

[0076] Optionally, in a case where it is determined that the management configuration message is the second setting configuration message, the management configuration message is parsed to obtain a setting sub-configuration message of the management configuration message, and it is identified whether the setting sub-configuration message conforms to a setting node specification.

[0077] For example, it is identified whether the setting sub-configuration message conforms to one of Set, AddObject, DelObject, etc., and if yes, it is determined that the management configuration message conforms to the message specification, and the management configuration message can be sent to the registered network entity.

[0078] If it is identified that the setting sub-configuration message does not conform to the setting node specification, the step S110 is returned to, and the management configuration message sent by the management configuration interface is listened to.

[0079] In a case where the management configuration message is parsed to obtain the setting sub-configuration message, if it is identified that the setting sub-configuration message does not conform to the setting node specification, it is determined that the management configuration message is a problem message, and information contained in the management configuration message cannot be extracted, and thus the step S110 is returned to, and the management configuration message sent by the management configuration interface is listened to.

[0080] If the management configuration message is not the second setting configuration message, it is identified whether the management configuration message is a second query configuration message, and if yes, it is identified whether the management configuration message conforms to a query node specification, and if yes, the management configuration message is sent to the registered network entity.

[0081] In a case where it is determined that the management configuration message is the second query configuration message, if it is identified that the management configuration message does not conform to the query node specification, the step S110 is returned to, and the management configuration message sent by the management configuration interface is listened to.

[0082] In a case where it is determined that the management configuration message is the second query configuration message, if it is identified that the management configuration message does not conform to the query node specification, it is determined that the management configuration message is a problem message, and information contained in the management configuration message cannot be extracted, and thus the step S110 is returned to, and the management configuration message sent by the management configuration interface is listened to.

[0083] In a case where the management configuration message is the second setting configuration message, it is identified whether the management configuration message conforms to the setting node specification, and in a case where the management configuration message is the second query configuration message, it is identified whether the management configuration message conforms to the query node specification, and based on the difference in message type, the node specification corresponding to the message type is used for identification, so that the result of identification is more accurate, and it is more convenient for the registered network entity to perform management configuration processing based on the management configuration message, and the efficiency of management configuration processing of the registered network entity is improved.

[0084] In an optional embodiment of the application, the management configuration message comprises one or more of a terminal device access restriction configuration message, a terminal device information query message, and a network entity configuration information synchronization message.

[0085] In some embodiments, the terminal device access restriction configuration message is used to configure the number of terminal devices included in the registration network entity, for example, the terminal device access restriction configuration message is used to configure the number of terminal devices included in the RE4 to be 8. The terminal device information query message is used to query the device information of the terminal devices included in the registration network entity, for example, the terminal device information query message is used to query the types of the terminal devices included in the RE4. The network entity configuration information synchronization message is used to keep the common information between the registration network entity and the management network entity in synchronization, for example, the common information is the type of the terminal device.

[0086] The management configuration message can be one or more of the terminal device access restriction configuration message, the terminal device information query message, and the network entity configuration information synchronization message, so that the terminal device access restriction, the device information query, and the network entity configuration information synchronization can be uniformly configured and managed by using the network entity management method of the present application, and the perception and operation convenience of the user in managing the Mesh network are improved.

[0087] In an optional embodiment of the present application, the network entity includes a message transfer module, a message processing module, a message collection module, and a message management module; the message transfer module, the message processing module, the message collection module, and the message management module perform message transmission in a chained manner.

[0088] The message format transmitted between the four modules is the format of a reference protocol message, for example, the reference protocol can be the IEEE1905 protocol.

[0089] In some embodiments, the message transfer module is a message transfer station for transmitting messages of the network entity, used to listen to messages, receive / send the interaction of messages between the network entity and other network entities, and if the message transfer module is a module of the management network entity, the message transfer module is also used to receive the management configuration message sent by the management network entity and the management configuration interface. For example, the message transfer module can be a libieee1905 module.

[0090] When the message transfer station receives and sends messages, it creates a network socket, encapsulates a receive / send system call interface, realizes the interaction of messages between network entities, and realizes the transfer of messages.

[0091] In some embodiments, the message processing module is a message processing station for transmitting messages of the network entity, and the message processing module is connected to the message transfer station, used to parse and filter the messages transferred by the message transfer station, encapsulate the content of the parsed messages, and used to centrally process the messages. For example, the message processing module can be a mesh_map module.

[0092] In some embodiments, the message collection module is connected with the message processing module, for listening to and receiving the message transmitted by the message processing module, and sending the listened and received message to the message management module. Through the message collection module, the message listened to by the message processing module can be transmitted to the message management module. For example, the message collection module can be a map_ext module.

[0093] In some embodiments, the message management module is connected with the message collection module, for calling the sending interface in the message collection module to request to query the network entity parameter, and calling the receiving interface in the message collection module to receive the network entity response message. The device information collection and the traffic data monitoring of the terminal device are supported, the collected device information and the monitored traffic data are stored into the management database, and the Mesh network deployment query, the configuration of each network entity and the terminal device included in each network entity are supported. For example, the message management module can be a stamanage module.

[0094] Optionally, when the message management module in the management network entity collects the device information and monitors the traffic data of the terminal device included in the management network entity, the collection and the monitoring can be directly performed. After the message management module in the registered network entity collects the device information and monitors the traffic data of the terminal device included in the registered network entity, the collected and monitored data can be sent to the management network entity, so as to realize the better unified management and configuration of the management network entity to each registered network entity.

[0095] By integrating the message relay module, the message processing module, the message collection module and the message management module in the network entity, the coupling degree between the modules is reduced, the modification of the module structure is facilitated, and the convenience of the network entity management method for the unified management and configuration of each network entity in the Mesh network is improved.

[0096] In some embodiments, during the power-on process of the network entity, the message relay module, the message processing module, the message collection module and the message management module are loaded. When the network entity is loaded, the functions of the modules are also loaded and start to work.

[0097] In some embodiments of the present application, the management network entity includes the message relay module, the message processing module, the message collection module and the message management module. The message relay module listens to the management configuration message sent by the management configuration interface, and sends the management configuration message to the message processing module; the message processing module analyzes and filters the management configuration message, and sends the analyzed and filtered management configuration message to the message collection module; the message collection module sends the management configuration message to the message management module; the message management module sends the management configuration message to the registered network entity.

[0098] Figure 2 is a schematic flow chart of another network entity management method provided by the embodiment of the present application, applied to a registered network entity.

[0099] Figure 2 The network entity management method shown includes steps S210 to S220.

[0100] Step S210, listening to the management configuration message sent by the management network entity.

[0101] Step S220, performing management configuration processing based on the management configuration message.

[0102] When the registered network entity listens to the management configuration message sent by the management network entity, the management configuration processing is performed based on the management configuration message, so as to realize the response to the management configuration requirement of generating the management configuration message through the management configuration interface.

[0103] Optionally, after the registered network entity performs the management configuration processing based on the management configuration message, a response configuration message is generated based on the processing result of the management configuration processing, and the response configuration message is returned to the management network entity.

[0104] Optionally, after the registered network entity performs the management configuration processing, the processing result is stored in the registered database.

[0105] When the registered network entity receives the management configuration message sent by the management network entity, the management configuration processing is performed based on the management configuration message, so as to realize the accurate response to the management configuration requirement, and facilitate the improvement of the perception of users.

[0106] In an optional embodiment of the present application, the registered network entity includes at least one terminal device; the registered network entity collects the device information of the terminal device and monitors the traffic data, so that the registered network entity performs the management configuration processing based on the device information and the traffic data of the terminal device.

[0107] The registration network entity collects and monitors the device information and traffic data of the included terminal device, facilitates subsequent collection based on the device information and traffic data, and through real-time collection and monitoring, avoids temporary collection and monitoring when there is management configuration processing, improves the efficiency of management configuration processing, and solves the problem in the prior art that the access restriction and information of the terminal device included in each network entity in the Mesh network cannot be uniformly configured and managed.

[0108] In an optional embodiment of the application, the registration network entity also includes a message transfer module, a message processing module, a message collection module and a message management module. The message transfer module receives the management configuration message sent by the management network entity, and sends the management configuration message to the message processing module; the message processing module analyzes and filters the management configuration message, and sends the analyzed and filtered management configuration message to the message collection module; the message collection module sends the management configuration message to the message management module; and the message management module performs management configuration processing based on the management configuration message.

[0109] When the management network entity and the registration network entity, the inside of the management network entity and the inside of the registration network entity perform message interaction, the messages to be interacted are encapsulated through a reference type protocol. For example, the reference type protocol is IEEE1905 protocol.

[0110] The following will be described in detail with reference to the accompanying drawings Figure 3 The above Figure 1 And Figure 2 The network entity management method provided by the application is further described. Wherein, Figure 3 is a processing process flow diagram of a network entity management method provided by an embodiment of the application, and specifically includes the following steps.

[0111] In step S310, the CAP listens to the IEEE1905 protocol message and obtains the transmission message.

[0112] The libieee module in the CAP listens to the IEEE1905 protocol message, and sends the listened IEEE1905 protocol message to the mesh_map module; the mesh_map module analyzes and filters the IEEE1905 protocol message, obtains the event type transmission message, and sends the transmission message to the map_ext module; and the map_ext module sends the listened transmission message to the sta manage module.

[0113] The map_ext module sends the monitored transmission message to the staManage module, which can include that when the CAP is powered on, the staManage module starts the staService service message, and monitors transmission messages of different event types from a registered network entity RE, a local terminal device, or a local management module (not limited to a TR-69, WEB GUI, or other management service module) of the CAP.

[0114] The transmission message monitored by the staManage module is chained through the libieee module, the mesh-map module, and the map_ext module, and is monitored by the staManage module.

[0115] In step S320, the CAP determines a management configuration target based on the transmission message, and transmits the transmission message to the RE if the management configuration target is the RE.

[0116] After the staManage module monitors the transmission message by using the staService service message, the staManage module identifies the message source of the transmission message. If the message source is the registered network entity RE, the staManage module determines that the transmission message is a response configuration message sent by the RE, and operates the management database according to the sub-type of the response configuration message. If the message source is a message of a setting type or a query type sent by the management configuration interface, the staManage module identifies the management configuration target. If the management configuration target is the CAP itself, the staManage module performs query processing based on a query message if the query message is a query message of the CAP itself. The query message can be a terminal device query, an access query of a terminal device, or a query event satisfying the TE-181X specification. The staManage module performs setting processing based on a setting message if the setting message is a setting message of the CAP itself. The setting message is a setting event satisfying the TR-181 specification.

[0117] After the staManage module monitors the event type transmission message by using the staService service message, the staManage module performs identification and judgment processing on the transmission message, determines a processing mode of the transmission message, and refers to Figure 4 , which shows an example process of identification and judgment processing on the event type transmission message.

[0118] Referring to Figure 4 , Figure 4 is a schematic diagram of a process of managing a network entity in a network entity management method provided in an embodiment of the present application.

[0119] The stamanage module is started, the stamanage module enables the staService to listen to the event type, it is judged whether the event type listened to is a setting operation, if yes, the operation sub-type of the setting operation is determined, it is judged whether the operation sub-type conforms to the ExtVendor, if yes, it is judged whether the operation sub-type conforms to the TR-181 node specification, for example, whether the operation sub-type is Set, AddOject, DelOject, if the operation sub-type conforms to the TR-181 node specification (yes), the event type is encapsulated, and the message is sent, if the operation sub-type does not conform to the ExtVendor (no), the listening event type is returned to execute, if the operation sub-type does not conform to the TR-181 node specification (no), the listening event type is returned to execute.

[0120] In the case where it is judged that the event type is not a setting operation (no), it is judged whether the event type listened to is a query operation, if yes, it is judged whether the query operation conforms to the devList, if yes, the transmission message of the event type is encapsulated and the message is sent, if the query operation does not conform to the devList (no), it is judged whether the query operation conforms to the ACLList, if yes, the transmission message of the event type is encapsulated and the message is sent, if the query operation does not conform to the ACLList (no), it is judged whether the query message conforms to the ExtVendor, if no, the listening event type is returned to execute, if the query message conforms to the ExtVendor (yes), it is judged whether the query operation conforms to the TR-181, if yes, the transmission message of the event type is encapsulated and the message is sent, if no, the listening event type is returned to execute.

[0121] In the case where it is judged that the event type is not a query operation, it is judged whether the event type listened to is a response message, if yes, it is judged whether the response message conforms to the devList, if yes, the management database is updated based on the response message, if no, it is judged whether the response message conforms to the ACLList, if yes, the management database is updated based on the response message, if the response message does not conform to the ACLList (no), the listening event type is returned to execute.

[0122] In the case where it is judged that the event type is not a response message, the listening event type is returned to execute.

[0123] In step S330, the RE listens to and receives the transmission message.

[0124] The RE listens to the transmission message sent by the CAP through the libieee module, and the transmission message reaches the stamanage module through the libieee module, the mesh_map module and the map_ext module.

[0125] Step S340, the RE performs management configuration processing based on the received transmission message, and returns the processing result of the management configuration processing to the CAP.

[0126] The stamanage module performs management configuration processing based on the transmission message, generates a response message based on the processing result of the management configuration processing, and returns the response message to the CAP.

[0127] For steps S320 to S340, in combination with Figure 5 are explained in detail, Figure 5 is a network entity interaction process schematic diagram in a network entity management method provided by the embodiment of the present application.

[0128] After the network entity CAP receives different event types, the staEventSerive service class of the staSendData function interface of the stamanage module is called according to the event type (T1), and the map_data_send interface of the map_ext dynamic link library is called by the staSendData function interface (T2).

[0129] The map_data_send function interface of the map_ext module creates a network socket, and sends the stamanage module message to the ieee1905Service service class in the mesh_map module (T3).

[0130] The ieee1905Service service class in the mesh_map module encapsulates the message according to the content delivered by the map_ext module, and calls the libieee1905 module after the message encapsulation is completed (T4).

[0131] The libieee1905 module sends the encapsulated message to the RE by using the backhaul link (BHL, Backhaul Link, BHL) in the Mesh network.

[0132] The libieee1905 module of the network entity RE listens to the message sent by the CAP encapsulation, the mesh_map module monitors and receives the IEEE1905 message on the BHL link, and performs message analysis and filtering in the ieee1905Service service class (T5). If it is an extended message, the mapExtService service class is further called (T6), and the message is sent to the map_ext module by using the network socket (T7). The mesh_map module in the CAP further includes the tdService service class, and the mesh_map module in the RE further includes the tdService service class.

[0133] The staRecvData function interface of the staEventService service class in the stamanage module dynamically links the map_ext module and calls map_event_get to listen to the network socket created in real time (T8) to receive information sent from the mesh_map module. After receiving the relevant message from the network entity CAP, different operations are performed according to different message types.

[0134] For example, if the received message is a query type event, the staService service class related function interface is called to query the relevant information in the registration database. If it is a setting type event, the staService service class related function interface (T9) is called to perform configuration validation, and the configuration information is updated to the registration database dataBase1 (T10).

[0135] After the network entity RE receives the relevant message, the response is to call the staSendData function interface of the staEventSerive service class in the stamanage module (R1), and the staSendData function interface calls the map_data_send interface of the map_ext dynamic link library (R2).

[0136] The map_data_send function interface of the map_ext module creates a network socket and sends the stamanage module message to the ieee1905Service in the mesh_map module (R3).

[0137] The ieee1905Service service class in the mesh_map module encapsulates the message according to the content delivered by the map_ext module, and calls the libieee1905 module after the message encapsulation is completed (R4).

[0138] The libieee1905 module sends the encapsulated message to the CAP through the backhaul link (BHL, Backhaul Link, BHL) in the Mesh network.

[0139] The libieee1905 module of the CAP listens to the message sent by the RE encapsulation, the mesh_map module monitors and receives the IEEE1905 message on the BHL link (R5), and performs message analysis and filtering in the ieee1905Service service class. If it is an extended message, the mapExtService service class is further called (R6), and the message is sent to the map_ext module through the network socket (R7).

[0140] The function interface staRecvData in the staEventService service class in the stamanage module dynamically links the map_ext module, and calls map_event_get to listen to the created network socket in real time (R8). The stamanage module calls the staService service class to receive the response sent by the mesh_map module (R9), and updates the management database dataBase2 based on the response message (R10).

[0141] By applying the scheme of the embodiments of the present application, the management configuration messages are listened to through the management configuration interface provided by the management network entity, and the listened management configuration messages are sent to the registered network entity, so that the registered network entity performs management configuration processing, the unified configuration and management of the network entity are realized, and the efficiency of managing the Mesh network is improved.

[0142] Figure 6 Fig. 1 is a framework diagram of a network entity management system provided by an embodiment of the present application. The network entity management system 600 includes a management network entity 610 and a registered network entity 620.

[0143] The management network entity 610 is configured to provide a management configuration interface, listen to a management configuration message sent by the management configuration interface, and send the listened management configuration message to the registered network entity 620. The registered network entity 620 is configured to perform management configuration processing based on the management configuration message.

[0144] The management network entity 610 is further configured to determine a management configuration target based on the management configuration message, and send the management configuration message to the registered network entity 620 when the management configuration target is the registered network entity 620.

[0145] The management network entity 610 is further configured to perform management configuration processing based on the management configuration message when the management configuration target is the management network entity 610.

[0146] The management network entity 610 includes at least one terminal device. The management network entity 610 is further configured to collect device information of the terminal device and monitor traffic data, so as to perform management configuration processing based on the device information and the traffic data of the terminal device.

[0147] The management network entity 610 is further configured to listen to a transmission message, identify whether a message source of the transmission message is the management configuration interface, determine that the transmission message is a management configuration message when the message source of the transmission message is the management configuration interface, and determine that the transmission message is a response configuration message when the message source of the transmission message is not the management configuration interface.

[0148] The management network entity 610 is further configured to identify whether the management configuration message is a first setting configuration message and / or a first query configuration message, and determine that the transmission message is the management configuration message if the management configuration message is the first setting configuration message and / or the first query configuration message.

[0149] The management network entity 610 is further configured to identify whether the management configuration message conforms to a message specification, and send the monitored management configuration message to the registration network entity 620 if a message source of the transmission message is the management configuration interface.

[0150] The management network entity 610 is further configured to identify whether the management configuration message is a second setting configuration message, and identify whether the management configuration message conforms to a message specification if the management configuration message is the second setting configuration message, wherein the message specification comprises a setting node specification.

[0151] The management network entity 610 is further configured to identify whether the management configuration message is a second query configuration message if the management configuration message is not the second setting configuration message, and identify whether the management configuration message conforms to a message specification if the management configuration message is the second query configuration message, wherein the message specification comprises a query node specification.

[0152] The management network entity 610 comprises a first message relay module, a first message processing module, a first message collection module, and a first message management module. The first message relay module is configured to monitor a management configuration message sent by a management configuration interface, and send the management configuration message to the first message processing module. The first message processing module is configured to analyze and filter the management configuration message, and send the analyzed and filtered management configuration message to the first message collection module. The first message collection module is configured to send the management configuration message to the first message management module. The first message management module is configured to send the management configuration message to the registration network entity 620.

[0153] The registration network entity 620 comprises a second message relay module, a second message processing module, a second message collection module, and a second message management module. The second message relay module is configured to monitor the management configuration message, and send the management configuration message to the second message processing module. The second message processing module is configured to analyze and filter the management configuration message, and send the analyzed and filtered management configuration message to the second message collection module. The second message collection module is configured to send the management configuration message to the second message management module. The second message management module is configured to perform management configuration processing based on the management configuration message.

[0154] Optionally, in actual applications, the network entity management system can only comprise the management network entity, and the management network entity monitors the management configuration message through the management configuration interface and performs management configuration processing based on the management configuration message. For example, the registration network entity can be 0, 1, 2, or more.

[0155] By applying the scheme of the embodiment of the application, the management configuration interface provided by the management network entity is used to listen to the management configuration message, and the listened management configuration message is sent to the registered network entity, so that the registered network entity performs management configuration processing, unified configuration and management of the network entity are realized, and the efficiency of management of the Mesh network is improved.

[0156] Figure 7 is a schematic diagram of an IEEE1905 protocol message format provided by the embodiment of the application.

[0157] DA, SA, 0x893A, Header, Verdor Specific TLV and End of Msg TLV jointly constitute a complete IEEE1905 protocol message format, wherein DA, SA and 0x893A are Ethernet protocols, header, TLV and END TLV are payload messages of the Ethernet, i.e. the message body of the IEEE1905 protocol.

[0158] Wherein, Type, Len, OUI, Specific Msg Type and Data are format descriptions of the IEEE1905 message, Specific Msg Type is a message sub-type, and Data is message content.

[0159] The type (Type) of the IEEE1905 protocol message can be IEEE1905_TLV_TYPE_VENDOR_SPECIFIC (a type that can be privately defined by each network entity manufacturer); the message sub-type (Specific Msg Type) can be IEEE1905_MSG_TR-181_EXT_TYPE_GET (used for obtaining TR181 node configuration), IEEE1905_MSG_DEVICE_LIST_TYPE_GET (used for obtaining terminal equipment query included by the network entity), IEEE1905_MSG_DEVICE_ACL_LIST_TYPE_GET (used for obtaining access restriction of the terminal equipment of the network entity), IEEE1905_MSG_TR181_EXT_TYPE_SET (used for sending TR-181 node configuration), IEEE1905_MSG_DEVICE_LIST_TYPE_SET (used for sending terminal equipment query included by the network entity), and IEEE1905_MSG_DEVICE_ACL_LIST_TYPE_SET (used for sending access restriction of the terminal equipment included by the network entity).

[0160] The above only describes preferred embodiments of the present application and is not used to limit the present application, and any modification, equivalent replacement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method for managing network entities, characterized in that, Applied to a management network entity that provides a management configuration interface, the method includes: Listen for management configuration messages sent by the management configuration interface; The monitored management configuration message is sent to the registered network entity so that the registered network entity can perform management configuration processing based on the management configuration message.

2. The method according to claim 1, characterized in that, Sending the monitored management configuration message to the registered network entity includes: Based on the management configuration message, determine the management configuration objective; When the management configuration target is a registered network entity, the management configuration message is sent to the registered network entity.

3. The method according to claim 2, characterized in that, After determining the management configuration target based on the management configuration message, the method further includes: When the management configuration target is the management network entity, management configuration processing is performed based on the management configuration message.

4. The method according to claim 3, characterized in that, The management network entity includes at least one terminal device; the method further includes: The device information of the terminal device is collected and traffic data is monitored to enable management and configuration processing based on the device information and traffic data of the terminal device.

5. The method according to claim 1, characterized in that, The process of listening to the management configuration messages sent by the management configuration interface includes: Listen to transmitted messages and identify whether the message source of the transmitted message is the management configuration interface; If the source of the transmitted message is the management configuration interface, then the transmitted message is determined to be a management configuration message; If the source of the transmitted message is not the management configuration interface, then the transmitted message is determined to be a response configuration message.

6. The method according to claim 5, characterized in that, The step of identifying whether the message source of the transmitted message is the management configuration interface includes: Identify whether the management configuration message is a first setting configuration message, and / or a first query configuration message; If the source of the transmitted message is the management configuration interface, then the transmitted message is determined to be a management configuration message, including: If the management configuration message is the first setting configuration message and / or the first query configuration message, then the transmission message is determined to be a management configuration message.

7. The method according to claim 1, characterized in that, Before sending the monitored management configuration message to the registered network entity, the method further includes: Identify whether the management configuration message conforms to the message specification; If so, then the step of sending the monitored management configuration message to the registered network entity is performed.

8. The method according to claim 7, characterized in that, Before identifying whether the management configuration message conforms to the message specification, the method further includes: Identify whether the management configuration message is a second setting configuration message; If so, then the step of identifying whether the management configuration message conforms to the message specification is performed, wherein the message specification includes setting node specifications.

9. The method according to claim 8, characterized in that, After identifying whether the management configuration message is a second setting configuration message, the method further includes: If the management configuration message is not the second setting configuration message, then identify whether the management configuration message is the second query configuration message; If so, then the step of identifying whether the management configuration message conforms to the message specification is performed, wherein the message specification includes the query node specification.

10. The method according to claim 1, characterized in that, The management configuration message includes one or more of the following: Terminal device access restriction configuration message; Terminal device information query message; Network entity configuration information synchronization message.

11. The method according to claim 1, characterized in that, The management network entity includes a message relay module, a message processing module, a message collection module, and a message management module; the method further includes: The message relay module listens for management configuration messages sent by the management configuration interface and sends the management configuration messages to the message processing module. The message processing module parses and filters the management configuration message, and then sends the parsed and filtered management configuration message to the message collection module. The management configuration message is sent to the message management module through the message collection module; The management configuration message is sent to the registered network entity through the message management module.

12. A method for managing network entities, characterized in that, Applied to registering network entities, the method includes: Listen for management configuration messages sent by the management network entity; Management configuration processing is performed based on the aforementioned management configuration message.

13. A network entity management system, characterized in that, The network entity management system includes managing network entities and registering network entities; The management network entity is used to provide a management configuration interface, listen for management configuration messages sent by the management configuration interface, and send the listened-for management configuration messages to the registered network entity; The registered network entity is used to perform management configuration processing based on the management configuration message.

Images