CN107547173B - Cloud-based internet of things multimedia data communication method - Google Patents
Cloud-based internet of things multimedia data communication method Download PDFInfo
- Publication number
- CN107547173B CN107547173B CN201710750761.2A CN201710750761A CN107547173B CN 107547173 B CN107547173 B CN 107547173B CN 201710750761 A CN201710750761 A CN 201710750761A CN 107547173 B CN107547173 B CN 107547173B
- Authority
- CN
- China
- Prior art keywords
- node
- address
- cloud
- multimedia data
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a cloud-based internet of things multimedia data communication method, wherein the internet of things comprises two nodes, namely an infrastructure node and an equipment node; the infrastructure nodes comprise access routers, switches and access nodes and are used for realizing the routing forwarding function; the device nodes are used for sensing and collecting data related to the geographic position and converting the data into a multimedia data form, and the device nodes do not have a route forwarding function. The user can quickly realize multimedia data communication and improve the service quality by the method, and the method can be widely applied to the fields of environment monitoring, road traffic management and the like.
Description
Technical Field
The invention relates to a data communication method, in particular to a cloud-based internet of things multimedia data communication method.
Background
The current internet of things architecture has the following disadvantages:
1) a user can only obtain target object information through a database server and cannot realize direct site-to-site communication with a target object;
2) the user can only inquire the information of the target object and cannot directly control the state of the target object;
3) the target object information can only be passively read by a reader-writer, and the target object cannot actively request data updating or send alarm information according to the current state.
Disclosure of Invention
The purpose of the invention is as follows: the invention aims to solve the technical problem of providing a cloud-based internet of things multimedia data communication method aiming at the defects of the prior art
The technical scheme is as follows: the invention discloses a cloud-based internet of things multimedia data communication method, wherein the internet of things comprises two nodes, namely an infrastructure node and an equipment node; the infrastructure nodes comprise access routers, switches and access nodes and are used for realizing the routing forwarding function; the device nodes are used for sensing and collecting data related to the geographic position and converting the data into a multimedia data form, such as video, and do not have a route forwarding function; the access node and the equipment node are provided with a wireless interface, the equipment node and the access node communicate through the wireless interface, at the same time, the equipment node can only communicate with one access node, and the access node is called as an associated access node of the equipment node; the Internet of things is composed of more than two subnets, one subnet comprises an access router, more than two switches, more than two access nodes and equipment nodes related to the access nodes, and the subnets are connected with the Internet through the access router; the topological structure of the infrastructure nodes of one subnet is a tree structure, the root node is an access router, the middle node is a switch, and the leaf nodes are access nodes; the equipment associated with one access node constructs an Internet of things cloud, cloud members in the Internet of things cloud can cooperate with each other to jointly generate multimedia data related to one geographic position, such as videos of a shopping mall, a user can obtain the videos through the Internet to judge whether the shopping mall is crowded or not, and the equipment can serve as the cloud members to provide the multimedia data and can also serve as a user request to obtain the multimedia data;
a user acquires multimedia data related to a geographic position through a cloud address and a unicast address; the cloud address is composed of a network prefix, a link prefix, a data ID and a cloud address identifier, wherein the network prefix uniquely identifies one subnet, the link prefix uniquely identifies an infrastructure node in one subnet, and the data ID uniquely identifies one multimedia data type, such as a picture, audio or video; the network prefix, the link prefix and the data ID uniquely identify one multimedia data related to the geographic location; the cloud address identifier is used for identifying that the address is a cloud address or a unicast address, if the cloud address identifier is 1, the address is indicated to be the cloud address, and if the cloud address identifier is 0, the address is indicated to be the unicast address; a cloud is uniquely identified by a cloud address;
the unicast address is composed of a network prefix, a link prefix, a device ID and a cloud address identifier, wherein the network prefix uniquely identifies one subnet, the link prefix uniquely identifies an infrastructure node in one subnet, the device ID of the access router is 1, the device IDs of the switch and the access node are 0, and the device ID of the device node is a hardware ID, such as an MAC address; the cloud address identifier value is 0, which indicates that the address is a unicast address;
link prefix partitioningLevel, where parameter i is the bit length of the link prefixThe parameter c is a bit length representing one level; the link prefix of the access router is 0, and the network prefix is preset, such as 3efc:1:1: 1/64; one subnet realizes the configuration of the link prefix through the following processes:
step 101: starting;
step 102: the access router sends a link prefix configuration message from each interface f meeting the condition 1, the source address of the link prefix configuration message is a unicast address of the access router, the destination address is 0, the load is a parameter c, a parameter i, a parameter f and a parameter h, the initial value of the parameter h is 0, the maximum value range of the parameter h is the maximum depth of the tree-shaped topological structure of the subnet, and the value (h +1) refers to the depth value of the tree-shaped structure of the infrastructure node receiving the link prefix configuration message;
condition 1: the interface is connected to an infrastructure node;
step 103: after receiving the link prefix configuration message, infrastructure nodes connected with the interface meeting the condition 1 construct an i-bit link prefix, wherein the front h & c bit value of the link prefix is the front h & c bit value of the link prefix of the source address of the link prefix configuration message, the next c bit value is an interface f, and finally the i- (h +1) & c bit value is 0;
step 104: if the infrastructure node receiving the link prefix configuration message is a switch, executing step 105, otherwise, executing step 106;
step 105: the switch receiving the link prefix configuration message increments the value of the parameter h by 1, the link prefix configuration message is sent from each interface f meeting the condition 1, the source address of the link prefix configuration message is the unicast address of the switch, the destination address is 0, the load is the parameter c, the parameter i and the parameter h, and step 103 is executed;
step 106: finishing;
after the access node configures the link prefix, regularly sending a beacon message through a wireless interface; after the device node associated with the access node receives the beacon message, it stores the link prefix of the access node.
The above procedure can implement the link prefix configuration of the device to ensure correct communication of multimedia data.
In the method, an infrastructure node maintains an index table for recording information of cloud members, and an index table item comprises an interface domain and a cloud address domain;
a multimedia data MD1 related to geographical location is uniquely identified by a cloud address CA1, under the condition that the cloud address CA1 has a network prefix of GRP1, a link prefix of LRP2, a data ID of CID1 and a cloud identifier of 1, an access node AP2 having a link address of LRP2 creates a multimedia data MD1 by constructing a cloud TC1, and the process is as follows:
step 201: starting;
step 202: the access node AP2 creates a unicast address, the network prefix of the unicast address is 0, the link prefix is LRP2, the equipment ID is 0, the cloud identifier is 0, the access node AP2 sends a message for creating multimedia data from a wireless interface, the source address of the message is the created unicast address, and the destination address is CA 1;
step 203: after receiving the multimedia data creating message, if part of data of the data MD1 can be created, the device node associated with the access node AP2 sends a multimedia data creating response message, where the source address of the multimedia data creating response message is the destination address of the multimedia data creating message, the destination address is the source address of the multimedia data creating message, and the load is the created multimedia data;
step 204: after receiving all the multimedia data creating response messages, the access node AP2 constructs the multimedia data in the multimedia data creating response messages into multimedia data MD1, and then sends multimedia data sharing messages from a wireless interface, wherein the source address of the multimedia data sharing messages is the unicast address created in the step 202, the destination address is CA1, and the load is data MD 1;
step 205: after receiving the message for creating the multimedia data sharing, the device node associated with the access node AP2 stores the data MD1 and identifies itself as a cloud member of the cloud TC1 if there is enough storage space for storing the data MD 1;
step 206: finishing;
after the access node AP2 creates the data MD1, deleting the data MD 1;
after the device node becomes a cloud member of the cloud TC1, the beacon message broadcast by the device node is loaded to the cloud address CA1.
The above process enables multimedia data to be quickly created and provided to a user.
In the method of the present invention, after receiving the beacon message with the load of cloud address CA1 from the interface f1, the access node determines whether there is an index table entry with cloud address domain value CA1 and interface domain value f1 in its index table, and if not, executes the following operations:
step 301: starting;
step 302: the access node creates an index table entry with a cloud address domain value of CA1 and an interface domain value of f1 in an index table, then creates a unicast address of the access node and a unicast address of a father node, wherein in the unicast address of the access node, a network prefix is 0, a link prefix is a link prefix of the access node, a device ID is 0, a cloud identifier is 0, in the unicast address of the father node, the network prefix is 0, the link prefix is a link prefix of the father node, if the father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a beacon message is sent from an interface connected with the father node, the source address of the beacon message is the unicast address of the access node, the destination address is the unicast address of the father node, and the load is the cloud address CA 1;
step 303: after receiving the beacon message with the load of the cloud address CA1 from the interface f2, the father node judges whether an index table entry with a cloud address domain value of CA1 and an interface domain value of f2 exists in the index table of the father node, if so, the step 306 is executed, otherwise, the step 304 is executed;
step 304: the father node creates an index table entry with a cloud address domain value of CA1 and an interface domain value of f2 in an index table, if the father node is an access router, step 306 is executed, otherwise, step 305 is executed;
step 305: a father node creates a self unicast address and a self unicast address of a father node, in the self unicast address, a network prefix is 0, a link prefix is a self link prefix, a device ID is 0, a cloud identifier is 0, in the self unicast address of the father node, the network prefix is 0, the link prefix is a link prefix of the father node, if the self father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a beacon message is sent from an interface connected with the self father node, the source address of the beacon message is a self unicast address, the destination address is a self unicast address of the father node, the load is a cloud address CA1, and the step 303 is executed;
step 306: and (6) ending.
The above process can quickly create the index table to ensure that the user can quickly acquire the multimedia data.
In the method of the invention, if the equipment node is invalid or departs from the communication range of the access node which is currently associated, the access node can not receive the beacon frame sent by the equipment node; if the access node does not receive any beacon message loaded with the cloud address CA1 from the interface f1 within a specified time, for example, 1s, the access node deletes the index table entry with the cloud address domain value of CA1 and the interface domain value of f1 from the index table; if the access node does not have the index table entry with the cloud address domain value of CA1 in the index table, the following cloud retrieval table entry deletion process is executed:
step 401: starting;
step 402: the access node creates a unicast address of the access node and a unicast address of a father node, in the unicast address of the access node, the network prefix is 0, the link prefix is the link prefix of the access node, the device ID is 0, the cloud identifier is 0, in the unicast address of the father node, the network prefix is 0, the link prefix is the link prefix of the father node, if the father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a retrieval table item deletion message is sent from an interface connected with the father node, the source address of the retrieval table item deletion message is the unicast address of the access node, the destination address is the unicast address of the father node, and the load is the cloud address CA 1;
step 403: after receiving a retrieval table item deletion message with the load of cloud address CA1 from an interface f2, the parent node deletes the index table item with the cloud address domain value of CA1 and the interface domain value of f2 from the index table, then judges whether the index table of the parent node has the index table item with the cloud address domain value of CA1, if so, executes step 406, otherwise, executes step 404;
step 404: if the parent node is an access router, executing step 406, otherwise executing step 405;
step 405: a father node creates a self unicast address and a self unicast address of a father node, in the self unicast address, a network prefix is 0, a link prefix is a self link prefix, a device ID is 0, a cloud identifier is 0, in the self unicast address of the father node, the network prefix is 0, the link prefix is a link prefix of the self father node, if the self father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a retrieval table item deleting message is sent from an interface connected with the self father node, the source address of the retrieval table item deleting message is the self unicast address, the destination address is the self unicast address of the father node, the load is a cloud address CA1, and step 403 is executed;
step 406: and (6) ending.
The process can quickly update the index table so as to ensure that the user can quickly and correctly acquire the multimedia data.
In the method, an infrastructure node maintains a request table for recording uncompleted multimedia data request information, and a request table item comprises an interface domain and a cloud address domain;
a multimedia data MD2 associated with a geographical location is uniquely identified by a cloud address CA2, the data MD2 is created by building a cloud TC 2; the device node D1 is located in the subnet S1, the network prefix of the subnet S1 is GRP1, and the device node D1 is associated with the access node AP 1; if the condition 2 or the condition 3 is satisfied, the device node D1 acquires the data MD2 by:
condition 2: the network prefix of the cloud address CA2 is GRP1 and the link prefix is equal to the link prefix of the access node AP 2;
condition 3: the network prefix of the cloud address CA2 is not equal to GRP1, but there is at least one cloud member of cloud TC2 in subnet S1;
step 501: starting;
step 502: the device node D1 creates a unicast address, the network prefix is 0, the link prefix is the link prefix of the access node AP1, the device ID is the device ID of the device node D1, and then sends a multimedia data request message, the source address of the multimedia data request message is the constructed unicast address, and the destination address is the cloud address CA 2;
step 503: judging whether the infrastructure node or the device node receives the multimedia data request message from the interface f3, if the infrastructure node receives the multimedia data request message, executing the step 504, otherwise executing the step 511;
step 504: if the infrastructure node has a request table entry with the cloud address of CA2 and the interface domain value of f3 in the request table, executing step 514, otherwise executing step 505;
step 505: the infrastructure node creates a request table entry with a cloud address of CA2 and an interface domain value of f3 in the request table, if the infrastructure node only has one request table entry with a cloud address of CA2, step 506 is executed, otherwise step 514 is executed;
step 506: if the infrastructure node has at least one index table entry with the cloud address of CA2 in the index table, executing step 507, otherwise executing step 508;
step 507: the infrastructure node randomly selects an index table entry with a cloud address of CA2, forwards the received multimedia data request message from the interface domain of the index table entry, and executes step 503;
step 508: if the infrastructure node is the access node AP2, go to step 509, otherwise go to step 510;
step 509: the access node AP2 executes the steps 201-206 to create the multimedia data MD2, then constructs a multimedia data response message, the load of the multimedia data response message is data MD2, the source address is the destination address of the received multimedia data request message, the destination address is the source address of the received multimedia data request message, and executes the step 514;
step 510: the infrastructure node checks all the child nodes, and if the matching degree of the link prefixes of all the child nodes and the link prefixes of the cloud address CA2 is the same as the matching degree of the link prefixes of the infrastructure node and the cloud address CA2, the multimedia data request message is forwarded from an interface connected with the parent node; otherwise, selecting a child node, wherein the matching degree of the link prefix of the child node and the link prefix of the cloud address CA2 is maximum, and then forwarding the multimedia data request message from an interface connected with the child node; step 503 is executed; the matching degree is judged to be compared from the first bit of the link prefix, and the more the number of continuous identical bits is, the greater the matching degree is;
step 511: if the device node receiving the multimedia data request message is capable of providing the data MD2, perform step 513, otherwise perform step 512;
step 512: the device node receiving the multimedia data request message discards the multimedia data request message, and performs step 514;
step 513: the equipment node receiving the multimedia data request message sends a multimedia data response message, wherein the load of the multimedia data response message is data MD2, the source address is the destination address of the received multimedia data request message, and the destination address is the source address of the received multimedia data request message;
step 514: if the infrastructure node constructs or receives a multimedia data response message, step 515 is performed, otherwise step 516 is performed;
step 515: the infrastructure node looks at the request table, and performs the following operations on each request table entry with the cloud address of CA 2: the infrastructure node forwards the multimedia data response message from the interface field value of the entry, then deletes the request entry, and performs step 514;
step 516: after receiving the multimedia data response message, the device node D1 stores the data MD2 and identifies itself as a cloud member of the cloud TC 2;
517: finishing;
after the device node D1 becomes a cloud member of the cloud TC2, the beacon message broadcast by it is loaded with the cloud address CA 2.
The user can rapidly and correctly acquire the multimedia data through the above process.
In the method of the present invention, a multimedia data MD3 related to a geographic location is uniquely identified by a cloud address CA3, a data MD3 is created by constructing a cloud TC3, an apparatus node D1 is located in a subnet S1, a network prefix of the subnet S1 is GRP1, an access router is AR1, a network prefix is GRP2 in the subnet S2, an access router is AR2, a network prefix is GRP2 in the cloud address CA3, a link prefix domain access node AP4 has the same link prefix, an access node AP4 is located in the subnet S2, and if a condition 4 is satisfied, the apparatus node D1 acquires the data MD3 by the following process under the condition that the apparatus node D1 is associated with the access node AP 1:
condition 4: there are no cloud members of cloud TC3 in subnet S1;
step 601: starting;
step 602: the device node D1 creates a unicast address, the network prefix is 0, the link prefix is the link prefix of the access node AP1, the device ID is the device ID of the device node D1, and then sends a multimedia data request message, the source address of the multimedia data request message is the constructed unicast address, and the destination address is the cloud address CA 3;
step 603: determining whether the infrastructure node or the device node receives the multimedia data request message from the interface f4, if the infrastructure node receives the multimedia data request message, performing step 604, otherwise performing step 614;
step 604: if condition 5 is satisfied or both conditions 6 and 7 are satisfied, then perform step 615, otherwise perform step 605;
condition 5: the infrastructure node has a request table entry with a cloud address of CA3 and an interface domain value of f4 in the request table;
condition 6: the infrastructure node is an access router AR2, and an interface f4 is connected with the Internet;
condition 7: the infrastructure node at least has one request table entry with the cloud address of CA3 in the request table;
condition 8: the infrastructure node does not have any request table entry with the cloud address of CA3 in the request table;
step 605: if conditions 6 and 8 are satisfied, performing step 607, otherwise performing step 606;
step 606: the infrastructure node creates a request table entry with a cloud address of CA3 and an interface domain value of f4 in the request table, if the infrastructure node only has one request table entry with a cloud address of CA3, step 607 is executed, otherwise step 615 is executed;
step 607: if the infrastructure node is located in subnet S1, then step 608 is performed, otherwise step 609 is performed;
step 608: if the infrastructure node is an access router AR1, updating the network prefix of the source address in the multimedia data request message to GRP1, then sending the multimedia data request message to the Internet, and finally reaching the access router AR2 through the Internet multimedia data request message; otherwise, the infrastructure node forwards the multimedia data request message from the interface connected with the father node; step 603 is executed;
step 609: if the infrastructure node has at least one index table entry with the cloud address of CA3 in the index table, executing step 610, otherwise executing step 611;
step 610: the infrastructure node randomly selects an index table entry with a cloud address of CA3, forwards the received multimedia data request message from an interface domain of the index table entry, and executes step 603;
step 611: if the infrastructure node is access node AP4, go to step 612, otherwise go to step 613;
step 612: the access node AP4 executes the steps 201-206 to create the multimedia data MD3, then constructs a multimedia data response message, the load of the multimedia data response message is data MD3, the source address is the destination address of the received multimedia data request message, the destination address is the source address of the received multimedia data request message, and executes the step 615;
step 613: the infrastructure node checks all the child nodes, and if the matching degree of the link prefixes of all the child nodes and the link prefixes of the cloud address CA2 is the same as the matching degree of the link prefixes of the infrastructure node and the cloud address CA2, the multimedia data request message is forwarded from an interface connected with the parent node; otherwise, selecting a child node, wherein the matching degree of the link prefix of the child node and the link prefix of the cloud address CA2 is maximum, and then forwarding the multimedia data request message from an interface connected with the child node; step 603 is executed; the matching degree is judged to be compared from the first bit of the link prefix, and the more the number of continuous identical bits is, the greater the matching degree is;
step 614: if the device node receiving the multimedia data request message can provide the data MD3, sending a multimedia data response message, wherein the load of the multimedia data response message is the data MD3, the source address is the destination address of the received multimedia data request message, and the destination address is the source address of the received multimedia data request message; otherwise, the equipment node receiving the multimedia data request message discards the multimedia data request message;
step 615: if the infrastructure node constructs or receives a multimedia data response message, then step 616 is performed, otherwise step 617 is performed;
step 616: if the infrastructure node is the access router AR2, the multimedia data response message is forwarded to the internet, and finally reaches the access router AR1 through the internet multimedia data response message, otherwise, the infrastructure node looks up the request table and performs the following operations for each request table entry with the cloud address CA 3: the infrastructure node forwards the multimedia data response message from the interface field value of the entry, then deletes the request entry, and performs step 615;
step 617: after receiving the multimedia data response message, the device node D1 stores the data MD2 and identifies itself as a cloud member of the cloud TC 3;
step 618: finishing;
after the device node D1 becomes a cloud member of the cloud TC3, the beacon message broadcast by it is loaded with the cloud address CA 3.
The user can rapidly and correctly acquire the multimedia data through the above process.
Has the advantages that: the invention provides a cloud-based internet of things multimedia data communication method, through which a user can quickly realize multimedia data communication and improve service quality.
Drawings
The foregoing and/or other advantages of the invention will become further apparent from the following detailed description of the invention when taken in conjunction with the accompanying drawings.
Fig. 1 is a schematic diagram illustrating a link prefix configuration flow according to the present invention.
Fig. 2 is a schematic diagram illustrating a process of creating multimedia data according to the present invention.
FIG. 3 is a flow chart of creating an index table according to the present invention.
FIG. 4 is a flow chart illustrating an update index table according to the present invention.
Fig. 5 is a schematic view of a local data acquisition process according to the present invention.
Fig. 6 is a schematic diagram of a remote data acquisition process according to the present invention.
The specific implementation mode is as follows:
the invention provides a cloud-based internet of things multimedia data communication method, through which a user can quickly realize multimedia data communication and improve service quality.
Fig. 1 is a schematic diagram illustrating a link prefix configuration flow according to the present invention. The Internet of things comprises two nodes, namely infrastructure nodes and equipment nodes; the infrastructure nodes comprise access routers, switches and access nodes and are used for realizing the routing forwarding function; the device nodes are used for sensing and collecting data related to the geographic position and converting the data into a multimedia data form, and the device nodes do not have a routing forwarding function; the access node and the equipment node are provided with a wireless interface, the equipment node and the access node communicate through the wireless interface, at the same time, the equipment node can only communicate with one access node, and the access node is called as an associated access node of the equipment node; the Internet of things is composed of more than two subnets, one subnet comprises an access router, more than two switches, more than two access nodes and equipment nodes related to the access nodes, and the subnets are connected with the Internet through the access router; the topological structure of the infrastructure nodes of one subnet is a tree structure, the root node is an access router, the middle node is a switch, and the leaf nodes are access nodes; the equipment associated with one access node constructs an Internet of things cloud, cloud members in the Internet of things cloud can cooperate with each other to jointly generate multimedia data related to one geographical position, and the equipment can serve as the cloud members to provide the multimedia data and can also serve as a user request to acquire the multimedia data;
a user acquires multimedia data related to a geographic position through a cloud address and a unicast address; the cloud address is composed of a network prefix, a link prefix, a data ID and a cloud address identifier, wherein the network prefix uniquely identifies one subnet, the link prefix uniquely identifies an infrastructure node in one subnet, and the data ID uniquely identifies one multimedia data type; the network prefix, the link prefix and the data ID uniquely identify one multimedia data related to the geographic location; the cloud address identifier is used for identifying that the address is a cloud address or a unicast address, if the cloud address identifier is 1, the address is indicated to be the cloud address, and if the cloud address identifier is 0, the address is indicated to be the unicast address; a cloud is uniquely identified by a cloud address;
the unicast address is composed of a network prefix, a link prefix, a device ID and a cloud address identifier, wherein the network prefix uniquely identifies one subnet, the link prefix uniquely identifies an infrastructure node in one subnet, the device ID of the access router is 1, the device IDs of the switch and the access node are 0, and the device ID of the device node is a hardware ID; the cloud address identifier value is 0, which indicates that the address is a unicast address;
link prefix partitioningA plurality of levels, wherein the parameter i is the bit length of the link prefix, and the parameter c is the bit length representing one level; access routingThe link prefix of the device is 0, and the network prefix is preset, such as 3efc:1:1: 1/64; one subnet realizes the configuration of the link prefix through the following processes:
step 101: starting;
step 102: the access router sends a link prefix configuration message from each interface f meeting the condition 1, wherein the source address of the link prefix configuration message is a unicast address of the access router, the destination address of the link prefix configuration message is 0, the load of the link prefix configuration message is a parameter c, a parameter i, a parameter f and a parameter h, and the initial value of the parameter h is 0; the maximum value range of the parameter h is the maximum depth of the tree topology structure of the subnet, and the value (h +1) refers to the depth value of the tree structure where the infrastructure node receiving the link prefix configuration message is located.
Condition 1: the interface is connected to an infrastructure node;
step 103: after receiving the link prefix configuration message, infrastructure nodes connected with the interface meeting the condition 1 construct an i-bit link prefix, wherein the front h & c bit value of the link prefix is the front h & c bit value of the link prefix of the source address of the link prefix configuration message, the next c bit value is an interface f, and finally the i- (h +1) & c bit value is 0;
step 104: if the infrastructure node receiving the link prefix configuration message is a switch, executing step 105, otherwise, executing step 106;
step 105: the switch receiving the link prefix configuration message increments the value of the parameter h by 1, the link prefix configuration message is sent from each interface f meeting the condition 1, the source address of the link prefix configuration message is the unicast address of the switch, the destination address is 0, the load is the parameter c, the parameter i and the parameter h, and step 103 is executed;
step 106: finishing;
after the access node configures the link prefix, regularly sending a beacon message through a wireless interface; after the device node associated with the access node receives the beacon message, it stores the link prefix of the access node.
Fig. 2 is a schematic diagram illustrating a process of creating multimedia data according to the present invention. The infrastructure node maintains an index table for recording information of cloud members, and an index table item comprises an interface domain and a cloud address domain;
a multimedia data MD1 related to geographical location is uniquely identified by a cloud address CA1, under the condition that the cloud address CA1 has a network prefix of GRP1, a link prefix of LRP2, a data ID of CID1 and a cloud identifier of 1, an access node AP2 having a link address of LRP2 creates a multimedia data MD1 by constructing a cloud TC1, and the process is as follows:
step 201: starting;
step 202: the access node AP2 creates a unicast address, the network prefix of the unicast address is 0, the link prefix is LRP2, the equipment ID is 0, the cloud identifier is 0, the access node AP2 sends a message for creating multimedia data from a wireless interface, the source address of the message is the created unicast address, and the destination address is CA 1;
step 203: after receiving the multimedia data creating message, if part of data of the data MD1 can be created, the device node associated with the access node AP2 sends a multimedia data creating response message, where the source address of the multimedia data creating response message is the destination address of the multimedia data creating message, the destination address is the source address of the multimedia data creating message, and the load is the created multimedia data;
step 204: after receiving all the multimedia data creating response messages, the access node AP2 constructs the multimedia data in the multimedia data creating response messages into multimedia data MD1, and then sends multimedia data sharing messages from a wireless interface, wherein the source address of the multimedia data sharing messages is the unicast address created in the step 202, the destination address is CA1, and the load is data MD 1;
step 205: after receiving the message for creating the multimedia data sharing, the device node associated with the access node AP2 stores the data MD1 and identifies itself as a cloud member of the cloud TC1 if there is enough storage space for storing the data MD 1;
step 206: finishing;
after the access node AP2 creates the data MD1, deleting the data MD 1;
after the device node becomes a cloud member of the cloud TC1, the beacon message broadcast by the device node is loaded to the cloud address CA1.
FIG. 3 is a flow chart of creating an index table according to the present invention. If the access node receives the beacon message with the load of the cloud address CA1 from the interface f1, the access node judges whether an index table entry with the cloud address domain value of CA1 and the interface domain value of f1 exists in the index table of the access node, if the index table entry does not exist, the following operations are executed:
step 301: starting;
step 302: the access node creates an index table entry with a cloud address domain value of CA1 and an interface domain value of f1 in an index table, then creates a unicast address of the access node and a unicast address of a father node, wherein in the unicast address of the access node, a network prefix is 0, a link prefix is a link prefix of the access node, a device ID is 0, a cloud identifier is 0, in the unicast address of the father node, the network prefix is 0, the link prefix is a link prefix of the father node, if the father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a beacon message is sent from an interface connected with the father node, the source address of the beacon message is the unicast address of the access node, the destination address is the unicast address of the father node, and the load is the cloud address CA 1;
step 303: after receiving the beacon message with the load of the cloud address CA1 from the interface f2, the father node judges whether an index table entry with a cloud address domain value of CA1 and an interface domain value of f2 exists in the index table of the father node, if so, the step 306 is executed, otherwise, the step 304 is executed;
step 304: the father node creates an index table entry with a cloud address domain value of CA1 and an interface domain value of f2 in an index table, if the father node is an access router, step 306 is executed, otherwise, step 305 is executed;
step 305: a father node creates a self unicast address and a self unicast address of a father node, in the self unicast address, a network prefix is 0, a link prefix is a self link prefix, a device ID is 0, a cloud identifier is 0, in the self unicast address of the father node, the network prefix is 0, the link prefix is a link prefix of the father node, if the self father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a beacon message is sent from an interface connected with the self father node, the source address of the beacon message is a self unicast address, the destination address is a self unicast address of the father node, the load is a cloud address CA1, and the step 303 is executed;
step 306: and (6) ending.
FIG. 4 is a flow chart illustrating an update index table according to the present invention. If the equipment node is invalid or is out of the communication range of the currently associated access node, the access node cannot receive the beacon frame sent by the equipment node; if the access node does not receive any beacon message loaded with the cloud address CA1 from the interface f1 within the specified time, the access node deletes the index table entry with the cloud address domain value of CA1 and the interface domain value of f1 from the index table; if the access node does not have the index table entry with the cloud address domain value of CA1 in the index table, the following cloud retrieval table entry deletion process is executed:
step 401: starting;
step 402: the access node creates a unicast address of the access node and a unicast address of a father node, in the unicast address of the access node, the network prefix is 0, the link prefix is the link prefix of the access node, the device ID is 0, the cloud identifier is 0, in the unicast address of the father node, the network prefix is 0, the link prefix is the link prefix of the father node, if the father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a retrieval table item deletion message is sent from an interface connected with the father node, the source address of the retrieval table item deletion message is the unicast address of the access node, the destination address is the unicast address of the father node, and the load is the cloud address CA 1;
step 403: after receiving a retrieval table item deletion message with the load of cloud address CA1 from an interface f2, the parent node deletes the index table item with the cloud address domain value of CA1 and the interface domain value of f2 from the index table, then judges whether the index table of the parent node has the index table item with the cloud address domain value of CA1, if so, executes step 406, otherwise, executes step 404;
step 404: if the parent node is an access router, executing step 406, otherwise executing step 405;
step 405: a father node creates a self unicast address and a self unicast address of a father node, in the self unicast address, a network prefix is 0, a link prefix is a self link prefix, a device ID is 0, a cloud identifier is 0, in the self unicast address of the father node, the network prefix is 0, the link prefix is a link prefix of the self father node, if the self father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a retrieval table item deleting message is sent from an interface connected with the self father node, the source address of the retrieval table item deleting message is the self unicast address, the destination address is the self unicast address of the father node, the load is a cloud address CA1, and step 403 is executed;
step 406: and (6) ending.
Fig. 5 is a schematic view of a local data acquisition process according to the present invention. The infrastructure node maintains a request table for recording uncompleted multimedia data request information, and the request table comprises an interface domain and a cloud address domain;
a multimedia data MD2 associated with a geographical location is uniquely identified by a cloud address CA2, the data MD2 is created by building a cloud TC 2; the device node D1 is located in the subnet S1, the network prefix of the subnet S1 is GRP1, and the device node D1 is associated with the access node AP 1; if the condition 2 or the condition 3 is satisfied, the device node D1 acquires the data MD2 by:
condition 2: the network prefix of the cloud address CA2 is GRP1 and the link prefix is equal to the link prefix of the access node AP 2;
condition 3: the network prefix of the cloud address CA2 is not equal to GRP1, but there is at least one cloud member of cloud TC2 in subnet S1;
step 501: starting;
step 502: the device node D1 creates a unicast address, the network prefix is 0, the link prefix is the link prefix of the access node AP1, the device ID is the device ID of the device node D1, and then sends a multimedia data request message, the source address of the multimedia data request message is the constructed unicast address, and the destination address is the cloud address CA 2;
step 503: judging whether the infrastructure node or the device node receives the multimedia data request message from the interface f3, if the infrastructure node receives the multimedia data request message, executing the step 504, otherwise executing the step 511;
step 504: if the infrastructure node has a request table entry with the cloud address of CA2 and the interface domain value of f3 in the request table, executing step 514, otherwise executing step 505;
step 505: the infrastructure node creates a request table entry with a cloud address of CA2 and an interface domain value of f3 in the request table, if the infrastructure node only has one request table entry with a cloud address of CA2, step 506 is executed, otherwise step 514 is executed;
step 506: if the infrastructure node has at least one index table entry with the cloud address of CA2 in the index table, executing step 507, otherwise executing step 508;
step 507: the infrastructure node randomly selects an index table entry with a cloud address of CA2, forwards the received multimedia data request message from the interface domain of the index table entry, and executes step 503;
step 508: if the infrastructure node is the access node AP2, go to step 509, otherwise go to step 510;
step 509: the access node AP2 executes the steps 201-206 to create the multimedia data MD2, then constructs a multimedia data response message, the load of the multimedia data response message is data MD2, the source address is the destination address of the received multimedia data request message, the destination address is the source address of the received multimedia data request message, and executes the step 514;
step 510: the infrastructure node checks all the child nodes, and if the matching degree of the link prefixes of all the child nodes and the link prefixes of the cloud address CA2 is the same as the matching degree of the link prefixes of the infrastructure node and the cloud address CA2, the multimedia data request message is forwarded from an interface connected with the parent node; otherwise, selecting a child node, wherein the matching degree of the link prefix of the child node and the link prefix of the cloud address CA2 is maximum, and then forwarding the multimedia data request message from an interface connected with the child node; step 503 is executed; the matching degree is judged to be compared from the first bit of the link prefix, and the more the number of continuous identical bits is, the greater the matching degree is;
step 511: if the device node receiving the multimedia data request message is capable of providing the data MD2, perform step 513, otherwise perform step 512;
step 512: the device node receiving the multimedia data request message discards the multimedia data request message, and performs step 514;
step 513: the equipment node receiving the multimedia data request message sends a multimedia data response message, wherein the load of the multimedia data response message is data MD2, the source address is the destination address of the received multimedia data request message, and the destination address is the source address of the received multimedia data request message;
step 514: if the infrastructure node constructs or receives a multimedia data response message, step 515 is performed, otherwise step 516 is performed;
step 515: the infrastructure node looks at the request table, and performs the following operations on each request table entry with the cloud address of CA 2: the infrastructure node forwards the multimedia data response message from the interface field value of the entry, then deletes the request entry, and performs step 514;
step 516: after receiving the multimedia data response message, the device node D1 stores the data MD2 and identifies itself as a cloud member of the cloud TC 2;
517: finishing;
after the device node D1 becomes a cloud member of the cloud TC2, the beacon message broadcast by it is loaded with the cloud address CA 2.
Fig. 6 is a schematic diagram of a remote data acquisition process according to the present invention. Under the condition that a multimedia data MD3 related to a geographical location is uniquely identified by a cloud address CA3, the data MD3 is created by constructing a cloud TC3, a device node D1 is located in a subnet S1, a network prefix of the subnet S1 is GRP1, an access router is AR1, a subnet S2 is located in a subnet S2, an access router is AR2, a network prefix in the cloud address CA3 is GRP2, link prefixes of link prefix domains and access nodes AP4 are the same, an access node AP4 is located in a subnet S2, and the device node D1 is associated with the access node AP1, if a condition 4 is satisfied, the device node D1 acquires the data MD3 by:
condition 4: there are no cloud members of cloud TC3 in subnet S1;
step 601: starting;
step 602: the device node D1 creates a unicast address, the network prefix is 0, the link prefix is the link prefix of the access node AP1, the device ID is the device ID of the device node D1, and then sends a multimedia data request message, the source address of the multimedia data request message is the constructed unicast address, and the destination address is the cloud address CA 3;
step 603: determining whether the infrastructure node or the device node receives the multimedia data request message from the interface f4, if the infrastructure node receives the multimedia data request message, performing step 604, otherwise performing step 614;
step 604: if condition 5 is satisfied or both conditions 6 and 7 are satisfied, then perform step 615, otherwise perform step 605;
condition 5: the infrastructure node has a request table entry with a cloud address of CA3 and an interface domain value of f4 in the request table;
condition 6: the infrastructure node is an access router AR2, and an interface f4 is connected with the Internet;
condition 7: the infrastructure node at least has one request table entry with the cloud address of CA3 in the request table;
condition 8: the infrastructure node does not have any request table entry with the cloud address of CA3 in the request table;
step 605: if conditions 6 and 8 are satisfied, performing step 607, otherwise performing step 606;
step 606: the infrastructure node creates a request table entry with a cloud address of CA3 and an interface domain value of f4 in the request table, if the infrastructure node only has one request table entry with a cloud address of CA3, step 607 is executed, otherwise step 615 is executed;
step 607: if the infrastructure node is located in subnet S1, then step 608 is performed, otherwise step 609 is performed;
step 608: if the infrastructure node is an access router AR1, updating the network prefix of the source address in the multimedia data request message to GRP1, then sending the multimedia data request message to the Internet, and finally reaching the access router AR2 through the Internet multimedia data request message; otherwise, the infrastructure node forwards the multimedia data request message from the interface connected with the father node; step 603 is executed;
step 609: if the infrastructure node has at least one index table entry with the cloud address of CA3 in the index table, executing step 610, otherwise executing step 611;
step 610: the infrastructure node randomly selects an index table entry with a cloud address of CA3, forwards the received multimedia data request message from an interface domain of the index table entry, and executes step 603;
step 611: if the infrastructure node is access node AP4, go to step 612, otherwise go to step 613;
step 612: the access node AP4 executes the steps 201-206 to create the multimedia data MD3, then constructs a multimedia data response message, the load of the multimedia data response message is data MD3, the source address is the destination address of the received multimedia data request message, the destination address is the source address of the received multimedia data request message, and executes the step 615;
step 613: the infrastructure node checks all the child nodes, and if the matching degree of the link prefixes of all the child nodes and the link prefixes of the cloud address CA2 is the same as the matching degree of the link prefixes of the infrastructure node and the cloud address CA2, the multimedia data request message is forwarded from an interface connected with the parent node; otherwise, selecting a child node, wherein the matching degree of the link prefix of the child node and the link prefix of the cloud address CA2 is maximum, and then forwarding the multimedia data request message from an interface connected with the child node; step 603 is executed; the matching degree is judged to be compared from the first bit of the link prefix, and the more the number of continuous identical bits is, the greater the matching degree is;
step 614: if the device node receiving the multimedia data request message can provide the data MD3, sending a multimedia data response message, wherein the load of the multimedia data response message is the data MD3, the source address is the destination address of the received multimedia data request message, and the destination address is the source address of the received multimedia data request message; otherwise, the equipment node receiving the multimedia data request message discards the multimedia data request message;
step 615: if the infrastructure node constructs or receives a multimedia data response message, then step 616 is performed, otherwise step 617 is performed;
step 616: if the infrastructure node is the access router AR2, the multimedia data response message is forwarded to the internet, and finally reaches the access router AR1 through the internet multimedia data response message, otherwise, the infrastructure node looks up the request table and performs the following operations for each request table entry with the cloud address CA 3: the infrastructure node forwards the multimedia data response message from the interface field value of the entry, then deletes the request entry, and performs step 615;
step 617: after receiving the multimedia data response message, the device node D1 stores the data MD2 and identifies itself as a cloud member of the cloud TC 3;
step 618: finishing;
after the device node D1 becomes a cloud member of the cloud TC3, the beacon message broadcast by it is loaded with the cloud address CA 3.
Example 1
Based on the simulation parameters in table 1, the present embodiment simulates the cloud-based internet of things multimedia data communication method in the present invention, and the performance analysis is as follows: when the user is far away from the destination node, the average communication cost and delay are increased, and when the communication radius is increased, the average communication cost and delay are reduced. The average traffic cost is 7 and the routing delay is 65 ms.
TABLE 1 simulation parameters
The invention provides a concept of a cloud-based internet of things multimedia data communication method, and a number of methods and ways for specifically implementing the technical scheme, where the foregoing description is only a preferred embodiment of the invention, it should be noted that, for those skilled in the art, a number of improvements and decorations can be made without departing from the principle of the invention, and these improvements and decorations should also be regarded as the protection scope of the invention. The components not specified in this embodiment can be implemented by the prior art.
Claims (6)
1. A cloud-based multimedia data communication method of an Internet of things is characterized in that the Internet of things comprises two nodes, namely an infrastructure node and an equipment node; the infrastructure nodes comprise access routers, switches and access nodes and are used for realizing the routing forwarding function; the device nodes are used for sensing and collecting data related to the geographic position and converting the data into a multimedia data form, and the device nodes do not have a routing forwarding function; the access node and the equipment node are provided with a wireless interface, the equipment node and the access node communicate through the wireless interface, at the same time, the equipment node can only communicate with one access node, and the access node is called as an associated access node of the equipment node; the Internet of things is composed of more than two subnets, one subnet comprises an access router, more than two switches, more than two access nodes and equipment nodes related to the access nodes, and the subnets are connected with the Internet through the access router; the topological structure of the infrastructure nodes of one subnet is a tree structure, the root node is an access router, the middle node is a switch, and the leaf nodes are access nodes; the equipment associated with one access node constructs an Internet of things cloud, cloud members in the Internet of things cloud can cooperate with each other to jointly generate multimedia data related to one geographical position, and the equipment can serve as the cloud members to provide the multimedia data and can also serve as a user request to acquire the multimedia data;
a user acquires multimedia data related to a geographic position through a cloud address and a unicast address; the cloud address is composed of a network prefix, a link prefix, a data ID and a cloud address identifier, wherein the network prefix uniquely identifies one subnet, the link prefix uniquely identifies an infrastructure node in one subnet, and the data ID uniquely identifies one multimedia data type; the network prefix, the link prefix and the data ID uniquely identify one multimedia data related to the geographic location; the cloud address identifier is used for identifying that the address is a cloud address or a unicast address, if the cloud address identifier is 1, the address is indicated to be the cloud address, and if the cloud address identifier is 0, the address is indicated to be the unicast address; a cloud is uniquely identified by a cloud address;
the unicast address is composed of a network prefix, a link prefix, a device ID and a cloud address identifier, wherein the network prefix uniquely identifies one subnet, the link prefix uniquely identifies an infrastructure node in one subnet, the device ID of the access router is 1, the device IDs of the switch and the access node are 0, and the device ID of the device node is a hardware ID; the cloud address identifier value is 0, which indicates that the address is a unicast address;
link prefix partitioningA plurality of levels, wherein the parameter i is the bit length of the link prefix, and the parameter c is the bit length representing one level; the prefix of a link of the access router is 0, and the prefix of a network is preset; one subnet realizes the configuration of the link prefix through the following processes:
step 101: starting;
step 102: the access router sends a link prefix configuration message from each interface f meeting the condition 1, wherein the source address of the link prefix configuration message is a unicast address of the access router, the destination address of the link prefix configuration message is 0, the load of the link prefix configuration message is a parameter c, a parameter i, a parameter f and a parameter h, and the initial value of the parameter h is 0;
condition 1: the interface is connected to an infrastructure node;
step 103: after receiving the link prefix configuration message, the infrastructure node connected with the interface meeting the condition 1 constructs an i-bit link prefix, wherein the front h & c bit value of the link prefix is the front h & c bit value of the link prefix of the source address of the link prefix configuration message, the c bit value immediately after the front h & c bit of the link prefix is f, and finally the i- (h +1) & c bit value is 0;
step 104: if the infrastructure node receiving the link prefix configuration message is a switch, executing step 105, otherwise, executing step 106;
step 105: the switch receiving the link prefix configuration message increments the value of the parameter h by 1, the link prefix configuration message is sent from each interface f meeting the condition 1, the source address of the link prefix configuration message is the unicast address of the switch, the destination address is 0, the load is the parameter c, the parameter i and the parameter h, and step 103 is executed;
step 106: finishing;
after the access node configures the link prefix, regularly sending a beacon message through a wireless interface; after the device node associated with the access node receives the beacon message, it stores the link prefix of the access node.
2. The cloud-based internet of things multimedia data communication method according to claim 1, wherein the infrastructure node maintains an index table for recording information of cloud members, and one index table entry comprises an interface domain and a cloud address domain;
a multimedia data MD1 related to geographical location is uniquely identified by a cloud address CA1, under the condition that the cloud address CA1 has a network prefix of GRP1, a link prefix of LRP2, a data ID of CID1 and a cloud identifier of 1, an access node AP2 having a link address of LRP2 creates a multimedia data MD1 by constructing a cloud TC1, and the process is as follows:
step 201: starting;
step 202: the access node AP2 creates a unicast address, the network prefix of the unicast address is 0, the link prefix is LRP2, the equipment ID is 0, the cloud identifier is 0, the access node AP2 sends a message for creating multimedia data from a wireless interface, the source address of the message is the created unicast address, and the destination address is CA 1;
step 203: after receiving the multimedia data creating message, if part of data of the data MD1 can be created, the device node associated with the access node AP2 sends a multimedia data creating response message, where the source address of the multimedia data creating response message is the destination address of the multimedia data creating message, the destination address is the source address of the multimedia data creating message, and the load is the created multimedia data;
step 204: after receiving all the multimedia data creating response messages, the access node AP2 constructs the multimedia data in the multimedia data creating response messages into multimedia data MD1, and then sends multimedia data sharing messages from a wireless interface, wherein the source address of the multimedia data sharing messages is the unicast address created in the step 202, the destination address is CA1, and the load is data MD 1;
step 205: after receiving the message for creating the multimedia data sharing, the device node associated with the access node AP2 stores the data MD1 and identifies itself as a cloud member of the cloud TC1 if there is enough storage space for storing the data MD 1;
step 206: finishing;
after the access node AP2 creates the data MD1, deleting the data MD 1;
after the device node becomes a cloud member of the cloud TC1, the beacon message broadcast by the device node is loaded to the cloud address CA1.
3. The method as claimed in claim 2, wherein if the access node receives the beacon message with the load of the cloud address CA1 from the interface f1, it determines whether there is an index table entry with a cloud address domain value of CA1 and an interface domain value of f1 in its index table, and if not, the following operations are performed:
step 301: start of
Step 302: the access node creates an index table entry with a cloud address domain value of CA1 and an interface domain value of f1 in an index table, then creates a unicast address of the access node and a unicast address of a father node, wherein in the unicast address of the access node, a network prefix is 0, a link prefix is a link prefix of the access node, a device ID is 0, a cloud identifier is 0, in the unicast address of the father node, the network prefix is 0, the link prefix is a link prefix of the father node, if the father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a beacon message is sent from an interface connected with the father node, the source address of the beacon message is the unicast address of the access node, the destination address is the unicast address of the father node, and the load is the cloud address CA 1;
step 303: after receiving the beacon message with the load of the cloud address CA1 from the interface f2, the father node judges whether an index table entry with a cloud address domain value of CA1 and an interface domain value of f2 exists in the index table of the father node, if so, the step 306 is executed, otherwise, the step 304 is executed;
step 304: the father node creates an index table entry with a cloud address domain value of CA1 and an interface domain value of f2 in an index table, if the father node is an access router, step 306 is executed, otherwise, step 305 is executed;
step 305: a father node creates a self unicast address and a self unicast address of a father node, in the self unicast address, a network prefix is 0, a link prefix is a self link prefix, a device ID is 0, a cloud identifier is 0, in the self unicast address of the father node, the network prefix is 0, the link prefix is a link prefix of the father node, if the self father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a beacon message is sent from an interface connected with the self father node, the source address of the beacon message is a self unicast address, the destination address is a self unicast address of the father node, the load is a cloud address CA1, and the step 303 is executed;
step 306: and (6) ending.
4. The cloud-based internet of things multimedia data communication method according to claim 3, wherein if a device node is invalid or out of a communication range of a currently associated access node, the access node cannot receive a beacon frame sent by the device node; if the access node does not receive any beacon message loaded with the cloud address CA1 from the interface f1 within the specified time, the access node deletes the index table entry with the cloud address domain value of CA1 and the interface domain value of f1 from the index table; if the access node does not have the index table entry with the cloud address domain value of CA1 in the index table, the following cloud retrieval table entry deletion process is executed:
step 401: start of
Step 402: the access node creates a unicast address of the access node and a unicast address of a father node, in the unicast address of the access node, the network prefix is 0, the link prefix is the link prefix of the access node, the device ID is 0, the cloud identifier is 0, in the unicast address of the father node, the network prefix is 0, the link prefix is the link prefix of the father node, if the father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a retrieval table item deletion message is sent from an interface connected with the father node, the source address of the retrieval table item deletion message is the unicast address of the access node, the destination address is the unicast address of the father node, and the load is the cloud address CA 1;
step 403: after receiving a retrieval table item deletion message with the load of cloud address CA1 from an interface f2, the parent node deletes the index table item with the cloud address domain value of CA1 and the interface domain value of f2 from the index table, then judges whether the index table of the parent node has the index table item with the cloud address domain value of CA1, if so, executes step 406, otherwise, executes step 404;
step 404: if the parent node is an access router, executing step 406, otherwise executing step 405;
step 405: a father node creates a self unicast address and a self unicast address of a father node, in the self unicast address, a network prefix is 0, a link prefix is a self link prefix, a device ID is 0, a cloud identifier is 0, in the self unicast address of the father node, the network prefix is 0, the link prefix is a link prefix of the self father node, if the self father node is an access router, the device ID is 1, otherwise, the device ID is 0, the cloud identifier is 0, then a retrieval table item deleting message is sent from an interface connected with the self father node, the source address of the retrieval table item deleting message is the self unicast address, the destination address is the self unicast address of the father node, the load is a cloud address CA1, and step 403 is executed;
step 406: and (6) ending.
5. The cloud-based Internet of things multimedia data communication method according to claim 4,
the infrastructure node maintains a request table for recording uncompleted multimedia data request information, and the request table comprises an interface domain and a cloud address domain;
a multimedia data MD2 associated with a geographical location is uniquely identified by a cloud address CA2, the data MD2 is created by building a cloud TC 2; the device node D1 is located in the subnet S1, the network prefix of the subnet S1 is GRP1, and the device node D1 is associated with the access node AP 1; if the condition 2 or the condition 3 is satisfied, the device node D1 acquires the data MD2 by:
condition 2: the network prefix of the cloud address CA2 is GRP1 and the link prefix is equal to the link prefix of the access node AP 2;
condition 3: the network prefix of the cloud address CA2 is not equal to GRP1, but there is at least one cloud member of cloud TC2 in subnet S1;
step 501: starting;
step 502: the device node D1 creates a unicast address, the network prefix is 0, the link prefix is the link prefix of the access node AP1, the device ID is the device ID of the device node D1, and then sends a multimedia data request message, the source address of the multimedia data request message is the constructed unicast address, and the destination address is the cloud address CA 2;
step 503: judging whether the infrastructure node or the device node receives the multimedia data request message from the interface f3, if the infrastructure node receives the multimedia data request message, executing the step 504, otherwise executing the step 511;
step 504: if the infrastructure node has a request table entry with the cloud address of CA2 and the interface domain value of f3 in the request table, executing step 514, otherwise executing step 505;
step 505: the infrastructure node creates a request table entry with a cloud address of CA2 and an interface domain value of f3 in the request table, if the infrastructure node only has one request table entry with a cloud address of CA2, step 506 is executed, otherwise step 514 is executed;
step 506: if the infrastructure node has at least one index table entry with the cloud address of CA2 in the index table, executing step 507, otherwise executing step 508;
step 507: the infrastructure node randomly selects an index table entry with a cloud address of CA2, forwards the received multimedia data request message from the interface domain of the index table entry, and executes step 503;
step 508: if the infrastructure node is the access node AP2, go to step 509, otherwise go to step 510;
step 509: the access node AP2 executes the steps 201-206 to create the multimedia data MD2, then constructs a multimedia data response message, the load of the multimedia data response message is data MD2, the source address is the destination address of the received multimedia data request message, the destination address is the source address of the received multimedia data request message, and executes the step 514;
step 510: the infrastructure node checks all the child nodes, and if the matching degree of the link prefixes of all the child nodes and the link prefixes of the cloud address CA2 is the same as the matching degree of the link prefixes of the infrastructure node and the cloud address CA2, the multimedia data request message is forwarded from an interface connected with the parent node; otherwise, selecting a child node, wherein the matching degree of the link prefix of the child node and the link prefix of the cloud address CA2 is maximum, and then forwarding the multimedia data request message from an interface connected with the child node; step 503 is executed; the matching degree is judged to be compared from the first bit of the link prefix, and the more the number of continuous identical bits is, the greater the matching degree is;
step 511: if the device node receiving the multimedia data request message is capable of providing the data MD2, perform step 513, otherwise perform step 512;
step 512: the device node receiving the multimedia data request message discards the multimedia data request message, and performs step 514;
step 513: the equipment node receiving the multimedia data request message sends a multimedia data response message, wherein the load of the multimedia data response message is data MD2, the source address is the destination address of the received multimedia data request message, and the destination address is the source address of the received multimedia data request message;
step 514: if the infrastructure node constructs or receives a multimedia data response message, step 515 is performed, otherwise step 516 is performed;
step 515: the infrastructure node looks at the request table, and performs the following operations on each request table entry with the cloud address of CA 2: the infrastructure node forwards the multimedia data response message from the interface field value of the entry, then deletes the request entry, and performs step 514;
step 516: after receiving the multimedia data response message, the device node D1 stores the data MD2 and identifies itself as a cloud member of the cloud TC 2;
517: finishing;
after the device node D1 becomes a cloud member of the cloud TC2, the beacon message broadcast by it is loaded with the cloud address CA 2.
6. The cloud-based internet of things multimedia data communication method according to claim 5, wherein, on the condition that a multimedia data MD3 related to a geographical location is uniquely identified by a cloud address CA3, the data MD3 is created by constructing a cloud TC3, the device node D1 is located in a subnet S1, a network prefix of the subnet S1 is GRP1, an access router is AR1, a subnet S2 is a network prefix of GRP2, an access router is AR2, a cloud address CA3 is a network prefix of GRP2, a link prefix domain access node AP4 has the same link prefix, an access node AP4 is located in the subnet S2, and the device node D1 is associated with the access node AP1, if the condition 4 is met, the device node D1 obtains the data MD3 by the following process:
condition 4: there are no cloud members of cloud TC3 in subnet S1;
step 601: starting;
step 602: the device node D1 creates a unicast address, the network prefix is 0, the link prefix is the link prefix of the access node AP1, the device ID is the device ID of the device node D1, and then sends a multimedia data request message, the source address of the multimedia data request message is the constructed unicast address, and the destination address is the cloud address CA 3;
step 603: determining whether the infrastructure node or the device node receives the multimedia data request message from the interface f4, if the infrastructure node receives the multimedia data request message, performing step 604, otherwise performing step 614;
step 604: if condition 5 is satisfied or both conditions 6 and 7 are satisfied, then perform step 615, otherwise perform step 605;
condition 5: the infrastructure node has a request table entry with a cloud address of CA3 and an interface domain value of f4 in the request table;
condition 6: the infrastructure node is an access router AR2, and an interface f4 is connected with the Internet;
condition 7: the infrastructure node at least has one request table entry with the cloud address of CA3 in the request table;
condition 8: the infrastructure node does not have any request table entry with the cloud address of CA3 in the request table;
step 605: if conditions 6 and 8 are satisfied, performing step 607, otherwise performing step 606;
step 606: the infrastructure node creates a request table entry with a cloud address of CA3 and an interface domain value of f4 in the request table, if the infrastructure node only has one request table entry with a cloud address of CA3, step 607 is executed, otherwise step 615 is executed;
step 607: if the infrastructure node is located in subnet S1, then step 608 is performed, otherwise step 609 is performed;
step 608: if the infrastructure node is an access router AR1, updating the network prefix of the source address in the multimedia data request message to GRP1, then sending the multimedia data request message to the Internet, and finally reaching the access router AR2 through the Internet multimedia data request message; otherwise, the infrastructure node forwards the multimedia data request message from the interface connected with the father node; step 603 is executed;
step 609: if the infrastructure node has at least one index table entry with the cloud address of CA3 in the index table, executing step 610, otherwise executing step 611;
step 610: the infrastructure node randomly selects an index table entry with a cloud address of CA3, forwards the received multimedia data request message from an interface domain of the index table entry, and executes step 603;
step 611: if the infrastructure node is access node AP4, go to step 612, otherwise go to step 613;
step 612: the access node AP4 executes the steps 201-206 to create the multimedia data MD3, then constructs a multimedia data response message, the load of the multimedia data response message is data MD3, the source address is the destination address of the received multimedia data request message, the destination address is the source address of the received multimedia data request message, and executes the step 615;
step 613: the infrastructure node checks all the child nodes, and if the matching degree of the link prefixes of all the child nodes and the link prefixes of the cloud address CA2 is the same as the matching degree of the link prefixes of the infrastructure node and the cloud address CA2, the multimedia data request message is forwarded from an interface connected with the parent node; otherwise, selecting a child node, wherein the matching degree of the link prefix of the child node and the link prefix of the cloud address CA2 is maximum, and then forwarding the multimedia data request message from an interface connected with the child node; step 603 is executed; the matching degree is judged to be compared from the first bit of the link prefix, and the more the number of continuous identical bits is, the greater the matching degree is;
step 614: if the device node receiving the multimedia data request message can provide the data MD3, sending a multimedia data response message, wherein the load of the multimedia data response message is the data MD3, the source address is the destination address of the received multimedia data request message, and the destination address is the source address of the received multimedia data request message; otherwise, the equipment node receiving the multimedia data request message discards the multimedia data request message;
step 615: if the infrastructure node constructs or receives a multimedia data response message, then step 616 is performed, otherwise step 617 is performed;
step 616: if the infrastructure node is the access router AR2, the multimedia data response message is forwarded to the internet, and finally reaches the access router AR1 through the internet multimedia data response message, otherwise, the infrastructure node looks up the request table and performs the following operations for each request table entry with the cloud address CA 3: the infrastructure node forwards the multimedia data response message from the interface field value of the entry, then deletes the request entry, and performs step 615;
step 617: after receiving the multimedia data response message, the device node D1 stores the data MD2 and identifies itself as a cloud member of the cloud TC 3;
step 618: finishing;
after the device node D1 becomes a cloud member of the cloud TC3, the beacon message broadcast by it is loaded with the cloud address CA 3.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710750761.2A CN107547173B (en) | 2017-08-28 | 2017-08-28 | Cloud-based internet of things multimedia data communication method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710750761.2A CN107547173B (en) | 2017-08-28 | 2017-08-28 | Cloud-based internet of things multimedia data communication method |
Publications (2)
Publication Number | Publication Date |
---|---|
CN107547173A CN107547173A (en) | 2018-01-05 |
CN107547173B true CN107547173B (en) | 2020-03-24 |
Family
ID=60958809
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201710750761.2A Active CN107547173B (en) | 2017-08-28 | 2017-08-28 | Cloud-based internet of things multimedia data communication method |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN107547173B (en) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1645809A (en) * | 2004-01-19 | 2005-07-27 | 威达电股份有限公司 | Method for accelerating packing filter |
CN102571599A (en) * | 2012-02-08 | 2012-07-11 | 福建三元达通讯股份有限公司 | Rapid storage method of routing table entry |
CN103634415A (en) * | 2012-08-22 | 2014-03-12 | 国基电子(上海)有限公司 | System, device and method for reducing network address header number |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7765294B2 (en) * | 2006-06-30 | 2010-07-27 | Embarq Holdings Company, Llc | System and method for managing subscriber usage of a communications network |
-
2017
- 2017-08-28 CN CN201710750761.2A patent/CN107547173B/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1645809A (en) * | 2004-01-19 | 2005-07-27 | 威达电股份有限公司 | Method for accelerating packing filter |
CN102571599A (en) * | 2012-02-08 | 2012-07-11 | 福建三元达通讯股份有限公司 | Rapid storage method of routing table entry |
CN103634415A (en) * | 2012-08-22 | 2014-03-12 | 国基电子(上海)有限公司 | System, device and method for reducing network address header number |
Non-Patent Citations (1)
Title |
---|
"浅谈云计算与物联网的融合发展";续晓燕等;《电脑知识与技术》;20121126(第24期);5782-5784 * |
Also Published As
Publication number | Publication date |
---|---|
CN107547173A (en) | 2018-01-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10798650B2 (en) | AP-local dynamic switching | |
US9736672B2 (en) | Targeted group-based discovery for wireless communication devices | |
US9525613B2 (en) | Communication system, logical channel control device, control device, communication method and program | |
US10419342B2 (en) | Gateways for sensor data packets in cellular networks | |
CN109561033B (en) | Method and device for multicast replication in Overlay network | |
CN104333914B (en) | A kind of Mesh link establishing method and equipment | |
CN106330718B (en) | Method for forwarding multicast message and device | |
US20100329177A1 (en) | Ap-local dynamic switching | |
US9628435B2 (en) | Duplicate address detection based on distributed bloom filter | |
CN105450521B (en) | A kind of multi-path network stream real time dynamic optimization method of software definition | |
CN109547348B (en) | Communication and route establishing method and device | |
CN106993321B (en) | Network data communication method based on cluster | |
CN105814943A (en) | VPNv4 ROUTE CONTROL FOR LTE X2 SON USING UNIQUE ROUTE TARGETS | |
US10009256B2 (en) | Hybrid routing table for reaching unstable destination device in a tree-based network | |
CN105814945A (en) | VPNv4 route control for LTE X2 SON using import route maps and outbound route filtering | |
CN105072605B (en) | Terminal roaming method under AP stand-alone modes and AP | |
CN105207909B (en) | A kind of method and network equipment sending information | |
CN107979645B (en) | Internet of things implementation method | |
CN107508927B (en) | Future Internet of vehicles data communication method based on cloud | |
US20150085734A1 (en) | Method and system for roamed client device handling | |
CN106850869B (en) | IP address configuration method and network equipment | |
CN101827455B (en) | Method for automatically establishing link connection, device and base station | |
CN107547173B (en) | Cloud-based internet of things multimedia data communication method | |
CN110401911B (en) | Vehicle-mounted cloud implementation method based on named data network | |
US10333830B2 (en) | Passive routing in mesh network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |