CN114627633A - Ad hoc network water meter centralized reading system and method based on multi-agent construction - Google Patents

Abstract

The invention relates to a system and a method for centralized reading of Ad hoc network water meters constructed based on multiple agents, wherein the system is divided into three stages, and comprises three different agents, namely a collector Agent, a concentrator Agent and a management center Agent; the collector Agent is connected with the water meter sensor and collects the reading of the water meter in real time; the concentrator Agent is responsible for managing the work of a plurality of collector agents and is used for summarizing the data of the collector agents or issuing instructions to the collectors to control the running states of the collectors; the management center Agent manages a plurality of concentrator Agent nodes, collects data of each concentrator Agent node, and issues commands to the collector agents under the concentrator Agent nodes. The invention provides a basic Internet of things perception layer for intelligent water affairs, provides accurate water affair data for water affair management, quickly acquires all available information such as water quality and the like at any time, realizes the aims of water saving and energy saving, better manages water supply and drainage facilities distributed all over, and improves the operation and maintenance management efficiency.

Description

Ad hoc network water meter centralized reading system and method based on multi-agent construction

technical field

The invention relates to the field of centralized reading of water meters, in particular to an Ad hoc network centralized reading system and method based on multi-agent construction.

Background technique

Micro-power wireless meter reading has been applied to the hydropower industry since the late 1990s. In more than 10 years of technological development, it has experienced star network, tree network, fixed frequency grid network transmission, and has now partially developed to The fourth generation technology, automatic frequency hopping, Ad-Hoc network data transmission mode of ad hoc network. Ad hoc network application has not received much attention in the meter reading industry. At present, domestic Yu Jian discussed the Ad hoc network protocol and its application in wireless meter reading system. Niu Tongxin and others designed and implemented a wireless meter reading system based on Ad-hoc network. The wireless communication module adopts CC1101, and the modulation method is GFSK. The residential micro-power wireless meter reading application scheme developed by Liu Lei et al. is based on the Ad-hoc network, and the modulation method of the wireless communication module is GFSK. These studies mainly focus on reducing the transmission power of nodes, detecting abnormal nodes, etc., but the intelligence and coordination of the nodes themselves are not considered, the receiving sensitivity is not good, and the meter reading speed is slow.

At present, domestic and foreign wireless water meter reading network technologies include WIFI, HomeRF, Bluetooth BLE4.0, Zigbee, GPRS, micro-power wireless network, and low-power wide-area network (LPWAN). WIFI, HomeRF, Bluetooth, etc. are not widely used in domestic water meter collection. Internationally, Zigbee communication technology is more widely used. In 2007, 270,000 residents of Gothenburg, Sweden realized the automatic meter reading system of Zigbee technology. However, Zigbee's implementation cost, low power consumption, alliance agreement and other characteristics are not fully suitable for domestic needs, and are hardly deployed in domestic applications. There are many solutions based on GPRS meter reading technology in China, and the applications are also relatively extensive, which will be limited to the operator's base station and traffic costs. There are many applications of domestic water meter reading and collection of micro-power wireless network, and there are many related documents, such as Li Dong's design of wireless ad hoc network meter reading system based on si4432, Xiong Bangmao's application and research based on 433M routing algorithm in meter reading system, etc. Using FSK, GFSK two modulation methods. With the rise of the Internet of Things, low-power wide-area networks (LPWAN) have emerged, and NB-IoT and LoRa are among the best. NB-IoT is currently not commercialized, and domestic research is very hot. The LoRa network has been piloted or deployed in many places abroad, but LoRa is rarely used in China, and even less in the centralized reading of water meters. Only Wang Rui's SX1278-based wireless meter reading controller for water meters is the only relevant domestic literature.

SUMMARY OF THE INVENTION

In view of this, the purpose of the present invention is to provide an Ad hoc network water meter centralized reading system and method based on multi-agent construction, provide a basic Internet of Things perception layer for smart water affairs, and provide accurate water affairs data for water affairs management. Obtain available information such as water quality to achieve water and energy savings.

To achieve the above object, the present invention adopts the following technical solutions:

An Ad hoc network water meter centralized reading system based on multi-agent construction. The system is divided into three levels, including three different agents: a collector agent, a concentrator agent, and a management center agent; the collector agent is connected to a water meter sensor, The readings of the water meters are collected in real time; the concentrator Agent is responsible for managing the work of a plurality of collector agents, and is used for summarizing the data of the collector agents or issuing instructions to the collectors to control their running states; the management center agent manages several A concentrator agent node, summarizes the data of each concentrator agent node, and issues commands to the collector agent under it through the concentrator agent node.

Further, an Ad hoc network is formed between the concentrator Agent and several collector Agents it manages, and any node in the network can forward packets as a route for other nodes.

Further, the Ad hoc network protocol is designed based on an on-demand protocol, and includes four basic messages: concentrator Agent broadcast message, route request broadcast message, route response broadcast message, and route error message.

Further, the concentrator Agent and several collector agents managed by it also have the ability to perceive the network topology and determine the data transmission path.

Further, the collector Agent includes a PIC microcontroller, a power supply module, a LoRa wireless communication module, an FMCOS-SE safety module, and a pulse measurement sensor module; the PIC microcontroller, the LoRa wireless communication module, the FMCOS-SE safety module, and the pulse measurement sensor module. The metering sensor modules are respectively connected; the power supply module and the Agent include a PIC microcontroller, a LoRa wireless communication module, and an FMCOS-SE security module, which are respectively connected.

Further, described concentrator Agent comprises mainboard module, LoRa wireless communication module, 4G communication module, power supply module and FMCOS-SE security module; Described mainboard module and LoRa wireless communication module, 4G communication module, FMCOS-SE security module. The modules are respectively connected; the power module and the motherboard module are respectively connected with the LoRa wireless communication module and the 4G communication module.

A method for building a multi-Agent network of an Ad hoc network water meter centralized reading system based on multi-Agent construction, comprising the following steps:

Step 1: The concentrator Agent that is not connected to the network actively initiates a network access request to the concentrator Agent;

Step 2: The request reaches the concentrator node directly or routes to the concentrator agent through multiple nodes in the network;

Step 3: After confirming the network access request, the concentrator Agent sends basic system parameters to it;

Step 4: After receiving the basic parameters of the system, the collector Agent will update the configuration of its own node, respond to the concentrator, and complete the network access;

Step 5: The concentrator agent accesses the management center agent to register and obtain the system configuration when it is started for the first time.

Further, the basic system parameters include a time point and an interval allocated to the node to initiate data uploading.

A multi-agent communication coordination method for an Ad hoc network water meter centralized reading system constructed based on multiple agents, comprising the following steps:

Step 1: The collector agent uploads data to the concentrator agent according to the determined time interval based on the upload time point determined when accessing the network;

Step 2: The concentrator agent caches the data sent by the collector agent in the local storage;

Step 3: The concentrator Agent sends a communication request to the management center Agent;

Step 4: When the management center agent receives the request of the concentrator agent, it will check whether there is a task not assigned to the agent in the task queue; if there is, it will issue the corresponding task in the response;

Step 5: When the concentrator Agent receives the task, it will actively contact the collector Agent node that should actually execute the task, and issue the task.

Further, the communication between the concentrator Agent and the management center agent has two modes: real-time and non-real-time; in the real-time mode, the concentrator agent will immediately receive the data sent by the collector agent or meet a certain time interval. Initiate communication with the management center and submit the data to the management center; in non-real-time mode, the concentrator Agent only initiates communication at fixed time intervals.

Compared with the prior art, the present invention has the following beneficial effects:

The present invention provides a basic IoT perception layer for smart water affairs, provides accurate water affairs data for water affairs management, quickly obtains all available information such as water quality at any time, achieves water-saving and energy-saving goals, and better manages water supply and drainage facilities all over the place , to improve the efficiency of operation and maintenance management.

Description of drawings

Fig. 1 is the system schematic diagram of the present invention;

2 is a schematic structural diagram of a collector Agent in an embodiment of the present invention;

3 is a schematic structural diagram of a concentrator Agent in an embodiment of the present invention;

4 is a schematic structural diagram of a security module in an embodiment of the present invention;

5 is a schematic diagram of a communication coordination flow between multiple agents in an embodiment of the present invention;

FIG. 6 is a schematic diagram of an address broadcasting method in an embodiment of the present invention;

7 is a schematic diagram of a new node E joining an existing network in an embodiment of the present invention;

FIG. 8 is a schematic diagram of a routing response in an embodiment of the present invention.

Detailed ways

The present invention will be further described below with reference to the accompanying drawings and embodiments.

Referring to FIG. 1, the present invention provides an Ad hoc network water meter centralized reading system based on multi-agent construction. The system is divided into three levels, including three different agents: collector agent, concentrator agent, and management center agent; The collector Agent is connected with the water meter sensor, and collects the readings of the water meter in real time; the concentrator Agent is responsible for managing the work of multiple collector agents, and is used for summarizing the data of the collector agent or issuing instructions to the collector to control its running state The management center Agent manages several concentrator Agent nodes, summarizes the data of each concentrator Agent node, and issues commands to the collector Agent under it via the concentrator Agent node.

In this embodiment, an Ad hoc network is formed between the collector Agent and the concentrator Agent. Although the concentrator agent is logically the central node of several collector agents, it is not necessary for the concentrator agent to communicate directly with the collector agent. Any node in the network can forward packets as a route for other nodes. The water meter data collected by the collector agent can be transmitted to the corresponding concentrator agent through multi-hop, and the control instructions of the concentrator agent can also reach a collector agent through multi-hop.

Preferably, the Ad hoc network protocol is designed based on an on-demand protocol, and includes four basic messages: concentrator Agent broadcast message, route request broadcast message, route response broadcast message, and route error message

Table 1 shows the broadcast message format of the concentrator Agent. The concentrator agent uses this type of message to broadcast the address to the collector agent node. The fields of the message are described as follows:

Table 1

①Version number: The version number of the currently used protocol

②Type: message type

③TTL: The number of hops that the packet survives. Each time a packet is forwarded by a route, the TTL is -1. When the TTL is 0, the packet is invalid.

④ Hop count: The number of hops the packet passes through

⑤ Via node address: the address of the current node via which the broadcast message is passed

⑥Concentrator Agent source node address: the address of the concentrator Agent node that sends out the broadcast

⑦Broadcast serial number: broadcast serial number maintained by the source

Table 2 shows the routing request protocol message. During communication, when the source node cannot find the destination node in the routing table, it broadcasts a routing request message to the adjacent nodes to establish a forwarding path to the destination. The fields of the routing request message are described as follows:

Table 2

① Via node address: The routing request message is currently via the node address

②Source node address: The address of the node that initiates the routing request

③ Source node serial number: Because of the serial number maintained by the source node, it indicates the new and old of the request

④Destination node address: The address of the destination node

⑤Destination node serial number: The serial number maintained by the destination node, indicating the new and old of the response.

Table 3 shows the route response message. The destination node in the routing request responds to the routing request with a routing response message. The fields of the routing request message are described as follows:

table 3

①

② Via node address: The route response message is currently via the node address

③ Forwarding node address: Specify which node the message is to be forwarded by

④Source node address: The address of the node sending the routing response message

⑤ Source node serial number: The serial number maintained by the source node, indicating the new and old of the response.

⑥Destination node address: The destination node address of the routing response message

Table 4 shows the routing error message. The route error message is used to broadcast the connection abnormal node to the network. The field descriptions of the routing error message are as follows:

Table 4

① Via node address: The address of the node that the routing error message is currently passing through

②Number of error nodes: the number of error nodes contained in the message

③ Error node address n: the address of the nth node with a connection error

④ Error node sequence number n: When an error occurs, the sequence number of the error node in the routing table cache.

In this embodiment, the collector agent and the concentrator agent also have the ability to perceive the network topology and determine the data transmission path. The communication between the concentrator Agent and the management center Agent is carried out via the 4G network using the HTTP protocol. When the concentrator agent submits a data request, it will submit the data to the corresponding HTTP API of the management center.

Referring to FIG. 2, in this embodiment, the collector Agent includes a PIC microcontroller, a power supply module, a LoRa wireless communication module, an FMCOS-SE security module, and a pulse measurement sensor module; the PIC microcontroller and the LoRa wireless communication module, FMCOS-SE The security module and the pulse metering sensor module are respectively connected; the power supply module and the Agent include a PIC microcontroller, a LoRa wireless communication module, and an FMCOS-SE security module, which are respectively connected.

Preferably, the microcontroller of the collector Agent is a PIC24FJ128GA308 16-bit low-power microcontroller from Microchip. The hardware module is responsible for sensor data reading, control signal output, data storage and communication. The microcontroller has a 16x16 hardware multiplier and a 32x16 hardware divider, which facilitates the processing of water meter data. At the same time, the current consumption of the microcontroller during sleep is 400nA, and it can run for a long time under battery power.

The power switching circuit supports the DC power supply and the dry battery to supply power separately. When the DC power supply and the battery are connected at the same time, the DC power supply is preferred. The storage module and wireless communication module are provided with 3.3V power input by two separate HT7333 low dropout linear regulators. The on-off of the control circuit is controlled by a MOS field effect transistor switch.

The LoRa wireless communication module uses Semtech's SX1278 LoRa wireless module. This module is a long-distance low-power wireless communication module. It adopts spread spectrum technology and has the characteristics of long communication distance, high receiving sensitivity and low power consumption. The typical current consumption is 0.2uA when sleeping, 10mA when receiving, and 2mA when transmitting with 7dm transmit power. The maximum transmission distance in the city is about 3 kilometers, which is suitable for long-distance low-power data transmission.

FMCOS-SE security module is a security module developed based on FM1280 chip, using ARM 32-bit security CPU, and equipped with a dedicated operating system. The FMSE security module encrypts some sensitive data related to the water meter, such as user password, user ID, card authentication data, stepped water price, water meter reading, valve control status, device root key and other data. The encryption algorithm used is SM4 security supported by FMSE. Encryption Algorithm.

Referring to FIG. 3 , in this embodiment, the concentrator Agent hardware is mainly based on the S3C6410 development board, and the development board is connected to the 4G communication module using the SPI interface and the USB interface wireless communication module respectively. The concentrator Agent obtains the FMCOS-SE encrypted system information, water meter information, valves, etc. transmitted by the collector Agent through the LoRa wireless module, and uploads it to the server through the 4G communication module. Encryption and decryption of data is performed by the server.

Preferably, in this implementation, the concentrator Agent processor uses Samsung S3C6410 processor. It is a core based on ARM1176JZF-S, including 16KB instruction data cache and 16KB instruction data TCM. The power supply on the agent board of the concentrator is provided by the DC power supply.

In this implementation, the concentrator Agent adopts U8300C 4G wireless module, which is suitable for wireless terminal products of FDD-LTE/TDD-LTE/TD-SCDMA/UMTS/EVDO/EDGE/GPRS/GSM/CDMA various network standards and GPS positioning services , Under the FDD-LTE network, the access speed of U8300C can reach 100Mbps downlink and 50Mbps uplink. Under the TDD-LTE network, the access speed of U8300C can reach 61Mbps downlink and 18Mbps uplink. In this case, U8300C can also be accessed through TD-SCDMA, with a rate of 4.2Mbps downlink and 2.2Mbps uplink, through UMTS access, the rate can reach 42Mbps downlink and 5.76Mbps uplink, and through EVDO access, the rate can reach 14.7Mbps downlink And uplink 5.4Mbps, EGDE access rate can reach 237kbps, GPRS access rate can reach 85.6kbps. GPS can support 55 channels, the tracking and navigation receiving sensitivity reaches -161dBm, the cold start time is within 32S, and the hot start time is within 1S. While providing high-speed data access and GPS positioning services, U8300C can provide functions such as SMS and address book, and can be widely used in mobile broadband access, video surveillance, handheld terminals, vehicle-mounted equipment and other products. The system uses the serial port UART of the ARM embedded system S3C6410 to complete the control of the U8300C 4G module. The 4G module is reset by driving the transistor S8050 through the S3C6410 GPIO pin. The concentrator Agent transmits user information, channel information, water meter dial data, valve control data and other related data to the background database through the U8300C 4G wireless module to realize the centralized management and monitoring of multiple concentrator agents.

In this embodiment, according to the characteristics of LoRa hardware and the actual application scenario, the communication protocol between the collector Agent and the concentrator Agent is designed. The communication between the collector Agent, the concentrator Agent and the server/handheld terminal is in the form of data packets. A complete command packet consists of the start identification unit, packet length, command 1, command 2, command 3, command unit and check unit terminator, see Table 5

Table 1 General format of server, concentrator and collector information exchange command package

command 1

On behalf of the source device 53H (V) on behalf of the server

57H(W) stands for Handheld Terminal/Bluetooth

55H (U) stands for serial debugger

52H(R) stands for collector

4DH(M) stands for Concentrator

command 2

On behalf of the terminal equipment 53H (V) on behalf of the server side

57H(W) stands for Handheld Terminal/Bluetooth

55H (U) stands for serial debugger

52H(R) stands for collector

4DH(M) stands for Concentrator

Command 3

This command includes up to 100 commands including querying the collector agent information, serial port setting, water meter information and valve information setting, Ad-Hoc network channel type and frequency setting.

Check unit

a) Check the "command data" in the protocol. From the first byte of "command 1" to the last byte of the data area;

b) Using a 16-bit CRC check polynomial x ¹⁶ +x ² +1 (0x8005), generate a 2-byte CRC checksum (high byte in the back, low byte in the front);

c) The sender shall generate a two-byte CRC checksum according to the "command unit", and the receiver shall generate a new CRC checksum according to the "command unit" after receiving the complete data packet;

d) The new CRC checksum is equal to the received checksum, indicating that the packet is valid.

Referring to Figure 4, in this embodiment, the security module is a dedicated security encryption chip designed based on the requirements of the ISO7816 specification, which supports the meter to realize the security protection of sensitive data; the security module contains a water meter application, and the application directory is MF. The file structure of the security module of the agent agent and the concentrator agent.

In this implementation, a method for forming a multi-Agent network of an Ad hoc network water meter centralized reading system based on a multi-Agent construction is also provided, comprising the following steps:

Step 1: The concentrator Agent that is not connected to the network actively initiates a network access request to the concentrator Agent;

Step 2: The request reaches the concentrator node directly or routes to the concentrator agent through multiple nodes in the network;

Step 3: After confirming the network access request, the concentrator Agent sends basic system parameters to it;

Step 4: After receiving the basic parameters of the system, the collector Agent will update the configuration of its own node, respond to the concentrator, and complete the network access;

Step 5: The concentrator agent accesses the management center agent to register and obtain the system configuration when it is started for the first time.

Preferably, the basic system parameters include a time point and an interval allocated to the node to initiate data uploading. Different upload time points are used to avoid network congestion caused by simultaneous uploading by multiple collector agents, and different time intervals affect the real-time performance and power consumption of data. The shorter the data upload time interval, the better the real-time performance of the data, but the higher the communication frequency, the higher the average power consumption, and the shorter the battery life; on the contrary, the longer the data upload time interval, the more real-time data. Poor, but the lower the average power consumption, the longer the battery life.

Referring to FIG. 5, in this implementation, a multi-agent communication coordination method based on an Ad hoc network water meter centralized reading system constructed by multiple agents is also provided, including the following steps:

Step 1: The collector agent uploads data to the concentrator agent according to the determined time interval based on the upload time point determined when accessing the network;

Step 2: The concentrator agent caches the data sent by the collector agent in the local storage;

Step 3: The concentrator Agent sends a communication request to the management center Agent;

Step 4: When the management center agent receives the request of the concentrator agent, it will check whether there is a task not assigned to the agent in the task queue; if there is, it will issue the corresponding task in the response;

Step 5: When the concentrator Agent receives the task, it will actively contact the collector Agent node that should actually execute the task, and issue the task.

Preferably, the communication between the agent of the concentrator and the agent of the management center has two modes of real-time and non-real-time; in the real-time mode, the agent of the concentrator will immediately receive the data sent by the agent of the collector or meet a certain time interval. Initiate communication with the management center and submit the data to the management center; in non-real-time mode, the concentrator Agent only initiates communication at fixed time intervals.

In this embodiment, each node maintains a routing table as shown in Table 6. The routing table contains the address of the next node to pass through to reach a node and the number of hops required to reach the node. The serial number field represents the newness of the data, and is mainly used for route update and loop avoidance. There are three ways for a node to discover routes to other nodes: address broadcast, passive acquisition, and on-demand request. Among them, the address broadcast mode can only be initiated by the concentrator Agent, which is mainly used to convey its own route to the reachable nodes in the network in the early stage of network establishment. When using address broadcast, the concentrator Agent will broadcast its own address to adjacent nodes, and the node receiving the broadcast will update its routing table and forward the broadcast packet to its adjacent nodes in the form of flooding The routing information of the concentrator Agent is communicated to all reachable nodes in the network. After the address broadcast is completed, the initial node when the network is established will establish a routing entry to reach the concentrator Agent node. Passive acquisition means that a node acquires a route to a node in the reverse direction during the communication process. Suppose a new collector Agent node A obtains the route to the concentrator Agent node C by requesting on demand, but at this time, node C does not know the route of node A. When node A sends a data packet to node C via node B routing, node C adds node B to the routing entry leading to node A. Before any node sends data to a node that is not recorded in the routing table, it will use the request-on-demand method to request the route to the destination from the adjacent node. This method is usually used when a new network node initiates communication with the concentrator agent and a node is unreachable due to a network failure, and other nodes need to update the routing table. The detailed steps of the address broadcast mode and the on-demand request mode will be described below.

Table 6

destination node address next hop address Hop count destination node number 0x00000001 0x00000004 3 3

1.1.1 Address broadcast mode

(1) Broadcast initiation

The broadcast message initiated by the concentrator Agent contains three elements of <via address, source address, source sequence number>. The address of the concentrator Agent is filled in via the address and the source address, and the source serial number is filled in a group of incremental serial numbers maintained by the concentrator that initiates the broadcast to identify the new and old of the broadcast message. Fill in the TTL according to the scale of the broadcast, and set the hop count to 0.

(2) Broadcast reception

After the adjacent node receives the concentrator Agent broadcast message, it first checks whether the TTL is greater than 0. If it is greater than 0, it continues to check whether the concentrator Agent node address in the broadcast message is equal to the address of the concentrator to which it belongs. If they are equal, check whether there is a route to the concentrator node in the routing table. If the routing table satisfies one of the following conditions: ① It does not contain the route of the node ② The sequence number of the node in the routing table is smaller than the sequence number in the packet ③ The sequence number of the node in the routing table is equal to the sequence number in the packet, and the hop count is greater than that in the packet If the number of hops in the message is reached, the routing table is updated and the message is forwarded.

(3) Routing table update:

Fill the source node address and source node serial number in the received message into the destination node address and destination node serial number fields respectively, fill in the next hop address field in the message via the node field, and add one hop count in the message, Fill in the Jump Number field.

(4) Message forwarding:

When forwarding a packet, fill in the address of the node into the via node field, subtract 1 from the TTL, and add 1 to the hop count.

As shown in Figure 6, the solid node is the concentrator Agent, and the address is D, and the hollow node is the collector agent, and the addresses are A, B, and C, respectively. Nodes directly connected by solid lines are adjacent reachable nodes. In the figure, the three nodes A, B, and C are adjacent, C and D are adjacent, and A, B and D are not adjacent. The address broadcast is initiated by the concentrator Agent node D, and the broadcast sequence number is 1. The arrow in the figure represents the propagation path of the address broadcast, and the address broadcast sent by A and B is omitted in the figure. When the broadcast is communicated to all reachable nodes in the network, each node caches the next-hop path to D in the routing table. The C node can directly transmit the data to the D node, while the A and B nodes will transfer the data to the C node, and the C node transfers it to the D node. After the broadcast is completed, node D does not know the existence of other nodes. Only when other nodes initiate communication to node D, node D can establish a reverse route by passive acquisition.

In this embodiment, the on-demand request mode specifically includes the following:

(1) Initiate a routing request

The routing request message contains five elements of <via node address, source node address, source node sequence number, destination node address, destination node sequence number>. The node that initiates the routing request fills in the source node address and via node address fields with the address of this node, the destination node address in the destination node address field, and the self-incrementing sequence number maintained by the node in the source node sequence number field. The destination node field is filled with the latest sequence number of the known destination node. If the destination node has never been found by this node, fill in -1.

(2) Processing of routing requests

The node that receives the routing request message first judges whether the TTL of the message is 0. If it is not 0, it continues to judge whether the message is sent by this node; Node address, source node sequence number> request, if not, check whether there is a record in the node routing table with the sequence number greater than the destination node sequence number in the message, if so, send a routing response message, if not, start the timer, and Create a routing record in the routing table with the source node in the packet as the destination node, fill in the next hop address field with the via node address, add 1 to the hop number field in the packet, fill in the hop number field, and set the source node The serial number is filled in the serial number field of the destination node. After completing the routing table, the node fills its own sequence number into the via node field of the received message, subtracts 1 from the TTL, adds 1 to the hop count, and forwards the message.

(3) Initiate a routing response

When a node receives a valid routing request message, if the node is the destination of the request or there is a routing record of the requesting node in the routing table of the node, and the node serial number in the record is greater than the serial number in the request message, it will send a routing response message. The node that sends the response fills the destination address and sequence number in the request message into the source node address and sequence number fields in the routing response message, fills in the node's own address in the via node address field, and fills in the hop count into the hop number field. The originating node address of the routing request message is filled in the destination node address field, the via node address is filled in the forwarding node field, the source node address is filled in the destination node address field, and the TTL value is reset.

(4) Processing of routing responses

The node that receives the routing response message checks whether the TTL value in the message is 0. If it is not 0, it continues to check whether the current node matches the destination node in the message. If it matches, and the sequence number of the source node in the message is greater than the sequence number of the node in the routing table, the source node address, source node sequence number, and via node address in the response message are respectively updated into the destination node address and destination node of the routing table. Serial number, next hop address field, and add 1 to the hop number to fill in the hop number field. If the destination node address of the received message does not match the current node address, check whether the node's own address matches the forwarding node field in the message. If it matches, update the routing table and match the destination address in the routing table. The next hop node address of the routing item is filled in the forwarding node address field, the self address is filled in the via node field, the hop count and the TTL are subtracted by 1, and then the response message is forwarded.

As shown in Figure 7, the new node E joins the existing network. Among them, A, B, C, D are the nodes in the existing Agent network. After a certain period of operation, A, B, C, and D have all learned the next hop routes to other nodes in the network. In the figure, only the routing tables of nodes A and B directly connected to E are listed. Node E broadcasts a routing request for Node D to neighboring nodes. Since node E does not know anything about node D, the sequence number of the destination node in the sent request message is -1.

As shown in Figure 8, since both the routing tables of A and B have routing entries reaching D, and the sequence numbers are both greater than -1, both A and B will initiate routing responses to E. Since the number of hops to reach D in the routing tables of A and B is 2, and the last known node D stored in the routing table needs to be the same, node E will update the information in the response packet that arrives first into the routing table , ignoring information in later arriving packets.

The above descriptions are only preferred embodiments of the present invention, and all equivalent changes and modifications made according to the scope of the patent application of the present invention shall fall within the scope of the present invention.

Claims (10)

1. A system for centralized reading of Ad hoc network water meters constructed based on multiple agents is characterized by being divided into three levels, wherein the system comprises three different agents, namely a collector Agent, a concentrator Agent and a management center Agent; the collector Agent is connected with the water meter sensor and collects the reading of the water meter in real time; the concentrator Agent is responsible for managing the work of a plurality of collector agents and is used for summarizing the data of the collector agents or issuing instructions to the collectors to control the running state of the collectors; the management center Agent manages a plurality of concentrator Agent nodes, collects data of each concentrator Agent node, and issues commands to the collector agents under the concentrator Agent nodes.

2. The Ad hoc network water meter centralized meter reading system constructed based on multiple agents according to claim 1, wherein an Ad hoc network is formed between the concentrator Agent and a plurality of collector agents managed by the concentrator Agent, and any node in the network can forward messages as a route for other nodes.

3. The Ad hoc network water meter centralized meter reading system constructed based on multiple agents according to claim 2, wherein the Ad hoc network protocol is designed based on an on-demand protocol, and comprises four basic messages: the concentrator Agent broadcasts messages, routing request broadcast messages, routing response broadcast messages and routing error messages.

4. The Ad hoc network water meter centralized meter reading system constructed based on multiple agents according to claim 1, wherein a sensing network topology is further provided between the concentrator Agent and a plurality of collector agents managed by the concentrator Agent, and the ability of determining a data transmission path is determined.

5. The Ad hoc network water meter centralized meter reading system constructed based on multiple agents according to claim 1, wherein the collector Agent comprises a PIC single chip microcomputer, a power module, a LoRa wireless communication module, a FMCOS-SE safety module and a pulse metering sensor module; the PIC singlechip is connected with the LoRa wireless communication module, the FMCOS-SE safety module and the pulse metering sensor module respectively; the power module and the Agent comprise a PIC single chip microcomputer, and the LoRa wireless communication module and the FMCOS-SE safety module are respectively connected.

6. The Ad hoc network water meter centralized meter reading system constructed based on multiple agents according to claim 1, wherein the concentrator Agent comprises a mainboard module, a LoRa wireless communication module, a 4G communication module, a power module and a FMCOS-SE security module; the main board module is respectively connected with the LoRa wireless communication module, the 4G communication module and the FMCOS-SE safety module; the power module is connected with the main board module, the LoRa wireless communication module and the 4G communication module respectively.

7. A multi-Agent network construction method of an Ad hoc network water meter centralized reading system based on multi-Agent construction is characterized by comprising the following steps:

step 1: the concentrator Agent which is not accessed to the network actively initiates a network access request to the concentrator Agent;

step 2: the request directly reaches the concentrator node or reaches the concentrator Agent through a plurality of node routes in the network;

and step 3: after confirming the network access request, the concentrator Agent issues basic system parameters to the network access request;

and 4, step 4: after receiving the basic parameters of the system, the collector Agent updates the configuration of the node per se, responds to the concentrator and completes network access;

and 5: the concentrator Agent is accessed to the management center Agent for registration and system configuration acquisition when the concentrator Agent is started for the first time.

8. The method for establishing the multi-Agent network of the Ad hoc network water meter centralized meter reading system based on the multi-Agent construction of claim 7, wherein the basic system parameters comprise time points and intervals allocated to the nodes to initiate data uploading.

9. A multi-Agent communication coordination method of an Ad hoc network water meter centralized reading system constructed based on multiple agents is characterized by comprising the following steps:

step 1: the collector Agent uploads data to the concentrator Agent according to a determined time interval by taking an uploading time point determined during network access as a reference;

step 2: the concentrator Agent caches the data transmitted by the collector Agent in a local storage;

and step 3: the concentrator Agent sends a communication request to the management center Agent;

and 4, step 4: when receiving a request of a concentrator Agent, a management center Agent checks whether a task which is not assigned to the Agent exists in a task queue; if yes, issuing corresponding tasks in the response;

and 5: when receiving the task, the concentrator Agent actively contacts the collector Agent node which actually executes the task and issues the task.

10. The method for coordinating communication among the agents of the Ad hoc network water meter centralized reading system constructed based on the agents as claimed in claim 9, wherein the communication between the concentrator Agent and the Agent of the management center has two modes of real time and non-real time; in a real-time mode, the concentrator Agent immediately initiates communication with the management center when receiving data sent by the collector Agent or meeting a certain time interval, and submits the data to the management center; in non-real time mode, the concentrator Agent initiates communication only at fixed time intervals.

Images