CN109428768B

CN109428768B - Autonomous network service method and autonomous network

Info

Publication number: CN109428768B
Application number: CN201711031491.6A
Authority: CN
Inventors: 陆宏成; 杨春晖
Original assignee: Shanghai Qianting Network Technology Co ltd
Current assignee: Shanghai Qianting Network Technology Co ltd
Priority date: 2017-10-27
Filing date: 2017-10-27
Publication date: 2022-07-19
Anticipated expiration: 2037-10-27
Also published as: CN109428768A

Abstract

The embodiment of the application provides a service communication method of an autonomous network and the autonomous network, wherein the autonomous network comprises a plurality of autonomous clouds distributed according to layers, and the method comprises the following steps: a master control server in a certain autonomous cloud receives a service request of a global data sink; a master control server in one or more autonomous clouds creates a global multicast link from a global data source to a global data sink in the autonomous cloud to which the master control server belongs according to the service request; and the master control server in one or more autonomous clouds controls the global data source and the global data sink to carry out service communication through the global multicast link control in the autonomous cloud to which the master control server belongs. Each autonomous cloud can become an independently operated centralized control network, and the stability of the autonomous network is improved.

Description

Autonomous network service method and autonomous network

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a service communication method for an autonomous network and an autonomous network.

Background

Networks, including the internet, enable the exchange of information and other information resources between different individuals and organizations. Networks typically include access, transport, signaling, and network management technologies. These techniques are widely available in various literature categories.

The path technology for connecting terminals to a wide area transmission network (e.g., local loops at the edge of the terminal device and network) has evolved from 14.4, 28.8, and 56K modems to technologies including ISDN, T1, cable modem, DSL, ethernet, and wireless connections.

Transmission techniques used in wide area networks today include: synchronous Optical Networks (SONET), Dense Wavelength Division Multiplexing (DWDM), frame relay, Asynchronous Transfer Mode (ATM), and Resilient Packet Ring (RPR).

The Internet Protocol (IP) is most widely used in all of the different signaling technologies, such as protocols and methods used to establish, maintain and terminate communications in a network. In fact, almost all communication and networking experts consider an IP protocol-based network (e.g., the internet) that integrates voice (e.g., telephony), video, and data networks into a single entity to be unavoidable. As stated by one author: it is clear that some passengers are very enthusiastic to the trip, and others are very unwillingly dragged to go, cry, call and kick, which list various defects of the IP. However, despite its shortcomings, IP has been adopted as an industry standard, and no technology other than it has so much potential and space for development. "

With the explosive growth of the Internet business, its application range has been expanded to various fields of society and various industries. From the telecommunications industry, IP transport, so-called eventing Over IP, has been increasingly adopted by traditional telecommunications services. The existing framework of telecommunication networks will gradually switch from circuit switching and its networking technology to a new framework based on packet switching, especially IP, and the traffic carried by telecommunication networks will switch from telephony to data traffic.

TCP/IP network protocol

TCP/IP (Transmission Control Protocol/Internet Protocol) is the most widely applied Protocol in the world at present, the popularity of the TCP/IP is closely related to the rapid development of the Internet-TCP/IP is originally designed for the prototype ARPANET of the Internet, and the purpose is to provide a whole set of convenient and practical protocols which can be applied to various networks. TCP/IP has proven to do this, which eases network interconnection and makes it a de facto standard for the Internet to add more and more networks to it.

Application layer-application layer is a generic term for all applications to which users are directed. The TCP/IP suite has many protocols at this level to support different applications, and many of the well-known Internet-based applications are implemented without departing from these protocols. For example, HTTP protocol for World Wide Web (WWW) access, FTP protocol for file transfer, SMTP for email transmission, DNS protocol for domain name resolution, Telnet protocol for remote login, and the like are all included in the TCP/IP application layer. For users, what the users see is an operation interface which is constructed by individual software and is mostly graphical, and what the users actually run in the background is the above protocols.

Transport layer-the function of the transport layer is mainly to provide communication between applications, and the TCP/IP protocol family has TCP and UDP as the protocols in this layer.

The network layer is a very critical layer in a TCP/IP protocol family, and an IP address format is mainly defined, so that data of different application types can be smoothly transmitted on the Internet, and the IP protocol is a network layer protocol.

The network interface layer is the bottom layer of the TCP/IP software and is responsible for receiving and sending IP data packets through the network, or receiving physical frames from the network, extracting the IP data packets and delivering the IP data packets to the IP layer.

How is IP enabled for internetworking? Network systems and devices, such as ethernet networks, packet switching networks, etc., from various vendors cannot communicate with each other. The main reason for the inability to interwork is because the formats of the elementary units of data they transmit (referred to in the art as "frames") differ. The IP protocol is actually a set of protocol software composed of software programs, and it uniformly converts various "frames" into "IP data packet" format, which is a most important feature of the internet, so that all the various computers can be intercommunicated on the internet, i.e. it has "openness" feature.

Then what is the "packet"? What characteristics it has? Data packets are also a form of packet switching, in which transmitted data segments are packed into "packets" and then transmitted. However, it is of the "connectionless type" in which each packet (packet) is transmitted as an "independent message", and is called a "data packet". Thus, it is not necessary to connect each circuit before starting communication, and each packet does not necessarily travel through the same path, and therefore, the connection-less type is called. This feature is very important, and in the case of text messaging, it greatly increases the robustness and security of the network.

Each data packet has two parts of a message and a header, and the header has necessary contents such as destination address, so that each data packet can accurately reach a destination without passing through the same path. At the destination, the data is recombined and restored to the original sent data, and the IP has the functions of packet packaging and aggregate assembling.

During actual transmission, the length of the data packet can be changed according to the packet size specified by the network, and the maximum length of the IP data packet can reach 65535 bytes.

How to guarantee quality of service (QoS) is a major issue in IP internet. If we ranked the major QoS milestones in time, it is not hard to see that internet QoS is an endless history of ever decreasing requirements and ever failing, despite the long-standing myriad of research reports attempting to solve this problem. From "Inte Serv" (1990) to "Diff Serv" (1997) to "Lightload" (2001), the various QoS local improvement schemes that seem to be effective add up to the goal of network-wide quality assurance, again like a moon in water, with QoS appearing close and far from being achievable.

Video applications have been the target of web services, such as MBone, as early as the IP Internet. Due to the lack of effective quality assurance, video communication services with commercial value cannot be developed for a long time, and the profitability of the IP internet is weakened. Therefore, the method solves the problem of network transmission quality and has great commercial value. The network transmission quality is embodied as packet loss and error code, the computer file is insensitive to the error in transmission, and even if most data packets are lost in the transmission process, the computer still considers that the network is available as long as a retransmission mechanism of TCP is provided. However, if the packet loss rate or the bit error rate is higher than one in a thousand, the video and audio quality of the synchronous video will be degraded. Empirical data tells us that high quality video communication even requires packet loss rates and bit error rates below one ten-thousandth. The test data of the current network environment shows that most packet loss occurs inside the router, and bit errors generated in optical fiber transmission can be almost ignored.

Why "Inte Serv" was unsuccessful?

The Inte Serv is established on the basis of independent flow Resource Reservation and adopts the Resource Reservation Protocol (RSVP) Protocol. In a large-scale network environment, it sounds good to dedicate a portion of the bandwidth resources between two video terminals for the video service, but it does not actually work.

First, this solution requires a total network equipment modification, equal to re-networking, which is almost impossible to operate practically.

Secondly, even if the entire network is modified, for example, in each switch, it can reserve 2Mbps bandwidth for 2Mbps video service, and can solve the quality assurance? The answer is likewise negative.

The 2Mbps bandwidth of so-called RSVP can only be macroscopically, and if 1 second of data is sent in the first half of a second in a concentration, it can cause problems, resulting in periodic bursty traffic. Since the core concept of IP internet is best effort, at each network node, the switch always tries to forward data at the fastest speed, when a video stream passes through a multi-stage switch, the traffic distribution is inevitably uneven, and a plurality of uneven non-synchronous streams are combined together, which causes greater unevenness in a period of time. That is, network traffic must be blocked periodically. With the increase of the number of video users, there is no upper limit for the periodic blocking, and when the internal storage capacity of the switch is exceeded, packet loss will be caused directly.

Why "Diff Serv" was unsuccessful?

Seven years after the advent of "Inte Serv," a new method, "Diff Serv," began to prevail. "Diff Serv" attempts to provide a better than best effort network service by eliminating the need for complex network-wide resource reservations and is simple to implement, as long as a "priority" flag is placed in each packet and the network switch first processes the video data with "priority". The basic principle of the method is better than that of issuing gold cards by VIP customers in silver behavior, and the queuing time of high-end customers can be effectively reduced. This method also sounds nice but is still not practical.

We cannot ignore the simple fact that the single video traffic is much larger (more than a hundred times) than the traditional non-video traffic.

As long as there are a small number of video users, almost all video packets are seen on the network. If most of the data packets hold the gold card, the VIP is not called. In addition, since the IP internet is not mandatory, although QoS establishes a unique set of ethical standards for users, it is not realistic to require others to perform it consciously.

Therefore, "Diff Serv" is difficult to be effectively popularized in a large-scale public network, except for being used in a few enterprise private networks.

Why "Light load" was unsuccessful?

Since the IP internet has been gradually popularized, people are constantly searching for good ways to solve the network quality assurance. Two QoS schemes are not ideal after the network technology experts search for intestines and scrape the belly for more than ten years. In a large environment where there is no confidence in resolving QoS, some people unwilling to keep their name propose an "Light load" which is not a solution. The basic idea is a so-called light load network, and it is considered that if the bandwidth is sufficient, the optical fiber enters the home, and there is no concern about network congestion.

Is the assumption of a lightly loaded network feasible? The answer is also negative.

Current network technology experts seem to be unaware of a fundamental principle that the root cause of network packet loss is traffic non-uniformity. Macroscopically, a little faster transmission in one time period inevitably leads to congestion in another time period, and as long as the network traffic is not uniform, the peak traffic that the network can reach has no upper limit, and any large bandwidth can be occupied in a short time.

In fact, if only 2Mbps bandwidth is available, a good video program can be transmitted, and if 8Mbps bandwidth is available, video content with HDTV quality can be transmitted. However, if we are free to view a text or a photo on a regular website, most of the current website servers use gigabit ports, which have ten times the instantaneous traffic of HDTV. If there are many similar sites that happen to collide together, the burst traffic generated in a short time will exceed the requirement of the full network users to use HDTV, and can fill any wide network. Statistical analysis shows that such collisions are frequent.

IP internet attempts to use storage to absorb transient traffic with the consequence of increased transmission delay. There is no upper limit for bursty traffic due to limited storage capacity. Therefore, the storage method can only improve the probability of packet loss of the device, and the burst traffic absorbed by the node will cause more pressure on the next node. Video traffic is continuous, the storage mode of the switch aggravates the convergence of burst traffic to weak nodes, and network packet loss cannot be avoided.

The current network constructors can cope with the narrow-band VoIP voice service by adopting the light load and the Diff Serv technology. This is because voice does not dominate the total traffic in the network, and once congestion occurs, computer files may be sacrificed, giving priority to voice. However, for high bandwidth video communication, local expansion can only receive a temporary improvement. If other places are also expanded, the nonuniformity of network flow follows the ship height of water fluctuation, and the effect of the original expanded part is reduced. If the whole network is expanded evenly, the transmission quality will be restored to the original state before expansion. That is, the entire expansion is ineffective.

The current equipment manufacturers recommend ultra wide band access networks of tens of or hundreds of millions of each household, and even if each household has optical fibers, the video communication service with guaranteed quality is difficult to show to consumers. The more complicated QoS means can only "improve" the transmission quality of the IP internet at best, but cannot "guarantee" the network transmission quality.

Disclosure of Invention

In view of the above problems, embodiments of the present application are provided to provide a network access method for an autonomous cloud in an autonomous network, a master control server, a micro cloud server, a terminal, and an autonomous network, which overcome or at least partially solve the above problems.

According to one aspect of the application, a service communication method of an autonomous network is provided, wherein the autonomous network comprises a plurality of autonomous clouds distributed according to layers, each autonomous cloud comprises a main control server, a micro cloud server, a terminal and a switching network, the micro cloud server comprises a boundary router, a terminal sub-control server and a boundary sub-control server, and two adjacent layers of autonomous clouds are connected by multiplexing the same boundary router;

in each autonomous cloud, a main control server and a micro cloud server are accessed into a switching network, a terminal sub-control server and a terminal are accessed into another switching network, and a boundary sub-control server and a boundary router are accessed into another switching network; the method comprises the following steps:

a master control server in a certain autonomous cloud receives a service request of a global data sink;

a master control server in one or more autonomous clouds creates a global multicast link from a global data source to a global data sink in the autonomous cloud to which the master control server belongs according to the service request;

And the master control server in one or more autonomous clouds controls the global data source and the global data sink to carry out service communication through the global multicast link control in the autonomous cloud to which the master control server belongs.

According to another aspect of the application, an autonomous network is provided, wherein the autonomous network comprises a plurality of autonomous clouds distributed according to layers, each autonomous cloud comprises a main control server, a micro cloud server, a terminal and a switching network, the micro cloud server comprises a boundary router, a terminal sub-control server and a boundary sub-control server, and two adjacent layers of autonomous clouds multiplex the same boundary router for connection;

in each autonomous cloud, a main control server and a micro cloud server are accessed into a switching network, a terminal sub-control server and a terminal are accessed into another switching network, and a boundary sub-control server and a boundary router are accessed into another switching network; the master server includes:

the service request receiving module is used for receiving a service request of the global data sink;

the global multicast link creating module is used for creating a global multicast link from a global data source to the global data sink in the autonomous cloud to which the service request belongs according to the service request;

and the service communication control module is used for controlling the global data source and the global data sink to carry out service communication through the global multicast link control in the autonomous cloud to which the service communication control module belongs.

The embodiment of the application has the following advantages:

the embodiment of the application provides an autonomous network, and the autonomous network is a novel network which is easy to manage and extensible, and can ensure the stable speed and controllable delay during data transmission.

First, in the embodiment of the present application, in an autonomous cloud manner, control and management are performed by a master control server inside each autonomous cloud, so that each autonomous cloud can become an independently operating centralized control network. Therefore, once a certain autonomous cloud breaks down, other autonomous clouds can still normally operate, the problem that the whole network cannot operate due to the fact that the certain autonomous cloud breaks down is avoided, and the stability of the autonomous network is improved.

Secondly, in the embodiment of the application, the device in the autonomous network registers on the master control server, and then obtains the service of the autonomous network after accessing the autonomous network through the network access process. Therefore, the illegal access of the equipment can be prevented, the safety and the manageability of the autonomous network are improved, and the stable operation of the autonomous network is also ensured.

Thirdly, in the embodiment of the application, hierarchical management is realized on the devices in a master control and sub-control manner inside the autonomous cloud, and network access parameters of the devices are accurately configured through a network access process between a manager (a master control server, a terminal sub-control server or a boundary sub-control server) and a manager (a micro-cloud server, a terminal or a boundary router), so that a clear network topology is established. Therefore, the devices in the autonomous cloud can communicate with each other without routing negotiation, and stability in communication is guaranteed.

Fourthly, in the embodiment of the application, network access parameters of each autonomous cloud are accurately configured in a layered access mode among a plurality of autonomous clouds through a network access process between a boundary router and an adjacent autonomous cloud, and a clear network topology is established. Therefore, devices among different autonomous clouds can communicate with each other without routing negotiation, so that the stability during communication is ensured, and the expandability of the autonomous network is also ensured.

Fifth, in the embodiment of the present application, the autonomous network uses a hierarchical network topology with a clear structure, so that a data switching node in the autonomous network does not need to perform routing calculation for each data packet or maintain the topology of peripheral devices of the data switching node, and can complete transmission of the data packet according to a relevant configuration command of the master control server. Therefore, the operation requirement of the data exchange node can be greatly reduced, the data transmission efficiency is improved, and meanwhile, the stable speed and controllable delay during data transmission can be ensured.

Sixth, in this embodiment of the application, before data packets of each service are transmitted, a data transmission channel needs to be configured through communication between the master control servers of each autonomous cloud, that is, data packets in the same service are transmitted through the same path, unlike the scheme of the existing IP protocol, each data packet solves a routing problem by means of self-negotiation, and it is not known which path the data packet will pass through before the data packet is sent out, that is, two data packets of the same service may be transmitted to a target terminal through different paths. Therefore, the stable transmission rate and the stable transmission delay can be ensured, and the transmission quality of the autonomous network is improved.

Seventh, in the embodiment of the present application, various existing network communication technologies (such as ethernet) may be merged at the bottom layer, so that a completely new transmission network does not need to be established from a physical layer, the cost of network modification may be greatly reduced, and the possibility of actual operation is improved. Meanwhile, the problem of poor reliability and usability of an IP network is solved, the requirements of controllability, manageability and service quality guarantee of an operation level network are met at least, and the large-scale networking capability is provided.

Eighth, in the embodiment of the present application, a data transmission manner may implement point-to-multipoint data communication in an autonomous network on the premise of not consuming a large amount of bandwidth, thereby improving a utilization rate of network bandwidth.

Ninth, in the embodiment of the present application, a data transmission manner adopts a distributed configuration and management method, and a master control server of each autonomous cloud does not need to uniformly manage multicast links of a whole network, thereby greatly reducing requirements (such as processing capability, memory space, and the like) for software and hardware resources of the master control server.

Drawings

FIG. 1 is a schematic diagram of an autonomous network according to an embodiment of the present application;

FIG. 2 is a schematic diagram of an autonomous cloud according to an embodiment of the present application;

Fig. 3 is a schematic structural diagram of a master server according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a sub-control server according to an embodiment of the present application;

FIG. 5 is a block diagram of a border router according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a terminal according to an embodiment of the present application;

FIG. 7 is a flow chart illustrating steps of a method for autonomous network traffic communication in accordance with one embodiment of the present application;

FIG. 8 is a flow chart of steps in another method of autonomous network traffic communication according to one embodiment of the present application;

FIG. 9 is a flow chart of steps in another method of autonomous network traffic communication according to one embodiment of the present application;

FIG. 10 is a flow chart of steps in another method of autonomous network traffic communication according to one embodiment of the present application;

FIG. 11 is a flow chart of steps in another method of autonomous network traffic communication according to one embodiment of the present application;

FIG. 12 is a flow chart of steps in a method of traffic communication for another autonomous network of one embodiment of the present application;

FIG. 13 is a flow chart of steps in another method of autonomous network traffic communication according to one embodiment of the present application;

FIG. 14 is a flow chart of steps in another method of autonomous network traffic communication according to one embodiment of the present application;

FIG. 15 is a flow diagram illustrating steps in another method of autonomous network traffic communication in accordance with one embodiment of the present application;

FIG. 16 is a flow chart of steps in another method of autonomous network traffic communication according to one embodiment of the present application;

FIG. 17 is a flow chart of steps in a method of traffic communication for another autonomous network of one embodiment of the present application;

FIG. 18 is a flow chart of steps in a method of traffic communication for another autonomous network of one embodiment of the present application;

FIG. 19 is a flow chart of steps in another method of autonomous network traffic communication according to one embodiment of the present application;

FIG. 20 is a flow chart of steps in a method of traffic communication for another autonomous network of one embodiment of the present application;

FIG. 21 is a flow chart of steps in a method of traffic communication for another autonomous network of one embodiment of the present application;

FIG. 22 is a flow chart of steps in another method of autonomous network traffic communication according to one embodiment of the present application;

FIG. 23 is a flow chart of steps in another method of autonomous network traffic communication according to one embodiment of the present application;

FIG. 24 is a flow chart of steps in another method of autonomous network traffic communication according to one embodiment of the present application;

FIG. 25 is a diagram illustrating an example of traffic communication for an autonomous network according to one embodiment of the present application;

FIG. 26 is a diagram of an example of traffic communication for another autonomous network according to one embodiment of the present application;

FIG. 27 is a diagram of an example of traffic communication for another autonomous network of one embodiment of the present application;

fig. 28 is a block diagram of an autonomous network according to an embodiment of the present application.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.

The autonomous network proposed by the embodiment of the present application is introduced as follows:

topological structure of autonomous network

Referring to fig. 1, a schematic structural diagram of an autonomous network according to an embodiment of the present application is shown.

As shown in fig. 1, the autonomous network is a distributed centralized control network, and includes a plurality of autonomous clouds distributed in layers, that is, the overall network structure of the autonomous network is formed by connecting a plurality of substructures called autonomous clouds, and the autonomous clouds exhibit a hierarchical structure when connected with each other.

Each autonomous cloud can be connected with one or more next-layer autonomous clouds from the top-layer autonomous cloud, the lower-layer autonomous clouds are connected with the next-layer autonomous clouds until the lowest-layer autonomous cloud, and all the autonomous clouds are connected layer by layer in the mode to form an autonomous network.

Obviously, the hierarchical structure is a tree structure, each autonomous cloud is a node in the tree, and the whole autonomous network is a tree formed by a plurality of autonomous clouds serving as nodes.

As shown in fig. 1, the autonomous network includes four layers, an autonomous cloud in the fourth layer (L4) connecting autonomous clouds in a plurality of third layers (L3), an autonomous cloud in the third layer (L3) connecting autonomous clouds in a plurality of second layers (L2), and an autonomous cloud in the second layer (L2) connecting autonomous clouds in one or more first layers (L1).

Referring to fig. 2, a schematic structural diagram of an autonomous cloud according to an embodiment of the present application is shown.

As shown in fig. 2, the autonomous cloud is a basic substructure in the autonomous network structure, and is also a structural unit that enables the autonomous network to operate normally.

Under the condition that one autonomous cloud is configured correctly, the function of the autonomous network can be independently realized in the autonomous cloud.

When the autonomous cloud cannot be connected with the upper and lower autonomous clouds due to communication faults, the service in the autonomous network can still be realized in a single autonomous cloud, which is also the source of the name of the autonomous cloud (autonomous operation).

When the autonomous clouds can normally communicate with autonomous clouds on upper and lower layers, the autonomous clouds form an autonomous network with a larger range, and a service crossing the autonomous clouds can be realized.

In a specific implementation, each autonomous cloud includes a master server, a micro cloud server, a terminal, and a switching network.

1. Master control server

The main control server is a centralized control node of the autonomous cloud, and the realized functions mainly comprise management of equipment in the autonomous cloud, realization of services inside and across the autonomous clouds, management communication of the autonomous network to realize higher-level management and the like.

In each autonomous cloud, the master control server and the micro cloud servers are accessed to a switching network, namely the master control server can be connected with a plurality of micro cloud servers through the same switching network, the switching network and the devices connected with the switching network jointly form the master control micro cloud of the autonomous cloud, the number of the master control micro clouds in the autonomous cloud is one, and the devices in the master control micro clouds can be connected in various topological types such as tree type, star type, full switching and the like.

Generally, a device in an autonomous network first needs to register on a master control server, and then accesses the autonomous network through a network access process, and a device which is not registered cannot access the network and cannot obtain a service provided by the autonomous network.

Referring to fig. 3, a schematic structural diagram of a master server according to an embodiment of the present application is shown.

As shown in fig. 3, the main control server 300 mainly includes a network transceiver module 301, a device management module 302, a multicast management module 303, a service processing module 304, and other modules.

Wherein:

the network transceiver module 301 is responsible for receiving and sending data packets, and when receiving a data packet, it checks whether the data packet conforms to the packet format of the autonomous network and whether the data packet is a packet to be sent to the main control server, and if the data packet conforms to the requirement, it distributes the data packet to the device management module 302, the multicast management module 303, and the service processing module 304 according to the message type in the data packet.

The device management module 302 is responsible for processing protocols related to the network access states of devices in the autonomous clouds and the access states between adjacent autonomous clouds, maintaining tables related to the states, and implementing processes such as network access and network logout of the devices, and access and disconnection between adjacent autonomous clouds.

The multicast management module 303 is responsible for processing a protocol related to a multicast data stream within the autonomous cloud or a multicast data stream across the autonomous cloud, maintaining a table related to the data streams, and implementing processes such as creation and destruction of a data stream transmitting end, addition and deletion of a data stream receiving end, management of a data stream across the autonomous cloud, and the like.

The service processing module 304 is responsible for processing protocols related to various autonomous network services, maintaining tables related to the services, and implementing processes of services such as live broadcast, video telephone, video conference, and the like.

2. Micro cloud server

The micro cloud server is an exchange core of the autonomous cloud, and in most cases, communication data sent by equipment in the autonomous network is forwarded to a final destination through the micro cloud server.

Further, the micro cloud server comprises a boundary router, a terminal sub-control server and a boundary sub-control server.

2.1 sub-control server

The terminal sub-control server and the boundary sub-control server are also called sub-control servers, and the sub-control servers are data forwarding nodes of the autonomous cloud and are provided with an uplink interface and a downlink interface. The uplink interface is used for being connected to a main control micro cloud of the autonomous cloud, the downlink interface can be connected with a terminal or a boundary router in other autonomous clouds through the same exchange network, and the exchange network and equipment connected with the exchange network form a sub-control micro cloud of the autonomous cloud.

The terminal sub-control server and the terminal are accessed into another switching network, and the corresponding sub-control micro-cloud is also called as the terminal sub-control micro-cloud.

The boundary sub-control server and the boundary router are connected to another switching network, and the corresponding sub-control micro-cloud is also called as the boundary sub-control micro-cloud.

In this embodiment, the master control cloudlet and the slave control cloudlet may be collectively referred to as a cloudlet.

Assuming that the hierarchical structure of the autonomous clouds is 4 layers, and the micro-cloud layer inside each autonomous cloud is 2 layers, the hierarchical structure of the micro-clouds in the whole autonomous network is 8 layers.

The devices in the sub-control micro-cloud can be connected in various topological types such as tree type, star type, full exchange and the like.

Each sub-control server in the master control micro-cloud can correspond to one sub-control micro-cloud, and the sub-control micro-cloud and the master control micro-cloud are connected by multiplexing the same sub-control server.

Because the micro cloud server can be simultaneously accessed into two different micro clouds, the micro clouds can be connected with each other through the micro cloud server, and the following rules need to be met during connection:

the sub-control micro-clouds in the autonomous cloud cannot be connected with each other;

when a master control micro cloud and a sub-control micro cloud in the autonomous cloud are connected, an uplink interface of a micro cloud server is connected into the master control micro cloud, and a downlink interface is connected into the sub-control micro cloud;

the main control micro cloud can be connected with the sub-control micro cloud in the upper autonomous cloud, an uplink interface of the micro cloud server is connected with the sub-control micro cloud, and a downlink interface is connected with the main control micro cloud;

The master control micro cloud can be connected with the sub-control micro cloud in the upper autonomous cloud only;

the sub-control micro cloud can be connected with a main control micro cloud in the lower autonomous cloud, an uplink interface of the micro cloud server is connected with the sub-control micro cloud, and a downlink interface is connected with the main control micro cloud;

the sub-control micro-cloud can be connected with the main control micro-clouds in the lower-layer autonomous clouds.

The sub-control server is also an auxiliary control node of the autonomous cloud, and can simply manage other devices in the sub-control micro-cloud and share part of functions of the main control server.

It should be noted that the terminal sub-control server and the boundary sub-control server are role differentiation, and one server may be an independent terminal sub-control server, an independent boundary sub-control server, or both a terminal sub-control server and a boundary sub-control server.

Referring to fig. 4, a schematic structural diagram of a control server according to an embodiment of the present application is shown.

As shown in fig. 4, the slave server 400 mainly includes a network interface module 401 (an uplink interface module and a downlink interface module), a switching engine module 402, and a protocol processing module 403.

The network interface module 401 is responsible for receiving and sending data packets, and when receiving, it will check whether the data packets conform to the set receiving filtering rule, if so, it will be handed to the switching engine module 402 for processing, and when sending, it will send the data packets from the switching engine module to other devices through the network interface.

The switching engine module 402 is responsible for forwarding the data packet, and after receiving the data packet from the network interface module 401 and the protocol processing module 403, modifies the relevant field of the data packet according to the address information in the data packet and an internal table, and then delivers the modified data packet to the network interface module 401 or the protocol processing module 403 for further processing.

The protocol processing module 403 is responsible for processing the autonomous network protocol, and implements functions of receiving the data packet from the switching engine module 402, processing the data packet according to the autonomous network protocol, configuring an internal table as needed, and delivering the data packet to the switching engine module 402 for further processing.

2.2, border routers

The boundary router is also a data forwarding node of the autonomous cloud, can be simultaneously connected to two layers of autonomous clouds, and can realize data forwarding across the autonomous clouds.

The boundary router is provided with an uplink interface and a downlink interface, the downlink interface is used for being connected to a main control micro cloud of one autonomous cloud, and the uplink interface is used for being connected to a sub-control micro cloud of another autonomous cloud.

At the moment, two adjacent layers of autonomous clouds are connected by multiplexing the same boundary router, after the autonomous clouds are connected, the autonomous clouds connected through the downlink interface are called lower-layer autonomous clouds, and the autonomous clouds connected through the uplink interface are called upper-layer autonomous clouds.

A plurality of autonomous clouds are interconnected by border routers in this manner to form a hierarchically distributed network.

Referring to fig. 5, a schematic structural diagram of a border router according to an embodiment of the present application is shown.

As shown in fig. 5, the border router 500 mainly includes a network interface module 501 (an uplink interface module, a downlink interface module), a switching engine module 502, and a protocol processing module 503.

The network interface module 501 is responsible for receiving and sending data packets, and when receiving, it will check whether the data packets conform to the set receiving filtering rules, if so, it will be sent to the switching engine module 502 for processing, and when sending, it will send the data packets from the switching engine module 502 to other devices through the network interface.

The switching engine module 502 is responsible for forwarding data packets, and after receiving the data packets from the network interface module 501 and the protocol processing module 503, modifies related fields of the data packets according to rules by combining internal tables according to address information in the data packets, and then sends the data packets to the network interface module 501 or the protocol processing module 503 for further processing.

The protocol processing module 503 is responsible for processing the autonomous network protocol, and implements functions of receiving the data packet from the switching engine module 502, processing the data packet according to the autonomous network protocol, configuring an internal table as needed, and delivering the data packet to the switching engine module 502 for further processing.

3. Terminal device

A terminal is a device that provides services to users in an autonomous network, such as a set-top box, a streaming media gateway, a code board, a memory, a media compositor, etc.

Referring to fig. 6, a schematic structural diagram of a terminal according to an embodiment of the present application is shown.

As shown in fig. 6, the terminal 600 mainly includes a network interface module 601, a data processing module 602, and a protocol processing module 603.

The network interface module 601 is responsible for receiving and sending data packets, and during receiving, it checks whether the data packets conform to the packet format of the autonomous network and whether the data packets are packets sent to the terminal, and if so, it distributes the data packets to the data processing module 602 and the protocol processing module 603 according to the message type in the data packets.

The data processing module 602 is responsible for processing service data related to the terminal.

The protocol processing module 603 is responsible for processing the autonomous network protocol, and implementing a network access flow and an autonomous network service flow (such as live broadcast, video telephone, video conference, etc.) of the terminal.

For example, if the terminal is a set-top box, the data processing module 602 is a video/audio codec engine module, and may compress and encode video/audio digital signals captured by itself according to various standards, and decompress and restore various video/audio encoded data into digital signals.

For another example, if the terminal is a code board, the data processing module 602 is a video/audio coding engine module, and can compress and code the video/audio digital signal captured by itself according to various standards.

For another example, if the terminal is a memory, the data processing module 602 is a disk array module, and may store information in the received service data on a disk or convert information on the disk into service data and transmit the service data.

4. Switching network

Switching networks are used to provide underlying network communication capabilities to autonomous networks so that devices connected to the same switching network can communicate with each other.

In one example, the switching network is an ethernet network, i.e., devices may communicate based on a standard ethernet protocol.

According to the actual situation of the ethernet, after the device accesses the master control clout or the slave control clout, various topologies can be formed, such as full-connected, star-shaped, tree-shaped, and so on.

The communication process between devices differs in different topologies.

Network parameters of autonomous network

1. Logical device type

The devices in the autonomous network have a logical device type, which is used to distinguish the functions implemented by the devices, and different physical entities can be implemented as logical devices of the same type.

For example, the logical device types include a master server, a micro cloud server (a terminal slave server, a boundary router), a terminal, and the like.

2. Logical device identification

The devices in the autonomous network have a logical device identification which is used to distinguish between devices of the same logical device type.

The logical device type and logical device identification are unique identifiers of devices in the autonomous network.

3. Logical port address

The network interface of the device connected to the autonomous network will be assigned an 8-bit logical port address when the device is brought into the network.

The logical port address is unique inside the connected micro cloud (master control micro cloud or sub-control micro cloud), usually represented by 16 systems, and the value range is 0x01-0xfe, that is, a total of 254 network interfaces can be accessed in the same micro cloud.

For a distributed control server or a border router, two interfaces of the distributed control server or the border router access two different micro clouds, and the assigned logical port addresses may be the same or different.

4. Logical addresses

The logical address is used to locate the network interface of the device. If a device accesses an autonomous network using multiple network interfaces, each network interface will have its own independent logical address.

The logical addresses include local logical addresses, logical address prefixes, and global logical addresses.

4.1, local logical Address

The network interfaces of the devices connected to the autonomous network are each assigned, when the device is connected to the network, a local logical address of 16 bits, which is unique within the autonomous cloud to which the device is connected and is usually represented by 16.

The local logical address is automatically generated by a logical port address within the cloudlet.

For a network interface within the master clouding, the local logical address is < logical port address of the interface within the master clouding > 00.

For the network interface in the sub-control micro cloud, the local logical address is < the logical port address of the uplink interface of the sub-control server in the main control micro cloud > < the logical port address of the interface in the sub-control micro cloud >.

For a border router, two interfaces of the border router access two different autonomous clouds, so that local logical addresses of the two autonomous clouds are unique in the corresponding autonomous cloud.

4.2 logical Address Prefix

Each autonomous cloud will be assigned a logical address prefix according to its location throughout the autonomous network.

The prefix of the logical address is 1 numerical value of 48 bits, and is divided into 3 sections, and each section is 16 bits. Logical address prefixes are typically represented in 16-ary notation, such as 12D4-56C 8-A07F.

The logical address prefixes of the respective layers of autonomous clouds are formed according to the following rules:

the logical address prefix of the layer 1 autonomous cloud has the composition rule of < access logical address 4> - < access logical address 3> - < access logical address 2 >;

the logical address prefix of the layer 2 autonomous cloud has the composition rule of < access logical address 4> - < access logical address 3> -0000;

the logical address prefix of the 3 rd layer autonomous cloud has the composition rule of < access logical address 4> -0000-;

the logical address prefix of the 4 th-layer autonomous cloud has the composition rule of 0000-;

wherein:

the < access logical address 2> represents a local logical address of a boundary router used when the layer 1 autonomous cloud is accessed to the layer 2 autonomous cloud in the layer 2 autonomous cloud;

the < access logical address 3> represents a local logical address of a boundary router used when the layer 2 autonomous cloud is accessed to the layer 3 autonomous cloud in the layer 3 autonomous cloud;

the < access logical address 4> represents a local logical address of a boundary router used when the layer 3 autonomous cloud is accessed to the layer 4 autonomous cloud in the layer 4 autonomous cloud;

4.3 Global logical Address

The network interfaces of the devices connected to the autonomous network are assigned a global logical address that is unique throughout the network when the devices are brought into the network.

The global logical address is 1 64-bit value, divided into 4 segments, each segment being 16-bit.

Global logical addresses are typically represented in 16, such as 12D4-56C8-A07F-3B 9E.

The global logical address can be formed by the local logical address of the network interface, the logical address prefix of the autonomous cloud and the hierarchy of the autonomous cloud according to the following rules:

the global logical address of the layer 1 autonomous cloud has a composition rule of (logical address prefix of the autonomous cloud > - < local logical address of the network interface >);

the global logic address in the layer 2 autonomous cloud has a composition rule of < first 2 segments of the logical address prefix of the autonomous cloud > - < local logic address of network interface > -0000;

the global logic address in the 3 rd layer autonomous cloud has the composition rule of < 1 st segment of the logical address prefix of the autonomous cloud > - < the local logic address of the network interface > -0000-;

the global logic address in the 4 th layer autonomous cloud has the composition rule of < the local logic address of the network interface > -0000-;

5. device number

The device number is used to locate the device in the traffic of the autonomous network, which is usually associated with the user using the autonomous network.

When the equipment of a certain user is replaced due to failure, the original equipment number can be bound to the new equipment without changing the equipment number.

The device number includes a local device number, a device number prefix, and a global device number.

5.1 local device number

Devices connected to the autonomous network are each assigned a local device number when the device is networked. The number is unique inside the autonomous cloud accessed by the device, and is a 5-bit 10-system number, namely the valid range is 00000-99999. Where the local device number 00000 is reserved and cannot be used to represent an actual device.

For the border router, two interfaces of the border router access two different autonomous clouds, so that the local device numbers of the two autonomous clouds are only unique in the corresponding autonomous clouds.

5.2 device number Prefix

Each autonomous cloud will be assigned a device number prefix based on its location throughout the autonomous network.

The prefix of the device number is a 15-bit 10-system number which is divided into 3 segments, and each segment is a 5-bit 10-system number. Such as 12345 vs 67890 vs 33333.

The construction rule of the device number prefixes of each layer of autonomous cloud is as follows:

the device number prefix of the layer 1 autonomous cloud has the composition rule of < access device number 4> - < access device number 3> - < access device number 2 >;

the device number prefix of the layer 2 autonomous cloud has a composition rule of < access device number 4> - < access device number 3> -00000;

The device number prefix of the layer 3 autonomous cloud has the composition rule of < access device number 4> -00000;

the device number prefix of the layer 4 autonomous cloud has the composition rule of 00000-;

wherein:

the access equipment number 2 represents the local equipment number of the boundary router used by the layer 1 autonomous cloud when accessing the layer 2 autonomous cloud in the layer 2 autonomous cloud;

the access equipment number 3 represents the local equipment number of the boundary router used by the layer 2 autonomous cloud when accessing the layer 3 autonomous cloud in the layer 3 autonomous cloud;

the < access logical address 4> represents the local equipment number of the boundary router used when the layer 3 autonomous cloud is accessed to the layer 4 autonomous cloud in the layer 4 autonomous cloud;

5.3 Global device number

Devices connected to the autonomous network are assigned a globally unique device number when the device is connected to the network.

The global device number is a 20-digit 10-digit number, and is divided into 4 segments, and each segment is a 5-digit 10-digit number. Such as 12345-.

The global device number may be formed by a local device number of the device, a device number prefix of the autonomous cloud, and a hierarchy of the autonomous cloud according to the following rule:

The global device number of the layer 1 autonomous cloud has a composition rule of < device number prefix > -of the autonomous cloud < local device number >;

the global device number in the layer 2 autonomous cloud has a composition rule of < first 2 segments of device number prefix of the autonomous cloud > - < local device number of the device > -00000;

the global device number in the 3 rd layer autonomous cloud has the composition rule of 1 st segment of device number prefix of the autonomous cloud- < the local device number of the device > -00000 and 00000;

the global device number in the 4 th layer autonomous cloud has a composition rule of < the local device number of the device > -00000;

6. micro cloud level

The micro-cloud hierarchy is used to represent the relative positions of the individual micro-clouds throughout the autonomous network.

The micro clouds in each autonomous cloud are divided into 2 layers, the main control micro cloud is arranged on the upper layer, and the sub control micro cloud is arranged on the lower layer. In this way, the total number of layers of micro clouds in the autonomous network with the 4-layer autonomous cloud structure is 8, that is, the master control micro cloud layer in the 4 th-layer autonomous cloud is 8, and the sub-control micro cloud layer in the 1 st-layer autonomous cloud is 1.

7. Micro cloud topology

The micro cloud topology is used for representing a connection mode among all devices in the same micro cloud.

The micro cloud topology is independent of the actual connection mode of the equipment in the exchange network, and is a logical topological relation. The micro cloud topology can affect the transmission path of the data packet in the micro cloud.

In particular implementations, the micro-cloud topology includes support for a star topology and a full-switch topology.

The star topology micro cloud comprises a central device, and most data among other devices need to be forwarded through the central device.

The full-exchange topology micro cloud has no central equipment, and data among the equipment can be directly sent point to point.

Because the terminal does not have a data forwarding function, the topology type of the terminal sub-control micro-cloud is a star topology and the central equipment is a corresponding terminal sub-control server.

8. Physical port information

The physical port information is used to describe parameters used when communicating with a network interface of a certain device over a switching network.

For the current ethernet implementation, information such as MAC address, ethernet type, and VLAN tag is included.

The MAC address indicates a destination MAC address used when transmitting a packet to the interface, the ethernet type indicates an ethernet frame type used when transmitting a packet to the interface, and the VLAN tag indicates VLAN information used when transmitting a packet to the interface.

To simplify the description, the description of the ethernet type and VLAN tag will generally be omitted hereafter and the entire physical port information will be replaced directly with the MAC address without causing ambiguity.

Data packet of three, autonomous network

1. Data packet definition

The data packet of the autonomous network mainly comprises the following parts: ethernet header, autonomous network header, payload (pdu), CRC.

The ethernet header can be further divided into: the Destination MAC Address (DMAC), the Source MAC Address (SMAC), and the Ethernet Type (ETYPE), and a VLAN header (VLAN) may be included in the ethernet header as necessary.

The autonomous network header can be further divided into: packet type (VTYPE), Reserved bytes (Reserved), destination autonomous network address (DA), and source autonomous network address (SA).

The specific format of the VLAN-less header is shown in the following table:

DMAC

SMAC

ETYPE

VTYPE

Reserved

DA

SA

Reserved

Payload

CRC

the specific format of the VLAN header is shown in the following table:

DMAC

SMAC

VLAN

ETYPE

VTYPE

Reserved

DA

SA

Reserved

Payload

CRC

wherein:

the Destination MAC Address (DMAC) may consist of 6 bytes, indicating the MAC address of the network interface of the device receiving the packet;

the Source MAC Address (SMAC) may consist of 6 bytes, indicating the MAC address of the network interface of the device sending the packet;

the Ethernet Type (ETYPE) may consist of 2 bytes, representing the frame type of the ethernet;

the VLAN header may be composed of 4 bytes, indicating VLAN information used when transmitting packets using a VLAN;

the packet type (VTYPE) may be 1 byte, and represents the type of the packet (e.g., a connection packet, a unicast packet, a multicast packet, etc.);

Reserved bytes can consist of 1 byte, typically set to 0;

the destination autonomous network address (DA) may consist of 8 bytes, indicating the address in the autonomous network of the receiver receiving the packet, the meaning of which is determined by the packet type;

the source autonomous network address (SA) may consist of 8 bytes, indicating the address in the autonomous network of the recipient sending the packet, the meaning of which is determined by the packet type;

the Payload stores the PDUs of the autonomous network, and the length of the PDUs is related to the type of the data packets. For example, the multicast packet may be 288 or 1056 bytes in length, and the connection packet and the unicast packet may be 64, 288 or 1056 bytes in length.

Of course, Payload is not limited to the above 3 lengths, and other lengths may be used, which is not limited in the embodiments of the present application.

The CRC may consist of 4 bytes, which is calculated in accordance with the standard ethernet CRC algorithm.

2. Autonomous network address

There are 3 different addresses in the autonomous network, which are a connection address, a unicast address, and a multicast address.

Wherein:

the connection address is used in the network entry process of the device, and its 8 bytes have the same value, such as 0x 01010 x 01010 x 01010 x 0101. The connection address is used for distinguishing equipment accessed to the same micro cloud;

The unicast address is a global logical address of the network interface, such as 0x 01020 x 03040 x 05060 x 0708;

the multicast address is used for distinguishing multicast data streams in the same autonomous cloud, and the multicast address can only be used as a destination autonomous network address but not as a source autonomous network address.

The multicast address may use the last 4 bytes of the 8 bytes, and the first 4 bytes are fixed to all 0, such as 0x 00000 x 00000 x 00120 x 3456.

3. Type of data packet

There are 3 types of packets in an autonomous network: a connection packet, a unicast packet, a multicast packet.

Wherein:

the connection packet is used in the network access flow of the equipment, and the destination autonomous network address and the source autonomous network address of the connection packet are connection addresses which respectively represent a receiving party and a sending party of the connection packet;

the unicast packet is used after the equipment is accessed to the network and is used for transmitting Protocol Data Units (PDU) between the equipment, and a target autonomous network address and a source autonomous network address of the unicast packet are unicast addresses and respectively represent a receiver and a sender of the unicast packet;

the multicast packet is used after the devices access the network and is used for transmitting data PDU between the devices, the destination autonomous network address of the multicast packet is a multicast address, the source autonomous network address of the multicast packet is a unicast address, and the destination autonomous network address and the source autonomous network address respectively represent a receiver and a sender of the multicast packet.

In order to distinguish different data packets, the following convention can be made in advance:

the value of the ethernet type is 0x 0800;

the packet type value of the connected packet is 0x 10;

the packet type value of the unicast packet is 0x 02;

the packet type value of the multicast packet is 0x 81.

When a specific part of the packet is described later, description of the ethernet type and the VLAN header will be generally omitted.

4. Data packet transmission

4.1, connect the package

The connection packet does not support forwarding, and can only be transmitted between two devices in the same clouding.

The connection packet indicates a sender and a receiver of the data packet using a connection address. The 8 bytes of the connection address all have the same value, and the value is usually the logical port address of the network interface of the sender or the receiver.

4.1.1, non-Forwarding node behavior

For a main control server and a terminal, when a connection packet is sent, a destination MAC address needs to be set as an MAC address of a receiver, a source MAC address needs to be set as an own MAC address, a destination autonomous network address needs to be set as a connection address of the opposite side, and an autonomous network address needs to be set as an own connection address. When receiving the connection packet, it is necessary to check whether the destination MAC address is its own MAC address.

4.1.2 Forwarding node behavior

For the branch control server and the boundary router, two Ethernet transmission matching tables are maintained internally. The two tables correspond to two network interfaces, the downlink interface is a port 0, the corresponding matching table is a port 0, the uplink interface is a port 1, and the corresponding matching table is a port 1. Each matching table contains 256 table entries corresponding to 8-bit logical port addresses. Each entry includes an ethernet MAC address (physical port information) and a transmission flag bit. A flag bit of 0 indicates that the port is invalid and the MAC address is meaningless. A flag bit of 1 indicates that the port is valid, and the MAC address is the destination MAC address used when sending packets to the port.

When the forwarding node sends the connection packet, the source autonomous network address is set as the own connection address, the source MAC address is set as the MAC address of the sending interface, and the target autonomous network address is set as the connection address of the other side. When setting the destination MAC address, firstly, the corresponding table item in the Ethernet transmission matching table is searched according to the connection address of the other side. For example, if the connection address of the opposite party is 0x 34340 x 34340 x 34340 x3434, and the connection packet needs to be sent to port 1, the 0x34 entry in the ethernet transmission matching table No. 1 is queried. If the sending flag bit is 0, the connection packet is not sent, and if the sending flag bit is 1, the destination MAC address is set to be the MAC address in the table entry and then the connection packet is sent.

When receiving the connection packet, the forwarding node needs to check whether the destination MAC address is the MAC address of the receiving interface.

4.2 unicast packet

Unicast packets use unicast addresses to indicate the sender and receiver of a data packet. The unicast packet can be transmitted from one micro cloud to another micro cloud through the forwarding of the data forwarding node, and the communication of the equipment in the full-autonomous network range is realized.

4.2.1 non-Forwarding node behavior

For a main control server and a terminal, when a unicast packet is sent, a source autonomous network address is required to be set as a global logic address of the main control server and the terminal, a source MAC address is required to be set as an MAC address of the main control server and the terminal, a destination autonomous network address is required to be set as a global logic address of a receiver, and a destination MAC address is required to be set as an MAC address corresponding to a next receiver of the unicast packet.

For the terminal, the next receiver of the unicast packet is the port 0 of the sub-control server belonging to the micro cloud.

For the master server, the next receiver of the unicast packet needs to calculate according to the following rule:

when the autonomous cloud level is 1, comparing whether the global logic address of the receiver is the same as the first 6 bytes of the global logic address of the receiver, if so, setting the local logic address of the next receiver as the 7 th byte and the 8 th byte of the global logic address of the receiver, and if not, setting the next receiver of the unicast packet as the port 0 of the boundary router in the master control micro cloud;

When the autonomous cloud level is 2, comparing whether the global logic address of the receiver is the same as the first 4 bytes of the global logic address of the receiver, if so, setting the local logic address of the next receiver as the 5 th byte and the 6 th byte of the global logic address of the receiver, and if not, setting the next receiver of the unicast packet as the port 0 of the boundary router in the main control micro cloud;

when the autonomous cloud level is 3, comparing whether the global logic address of the receiver is the same as the first 2 bytes of the global logic address of the receiver, if so, setting the local logic address of the next receiver as the 3 rd and 4 th bytes of the global logic address of the receiver, and if not, setting the next receiver of the unicast packet as the port 0 of the boundary router in the main control micro cloud;

when the autonomous cloud level is 4, setting the local logic address of the next receiver as the 1 st byte and the 2 nd byte of the global logic address of the receiver;

finding the corresponding equipment according to the local logic address of the next receiver;

if the device is a boundary router in the master control micro cloud, the next receiver of the unicast packet is the port 0 of the boundary router in the master control micro cloud;

if the device is not a boundary router in the master control micro cloud, checking the topology type of the master control micro cloud;

If the topology type of the master control micro cloud is star, the next receiver of the unicast packet is the port 1 of the central equipment in the master control micro cloud;

if the topology type of the master control micro cloud is full exchange, whether the equipment is a sub-control server is checked;

if the equipment is the sub-control server, the next receiver of the unicast packet is the port 1 of the sub-control server;

if the equipment is not the sub-control server, the equipment is the equipment under a certain sub-control micro cloud, and the next receiver of the unicast packet is the number 1 port of the sub-control server of the sub-control micro cloud;

when the main control server and the terminal receive the unicast packet, whether the destination MAC address is the own MAC address or not and whether the destination autonomous network address is the own global logic address or not are required to be checked.

4.2.2 Forwarding node behavior

For the branch control server and the boundary router, after the branch control server and the boundary router are connected to the network, the global logic addresses of the port 0 and the port 1 and the layer of the micro cloud corresponding to the port 0 in the autonomous network can be known.

A protocol processing module in a specified data forwarding node in the autonomous network uses the global logic address of the port 0 as a unicast address of the protocol processing module and communicates with other equipment.

When a forwarding node receives a unicast packet from a port 0 or a port 1, it needs to check whether a destination MAC address is the MAC address of a receiving interface, and then calculates the next receiver of the unicast packet according to the destination autonomous network address, the global logical address of the port 0 and the micro cloud level.

Suppose the destination autonomous network address is d8.d7.d6.d5.d4.d3.d2.d1, and the own port 0 global logical address is s8.s7.s6.s5.s4.s3.s2.s 1. Where D8 through D1, S8 through S1 represent 1 byte in the address, respectively.

Before calculation, a target autonomous network address and a port 0 global logic address are divided into 3 parts according to a port 0 micro-cloud layer, wherein the 3 parts are respectively called as an address 2, an address 1 and an address 0.

The following table is a method of partitioning addresses:

4 cases of the next receiver time division are calculated:

if the 3 parts of the two addresses are the same, the next receiver is the receiver, and the data packet is handed to an internal protocol processing module for processing without forwarding;

if only the address 0 part of the two addresses is different, the next receiver is positioned in the micro cloud to which the port 0 belongs, and the corresponding logical port address is the address 0 part of the destination autonomous network address;

if the address 2 parts of the two addresses are the same but the address 1 parts are different, the next receiver is positioned in the micro cloud to which the No. 1 port belongs, and the corresponding logical port address is the address 1 part of the target autonomous network address;

if the addresses 2 of the two addresses are different, the next receiver is a special device called an upper-layer forwarding node in the micro cloud (master control micro cloud or sub-control micro cloud) to which the port 1 belongs, and the logical port address of the special device is obtained when the forwarding node accesses the network;

And if the calculation is needed to be forwarded after the calculation is finished, inquiring a corresponding table entry in an Ethernet matching table of a corresponding interface according to the calculation result, if the sending flag bit is 0, not sending the unicast packet, if the sending flag bit is 1, setting the destination MAC address as the MAC address in the table entry, and setting the source MAC address as the MAC address of the corresponding interface and then sending.

When the internal protocol processing module sends a unicast packet, a global logic address with a control network address of 0 port is set, and a target autonomous network address is set as a global logic address of a receiver. And then calculating the next receiver of the unicast packet according to the global logical address of the receiver, the own global logical address of the port 0 and the micro cloud level. The calculation method is the same as the method of calculating the next receiver from the unicast packet on port 0 or port 1, and then the method of setting the destination MAC address and the source MAC address is the same.

There are point-to-multipoint data communication scenarios in the services of the autonomous network, for example, many people watch a live concert simultaneously, a large number of participants watch the audio and video of the speaking party simultaneously in a video conference, and so on.

In these data communication scenarios, if a point-to-point unicast mechanism is still used for communication, the actual network bandwidth is limited, which may not be realized, so that for these data communication scenarios, the autonomous network implements a multicast communication mechanism, and can perform point-to-multipoint data communication in the whole network range without consuming a large amount of bandwidth.

The characteristics of the multicast communication mechanism in the single autonomous cloud include at least one of the following:

the multicast address is used as a unique identifier for distinguishing multicast data streams, namely the multicast address of the data stream sent by the same sender is unchanged during the survival period of the data stream no matter how many receivers exist;

the multicast address is dynamically maintained, distributed in real time when the data stream is generated, and released in real time when the data stream disappears;

the data sink dynamic maintenance can add or delete the receiver of the data stream at any time during the life of the data stream;

the master control server uniformly calculates the propagation path and the consumed bandwidth of the data stream in the autonomous cloud;

the master control server uniformly controls the data forwarding nodes on the data stream propagation path to forward data;

according to the actual propagation path of the data stream, when one or more devices need to receive or forward the data stream in the same micro cloud, the data stream is forwarded through the data forwarding node.

The characteristics of the multicast communication mechanism in the case of multiple autonomous clouds include at least one of the following:

the multicast address is unique in the autonomous cloud, and needs to be replaced when the autonomous cloud is crossed;

each autonomous cloud independently maintains the multicast address and related information of the autonomous cloud;

The master control servers of all autonomous clouds interact through protocols of autonomous networks, and information of multicast data streams of the autonomous clouds is cooperatively maintained;

the boundary router is responsible for forwarding the multicast data stream and replacing the multicast address when the autonomous cloud is crossed;

and the master control servers uniformly control the boundary routers on the data stream propagation path to forward data and replace multicast addresses.

In the multicast communication mechanism, a device that sends a data stream is referred to as a data source, a device that receives the data stream is referred to as a data sink, and a propagation path between the data source and the data sink is referred to as a multicast link.

In a multicast link, a transmitted data packet is a multicast packet, and a multicast packet sent by a data source may reach a data sink after being forwarded by one or more data forwarding nodes.

The data forwarding nodes are divided into data forwarding nodes inside the autonomous cloud and data forwarding nodes on boundaries of the autonomous cloud. And the data forwarding nodes in the autonomous cloud comprise terminal sub-control servers and boundary sub-control servers. The data forwarding nodes on the boundary of the autonomous cloud are boundary routers.

When the data source and the data sink belong to the same autonomous cloud, the multicast packet is transmitted from the data source and then is forwarded by one or more internal data forwarding nodes in the autonomous cloud to reach the data sink.

When a data source and a data sink belong to different autonomous clouds, after a multicast packet is sent from the data source, the multicast packet firstly reaches a boundary router after being forwarded by one or more internal data forwarding nodes in the autonomous cloud where the data source is located, then multicast address replacement is carried out on the boundary router, the multicast address is replaced by a multicast address in the autonomous cloud of the next hop, then forwarding is continuously carried out in the autonomous cloud of the next hop, forwarding possibly needs to be carried out in the autonomous clouds according to the position of the data sink, the multicast packet reaches the autonomous cloud where the data sink is located after being subjected to multiple address replacement by one or more boundary routers, and finally the data sink is reached by forwarding in the autonomous cloud where the data sink is located.

For better describing multicast communication, a transmission path of a multicast data stream from a data source to a data sink is referred to as a global multicast link, and a transmission path of the global multicast link inside each autonomous cloud is referred to as a local multicast link.

The data sources and data sinks in the global multicast link are also called global data sources and global data sinks.

There are also concepts of data sources and data sinks in the local multicast link, which are also called local data sources and local data sinks.

The global data source and the global data sink can be terminals, terminal sub-control servers or boundary sub-control servers.

The local data source and the local data sink can be terminals, terminal sub-control servers, boundary sub-control servers or boundary routers.

When the local data source is a terminal, the local data source is called a physical data source; when the local data source is a terminal sub-control server or a boundary sub-control server, the local data source is called a virtual data source; when the local data source is a border router, it is called a relay data source.

When the local data sink is a terminal, the local data sink is called a physical data sink; when the local data sink is a terminal sub-control server or a boundary sub-control server, the local data sink is called a virtual data sink; when the local data sink is a border router, it is called a relay data sink.

When the multicast packet carries out multicast address replacement on the boundary router, the multicast packets before and after replacement belong to the same path of multicast data stream. At this time, the boundary router is a local data sink in the autonomous cloud in the data source direction, and is also a local data source in the autonomous cloud in the data sink direction.

The multicast packet may also be subjected to multicast address replacement in the autonomous cloud, that is, a data forwarding node in the autonomous cloud replaces the multicast address in the multicast packet with another multicast address. At this time, the multicast packets before and after the replacement belong to different multicast data streams. The multicast packet before replacement belongs to the old multicast data stream, and the data forwarding node for address replacement is the global data sink of the old multicast data stream. The replaced multicast packet belongs to a new multicast data stream, and the data forwarding node for address replacement is the global data source of the new multicast data stream. I.e. the data forwarding node performing the address replacement is both the data sink and the data source.

When forwarding the multicast packet, the data forwarding node (terminal sub-control server, boundary router) determines how to forward the multicast packet by querying an internal multicast guide table and multicast information table.

1. Multicast guide table

The multicast guide table has 4 guide tables, which are respectively called as 0 number, 1 number, 2 number and 3 number, the guide tables of 0 number, 1 number, 2 number and 3 number can be used in the terminal sub-control server and the boundary sub-control server, and the guide tables of 1 number and 2 number can be used in the boundary router.

And the number of entries of each guide table is equal to the maximum number of multicast data streams supported in the autonomous cloud, and the index is carried out through the multicast address.

For example, the maximum number of 1M multicast data streams in the autonomous cloud is supported, the effective range of the multicast address is 0x00000000-0x000 ffffff, and the number of entries in each guide table is 1M.

The entry of the guide table No. 0 records the guide information when the multicast packet from port No. 0 is sent to port No. 0.

The entry of the direction table No. 1 records direction information when the multicast packet from port No. 0 is sent to port No. 1.

In the border router, the number of entries is determined by the autonomous cloud (lower autonomous cloud) accessed by port 0.

The entry of the direction table No. 2 records direction information when the multicast packet from port No. 1 is sent to port No. 0.

In the border router, the number of entries is determined by the autonomous cloud (upper autonomous cloud) accessed by port No. 1.

The entry of the direction table No. 3 records direction information when the multicast packet from port No. 1 is sent to port No. 1.

The guidance information includes a guidance mode and a replacement address list.

A steering mode of 0 indicates that no multicast packet needs to be transmitted in that direction, 1 indicates that transmission is required but no address replacement is required, 2 indicates that transmission is required and address replacement of a single multicast address is required, and 3 indicates that transmission is required and address replacement of multiple multicast addresses is required.

The replacement address list records multicast addresses for address replacement, the table does not contain multicast addresses when the guided mode is 0 or 1, the table contains 1 multicast address when the guided mode is 2, and the table contains a plurality of multicast addresses when the guided mode is 3.

2. Multicast information table

The multicast information table has 2 pieces of information, which are called as the information table No. 0 and the information table No. 1 respectively. And the number of entries of each information table is equal to the maximum number of multicast data streams supported in the autonomous cloud, and the indexing is carried out through the multicast address.

The table entry of the information table No. 0 records the address information when the multicast packet is sent to the port No. 0.

The table entry of the information table No. 1 records the address information when the multicast packet is sent to the port No. 1.

In the border router, the number of entries is determined by the autonomous cloud (upper autonomous cloud) to which port No. 1 is connected.

The address information contains 256 bits in total. 256 bits correspond to 256 interfaces in the micro cloud, and the position of the bit is the logical port address of the interface. A bit value of 0 indicates that no multicast packets need to be sent to the interface and a value of 1 indicates that a multicast packet needs to be sent to the interface.

For example, the 3 rd and 7 th bits in the 0x00012345 entry in the information table No. 1 are 1, which indicates that the packet with the multicast address 0x00012345 needs to be sent to two network interfaces with logical port addresses 0x03 and 0x07 at the same time when being sent to port No. 1.

When managing multicast data stream, the main control server mainly uses tables such as data source information table, data source index table and multicast routing table.

1. Data source information table

The number of entries in the data source information table is the same as the total multicast address, and the information of the corresponding multicast data stream is recorded. Each entry contains the following information:

the data source state: 0 indicates that the multicast data stream does not exist, and 1 indicates that the multicast data stream exists;

data source type: 1 represents that a data source is a terminal, namely a physical data source, 2 represents that the data source is a terminal sub-control server, namely a virtual data source, and 3 represents that a local data source is a boundary router, namely a relay data source;

Data source device number: a local device number of the data source;

data source channel number: when the data source types are 1 and 2, the data source type is meaningless, and when the data source type is 3, the data source type is used for distinguishing multiple paths of data streams sent by the same equipment;

multicast address before replacement: the data source type is meaningless when 1, the data source types are 2 and 3, the multicast address of the data stream before the multicast address replacement is carried out is shown, and the multicast address before the replacement is 0, the multicast data stream of the path is not replaced by any multicast data stream;

global data source device number: the data source types are meaningless when 1 and 2, and the data source type is 3, the data source type represents the global equipment number of the global data source;

global data source channel number: the data source type is meaningless when 1 and 2, and the data source type is 3, the channel number of the global data source is represented;

data flow rate: representing the bandwidth occupied by the multicast data stream;

data stream media attribute: recording the properties of the multicast data stream, such as the type of the data stream (video, audio), the coding and decoding format, etc.;

data stream service attributes: recording data flow and service related attributes, such as belonging service type, global equipment number of a service initiator, and the like;

2. data source index table

And the data source index table is used for searching a corresponding multicast address according to the global device number and the channel number of the data source, and if the corresponding multicast address cannot be searched, the data source index table indicates that no corresponding multicast data stream exists in the self-autonomous cloud.

3. Multicast routing table

The multicast routing table is used for recording transmission paths of data streams in each micro cloud (master control micro cloud or sub-control micro cloud), and each table entry corresponds to routing information of one multicast data stream in a certain micro cloud. And searching the multicast routing table in a mode of a multicast address and a micro cloud number, and if the multicast routing table cannot be searched, indicating that the multicast data stream corresponding to the multicast address is not transmitted in the corresponding micro cloud.

The micro cloud number is used for distinguishing different micro clouds, and is defined as a logical port address of a manager of the micro cloud in the master control micro cloud.

Each entry of the multicast routing table consists of 256 bytes. Each byte corresponds to the routing information of a certain network interface in the micro cloud, and the position of the byte in the table entry is the logical port address of the corresponding network interface.

When the value of a byte in the table entry is 0, it indicates that the corresponding network interface does not receive the multicast data stream.

When the value of a byte in the table entry is the logical port address of the corresponding network interface, it indicates that the interface is the data source of the multicast data stream in the corresponding micro cloud, i.e. the multicast packets of other interfaces in the micro cloud come from the interface directly or indirectly.

When the value of a byte in the table entry is other values, it indicates that the data on the interface comes from the network interface corresponding to the value.

The following is an example of a multicast routing table:

byte position	1	3	5	10	30	100	150
								Byte content	5	5	10	10	10	30	30

The first row in the above table represents the number of bytes in 256 bytes, the second row represents the value at the corresponding byte, and the other bytes not listed have a value of 0.

It is assumed that the table indicates the routing information of the data stream with multicast address 0x00001234 in cloudlet No. 0x 78.

According to the definition, the source of the multicast data stream of the data stream with the multicast address of 0X00001234 in clout No. 0X78 is from the device X to which the interface with the logical port address of 10 belongs, then the multicast data stream is forwarded by the device X to the device Y to which the interface with the logical port address of 5 belongs and the device Z to which the interface with the logical port address of 30 belongs, the device Y forwards the multicast data stream to the two devices to which the interfaces with the logical port addresses of 1 and 3 belong, and the device Z forwards the data stream to the two devices to which the interfaces with the logical port addresses of 100 and 150 belong.

The transmission of the multicast packet is realized by the terminal sub-control server, the boundary sub-control server and the boundary router.

And after receiving a multicast packet, the terminal sub-control server or the boundary sub-control server judges whether the multicast packet meets the receiving and filtering rules of the multicast packet. And if so, inquiring a corresponding multicast guide table according to the receiving port of the multicast packet.

The multicast packet from the port 0 needs to be queried in the multicast guide table No. 0 and the multicast guide table No. 1, and the multicast packet from the port 1 needs to be queried in the multicast guide table No. 2 and the multicast guide table No. 3.

And after the inquiry, determining how to send the information according to the guiding information, and if the guiding mode is 0, not sending the information.

If the guide mode is 1, inquiring a multicast information table corresponding to an interface needing to be sent, determining the equipment corresponding to which logical port addresses the multicast packet needs to be sent according to the address information, then inquiring a sending matching table corresponding to a sending interface to obtain the MAC address (physical port information) of each equipment, finally replacing the destination MAC address of the multicast packet with the MAC address of the equipment needing to be sent, replacing the source MAC address with the MAC address of the sending interface, and then sending the MAC addresses in sequence, wherein several logical ports send several multicast packets.

If the guide mode is 2, a multicast information table corresponding to an interface needing to be sent is inquired, a replacement address in a replacement address list is used as index inquiry during inquiry, the equipment corresponding to which logical port addresses the multicast packet needs to be sent is determined according to the address information obtained through inquiry, then a sending matching table corresponding to a sending interface is inquired to obtain the MAC address (physical port information) of each equipment, finally, the destination MAC address of the multicast packet is replaced by the MAC address of the equipment needing to be sent, the source MAC address is replaced by the MAC address of the sending interface, the multicast address in the destination autonomous network address is replaced by the replacement address in a replacement address list and then is sent in sequence, and several multicast packets are sent by several logical ports.

If the guidance mode is 3, there are a plurality of replacement addresses in the replacement address list, and the processing may be performed for each replacement address in accordance with the processing flow when the guidance mode is 2.

After receiving a multicast packet, the border router judges whether the multicast packet meets the receiving and filtering rules of the multicast packet. If yes, inquiring a corresponding multicast guide table according to a receiving port of the multicast packet.

The multicast packet from the port 0 needs to query the multicast guide table No. 1, and the multicast packet from the port 1 needs to query the multicast guide table No. 2.

If the direction mode is 2, a multicast information table corresponding to an interface needing to be sent is inquired, a replacement address in the direction information is used as index inquiry during inquiry, the equipment corresponding to which several logical port addresses the multicast packet needs to be sent is determined according to the inquired address information, then a sending matching table corresponding to a sending interface is inquired to obtain the MAC address (physical port information) of each equipment, finally, the target MAC address of the multicast packet is replaced by the MAC address of the equipment needing to be sent, the source MAC address is replaced by the MAC address of the sending interface, the multicast address in the target autonomous network address is replaced by the replacement address in the direction information and then is sent in sequence, and several multicast packets are sent by several logical ports.

Referring to fig. 7, a flowchart illustrating steps of a service communication method of an autonomous network according to an embodiment of the present application is shown, which may specifically include the following steps:

and 701, respectively controlling the main control servers in the cloud to be powered on and initialized.

In an initialization stage, the main control server can know key information such as system parameters of the autonomous cloud and registration information of all devices in the autonomous cloud by reading information on the storage medium.

Wherein the system parameters of the autonomous cloud include one or more of:

a device number prefix of the autonomous cloud;

a logical address prefix of the autonomous cloud;

the micro cloud level of the micro cloud is controlled;

a micro cloud topology of a master control micro cloud;

a local device number of the master control server;

a logical device type of the master server;

a logical device identification of the master control server;

a logical port address of the master server;

MAC address of the master server.

The registration information of the device includes one or more of:

a local device number of the device;

a logical device type of the device;

a logical device identification of the device;

the logic port address list of the equipment-the sub-control server has 2 interfaces;

MAC address (physical port information) list of the equipment-the sub-control server has 2 interfaces;

The node types of the equipment, namely the terminal, the boundary router, the terminal sub-control server, the boundary sub-control server and the like, can be understood as the large types of the equipment, and each large type is subdivided by the type of the logic equipment;

the local equipment number of a manager, namely equipment in the micro cloud which is responsible for managing other equipment, is a main control server in the main control micro cloud, and is a branch control server in the branch control micro cloud;

micro cloud topology of sub-control micro-clouds-sub-control server specific attributes;

local equipment number of the central equipment-star topology specific attribute;

the device management module of the master control server comprises main tables such as a device static information table, a device dynamic information table, an address number mapping table and an autonomous cloud access table.

The multicast management module of the main control server comprises main tables such as a data source index table, a data source information table, a multicast routing table and the like.

The device static information table is indexed by the local device number of the device, and records information that the device is basically unchanged during the operation of the master server, such as registration information of the device. The range of local device numbers is 00000-99999, so there are 100000 entries. The table entry uses a valid bit to indicate whether the device is registered. The device static information table is mainly initialized by device registration information on the storage medium.

The device dynamic information table also takes the local device number of the device as an index, and records the information that the device dynamically changes during the operation of the master server, such as the network access state of the device. After the device dynamic information table is initialized, all devices are in an unconnected state.

The address number mapping table takes the local logic address as an index, and can search the local equipment number corresponding to the address. If the device corresponding to the address does not exist, the corresponding local device number is 0. The address number mapping table is initialized by the registration information of the device.

The autonomous cloud access table is used for recording access states between the autonomous cloud access table and other autonomous clouds, and 65536 entries are used in the autonomous cloud access table by taking the local logic address of the boundary router used when the other autonomous clouds access the server as an index. Besides the access state, information such as the global device number and the global logic address of the master control server in the accessed autonomous cloud can be recorded in each table entry. After initialization, all the table entries of the autonomous cloud access table are in an unaccessed state.

And step 702, respectively controlling the terminal sub-control servers in the cloud to be powered on and initialized.

In the initialization stage, the terminal sub-control server can know the intrinsic parameters of the terminal sub-control server by reading the information on the storage medium, wherein the intrinsic parameters comprise the type of the logic device, the identification of the logic device, the MAC addresses of 2 interfaces and the like.

The terminal sub-control server comprises main tables such as an Ethernet transmission matching table, an equipment static information table, an equipment dynamic information table, a multicast guide table, a multicast information table and the like.

The device static information table takes the logical port address of the terminal in the sub-control micro-cloud as an index, and records the information that all terminals in the sub-control micro-cloud are basically unchanged during the operation of the server, such as the registration information of the device. The logical port address is 8bit, so there are 256 table entries. The table entry uses a valid bit to indicate whether the device is registered. The device static information table does not contain any devices after initialization.

The device dynamic information table also takes the address of the logical port of the terminal in the sub-control micro-cloud as an index, and records the information of the device which dynamically changes during the operation of the server, such as the network access state of the device. After the device dynamic information table is initialized, all devices are in an unconnected state.

And 703, electrifying and initializing the boundary sub-control servers in each autonomous cloud.

In the initialization stage, the boundary sub-control server can know the intrinsic parameters of the boundary sub-control server by reading the information on the storage medium, wherein the intrinsic parameters comprise the type of the logic device, the identification of the logic device, the MAC addresses of 2 interfaces and the like.

The boundary sub-control server and the terminal sub-control server have similar functions, and the contained tables are the same. That is, the table includes the main tables such as the ethernet transmission matching table, the device static information table, the device dynamic information table, the multicast guide table, and the multicast information table.

Step 704, the border routers in each autonomous cloud are powered on and initialized.

In the initialization stage, the boundary router can know the intrinsic parameters of itself by reading the information on the storage medium, including the type of the logical device, the identification of the logical device, the MAC addresses of 2 interfaces, etc.

The boundary router includes main tables such as an ethernet transmission matching table, a multicast guide table, and a multicast information table.

And step 705, respectively controlling the power-on initialization of the terminals in the cloud.

In the initialization stage, the terminal can know the inherent parameters of the terminal by reading the information on the storage medium, including the type of the logical device, the identification of the logical device, the MAC address of the interface, and the like.

And step 706, the master control server in each control cloud accesses and configures each device according to the registration information of each device.

And step 707, after the device accesses the network, the device initiates a service request to a master control server of the autonomous cloud to which the device belongs.

And step 708, the master control server processes the service request and performs service control in cooperation with the master control servers in other autonomous clouds.

In the service control, if a multicast data stream (user data) needs to be received and transmitted, the main control server calculates a local multicast link of the multicast data stream in the autonomous cloud, forms a global multicast link in the autonomous network through the cooperation with the main control servers in other autonomous clouds, and transmits a command to each relevant device in the autonomous cloud to which the global multicast link belongs, so that the receiving and transmitting of the multicast data stream are completed.

Referring to fig. 8, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application is shown, which may specifically include the following steps:

step 801, the terminal sub-control server accesses the main control server.

And step 802, the main control server and the terminal sub-control server maintain network access connection of the main control server and the terminal sub-control server through heartbeat.

And the terminal sub-control server reports the network access states of all terminals in the sub-control micro cloud to the main control server through heartbeat, and if the terminal sub-control server quits the network, all terminals in the sub-control micro cloud automatically quit the network.

And step 803, the main control server transmits the exchange node information to the terminal sub-control servers.

The exchange node information includes MAC address information (physical port information) corresponding to the terminal slave control server and other ports in the master control clout when data transmission is performed.

And step 804, the boundary sub-control server accesses the main control server.

Step 805, the main control server and the border sub-control server maintain the network access connection of the two parties through heartbeat.

And the boundary sub-control server reports the network access states of all boundary routers in the sub-control micro-cloud to the main control server through heartbeat, and if the boundary sub-control server quits the network, all boundary routers in the sub-control micro-cloud automatically quit the network.

In step 806, the main control server transmits the switching node information to the border sub-control servers.

The switching node information includes MAC address information (physical port information) corresponding to the boundary sub-control server and other ports in the main control micro-cloud when data transmission is performed.

In step 807, the border router in the master control micro cloud accesses the master control server through the downlink interface.

And 808, the master control server and the boundary router in the master control micro cloud maintain the network access connection of the master control server and the boundary router through heartbeat.

And the boundary router in the master control micro cloud reports the network access state between the uplink interface of the boundary router and the boundary sub-control server in the upper autonomous cloud to the master control server through heartbeat.

After a downlink interface and an uplink interface of the boundary router in the master control micro cloud are connected to the network, the boundary router can be connected with a master control server of the autonomous cloud to which the two interfaces are connected.

Step 809, the master control server transmits the exchange node information to the border router in the master control micro cloud.

The switching node information includes MAC address information (physical port information) corresponding to the boundary router in the master clouding and other ports in the master clouding during data transmission.

Step 810, the main control server transmits the device registration information to the terminal sub-control servers.

The equipment registration information comprises registration information of terminals in the sub-control micro cloud.

And step 811, accessing the terminal in the sub-control micro cloud to the terminal sub-control server.

And step 812, the terminal sub-control server and the terminal in the sub-control micro cloud maintain the network access connection of the both sides through heartbeat.

In step 813, the main control server transmits the device registration information to the border sub-control server.

The equipment registration information comprises registration information of the border router in the sub-control micro cloud.

And 814, accessing the boundary router in the sub-control micro-cloud to the boundary sub-control server.

And step 815, the boundary sub-control server and the boundary router in the sub-control micro cloud maintain the network access connection of the two parties through a heartbeat process.

Step 816, the border sub-control server transmits the exchange node information to the border router in the sub-control micro-cloud.

The switching node information includes MAC address information (physical port information) corresponding to the boundary router in the sub-control clout and other ports in the sub-control clout during data transmission.

It should be noted that, if the cloudlet topology of the master cloudlet is full exchange, the master server starts a network access process with all the devices in the master cloudlet at the same time.

If the micro cloud topology of the master control micro cloud is star-shaped, the master control server firstly starts a network access process with the central equipment in the master control micro cloud, continues to start a network access process with all the non-central equipment after the central equipment accesses the network, and if the central equipment leaves the network, all the non-central equipment automatically leaves the network.

Referring to fig. 9, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application may specifically include the following steps:

step 901, a master control server in each autonomous cloud controls a micro cloud server to access a master control server.

And step 902, the terminal sub-control servers in each autonomous cloud control the terminal to access the terminal sub-control server.

And step 903, controlling the border router to access the border sub-control server by the border sub-control server in each autonomous cloud.

In the master control micro-clouds of the autonomous clouds, a master control server controls micro-cloud servers (namely terminal sub-control servers, boundary sub-control servers and boundary routers) to access the master control server.

And in one sub-control micro-cloud of each autonomous cloud, the terminal sub-control server controls the terminal to access the terminal sub-control server.

And in the other sub-control micro-cloud of each autonomous cloud, the boundary sub-control server controls the boundary router to access the boundary sub-control server.

Referring to fig. 10, a flowchart illustrating steps of another autonomous network service communication method according to an embodiment of the present application is shown, which may specifically include the following steps:

step 1001, the master control server sends a device connection command to the micro cloud server.

In the master control micro cloud of the autonomous cloud, the master control server sends a device connection command to the micro cloud server according to the device registration information of the master control server.

The uplink interface of the border router is connected to the sub-control clouding of the upper layer of the autonomous cloud, and the downlink interface of the border router is connected to the main control clouding of the autonomous cloud.

The device connect command is transmitted using a connection packet, i.e. the type of the autonomous network address is a connection address.

8 bytes of the connection address of the master server are all 0xff, and 8 bytes of the connection address of the micro cloud server are all the logical port addresses in the master micro cloud.

In a specific implementation, the format of the device connect command may be as shown in the following table:

Step 1002, the master control server receives an equipment connection response sent by the micro cloud server after verifying that the equipment connection command belongs to the micro cloud server.

After receiving the device connection command (connection packet), the micro cloud server checks whether the device connection command is sent to the micro cloud server by the master control server, if so, records related information (including connection addresses of both sides) in the device connection command, then sends a device connection response (connection packet) to the master control server, and if not, continues to wait for the device connection command sent to the micro cloud server.

In one embodiment of the present application, the device connection command includes a logical device type and a logical device identifier, and the logical device type and the logical device identifier may uniquely represent one device.

In this embodiment, the micro cloud server determines whether the logical device type and the logical device identifier in the device connection command are the same as the logical device type and the logical device identifier of the micro cloud server; if yes, determining that the equipment connection command belongs to the equipment connection command; if not, determining that the equipment connection command does not belong to the equipment connection command.

In a specific implementation, the device connection response is transmitted using a connection packet, i.e. the type of the autonomous network address is a connection address.

In a specific implementation, the format of the device connection response may be as shown in the following table:

in the device connection command and the device connection response, the session identifier indicates a session identifier used in the current network access process, and a numerical value in the device connection response is the same as a numerical value in the device connection command.

The destination MAC address represents a destination MAC address used when the micro-cloud server sends a connection packet to the master control server in the network access process.

The Ethernet type represents the Ethernet type used when the micro cloud server sends the connection packet to the master control server in the network access process.

The VLAN label represents a VLAN label used when the micro cloud server sends a connection packet to the master control server in the network access process.

The reserved space is 8 bytes long in the device connect command and 18 bytes long in the device connect response.

In step 1003, the master control server sends an equipment authentication command to the micro cloud server to transmit the authentication parameters.

The device authentication command is transmitted using a connection packet, i.e. the type of the autonomous network address is a connection address.

The 8 bytes of the connection address of the master server are all 0xff, and the 8 bytes of the connection address of the micro cloud server are all the logical port addresses thereof.

The master control server sends an equipment authentication command (connection packet) to the micro cloud server, wherein the command comprises authentication parameters such as an authentication algorithm type and an authentication random number, and the command can be used for authentication between the master control server and the micro cloud server so as to improve the network security.

In a specific implementation, the format of the device authentication command may be as shown in the following table:

information element	Presence of	Format	Length of	Description of the invention
					Session identification	M	V	4
Authentication algorithm type	M	V	4
					Authenticating random numbers	M	V	4
Connection signaling check code	M	TLV	4

The authentication algorithm type represents an algorithm used in an authentication operation, and the authentication random number represents a random number used in the authentication operation and is generated by the master server.

Step 1004, the main control server receives the device authentication response sent by the micro cloud server after executing the authentication operation by using the authentication parameter.

The device authentication response is transmitted using a connection packet, i.e. the type of the autonomous network address is the connection address.

And the micro cloud server performs related authentication operation by adopting the authentication parameters sent by the master control server, packages the authentication operation result into an equipment authentication response (connection packet) and returns the equipment authentication response to the master control server.

In one embodiment of the present application, the authentication parameters include an authentication algorithm type, an authentication nonce.

In the embodiment of the application, the micro cloud server calls an authentication algorithm corresponding to the authentication algorithm type, and executes an authentication operation by using an authentication random number to obtain an authentication candidate result.

And the micro cloud server packages the authentication candidate result to an equipment authentication response and sends the equipment authentication response to the master control server.

Of course, the above authentication operations are only examples, and when the embodiment of the present application is implemented, other authentication operations may be set according to practical situations, and the embodiment of the present application is not limited to this. In addition, besides the above authentication operations, those skilled in the art may also adopt other authentication operations according to actual needs, and the embodiment of the present application is not limited thereto.

In a specific implementation, the format of the device authentication response may be as shown in the following table:

information element	Existence of	Format	Length of	Description of the invention
					Session identification	M	V	4
Authentication algorithm type	M	V	4
					Authenticating random numbers	M	V	4
Authentication calculation result	M	V	16	Authentication candidate result
					Connection signaling check code	M	TLV	4

In the device authentication command and the device authentication response, the main control server and the micro cloud server need to check whether the session identifier is the same as the session identifier in the device connection command, and if the session identifier is different from the session identifier in the device connection command, the current network access process is terminated.

Step 1005, the master control server judges whether the micro cloud server is successfully authenticated; if yes, go to step 1006.

In a specific implementation, the master control server may perform the same authentication operation using the authentication parameter to determine whether the authentication of the micro cloud server is successful.

Further, the master control server extracts a result of the authentication operation from the device authentication response of the micro cloud server, compares the result with a result of the self-executed authentication operation, and determines whether the micro cloud server is successfully authenticated.

If the authentication is successful, configuring the network access parameters through the equipment network access command, and if the authentication is failed, terminating the current network access process.

In this embodiment, the master control server invokes an authentication algorithm corresponding to the authentication algorithm type, and performs an authentication operation using the authentication random number to obtain an authentication reference result.

The master control server judges whether the authentication candidate result is the same as the authentication reference result; if so, determining that the authentication of the micro cloud server is successful; if not, determining that the micro cloud server fails in authentication.

Of course, the above-mentioned manner of authentication judgment is only an example, and when the embodiment of the present application is implemented, another manner of authentication judgment may be set according to the actual situation, and the embodiment of the present application is not limited thereto. In addition, besides the above authentication operation, a person skilled in the art may also adopt other authentication judgment modes according to actual needs, and the embodiment of the present application is not limited thereto.

Step 1006, the master control server sends a device network access command to the micro cloud server to transmit the network access parameter.

Step 1007, the master control server receives the device network access response sent by the micro cloud server after configuring the network access parameter.

The device network access command and the device network access response are transmitted by using a connection packet, namely the type of the autonomous network address is a connection address.

The method comprises the steps that a main control server sends a device networking command (connection packet) to a micro cloud server, wherein the command comprises information such as local logical addresses and local device numbers of the main control server and the micro cloud server, MAC addresses (physical port information) used when a unicast packet is sent to the main control server, and logical address prefixes and device number prefixes of autonomous clouds.

After receiving the device network access command, the micro cloud server records the relevant information in the command, and then sends a device network access response (connection packet) to the master control server.

In a specific implementation, the format of the device network entry command may be as shown in the following table (i.e., the network entry parameters include one or more of the following):

it should be noted that the destination MAC address, the ethernet type, and the VLAN tag are examples of physical port information when sending a unicast packet to the main control server, and other physical port information may be used besides the destination MAC address, the ethernet type, and the VLAN tag, which is not limited in this embodiment of the present application.

In a specific implementation, the format of the device network entry response may be as shown in the following table:

information element	Existence of	Format	Length of	Description of the invention
					Session identification	M	V	4
Local equipment number	C	TLV	4	Next layer boundary router
					Local logical address	C	TLV	2	Next layer boundary router
Connection signaling check code	M	TLV	4

In the device network access command and the device network access response, the main control server and the micro cloud server check whether the session identifier in the device network access command and the device network access response is the same as the session identifier in the device connection command, and if the session identifier in the device network access response is different from the session identifier in the device connection command, the current network access process is terminated.

And calculating the global equipment number of the equipment according to the local equipment number, the equipment number prefix and the micro cloud level.

And calculating the global logical address of the logical port according to the local logical address, the logical address prefix and the micro cloud level.

The destination MAC address represents a destination MAC address used when the micro cloud server sends a unicast packet to the master control server after accessing the network.

The Ethernet type represents the Ethernet type used when the micro cloud server sends a unicast packet to the master control server after accessing the network.

The VLAN label represents a VLAN label used when the micro cloud server sends a unicast packet to the master control server after accessing the network.

The system time represents the system time when the master server transmits the network access command.

If the information element is included in the network access command, the system time of the micro cloud server needs to be synchronized with the information element, and if the information element is not included, the system time of the micro cloud server does not need to be synchronized.

The physical port information represents physical port information corresponding to a downlink interface of the micro cloud server.

The micro cloud topology represents the topology type of the micro cloud (switching network) to which the downlink interface of the micro cloud server belongs.

The local device number represents the local device number of the boundary router in the autonomous cloud to which the port 0 belongs.

The local logical address represents the local logical address of port 0 of the border router in the autonomous cloud to which the border router belongs.

Step 1008, the master control server sends a device heartbeat command to the micro cloud server.

The device heartbeat command is transmitted using a unicast packet, i.e., the type of autonomous network address is a unicast address (i.e., a global logical address).

After the micro cloud server accesses the network, the main control server sends a device heartbeat command (unicast packet) to the micro cloud server at regular time (for example, at an interval of 1 second), and the device heartbeat command (unicast packet) can be used for maintaining the network access state of the device between the main control server and the micro cloud server.

In a particular implementation, the format of the device heartbeat command may be as shown in the following table:

Information element	Presence of	Format	Length of	Description of the preferred embodiment
					Heartbeat sequence number	M	V	4
System time	C	TLV	8
					Message check code	O	TLV	4

In step 1009, the master server receives the device heartbeat response sent by the micro cloud server.

The device heartbeat response is transmitted using a unicast packet, i.e., the type of autonomous network address is a unicast address (i.e., a global logical address).

And after receiving the equipment heartbeat command, the micro cloud server sends an equipment heartbeat response (unicast packet) to the master control server.

In a specific implementation, the format of the device heartbeat response may be as shown in the following table:

information element	Presence of	Format	Length of	Description of the preferred embodiment
					Heartbeat sequence number	M	V	4
System time	C	TLV	8
					Lower layer device online information	C	TLV	32
Upper layer device presence information	C	TLV	4
					Message check code	O	TLV	4

In the device heartbeat command and the device heartbeat response, the heartbeat sequence number represents the sequence number of the device heartbeat, and the master server starts to accumulate from 0.

The heartbeat sequence number of the equipment heartbeat response is the same as the heartbeat sequence number of the equipment heartbeat command center.

The system time represents the system time when the heartbeat command is sent by the master server.

If the system time is included in the device heartbeat command, the system time of the micro cloud server needs to be synchronized with the system time.

If the system time is not included in the device heartbeat command, the system time of the micro cloud server does not need to be synchronized.

In one embodiment of the present application, the device heartbeat response includes upper layer device presence information and lower layer device presence information.

If the micro cloud server is the boundary router, the online information of the upper layer equipment is effective, and whether the boundary router is connected to the boundary sub-control server in the upper layer autonomous cloud is indicated.

If the micro cloud server is a terminal sub-control server, the online information of the lower-layer equipment is effective and represents whether the terminal accessed to the terminal sub-control server is online or not;

if the micro cloud server is the boundary sub-control server, the lower-layer equipment online information is effective and represents whether the boundary router accessed to the boundary sub-control server is online or not.

In one example, the upper layer device presence information is 4 bytes in length.

And 0 represents that the boundary sub-control server is not accessed to the upper autonomous cloud.

And 1 represents a boundary sub-control server which is accessed into an upper autonomous cloud.

In one example, the length of the lower-layer device presence information is 32 bytes, and the total length is 256 bits, and each bit corresponds to one logical port in the sub-control micro-cloud.

When the device to which the logic port belongs does not exist or is not accessed to the network, the corresponding bit is set to be 0.

When the device to which the logical port belongs is in the network access state, the corresponding bit is set to 1.

In the embodiment of the application, if the online information of the upper-layer device indicates that the boundary router is not connected to the boundary sub-control server in the upper-layer autonomous cloud, the master control server sets an access state between the autonomous cloud where the master control server is located and the upper-layer autonomous cloud where the boundary router is located to be a non-access state.

And if the online information of the lower-layer equipment is that the boundary router accessing the boundary sub-control server is not online, the main control server sets the access state between the autonomous cloud where the main control server is located and the next autonomous cloud where the boundary router is located as the unaccessed state.

In another embodiment of the present application, if the master server does not receive the device heartbeat response of the micro cloud server over a preset time period (for example, 6 seconds), the micro cloud server is set to the non-network-access state, and step 1001 is executed again.

Further, when the micro cloud server is a boundary router, the master control server sets an access state between the autonomous cloud where the master control server is located and the last autonomous cloud where the boundary router is located as an unaccessed state.

And when the micro cloud server is the boundary sub-control server, the main control server sets the access state between the autonomous cloud where the main control server is located and the next autonomous cloud where the boundary router accessing the boundary sub-control server is located as the unaccessed state.

Correspondingly, if the micro cloud server does not receive the device heartbeat command of the main control server within a preset time period (for example, 6 seconds), the micro cloud server sets the micro cloud server to be in a non-network access state and waits for the device connection command of the main control server.

Referring to fig. 11, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application may specifically include the following steps:

step 1101, the master control server sends an exchange node information configuration command to the newly-accessed micro cloud server to transmit physical port information of the already-accessed micro cloud server.

Step 1102, the master control server receives an exchange node information configuration response sent after the micro cloud server which just enters the network configures the physical port information of the micro cloud server which has already entered the network.

Step 1103, the master control server sends an exchange node information configuration command to the connected micro cloud server to transmit physical port information of the newly connected micro cloud server.

And 1104, the master control server receives an exchange node information configuration response sent by the micro cloud server which has accessed the network after configuring the physical port information of the micro cloud server which has just accessed the network.

In step 1105, the master control server sends an exchange node information configuration command to the connected cloudlet server to transmit the physical port information of the cloudlet server that has just exited the network.

Step 1106, the master control server receives an exchange node information configuration response sent by the micro cloud server which has accessed the network after deleting the physical port information of the micro cloud server which has just exited the network.

After the micro cloud servers in the master control micro cloud access to the network, the master control server obtains the network parameter configuration of other micro cloud servers to complete the exchange of protocols and data in the autonomous network.

The switching node information configuration command and the switching node information configuration response are transmitted by using a unicast packet, and the autonomous network address used during transmission is the unicast addresses (namely the global logic address) of the two parties.

In a specific implementation, after a micro cloud server in a master control micro cloud accesses a network, the master control server sends physical port information (including all ports allowed to send and ports prohibited from sending) of the micro cloud server which has accessed the network to the micro cloud server which has just accessed the network through an exchange node information configuration command (unicast packet) according to a topology type of a switching network, and simultaneously sends physical port information (including a changed port, namely the micro cloud server which has accessed the network) of the micro cloud server which has just accessed the network to the micro cloud server which has accessed the network through the exchange node information configuration command.

After receiving the switching node information configuration command, the micro cloud server configures a corresponding Ethernet transmission matching table according to the information in the switching node information configuration command, and then transmits a switching node information configuration response (unicast packet) to the master control server.

In addition, after the micro cloud server in the master micro cloud quits, the master control server deletes the physical port information (including the changed port, namely the micro cloud server of the just quit network) of the micro cloud server of the just quit network from the micro cloud server of the already accessed network through the exchange node information configuration command (unicast packet) according to the topology type of the exchange network.

Similarly, after receiving the switching node information configuration command, the micro cloud server configures the corresponding ethernet transmission matching table according to the information therein, and then transmits a switching node information configuration response (unicast packet) to the master server.

In an example, if the topology type of the master control micro cloud accessed by the master control server and the micro cloud server is a full exchange topology, the physical port information of the networked micro cloud server, the newly-networked micro cloud server, or the newly-networked micro cloud server is the physical port information of the self.

In another example, if the topology type of the master cloud that the master server and the micro cloud server access is a star topology, and the networked micro cloud server, the newly networked micro cloud server, or the newly networked micro cloud server is the central device, the physical port information of the networked micro cloud server, the newly networked micro cloud server, or the newly networked micro cloud server is its own physical port information.

In another example, if the topology type of the master control micro cloud that the master control server and the micro cloud server access is a star topology, and the networked micro cloud server, the newly networked micro cloud server, or the newly released micro cloud server is not the central device, the physical port information of the networked micro cloud server, the newly networked micro cloud server, or the newly released micro cloud server is the physical port information of the central device.

In a specific implementation, the format of the switching node information configuration command may be as shown in the following table:

the format of the switching node information configuration response may be as shown in the following table:

information element	Existence of	Format	Length of	Description of the invention
					Operation code	M	V	4
Responsive to the result	M	V	4	0 is successful and others are failed
					Message check code	O	TLV	4

In the switching node information configuration command and the switching node information configuration response, the logical port address list indicates the logical port address of the micro cloud server interface in the micro cloud (switching network) to which the micro cloud server interface belongs, and the numerical value of the logical port address indicates which entry in the matching table is sent in the current operation.

The number of entries in the list is the same as the number of entries in the sub opcode list.

The physical port information list represents physical port information of the micro cloud server interface, and the content of the physical port information is used for setting the content of sending the table entry of the matching table.

In step 1107, the main control server sends a lower layer device information configuration command to the terminal sub-control server to transmit the registration information of the terminal accessing the terminal sub-control server.

Step 1108, the main control server receives the registration information of the terminal sub-control server configuration terminal and then sends a lower layer device information configuration response.

Step 1109, the main control server sends a lower layer device information configuration command to the terminal sub-control server when the registration information of the terminal changes, so as to transmit the registration information after the terminal changes.

Step 1110, the main control server receives the registration information after the terminal sub-control server configures the terminal change, and then sends a lower-layer device information configuration response.

Step 1111, the main control server sends a lower layer device information configuration command to the border sub-control server to transmit the registration information of the border router accessing the border sub-control server.

Step 1112, the main control server receives the registration information of the border sub-control server configured border router and then sends a lower layer device information configuration response.

Step 1113, when the registration information of the border router changes, the main control server sends a lower layer device information configuration command to the border sub-control server to transmit the changed registration information of the border router.

Step 1114, the main control server receives the registration information after the border sub-control server configures the border router, and then sends a lower layer device information configuration response.

The lower layer device information configuration command and the lower layer device information configuration response are transmitted by using a unicast packet, and the autonomous network address used in the transmission is the unicast addresses (namely, the global logic address) of the two parties.

Through the lower-layer equipment information configuration command and the lower-layer equipment information configuration response, the main control server can dynamically configure the registration information of the terminals of the sub-control micro-clouds corresponding to the terminal sub-control servers and the registration information of the boundary routers corresponding to the boundary sub-control servers.

Further, after a micro cloud server (i.e., a terminal sub-control server and a boundary sub-control server) in the main control micro-cloud accesses to the network, the main control server needs to send registration information of terminals and boundary routers in the sub-control micro-cloud corresponding to the micro cloud server (i.e., the terminal sub-control server and the boundary sub-control server) which has just accessed to the network through a lower-layer device information configuration command (unicast packet).

When the registration information of the terminal and the boundary router in the sub-control micro-cloud changes (such as addition, modification, deletion and the like), the main control server can send the change situation to the corresponding micro-cloud server (namely the terminal sub-control server and the boundary sub-control server) through the lower-layer equipment information configuration command.

After receiving the lower-layer equipment information configuration command, the micro cloud server (namely the terminal sub-control server and the boundary sub-control server) completes the configuration of the relevant registration information, and then sends a lower-layer equipment information configuration response (unicast packet), and the deleted terminal and the boundary sub-control server automatically quit the network.

In a specific implementation, the format of the lower layer device information configuration command may be as shown in the following table:

information element	Degree of existence	Format	Length of	Description of the preferred embodiment
					Operation code	M	V	4	1: synchronizing commands
Lower layer device information list	C	TLV		Device registration information for a device to be added
					Local device number list	C	TLV		Local device number of device to be deleted
Message check code	O	TLV	4

The format of the lower layer device information configuration response may be as shown in the following table:

information element	Presence of	Format	Length of	Description of the invention
					Operation code	M	V	4
Responsive to the result	M	V	4	Success 0, failure others
					Detailed results List	C	TLV
Message check code	O	TLV	4

Referring to fig. 12, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application may specifically include the following steps:

step 1201, the terminal sub-control server sends a device connection command to the terminal.

In the sub-control micro-cloud of the autonomous cloud, after a terminal sub-control server accesses the network, a device connection command is sent to a terminal according to the device registration information of the terminal sub-control server.

The 8 bytes of the connection address of the terminal sub-control server are all 0xff, and the 8 bytes of the connection address of the terminal are all the logical port addresses thereof.

step 1202, the terminal sub-control server receives a device connection response sent by the terminal when the terminal verifies that the device connection command belongs to the terminal sub-control server.

The device connection response is transmitted using a connection packet, i.e. the type of the autonomous network address is a connection address.

After receiving the device connection command (connection packet), the terminal checks whether the device connection command is sent to the terminal sub-control server, if so, the terminal records the related information (including the connection addresses of both sides) in the device connection command, then sends a device connection response (connection packet) to the terminal sub-control server, and if not, the terminal continues to wait for the device connection command sent to the terminal.

In this embodiment, the terminal determines whether the logical device type and the logical device identifier in the device connection command are the same as the logical device type and the logical device identifier of the terminal; if yes, determining that the equipment connection command belongs to the equipment connection command; if not, determining that the equipment connection command does not belong to the equipment connection command.

The destination MAC address represents a destination MAC address used when the terminal sends a connection packet to the terminal sub-control server in the network access process.

The Ethernet type represents the Ethernet type used when the terminal sends the connection packet to the terminal sub-control server in the network access process.

The VLAN tag indicates a VLAN tag used when the terminal sends a connection packet to the terminal sub-control server in the network access process.

In step 1203, the terminal sub-control server sends a device authentication command to the terminal to transmit the authentication parameters.

The terminal sub-control server sends an equipment authentication command (connection packet) to the terminal, wherein the command comprises authentication parameters such as an authentication algorithm type, an authentication random number and the like, and can be used for authentication between the terminal sub-control server and the terminal so as to improve the network security.

information element	Presence of	Format	Length of	Description of the preferred embodiment
					Session identification	M	V	4
Authentication algorithm type	M	V	4
					Authenticating random numbers	M	V	4
Connection signaling check code	M	TLV	4

The authentication algorithm type represents an algorithm used in authentication operation, and the authentication random number represents a random number used in the authentication operation and is generated by the terminal sub-control server.

And 1204, the terminal sub-control server receives the equipment authentication response sent by the terminal after the terminal executes the authentication operation by using the authentication parameters.

And the terminal performs related authentication operation by adopting the authentication parameters sent by the terminal sub-control server, packages the authentication operation result into an equipment authentication response (connection packet) and returns the equipment authentication response to the terminal sub-control server.

In one embodiment of the application, the authentication parameters include an authentication algorithm type, an authentication nonce.

In the embodiment of the present application, the terminal invokes an authentication algorithm corresponding to the authentication algorithm type, and performs an authentication operation using the authentication random number to obtain an authentication candidate result.

And the terminal packages the authentication candidate result to the equipment authentication response and sends the equipment authentication response to the terminal sub-control server.

information element	Presence of	Format	Length of	Description of the invention
					Session identification	M	V	4
Authentication algorithm type	M	V	4
					Authenticating random numbers	M	V	4
Authentication calculation result	M	V	16	Authentication candidate result
					Connection signaling check code	M	TLV	4

In the equipment authentication command and the equipment authentication response, the terminal sub-control server and the terminal need to check whether the session identifier is the same as the session identifier in the equipment connection command, and if the session identifier is different from the session identifier in the equipment connection command, the current network access process is terminated.

Step 1205, the terminal sub-control server judges whether the terminal is successfully authenticated; if yes, go to step 1206.

In a specific implementation, the terminal sub-control server may perform the same authentication operation using the authentication parameter to determine whether the authentication of the terminal is successful.

Further, the terminal sub-control server extracts the result of the authentication operation from the device authentication response of the terminal, compares the result with the result of the authentication operation executed by the terminal sub-control server, and judges whether the terminal is successfully authenticated.

In the embodiment of the application, the terminal sub-control server calls the authentication algorithm corresponding to the authentication algorithm type, and executes the authentication operation by adopting the authentication random number to obtain the authentication reference result.

The terminal sub-control server judges whether the authentication candidate result is the same as the authentication reference result or not; if so, determining that the terminal authentication is successful; and if not, determining that the terminal authentication fails.

And step 1206, the terminal sub-control server sends a device network access command to the terminal so as to transmit the network access parameters.

Step 1207, the terminal sub-control server receives the device network access response sent by the terminal after configuring the network access parameter.

The terminal sub-control server sends a device network access command (connection packet) to the terminal, wherein the command comprises information such as a local logical address and a local device number of the terminal sub-control server, the terminal and the main control server, an MAC address (physical port information) used when a unicast packet is sent to the terminal sub-control server, a logical address prefix and a device number prefix of the autonomous cloud, a logical port address list and the like.

After receiving the device network access command, the terminal records the relevant information in the command, and then sends a device network access response (connection packet) to the terminal sub-control server.

It should be noted that the destination MAC address, the ethernet type, and the VLAN tag are examples of physical port information when sending the unicast packet to the terminal sub-control server, and other physical port information may be used besides the destination MAC address, the ethernet type, and the VLAN tag, which is not limited in this embodiment of the present application.

information element	Presence of	Format	Length of	Description of the preferred embodiment
					Session identification	M	V	4
Local equipment number	C	TLV	4	Next layer boundary router
					Local logical address	C	TLV	2	Next layer boundary router
Connection signaling check code	M	TLV	4

In the device network access command and the device network access response, the terminal sub-control server and the terminal check whether the session identifier is the same as the session identifier in the device connection command, and if the session identifier is different from the session identifier in the device connection command, the current network access process is terminated.

The destination MAC address represents a destination MAC address used when the terminal sends a unicast packet to the terminal sub-control server after accessing the network.

The Ethernet type represents the Ethernet type used when the terminal sends the unicast packet to the terminal sub-control server after accessing the network.

The VLAN label represents a VLAN label used when the terminal sends a unicast packet to the terminal sub-control server after accessing the network.

The logical port address list represents the logical port addresses of all the logical ports of the terminal, and the information element is valid only when the terminal includes a plurality of logical ports, and is not used in other cases.

The system time represents the system time when the terminal sub-control server sends the network access command.

If the information element is included in the network access command, the system time of the terminal needs to be synchronized with the time, and if the information element is not included, the system time of the terminal does not need to be synchronized.

And step 1208, the terminal sub-control server sends a device heartbeat command to the terminal.

After the terminal accesses the network, the terminal sub-control server sends a device heartbeat command (unicast packet) to the terminal at a fixed time (for example, at an interval of 1 second), and the terminal heartbeat command can be used for maintaining the network access state of the device between the terminal sub-control server and the terminal.

In a specific implementation, the format of the device heartbeat command may be as shown in the following table:

Information element	Presence of	Format	Length of	Description of the invention
					Heartbeat sequence number	M	V	4
System time	C	TLV	8
					Message check code	O	TLV	4

Step 1209, the terminal sub-control server receives the device heartbeat response sent by the terminal.

And after receiving the equipment heartbeat command, the terminal sends an equipment heartbeat response (unicast packet) to the terminal sub-control server.

information element	Presence of	Format	Length of	Description of the invention
					Heartbeat sequence number	M	V	4
System time	C	TLV	8
					Lower layer device online information	C	TLV	32
Upper layer device presence information	C	TLV	4
					Message check code	O	TLV	4

In the device heartbeat command and the device heartbeat response, the heartbeat sequence number represents the sequence number of the device heartbeat, and the terminal sub-control server starts accumulation from 0.

The system time represents the system time when the terminal sub-control server sends the heartbeat command.

If the system time is included in the device heartbeat command, the system time of the terminal needs to be synchronized with the system time.

If the system time is not included in the device heartbeat command, the system time of the terminal does not need to be synchronized.

In an embodiment of the present application, if the terminal sub-control server does not receive the device heartbeat response of the terminal over a preset time period (for example, 6 seconds), the terminal is set to the non-network-access state, and the step 1201 is returned to.

Correspondingly, if the terminal does not receive the equipment heartbeat command of the terminal sub-control server within a preset time period (such as 6 seconds), the terminal sets the terminal to be in a non-network-access state and waits for the equipment connection command of the terminal sub-control server.

Referring to fig. 13, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application may specifically include the following steps:

step 1301, the border sub-control server sends a device connection command to the border router.

And an uplink interface of the boundary router is accessed into the sub-control micro-cloud of the autonomous cloud, and a downlink interface of the boundary router is accessed into the main control micro-cloud of the next autonomous cloud.

In the sub-control micro-cloud of the autonomous cloud, after the boundary sub-control server accesses the network, the boundary sub-control server sends a device connection command to the boundary router according to the device registration information of the boundary sub-control server.

The 8 bytes of the connection address of the border sub-control server are all 0xff, and the 8 bytes of the connection address of the border router are all its logical port address.

information element	Presence of	Format	Length of	Description of the invention
					Session identification	M	V	4
Logical device type	M	V	4	Logical device type of boundary sub-control server
					Logical device identification	M	V	8	Logical device identification of boundary sub-control server
Logical device type	M	V	4	Logical device type of border router
					Logical device identification	M	V	8	Logical device type of border router
Micro cloud level	M	V	1	Hierarchy of micro clouds to which border routers belong
					Node type	M	V	1	Node type of border router
Destination MAC address	M	V	6
					Ethernet type	M	V	2
VLAN label	M	V	2
					Head space	M	V	8
Connection signaling check code	M	V	4

Step 1302, the border sub-control server receives an equipment connection response sent by the border router when the border router verifies that the equipment connection command belongs to itself.

After receiving the device connection command (connection packet), the boundary router checks whether the device connection command is sent to itself by the terminal sub-control server, if so, records the relevant information (including the connection addresses of both sides) in the device connection command, then sends the device connection response (connection packet) to the boundary sub-control server, and if not, then continues to wait for the device connection command sent to itself.

In this embodiment, the border router determines whether the logical device type and the logical device identifier in the device connection command are the same as the logical device type and the logical device identifier of the border router; if yes, determining that the equipment connection command belongs to the equipment connection command; if not, determining that the equipment connection command does not belong to the equipment connection command.

information element	Existence of	Format	Length of	Description of the invention
					Session identification	M	V	4
Logical device type	M	V	4	Logical device type of boundary sub-control server
					Logical device identification	M	V	8	Logical device identification of boundary sub-control server
Logical device type	M	V	4	Logical device type of border router
					Logical device identification	M	V	8	Logical device type of border router
Micro cloud level	M	V	1	Hierarchy of micro clouds to which border routers belong
					Node type	M	V	1	Node type of border router
Head space	M	V	18
					Connection signaling check code	M	V	4

The destination MAC address represents a destination MAC address used when the boundary router sends a connection packet to the boundary sub-control server in the network access process.

The ethernet type indicates the ethernet type used when the boundary router sends a connection packet to the boundary sub-control server in the network access process.

The VLAN label represents a VLAN label used when the boundary router sends a connection packet to the boundary sub-control server in the network access process.

And step 1303, the border sub-control server sends an equipment authentication command to the border router to transmit authentication parameters.

The 8 bytes of the connection address of the border sub-control server are all 0xff, and the 8 bytes of the connection address of the border router are all the logical port addresses thereof.

The boundary sub-control server sends an equipment authentication command (connection packet) to the boundary router, wherein the command comprises authentication parameters such as an authentication algorithm type, an authentication random number and the like, and can be used for authentication between the boundary sub-control server and the boundary router so as to improve the network security.

The authentication algorithm type represents an algorithm used in authentication operation, and the authentication random number represents a random number used in the authentication operation and is generated by the boundary sub-control server.

In step 1304, the border sub-control server receives the device authentication response sent by the border router after executing the authentication operation using the authentication parameter.

The device authentication response is transmitted using a connection packet, i.e. the type of the autonomous network address is a connection address.

The boundary router adopts the authentication parameters sent by the boundary sub-control server to carry out relevant authentication operation, encapsulates the result of the authentication operation into an equipment authentication response (connection packet) and returns the result to the boundary sub-control server.

In the embodiment of the present application, the border router invokes an authentication algorithm corresponding to the authentication algorithm type, and performs an authentication operation using the authentication random number to obtain an authentication candidate result.

And the boundary router packages the authentication candidate result to an equipment authentication response and sends the equipment authentication response to the boundary sub-control server.

In the equipment authentication command and the equipment authentication response, the boundary sub-control server and the boundary router need to check whether the session identifier is the same as the session identifier in the equipment connection command, and if the session identifier is different from the session identifier in the equipment connection command, the current network access process is terminated.

Step 1305, the border sub-control server judges whether the border router is successfully authenticated; if yes, go to step 1306.

In a specific implementation, the border sub-control server may perform the same authentication operation using the authentication parameter to determine whether the border router is successfully authenticated.

Further, the border sub-control server extracts the result of the authentication operation from the device authentication response of the border router, compares the result with the result of the authentication operation executed by the border sub-control server, and judges whether the border router is authenticated successfully.

In the embodiment of the present application, the boundary sub-control server invokes an authentication algorithm corresponding to the authentication algorithm type, and executes an authentication operation using the authentication random number to obtain an authentication reference result.

The boundary sub-control server judges whether the authentication candidate result is the same as the authentication reference result or not; if yes, determining that the authentication of the border router is successful; if not, determining that the authentication of the border router fails.

Of course, the above-mentioned manner of authentication judgment is only an example, and when the embodiment of the present application is implemented, another manner of authentication judgment may be set according to the actual situation, and the embodiment of the present application is not limited thereto. In addition, besides the above authentication operation, a person skilled in the art may also adopt other authentication judgment modes according to actual needs, and this embodiment of the present application is not limited to this.

In step 1306, the border sub-control server sends a device network access command to the border router to transmit the network access parameters.

Step 1307, the border sub-control server receives the device network access response sent by the border router after configuring the network access parameter.

The boundary sub-control server sends a device network access command (connection packet) to the boundary router, wherein the command comprises information such as a local logical address and a local device number of the boundary sub-control server, the boundary router and the main control server, an MAC address (physical port information) used when a unicast packet is sent to the boundary sub-control server, a logical address prefix and a device number prefix of the autonomous cloud, a logical port address list and the like.

After receiving the device network access command, the boundary router records the relevant information in the command, and then sends a device network access response (connection packet) to the boundary sub-control server.

it should be noted that the destination MAC address, the ethernet type, and the VLAN tag are examples of physical port information when sending the unicast packet to the border sub-control server, and other physical port information may be used besides the destination MAC address, the ethernet type, and the VLAN tag, which is not limited in this embodiment of the present application.

information element	Presence of	Format	Length of	Description of the invention
					Session identification	M	V	4
Local equipment number	C	TLV	4	Next layer boundary router
					Local logical address	C	TLV	2	Next layer boundary router
Connection signaling check code	M	TLV	4

In the device network access command and the device network access response, the boundary sub-control server and the boundary router check whether the session identifier is the same as the session identifier in the device connection command, and if the session identifier is different from the session identifier in the device connection command, the current network access process is terminated.

The destination MAC address represents a destination MAC address used when the boundary router sends a unicast packet to the boundary sub-control server after accessing the network.

The Ethernet type represents the Ethernet type used when the boundary router sends a unicast packet to the boundary sub-control server after accessing the network.

The VLAN label represents a VLAN label used when the boundary router sends a unicast packet to the boundary sub-control server after accessing the network.

The system time represents the system time when the boundary sub-control server sends the network access command.

If this information element is included in the network entry command, the system time of the border router needs to be synchronized with this time, and if this information element is not included, the system time of the border router does not need to be synchronized.

Step 1308, the border sub-control server sends a device heartbeat command to the border router.

After the terminal accesses the network, the boundary sub-control server sends a device heartbeat command (unicast packet) to the boundary router at a fixed time (for example, at an interval of 1 second), which can be used between the boundary sub-control server and the boundary router to maintain the network access state of the device.

information element	Existence of	Format	Length of	Description of the invention
					Heartbeat sequence number	M	V	4
System time	C	TLV	8
					Message check code	O	TLV	4

In step 1309, the border sub-control server receives the device heartbeat response sent by the border router.

After receiving the device heartbeat command, the boundary router sends a device heartbeat response (unicast packet) to the boundary sub-control server.

in the device heartbeat command and the device heartbeat response, the heartbeat sequence number represents the sequence number of the device heartbeat, and the boundary sub-control server starts accumulation from 0.

The system time represents the system time when the boundary slave control server sends the heartbeat command.

If the system time is included in the device heartbeat command, the system time of the border router needs to be synchronized with the system time.

If the system time is not included in the device heartbeat command, the system times of the border routers need not be synchronized.

In an embodiment of the present application, if the boundary sub-control server does not receive the device heartbeat response of the boundary router over a preset time period (for example, 6 seconds), the boundary router is set to the non-network-entry state, and the step 1301 is executed.

Correspondingly, if the border router does not receive the device heartbeat command of the border sub-control server over a preset time period (for example, 6 seconds), the border router sets itself to be in a non-network-accessing state and waits for the device connection command of the border sub-control server.

Referring to fig. 14, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application is shown, which may specifically include the following steps:

In step 1401, the border sub-control server sends a switch node information configuration command to the border router that has just entered the network, so as to transmit the physical port information of the border router that has entered the network.

Step 1402, the border sub-control server receives the switching node information configuration response sent after the border router which just accessed the network configures the physical port information of the border router which has accessed the network.

Step 1403, the border sub-control server sends a switching node information configuration command to the border router which has already entered the network, so as to transmit the physical port information of the border router which has just entered the network.

Step 1404, the border sub-control server receives the switching node information configuration response sent by the border router which has accessed the network after configuring the physical port information of the border router which has just accessed the network.

Step 1405, the border sub-control server sends a switch node information configuration command to the border router which has already entered the network, so as to transmit the physical port information of the border router which has just exited the network.

In step 1406, the border sub-control server receives the switching node information configuration response sent by the border router which has already accessed the network after deleting the physical port information of the border router which has just exited the network.

After the border router in the sub-control micro cloud accesses the network, the network parameter configuration of other border routers is obtained through the border sub-control server to complete the exchange of protocols and data in the autonomous network.

In a specific implementation, after a border router in a distributed control micro cloud accesses a network, a border distributed control server sends physical port information (including all ports allowed to send and ports prohibited from sending) of the border router which has accessed the network to a border router which has just accessed the network through a switching node information configuration command (unicast packet) according to a topology type of a switching network, and simultaneously sends physical port information (including changed ports, namely the border router which has accessed the network) of the border router which has accessed the network to the border router which has accessed the network through the switching node information configuration command.

After receiving the switching node information configuration command, the border router configures a corresponding Ethernet transmission matching table according to the information in the switching node information configuration command, and then transmits a switching node information configuration response (unicast packet) to the border sub-control server.

In addition, after the border router in the distributed control micro cloud quits the network, the border distributed control server deletes the physical port information (including the changed port, namely the border router which just quits the network) of the border router which just quits the network from the border router which has already entered the network through the switching node information configuration command (unicast packet) according to the topology type of the switching network.

Similarly, after receiving the switching node information configuration command, the border router configures the corresponding ethernet transmission matching table according to the information therein, and then transmits a switching node information configuration response (unicast packet) to the master server.

In one example, if the topology type of the distributed control clouding accessed by the boundary distributed control server and the boundary router is a full switching topology, the physical port information of the boundary router which has accessed the network, or the boundary router which has just exited the network is the physical port information of the boundary router itself.

In another example, if the topology type of the distributed control micro-cloud accessed by the boundary distributed control server and the boundary router is a star topology, and the boundary router which has entered the network, or the boundary router which has just exited the network is a central device, the physical port information of the boundary router which has entered the network, or the boundary router which has just exited the network is its own physical port information.

In another example, if the topology type of the distributed control micro-cloud accessed by the boundary distributed control server and the boundary router is a star topology, and the boundary router which has entered the network, or the boundary router which has just exited the network is not the central device, the physical port information of the boundary router which has entered the network, or the boundary router which has just exited the network is the physical port information of the central device.

information element	Presence of	Format	Length of	Description of the invention
					Operation code	M	V	4
Responsive to the result	M	V	4	0 is successful and others are failed
					Message check code	O	TLV	4

In the switching node information configuration command and the switching node information configuration response, the logical port address list indicates the logical port address of the border router interface in the micro cloud (switching network) to which the border router interface belongs, and the value of the logical port address indicates which entry in the matching table is sent in the current operation.

The number of entries in the list is the same as the number of entries in the sub-opcode list.

The physical port information list represents the physical port information of the interface of the border router, and the content of the physical port information is used for setting the content of the table entry of the sending matching table.

Referring to fig. 15, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application is shown, which may specifically include the following steps:

step 1501, the master control server in the autonomous cloud controls the last layer of autonomous cloud to access the autonomous cloud.

In order to realize related services between upper and lower layers of crossing autonomous clouds, after a boundary router multiplexed by the autonomous cloud and an upper layer of autonomous clouds is respectively accessed to a main control server of the autonomous cloud and a boundary sub-control server of the upper layer of autonomous clouds, the main control server of the autonomous cloud can control the upper layer of autonomous clouds to be accessed to the autonomous clouds.

In one embodiment of the present application, step 1501 may include the following sub-steps:

in sub-step 15011, the main control server in the autonomous cloud receives an autonomous cloud network access configuration command of the border router multiplexed with the previous layer of autonomous cloud to transmit network parameters of the previous layer of autonomous cloud.

In the embodiment of the application, after the downlink interface and the uplink interface of the boundary router are both connected to the network, an autonomous cloud network access configuration command can be simultaneously sent to the master control server of the autonomous cloud and the master control server of the previous autonomous cloud.

The autonomous cloud network access configuration command sent to the main control server of the autonomous cloud comprises the logic device type and the logic device identification of the boundary router, and the local logic address and the local device number of the main control server of the upper autonomous cloud.

In a specific implementation, the autonomous cloud network entry configuration command is transmitted by using a unicast packet, that is, the type of the autonomous network address is a unicast address (i.e., a global logical address).

The format of the autonomous cloud network access configuration command can be shown as the following table:

when the operation code is 1, the local device number and the local logical address of the main control server correspond to information of the main control server of the autonomous cloud accessed by the boundary router through an uplink interface (port 1).

When the operation code is 2, the local device number and the local logical address of the main control server correspond to the information of the main control server of the autonomous cloud accessed by the border router through a downlink interface (port 0).

The local device number and the local logical address of the border router are valid only when the operation code is 2.

Substep 15012, the master control server in the autonomous cloud checks whether the autonomous cloud network access configuration command belongs to the autonomous cloud network access configuration command; if so, then sub-step 15013 is performed.

Substep 15013, performing network access configuration on the previous autonomous cloud according to the network parameters of the previous autonomous cloud, and sending an autonomous cloud network access configuration response to the border router.

After receiving an autonomous cloud network access configuration command (unicast packet), the main control server verifies whether the autonomous cloud network access configuration command is sent to the main control server by the boundary router, if so, relevant information in the autonomous cloud network access configuration command is recorded so as to carry out network access configuration on the upper layer of autonomous cloud, then an autonomous cloud network access configuration response is sent to the boundary router, and if not, the main control server continues to wait for the autonomous cloud network access configuration command sent to the main control server.

The autonomous cloud networking configuration response is transmitted by using a unicast packet, namely the type of the autonomous network address is a unicast address (namely a global logical address).

In a specific implementation, the format of the autonomous cloud network access configuration response may be as shown in the following table:

information element	Presence of	Format	Length of	Description of the invention
					Operation code	M	V	4
Responsive to the result	M	V	4
					Message check code	O	TLV	4

In an embodiment of the present application, the autonomous cloud networking configuration command includes a device type and a logical device identifier of the border router, and the logical device type and the logical device identifier may uniquely represent one device.

In this embodiment, the master control server determines whether the device type and the logical device identifier in the autonomous cloud network access configuration command are the same as the previously recorded logical device type and logical device identifier of the border router; if yes, determining that the autonomous cloud network access configuration command belongs to the autonomous cloud network access configuration command; if not, determining that the autonomous cloud network access configuration command does not belong to the autonomous cloud network access configuration command.

And the master control server in the autonomous cloud records the network parameters of the previous layer of autonomous cloud, and sets the access state between the autonomous cloud and the previous layer of autonomous cloud as accessed to realize the access of the previous layer of autonomous cloud.

And 1502, controlling the next layer of autonomous cloud to be accessed into the autonomous cloud by the master control server in the autonomous cloud.

In order to realize related services between upper and lower layers of crossing autonomous clouds, after a boundary router multiplexed by the autonomous cloud and the next autonomous cloud is respectively accessed to a boundary sub-control server of the autonomous cloud and a main control server of the next autonomous cloud, the main control server of the autonomous cloud can control the next autonomous cloud to be accessed to the autonomous cloud.

In one embodiment of the present application, step 1502 may include the following sub-steps:

in sub-step 15201, the main control server in the autonomous cloud receives an autonomous cloud network access configuration command of the boundary router multiplexed with the next autonomous cloud to transmit network parameters of the next autonomous cloud.

In this embodiment of the present application, after the downlink interface and the uplink interface of the boundary router are both connected to the network, an autonomous cloud network access configuration command may be simultaneously sent to the master control server of the autonomous cloud and the master control server of the next layer of autonomous cloud.

The autonomous cloud network access configuration command sent to the main control server of the autonomous cloud comprises the logic device type and the logic device identification of the boundary router, the local logic address and the local device number of the main control server of the next layer of autonomous cloud, and the local logic address and the local device number of the boundary router in the next layer of autonomous cloud.

Sub-step 15202, the master control server in the autonomous cloud checks whether the autonomous cloud network access configuration command belongs to itself; if so, go to sub-step 15203.

And a substep 15203 of performing network access configuration on the next autonomous cloud according to the network parameters of the next autonomous cloud, and sending an autonomous cloud network access configuration response to the border router.

After receiving an autonomous cloud network access configuration command (unicast packet), the main control server checks whether the autonomous cloud network access configuration command is sent to the main control server by the boundary router, if so, the main control server records relevant information in the autonomous cloud network access configuration command so as to perform network access configuration on the next autonomous cloud layer, then sends an autonomous cloud network access configuration response to the boundary router, and if not, the main control server continuously waits for the autonomous cloud network access configuration command sent to the main control server.

The autonomous cloud network access configuration response is transmitted by using a unicast packet, namely the type of the autonomous network address is a unicast address (namely a global logical address).

information element	Existence of	Format	Length of	Description of the preferred embodiment
					Operation code	M	V	4
Responsive to the result	M	V	4
					Message check code	O	TLV	4

In this embodiment, the master control server determines whether the device type and the logical device identifier in the autonomous cloud network access configuration command are the same as the previously recorded logical device type and logical device identifier of the border router; if so, determining that the autonomous cloud network access configuration command belongs to the autonomous cloud network access configuration command; if not, determining that the autonomous cloud network access configuration command does not belong to the autonomous cloud network access configuration command.

And the master control server in the autonomous cloud records the network parameters of the autonomous cloud of the next layer, sets the access state between the autonomous cloud and the autonomous cloud of the next layer as accessed, and realizes the access of the autonomous cloud of the next layer.

Referring to fig. 16, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application is shown, which may specifically include the following steps:

Step 1601, a master control server in a certain autonomous cloud receives a service request of a global data sink.

According to the service requirements, a device (e.g., a terminal) in a certain autonomous cloud may send a service request, i.e., a request for a service-related operation, such as a video telephone request, a request for watching a live broadcast, a video conference request, to a service processing module of the main control server as a global data sink.

In step 1602, a master server in one or more autonomous clouds creates a global multicast link from a global data source to the global data sink in the autonomous cloud to which the master server belongs according to the service request.

The master control server of one or more connected autonomous clouds (including the autonomous clouds to which the global data sources and the global data sinks belong) between the global data sources and the global data sinks can establish global multicast links from the global data sources to the global data sinks in the autonomous clouds according to the service requests.

Step 1603, the master server in one or more autonomous clouds controls the global data source and the global data sink to perform service communication through the global multicast link control in the autonomous cloud to which the master server belongs.

The master control servers of these autonomous clouds can perform service control in these autonomous clouds, that is, the master control servers of these autonomous clouds can actively send various service-related operations to each device, for example, video telephone preparation, video conference start, video conference switch, and the like.

Step 1604, when the service communication is finished, the master server in one or more autonomous clouds closes the global multicast link from the global data source to the global data sink in the autonomous cloud to which the master server belongs.

If the service communication is finished, the master control servers of the autonomous clouds can close the global multicast link from the global data source to the global data sink in the autonomous clouds, and relevant resources are released.

Referring to fig. 17, a flowchart illustrating steps of a service communication method of an autonomous network according to an embodiment of the present application is shown, which may specifically include the following steps:

step 1701, the master control server in the autonomous cloud receives a request for adding data sink.

And the service processing module of the master control server sends a request for adding a data sink to the multicast management module according to the requirement of the multicast service.

The data sink adding request comprises information such as a global device number of a global data sink, a channel number of the global data sink, a global device number of a global data source, a channel number of the global data source and the like.

Step 1702, querying an autonomous cloud to which a global data source and global data sink belong in an autonomous network according to the request for adding data sink.

And after receiving the data sink adding request, the multicast management module judges whether the global data sink and the global equipment number of the global data source are the equipment in the self-control cloud or not according to the global data sink and the global equipment number of the global data source.

In an embodiment of the present application, after step 1702, if the global data source belongs to the autonomous cloud, it is determined whether the global data source is a terminal, a terminal sub-control server, or a boundary sub-control server.

If yes, determining that the global data source is legal, and allowing the processing to be continued.

If not, determining that the global data source is illegal, generating an added data sink response to inform that an error occurs, and ending the processing.

In another embodiment of the present application, after step 1702, if the global data sink belongs to the autonomous cloud, it is determined whether the global data sink is a terminal, a terminal sub-control server, or a boundary sub-control server.

If yes, determining that the global data are legal, and allowing the processing to be continued.

If not, determining that the global data sink is illegal, generating an additional data sink response to inform that an error occurs, and ending the processing.

In another embodiment of the present application, after step 1702, if the global data sink does not belong to the autonomous cloud, it is determined that the global data sink is illegal, an add data sink response is generated to notify that an error occurs, and the process is ended.

And 1703, judging whether the multicast data stream corresponding to the data sink adding request exists in the autonomous cloud.

The multicast management module can search whether the multicast data stream exists through the data source index table and then search whether the multicast data stream exists through the data source information table.

And if at least one of the data source index table and the data source information table finds that the multicast data stream does not exist, determining that the multicast data stream does not exist in the autonomous cloud.

And if the existence of the multicast data stream is found in the data source index table and the data source information table at the same time, determining that the multicast data stream exists in the autonomous cloud.

If there is a multicast data stream, processing may continue.

And if the multicast data stream does not exist and the global data source belongs to the autonomous cloud, generating an added data sink response to inform the service processing module of an error, and ending the processing.

Step 1704, if the multicast data stream exists, determining a local data source and a local data sink in the local autonomous cloud according to the global data source and the autonomous cloud to which the global data sink belongs.

In one case, if the global data source belongs to the autonomous cloud, the global data source is determined to be a local data source in the autonomous cloud.

In another case, if the global data source does not belong to the local autonomous cloud, a border router which can be routed to the autonomous cloud to which the global data source belongs and belongs to the local autonomous cloud is queried as the local data source in the local autonomous cloud.

In another case, if the global data sink belongs to the local autonomous cloud, the global data sink is determined to be a local data sink in the local autonomous cloud.

Step 1705, a local multicast link for transmitting the multicast data stream from the local data source to the local data sink is established in the self-governing cloud, so as to establish a global multicast link for transmitting at least part of the multicast data stream from the global data source to the global data sink.

The multicast management module can calculate a local multicast link of the multicast data stream requested by adding the data sink in the autonomous cloud according to the local device number (local data sink) of the global data sink and the local data source device number (local data source) in the data source information table, so as to establish the global multicast link in the autonomous network.

In one embodiment of the present application, step 1705 may include the following sub-steps:

substep 17051, computing a local multicast link in the local autonomous cloud, where the multicast data stream is transmitted from the local data source to the local data sink via a data forwarding node.

The data forwarding nodes are terminal sub-control servers and/or boundary sub-control servers.

Sub-step 17052 of sending a multicast link setup command to a device on the local multicast link to open the local multicast link.

And a sub-step 17053 of receiving a multicast link establishment response returned by the device on the local multicast link.

The multicast management module can send a corresponding multicast link establishment command according to the device type of each device on the local multicast link, so that the multicast data stream can be sent from a local data source and transmitted to a local data sink through the data forwarding node, and the local multicast link is opened.

And after receiving the multicast link establishment response of each device on the local multicast link, the multicast management module updates the related multicast table.

In a specific implementation, the multicast link establishment command comprises a data source state control command and a multicast link control command; therefore, the corresponding multicast link establishment response includes a data source status control response and a multicast link control response.

The data source state control command and the data source state control response may be used to control whether the terminal device to which the multicast data stream belongs sends the multicast data stream.

When the multicast data stream is not received by any data sink, the master control server may control its corresponding terminal to stop sending the multicast data stream, so as to reduce the traffic on the network.

When there is data sink to receive the multicast data stream, the main control server controls the corresponding terminal to start sending the multicast data stream.

The PDU of the data source status control command is transmitted using a unicast packet, and the format can be as shown in the following table:

when the operation code is 1, it indicates that the transmission of the packet of the data source is started.

When the operation code is 2, the transmission of the data packet of the data source is stopped.

The PDU of the data source status control response is transmitted using a unicast packet, and the format can be as shown in the following table:

information element	Presence of	Format	Length of	Description of the preferred embodiment
					Operation code	M	V	4
Multicast address	M	V	4	Multicast address for multicast data stream
					Responsive to the result	M	V	4	0 is successful and others are failed
Message check code	O	TLV	4

The multicast link control command and the multicast link control response can be used for controlling the receiving, copying and sending of the multicast data stream on the local multicast link by the main control server.

The multicast link control command and the multicast link control response allow control of a plurality of local multicast links at the same time, so most of the information elements are in a list form.

The PDUs of the multicast link control commands are transmitted using unicast packets, and the format can be as shown in the following table:

the operation code list comprises a plurality of operation codes, and each operation code corresponds to the operation of one table entry.

The opcode is defined as follows:

1: add direction information of multicast direction table No. 0

2: add guide information of multicast guide table No. 1

3: guide information adding No. 2 multicast guide table

4: guide information adding No. 3 multicast guide table

5: deleting the guide information of the multicast guide table No. 0

6: deleting guide information of multicast guide table No. 1

7: deleting the guide information of the multicast guide table No. 2

8: deleting guide information of multicast guide table No. 3

9: data channel for opening multicast information table No. 0

10: data channel for opening multicast information table No. 1

11: data channel for closing multicast information table No. 0

12: data channel for closing No. 1 multicast information table

13: data channel for clearing number 0 multicast information table

14: data channel for clearing No. 1 multicast information table

The original multicast address list comprises a plurality of multicast addresses before replacement, and the number of the multicast addresses is the same as the number of operation codes.

The replacement multicast address list comprises a plurality of replaced multicast addresses, and the number of the replaced multicast addresses is the same as the number of the operation codes.

The logical port address list comprises a plurality of logical port addresses, and the number of the logical port addresses is the same as the number of the operation codes.

When an opcode in the opcode list is 1-4, the corresponding entries in the original multicast address list and the alternate multicast address list are meaningful. A replacement address (determined by the replacement multicast address) may be added to the list of replacement addresses for a particular entry (determined by the original multicast address) of a particular multicast steering table (determined by the opcode) based on the opcode, original multicast address, replacement multicast address, etc.

When an opcode in the opcode list is 5-8, the corresponding entries in the original multicast address list and the alternate multicast address list are meaningful. A replacement address (determined by the replacement multicast address) may be deleted from the list of replacement addresses for a particular entry (determined by the original multicast address) of a particular multicast steering table (determined by the opcode) based on information such as the opcode, the original multicast address, the replacement multicast address, etc.

When an opcode in the opcode list is 9-10, the corresponding entries in the original multicast address list and the logical port address list are meaningful. A specific bit (determined by the logical port address) in a specific entry (determined by the original multicast address) of a specific multicast information table (determined by the operation code) can be set to 1 (start transmission) according to the operation code, the original multicast address, the logical port address and the like.

When an opcode in the opcode list is 11-12, the corresponding entries in the original multicast address list and the logical port address list are meaningful. A specific bit (determined by the logical port address) in a specific entry (determined by the original multicast address) of a specific multicast information table (determined by the operation code) can be set to 0 (stop transmission) according to the operation code, the original multicast address, the logical port address and the like.

When an opcode in the opcode list is 13-14, the corresponding entry in the original multicast address list makes sense. All bits in a specific entry (determined by the original multicast address) of a specific multicast information table (determined by the operation code) can be set to 0 (transmission is stopped) according to the operation code, the original multicast address and other information.

The PDUs of the multicast link control response are transmitted using unicast packets, and the format may be as shown in the following table:

information element	Existence of	Format	Length of	Description of the preferred embodiment
					List of operation codes	M	TLV
Responsive to the result	M	V	4	Success 0, failure others
					Multicast address list	C	TLV	Original multicast address information
Multicast address list	C	TLV		Replacement of multicast address information
					Logical port address list	C	TLV
Message check code	O	TLV	4

In one case, if the device on the local multicast link is the local data source and is the terminal, a data source status control command is sent to the device to start sending the multicast data stream.

In another case, if the device on the local multicast link is a local data source and is a terminal sub-control server or a boundary sub-control server, the device sends the multicast link control command to the device to open a transmission channel of the multicast data stream.

In another case, if the device on the local multicast link is a local data source and a boundary router, sending a multicast link control command to the device to open a transmission channel of a multicast data stream;

In another case, if the device on the local multicast link is a data forwarding node, a multicast link control command is sent to the device to open a transmission channel of the multicast data stream.

In another case, if the device on the local multicast link is a local data sink and is a terminal sub-control server or a boundary sub-control server, it is determined whether the multicast data stream serves the specified multicast service.

If the specified multicast service is serviced, a multicast link control command is sent to the device to begin replacing the multicast address of the multicast data stream with the specified multicast address.

For multicast services such as video conferences, operations such as switching speakers (terminals) are frequently performed so that multicast data streams viewed by a large number of terminals are frequently changed simultaneously, and in order to reduce communication overhead with data forwarding nodes, a terminal sub-control server or a boundary sub-control server may replace a multicast address in the multicast service with a designated multicast address.

When the terminal sub-control server or the boundary sub-control server replaces the multicast address, the terminal sub-control server or the boundary sub-control server is not only a data sink but also a data source, and because the terminal sub-control server or the boundary sub-control server can simultaneously replace the multicast address of the multi-path multicast data stream, the multicast data stream after address replacement is distinguished through different channel numbers.

In another embodiment of the present application, step 1705 may include the following sub-steps:

sub-step 17054, querying traffic information of the multicast data stream, and remaining bandwidth information of devices on the local multicast link.

Substep 17055, determining whether the remaining bandwidth information of the device on the local multicast link satisfies the traffic information of the multicast data stream; if so, then sub-step 17056 is performed, otherwise, sub-step 17057 is performed.

Sub-step 17056, allowing to build a local multicast link for the multicast data stream to be transmitted from the local data source to the local data sink.

Substep 17057, refraining from establishing a local multicast link for transmission of the multicast data stream from the local data source to the local data sink.

The multicast management module may query the traffic information (i.e., occupied bandwidth) of the local multicast link between the local data sink and the local data source in the data source information table, compare the traffic information with the remaining bandwidth information of each device on the local multicast link, determine whether the bandwidth requirement is met, allow the local multicast link to be opened if the bandwidth requirement is met, and prohibit the local multicast link from being opened otherwise.

In one embodiment of the present application, after step 1705, the multicast management module may generate an add data sink response to notify the completion of creating the global multicast link.

The added data sink response includes information such as multicast address and data stream media attribute.

And after receiving the data sink adding response, the service processing module continues to process the multicast service.

In an embodiment of the present application, if there is no multicast data stream and the global data source does not belong to the autonomous cloud, an autonomous cloud that can be routed to the autonomous cloud to which the global data source belongs and is connected to the autonomous cloud is queried to obtain the previous hop autonomous cloud.

Further, the multicast management module searches the device static information table according to the local device number of the boundary router in the global data source direction to obtain the local logical address of the device static information table, and then searches the autonomous cloud access table according to the local logical address of the boundary router to obtain the information (such as the global device number, the global logical address and the like) of the corresponding previous hop master server.

Sending a command of adding a remote data sink to a master control server in the previous-hop autonomous cloud, wherein the command of adding the remote data sink comprises information such as a global device number of the global data sink, a channel number of the global data sink, a global device number of the global data source, a channel number of the global data source and the like, so as to inform the master control server in the previous-hop autonomous cloud to establish a global multicast link for transmitting at least part of multicast data streams from the global data source to the global data sink in the previous-hop autonomous cloud.

And waiting for a response of adding the remote data sink sent by the master control server of the previous hop of the autonomous cloud.

Referring to fig. 18, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application may specifically include the following steps:

step 1801, the master control server in the autonomous cloud receives a command to add a foreign data sink.

The master control server in the autonomous cloud can receive a command of adding a remote data sink of the master control server in the connected autonomous cloud.

The remote data sink adding command comprises information such as a global device number of a global data sink, a channel number of the global data sink, a global device number of a global data source, a channel number of the global data source and the like.

The PDU added with the allopatric data transfer command is transmitted using a unicast packet, and the format can be as shown in the following table:

information element	Presence of	Format	Length of	Description of the invention
					Global device number	C	TLV	16	Global device number for global data sink
Channel number	C	TLV	2	Channel number of global data sink
					Global device number	C	TLV	16	Global device number of global data source
Channel number	C	TLV	2	Channel number of global data source
					Message check code	O	TLV	4

Step 1802, inquiring an autonomous cloud to which a global data source and a global data sink in the autonomous network belong according to the command of adding the remote data sink.

And after receiving the command of adding the remote data sink, the master control server judges whether the global data sink and the global equipment number of the global data source are the equipment in the self-control cloud or not according to the global data sink and the global equipment number of the global data source.

In an embodiment of the present application, after step 1802, if the global data source belongs to the autonomous cloud, it is determined whether the global data source is a terminal, a terminal sub-control server, or a boundary sub-control server.

And if so, determining that the global data source is legal and allowing the processing to be continued.

And if not, determining that the global data source is illegal, inquiring an autonomous cloud which can be routed to the autonomous cloud to which the global data is converged and is connected with the autonomous cloud, and obtaining the next hop of autonomous cloud.

And sending a foreign data sink adding response to the master control server in the next hop autonomous cloud to inform the occurrence of errors, and ending the processing.

In another embodiment of the present application, after step 1802, if the global data sink belongs to the self-governing cloud, it is determined that the global data sink is illegal, and an autonomous cloud that can be routed to the self-governing cloud to which the global data sink belongs and is connected to the self-governing cloud is queried to obtain the next-hop self-governing cloud.

And sending a response of adding the remote data sink to the master control server in the next-hop autonomous cloud to inform that an error occurs, and ending the processing.

Step 1803, determining whether there is a multicast data stream corresponding to the add allopatric data sink command in the autonomous cloud.

The main control server can search whether the multicast data stream exists through the data source index table and then search whether the multicast data stream exists through the data source information table.

Step 1804, if the multicast data stream exists, determining a local data source and a local data sink in the local autonomous cloud according to the global data source and the autonomous cloud to which the global data sink belongs.

In another case, a border router that can be routed to an autonomous cloud to which the global data sink belongs and belongs to the local autonomous cloud is queried as a local data sink in the local autonomous cloud.

Step 1805, a local multicast link for transmitting the multicast data stream from the local data source to the local data sink is established in the autonomous cloud, so as to establish a global multicast link for transmitting at least part of the multicast data stream from the global data source to the global data sink.

The main control server can calculate a local multicast link of the multicast data stream added with the allopatric data sink command in the autonomous cloud according to the local equipment number (local data sink) of the global data sink and the local data source equipment number (local data source) in the data source information table, so that the global multicast link in the autonomous network is established.

In one embodiment of the present application, step 1805 may include the following sub-steps:

sub-step 18051, calculating a local multicast link in the local autonomous cloud, where the multicast data stream is transmitted from the local data source to the local data sink via the data forwarding node.

Sub-step 18052, sending a multicast link establishment command to the device on the local multicast link to open the local multicast link.

And a substep 18053 of receiving a multicast link establishment response returned by the device on the local multicast link.

The main control server can send a corresponding multicast link establishment command according to the device type of each device on the local multicast link, so that the multicast data stream can be sent from a local data source and transmitted to a local data sink through the data forwarding node, and the local multicast link is opened.

And after receiving the multicast link establishment response of each device on the local multicast link, the main control server updates the related multicast table.

In a specific implementation, the multicast link establishment command comprises a data source state control command and a multicast link control command; therefore, the corresponding multicast link establishment response includes a data source state control response and a multicast link control response.

In one case, if the device on the local multicast link is a local data source and a terminal, the data source status control command is sent to the device to start sending the multicast data stream.

In another case, if the device on the local multicast link is a local data source and is a terminal sub-control server or a boundary sub-control server, a multicast link control command is sent to the device to open a transmission channel of the multicast data stream.

In another case, if the device on the local multicast link is a local data source and is a boundary router, the device sends the multicast link control command to open a transmission channel of the multicast data stream.

In another embodiment of the present application, step 1805 may include the following sub-steps:

sub-step 18054, inquiring the traffic information of the multicast data stream and the remaining bandwidth information of the device on the local multicast link.

Substep 18055, determining whether the remaining bandwidth information of the device on the local multicast link satisfies the traffic information of the multicast data stream; if yes, go to substep 18056, otherwise go to substep 18057.

Sub-step 18056, allows to build a local multicast link for the transmission of the multicast data stream from the local data source to the local data sink.

Substep 18057, prohibiting the establishment of a local multicast link for the transmission of the multicast data stream from the local data source to the local data sink.

The main control server can inquire the flow information (i.e. occupied bandwidth) of the local multicast link between the local data sink and the local data source in the data source information table, compare the flow information with the residual bandwidth information of each device on the local multicast link, judge whether the bandwidth requirement is met, if the bandwidth requirement is met, allow to open the local multicast link, otherwise forbid to open the local multicast link.

In an embodiment of the present application, after step 1805, an autonomous cloud that can be routed to the autonomous cloud to which the global data is converged and connected to the autonomous cloud is queried, and a next-hop autonomous cloud is obtained.

Further, the master control server searches the device static information table according to the local device number of the boundary router in the global data sink direction to obtain the local logical address of the device static information table, and then searches the autonomous cloud access table according to the local logical address of the boundary router to obtain the corresponding information (such as the global device number, the global logical address and the like) of the next hop master control server.

And sending a response of adding a remote data sink to a master control server in the next-hop autonomous cloud, wherein the remote data sink response comprises a multicast address of the global data source in the autonomous cloud besides information such as the global device number of the global data sink, the channel number of the global data sink, the global device number of the global data source, the channel number of the global data source and the like, so as to inform the master control server in the next-hop autonomous cloud to establish a global multicast link for transmitting at least part of multicast data streams from the global data source to the global data sink in the next-hop autonomous cloud.

In an embodiment of the present application, if there is no multicast data stream and the global data source belongs to the autonomous cloud, the autonomous cloud that can be routed to the global data sink and connected to the autonomous cloud is queried to obtain the next hop autonomous cloud.

And sending a foreign data sink adding response to the master control server in the next-hop autonomous cloud to inform that an error occurs.

And sending a command of adding a remote data sink to the master control server in the previous-hop autonomous cloud to inform the master control server in the previous-hop autonomous cloud to establish a global multicast link for transmitting at least part of multicast data streams from the global data source to the global data sink in the previous-hop autonomous cloud.

And waiting for the response of adding the remote data sink sent by the master control server of the previous hop of the autonomous cloud.

Referring to fig. 19, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application is shown, which may specifically include the following steps:

Step 1901, the master server in the autonomous cloud receives a response of adding the remote data sink.

The master control server in the autonomous cloud can receive the remote data sink adding response of the master control server in the connected autonomous cloud.

The added allopatric data sink response comprises information such as a global device number of a global data sink, a channel number of the global data sink, a global device number of a global data source, a channel number of the global data source, and a multicast address of the global data source in a previous hop autonomous cloud.

The PDU with the allopatric data transfer response is transmitted using unicast packets, and the format can be as shown in the following table:

information element	Presence of	Format	Length of	Description of the invention
					Responsive to the result	M	V	4	0 is successful and others are failed
Global device number	C	TLV	16	Global device number for global data sink
					Channel number	C	TLV	2	Channel number of global data sink
Global device number	C	TLV	16	Global device number of global data source
					Channel number	C	TLV	2	Channel number of global data source
Multicast address	C	TLV	4
					Data stream flow	C	TLV	4	Flow of multicast data stream
Data stream media attributes	C	TLV		Media attributes for multicast data streams
					Message check code	O	TLV	4

The multicast address indicates a local multicast address of a global data source in an autonomous cloud to which a sender (a certain master server) adding the allopatric data sink response belongs.

Step 1902, querying an autonomous cloud to which a global data source and a global data sink in the autonomous network belong according to the response of the added allopatric data sink.

And after receiving the response of adding the remote data sink, the master control server judges whether the remote data sink is a device in the self-control cloud or not according to the global data sink and the global device number of the global data source.

In an embodiment of the present application, after step 1902, if the global data source belongs to the autonomous cloud, it is determined that the global data source is illegal, it is determined that an error occurs, and the process is ended.

In another embodiment of the present application, after step 1902, if the global data sink belongs to the autonomous cloud, it is determined whether the global data sink is a terminal, a terminal sub-control server, or a boundary sub-control server.

If not, determining that the global data sink is illegal, determining that an error occurs, and ending the processing.

Step 1903, determining whether there is a multicast data stream corresponding to the add allopatric data sink response in the self-managing cloud.

And if the multicast data stream exists, determining that an error occurs, and ending the processing.

If there is no multicast data stream, processing may continue.

Step 1904, if the multicast data stream does not exist, determining a local data source and a local data sink in the local autonomous cloud according to the global data source and the autonomous cloud to which the global data sink belongs.

In one case, a border router that can be routed to an autonomous cloud to which the global data source belongs and that belongs to the local autonomous cloud is queried as a local data source in the local autonomous cloud.

In another case, if the global data sink does not belong to the local autonomous cloud, a border router that can be routed to the autonomous cloud to which the global data sink belongs and belongs to the local autonomous cloud is queried as the local data sink in the local autonomous cloud.

Step 1905, a local multicast link for transmitting the multicast data stream from the local data source to the local data sink is established in the autonomous cloud, so as to establish a global multicast link for transmitting at least part of the multicast data stream from the global data source to the global data sink.

In one embodiment of the present application, step 1905 may comprise the sub-steps of:

substep 19051, calculating a local multicast link in the local autonomous cloud, where the multicast data stream is transmitted from the local data source to the local data sink via a data forwarding node.

Sub-step 19052 sends a multicast link setup command to devices on the local multicast link to open the local multicast link.

And a sub-step 19053 of receiving a multicast link establishment response returned by the device on the local multicast link.

In a specific implementation, the multicast link establishment command comprises a multicast link control command; accordingly, the corresponding multicast link setup response includes a multicast link control response.

In one case, if the device on the local multicast link is the local data source, a multicast link control command is sent to the device to start sending the multicast data stream.

If the specified multicast service is served, a multicast link control command is sent to the device to replace the multicast address of the multicast data stream with the specified multicast address.

In another embodiment of the present application, step 1905 may comprise the sub-steps of:

sub-step 19054, inquiring the traffic information of the multicast data stream, the remaining bandwidth information of the devices on the local multicast link.

Substep 19055, determining whether the remaining bandwidth information of the device on the local multicast link satisfies the traffic information of the multicast data stream; if yes, go to substep 19056, if no, go to substep 19057.

Sub-step 19056 allows for the establishment of a local multicast link for the transmission of the multicast data stream from the local data source to the local data sink.

Sub-step 19057, refraining from establishing a local multicast link for transmission of the multicast data stream from the local data source to the local data sink.

In one embodiment of the present application, if there is no multicast data stream, the master server may create a multicast data stream in the local data source.

And sending a multicast link control command to the local data source so as to replace the multicast address of the self-control cloud of the previous hop with the multicast address of the self-control cloud.

In an embodiment of the present application, after step 1905, if the global data sink belongs to the local autonomous cloud, an add data sink response is generated to notify that the establishment of the global multicast link is completed.

In an embodiment of the present application, after step 1905, if the global data sink does not belong to the autonomous cloud, the autonomous cloud that can be routed to the global data sink and connected to the autonomous cloud is queried to obtain the next hop autonomous cloud.

And sending a response of adding the remote data sink to the master control server in the next-hop autonomous cloud to inform the master control server in the next-hop autonomous cloud of establishing a global multicast link for transmitting at least part of multicast data streams from the global data source to the global data sink in the next-hop autonomous cloud.

Referring to fig. 20, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application is shown, which may specifically include the following steps:

step 2001, the master server in the autonomous cloud receives a delete data sink request.

And the service processing module of the master control server sends a request for deleting the data sink to the multicast management module according to the requirement of the multicast service.

The data sink deleting request comprises information such as the global device number of the global data sink, the channel number of the global data sink, the global device number of the global data source, the channel number of the global data source and the like.

Step 2002, querying the global data source and the autonomous cloud to which the global data sink belongs in the autonomous network according to the request for deleting the data sink.

And after receiving the request for deleting the data sink, the multicast management module judges whether the data sink is the equipment in the self-healing cloud or not according to the global equipment numbers of the global data sink and the global data source.

In an embodiment of the present application, after step 2002, if the global data source belongs to the autonomous cloud, it is determined whether the global data source is a terminal, a terminal sub-control server, or a boundary sub-control server.

If not, determining that the global data source is illegal, generating a deleted data sink response to inform that an error occurs, and ending the processing.

In another embodiment of the present application, after step 2002, if the global data sink belongs to the autonomous cloud, it is determined whether the global data source is a terminal, a terminal sub-control server, or a boundary sub-control server.

If not, determining that the global data sink is illegal, generating a data sink deleting response to inform that an error occurs, and ending the processing.

In another embodiment of the present application, after step 2002, if the global data sink does not belong to the autonomous cloud, the global data sink is determined to be illegal, a delete data sink response is generated to notify that an error occurs, and the process is ended.

Step 2003, judging whether a multicast data stream corresponding to the data sink deletion request exists in the autonomous cloud.

If there is a multicast data stream, processing may continue.

And if the multicast data stream does not exist, generating a deleted data sink response to inform that an error occurs, and ending the processing.

Step 2004, if the multicast data stream exists, determining a local data source and a local data sink in the local autonomous cloud according to the global data source and the autonomous cloud to which the global data sink belongs.

Step 2005, in the autonomous cloud, closing a local multicast link through which the multicast data stream is transmitted from the local data source to the local data sink, so as to close a global multicast link through which at least part of the multicast data stream is transmitted from the global data source to the global data sink.

The multicast management module may calculate a local multicast link of the multicast data stream requested by deleting the data sink in the autonomous cloud according to a local device number (local data sink) of the global data sink and a local data source device number (local data source) in the data source information table, so as to close the global multicast link in the autonomous network.

In one embodiment of the present application, step 2005 may include the following sub-steps:

substep 20051, calculating a local multicast link of the multicast data stream transmitted from the local data source to the local data sink via the data forwarding node in the local autonomous cloud.

Sub-step 20052, sending a multicast link close command to the device on the local multicast link to close the local multicast link.

And a substep 20053 of receiving a multicast link shutdown response returned by the device on the local multicast link.

The multicast management module may send a corresponding multicast link closing command according to the device type of each device on the local multicast link, so that the multicast data stream stops being sent from the local data source and stops being transmitted to the local data sink via the data forwarding node, thereby closing the local multicast link.

And after receiving the multicast link closing response of each device on the local multicast link, the multicast management module updates the related multicast table.

In a specific implementation, the multicast link closing command comprises a data source state control command and a multicast link control command; therefore, the corresponding multicast link shutdown response includes a data source state control response and a multicast link control response.

In one case, if the device on the local multicast link is a local data source and a terminal, the data source status control command is sent to the device to stop sending the multicast data stream.

In another case, if the device on the local multicast link is a local data source and is a terminal sub-control server or a boundary sub-control server, the device sends the multicast link control command to close the transmission channel of the multicast data stream.

In another case, if the device on the local multicast link is a local data source and is a boundary router, a multicast link control command is sent to the device to close the transmission channel of the multicast data stream.

In another case, if the device on the local multicast link is a data forwarding node, a multicast link control command is sent to the device to close the transmission channel of the multicast data stream.

And if the specified multicast service is served, sending a multicast link control command to the equipment to stop replacing the multicast address of the multicast data stream with the specified multicast address.

In an embodiment of the present application, after step 2005, if the global data source belongs to the self-governing cloud, a delete data sink response is generated to notify that closing of the global multicast link is completed.

In another embodiment of the present application, after step 2005, if the global data source does not belong to the local autonomous cloud, it is determined whether there is another data sink in the local autonomous cloud to receive the multicast data stream, except the local data sink.

And if so, generating a data sink deleting response to inform the completion of closing the global multicast link.

And if not, inquiring the autonomous cloud which can be routed to the autonomous cloud belonging to the global data source and is connected with the autonomous cloud, and obtaining the autonomous cloud of the previous hop.

Sending a command for deleting the remote data sink to a master control server in the previous-hop autonomous cloud, wherein the command for deleting the remote data sink comprises information such as a global device number of the global data sink, a channel number of the global data sink, a global device number of the global data source, a channel number of the global data source and the like, so as to inform the master control server in the previous-hop autonomous cloud of closing a global multicast link for transmitting at least part of multicast data streams from the global data source to the global data sink in the previous-hop autonomous cloud.

And waiting for the remote data sink deletion response sent by the master control server of the previous-hop autonomous cloud.

Referring to fig. 21, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application is shown, which may specifically include the following steps:

step 2101, the master control server in the autonomous cloud receives a command to delete a foreign data sink.

The master control server in the autonomous cloud can receive a command of deleting the remote data sink from the master control server in the connected autonomous cloud.

The remote data sink deleting command comprises information such as the global equipment number of the global data sink, the channel number of the global data sink, the global equipment number of the global data source, the channel number of the global data source and the like.

The PDU for deleting the foreign data transfer command is transmitted using a unicast packet, and the format can be as shown in the following table:

step 2102, querying an autonomous cloud to which a global data source and global data sink belong in the autonomous network according to the command of deleting the remote data sink.

And after receiving the command of deleting the remote data sink, the master control server judges whether the remote data sink is a device in the self-control cloud or not according to the global data sink and the global device number of the global data source.

In an embodiment of the present application, after step 2102, if the global data source belongs to the autonomous cloud, it is determined whether the global data source is a terminal, a terminal sub-control server, or a boundary sub-control server.

If not, determining that the global data source is illegal, inquiring an autonomous cloud which can be routed to the global data sink and is connected with the autonomous cloud, and obtaining the next hop of autonomous cloud.

And sending a remote data sink deleting response to the master control server in the next-hop autonomous cloud to inform that an error occurs, and ending the processing.

In another embodiment of the present application, after step 2102, if the global data sink belongs to the autonomous cloud, it is determined that the global data sink is illegal, and an autonomous cloud that can be routed to the autonomous cloud to which the global data sink belongs and is connected to the autonomous cloud is queried to obtain a next hop autonomous cloud.

Step 2103, judging whether the multicast data stream corresponding to the remote data sink deleting command exists in the autonomous cloud.

If there is a multicast data stream, processing may continue.

And if the multicast data stream does not exist, inquiring an autonomous cloud which can be routed to the global data sink and is connected with the autonomous cloud, and obtaining the next hop of autonomous cloud.

Step 2104, if the multicast data stream exists, determining a local data source and a local data sink in the local autonomous cloud according to the autonomous cloud to which the global data source and the global data sink belong.

In another case, if the global data source does not belong to the local autonomous cloud, querying a border router which can be routed to the autonomous cloud to which the global data source belongs and belongs to the local autonomous cloud, as a local data source in the local autonomous cloud.

Step 2105, in the autonomous cloud, closing a local multicast link where the multicast data stream is transmitted from the local data source to the local data sink, so as to close a global multicast link where at least part of the multicast data stream is transmitted from the global data source to the global data sink.

In one embodiment of the present application, step 2105 may include the following sub-steps:

substep 21051, calculating a local multicast link in the local autonomous cloud, wherein the local multicast link is transmitted by the multicast data stream from the local data source to the local data sink via the data forwarding node.

Sub-step 21052, sending a multicast link shutdown command to the devices on the local multicast link to shutdown the local multicast link.

And a substep 21053 of receiving a multicast link shutdown response returned by the device on the local multicast link.

The main control server may send a corresponding multicast link closing command according to the device type of each device on the local multicast link, so that the multicast data stream stops being sent from the local data source, and stops being transmitted to the local data sink via the data forwarding node, thereby closing the local multicast link.

And after receiving the multicast link closing response of each device on the local multicast link, the main control server updates the related multicast table.

In a specific implementation, the multicast link closing command comprises a data source state control command and a multicast link control command; therefore, the corresponding multicast link shutdown response includes a data source status control response, a multicast link control response.

In another case, if the device on the local multicast link is a local data source and is a terminal sub-control server or a boundary sub-control server, a multicast link control command is sent to the device to close a transmission channel of the multicast data stream.

In another case, if the device on the local multicast link is a local data source and is a boundary router, a multicast link control command is sent to the device to close a transmission channel of the multicast data stream.

In an embodiment of the present application, after step 2105, if the global data source belongs to the autonomous cloud, the autonomous cloud that can be routed to the global data sink and is connected to the autonomous cloud is queried to obtain the next hop autonomous cloud.

Further, the master control server searches the device static information table according to the local device number of the border router in the global data sink direction to obtain the local logical address thereof, and then searches the autonomous cloud access table according to the local logical address of the border router to obtain the corresponding information (such as the global device number, the global logical address and the like) of the next-hop master control server.

And sending a response for deleting the remote data sink to a master control server in the next-hop autonomous cloud, wherein the response for deleting the remote data sink comprises information such as the global device number of the global data sink, the channel number of the global data sink, the global device number of the global data source, the channel number of the global data source and the like, so as to inform the master control server in the next-hop autonomous cloud of closing the multicast data stream in the next-hop autonomous cloud.

In an embodiment of the present application, after step 2105, if the global data source belongs to another local autonomous cloud, it is determined whether there are other data sinks besides the local data sink in the local autonomous cloud to receive the multicast data stream.

And if so, inquiring the autonomous cloud which can be routed to the global data sink and is connected with the autonomous cloud to obtain the next hop autonomous cloud.

And sending a remote data sink deletion response to the master control server in the next-hop autonomous cloud to inform the master control server in the next-hop autonomous cloud of closing the multicast data stream in the next-hop autonomous cloud.

And if not, inquiring the autonomous cloud which can be routed to the autonomous cloud to which the global data source belongs and is connected with the autonomous cloud, and obtaining the autonomous cloud of the previous hop.

Referring to fig. 22, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application may specifically include the following steps:

step 2201, the main control server in the autonomy cloud receives a response of deleting the remote data sink.

The master control server in the autonomous cloud can receive a remote data sink deletion response of the master control server in the connected autonomous cloud.

The remote data sink deleting response comprises information such as the global equipment number of the global data sink, the channel number of the global data sink, the global equipment number of the global data source, the channel number of the global data source and the like.

The PDU with the foreign data transfer response deleted is transmitted by using a unicast packet, and the format can be shown as the following table:

and 2202, responding and inquiring the autonomous cloud to which the global data source belongs in the autonomous network according to the deleted remote data sink.

And after receiving the response of adding and deleting the remote data sink, the master control server judges whether the remote data sink is a device in the autonomous cloud according to the global device number of the global data source.

In one embodiment of the present application, after step 2202, if the global data source belongs to the autonomous cloud, an error is confirmed to occur, and the process is ended.

Step 2203, judging whether the multicast data stream corresponding to the deleted remote data sink response exists in the self-managing cloud.

If there is a multicast data stream, processing may continue.

If the multicast data stream does not exist, the occurrence of an error is confirmed, and the processing is finished.

Step 2204, if the multicast data stream exists, judging whether a data tandem exists in the autonomous cloud or not to receive the multicast data stream; if yes, go to step 2205, otherwise go to step 2206.

In a specific implementation, the master control server may check whether there are any data sinks in the autonomous cloud to receive the multicast data stream by searching the multicast routing table.

And step 2205, ignoring the deleted allopatric data sink response.

If the data sink in the autonomous cloud receives the multicast data stream, the deletion of the allopatric data sink response can be omitted.

Step 2206, determining a local data source in the local autonomous cloud according to the autonomous cloud to which the global data source belongs.

If no data sink in the autonomous cloud receives the multicast data stream, a boundary router which is routed to a global data source and belongs to the autonomous cloud can be inquired and used as a local data source in the autonomous cloud.

Step 2207, closing the multicast data stream in the local data source.

In a particular implementation, step 2207 may include the following sub-steps:

And a substep 22071, sending a multicast link control command to the local data source to stop replacing the multicast data stream with the multicast address of the local autonomous cloud from the previous hop of the autonomous cloud.

Sub-step 22072, receiving the multicast link control response sent by the local data source.

Sub-step 22073, deleting said multicast data stream.

In a specific implementation, the master server may send a multicast link control command to the border router in the global data source direction, where the multicast link control command is used to configure a multicast steering table of the border router to stop address replacement.

After receiving the multicast link control response of the border router, the main control server updates the related multicast table and deletes the multicast data stream.

In one embodiment of the application, an autonomous cloud to which global data sinks in the autonomous network belong is queried in response to deleting the foreign data sink.

In this embodiment, after receiving the response of deleting the remote data sink, the master control server determines whether the remote data sink is a device in the autonomous cloud according to the global device number of the global data sink.

And if the global data sink belongs to the autonomous cloud, judging whether the global data sink is a terminal or a terminal sub-control server or a boundary sub-control server.

If yes, determining that the global data are legal to merge, and allowing the processing to be continued.

If not, determining that the global data sink is illegal, confirming that an error occurs, and ending the processing.

And if the global data sink belongs to the autonomous cloud, generating a data sink deleting response to inform that the closing of the global multicast link is finished.

And if the global data sink does not belong to the autonomous cloud, inquiring the autonomous cloud which can be routed to the autonomous cloud to which the global data sink belongs and is connected with the autonomous cloud to obtain the next hop of autonomous cloud.

Referring to fig. 23, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application is shown, which may specifically include the following steps:

step 2301, a master control server in the autonomous cloud receives a request for creating a data source.

And the service processing module of the main control server sends a request for establishing a data source to the multicast management module according to the requirement of the service flow.

The data source creating request comprises related information such as a data source type (a physical data source or a virtual data source), a data source global equipment number (a terminal or a terminal sub-control server), a data source channel number and the like.

And 2302, inquiring the autonomous cloud to which the global data source belongs in the autonomous network according to the request for creating the data source.

And after receiving the request for creating the data source, the multicast management module judges whether the data source is a device in the autonomous cloud according to the global device number of the global data source.

If the global data source belongs to the autonomy cloud, processing can continue.

And if the global data source does not belong to the autonomous cloud, generating a data source creating response to inform the service processing module of an error, and ending the processing.

Step 2303, if the global data source belongs to the autonomous cloud, determining whether a multicast data stream corresponding to the data source creating request exists in the autonomous cloud.

If there is no multicast data stream, processing may continue.

And if the multicast data stream exists, generating a create data source response to inform that an error occurs.

In an embodiment of the application, if the global data source belongs to the autonomous cloud, it may be determined whether the global data source is a terminal, a terminal sub-control server, or a boundary sub-control server.

If not, determining that the global data source is illegal, generating a data source creating response to inform that an error occurs, and ending the processing.

Step 2304, if the multicast data stream does not exist, creating a multicast data stream in the global data source.

In a specific implementation, the multicast management module may perform operations such as allocating a multicast address, updating a data source information table, updating a data source index table, and the like, and create a multicast data stream.

Step 2305, a create data source response is generated to notify completion of creating the multicast data stream.

After the multicast data stream is created, the multicast management module sends a data source creating response to the service processing module, wherein the data source creating response comprises information such as a multicast address.

Referring to fig. 24, a flowchart illustrating steps of another service communication method of an autonomous network according to an embodiment of the present application may specifically include the following steps:

step 2401, the master control server in the autonomous cloud receives the data source destroying request.

And the service processing module of the master control server sends a data source destroying request to the multicast management module according to the requirement of the service flow.

The data source destroying request includes relevant information such as a data source type (a physical data source or a virtual data source), a data source global device number (a terminal or a terminal sub-control server), a data source channel number and the like.

Step 2402, inquiring an autonomous cloud to which a global data source belongs in an autonomous network according to the request of destroying the data source.

And after receiving the data source destroying request, the multicast management module judges whether the data source is a device in the autonomous cloud or not according to the global device number of the global data source.

If the global data source belongs to the autonomous cloud, processing can continue.

If the global data source does not belong to the autonomous cloud, a data source destruction response can be generated to inform the service processing module of an error, and the processing is finished.

Step 2403, if the global data source belongs to the self-governing cloud, determining whether a multicast data stream corresponding to the data source creating request exists in the self-governing cloud.

If there is a multicast data stream, processing may continue.

And if the multicast data stream does not exist, generating a destroy data source response to inform that an error occurs.

If not, determining that the global data source is illegal, generating a response of destroying the data source to inform that an error occurs, and ending the processing.

Step 2404, if the multicast data stream exists, judging whether a data sink exists in the self-autonomous cloud to receive the multicast data stream; if not, go to step 2405.

In a specific implementation, the multicast management module may check whether there is any data sink in the autonomous cloud to receive the multicast data stream by searching the multicast routing table.

Step 2405, destroying the multicast data stream in the global data source.

In a specific implementation, the multicast management module may perform operations such as updating the multicast routing table, updating the data source index table, updating the data source information table, releasing the multicast address, and the like, and destroy the multicast data stream.

Step 2406, generating a destroy data source response to notify that the multicast data stream is destroyed.

And after the multicast data stream is destroyed, the multicast management module sends a data source destroying response to the service processing module, wherein the data source destroying response comprises information such as a multicast address.

Secondly, in the embodiment of the application, the equipment in the autonomous network is registered on the master control server, and then the equipment is accessed into the autonomous network through the network access process to obtain the service of the autonomous network. Therefore, the illegal access of the equipment can be prevented, the safety and the manageability of the autonomous network are improved, and the stable operation of the autonomous network is also ensured.

Fourthly, in the embodiment of the application, the network access parameters of each autonomous cloud are accurately configured in a hierarchical access mode among the autonomous clouds through the network access process between the boundary router and the adjacent autonomous clouds, and a clear network topology is established. Therefore, devices among different autonomous clouds can communicate with each other without routing negotiation, so that the stability during communication is ensured, and the expandability of the autonomous network is also ensured.

Seventh, in the embodiment of the present application, various existing network communication technologies (such as ethernet) may be fused at the bottom layer, so that a completely new transmission network does not need to be established from a physical layer, the cost of network modification may be greatly reduced, and the possibility of actual operation is improved. Meanwhile, the problem of poor reliability and usability of an IP network is solved, the requirements of controllability, manageability and service quality guarantee of an operation level network are met at least, and the large-scale networking capability is achieved.

Ninth, in the embodiment of the present application, a data transmission manner adopts a distributed configuration and management method, and a master control server of each autonomous cloud does not need to perform unified management on multicast links of a whole network, so that requirements on software and hardware resources of the master control server (such as processing capability, memory space, and the like) are greatly reduced.

In order to make those skilled in the art better understand the embodiment of the present application, a configuration method of a multicast link in an autonomous network in the embodiment of the present application is described below by using a specific example.

Example one, Single autonomous cloud Access network

As shown in fig. 25, assuming that the autonomous cloud C2 is located at layer 2 in the autonomous network, for simplicity, the boundary sub-control server and the boundary router are omitted, the main control server a2, the terminal sub-control server B21, the terminal sub-control server B22, and the terminal sub-control server B23 are connected in the same switching network, the terminal sub-control server B21, the terminal T21, and the terminal T22 are connected in the same switching network, the terminal sub-control server B22, the terminal T23, and the terminal T24 are connected in the same switching network, and the terminal sub-control server B23, the terminal T25, and the terminal T26 are connected in the same switching network.

S1, device initialization.

S11, the power-on initialization of the master control server A2

In an initialization stage, the master control server a2 obtains the system parameters of the autonomous cloud as follows:

the device number prefix is 60031-

The prefix of the logical address is 4231-

Master control cloudlet level of 4

The master control micro cloud topology is star type

The number of the local equipment of the master control server is 90002

The logical port address of the main control server is fb

The MAC address of the master server is 00:00:00:02: fb: 00.

According to the information, the local logic address of the master server a2 is calculated to be 0xfb00, the global device number is 60031-.

The registration information of the device is obtained as follows:

the number of the logical port addresses and the MAC addresses of the terminal sub-control server B21, the terminal sub-control server B22 and the terminal sub-control server B23 is 2, the first represents the information of the port No. 0 (downlink interface), and the second represents the information of the port No. 1 (uplink interface).

The central device number of the terminal sub-control server B21 is 0, which indicates that it is a central device in the main control micro cloud with a star topology type, so the central device numbers of the terminal sub-control server B22 and the terminal sub-control server B23 are 70021 (terminal sub-control server B21).

If the topology of the master cloudlet is the full switching topology, the central device numbers of the terminal sub-control server B22 and the terminal sub-control server B23 should be 0.

It should be noted that the topology field of the cloudlet of the 3 terminal sub-control servers represents the topology of the 3 sub-control cloudlets rather than the topology of the master cloudlet.

Since the central device in the sub-control micro cloud is a terminal sub-control server (i.e. a manager), the number of the central device of each terminal is the same as the number of the manager.

The master control server a2 initializes the device static information table according to the registration information, and calculates the local logical address and the global device number of each device, and the global logical address are as follows:

Similarly, there are 2 local logical addresses and 2 global logical addresses of the terminal sub-control server B21, the terminal sub-control server B22, and the terminal sub-control server B23, which correspond to the port 0 and the port 1, respectively.

The master server a2 initializes the device dynamic information table and the address number mapping table according to the above information.

S12, the terminal sub-control server B21, the terminal sub-control server B22 and the terminal sub-control server B23 are electrified and initialized

And in an initialization stage, the terminal sub-control server B21, the terminal sub-control server B22 and the terminal sub-control server B23 obtain the respective logic device types, the logic device identifications and the MAC addresses of the 2 interfaces.

During initialization, the receiving and filtering rules of the data packets also need to be set, and the data packets which do not accord with all the rules can be discarded. And only the connection packet can be received under the condition of no network access.

The connection packet receiving rule is that the destination MAC address of the data packet is the same as the MAC address of the interface, the data packet type is a connection packet, and the Payload part length of the data packet can only be 64, 288 or 1056 bytes.

During initialization, the sending flag bits of all the table entries in the Ethernet sending matching table No. 0 and No. 1 are initialized to 0, that is, no data packet can be sent.

After the initialization, the terminal sub-control server B21, the terminal sub-control server B22, and the terminal sub-control server B23 are in a state of waiting for receiving the device connection command on port No. 1.

S13, terminal T21, terminal T22, terminal T23, terminal T24, terminal T25 and terminal T26 are electrified and initialized

The terminal T21, the terminal T22, the terminal T23, the terminal T24, the terminal T25, and the terminal T26 obtain the respective logical device type, the logical device identifier, and the MAC address of the interface at the initialization stage.

After the initialization, the terminal T21, the terminal T22, the terminal T23, the terminal T24, the terminal T25, and the terminal T26 are in a state of waiting for receiving a device connection command.

And S2, accessing the network by the terminal sub-control server B21.

S21, the master control server a2 checks all registered devices in the master cloudset but not accessing the network, and finds that the terminal sub-control server B21 is the central device, so it may send a device connection command to the terminal sub-control server B21, and finds that the terminal sub-control server B22 and the terminal sub-control server B23 are not the central device and the central device does not access the network at this time, so it does not send a device connection command to the terminal sub-control server B22 and the terminal sub-control server B23.

When the master control server a2 sends a device connection command to the terminal sub-control server B21, the packet type is a connection packet, the destination MAC address is the port 1 MAC address of the terminal sub-control server B21, the source MAC address is its own MAC address, the destination autonomous network address is the connection address 0x21210x 21210x 21210x2121 (the port 1 logical port address of B21 is 0x21), and the source autonomous network address is the connection address 0xffff 0xffff 0xffff 0xffff (the logical port address of the administrator is fixed to 0 xff).

The Payload part of the device connection command includes, in addition to the logical device types and identifiers of both parties, a micro cloud level equal to 4, a node type equal to a terminal slave control server, a MAC address used when sending a connection packet to the master control server as the MAC address of the master control server, a session identifier equal to 1, and the like.

In addition, the master server a2 needs to record related information (network access status, session identifier, etc.) in the 70021 th entry of the device dynamic information table.

S22, the terminal sub-control server B21 receives the device connection command on the port No. 1, finds that the destination MAC address, the packet type and the length of the data packet all accord with the connection packet receiving rule, and directly sends the data packet to the protocol processing module for processing.

And the protocol processing module judges that the data packet belongs to the protocol processing module according to the type and the identification of the logic equipment, and records information (a micro cloud level, an MAC (media access control) address of a master control server, a session identification and the like) in the command, wherein the micro cloud level needs to be reduced by 1 to be 3.

The protocol processing module configures the 0xff table entry of the Ethernet transmission matching table No. 1, sets the transmission flag bit to be 1, and sets the MAC address to be the MAC address of the master server (00:00:00:02: fb: 00).

The protocol processing module sends a device connection response to the port 1, the packet type is a connection packet, the destination autonomous network address is a connection address 0 xfffff, the source autonomous network address is a connection address 0x 21210 x 21210 x2121, the destination MAC address is obtained by searching the Ethernet transmission matching table of the port 1, and meanwhile, the transmission flag bit is 1 (indicating that transmission is allowed) and the source MAC address is the MAC address of the port 1.

S23, the main control server a2 receives the device connection response, obtains the logical port address 0x21 according to the home network address, deduces that the local logical address is 0x2100, and obtains the corresponding local device number 70021 after searching the address number mapping table.

At 70021, the item in the dynamic information table is looked up, and the session ID is used to judge whether the response belongs to the current connection session.

And sending a device authentication command to the terminal sub-control server B21, wherein the Payload part of the command comprises the type of the authentication algorithm, the random number and the session identification.

S24, the terminal sub-control server B21 receives the equipment authentication command on the No. 1 port, judges whether the command belongs to the current connection session according to the session identification, then calculates the authentication calculation result, and sends the equipment authentication response to the main control server A2.

S25, the master control server A2 judges whether the authentication calculation result is correct after receiving the device authentication response. And if the answer is correct, sending a device networking command to the terminal sub-control server B21.

S26, after receiving the device network access command, the terminal sub-control server B21 judges whether the command belongs to the current connection session according to the session identifier, and then records relevant information including the local device number (90002) of the main control server, the local logical address (0xfb00) of the main control server, the local device number (70021) of the terminal sub-control server, the local logical address (0x21fb) of the number 0 port of the terminal sub-control server, the MAC address used when sending a unicast packet to the main control server (namely the MAC address of the main control server), the number prefix of the autonomous cloud device, the logical address prefix of the autonomous cloud, the topology type (star) of the sub-control micro-cloud, and the logical port address (0x00 means that no upper forwarding node exists).

According to the above information, the protocol processing module can calculate that its global device number is 60031-.

The 0 st 0xfb table entry of the ethernet transmission matching table No. 1 is configured according to the logical port address of the master server a2, the transmission flag bit is set to 1, and the MAC address is the MAC address of the master server a2 (00:00:00:02: fb: 00).

And adding a filtering rule for receiving the unicast packet and the multicast packet, wherein the unicast packet receiving rule is that the destination MAC address and the interface MAC address are the same, the packet type is a unicast packet and the length is 64 bytes, 288 bytes or 1056 bytes, and the multicast packet receiving rule is that the destination MAC address and the interface MAC address are the same, the packet type is a multicast packet and the length is 288 bytes or 1056 bytes.

Finally, the device network access response is sent to the master server a2 while setting itself in the network-accessed state.

And S3, accessing the network by the terminal sub-control server B22 and the terminal sub-control server B23.

After receiving the device network access response sent by the terminal sub-control server B21, the main control server a2 sets the device in the network access state in the device dynamic information table.

Then, when all the registered but non-networked devices in the master clouding are checked, it is found that the terminal sub-control server B22 and the terminal sub-control server B23 are not the center device and the center device is networked at this time, so a device connection command can be sent thereto.

The subsequent network access process is substantially the same as the network access process between the terminal sub-control server B21, and the biggest difference is that the parameter "MAC address used when sending unicast packet to the main control server" in the device network access command is no longer the MAC address of the main control server, but is the MAC address of port 1 of the terminal sub-control server (central device) B21.

Accordingly, the MAC addresses in the 0 th 0xfb entry of the ethernet transmission matching table No. 1 of the terminal sub-control server B22 and the terminal sub-control server B23 also become the port 1 MAC address of the terminal sub-control server (center device) B21.

S4, the terminal branch control server B21 heartbeats.

And S41, the master control server A2 sends a device heartbeat command to the terminal sub-control server B21 at regular time after the terminal sub-control server B21 accesses the network.

The packet type of the device heartbeat command is a unicast packet, the destination MAC address is port 1 MAC address of the terminal sub-control server B21, the source MAC address is its own MAC address, the destination autonomous network address is unicast address 0x 42310 x 32210 x21fb 0x0000 (port 0 global logical address in the terminal sub-control server B21), and the home autonomous network address is unicast address 0x 42310 x 32210 xfb 000 x0000 (global logical address in the main control server a 2).

S42, the terminal sub-control server B21 receives the device heartbeat order on the port No. 1, and if the destination MAC address, the packet type and the length of the data packet are found to accord with the unicast packet receiving rule, the step of calculating the next receiver is carried out.

Since the destination autonomous network address of the data packet is identical to the port 0 global logic address of the terminal sub-control server B21, the next receiver is an internal protocol processing module.

The protocol processing module compares whether the autonomous network address of the data packet is the same as the recorded global logical address of the master server a2, and if so, sends a device heartbeat response to the master server a 2.

The packet type of the device heartbeat response is a unicast packet, the destination autonomous network address is a unicast address 0x 42310 x 32210 xfb 000 x0000 (global logical address of the master control server a 2), and the source autonomous network address is a unicast address 0x 42310 x 32210 x21fb 0x0000 (port 0 global logical address of the terminal slave control server B21).

Then, the step of calculating the next receiver of the unicast packet is entered. The micro cloud level is 3, so that the 3-part addresses of the destination autonomous network address are 42313221, fb and 00, respectively, and the 3-part addresses of the port 0 global logical address are 42313221, 21 and fb, respectively.

According to the situation that the calculation rule corresponds to the situation that the address 2 part is the same but the address 1 part is different, the next receiver is located in the micro cloud to which the port 1 belongs, and the corresponding logical port address is the address 1 part of the destination autonomous network address, so that the unicast packet needs to be sent to the device with the logical port address of 0xfb in the main control micro cloud of the port 1. Its destination MAC address is obtained by looking up ethernet send match table No. 1 entry 0xfb, which is obviously the MAC address of the master server. The source MAC address is set to the MAC address of port No. 1.

The device heartbeat response further includes network access states of the terminal T21 and the terminal T22 in the sub-control cloudset managed by the terminal sub-control server B21, and the current state is that neither the terminal T21 nor the terminal T22 is connected to the network.

And S43, after receiving the device heartbeat response sent by the terminal sub-control server B21, the main control server updates the information of the corresponding device in the device dynamic information table according to the terminal network access state in the response.

S5, the terminal sub-control server B21 exchanges node information configuration.

After the terminal sub-control server B21 accesses the network, the main control server a2 configures the ethernet transmission matching table No. 1 of the terminal sub-control server B21 by transmitting the switching node information configuration command.

When other devices in the master control micro cloud enter or leave the network, the master control server a2 sends an exchange node information configuration command to the terminal sub-control server B21.

For example, the terminal sub-control server B21 does not need to send the switch node information configuration command when it is just connected to the network.

If the terminal sub-control server B22 is also accessed to network, the switching node information configuration command needs to be sent.

After receiving the switching node information configuration command, the terminal sub-control server B21 performs the following configuration according to the parameters therein: the transmission flag bit of the 0x22 th table entry (port 1 logical port address corresponding to B22) of the Ethernet transmission matching table No. 1 is set to 1, and the MAC address is set to 00:00:00:02:22: fc (port 1 MAC address of B22).

Similarly, after the sub-terminal control server B23 accesses the network, the 0x23 entry of the 1 st transmission matching table of the sub-terminal control server B21 is configured as the 1 st port MAC address of the sub-terminal control server B23.

And S6, the terminal sub-control server B22 and the terminal sub-control server B23 heartbeat.

S61, after the terminal sub-control servers B22 and B23 access the network, the main control server a2 also sends the device heartbeat command to the terminal sub-control server B22 and the terminal sub-control server B23 at regular time.

Since the terminal sub-control server B22 and the terminal sub-control server B23 are not central devices, and the unicast packet needs to be forwarded through the terminal sub-control server B21, the destination MAC address of the device heartbeat command sent to the terminal sub-control server B22 and the terminal sub-control server B23 is the MAC address of port 1 of the terminal sub-control server B21, and the destination autonomous network addresses are the global logical addresses of port 0 of the terminal sub-control server B22 and the terminal sub-control server B23, respectively.

S62, the terminal sub-control server B21 receives the device heartbeat command sent to the terminal sub-control server B22 and the terminal sub-control server B23, and then calculates the next receiver of the unicast packet.

For example, in the device heartbeat command issued to the terminal slave control server B22, the destination autonomous network address is 0x 42310 x 32210 x22fb 0x0000 (port 0 global logical address of the terminal slave control server B22), and the port 0 global logical address of the terminal slave control server B21 is 0x 42310 x 32210 x21fb 0x 0000.

The micro cloud level is 3, so that 3 part addresses of the destination autonomous network address are 42313221, 22 and fb respectively, and 3 part addresses of the port 0 global logical address are 42313221, 21 and fb respectively.

And obtaining the equipment with the logical port address of 0x22 in the master control micro cloud of which the unicast packet needs to be sent to the port 1 according to the calculation rule, and forwarding the heartbeat command to the terminal branch control server B22 through the port 1 sent to the terminal branch control server B21 after table lookup.

S63, the processing flow of the terminal sub-control server B22 and the terminal sub-control server B23 after receiving the device heartbeat command is basically the same as that of the terminal sub-control server B21, and the difference is that when the device heartbeat response is sent to the main control server, the destination MAC address obtained by searching and sending the matching table through the destination autonomous network address is the No. 1 port MAC address of the terminal sub-control server B21.

These device heartbeat responses will be received by the terminal sub-control server B21 and then forwarded to the main control server a2 according to the forwarding rule of the unicast packet.

S7, the terminal sub-control server B22 and the terminal sub-control server B23 exchange node information configuration.

S71, the master server a2 configures the ethernet transmission matching table No. 1 by sending the switch node information configuration command after the terminal sub-control server B22 and the terminal sub-control server B23 access the network.

Whenever other devices in the master cloudlet enter or leave the network, the master server a2 sends an exchange node information configuration command to them.

For example, the terminal sub-control server B22 accesses the network first, and the terminal sub-control server B23 accesses the network later.

After the terminal sub-control server B22 accesses the network, the master control server a2 sends the MAC address information related to the terminal sub-control server B21 to the terminal sub-control server B22.

After the terminal sub-control server B23 accesses the network, the main control server a2 sends the MAC address information related to the terminal sub-control server B21 and the terminal sub-control server B22 to the terminal sub-control server B23, and also sends the MAC address information related to the terminal sub-control server B23 to the terminal sub-control server B22.

So far, after the terminal sub-control server B21, the terminal sub-control server B22 and the terminal sub-control server B23 all access the network, the table entries with the sending flag bit set to 1 in the No. 1 sending matching table are as follows:

s72, if the topology of the master cloudlet is full-exchange, any two devices in the cloudlet can directly communicate without being forwarded by the central device.

The MAC address stored in the No. 1 transmission matching table of the terminal sub-control server a2 is the MAC address of the device corresponding to the logical port address. The specific table items are as follows:

s8, terminal sub-control server B21, terminal sub-control server B22 and terminal sub-control server B23 configure registration information of terminal T21, terminal T22, terminal T23, terminal T24, terminal T25 and terminal T26

S81, after the terminal sub-control server B21, the terminal sub-control server B22, and the terminal sub-control server B23 access the network, the main control server a2 sends a device lower layer device information configuration command to the terminal sub-control server B21, the terminal sub-control server B22, and the terminal sub-control server B23, where the device lower layer device information configuration command includes device registration information of the terminal T21, the terminal T22, the terminal T23, the terminal T24, the terminal T25, and the terminal T26.

For example, after the terminal slave control server B21 accesses the network, the lower layer device information configuration command transmitted includes the registration information of the terminal T21 and the terminal T22.

After receiving the lower-layer device information configuration command, the terminal sub-control server B21 records the registration information of the terminal T21 and the terminal T22 in the corresponding entry in the device static information table and marks the entry as valid.

S82, the terminal sub-control server B21 sends a matching table according to the logical port address and the MAC address configuration No. 0 in the lower-layer equipment information configuration command.

For example, if the logical port address of the terminal T21 is 0x21 and the MAC address is 00:00:00:02:21:21, the sending flag bit in the 0x21 entry in the sending matching table No. 0 is set to 1, the MAC address is set to the MAC address of the terminal T21, and similarly, the matching entry of the terminal T22 is set.

After the configuration is completed, the terminal sub-control server B21 sends a lower layer device information configuration response to the master control server a 2.

S9, terminal T21, terminal T22, terminal T23, terminal T24, terminal T25 and terminal T26.

Taking the terminal T26 as an example:

and S91, the terminal sub-control server B21, the terminal sub-control server B22 and the terminal sub-control server B23 check all registered terminals which do not enter the network in the sub-control micro-cloud, and send a device connection command to the terminals.

The terminal sub-control server B23 finds that the valid bit of the 0x26 entry in the device static information table is 1, and the network access state of the 0x26 entry in the device dynamic information table is not network access, then sends a device connection command to the terminal T26.

The packet type of the device connection command is a connection packet, the destination MAC address is a MAC address of a terminal T26, the source MAC address is a port 0 MAC address of B23, the destination autonomous network address is a connection address 0x 26260 x 26260 x 26260 x2626 (a logical port address of a terminal T26 is 0x26), and the source autonomous network address is a connection address 0xffff 0xffff 0xffff 0xffff (a logical port address of a manager is fixed to 0 xff).

The Payload part of the device connection command includes, in addition to the logical device types and identifiers of both parties, a micro cloud level equal to 3, a node type equal to a terminal, a MAC address used when sending a connection packet to the terminal slave control server, which is a port 0 MAC address of the terminal slave control server B23, a session identifier equal to 2, and the like.

The sub-control server B23 also needs to record the related information (network access status, session identification, etc.) in the 0x26 entry of the device dynamic information table.

S92, the terminal T26 receives the device connection command, judges the data packet belongs to itself according to the type and the identification of the logic device, and records the information (micro cloud level, port 0 MAC address of the terminal sub-control server B23, session identification and the like) in the command.

And then sending an equipment connection response to the terminal sub-control server B23, wherein the packet type is a connection packet, the destination autonomous network address is a connection address 0 xfffff, the source autonomous network address is a connection address 0x 26260 x 26260 x 26260 x2626, the destination MAC address is a port 0 MAC address of the terminal sub-control server B23, and the source MAC address is a MAC address of the terminal T26.

S93, the terminal sub-control server B23 receives the device connection response, obtains the logical port address 0x26 according to the autonomous network address, searches the device dynamic information table according to 0x26, and judges whether the response belongs to the current connection session according to the session identifier. A device authentication command is then sent to terminal T26, the Payload part of which includes the type of authentication algorithm and the random number, as well as the session identification.

S94, the terminal T26 receives the equipment authentication command, judges whether the command belongs to the current connection session according to the session identification, then calculates the authentication calculation result, and then sends an equipment authentication response to the terminal sub-control server B23.

And S95, after the terminal sub-control server B23 receives the equipment authentication response, judging whether the authentication calculation result is correct. If it is correct, a device network-entry command is sent to the terminal T26.

S96, after receiving the device network access command, the terminal T26 determines whether the command belongs to the current connection session according to the session identifier, and records relevant information, including a local device number (70023) of the terminal sub-control server B23, a local logical address (0x23fb) of the terminal sub-control server B23, a local device number (00026) of the terminal, a local logical address (0x2326) of the terminal, a local device number (90002) of the master control server a2, a local logical address (0xfb00) of the master control server a2, a MAC address (No. 0 MAC address of the terminal sub-control server B23) used when sending a unicast packet to the terminal sub-control server, a prefix of an autonomous cloud device number, and a prefix of an autonomous cloud logical address.

According to the information, the terminal T26 can calculate that its global device number is 60031-.

And then sends a device network access response to the terminal sub-control server B23, and sets itself to be in a network access state.

And S97, after receiving the device network access response sent by the terminal T26, the terminal sub-control server B23 sets the device in the network access state in the device dynamic information table.

S98, after the terminal T26 accesses the network, the terminal sub-control server B23 sends the terminal access state in the device heartbeat response to the main control server a2 to indicate that the access state of the terminal with the current logical port address of 0x26 is changed to the already-accessed state.

After receiving the heartbeat response, the main control server a2 determines that the local logical address of the terminal is 0x2326 according to the port 1 logical port address 0x23 of the terminal sub-control server B23 and the logical port address 0x26 of the terminal T26, searches the address number mapping table to obtain the number of the local device as 00026, and sets the network access state as accessed in the device dynamic information table.

S10, terminal T21, terminal T22, terminal T23, terminal T24, terminal T25, and terminal T26 heartbeat.

Taking the heartbeat of the terminal T26 as an example, the terminal sub-control server B23 sends a device heartbeat command to the terminal T26 at a fixed time after the terminal T26 accesses the network.

The packet type of the device heartbeat command is a unicast packet, the destination autonomous network address is a unicast address 0x 42310 x 32210 x 23260 x0000 (global logical address of the terminal T26), and the source autonomous network address is a unicast address 0x 42310 x 32210 x23fb 0x0000 (port 0 global logical address of the terminal sub-control server B23).

Similarly, when the device heartbeat command is sent, the destination MAC address needs to be calculated by the destination autonomous network address, and the calculation result is that the device with the logical port address of 0x26 needs to be sent to the port No. 0. And searching a 0x26 table entry of the 0-number transmission matching table to obtain a destination MAC address of 00:00:00:02:23:26 (namely the MAC address of the terminal T26), and setting the source MAC address as the own 0-number port MAC address for transmission.

After receiving the device heartbeat command, the terminal T26 sends a device heartbeat response to the terminal sub-control server B23.

And S11, the equipment quits the network.

Taking the exit of the terminal T26 as an example:

and if the terminal sub-control server B23 does not receive the equipment heartbeat response of the terminal T26 within 6 seconds, judging that the terminal is quitted, and updating the network access state in the equipment dynamic information table to be non-network access.

In the device heartbeat response sent to the master control server a2, the terminal sub-control server B23 sets the network access state corresponding to the terminal T26 as non-network access.

And after receiving the heartbeat response, the master control server A2 updates the network access state of the terminal T26 in the device dynamic information table to be non-network access state.

After the terminal T26 quits from the network, the terminal sub-control server B23 sets the sending flag bit of the 0 th x26 entry in the sending matching table No. 0 to 0, which indicates that the corresponding data packet is not sent.

Taking the logout of the terminal sub-control server B23 as an example:

if the master control server A2 does not receive the device heartbeat response of the terminal sub-control server B23 within 6 seconds, the network quitting is judged, and the network access state in the device dynamic information table is updated to be non-network access. Meanwhile, the network access states of all the terminals T25 and T26 managed by the terminal sub-control server B23 in the device dynamic information table are also set to be non-network access.

In addition, after the sub-control server B23 quits the network, the main control server a2 needs to send an exchange node information configuration command to the sub-control server B21 and the sub-control server B22 to notify them that the sub-control server B23 has quit the network.

After receiving the switching node information configuration command, the sub-control server B21 and the sub-control server B22 set the sending flag bit of the 0x23 table entry of the No. 1 sending matching table to 0 according to the parameters in the command, which indicates that the corresponding data packet is not sent.

When the main control micro cloud topology is a star topology, if the terminal sub-control server B21 quits the network, since the sub-control server B21 is a central device, the sub-control server B22 and the sub-control server B23 also automatically quit the network, that is, at this time, the network access states of the terminal sub-control server B21, the terminal sub-control server B22, the terminal sub-control server B23, the terminal T21, the terminal T22, the terminal T23, the terminal T24, the terminal T25 and the terminal T26 all become non-network access states.

Example two, Multi-autonomous cloud Access network

As shown in fig. 26, it is assumed that the autonomous cloud C2 is located at the layer 2 of the autonomous network, the autonomous cloud C3 is located at the layer 3 of the autonomous network, and the autonomous cloud C2 and the autonomous cloud C3 multiplexing boundary router M21 are connected, and for simplicity of description, the terminal is omitted.

In the autonomous cloud C2, a master control server a2, a terminal sub-control server B21, a boundary sub-control server B22, and a boundary router M21 are connected in the same switching network.

In the autonomous cloud C3, a master control server A3, a terminal sub-control server B31, a boundary sub-control server B32, and a boundary router M31 are connected to the same switching network, and a boundary sub-control server B32, a boundary router M21, and a boundary router M22 are connected to another switching network.

First, device initialization

S1, initializing after the master control server A2 is powered on, and obtaining the system parameters of the autonomous cloud as follows: the device number prefix is 60031-. According to the information, the local logic address of the master control server is 0xfb00, the global device number is 60031-.

The registration information of the device is obtained as follows:

the number of the logical port address and the MAC address of the boundary sub-control server is 2, the first represents the information of the port 0 (downlink interface), and the second represents the information of the port 1 (uplink interface). The logical port address and the MAC address of the border router 80021 correspond to information of port No. 0 (downstream interface).

The central device number of the terminal sub-control server B21 is 0, which indicates that it is a central device in the main control micro cloud with the topology type of star, so the central device number of the boundary sub-control server B22 is 70021 (B21).

For the boundary router M21 accessing the master cloudlet through the downlink interface, the central device number is always 0 regardless of the topology type of the master cloudlet.

Note that the micro-cloud topology field of the border sub-control server represents the topology of the sub-control micro-cloud rather than the topology of the master micro-cloud.

The master control server a2 initializes the device static information table according to the registration information, and calculates the local logical address, the global device number, and the global logical address of each device as follows:

similarly, the number of the local logical addresses and the global logical addresses of the border sub-control server is also 2, and the local logical addresses and the global logical addresses correspond to the port 0 and the port 1 respectively.

The master server a2 initializes the device dynamic state table and the address number mapping table according to the above information.

S2, initializing after the master control server A3 is powered on, and obtaining the system parameters of the autonomous cloud as follows: the device number prefix is 60031-00000, the logical address prefix is 4231-0000, the master control micro cloud layer is 6, the master control micro cloud topology is star, the local device number of the master control server is 90003, the logical port address of the master control server is fb, and the MAC address of the master control server is 00:00:00:03: fb: 00. According to the information, the local logic address of the master server is 0xfb00, the global device number is 60031-fb 90003-00000 and the global logic address is 4231-fb 00-0000.

The registration information of the device is obtained as follows:

the logical port address and the MAC address of the border router M31 correspond to port No. 0 (downlink interface), and the logical port address and the MAC address of the border router M21 and the border router M22 correspond to port No. 1 (uplink interface).

The central device number of the terminal sub-control server B31 is 0, which indicates that it is the central device in the main control micro cloud with the topology type of star, so the central device number of the boundary sub-control server B32 is 70031 (B31).

For the boundary router M31 accessing the master cloudlet through the downlink interface, the central device number is always 0 regardless of the topology type of the master cloudlet.

For the boundary router M21 and the boundary router M22 that access the sub-control cloudland through the uplink interface, when the topology type of the sub-control cloudlet is star, the central device number thereof is necessarily the number of the boundary sub-control server, and when the topology type of the sub-control cloudlet is full switching, the central device number thereof is always 0.

The master control server a3 initializes the device static information table according to the registration information, and calculates the local logical address, the global device number, and the global logical address of each device as follows:

the master server a3 initializes the device dynamic state table and address number mapping table based on the above information.

And S3, the terminal sub-control server, the boundary sub-control server and the boundary router are initialized after being electrified, and the respective logic device type, the logic device identification and the MAC addresses of 2 interfaces are obtained.

When the border sub-control server and the border router are initialized, the receiving and filtering rules of the data packets also need to be set, and the data packets which do not accord with all the rules can be discarded. And only the connection packet can be received under the condition of no network access. The receiving rule of the connection packet is the same as the rule of the terminal sub-control server.

The sending flag bits of all table entries in the Ethernet sending matching table No. 0 and No. 1 of the boundary sub-control server and the boundary router are initialized to 0, that is, no data packet can be sent.

After initialization, the border sub-control server is in a state of waiting for receiving the equipment connection command on the port No. 1, and the border router is in a state of waiting for receiving the equipment connection command on the port No. 0.

Second, boundary router M21 downstream interface network access

S4, the master server a2 checks all registered devices in the master cloudlet that are not networked, finds that the border router M21 is not networked yet, and can send a device connection command to the border router M21 regardless of the topology type of the master cloudlet because the device type is a border router.

When a device connection command is sent to the boundary router M21, the packet type is a connection packet, the destination MAC address is the port 0 MAC address of M21, the source MAC address is its own MAC address, the destination autonomous network address is the connection address 0xf1f 10 xf1f 10 xf1f1 (the port 0 logical port address of M21 is 0xf1), and the autonomous network address is the connection address 0 xfffff (the logical port address of the administrator is fixed to 0 xff).

The Payload part of the device connection command includes, in addition to the logical device types and identifiers of both parties, a cloudlet level equal to 4, a node type equal to a border router, an MAC address used when sending a connection packet to the master server as an MAC address of the master server, a session identifier equal to 1, and the like. The master server also needs to record related information (network access state, session identification, etc.) in the 80021 th entry of the device dynamic information table.

S5, boundary router M21 receives the device connection command on port 0, finds that the destination MAC address, packet type and length of the data packet all accord with the connection packet receiving rule, and directly delivers the connection packet to the protocol processing module for processing.

And the protocol processing module judges that the data packet belongs to the protocol processing module according to the type and the identification of the logic equipment and records information (micro cloud level, MAC address of the master control server, session identification and the like) in the command. Where the micro-cloud hierarchy does not need to be decremented by 1 or recorded as 4.

The protocol processing module configures the 0xff table entry of the Ethernet transmission matching table 0, sets the transmission flag bit to be 1, and sets the MAC address to be the MAC address of the master server (00:00:00:02: fb: 00).

The protocol processing module sends a device connection response to the port 0, the packet type is a connection packet, the destination autonomous network address is a connection address 0 xfffff, the source autonomous network address is a connection address 0xf1f 10 xf1f 10 xf1f 10 xf1f1, the destination MAC address is obtained by searching the Ethernet transmission matching table of the port 0, and meanwhile, the transmission flag bit is 1 (indicating that transmission is allowed) and the source MAC address is the MAC address of the port 0.

S6, the master control server A2 receives the device connection response, obtains the logical port address 0xf1 according to the source control network address, deduces that the local logical address is 0xf100, and obtains the corresponding local device number 80021 after searching the address number mapping table. Then, a device dynamic information table is searched according to 80021, and whether the response belongs to the current connection session is judged according to the session identification. A device authentication command is then sent to the border router M21, including the type of authentication algorithm and the random number, as well as the session identification, in the Payload section of the command.

S7, the boundary router M21 receives the device authentication command on the port 0, judges whether the command belongs to the current connection session according to the session identification, and then calculates the authentication calculation result. A device authentication response is then sent to master server a 2.

And S8, after receiving the device authentication response, the master control server A2 judges whether the authentication calculation result is correct. If it is correct, a device network entry command is sent to the border router M21.

S9, after receiving the device network access command, the border router M21 determines whether the command belongs to the current connection session according to the session identifier, and then records related information, including a local device number (90002) of the master control server, a local logical address (0xfb00) of the master control server, a local device number (80021) of the border router, a local logical address (0xf100) of the border router at port 0 of the border router, a MAC address used when sending a unicast packet to the master control server (i.e., a MAC address of the master control server), a prefix of the autonomous cloud device number, and a prefix of the autonomous cloud logical address.

Then, the 0 th 0xfb table item of the 0 th Ethernet transmission matching table is configured according to the logical port address of the main control server, the transmission flag bit is set to be 1, and the MAC address is the MAC address of the main control server (00:00:00:02: fb: 00). And adding a filtering rule for receiving the unicast packet and the multicast packet, wherein the unicast packet receiving rule is that the destination MAC address is the same as the interface MAC address, the packet type is a unicast packet and the length is 64 bytes, 288 bytes or 1056 bytes, and the multicast packet receiving rule is that the destination MAC address is the same as the interface MAC address, the packet type is a multicast packet and the length is 288 bytes or 1056 bytes.

And finally, sending a device network access response to the master control server A2 and setting the number 0 port of the master control server A to be in the network access state.

Third, boundary router M21 downstream interface heartbeat

S10, after M21 accesses the network, the master control server A2 sends a device heartbeat command to the M21 at regular time. The packet type is a unicast packet, the destination MAC address is port 0 MAC address of M21, the source MAC address is its own MAC address, the destination autonomous network address is unicast address 0x 42310 x 32210 xf 1000 x0000 (port 0 global logical address of M21), and the source autonomous network address is unicast address 0x 42310 x 32210 xfb 000 x0000 (global logical address of the master server).

S11, the boundary router M21 receives the device heartbeat order on the port 0, and the step of calculating the next receiver is entered when the destination MAC address, the packet type and the length of the data packet are all in accordance with the unicast packet receiving rule. Since the destination autonomous network address of the packet is identical to the port 0 global logical address of M21, the next receiver is an internal protocol processing module.

And the protocol processing module compares whether the self-control network address of the data packet is the same as the recorded global logic address of the master control server, and sends a device heartbeat response to the master control server if the self-control network address of the data packet is the same as the recorded global logic address of the master control server. The packet type is a unicast packet, the destination autonomous network address is a unicast address 0x 42310 x 32210 xfb 000 x0000 (global logical address of the master server), and the source autonomous network address is a unicast address 0x 42310 x 32210 xf 1000 x0000 (port 0 global logical address of M21).

And then proceed to the step of computing the next recipient of the unicast packet. The cloudlet level is 4, so the 3 part addresses of the destination autonomous network addresses are 423132, 21, and fb, respectively, and the 3 part addresses of port 0 global logical addresses are 423132, 21, and f1, respectively. According to the calculation rule, the situation that only address 0 part is different, which means that the next receiver is located in the micro cloud to which the port 0 belongs, and the corresponding logical port address is the address 0 part of the destination autonomous network address is corresponding, so that the unicast packet needs to be sent to the device with the logical port address of 0xfb in the master control micro cloud of the port 0. Its destination MAC address is obtained by looking up ethernet No. 0 sending the 0 th 0xfb entry of the matching table, which is obviously the MAC address of the master server. The source MAC address is set to the MAC address of port No. 0.

The device heartbeat response also includes the network access state of port 1 of the boundary router M21, that is, the network access state between the boundary branch control server B32 in the autonomous cloud C3.

S12, after receiving the device heartbeat response sent by the border router M21, the master control server a2 updates the corresponding information in the 0xf100 (local logical address of M21) table entry in the autonomous cloud access table according to the No. 1 network access status in the response.

Four, boundary router M21 downlink interface exchange node information configuration

S13, after the border router M21 accesses the network, the master server a2 needs to send an exchange node information configuration command to the border router M21 and other devices in the master cloudset that have accessed the network. The command sent to the border router M21 is used to configure its send match table No. 0, while the commands sent to other devices are used to configure their send match table No. 1.

Assuming that the terminal sub-control server B21, the boundary sub-control server B22 and the boundary router M21 are all already in network, the effective entries in their transmission matching tables are as follows:

s14, after the border router M21 enters the network through port 0, it waits for a device connect command from the border slave server B32 on port 1.

S15, border router M31 in autonomous cloud C3, enter the network in a similar manner.

Fifthly, the boundary sub-control server B32 accesses the network

S16, the master server A3 checks all registered devices in the master cloudlet that are not networked, and if the terminal sub-control server B31 is networked, finds that the boundary sub-control server B32 is not a central device but the central device (the terminal sub-control server B31) is networked, so it may send a device connection command to the boundary sub-control server B32.

When a device connection command is sent to the boundary sub-control server B32, the packet type is a connection packet, the destination MAC address is the port 1 MAC address of the boundary sub-control server B32, the source MAC address is its own MAC address, the destination autonomous network address is the connection address 0x 32320 x 32320 x3232 (the port 1 logical port address of B32 is 0x32), and the source autonomous network address is the connection address 0 xfffff (the logical port address of the administrator is fixed to 0 xff).

The Payload part of the device connection command includes, in addition to the logical device types and identifiers of both sides, a micro cloud level equal to 6, a node type equal to a border slave control server, a MAC address used when sending a connection packet to the master control server as the MAC address of the master control server, a session identifier 2, and the like. The master server also needs to record the relevant information (network entry status, session identification, etc.) in 70032 th entry of the device dynamic information table.

S17, boundary sub-control server B32 receives the device connection command on port No. 1, finds that the destination MAC address, packet type and length of the data packet all accord with the connection packet receiving rule, and directly sends the data packet to the protocol processing module for processing. And the protocol processing module judges that the data packet belongs to the protocol processing module according to the type and the identification of the logic equipment and records information (a micro cloud layer, an MAC address of a master control server, a session identification and the like) in the command. Where the cloudiness is less than 1 to 5.

The protocol processing module configures the 0xff table entry of the Ethernet transmission matching table No. 1, sets the transmission flag bit to be 1, and the MAC address is the MAC address of the main control server (00:00:00:03: fb: 00).

The protocol processing module sends a device connection response to the port 1, the packet type is a connection packet, the destination autonomous network address is a connection address 0 xfffff, the source autonomous network address is a connection address 0x 32320 x 32320 x3232, the destination MAC address is obtained by searching the Ethernet transmission matching table of the port 1, and meanwhile, the transmission flag bit is 1 (indicating that transmission is allowed) and the source MAC address is the MAC address of the port 1.

S18, the main control server A3 receives the device connection response, obtains the logical port address 0x32 according to the home network address, deduces that the local logical address is 0x3200, and obtains the corresponding local device number 70032 after searching the address number mapping table. Then according to 70032, the dynamic information table of the device is searched, and according to the session identification, whether the response belongs to the current connection session is judged.

Then sends a device authentication command to the border sub-control server B32, the Payload part of the command including the type of authentication algorithm and the random number, as well as the session identification.

S19, the boundary sub-control server B32 receives the equipment authentication command on the port No. 1, judges whether the command belongs to the current connection session according to the session identification, and then calculates the authentication calculation result. A device authentication response is then sent to the master server.

And S20, after receiving the device authentication response, the master control server A3 judges whether the authentication calculation result is correct. If the data is correct, a device network-accessing command is sent to the boundary sub-control server B32.

S21, after receiving the device network access command, the boundary sub-control server B32 determines whether the command belongs to the current connection session according to the session identifier, and then records related information, including a local device number (90003) of the main control server, a local logical address (0xfb00) of the main control server, a local device number (70032) of itself, a local logical address (0x32fb) of its 0 port, a MAC address (No. 1 MAC address of the central device B31) used when sending a unicast packet to the main control server, an autonomous cloud device number prefix, an autonomous cloud logical address prefix, a topology type (star) of the sub-control cloudlet, and a logical port address (0xf1 corresponds to the logical port address of the 0 port of the boundary router M31) of the upper layer forwarding node.

According to the information, the protocol processing module can calculate that the global device number of the protocol processing module is 60031-70032-00000, the global logic address of the port 0 is 4231-32fb-0000, the logic port address of the master server is 0xfb, the global device number of the master server is 60031-90003-00000, and the global logic address of the master server is 4231-fb 00-0000.

Then, the 0 th 0xfb table item of the Ethernet transmission matching table No. 1 is configured according to the logical port address of the master control server, the transmission flag bit is set to be 1, and the MAC address is the MAC address No. 1 (00:00:00:03:31: fc) of the central equipment (terminal sub-control server B31). And adding a filtering rule for receiving the unicast packet and the multicast packet, wherein the unicast packet receiving rule is that the destination MAC address and the interface MAC address are the same, the packet type is a unicast packet and the length is 64 bytes, 288 bytes or 1056 bytes, and the multicast packet receiving rule is that the destination MAC address and the interface MAC address are the same, the packet type is a multicast packet and the length is 288 bytes or 1056 bytes.

And finally, sending a device network access response to the master server a3 and setting the device in the network access state.

Sixthly, boundary sub-control server B32 heartbeat

And S22, the main control server A3 sends a device heartbeat command to the boundary sub-control server B32 at regular time after the boundary sub-control server B32 accesses the network. Since the border sub-control server B32 is not a central device, the unicast packet needs to be forwarded through the terminal sub-control server B31. Therefore, the destination MAC address of the device heartbeat command issued to the border sub-control server B32 is port 1 MAC address of the terminal sub-control server B31, and the destination autonomous network address is port 0 global logical address of the border sub-control server B32.

S23, the terminal slave controller B31 receives the device heartbeat command sent to the border slave controller B32, and then calculates the next receiver of the unicast packet.

Since the destination autonomous network address is 0x 42310 x32fb 0x 00000 x0000 (port 0 global logical address of B32), and the port 0 global logical address of the terminal slave server B31 is 0x 42310 x31fb 0x 00000 x0000, the micro cloud level is 5. So the 3 part addresses of the destination autonomous network address are 4231, 32 and fb respectively, and the 3 part addresses of port 0 global logical address are 4231, 31 and fb respectively. And obtaining the equipment with the logical port address of 0x32 in the master control micro cloud of the number 1 port to which the unicast packet needs to be sent according to the calculation rule. After the table is looked up, the heartbeat command is forwarded to the boundary sub-control server B32 through the port 1 of the terminal sub-control server B31.

S24, the boundary sub-control server B32 receives the device heartbeat order on the port No. 1, and if the destination MAC address, the packet type and the length of the data packet are found to accord with the unicast packet receiving rule, the next receiver is calculated. Since the destination autonomous network address of the packet is identical to the global logical address of port 0 of the border sub-control server B32, the next receiver is an internal protocol processing module.

And the protocol processing module compares whether the self-control network address of the data packet is the same as the recorded global logic address of the master control server, and sends a device heartbeat response to the master control server if the self-control network address of the data packet is the same as the recorded global logic address of the master control server. The packet type is a unicast packet, the destination autonomous network address is the global logic address of the master control server, and the source autonomous network address is the global logic address of port 0 of the boundary sub-control server B32.

And then determining the equipment with the logical port address of 0xfb in the master control micro cloud needing to be sent to the port 1 according to the forwarding rule of the unicast packet, wherein the destination MAC address obtained after table lookup is the port 1 MAC address of the central equipment B31. Then, these heartbeat responses are received by the terminal sub-control server B31, and are forwarded to the main control server A3 according to the forwarding rule of the unicast packet.

In addition, the border sub-control server B32 reports the network access status of the border routers in the sub-control micro-cloud managed by itself when sending the response. The current state is that all border routers are not meshed.

Seven, boundary sub-control server B32 configuration

S25, after the border sub-control server B32 accesses the network, the main control server A3 needs to send an exchange node information configuration command to the border sub-control server B32 and other devices in the main control micro-cloud that have accessed the network. The command sent to the boundary sub-control server B32 is used to configure its transmission matching table No. 1, and indicates MAC address information (such as information of the boundary router M31 and the terminal sub-control server B31) used when sending a unicast packet to other networked devices, the command sent to other devices is used to configure the transmission matching table No. 0 of the device when the device is a boundary router (such as the boundary router M31), configured is used to configure the transmission matching table No. 1 of the device when the device is a sub-control server (such as the terminal sub-control server B31), and the switching node information configuration command sent to other devices contains MAC address information used when other devices send unicast packets to the boundary sub-control server B32.

S26, after the border sub-control server B32 accesses the network, the main control server A3 sends a device registration information configuration command to it. The device registration information configuration command includes device registration information of the border router M21 and the border router M22.

After receiving the command, the border sub-control server B32 records the registration information in the corresponding entry in the device static information table and marks it as valid.

The boundary sub-control server B32 further needs to send a matching table according to the logical port address and the MAC address configuration number 0 in the device registration information. For example, the logical port address of port 1 of the boundary router M21 is 0x21, and the MAC address of port 1 is 00:00:00:02:21: f2, then the sending flag bit in the 0x21 table entry of the sending matching table No. 0 of the boundary sub-control server B32 is set to 1, and the MAC address is set to the MAC address of port 1 of the boundary router M21. The matching table entry of the border router M22 is set similarly.

After the configuration is completed, the border sub-control server B32 sends a device registration information configuration response to the master server A3.

Eighthly, the boundary router M21 and the boundary router M22 uplink interface network access

And S27, the boundary sub-control server checks all registered but non-networked terminals in the sub-control micro-cloud and sends a device connection command to the terminals.

For example, when the boundary sub-control server B32 finds that the valid bit of the 0x21 entry in the device static information table is 1 and the network entry status of the 0x21 entry in the device dynamic information table is not network entry, it sends a device connect command to port 1 of the boundary router M21.

The packet type of the device connect command is a connect packet, the destination MAC address is port 1 MAC address of M21, the source MAC address is port 0 MAC address of B32, the destination autonomous network address is connection address 0x 21210 x 21210 x 21210 x2121 (port 1 logical port address of M21 is 0x21), and the source autonomous network address is connection address 0xffff 0xffff 0xffff 0xffff (logical port address of administrator is fixed to 0 xff).

The Payload part of the device connection command includes, in addition to the logical device types and identifiers of both parties, a micro cloud level equal to 5, a node type equal to the border router, and a MAC address used when sending a connection packet to the border sub-control server is port 0 MAC address of the border sub-control server B32, and a session identifier is 1. The boundary sub-control server B32 needs to record the related information (network access status, session identification, etc.) in the 0x21 th entry of the device dynamic information table.

S28, boundary router M21 receives the device connection command on port No. 1, finds that the destination MAC address, packet type and length of the data packet all accord with the connection packet receiving rule, and directly delivers the data packet to the protocol processing module for processing. The protocol processing module finds that the network access state of port 0 of the border router M21 is the network access state, that is, the network access process of port 1 is started.

The protocol processing module judges that the data packet belongs to the protocol processing module according to the type and the identification of the logic device, finds that a value obtained by subtracting 1 from the cloudlet level in the command (5 is changed into 4) is equal to a cloudlet level value (4) obtained through the 0 port network access process, and then records information in the command (the 0 port MAC address, the session identification and the like of B32).

The protocol processing module configures the 0xff table entry of the ethernet transmission matching table No. 1, sets the transmission flag bit to be 1, and sets the MAC address to be the MAC address of port 0 of the boundary slave control server B32 (00:00:00:03:32: fb).

The protocol processing module sends a device connection response to port 1, the packet type is a connection packet, the destination autonomous network address is a connection address 0 xfffff, the source autonomous network address is a connection address 0x 21210 x 21210 x2121, the destination MAC address is obtained by searching the ethernet transmission matching table port 1 (port 0 MAC address of B32), and the source MAC address is port 1 MAC address of M21, and the transmission flag bit is 1 (indicating transmission is allowed).

S29, the boundary sub-control server B32 receives the device connection response, obtains the logical port address 0x21 according to the autonomous network address, searches the device dynamic information table according to 0x21, and judges whether the response belongs to the current connection session according to the session identifier. A device authentication command is then sent to the border router M21, including the type of authentication algorithm and the random number, as well as the session identification, in the Payload section of the command.

S30, the boundary router M21 receives the device authentication command, judges whether the command belongs to the current connection session according to the session identification, and then calculates the authentication calculation result. And then sends a device authentication response to the border sub-control server B32.

And S31, after receiving the equipment authentication response, the boundary sub-control server B32 judges whether the authentication calculation result is correct. If so, a device network entry command is sent to the border router M21.

S32, after receiving the device network access command, the border router M21 determines whether the command belongs to the current connection session according to the session identifier, and then records related information, including the local device number (70032) of the border sub-control server B32, the local logical address (0x32fb) of the border sub-control server B32, the local device number (60021) of the border sub-control server B, the local logical address (0x3221) of the border sub-control server B, the local device number (90003) of the main control server A3, the local logical address (0xfb00) of the main control server A3, the MAC address (0 port MAC address of B32) used when sending a unicast packet to the border sub-control server, the prefix of the number of the autonomous cloud device, the prefix of the logical address of the autonomous cloud, and the logical port address of the upper forwarding node (0xfb corresponds to the 0 port logical port address of the border sub-control server B32).

Based on the above information, the boundary router M21 can calculate that the global device number of the boundary sub-control server is 60031-fb 70032-00000, the global logic address of the boundary sub-control server is 4231-32fb-0000, the global device number of the main control server A3 is 60031-90003-00000, and the global logic address of the main control server A3 is 4231-fb 00-0000.

The border router M21 further needs to calculate the device number prefix of the autonomous cloud C2 to be 60031-. Since the comparison results are all the same, it can be determined that the autonomous cloud C3 accessed through the port 1 is indeed the upper autonomous cloud of the autonomous cloud C2 accessed through the port 0.

Then, the boundary router M21 configures the 0 th 0xfb entry of the ethernet transmission matching table No. 1 according to the port 0 logical port address of the boundary slave server B32, sets the transmission flag bit to 1, and sets the MAC address to the port 0 MAC address (00:00:00:03:32: fb) of the boundary slave server B32. And adding a filtering rule for receiving the unicast packet and the multicast packet, wherein the unicast packet receiving rule is that the destination MAC address and the interface MAC address are the same, the packet type is a unicast packet and the length is 64 bytes, 288 bytes or 1056 bytes, and the multicast packet receiving rule is that the destination MAC address and the interface MAC address are the same, the packet type is a multicast packet and the length is 288 bytes or 1056 bytes.

Finally, the boundary router M21 sends a device network access response to the boundary sub-control server B32, where the device network access response needs to include the local logical address (0xf100) and the local device number (80021) obtained through the port 0 network access flow. Meanwhile, setting the number 1 port of the user to be in a network access state.

And S33, after receiving the device network access response sent by the boundary router M21, the boundary sub-control server B32 sets the device in the network access state in the device dynamic information table. Meanwhile, the port 0 global logic address of the boundary router M21 is 4231-.

S34, the border router M22 enters the network through port No. 1 in the same flow. After the border router M21 and the border router M22 are networked, the heartbeat flow between them and the border sub-control server B32 is similar to the heartbeat flow between the main control server A3 and the border sub-control server B32, but for the border sub-control server B32, the destination autonomous network address of the device heartbeat command sent by it must be the port 0 global logical address of the border router M21 and the border router M22. Otherwise, the data packet cannot be transferred to the internal protocol processing module.

S35 and the border sub-control server B32, after the border router M21 and the border router M22 access the network, the border router access state in the device heartbeat response sent to the main control server a3 would indicate that the access state of the border router with the current logical port addresses 0x21 and 0x22 is changed into an already-accessed network.

After receiving the heartbeat response, the main control server a3 determines that the local logical addresses of the boundary router are 0x3221 and 0x3222, respectively, according to the port 1 logical port address 0x32 of the boundary sub-control server B32 and the logical port addresses 0x21 and 0x22 of the boundary router. Then, the address number mapping table is searched to obtain the local device numbers 60021 and 60022, and then the network access states are set in the device dynamic information table as the network access states.

It should be emphasized that, although the border router M21 and the border router M22 can know the global logical address of the master server A3 after entering the network, the master server A3 knows their port 1 global logical address instead of port 0 global logical address, i.e. the master server A3 can only receive unicast packets from the border router M21 and the border router M22 but cannot send them.

Nine, border router M21 and border router M22 upstream interface switching node information configuration

S36, after the border router M21 accesses the network, the border sub-control server B32 needs to send an exchange node information configuration command to the border router M21 and other border routers that have accessed the network in the sub-control clout. The command sent to the border routers is used to configure their No. 1 send match table.

Assuming that both border router M21 and border router M22 are networked, the table entry valid in their No. 1 forwarding matching table is as follows:

if the topology of the sub-control micro-cloud is full exchange, the table entry in the No. 1 sending matching table is as follows:

ten, autonomous cloud access

S37, after the border router M21 accesses the network through port 1, it knows the information of the master server a2 and also knows the information of the master server A3. It would then send autonomous cloud network entry configuration commands to master server a2 and master server A3, respectively.

The autonomous cloud networking configuration command sent by the boundary router M21 to the master server a2 includes its own logical device type and logical device identifier, and the local logical address and local device number of the master server A3.

After receiving the command, the main control server a2 determines that the sender is located in the autonomous cloud and the corresponding local logical address is 0xf100 according to the autonomous network address (0x 42310 x 32210 xf 1000 x0000) in the data packet, then queries the address number mapping table to obtain the local device number 80021, then queries the device static information table, the device dynamic information table, and the autonomous cloud access table, determines whether the boundary router M21 is registered, has accessed to the network through port No. 1, and the like, and finally determines whether the logical device type and the logical device identifier in the command are the same as the information in the device static information table.

If the check is passed, the global logical address and the global device number of the master server A3 can be calculated according to the hierarchy of the master micro cloud, the logical address prefix, the device number prefix, the local logical address of the master server A3 and the local device number, then the information is recorded in the 0xf100 table entry of the autonomous cloud access table, and the access state in the table entry is updated to be accessed.

After the command is processed, the master control server a2 sends an autonomous cloud network access configuration response to the M21. And the M21 completes the process of accessing the upper layer autonomous cloud into the lower layer autonomous cloud after receiving the message.

S38, when the boundary router M21 sends an autonomous cloud networking configuration command to the master control server A3, the command includes a logical device type and a logical device identifier of the command, a local logical address and a local device number of the boundary router M21 in the autonomous cloud C2, and a local logical address and a local device number of the master control server a 2.

When the border router M21 sends this packet, it needs to calculate the next receiver because it is a unicast packet. The destination autonomous network address of the data packet is a global logical address 0x 42310 xfb 000 x 00000 x0000 of the master control server a3, and the port 0 global logical address of M21 is 0x 42310 x 32210 xf 1000 x 0000. The cloudlet hierarchy of the boundary router M21 is 4, so the address of the master server A3 is divided into three parts 4231fb, 00, and the address of the boundary router M21 is divided into three parts 423132, 21, f 1.

According to the rule, the address 2 parts belonging to the two addresses are different, and the next receiver is a special device called an upper layer forwarding node in the micro cloud to which the port 1 belongs, so that the next receiver of the data packet is the upper layer forwarding node in the micro cloud to which the port 1 belongs, and the logical port address of the next receiver is 0 xfb. By inquiring the transmission matching table No. 1 of the border router M21, it can be known that the destination MAC address of the packet is port 0 MAC address of the border slave server B32.

The boundary slave server B32 receives the packet on port 0 and calculates the next receiver as well. Since the micro cloud level of the boundary sub-control server B32 is 5, the address of A3 is divided into three parts, 4231, fb and 00, and the address of the boundary router M21 is divided into three parts, 4231, 32 and 21.

According to the rule, the next receiver is the equipment with the logical port address of 0xfb in the micro cloud to which the port No. 1 belongs. After inquiring the transmission matching table No. 1 of the boundary sub-control server B32, it can be known that the destination MAC address of the packet is the MAC address No. 1 of the terminal sub-control server B31 (the terminal sub-control server B31 is the central device).

Finally, the data packet is forwarded to the master server A3 through the terminal slave server B31.

S39 and the main control server A3, after receiving the autonomous cloud network access configuration command, determine that the sender is located in the autonomous cloud and the corresponding local logical address is 0x3221 according to the autonomous network address (0x 42310 x 32210 xf 1000 x0000) in the data packet, then query the address number mapping table to obtain the local device number 60021, then query the device static information table and the device dynamic information table, determine whether the boundary router M21 is registered, determines whether the router has accessed the network, and the like, and finally determine whether the type of the logical device and the identifier of the logical device in the command are the same as the information in the device static information table.

If the above checks all pass, the global logical address and the global device number of port 0 of the boundary router M21 can be calculated to be 4231-f 100-0000 and 60031-60021-80021-00000 respectively according to the hierarchy of the master cloudlet, the logical address prefix, the device number prefix, the local logical address and the local device number of the boundary router M21 in the autonomous cloud C2 and other information. The global logical address and the global device number of the master server a2 can be calculated according to the information and the local logical address and the local device number of the master server a 2. Then, the information is recorded in the 0x3221 table entry of the autonomous cloud access table, and the access state in the table entry is updated to be accessed.

After the command is processed, the master control server a3 sends an autonomous cloud network access configuration response to the border router M21, and the destination autonomous network address used at this time is the global logical address of port 0 of the border router M21. And the boundary router M21 completes the process of accessing the lower autonomous cloud to the upper autonomous cloud after receiving the information.

Third, configuring multicast link in single autonomous cloud (autonomous cloud interior no multicast address replacement)

As shown in fig. 25, assuming that the autonomous cloud C2 is located at layer 2 of the autonomous network, for simplicity, the boundary sub-control server and the boundary router are omitted, the main control server a2, the terminal sub-control server B21, the terminal sub-control server B22, and the terminal sub-control server B23 are connected in the same switching network, the terminal sub-control server B21, the terminal T21, and the terminal T22 are connected in the same switching network, the terminal sub-control server B22, the terminal T23, and the terminal T24 are connected in the same switching network, and the terminal sub-control server B23, the terminal T25, and the terminal T26 are connected in the same switching network.

1. Creation of data Source for terminal T21

Assuming that a 2-way multicast data stream needs to be created for the terminal T21 in a certain service flow, the service processing module of the main control server a2 first sends a 1 st request for creating a data source to the multicast management module, where the data source type in the request is 1 (physical data source), the global device number of the global data source is 60031-.

And the multicast management module finds that the global data source belongs to the autonomous cloud and the equipment type is the terminal.

The multicast management module queries the data source index table according to the global device number and the channel number of the global data source, starts to allocate a multicast address after finding that the multicast data stream does not exist, obtains a new multicast address of 0x00000001 (the multicast address 0 is reserved and cannot be allocated) because no multicast data stream exists at the moment, and then sets the next allocable multicast address of 0x 00000002.

The multicast management module updates the information in the 0x00000001 entry of the data source information table, and adds a new entry (which can be found to 0x00000001 through 60031-.

The multicast management module sends a data source creating response to the service processing module, and the service processing module records that the multicast address corresponding to the 1 st data channel is 0x 00000001.

The service processing module sends a 2 nd request for creating a data source to the multicast management module, where the data source type in the request is 1, the global device number of the global data source is 60031-.

The multicast management module processes according to the same flow, the allocated multicast address is 0x00000002, the next allocable multicast address is 0x00000003, the data source index table and the information table are updated similarly, and then the created data source response is sent to the service processing module.

The service processing module receives the data source creating response and then notifies the terminal T21 through the service flow, and the multicast addresses of the 2-way data source are 0x00000001 and 0x00000002, respectively.

The terminal T21 starts to generate a packet of the 1 st data source but does not transmit it. The type of the packet is a multicast packet, the destination MAC address is the port 0 MAC address of the terminal sub-control server B21, the source MAC address is the MAC address of the terminal T21, the destination autonomous network address is 0x00000 x00000 x00000 x0001, and the source autonomous network address is the global logical address of the terminal T21.

The terminal T21 also generates a packet of the source of the 2 nd data, but does not transmit the packet, and the destination autonomous network address of the packet is 0x00000 x00000 x00000 x 0002.

2. Adding a data sink for terminal T22

Assuming that the 1 st data channel of the terminal T22 is required to receive the 1 st multicast data stream of the terminal T21 and the 2 nd data channel of the terminal T22 is required to receive the 2 nd multicast data stream of the terminal T21 in the service flow, the service processing module of the main control server a2 first sends a 1 st add data sink request to the multicast management module, where the global data sink global device number in the request is 60031 plus 00022 plus 00000 (the global device number of the terminal T22), the global data sink channel number is 1, the global data source global device number bit 60031 plus 60021 plus 00021 plus 00000 (the global device number of the terminal T21), and the global data source channel number is 1.

And after receiving the data sink adding request, the multicast management module finds that the global data source belongs to the local autonomous cloud and the equipment type is a terminal, and finds that the global data sink belongs to the local autonomous cloud and the equipment type is a terminal.

The multicast management module inquires a data source index table according to the global device number and the channel number of the global data source, finds that the multicast data stream exists, the corresponding multicast address is 0x00000001, inquires the 0x00000001 table item of the data source information table, finds that the multicast data stream exists, the data source type is 1, the data source device number is 00021, and then obtains the local device number of 00022 according to the global data convergence global device number.

The multicast management module can know that the local data source 00021 and the local data sink 00022 corresponding to the data sink adding operation are located in the same cloudland managed by the terminal sub-control server B21 through the device management module, so that the local multicast link of the multicast management module is terminal T21 → terminal sub-control server B21 → terminal T22.

The multicast management module checks whether the available flow of each device on the local multicast link meets the flow requirement of the data flow.

The multicast management module uses the multicast address 0x00000001 and the cloudlet number 0x21 to query the multicast routing table, finds that no entry exists, that is, the multicast data stream is not transmitted in the sub-control cloudlet managed by the terminal sub-control server B21, and therefore sends a data source state control command to the terminal T21 and sends a multicast link control command to the terminal sub-control server B21.

The multicast management module sends a data source status control command to the terminal T21, where the data source status control command requests the terminal T21 to start sending a data packet of a multicast data stream with a multicast address of 0x 00000001.

The multicast management module sends a multicast link control command to the terminal sub-control server B21, where the multicast link control command requires the terminal sub-control server B21 to send a multicast data stream with a multicast address of 0x00000001 from port 0 to port 0 at the same multicast address (configure a multicast guide table), and simultaneously starts sending the multicast data stream with the multicast address of 0x00000001 from port 0 to a device with a logical port address of 0x22 (configure a multicast information table).

After receiving the multicast link control command, the terminal T21 sends a multicast link control response and starts to send the data packet of the 1 st path multicast data stream.

After receiving the multicast link control command, the terminal sub-control server B21 queries the 0x00000001 entry of the multicast guide table No. 0, finds that the guide mode is 0 (no transmission), sets the guide mode to 1 (no transmission replacement) because the multicast addresses to be transmitted are the same, sets the 0x22 bit in the 0x00000001 entry of the multicast information table No. 0 to 1, and finally transmits a multicast link control response to the main control server a 2.

After receiving the multicast link control response, the multicast management module adds an entry with a multicast address of 0x00000001 and a micro cloud number of 0x21 to the multicast routing table, where bytes 0x21 in the entry are set to 0x21 (indicating that the data source is a terminal T21), bytes 0xfb are set to 0x21 (indicating that data of the terminal sub-control server B21 is from the terminal T21), and bytes 0x22 are set to 0xfb (indicating that data of the terminal T22 is from the terminal sub-control server B21).

The multicast management module sends a data sink adding response to inform the service processing module that the data sink adding of the 1 st path is successful, and the multicast address is 0x 00000001.

The service processing module sends a 2 nd request for adding data sink to the multicast management module, where the global data sink global device number is 60031-.

And the multicast management module adds the 2 nd data sink according to the same flow, the corresponding multicast address is 0x00000002, and then sends a data sink adding response to the service processing module.

After receiving the add data sink response, the service processing module notifies the terminal T22 through the service flow to start receiving multicast data streams with multicast addresses of 0x00000001 and 0x00000002 on the 1 st and 2 nd data channels, respectively.

After the above-mentioned process is completed, terminal T21 starts to send out multicast packet, the multicast packet is first sent to port 0 of terminal sub-control server B21, after terminal sub-control server B21 receives the multicast packet, it first queries the corresponding table entry in the guide table of port 0, finds that the guide mode in the table entry is 1, it indicates that the multicast packet needs to be sent to port 0 and does not replace multicast address, then queries the corresponding table entry in the multicast information table of port 0, finds that only 0x22 bit of 256 bits is 1, it indicates that the multicast packet only needs to be sent to the device with logical port address 0x22, finally queries 0x22 table entry in the transmission matching table of port 0 to obtain the MAC address of terminal T22, replaces the destination MAC address of the received multicast packet with the MAC address of terminal T22, and replaces the source MAC address with the MAC address of port 0 of terminal sub-control server B21, and then sends out, so that terminal T22 receives the needed multicast packet, after the processing of the guide table No. 0 is completed, the terminal sub-control server B21 continues to query the corresponding table entry in the guide table No. 1, and finds that the guide mode in the table entry is 0, that is, it is not necessary to send the data to the port No. 1, and then the processing flow of the multicast packet is finished.

3. Adding a data sink to terminal T26

Assuming that the 1 st data channel of the terminal T26 is required to receive the 2 nd multicast data stream of the terminal T21 in the service flow, the service processing module of the main control server a2 sends an add data sink request to the multicast management module, where the global data sink global device number in the request is 60031-60021-00026-00000 (the global device number of the terminal T26), the global data sink channel number is 1, the global data source global device number bit 60031-00021-00000 (the global device number of the terminal T21), and the global data source channel number is 2.

The multicast management module inquires a data source index table according to the global device number and the channel number of the global data source, finds that the multicast data stream exists, the multicast address is 0x00000002, inquires a data source information table, finds that the multicast data stream exists, the data source type is 1, the data source device number is 00021, and then obtains the local device number of 00026 according to the global data sink global device number.

The multicast management module calculates that a local multicast link between the local data source T21 and the local data sink T26 is a terminal T21 → a terminal sub-control server B21 → a terminal sub-control server B23 → a terminal T26, and then checks whether traffic meets the demand.

The multicast management module queries a multicast routing table by using a multicast address 0x00000002 and a micro cloud number 0x21, finds that an entry exists, that is, a multicast data stream is already transmitted in a sub-control micro cloud managed by a terminal sub-control server B21, then queries the multicast routing table by using the multicast address 0x00000002 and the micro cloud number 0xfb, finds that an entry does not exist, that is, the multicast data stream is not yet transmitted in a main control micro cloud managed by a main control server a2, so that a multicast link control command is sent to a terminal sub-control server B21, and finally queries the multicast routing table by using the multicast address 0x00000002 and the micro cloud number 0x23, finds that an entry does not exist, that is, the multicast data stream is not yet transmitted in a sub-control micro cloud managed by a terminal sub-control server B23, so that a multicast link control command is sent to a terminal sub-control server B23.

The multicast management module sends a multicast link control command to the terminal sub-control server B21, where the multicast link control command requests the terminal sub-control server B21 to send a multicast data stream with a multicast address of 0x00000002 from port No. 0 to port No. 1 at the same multicast address (configure multicast guide table), and at the same time, starts to send the multicast data stream with the multicast address of 0x00000002 from port No. 1 to a device with a logical port address of 0x23 (configure multicast information table).

The multicast management module sends a multicast link control command to the terminal sub-control server B23, where the multicast link control command requests the terminal sub-control server B23 to send the multicast data stream with the multicast address 0x00000002 from the port No. 1 to the port No. 0 at the same multicast address (configure multicast direction table), and at the same time, starts to send the multicast data stream with the multicast address 0x00000002 from the port No. 0 to the device with the logical port address 0x26 (configure multicast information table).

The terminal sub-control server B21, after receiving the multicast link control command, queries the 0x00000002 entry of the multicast information table No. 1, finds that the guidance mode is 0 (no transmission), then sets the guidance mode to 1 (no transmission replacement), sets the 0x23 bit in the 0x00000002 entry of the multicast information table No. 1 to 1, and finally sends a multicast link control response to the main control server a 2.

The terminal sub-control server B23 inquires the 0x00000002 table entry of the multicast guide table No. 2 after receiving the multicast link control command, finds that the guide mode is 0 (no transmission), then sets the guide mode to 1 (no replacement by transmission), sets the 0x26 bit in the 0x00000002 table entry of the multicast information table No. 0 to 1, and finally sends the multicast link control response to the main control server A2.

After receiving the multicast link control response, the multicast management module adds an entry with a multicast address of 0x00000002 and a micro cloud number of 0xfb in the multicast routing table, where a 0x21 byte in the entry is set to 0x21 (indicating that a data source is a terminal sub-control server B21), and a 0x23 byte is set to 0x21 (indicating that data of the terminal sub-control server B23 comes from the terminal sub-control server B21).

Then, a table entry with a multicast address of 0x00000002 and a micro cloud number of 0x23 is added to the multicast routing table, where byte 0xfb in the table entry is set to 0xfb (indicating that a data source is a terminal sub-control server B23), and byte 0x26 is set to 0xfb (indicating that data of a terminal T26 is derived from a terminal sub-control server B23).

The multicast management module sends an add data sink response to the service processing module, and the service processing module receives the add data sink response and then notifies the terminal T26 of receiving the multicast data stream with the multicast address of 0x00000002 on the 1 st data channel through the service flow.

After the above flow is completed, the multicast packet with the multicast address of 0x00000002 sent by the terminal T21 is first sent to the port 0 of the terminal sub-control server B21, the terminal sub-control server B21 receives the multicast packet and then queries the corresponding table entries in the multicast guide table No. 0 and No. 1, it is found that the guide mode in the table entry No. 0 is 1, the 0x22 bit in the corresponding table entry of the multicast information table No. 0 is 1, so the multicast packet is sent to the terminal T22 through the port 0, it is found that the guide mode in the table entry No. 1 is 1, the 0x23 bit in the corresponding table entry of the multicast information table No. 1 is 1, so the multicast packet is sent to the terminal sub-control server B23 through the port 1, after the terminal sub-control server B23 receives the multicast packet, it also queries its own multicast guide table and information table, and as a result, the multicast packet is sent to the terminal T26, so that the terminal T22 and the terminal T26 receive the needed multicast packet.

4. Adding data sinks for other terminals

Assuming that a 1 st data channel of a terminal T23, a terminal T24, and a terminal T25 is needed in a service flow to receive a2 nd multicast data stream of the terminal T21, after the same flow is passed, an entry with a multicast address of 0x00000002 and a micro cloud number of 0x22 is added in a multicast routing table of the master server a2, a transmission path of the multicast data stream in the master micro cloud is changed to the terminal sub-control server B21 and is simultaneously sent to the terminal sub-control server B22 and the terminal sub-control server B23, a transmission path of the multicast data stream in the sub-control micro cloud managed by the terminal sub-control server B22 is changed to the terminal sub-control server B22 and is simultaneously sent to the terminal T23 and the terminal T24, and a transmission path of the multicast data stream in the sub-control micro cloud managed by the terminal sub-control server B23 is changed to the terminal sub-control server B23 and is simultaneously sent to the terminal T25 and the terminal T26.

After the above flow is completed, the multicast packet with the multicast address of 0x00000002 sent by the terminal T21 is simultaneously sent to 5 terminals T22, T23, T24, T25, T26, and the multicast packet with the multicast address of 0x00000001 is separately sent to the terminal T22.

5. Deleting data sink for terminal T22

Assuming that the 1 st and 2 nd data channels of the terminal T22 are required in the service flow to no longer receive the 1 st and 2 nd multicast data streams of the terminal T21, the service processing module of the main control server a2 first sends a request for deleting the data sink of the 1 st data sink to the multicast management module, where the global data sink global device number in the request is 60031 + 60021 + 00022 + 00000 (the global device number of the terminal T22), the global data sink channel number is 1, the global data source global device number bit 60031 + 60021 + 00021 + 00000 (the global device number of the terminal T21), and the global data source channel number is 1.

And after receiving the request for deleting the data sink, the multicast management module finds that the global data source belongs to the autonomous cloud and the equipment type is terminal, and finds that the global data sink belongs to the autonomous cloud and the equipment type is terminal.

The multicast management module finds that the multicast data stream exists, and calculates a local multicast link between the local data source T21 and the local data sink T22 as a terminal T21 → a terminal sub-control server B21 → a terminal T22.

The multicast management module searches a multicast routing table, obtains an entry with a multicast address of 0x00000001 and a micro cloud number of 0x21, finds that the terminal T22 really receives the multicast data stream of the path and no other device receives data from the terminal sub-control server B21 after analysis, then sends a multicast link control command to the terminal sub-control server B21, and requires the terminal T22 to stop sending the multicast data stream with the multicast address of 0x00000001 from the port 0 to the device with the logical port address of 0x22 (configure a multicast information table), and simultaneously stops sending the multicast data stream with the multicast address of 0x00000001 from the port 0 to the port 0 with the same multicast address (configure a multicast guide table).

The multicast management module checks the table entry of the multicast routing table, and finds that, at this time, except for the terminal sub-control server B21, other terminals do not receive the multicast data stream, that is, there is no data sink in the cloud to which the port 0 of the terminal sub-control server B21 belongs, it is necessary to check whether there is a data sink in the cloud to which the port 1 of the terminal sub-control server B21 belongs, and the cloud to which the port 1 belongs is the master cloud, so it is necessary to search for a table entry having a multicast address of 0x00000001 and a cloud number of 0xfb in the multicast routing table, and as a result, there is no table entry, that is, there is no data sink in the cloud to which the port 1 of the terminal sub-control server B21 belongs, and at this time, a transmission path from the terminal T21 to the terminal sub-control server B21 should be closed, so that a data source state control command is sent to the terminal T21, and the terminal T21 is required to stop sending the multicast data stream having a multicast address of 0x 00000001.

After receiving the multicast link control command, the terminal sub-control server B21 sets the 0x22 bit of the 0x00000001 table entry of the multicast information table No. 0 to 0, queries the 0x00000001 table entry of the multicast guide table No. 0, finds that the guide mode is 1 (sending and not replacing), sets the guide mode to 0, and then sends a multicast link control response to the main control server a 2.

After receiving the data source state control command, the terminal T21 stops sending the data stream with the multicast address of 0x00000001, and then sends a data source state control response to the master server a 2.

After receiving the multicast link control response of the terminal sub-control server B21 and the data source state control response of the terminal T21, the multicast management module deletes the corresponding entry in the multicast routing table, and then sends a delete data convergence response to the service processing module.

The service processing module sends a request for deleting data sink of the 2 nd path multicast data stream to the multicast management module, after processing, the multicast management module finds that a multicast link control command needs to be sent to the terminal sub-control server B21, and requests the multicast management module to stop sending the multicast data stream with the multicast address of 0x00000002 to the device with the logical port address of 0x22 from the port No. 0 (configuring a multicast information table), and simultaneously stops sending the multicast data stream with the multicast address of 0x00000002 from the port No. 0 to the port No. 0 with the same multicast address (configuring a multicast guide table).

The multicast management module finds that although no other receiver exists in the cloudset to which the port 0 of the terminal sub-control server B21 belongs, no other receiver exists in the cloudset to which the port 1 of the terminal sub-control server B21 belongs, so that the transmission path from the terminal T21 to the terminal sub-control server B21 cannot be closed.

The terminal sub-control server B21 processes the multicast link control command after receiving the command, and then sends a multicast link control response to the main control server.

And after receiving the multicast link control response of the terminal sub-control server B21, the multicast management module sends a delete data sink response to the service processing module.

After receiving the delete data sink response, the service processing module notifies the terminal T22 through the service flow that the multicast data stream with the multicast addresses 0x00000001 and 0x00000002 is no longer received.

6. Destroying data source for terminal T21

The service processing module sends 2 data source destroying requests to the multicast management module, wherein the data source type in the requests is 1, the global data source global device number is the global device number of the terminal T21, and the global data source channel numbers are 1 and 2 respectively.

And the multicast management module finds that the global data sources all belong to the autonomous cloud and the equipment type is the terminal.

The multicast management module finds that the multicast data streams needing to be destroyed all exist through table lookup.

For the multicast data stream with the multicast address of 0x00000001, it may be found that there is no entry of the clout where the terminal T21 is located in the multicast routing table, that is, there is no other data sink. Therefore, the table entry in the data source index table is directly deleted, and the data source state of the table entry in the data source information table is set to 0.

For the multicast data stream with the multicast address of 0x00000002, it is found that there is an entry corresponding to the cloudlet where the terminal T21 is located in the multicast routing table, that is, there are other receivers, so that the multicast data stream cannot be destroyed.

The multicast management module sends 2 destroyed data source responses to the service processing module, which respectively indicate that the 1 st destroyed data source request processing is successful and the 2 nd destroyed data source request processing is failed.

And the service processing module continues the subsequent service process after receiving the data source destroying response.

Example four, configuring multicast link in single autonomous cloud (autonomous cloud with multicast address replacement inside)

As shown in fig. 25, assuming that the autonomous cloud C2 is located at the level 2 of the autonomous network, for simplicity of description, ignoring the boundary sub-control server and the boundary router, the main control server a2, the terminal sub-control server B21, the terminal sub-control server B22, and the terminal sub-control server B23 are connected in the same switching network, the terminal sub-control server B21, the terminal T21, and the terminal T22 are connected in the same switching network, the terminal sub-control server B22, the terminal T23, and the terminal T24 are connected in the same switching network, and the terminal sub-control server B23, the terminal T25, and the terminal T26 are connected in the same switching network.

The device configured to participate in a certain service flow includes a terminal T21, a terminal T22, a terminal T23, a terminal T24, a terminal T25, a terminal T26, and a terminal sub-control server B22, where each terminal is configured to be able to send 2-way multicast data streams and to receive 3-way multicast data streams, and the terminal sub-control server B22 is configured to be required to replace 3-way multicast data streams.

1. Creating a data Source

The service processing module of the main control server a2 sends 12 requests for creating data sources to the multicast management module, creates 12 multicast data streams of 6 terminals, so that the 6 terminals become physical data sources, and assumes that the multicast addresses of the 12 multicast data streams are 1 to 12 respectively, that is, the multicast addresses of the terminal T21 are 1 and 2, the multicast addresses of the terminal T22 are 3 and 4, and so on.

Then, 3 requests for creating data sources are sent to the multicast management module, and 3 multicast data streams are created for the sub-control terminal server B22, so that the sub-control terminal server B22 becomes a virtual data source, where it is assumed that the data channel number of the 3 multicast data streams is 1 to 3 (if there are already other data sources on the sub-control terminal server B22, other values may be taken), and it is further assumed that the multicast addresses of the sub-control terminal server B22 are 13 to 15 in sequence, and since the multicast data stream of the sub-control terminal server B22 has not been subjected to address replacement at this time, the multicast address before replacement in the entry of the data source information table is 0.

After receiving all the created data source responses, the service processing module of the main control server a2 notifies the multicast address of the 2-way multicast data stream of each terminal through the service flow.

After receiving the notification, each terminal starts to generate the corresponding multicast data stream but does not transmit the multicast data stream.

2. Adding physical data sink 1

The service processing module of the main control server a2 sends multiple add data sink requests to the multicast management module, where the requests require the 1 st data channel of the terminal T21 to receive the data of the 1 st multicast data stream from the terminal sub-control server B22, the 1 st data channels of the other 5 terminals to receive the data of the 1 st multicast data stream from the terminal sub-control server B22, the 2 nd data channel to receive the data of the 2 nd multicast data stream from the terminal sub-control server B22, and the 3 rd data channel to receive the data of the 3 rd multicast data stream from the terminal sub-control server B22.

The multicast management module processes the requests and then sends multicast link control commands to the terminal sub-control server B21, the terminal sub-control server B22, the terminal sub-control server B23 and the like to configure related entries, the terminal sub-control server B21 and the terminal sub-control server B23 are data forwarding nodes located on a local multicast link, and need to configure a corresponding multicast guide table and a multicast information table, and the terminal sub-control server B22 is a terminal sub-control server as a data source, so that only the multicast information table needs to be configured.

The terminal sub-control server B22 receives the multicast link control command and then performs configuration, and as a result of the configuration, the 0x23 bit and the 0x24 bit of the entry with multicast addresses 13, 14 and 15 in the multicast information table 0 are set to 1, which indicates that the 3-way multicast data stream is sent to the terminal T23 and the terminal T24 from the port 0, and the 0x21 bit and the 0x23 bit of the entry with multicast addresses 13, 14 and 15 in the multicast information table 1 are set to 1, which indicates that the 3-way multicast data stream is sent to the terminal sub-control server B21 and the terminal sub-control server B23 from the port 1.

After the configuration of the terminal sub-control server B21, the terminal sub-control server B22, and the terminal sub-control server B23, the multicast management module of the main control server a2 sends a multicast link control response to the main control server a2, and after receiving the multicast link control response, the multicast management module processes the multicast link control response and sends an add data sink response to the service processing module.

3. Adding virtual data sink 1

The service processing module of the main control server a2 sends 2 requests for adding data sinks to the multicast management module, where the requests require that the 1 st data channel of the terminal sub-control server B22 receive the 1 st multicast data stream sent by the terminal T21, and the 2 nd data channel receive the 2 nd multicast data stream sent by the terminal T21.

When the multicast management module processes the requests, it finds that the data sink is the terminal sub-control server, so besides the same process as that when no multicast address is replaced, it also needs to send a multicast link control command to the data sink, firstly, the global device number and the data sink channel number (equal to the data source channel number) of the terminal sub-control server B22 are used to query the data source index table, find that the corresponding data source exists, then query the data source information table, find that the multicast address before replacement is 0, so it can perform address replacement. At this time, it can be known that the new multicast addresses before replacement are 1 and 2 (multicast addresses of multicast data streams), respectively, and the multicast addresses after replacement are 13 and 14.

The multicast management module needs to query the related multicast routing table, determine whether multicast data streams with multicast addresses 13 and 14 have data sink reception in the cloudsets to which the port 0 and the port 1 of the terminal sub-control server B22 belong, if yes, determine that the multicast data streams with multicast addresses 1 and 2 need to be received through the port 1 of the terminal sub-control server B22, therefore, 4 multicast link control commands need to be sent to the slave terminal control server B22, the 1 st and 2 nd multicast link control commands require the slave terminal control server B22 to send the multicast data stream with the multicast address 1 from the port 1 to the port 0 and the port 1 with the new multicast address 13, and the 3 rd and 4 th multicast link control commands require the slave terminal control server B22 to send the multicast data stream with the multicast address 2 from the port 1 to the port 0 and the port 1 with the new multicast address 14.

After receiving the multicast link control command, the terminal sub-control server B22 configures the relevant multicast directing table, for example, after receiving the 1 st multicast link control command, queries the 1 st entry in the multicast directing table No. 2, finds that the directing mode is 0, and the new multicast address 13 is not the same as the old multicast address 1, so that the directing mode needs to be set to 2 (send a single replacement), and adds the multicast address 13 into the replacement address list, and then sends a multicast link control response to the main control server a 2.

After receiving the multicast link control response, the multicast management module of the main control server a2 updates the related multicast routing table, updates the multicast address fields (changed from 0 to 1 and 2, respectively) of the 2-way data source of the terminal sub-control server B22 before replacement in the data source information table, and then sends an add data sink response to the service processing module.

After receiving the add data sink response, the service processing module notifies each terminal through the service flow which multicast data stream and corresponding multicast address, for example, the information given to the terminal T21 is to receive the 1 st multicast data stream and the multicast address is 13, and does not receive other 2 nd multicast data streams, the information given to the terminal T22 is to receive the 1 st multicast data stream and the multicast address is 13, receive the 2 nd multicast data stream and the multicast address is 14, receive the 3 rd multicast data stream and the multicast address is 15.

4. Data stream transmission procedure 1

After the above-mentioned flow is completed, the 1 st data of the terminal T21 is sent to port 0 of the terminal sub-control server B21 through the multicast data stream with multicast address 1, then sent to port 1 of the terminal sub-control server B22 through port 1 of the terminal sub-control server B21, the terminal sub-control server B22 queries the multicast correlation table and then replaces the multicast address with 13, and then sent to the terminal T23 and the terminal T24 through port 0, and simultaneously sent to ports 1 of the terminal sub-control server B21 and the terminal sub-control server B23 through port 1, after the terminal sub-control server B21 and the terminal sub-control server B23 receive the multicast data stream, according to the internal table configuration, the multicast data stream is continuously sent to the terminal T21, the terminal T22, the terminal T25, and the terminal T26 under port 0, and the 1 st multicast data stream received by these terminals is the 1 st multicast data stream of the terminal T21.

Similarly, the 2 nd data of the terminal T21 is sent out through the multicast data stream with multicast address 2, then the multicast data stream with multicast address 14 is replaced by the terminal sub-control server B22, and finally received by the other 5 terminals, so that the 2 nd multicast data stream received by these terminals is the 2 nd multicast data stream of the terminal T21.

As for the 3 rd multicast data stream that other 5 terminals need to receive, since the 3 rd multicast data stream (multicast address is 15) from the terminal sub-control server B22, and the 3 rd multicast data stream of the terminal sub-control server B22 is in a state that it is not replaced by any multicast data stream at this time, and there is no other multicast address in the multicast direction table to replace the multicast data stream, the terminal will not receive any data packet of the multicast data stream.

5. Adding and deleting physical data sinks

The service processing module sends a request for adding data sink to the multicast management module, and requests the 2 nd data channel of the terminal T21 to receive data of the 2 nd multicast data stream from the terminal sub-control server B22, after receiving the request, the multicast management module performs processing according to the data sink adding process, and opens a transmission channel between the 2 nd data channel of the terminal sub-control server B22 and the terminal T21, the terminal sub-control server B22 is the terminal sub-control server as a data source, but the 2 nd multicast data stream of the terminal sub-control server B22 is already sent to the terminal sub-control server B21, so it is not necessary to send a multicast link control command to the terminal sub-control server B22 to open the transmission channel.

The service processing module sends 2 requests for deleting data sink to the multicast management module, and requires the 1 st and 2 nd data channels of the terminal T23 not to receive data any more, and after receiving the requests, the multicast management module processes according to the delete data sink process, and closes the transmission channel between the 1 st and 2 nd data channels of the terminal sub-control server B22 and the terminal T23, and since the data source is the terminal sub-control server, it needs to send a multicast link control command to the terminal sub-control server B22 to configure a multicast information table to stop sending multicast data streams.

The terminal sub-control server B22 configures after receiving the multicast link control command, and the configuration result is that the 0x23 bit of the entry with the multicast addresses 13 and 14 in the multicast information table No. 0 is set to 0, which indicates that the 2 channels of data are no longer sent to the terminal T23 from the port No. 0.

The service processing module sends 1 add data sink request to the multicast management module, and requests the 1 st data channel of the terminal T23 to receive the data of the 1 st multicast data stream from the terminal T21, and after receiving the request, the multicast management module performs processing according to an add data sink process, and opens a transmission channel between the 1 st data channel of the terminal T21 and the terminal T23.

6. Deleting virtual data sinks 1

The service processing module sends 2 requests for deleting data sink to the multicast management module, and requires the 1 st and 2 nd data channels of the terminal sub-control server B22 not to receive data any more, the multicast management module processes according to the delete data sink after receiving the requests, and closes the transmission channel between the 1 st and 2 nd data channels of the terminal T21 and the terminal sub-control server B22, and because the data sink is the terminal sub-control server, it needs to send a multicast link control command to the terminal sub-control server B22 to configure a multicast guide table to stop address replacement.

The multicast management module needs to query a related multicast routing table, determine whether the multicast data streams with multicast addresses 13 and 14 have data sink reception in the cloudsets belonging to port 0 and port 1 of B22, and determine whether the multicast data streams with multicast addresses 1 and 2 need to be received through port 1 of the terminal sub-control server B22, therefore, 4 multicast link control commands need to be sent to the slave terminal control server B22, the 1 st and 2 nd multicast link control commands require the slave terminal control server B22 to stop sending the multicast data stream with the multicast address 1 from port 1 to port 0 and port 1 with the new multicast address 13, and the 3 rd and 4 th multicast link control commands require the slave terminal control server B22 to stop sending the multicast data stream with the multicast address 2 from port 1 to port 0 and port 1 with the new multicast address 14.

After receiving the multicast link control command, the terminal sub-control server B22 configures the relevant multicast directing table, for example, after receiving the 1 st multicast link control command, queries the 1 st entry in the multicast directing table No. 2, finds that the directing mode is 2, deletes the replaced multicast address 13 from the replacement address list, and then does not have any multicast address in the list, so that the directing mode needs to be set to 0 (not sent), and then sends a multicast link control response to the main control server a 2.

After receiving the multicast link control response, the multicast management module of the main control server a2 updates the related multicast routing table, updates the multicast address field (changed from 1 and 2 to 0) of the 2-way data source of the terminal sub-control server B22 before replacement in the data source information table, and then sends an add data sink response to the service processing module.

7. Add virtual data sink 2

The service processing module sends 3 requests for adding data sinks to the multicast management module, and requests the 1 st data channel of the terminal sub-control server B22 to receive data (multicast address is 5) of the 1 st multicast data stream from the terminal T23, the 2 nd data channel receives data (multicast address is 6) of the 2 nd multicast data stream from the terminal T23, the 3 rd data sink receives data (multicast address is 2) of the 2 nd multicast data stream from the terminal T21, the multicast management module processes according to an add data sink procedure after receiving the request, opens a corresponding transmission channel, and since the data sink is the terminal sub-control server, it needs to send a multicast link control command to the terminal sub-control server B22 to configure a multicast direction table to start address replacement.

The terminal sub-control server B22 configures the multicast guide table after receiving the multicast link control command, and the configuration result is as follows:

the guide mode in the 5 th item of the multicast guide table No. 0 is 2, and the replacement address is 13;

the number 1 multicast guide table has the 5 th table entry with the guide mode of 2 and the replacement address of 13;

the 6 th item of the multicast guide table 0 has a guide mode of 2 and a replacement address of 14;

the 6 th item of the multicast guide table No. 1 has a guide mode of 2 and a replacement address of 14;

the 2 nd table entry of the multicast guide table No. 2 has a guide mode of 2 and a replacement address of 15;

the entry 2 of the multicast guide table No. 3 has a guide mode of 2 and a replacement address of 15.

After the above operations are completed, the service processing module notifies the terminal T21 and the terminal T23 of which multicast data streams and corresponding multicast addresses need to be received through the service flow, the data source state control command to the terminal T21 is to receive the 2 nd multicast data stream and the multicast address is 14, the data source state control command to the terminal T23 is to receive the 1 st multicast data stream and the multicast address is 1, and stop receiving the 2 nd multicast data stream.

8. Data stream transmission process 2

After the above flow is completed, the 1 st path of data of the terminal T21 is sent to the port 0 of the terminal sub-control server B21 through the multicast data stream whose multicast address is 1, then sent to the port 1 of the terminal sub-control server B22 through the port 1 of the terminal sub-control server B21, and the terminal sub-control server B22 is sent to the terminal T23 through the port 0, so that the 1 st path of multicast data stream received by the terminal T23 is the 1 st path of multicast data stream of the terminal T21.

Similarly, the 2 nd data of the terminal T21 is first sent out by the multicast data stream with multicast address 2, then the multicast data stream with multicast address 15 is replaced by the terminal sub-control server B22, and finally received by the other 5 terminals, so that the 3 rd multicast data stream received by the 5 terminals is the 1 st multicast data stream of the terminal T21.

The 1 st path of data of the terminal T23 is sent to port 0 of the terminal sub-control server B22 through a multicast data stream whose multicast address is 5, the terminal sub-control server B22 queries a multicast related table, then replaces the multicast address with 13, and sends the multicast address to the terminal T24 through port 0, and sends the multicast address to ports 1 of the terminal sub-control server B21 and the terminal sub-control server B23 through port 1, and the terminal sub-control server B21 and the terminal sub-control server B23 continue to send the multicast data to the terminal T21, the terminal T22, the terminal T25 and the terminal T26 under port 0 according to internal table configuration after receiving the multicast data, so that the 1 st path of multicast data stream received by these 5 terminals is the 1 st path of multicast data stream of the terminal T23.

The 2 nd path data of the terminal T23 is sent to port 0 of the terminal sub-control server B22 through the multicast data stream whose multicast address is 6, the terminal sub-control server B22 queries the multicast related table and then replaces the multicast address with 14, and then sends the multicast address to the terminal T24 through port 0, and simultaneously sends the multicast address to ports 1 of the terminal sub-control server B21 and the terminal sub-control server B23 through port 1, after the terminal sub-control server B21 and the terminal sub-control server B23 receive the multicast address, the multicast address is continuously sent to the terminal T21, the terminal T22, the terminal T25 and the terminal T26 under port 0 according to the internal table configuration, and then the 2 nd path multicast data stream received by these 5 terminals is the 2 nd path multicast data stream of the terminal T23.

Example five, configuring multicast links in multiple autonomous clouds (autonomous cloud interior no multicast address replacement)

As shown in fig. 27, it is assumed that the autonomous cloud C21 and the autonomous cloud C22 are located at the layer 2 of the autonomous network, the autonomous cloud C3 is located at the layer 3 of the autonomous network, the autonomous cloud C21 and the autonomous cloud C3 are connected by using the boundary router M21, and the autonomous cloud C22 and the autonomous cloud C3 are connected by using the boundary router M22.

In the autonomous cloud C3, the master server A3 and the border sub-control server B31 are connected to the same switching network, and the border sub-control server B31, the border router M21, and the border router M22 are connected to the same switching network.

In the autonomous cloud C21, the master control server a21, the border router M21, and the terminal sub-control server B21 are connected to the same switching network, and the terminal sub-control server B21, the terminal T21, and the terminal T22 are connected to the same switching network.

In the autonomous cloud C22, the master control server a22, the border router M22, and the terminal sub-control server B22 are connected to the same switching network, and the terminal sub-control server B22, the terminal T23, and the terminal T24 are connected to the same switching network.

It is assumed that in a certain service flow, 1-way multicast data stream is already created in the master server a21, and is the 1 st-way multicast data stream of the terminal T21, that is, the terminal T21 is a physical data source. The multicast address of the multicast data stream in the master server a21 is 1.

1. Adding a data sink for terminal T24

1.1, the master control server A22 processes the request for adding the data sink

The service processing module of the master control server a22 sends a request for adding a data sink to the multicast management module, where the global device number of the global data sink in the request is the global device number of the terminal T24, the channel number of the global data sink is 1, the global device number of the global data source is the global device number of the terminal T21, and the channel number of the global data source is 1 (that is, the 1 st data channel of the terminal T24 receives the 1 st multicast data stream of the terminal T21).

After receiving the data sink adding request, the multicast management module of the main control server a22 determines that the global data sink T24 belongs to the self-owned cloud (C22) and the type is a terminal, determines that the global data source T21 does not belong to the self-owned cloud (C22), and then searches for the data source index table by using the global device number and the channel number 1 of the terminal T21 to find that the multicast data stream does not exist.

The multicast management module of the main control server a22 calculates the boundary router in the global data source direction according to the global device number of T21, obtains that the local device number of the boundary router is 80022 (i.e., the boundary router M22), then queries the device static information table according to 80022 to obtain the local logical address of 0xf100, and then queries the 0xf100 entry of the autonomous cloud access table to obtain the global logical address of the main control server A3 as 4231-fb 00-0000-.

The multicast management module of the master server a22 sends a command of adding a foreign data sink to the master server A3, where the command includes the global device number and channel number 1 of the global data sink T24, and the global device number and channel number 1 of the global data source T21.

1.2, the master control server A3 processes the command of adding the allopatric data sink

After receiving the command of adding the allopatric data sink, the master control server a3 judges that the global data sink T24 and the global data source T21 do not belong to the autonomous cloud (C3), and then searches a data source index table by using the global device number and the channel number 1 of the global data source T21, and finds that the multicast data stream does not exist.

The multicast management module of the master server A3 calculates a border router in the global data source direction according to the global device number of the global data source T21, obtains that the local device number of the border router is 60021 (i.e., the border router M21), then queries the device static information table according to 60021 to obtain that the local logical address is 0x3121, and then queries the 0x3121 entry of the autonomous cloud access table to obtain that the global logical address of the master server a21 is 4231-fb 00-0000.

The multicast management module of the master control server A3 sends an add allopatric data sink command to the master control server a21, where the add allopatric data sink command includes the global device number and channel number 1 of the global data sink T24, and the global device number and channel number 1 of the global data source T21.

1.3, the master control server A21 processes the command of adding the allopatric data sink

After receiving the command of adding the remote data sink, the master control server a21 determines that the global data sink T24 does not belong to the local autonomous cloud (C21), the global data source T21 belongs to the local autonomous cloud (C21) and is of a terminal type, and then searches for a data source index table by using the global device number and the channel number 1 of the global data source T21 to find that a multicast data path exists, and the multicast address of the local autonomous cloud (C21) is 1.

The multicast management module of the master server a21 calculates a boundary router in the data sink direction according to the global device number of the global data sink T24, obtains that the local device number of the boundary router is 80021 (i.e. the boundary router M21), then calculates a local multicast link between the local data sink M21 and the local data source T21, assuming that the local multicast link is terminal T21 → terminal sub-control server B21 → boundary router M21, after querying the relevant multicast routing table, finds that it is necessary to send a data source state control command to the terminal T21, requires it to start sending a multicast data stream with multicast address 1, and also requires it to send a multicast link control command to the terminal sub-control server B21, requires it to send a multicast data stream with multicast address 1 from port No. 0 to port No. 1 with the same multicast address (configure a multicast direction table), and simultaneously starts sending the multicast data stream with multicast address 1 to a device with multicast port address 0xf1 (configure multicast direction table) (configuration) Information table).

After receiving the data source state control command, the terminal T21 starts to send a multicast data stream with a multicast address of 1, and then sends a data source state control response to the master server a 21.

After receiving the multicast link control command, the terminal sub-control server B21 locates the 1 st entry in the multicast guide table No. 1, changes its guide mode from 0 (no transmission) to 1 (transmission and no replacement), sets the 0xf1 bit in the 1 st entry of the multicast information table No. 1 to 1, and then sends a multicast link control response to the main control server a 21.

After receiving the data source state control response of the terminal T21 and the multicast link control response of the terminal sub-control server B21, the main control server a21 updates the related multicast routing table, then searches the autonomous cloud access table according to the local logical address of the border router M21, obtains the information of the main control server A3, sends a response of adding a remote data sink to the main control server A3, and adds the information of the global data sink and the global data source in the remote data sink response, and further includes a local multicast address 1.

1.4, the master control server A3 processes the response of adding the allopatric data sink

After receiving the response of adding the remote data sink, the master control server a3 determines that neither the global data sink T24 nor the global data source T21 belongs to the autonomous cloud (C3), and then calculates the boundary router in the data sink direction as M22 according to the global device number of the global data sink T24, and calculates the boundary router in the data source direction as M21 according to the global device number of the global data source T21.

The master control server a3 creates a new multicast data stream, and if the allocated local multicast address is 3, it needs to add an entry in the data source index table, where the data source global device number is 60031-,

The master server a3 sends a multicast link control command to the border router M21, requesting it to send the multicast data stream with multicast address 1 from port 0 to port 1 with new multicast address 3 (configure multicast direction table).

After receiving the multicast link control command, the border router M21 locates the 1 st entry in the multicast guide table No. 1, changes its guide mode from 0 (no transmission) to 2 (transmission and single address replacement), sets its replacement address to 3, and then sends a multicast link control response to the master server A3.

After receiving the multicast link control response from the boundary router M21, the master server a3 calculates a local multicast link between the local data sink M22 and the local data source M21, which satisfies the traffic demand, and assumes that the local multicast link is the boundary router M21 → the boundary router M22, after querying the related multicast routing table, finds that it is necessary to send a multicast link control command to the boundary router M21, and requests it to start sending the multicast data stream with multicast address 3 to the device with logical port address 0x22 from port No. 1 (configuring the multicast information table).

After receiving the multicast link control command, the border router M21 sets the 0x22 bit in the 3 rd entry of the multicast information table No. 1 to 1, and then sends a multicast link control response to the master server A3.

After receiving the multicast link control response of the border router M21, the master control server A3 updates the related multicast routing table, and since the global data sink does not belong to the local autonomous cloud (C3), searches the autonomous cloud access table according to the local logical address of the local data sink M22, obtains the information of the master control server a22, and sends a response of adding a remote data sink to the master control server a22, wherein the response of adding the remote data sink includes the information of the global data sink and the global data source, and also includes the local multicast address 3.

1.5, the master control server A22 processes the response of adding the allopatric data sink

After receiving the response of adding the remote data sink, the master control server a22 determines that the global data source T21 does not belong to the local autonomous cloud (C21), the global data sink T24 belongs to the local autonomous cloud (C21) and the device type is a terminal, and then calculates the boundary router in the global data source direction as M22 according to the global device number of the global data source T21.

The master control server a22 creates a new multicast data stream, and if the allocated local multicast address is 5, it needs to add an entry in the data source index table, where the data source global device number is 60031-.

The master server a22 sends a multicast link control command to the border router M22 requesting it to send the multicast data stream with multicast address 3 from port No. 1 to port No. 0 with new multicast address 5 (configure multicast direction table).

After receiving the multicast link control command, the border router M22 locates to item 3 in the multicast guide table No. 2, changes its guide mode from 0 (no transmission) to 2 (transmission and single address replacement), sets its replacement address to 5, and then sends a multicast link control response to the master server a 22.

After receiving the multicast link control response from the boundary router M22, the master control server a22 calculates a local multicast link between the local data sink T24 and the local data source M22, assuming that the local multicast link is the boundary router M22 → the terminal sub-control server B22 → the terminal T24, after querying the relevant multicast routing table, it is found that it is necessary to send a multicast link control command to the border router M22, and it is required to start sending the multicast data stream with multicast address 5 from port 0 to the device with logical port address 0x22 (configure multicast information table), and it is also required to send a multicast link control command to the slave terminal server B22, and it is required to send the multicast data stream with multicast address 5 from port 1 to port 0 with the same multicast address (configure multicast direction table), at the same time, the multicast data stream with multicast address 5 starts to be transmitted from port No. 0 to the device with logical port address 0x24 (configure multicast information table).

After receiving the multicast link control command, the border router M22 sets the 0x22 bit in the 5 th entry of the multicast information table No. 0 to 1, and then sends a multicast link control response to the master server a 22.

After receiving the multicast link control command, the terminal sub-control server B22 locates the 5 th entry in the multicast guide table No. 2, changes its guide mode from 0 (no transmission) to 1 (transmission and no replacement), sets the 0x24 bit in the 5 th entry of the multicast information table No. 0 to 1, and then sends a multicast link control response to the main control server a 22.

After receiving the multicast link control response of the border router M22 and the terminal sub-control server B22, the multicast management module of the main control server a22 updates the related multicast routing table, and since the global data is locally aggregated, it needs to send an add data aggregation response to the service processing module, and notifies that the 1 st data of the add terminal T24 is successfully aggregated, and its local multicast address is 5.

2 data stream transmission procedure

After the establishment of the multicast link is completed, the 1 st data of the terminal T21 is sent out through the multicast data stream with the multicast address of 1, and reaches the port 0 of the terminal sub-control server B21, and the terminal sub-control server B21 queries the multicast guide table and the multicast information table, and sends the multicast packet to the border router M21 from the port 1.

After receiving the multicast packet with the multicast address of 1 at port No. 0, the border router M21 queries its multicast guide table and multicast information table, replaces the multicast address of the multicast packet with 3, and sends the multicast packet to the border router M22 from port No. 1.

The boundary router M22 receives the multicast packet with the multicast address of 3 on port No. 1, inquires the multicast guide table and the multicast information table of itself, replaces the multicast address of the multicast packet with 5, and then sends the multicast packet to the terminal sub-control server B22 from port No. 0.

The terminal sub-control server B22 receives the multicast packet with the multicast address 5 at port No. 1, inquires its own multicast guide table and multicast information table, and then sends the multicast packet to the terminal T24 from port No. 0 with the same multicast address 5.

Thus, the terminal T24 receives the 1 st multicast data stream of the terminal T21 in its 1 st data channel.

3. Deleting data sink for terminal T24

3.1 Master Server A22 processing delete data sink request

The service processing module of the master server a22 sends a request for deleting data sink to the multicast management module, and requests the 1 st data channel of the terminal T24 not to receive the 1 st multicast data stream of the terminal T21 any more.

After receiving the request for deleting the data sink, the multicast management module of the master server a22 determines that the global data sink T24 belongs to the self-governing cloud (C22) and the device type is a terminal, determines that the global data source T21 does not belong to the self-governing cloud (C22), then searches the data source index table according to the global device number and the channel number of the terminal T21 to obtain a corresponding multicast address of 5, and then queries the 5 th entry of the data source information table to find that the data source state is valid, the data source type is a relay data source, the local data source device number is 80022 (i.e., a boundary router M22), and the like.

The multicast management module of the master server a22 can know that the local data sink (i.e. the terminal T24) exists and the local multicast link between the local data sink and the local data source (i.e. the boundary router M22) is the boundary router M22 → the terminal sub-control server B22 → the terminal T24 by looking up the multicast routing table, and then sends a multicast link control command to the boundary router M22 and the terminal sub-control server B22 to close the transmission channel of the multicast data stream with the multicast address of 5.

After receiving the multicast link control response of the border router M22 and the terminal sub-control server B22, the multicast management module of the master control server a22 updates the related multicast routing table, and since the global data source T21 does not belong to the self-governing cloud (C22), checks the multicast routing table, and finds that no data sink exists in the self-governing cloud (C22) to receive the multicast data stream, it is necessary to send a command to delete the remote data sink to the master control server A3 of the previous hop self-governing cloud (C3).

3.2, the master control server A3 processes the command of deleting the data sink at different places

After receiving the command of deleting the remote data sink, the multicast management module of the master server a3 determines that neither the global data source T21 nor the global data sink T24 belongs to the local autonomous cloud (C3), and then queries that the border router in the direction of the global data source T21 is M21 and the border router in the direction of the global data sink T24 is M22.

After querying the data source index table and the data source information table, the multicast management module of the master server a3 knows that the data stream of the global data source T21 has been sent to the self-governing cloud (C3), that the corresponding multicast address is 3, then searches the multicast routing table to obtain that the corresponding local multicast link is the boundary router M21 → the boundary router is M22, and then sends a multicast link control command to the boundary router M21 to close the transmission channel of the data stream with the multicast address of 3.

After receiving the multicast link control response of the border router M21, the multicast management module of the master control server A3 updates the relevant multicast routing table, and since the global data source T21 does not belong to the self-governing cloud (C3), checks the multicast routing table, finds that there is no data sink in the self-governing cloud (C3) to receive the multicast data stream, and needs to send a command to delete the foreign data sink to the master control server a21 of the previous-hop self-governing cloud (C21).

3.3, the master control server A21 processes the command of deleting the data sink at different places

After receiving the command of deleting the remote data sink, the multicast management module of the master server a21 determines that the global data source T21 belongs to the local autonomous cloud (C21) and the device type is a terminal, determines that the global data sink T24 does not belong to the local autonomous cloud (C21), and then queries that the border router in the direction of the global data sink T24 is M21.

After inquiring the data source index table and the data source information table, the multicast management module of the master server a21 knows that the multicast address of the global data source T21 in the self-managed cloud (C21) is 1, then searches the multicast routing table to obtain the corresponding local multicast link as terminal T21 → terminal sub-control server B21 → boundary router M21, and then sends a multicast link control command to the terminal sub-control server B21 to close the transmission channel of the multicast data stream with the multicast address of 1, and sends a data source state control command to the terminal T21 to stop sending the multicast data stream with the multicast address of 1.

After receiving the data source state control response of the terminal T21 and the multicast link control response of the terminal sub-control server B21, the multicast management module of the master control server a21 updates the related multicast routing table, and since the global data source T21 belongs to the local autonomous cloud (C21), it needs to send a delete remote data sink response to the master control server A3 of the next hop autonomous cloud (C3).

3.4, the main control server A3 processes the response of deleting the data exchange at different places

After receiving the response of deleting the remote data sink, the multicast management module of the master server a3 determines that neither the global data source T21 nor the global data sink T24 belongs to the local autonomous cloud (C3), and then queries that the border router in the direction of the global data source T21 is M21 and the border router in the direction of the global data sink T24 is M22.

After inquiring the data source index table and the data source information table, the multicast management module of the main control server a3 obtains that the local multicast address of the multicast data stream is 3 and the multicast address before replacement is 1, finds that no data in the self-governing cloud (C3) converges to receive the multicast data stream after checking the multicast routing table, and then sends a multicast link control command to the border router M21 in the direction of the global data source T21, and requires that the multicast link control command stop sending the multicast data stream with the multicast address 1 from the port 0 to the port 1 at the new multicast address 3 (configuring the multicast direction table).

After receiving the multicast link control command, the border router M21 locates to item 1 in the multicast guide table No. 1, changes its guide mode from 2 (send and single address replace) to 0 (no send), and then sends a multicast link control response to the master server A3.

After receiving the multicast link control response of the border router M21, the master control server a3 deletes the multicast data stream from the data source index table and the data source information table, and since the global data sink T24 does not belong to the local autonomous cloud (C3), it needs to send a delete foreign data sink response to the master control server a22 of the next hop autonomous cloud (C22).

3.5, the main control server A22 processes the response of deleting the allopatric data sink

After receiving the response of deleting the remote data sink, the multicast management module of the master control server a22 determines that the global data sink T24 belongs to the self-owned cloud (C22) and the device type is a terminal, determines that the global data source T21 does not belong to the self-owned cloud (C22), and then obtains a border router in the direction of the global data source T21 as M22.

After inquiring the data source index table and the data source information table, the multicast management module of the main control server a22 obtains that the local multicast address of the multicast data stream is 5 and the multicast address before replacement is 3, finds that no data in the self-governing cloud (C22) converges to receive the multicast data stream after checking the multicast routing table, and then sends a multicast link control command to the border router M22 in the direction of the global data source T21, and requires that the multicast link control command stop sending the multicast data stream with the multicast address of 3 from port 1 to port 0 at the new multicast address of 5 (configuring a multicast guide table).

After receiving the multicast link control command, the border router M22 locates to item 3 in the multicast guide table No. 2, changes its guide mode from 2 (send and single address replace) to 0 (not send), and then sends a multicast link control response to the master server a 22.

After receiving the multicast link control response of the border router M22, the multicast management module of the master server a22 deletes the data source from the data source index table and the data source information table, and since the global data sink T24 belongs to the self-managed cloud (C22), sends a delete data sink response to the service processing module, and notifies the service processing module that the deletion of the 1 st data channel of the terminal T24 is successful.

It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the embodiments are not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the embodiments. Further, those skilled in the art will also appreciate that the embodiments described in the specification are presently preferred and that no particular act is required of the embodiments of the application.

Referring to fig. 28, a structural block diagram of an autonomous network according to an embodiment of the present application is shown, where the autonomous network includes a plurality of autonomous clouds distributed in layers, each autonomous cloud includes a master control server 2810, a micro cloud server 2820, a terminal 2830, and a switching network 2840, the micro cloud server 2820 includes a boundary router 2821, a terminal sub-control server 2822, and a boundary sub-control server 2823, and two adjacent layers of autonomous clouds multiplex the same boundary router 2823 to connect;

in each autonomous cloud, a main control server 2810 and a micro cloud server 2820 are accessed to a switching network 2840, a terminal sub-control server 2822 and a terminal 2830 are accessed to another switching network 2840, and a boundary sub-control server 2823 and a boundary router 2821 are accessed to another switching network 2840; the master server 2810 includes:

A service request receiving module 28101, configured to receive a service request of a global data sink;

a global multicast link creation module 28102, configured to create a global multicast link from a global data source to the global data sink in an autonomous cloud to which the service request belongs according to the service request;

a service communication control module 28103, configured to control, in the autonomous cloud to which the service communication control module belongs, the global data source and the global data sink to perform service communication through the global multicast link control.

In an embodiment of the present application, the global multicast link creating module 28102 includes:

the data sink adding request receiving submodule is used for receiving a data sink adding request;

the first autonomous cloud attribution inquiring sub-module is used for inquiring an autonomous cloud to which a global data source and global data in an autonomous network belong according to the data sink adding request;

the first multicast data stream judgment sub-module is used for judging whether a multicast data stream corresponding to the data sink adding request exists in the autonomous cloud or not;

a first local source sink determining submodule, configured to determine, if the multicast data stream exists, a local data source and a local data sink in a local autonomous cloud according to the global data source and an autonomous cloud to which the global data sink belongs;

The first local multicast link establishing sub-module is used for establishing a local multicast link in the self-autonomous cloud, wherein the local multicast link is used for transmitting the multicast data stream from the local data source to the local data sink, so as to establish a global multicast link, and at least part of the multicast data stream is transmitted from the global data source to the global data sink.

In an embodiment of the present application, the global multicast link creation module 28102 further includes:

a first front hop autonomous cloud query submodule, configured to query, if the multicast data stream does not exist and the global data source does not belong to the autonomous cloud, an autonomous cloud that can be routed to the autonomous cloud to which the global data source belongs and that is connected to the autonomous cloud, and obtain a front hop autonomous cloud;

the first off-site data sink adding command sending submodule is used for sending an off-site data sink adding command to a main control server in the previous-hop autonomous cloud so as to inform the main control server in the previous-hop autonomous cloud to establish a global multicast link for transmitting at least part of multicast data streams from the global data source to the global data sink;

and the first remote data sink adding response waiting submodule is used for waiting for a remote data sink adding response sent by the master control server of the previous-hop autonomous cloud.

the data sink adding sub-module is used for receiving a data sink adding command;

the second autonomous cloud attribution query sub-module is used for querying autonomous clouds to which the global data source and the global data sink in the autonomous network belong according to the command of adding the remote data sink;

the second multicast data stream judgment sub-module is used for judging whether a multicast data stream corresponding to the remote data sink adding command exists in the autonomous cloud or not;

a second local source sink determining submodule, configured to determine, if the multicast data stream exists, a local data source and a local data sink in a local autonomous cloud according to the global data source and an autonomous cloud to which the global data sink belongs;

and the second local multicast link establishing submodule is used for establishing a local multicast link for transmitting the multicast data stream from the local data source to the local data sink in the autonomous cloud so as to establish a global multicast link for transmitting at least part of the multicast data stream from the global data source to the global data sink.

In an embodiment of the present application, the global multicast link creating module 28102 further includes:

The first back-hop autonomous cloud query submodule is used for querying an autonomous cloud which can be routed to the global data sink and is connected with the autonomous cloud to obtain a back-hop autonomous cloud;

and the first adding remote data sink response sending submodule is used for sending an adding remote data sink response to the master control server in the next-hop autonomous cloud so as to inform the master control server in the next-hop autonomous cloud of establishing a global multicast link for transmitting at least part of multicast data streams from the global data source to the global data sink.

a second front hop autonomous cloud query submodule, configured to query, if the multicast data stream does not exist and the global data source does not belong to the autonomous cloud, an autonomous cloud that can be routed to the autonomous cloud to which the global data source belongs and that is connected to the autonomous cloud, and obtain a front hop autonomous cloud;

the second remote data sink adding command sending submodule is used for sending a remote data sink adding command to the main control server in the previous-hop autonomous cloud so as to inform the main control server in the previous-hop autonomous cloud to establish a global multicast link for transmitting at least part of multicast data streams from the global data source to the global data sink;

And the second remote data sink adding response waiting submodule is used for waiting for the remote data sink adding response sent by the master control server of the previous-hop autonomous cloud.

In an embodiment of the present application, the global multicast link creation module 28102 includes:

the adding different-place data transfer response receiving submodule is used for receiving the adding different-place data transfer response;

a third autonomous cloud attribution query sub-module, configured to query, according to the added remote data sink response, an autonomous cloud to which a global data source and global data sink in an autonomous network belong;

a third multicast data stream judgment submodule, configured to judge whether a multicast data stream corresponding to the remote data sink addition response exists in the autonomous cloud;

a third local source sink determining submodule, configured to determine, if the multicast data stream does not exist, a local data source and a local data sink in a local autonomous cloud according to the global data source and an autonomous cloud to which the global data sink belongs;

and the third local multicast link establishing sub-module is used for establishing a local multicast link for transmitting the multicast data stream from the local data source to the local data sink in the autonomous cloud so as to establish a global multicast link for transmitting at least part of the multicast data stream from the global data source to the global data sink.

In an embodiment of the present application, if the multicast data stream does not exist, the global multicast link creation module 28102 further includes:

a first multicast data stream creating sub-module, configured to create a multicast data stream in the local data source;

and the local data source control module is used for sending a multicast link control command to the local data source so as to replace the multicast address of the multicast data stream from the previous hop autonomous cloud with the multicast address of the autonomous cloud.

In an embodiment of the present application, the global multicast link creation module 2812 further includes:

a second back-hop autonomous cloud query submodule, configured to query, if the global data sink does not belong to the autonomous cloud, an autonomous cloud that can be routed to the autonomous cloud to which the global data sink belongs and is connected to the autonomous cloud, and obtain a back-hop autonomous cloud;

and the second adding remote data sink response sending submodule is used for sending a adding remote data sink response to the master control server in the next-hop autonomous cloud so as to inform the master control server in the next-hop autonomous cloud to establish a global multicast link for transmitting at least part of multicast data streams from the global data source to the global data sink.

a data source creation request receiving submodule, which is used for receiving a data source creation request by a master control server in the autonomous cloud;

a fourth autonomous cloud attribution query sub-module, configured to query, according to the created data source request, an autonomous cloud to which a global data source belongs in an autonomous network;

a fourth multicast data stream judgment submodule, configured to judge whether a multicast data stream corresponding to the data source creation request exists in the autonomous cloud if the global data source belongs to the autonomous cloud;

a second multicast data stream creating submodule, configured to create a multicast data stream in the global data source if the multicast data stream does not exist;

and the created data source response generating submodule is used for generating a created data source response so as to inform the completion of the creation of the multicast data stream.

In one embodiment of the present application, the master server 2810 further includes:

a global multicast link closing module 28104, configured to close a global multicast link from the global data source to the global data sink in an autonomous cloud to which the service communication belongs when the service communication is ended.

In an embodiment of the present application, the global multicast link shutdown module 28104 includes:

The data sink deletion request receiving submodule is used for receiving a data sink deletion request by a master control server in the autonomous cloud;

a fifth autonomous cloud attribution query sub-module, configured to query, according to the data sink deletion request, an autonomous cloud to which a global data source and a global data sink in an autonomous network belong;

a fifth multicast data stream judgment sub-module, configured to judge whether a multicast data stream corresponding to the data sink deletion request exists in the self-managing cloud;

a fourth local source sink determining submodule, configured to determine, if the multicast data stream exists, a local data source and a local data sink in a local autonomous cloud according to the global data source and the autonomous cloud to which the global data sink belongs;

the first local multicast link closing submodule is used for closing a local multicast link of the multicast data stream transmitted from the local data source to the local data sink in the autonomous cloud so as to close a global multicast link of at least part of the multicast data stream transmitted from the global data source to the global data sink.

In an embodiment of the present application, the global multicast link shutdown module 28104 further includes:

a first data sink judgment submodule, configured to judge whether there is another data sink in the autonomous cloud except the local data sink to receive the multicast data stream if the global data source does not belong to the autonomous cloud; if yes, calling a deleted data sink response generation sub-module, and if not, calling a third previous hop autonomous cloud query sub-module;

A deleted data sink response generation submodule, configured to generate a deleted data sink response to notify that the closing of the global multicast link is completed;

a third front hop autonomous cloud query submodule, configured to query an autonomous cloud that can be routed to the global data source and is connected to the autonomous cloud, and obtain a front hop autonomous cloud;

a third adding different-place data sink command sending submodule, configured to send a delete different-place data sink command to a master control server in the previous-hop autonomous cloud, so as to notify the master control server in the previous-hop autonomous cloud to close a global multicast link, where at least part of the multicast data stream is transmitted from the global data source to the global data sink, in the previous-hop autonomous cloud;

and a third step of adding a remote data sink response waiting submodule for waiting for a remote data sink deletion response sent by the master control server of the previous-hop autonomous cloud.

the data sink command receiving submodule for deleting the different place is used for receiving a data sink command for deleting the different place;

a sixth autonomous cloud attribution query sub-module, configured to query, according to the remote data sink deletion command, an autonomous cloud to which a global data source and global data sink in an autonomous network belong;

A sixth multicast data stream judgment sub-module, configured to judge whether a multicast data stream corresponding to the remote data sink deletion command exists in the self-managing cloud;

a fifth local source sink determining submodule, configured to determine, if the multicast data stream exists, a local data source and a local data sink in a local autonomous cloud according to the global data source and an autonomous cloud to which the global data sink belongs;

and the second local multicast link closing submodule is used for closing the local multicast link of the multicast data stream transmitted from the local data source to the local data sink in the autonomous cloud so as to close the global multicast link of at least part of the multicast data stream transmitted from the global data source to the global data sink.

a third back-hop autonomous cloud query submodule, configured to query, if the global data source belongs to the autonomous cloud, an autonomous cloud that can be routed to the autonomous cloud to which the global data is converged and is connected to the autonomous cloud, and obtain a back-hop autonomous cloud;

and a third step of adding a remote data sink response sending submodule for sending a remote data sink deletion response to the master control server in the next-hop autonomous cloud so as to inform the master control server in the next-hop autonomous cloud of closing the multicast data stream in the next-hop autonomous cloud.

a second data sink judgment submodule, configured to judge whether there is another data sink in the autonomous cloud, except the local data sink, to receive the multicast data stream if the global data source belongs to another autonomous cloud; if yes, a fourth back-jump autonomous cloud query submodule is called, and if not, a fourth front-jump autonomous cloud query submodule is called;

a fourth back-hop autonomous cloud query sub-module, configured to query an autonomous cloud that can be routed to the autonomous cloud to which the global data is converged and is connected to the autonomous cloud, and obtain a back-hop autonomous cloud;

a fourth adding non-local data sink response sending submodule is used for sending a delete non-local data sink response to the main control server in the next-hop autonomous cloud so as to inform the main control server in the next-hop autonomous cloud of closing the multicast data stream in the next-hop autonomous cloud;

a fourth front hop autonomous cloud query submodule, configured to query an autonomous cloud that can be routed to the global data source and is connected to the autonomous cloud, and obtain a front hop autonomous cloud;

a fourth off-site data sink adding command sending submodule, configured to send a command to delete off-site data sinks to a master control server in the previous-hop autonomous cloud, so as to notify the master control server in the previous-hop autonomous cloud to close a global multicast link, where at least part of the multicast data streams are transmitted from the global data source to the global data sink, in the previous-hop autonomous cloud;

And a fourth step of adding a remote data sink response waiting submodule for waiting for a remote data sink deletion response sent by the master control server of the previous-hop autonomous cloud.

the deleted remote data transfer response receiving submodule is used for receiving a deleted remote data transfer response;

a seventh autonomous cloud attribution query sub-module, configured to respond to query, according to the deleted remote data sink, an autonomous cloud to which a global data source belongs in an autonomous network;

a seventh multicast data stream judgment submodule, configured to judge whether a multicast data stream corresponding to the deleted remote data sink response exists in the self-governing cloud;

a third data sink judgment submodule, configured to judge whether there is a data sink in the autonomous cloud to receive the multicast data stream if the multicast data stream exists; if yes, calling a delete remote data sink response ignoring sub-module, and if not, calling a local source end determining sub-module;

the remote data sink response deleting ignoring sub-module is used for ignoring the remote data sink response deleting module;

the local source end determining submodule is used for determining a local data source in the local autonomous cloud according to the autonomous cloud to which the global data source belongs;

And the multicast data stream closing submodule is used for closing the multicast data stream in the local data source.

In an embodiment of the present application, the multicast data stream closing sub-module 28104 includes:

an address replacement stopping unit, configured to send a multicast link control command to the local data source, so as to stop replacing the multicast data stream with the multicast address of the local autonomous cloud from the multicast address of the previous hop autonomous cloud;

a multicast link control response receiving unit, configured to receive a multicast link control response sent by the local data source;

and the multicast data stream deleting unit is used for deleting the multicast data stream.

the local sink determining submodule is used for responding and inquiring the autonomous cloud to which the global data in the autonomous network belongs according to the deleted remote data sink;

a fifth back-hop autonomous cloud query submodule, configured to query, if the global data sink does not belong to the autonomous cloud, an autonomous cloud that can be routed to the autonomous cloud to which the global data sink belongs and is connected to the autonomous cloud, and obtain a back-hop autonomous cloud;

and a fifth adding different-place data sink response sending submodule for sending a delete different-place data sink response to the main control server in the next-hop autonomous cloud so as to inform the main control server in the next-hop autonomous cloud of closing the multicast data stream.

the data source destroying request receiving submodule is used for receiving a data source destroying request;

an eighth autonomous cloud attribution query submodule, configured to query, according to the destroy data source request, an autonomous cloud to which a global data source in an autonomous network belongs;

an eighth multicast data stream judgment submodule, configured to judge whether a multicast data stream corresponding to the data source creation request exists in the autonomous cloud if the global data source belongs to the autonomous cloud;

a fourth data sink judgment submodule, configured to judge whether there is a data sink in the autonomous cloud to receive the multicast data stream if the multicast data stream exists; if not, calling a multicast data stream destroying submodule;

the multicast data stream destroying submodule is used for destroying the multicast data stream in the global data source;

and the destroyed data source response generating submodule is used for generating a destroyed data source response so as to inform that the multicast data stream is destroyed.

the micro cloud server control access module 28105 is used for controlling the micro cloud server to access the master control server;

The terminal sub-control server 2822 includes:

a terminal control access module 28221, configured to control a terminal to access a terminal sub-control server;

the border branch control server 2823 includes:

and the border router control access module 28231 is used for controlling the border router to access the border sub-control server.

In one embodiment of the present application, the micro cloud server control access module 28105 includes:

the first equipment connection command sending submodule is used for sending an equipment connection command to the micro cloud server;

the first equipment connection response receiving submodule is used for receiving an equipment connection response sent by the micro cloud server after the micro cloud server verifies that the equipment connection command belongs to the micro cloud server;

the first equipment network access command sending submodule is used for sending an equipment network access command to the micro cloud server so as to transmit network access parameters;

and the first equipment network access response receiving submodule is used for receiving the equipment network access response sent by the micro cloud server after the network access parameters are configured.

In an embodiment of the present application, the micro cloud server control access module 28105 further includes:

the first equipment authentication command sending submodule is used for sending an equipment authentication command to the micro cloud server so as to transmit authentication parameters;

The first equipment authentication response receiving submodule is used for receiving an equipment authentication response sent by the micro cloud server after the micro cloud server executes authentication operation by using the authentication parameters;

the first authentication judgment sub-module is used for judging whether the micro cloud server is successfully authenticated; and if so, calling the first equipment network access command sending submodule.

the first equipment heartbeat command sending submodule is used for sending an equipment heartbeat command to the micro cloud server;

and the first device heartbeat response receiving submodule is used for receiving the device heartbeat response sent by the micro cloud server.

In an embodiment of the present application, the device heartbeat response includes upper layer device online information and lower layer device online information;

if the micro cloud server is a boundary router, the online information of the upper-layer equipment indicates whether the boundary router is connected to a boundary sub-control server in the upper-layer autonomous cloud;

if the micro cloud server is a terminal sub-control server, the lower-layer equipment online information represents whether a terminal accessed to the terminal sub-control server is online or not;

and if the micro cloud server is the boundary sub-control server, the lower-layer equipment online information represents whether a boundary router accessed to the boundary sub-control server is online or not.

and the first state setting submodule is used for setting the access state between the autonomous cloud where the main control server is located and the last autonomous cloud where the boundary router is located as a non-access state if the online information of the upper-layer equipment indicates that the boundary router is not accessed to the boundary sub-control server in the last autonomous cloud.

and the second state setting submodule is used for setting the access state between the autonomous cloud where the main control server is located and the next autonomous cloud where the boundary router is located as an unaccessed state if the online information of the lower-layer equipment is that the boundary router accessing the boundary sub-control server is not online.

and the third state setting submodule is used for setting the micro cloud server to be in a non-network-access state if the equipment heartbeat response of the micro cloud server is not received within the preset time period.

The fourth state setting submodule is used for setting the access state between the autonomous cloud where the main control server is located and the last autonomous cloud where the boundary router is located as the unaccessed state when the micro cloud server is the boundary router;

and the fifth state setting submodule is used for setting the access state between the autonomous cloud where the main control server is located and the next autonomous cloud where the boundary router accessing the boundary sub-control server is located as the non-access state when the micro-cloud server is the boundary sub-control server.

the first exchange node information configuration command sending submodule is used for sending an exchange node information configuration command to a newly-accessed micro cloud server so as to transmit physical port information of the accessed micro cloud server;

and the first exchange node information configuration response receiving submodule is used for receiving an exchange node information configuration response sent after the micro cloud server which just enters the network configures the physical port information of the micro cloud server which has already entered the network.

the second exchange node information configuration command sending submodule is used for sending an exchange node information configuration command to the connected micro cloud server so as to transmit the physical port information of the newly connected micro cloud server;

And the second exchange node information configuration response receiving submodule is used for receiving an exchange node information configuration response sent after the micro cloud server which has accessed the network configures the physical port information of the micro cloud server which has just accessed the network.

a third exchange node information configuration command sending submodule, configured to send an exchange node information configuration command to a micro cloud server that has already accessed the network, so as to transmit physical port information of the micro cloud server that has just exited the network;

and the third exchange node information configuration response receiving submodule is used for receiving an exchange node information configuration response sent by the micro cloud server which has accessed the network after deleting the physical port information of the micro cloud server which has just exited the network.

the first lower-layer equipment information configuration command sending submodule is used for sending a lower-layer equipment information configuration command to the terminal sub-control server so as to transmit the registration information of the terminal accessed to the terminal sub-control server;

and the first lower-layer equipment information configuration response receiving submodule is used for receiving a lower-layer equipment information configuration response sent after the terminal sub-control server configures the registration information of the terminal.

the second lower-layer equipment information configuration command sending submodule is used for sending a lower-layer equipment information configuration command to the terminal sub-control server when the registration information of the terminal changes so as to transmit the changed registration information of the terminal;

and the second lower-layer equipment information configuration response receiving submodule is used for receiving a lower-layer equipment information configuration response sent after the terminal sub-control server configures the changed registration information of the terminal.

the third lower-layer equipment information configuration command sending submodule is used for sending a lower-layer equipment information configuration command to the boundary sub-control server so as to transmit the registration information of the boundary router accessed to the boundary sub-control server;

and the third lower-layer equipment information configuration response receiving submodule is used for receiving a lower-layer equipment information configuration response sent by the boundary sub-control server after the registration information of the boundary router is configured.

a fourth lower layer device information configuration command sending submodule, configured to send a lower layer device information configuration command to the boundary sub-control server when the registration information of the boundary router changes, so as to transmit the changed registration information of the boundary router;

And the fourth lower-layer equipment information configuration response receiving submodule is used for receiving a lower-layer equipment information configuration response sent after the boundary sub-control server configures the changed registration information of the boundary router.

In one embodiment of the present application, the terminal control access module 28221 includes:

the second equipment connection command sending submodule is used for sending an equipment connection command to the terminal;

the second equipment connection response receiving submodule is used for receiving an equipment connection response sent by the terminal when the equipment connection command is verified to belong to the second equipment connection response receiving submodule;

the second equipment network access command sending submodule is used for sending an equipment network access command to the terminal so as to transmit network access parameters;

and the second equipment network access response receiving submodule is used for receiving the equipment network access response sent by the terminal after the network access parameters are configured.

In one embodiment of the present application, the terminal control access module 28221 further includes:

the second equipment authentication command sending submodule is used for sending an equipment authentication command to the terminal so as to transmit authentication parameters;

the second equipment authentication response receiving submodule is used for receiving the equipment authentication response sent by the terminal after the terminal executes the authentication operation by using the authentication parameters;

The second authentication judgment sub-module is used for judging whether the terminal is successfully authenticated; and if so, executing the second device connection command calling sending submodule.

the second equipment heartbeat command sending submodule is used for sending an equipment heartbeat command to the terminal;

and the second equipment heartbeat response receiving submodule is used for receiving the equipment heartbeat response sent by the terminal.

and the sixth state setting submodule is used for setting the terminal to be in a non-network-access state if the heartbeat response of the terminal is not received within the preset time period.

In one embodiment of the present application, the border router control access module 28231 includes:

a third device connection command sending submodule, configured to send a device connection command to the border router;

a third device connection response receiving submodule, configured to receive a device connection response sent by the boundary router when it is verified that the device connection command belongs to the third device connection response receiving submodule;

the third device network access command sending submodule is used for sending a device network access command to the boundary router so as to transmit network access parameters;

And the third device network access response receiving submodule is used for receiving the device network access response sent by the boundary router after the network access parameters are configured.

In one embodiment of the present application, the border router control access module 28231 further includes:

the third equipment authentication command sending submodule is used for sending an equipment authentication command to the boundary router so as to transmit authentication parameters;

the third equipment authentication response receiving submodule is used for receiving an equipment authentication response sent by the boundary router after the boundary router uses the authentication parameters to execute authentication operation;

the third authentication judgment sub-module is used for judging whether the boundary router is successfully authenticated; if yes, the third equipment network access command sending submodule is called.

In one embodiment of the present application, the border router control access module 28231 further comprises:

a third device heartbeat command sending submodule, configured to send a device heartbeat command to the border router;

and the third device heartbeat response receiving submodule is used for receiving the device heartbeat response sent by the boundary router.

and the seventh state setting submodule is used for setting the border router to be in a non-network-accessing state if the equipment heartbeat response of the border router is not received after the preset time period is exceeded.

a fourth switching node information configuration command sending submodule, configured to send a switching node information configuration command to a boundary router that has just entered the network, so as to transmit physical port information of the boundary router that has entered the network;

and the fourth switching node information configuration response receiving submodule is used for receiving the switching node information configuration response sent after the boundary router which just enters the network configures the physical port information of the boundary router which has already entered the network.

a fifth switching node information configuration command sending submodule, configured to send a switching node information configuration command to a boundary router that has already accessed the network, so as to transmit physical port information of the boundary router that has just accessed the network;

and the fifth switching node information configuration response receiving submodule is used for receiving the switching node information configuration response sent after the boundary router which has accessed the network configures the physical port information of the boundary router which has just accessed the network.

A sixth switching node information configuration command sending submodule, configured to send a switching node information configuration command to a border router that has already entered a network, so as to transmit physical port information of a border router that has just exited the network;

and the sixth switching node information configuration response receiving submodule is used for receiving the switching node information configuration response sent by the border router which has accessed the network after deleting the physical port information of the border router which has just exited the network.

an upper autonomous cloud access control module 28106, configured to control an access of an upper autonomous cloud to the autonomous cloud;

and a lower autonomous cloud access control module 28107, configured to control access of a next autonomous cloud to the autonomous cloud.

In an embodiment of the present application, the upper autonomous cloud access control module 28106 includes:

the first autonomous cloud network access configuration command receiving submodule is used for receiving an autonomous cloud network access configuration command of a boundary router multiplexed with the upper layer of autonomous cloud so as to transmit network parameters of the upper layer of autonomous cloud;

the first autonomous cloud network access configuration command checking submodule is used for checking whether the autonomous cloud network access configuration command belongs to the first autonomous cloud network access configuration command; if yes, calling an upper-layer autonomous network access configuration submodule;

And the upper layer autonomous network access configuration submodule is used for performing network access configuration on the upper layer autonomous cloud according to the network parameters of the upper layer autonomous cloud and sending an autonomous cloud network access configuration response to the boundary router.

In an embodiment of the present application, the lower autonomous cloud access control module 28107 includes:

the second autonomous cloud network access configuration command receiving submodule is used for receiving an autonomous cloud network access configuration command of a boundary router multiplexed with the next layer of autonomous cloud so as to transmit network parameters of the next layer of autonomous cloud;

the second autonomous cloud network access configuration command checking submodule is used for checking whether the autonomous cloud network access configuration command belongs to the second autonomous cloud network access configuration command checking submodule; if yes, calling a lower layer autonomous network access configuration submodule;

and the lower autonomous network access configuration submodule is used for performing network access configuration on the next autonomous cloud according to the network parameters of the next autonomous cloud and sending an autonomous cloud network access configuration response to the boundary router.

For the embodiment of the autonomous network, since it is basically similar to the method embodiment, the description is simple, and for relevant points, refer to part of the description of the method embodiment.

The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

As will be appreciated by one of skill in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present application have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the true scope of the embodiments of the application.

Finally, it should also be noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.

The service communication method of an autonomous network and the autonomous network provided by the present application are introduced in detail above, and a specific example is applied in the present application to explain the principle and the implementation of the present application, and the description of the above embodiment is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A service communication method of an autonomous network is characterized in that the autonomous network comprises a plurality of autonomous clouds distributed according to layers, each autonomous cloud comprises a main control server, a micro cloud server, a terminal and a switching network, the micro cloud server comprises a boundary router, a terminal sub-control server and a boundary sub-control server, and two adjacent layers of autonomous clouds are connected by multiplexing the same boundary router;

in each autonomous cloud, a main control server and a micro cloud server are connected into a switching network to form a main control micro cloud, a terminal sub-control server and a terminal are connected into another switching network to form a terminal sub-control micro cloud, and a boundary sub-control server and a boundary router are connected into another switching network to form a boundary sub-control micro cloud; the connection mode of the equipment in the master control micro cloud, the terminal sub-control micro cloud and the terminal sub-control micro cloud at least comprises one of tree type, star type and full connection type; the method comprises the following steps:

a master control server in a certain autonomous cloud receives a service request of a global data sink; the global data sink is a terminal, a terminal sub-control server or a boundary sub-control server;

2. The method according to claim 1, wherein the creating, by a master server in one or more autonomous clouds, a global multicast link from a global data source to the global data sink in the autonomous cloud to which the service request belongs according to the service request comprises:

a master control server in the autonomous cloud receives a request for adding data sink;

inquiring an autonomous cloud to which a global data source and global data in an autonomous network belong according to the data sink adding request;

judging whether a multicast data stream corresponding to the data sink adding request exists in the autonomous cloud or not;

if the multicast data stream exists, determining a local data source and a local data sink in the autonomous cloud according to the global data source and the autonomous cloud to which the global data sink belongs; the local data sink is a terminal, a terminal sub-control server, a boundary sub-control server or a boundary router;

and establishing a local multicast link for transmitting the multicast data stream from the local data source to the local data sink in the autonomous cloud so as to establish a global multicast link for transmitting at least part of the multicast data stream from the global data source to the global data sink.

3. The method according to claim 2, wherein the master server in the one or more autonomous clouds creates a global multicast link from a global data source to the global data sink in the autonomous cloud to which the service request belongs according to the service request, and further comprising:

if the multicast data stream does not exist and the global data source does not belong to the autonomous cloud, inquiring the autonomous cloud which can be routed to the autonomous cloud to which the global data source belongs and is connected with the autonomous cloud to obtain a previous hop autonomous cloud;

sending a command of adding a remote data sink to a master control server in a previous-hop autonomous cloud to inform the master control server in the previous-hop autonomous cloud to establish a global multicast link for transmitting at least part of multicast data streams from a global data source to the global data sink in the previous-hop autonomous cloud;

4. The method according to claim 1, wherein the creating, by a master server in one or more autonomous clouds, a global multicast link from a global data source to the global data sink in the autonomous cloud to which the service request belongs according to the service request comprises:

The method comprises the steps that a main control server in the autonomy cloud receives a command of adding a remote data sink;

querying an autonomous cloud to which a global data source and global data sink belong in an autonomous network according to the command of adding the allopatric data sink;

judging whether a multicast data stream corresponding to the command of adding the remote data sink exists in the autonomous cloud;

5. The method according to claim 4, wherein the master server in the one or more autonomous clouds creates a global multicast link from a global data source to the global data sink in the autonomous cloud to which the service request belongs according to the service request, and further comprising:

Inquiring an autonomous cloud which can be routed to the global data sink and is connected with the autonomous cloud to obtain a next hop autonomous cloud;

and sending a response of adding the remote data sink to a master control server in the next-hop autonomous cloud to inform the master control server in the next-hop autonomous cloud to establish a global multicast link for transmitting at least part of the multicast data stream from the global data source to the global data sink in the next-hop autonomous cloud.

6. The method according to claim 4, wherein the master server in the one or more autonomous clouds creates a global multicast link from a global data source to the global data sink in the autonomous cloud to which the service request belongs according to the service request, and further comprising:

7. The method according to claim 1, wherein the creating, by a master server in one or more autonomous clouds, a global multicast link from a global data source to the global data sink in the autonomous cloud to which the service request belongs according to the service request comprises:

the master control server in the autonomous cloud receives a response of adding the remote data sink;

inquiring an autonomous cloud to which a global data source and global data sink belong in an autonomous network according to the response of the adding of the allopatric data sink;

judging whether a multicast data stream corresponding to the remote data sink adding response exists in the autonomous cloud;

if the multicast data stream does not exist, determining a local data source and a local data sink in the autonomous cloud according to the global data source and the autonomous cloud to which the global data sink belongs; the local data sink is a terminal, a terminal sub-control server, a boundary sub-control server or a boundary router;

8. The method according to claim 7, wherein if the multicast data stream does not exist, the master server in one or more autonomous clouds creates a global multicast link from a global data source to the global data sink in the autonomous cloud to which the service request belongs according to the service request, further comprising:

creating a multicast data stream in the local data source;

and sending a multicast link control command to the local data source so as to replace the multicast address of the multicast data stream from the previous hop autonomous cloud with the multicast address of the local autonomous cloud.

9. The method according to claim 7, wherein a master server in the one or more autonomous clouds creates a global multicast link from a global data source to the global data sink in the autonomous cloud to which the service request belongs according to the service request, and further comprising:

if the global data sink does not belong to the autonomous cloud, inquiring the autonomous cloud which can be routed to the autonomous cloud to which the global data sink belongs and is connected with the autonomous cloud to obtain the next hop of autonomous cloud;

10. The method according to claim 1, wherein the creating, by a master server in one or more autonomous clouds, a global multicast link from a global data source to the global data sink in the autonomous cloud to which the service request belongs according to the service request comprises:

a master control server in the autonomy cloud receives a request for creating a data source;

inquiring the autonomous cloud to which the global data source belongs in the autonomous network according to the data source creating request;

if the global data source belongs to the self-governing cloud, judging whether a multicast data stream corresponding to the data source establishing request exists in the self-governing cloud;

if the multicast data stream does not exist, creating a multicast data stream in the global data source;

and generating a create data source response to inform the completion of creating the multicast data stream.

11. The method of any one of claims 1-10, further comprising:

and when the service communication is finished, the master control server in one or more autonomous clouds closes a global multicast link from the global data source to the global data sink in the autonomous cloud to which the master control server belongs.

12. The method according to claim 11, wherein when the service communication is finished, the master server in the one or more autonomous clouds closes a global multicast link from the global data source to the global data sink in the autonomous cloud to which the master server belongs, and the method includes:

A master control server in the autonomous cloud receives a request for deleting data sink;

querying an autonomous cloud to which a global data source and global data sink belong in an autonomous network according to the data sink deletion request;

judging whether a multicast data stream corresponding to the data sink deleting request exists in the autonomous cloud or not;

and closing a local multicast link of the multicast data stream transmitted from the local data source to the local data sink in the autonomous cloud, so as to close a global multicast link of at least part of the multicast data stream transmitted from the global data source to the global data sink.

13. The method according to claim 12, wherein the master server in the one or more autonomous clouds closes a global multicast link from the global data source to the global data sink in the autonomous cloud to which the master server belongs when the service communication is ended, and further comprising:

If the global data source does not belong to the autonomous cloud, judging whether other data sinks except the local data sink exist in the autonomous cloud or not to receive the multicast data stream;

if so, generating a data sink deleting response to inform the completion of closing the global multicast link;

if not, inquiring an autonomous cloud which can be routed to the autonomous cloud to which the global data source belongs and is connected with the autonomous cloud to obtain a previous hop autonomous cloud;

sending a command of deleting the remote data sink to a master control server in the previous-hop autonomous cloud to inform the master control server in the previous-hop autonomous cloud of closing a global multicast link for transmitting at least part of multicast data streams from the global data source to the global data sink in the previous-hop autonomous cloud;

14. The method according to claim 11, wherein when the service communication is finished, the master server in the one or more autonomous clouds closes a global multicast link from the global data source to the global data sink in the autonomous cloud to which the master server belongs, and the method includes:

the method comprises the steps that a main control server in the autonomy cloud receives a command of deleting a remote data sink;

Inquiring an autonomous cloud to which a global data source and global data sink belong in an autonomous network according to the command of deleting the allopatric data sink;

judging whether a multicast data stream corresponding to the remote data sink deleting command exists in the autonomous cloud;

15. The method according to claim 14, wherein the master server in the one or more autonomous clouds closes a global multicast link from the global data source to the global data sink in the autonomous cloud to which the master server belongs when the service communication is ended, and further comprising:

if the global data source belongs to the autonomous cloud, inquiring the autonomous cloud which can be routed to the autonomous cloud to which the global data is converged and is connected with the autonomous cloud, and obtaining the next hop of autonomous cloud;

16. The method according to claim 14, wherein the master server in the one or more autonomous clouds closes a global multicast link from the global data source to the global data sink in the autonomous cloud to which the master server belongs when the service communication is ended, and further comprising:

if the global data source belongs to other self-governing clouds, judging whether other data sinks except the local data sink exist in the self-governing cloud or not to receive the multicast data stream;

if yes, inquiring an autonomous cloud which can be routed to the global data sink and is connected with the autonomous cloud to obtain a next hop autonomous cloud;

sending a remote data sink deletion response to a master control server in the next-hop autonomous cloud to inform the master control server in the next-hop autonomous cloud of closing the multicast data stream in the next-hop autonomous cloud;

17. The method according to claim 11, wherein the closing, by the master server in the one or more autonomous clouds, a global multicast link from the global data source to the global data sink in the autonomous cloud to which the master server belongs when the service communication is finished comprises:

the main control server in the autonomy cloud receives a response of deleting the remote data sink;

responding and inquiring an autonomous cloud to which a global data source belongs in an autonomous network according to the deleted allopatric data sink;

judging whether a multicast data stream corresponding to the deleted allopatric data sink response exists in the autonomous cloud or not;

if the multicast data stream exists, judging whether a data sink exists in the autonomous cloud or not to receive the multicast data stream;

if yes, ignoring the remote data sink deleting response;

If not, determining a local data source in the local autonomous cloud according to the autonomous cloud to which the global data source belongs;

and closing the multicast data stream in the local data source.

18. The method of claim 17, wherein closing the multicast data stream in the local data source comprises:

sending a multicast link control command to the local data source to stop replacing the multicast data stream with the multicast address of the self-control cloud from the previous hop;

receiving a multicast link control response sent by the local data source;

and deleting the multicast data stream.

19. The method according to claim 17, wherein the master server in the one or more autonomous clouds, when the service communication is finished, closes a global multicast link from the global data source to the global data sink in the autonomous cloud to which the master server belongs, and further comprising:

responding and inquiring the autonomous cloud to which the global data in the autonomous network belongs according to the deleted remote data sink;

20. The method according to claim 11, wherein the master server in the one or more autonomous clouds closes a global multicast link from the global data source to the global data sink in the autonomous cloud to which the master server belongs when the service communication is ended, and further comprising:

a main control server in the autonomous cloud receives a data source destroying request;

inquiring the autonomous cloud to which the global data source belongs in the autonomous network according to the destroy data source request;

if the global data source belongs to the autonomous cloud, judging whether a multicast data stream corresponding to a data source creating request exists in the autonomous cloud;

if not, destroying the multicast data stream in the global data source;

and generating a data source destroying response to inform the completion of destroying the multicast data stream.

21. The method of claim 1, further comprising:

The main control server in each autonomous cloud controls the micro cloud server to access the main control server;

the terminal sub-control server in each autonomous cloud controls the terminal to access the terminal sub-control server;

and the boundary sub-control server in each autonomous cloud controls the boundary router to access the boundary sub-control server.

22. The method according to claim 21, wherein the controlling the micro cloud servers to access the master server by the master server in each autonomous cloud comprises:

the master control server sends a device connection command to the micro cloud server;

the main control server receives an equipment connection response sent by the micro cloud server after the micro cloud server verifies that the equipment connection command belongs to the main control server;

the master control server sends a device network access command to the micro cloud server to transmit network access parameters;

and the master control server receives the equipment network access response sent by the micro cloud server after the network access parameters are configured.

23. The method according to claim 22, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, further comprising:

the master control server sends an equipment authentication command to the micro cloud server to transmit authentication parameters;

the master control server receives an equipment authentication response sent by the micro cloud server after the micro cloud server executes authentication operation by using the authentication parameters;

The main control server judges whether the micro cloud server is successfully authenticated; and if so, executing the main control server to send a device network access command to the micro cloud server so as to transmit network access parameters.

24. The method according to claim 22, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, further comprising:

the master control server sends a device heartbeat command to the micro cloud server;

and the master control server receives the equipment heartbeat response sent by the micro cloud server.

25. The method of claim 24, wherein the device heartbeat response includes upper layer device presence information, lower layer device presence information;

if the micro cloud server is a boundary router, the online information of the upper layer equipment indicates whether the boundary router is connected to a boundary sub-control server in the upper layer autonomous cloud or not;

26. The method according to claim 25, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, further comprising:

if the online information of the upper layer equipment indicates that the boundary router is not connected to the boundary sub-control server in the upper layer autonomous cloud, the main control server sets the connection state between the autonomous cloud where the main control server is located and the upper layer autonomous cloud where the boundary router is located to be a non-connection state.

27. The method according to claim 25, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, further comprising:

and if the online information of the lower-layer equipment is that the boundary router accessing the boundary sub-control server is not online, the main control server sets the access state between the autonomous cloud where the main control server is located and the next autonomous cloud where the boundary router is located to be the unaccessed state.

28. The method according to claim 24, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, and further comprising:

and if the master control server does not receive the equipment heartbeat response of the micro cloud server in a preset time period, setting the micro cloud server in a non-network-access state.

29. The method according to claim 28, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, further comprising:

when the micro cloud server is a boundary router, the main control server sets the access state between the autonomous cloud where the main control server is located and the upper layer autonomous cloud where the boundary router is located as the unaccessed state;

30. The method of claim 22, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, and further comprising:

the method comprises the steps that a master control server sends an exchange node information configuration command to a newly-accessed micro cloud server to transmit physical port information of the newly-accessed micro cloud server;

and the master control server receives the switching node information configuration response sent after the micro cloud server which is just accessed to the network configures the physical port information of the micro cloud server which is accessed to the network.

31. The method according to claim 22, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, further comprising:

The method comprises the steps that a master control server sends an exchange node information configuration command to a micro cloud server which is accessed to the network so as to transmit physical port information of the micro cloud server which is just accessed to the network;

and the master control server receives the switching node information configuration response sent after the micro cloud server which has accessed the network configures the physical port information of the micro cloud server which has just accessed the network.

32. The method according to claim 22, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, further comprising:

the method comprises the steps that a main control server sends an exchange node information configuration command to a micro cloud server which is connected to the network so as to transmit physical port information of the micro cloud server which is just disconnected from the network;

and the master control server receives the switching node information configuration response sent by the micro cloud server which is accessed to the network after deleting the physical port information of the micro cloud server which is just quitted from the network.

33. The method according to claim 22, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, further comprising:

the main control server sends a lower-layer equipment information configuration command to the terminal sub-control server so as to transmit the registration information of the terminal accessed to the terminal sub-control server;

And the main control server receives the lower-layer equipment information configuration response sent after the terminal sub-control server configures the registration information of the terminal.

34. The method according to claim 32, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, further comprising:

when the registration information of the terminal changes, the main control server sends a lower-layer equipment information configuration command to the terminal sub-control server so as to transmit the changed registration information of the terminal;

and the main control server receives the registration information which is sent after the terminal sub-control server configures the terminal change, and then sends a lower-layer equipment information configuration response.

35. The method according to claim 22, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, further comprising:

the main control server sends a lower layer equipment information configuration command to the boundary sub-control server so as to transmit registration information of a boundary router accessed to the boundary sub-control server;

and the main control server receives the lower-layer equipment information configuration response sent after the boundary sub-control server configures the registration information of the boundary router.

36. The method according to claim 35, wherein the master server in each autonomous cloud controls the micro cloud server to access the master server, further comprising:

When the registration information of the boundary router changes, the main control server sends a lower-layer equipment information configuration command to the boundary sub-control server so as to transmit the changed registration information of the boundary router;

and the main control server receives the registration information after the boundary sub-control server configures the boundary router to change, and then sends a lower-layer equipment information configuration response.

37. The method according to claim 21, 33 or 34, wherein the sub-control terminal servers in the respective autonomous clouds control the sub-control terminal access sub-control terminal servers, and the method comprises:

the terminal sub-control server sends a device connection command to the terminal;

the terminal sub-control server receives a device connection response sent by the terminal when the terminal verifies that the device connection command belongs to the terminal sub-control server;

the terminal sub-control server sends a device network access command to the terminal so as to transmit network access parameters;

and the terminal sub-control server receives the equipment network access response sent by the terminal after the network access parameters are configured.

38. The method according to claim 37, wherein the sub-control terminal server in each autonomous cloud controls a sub-control terminal access to the sub-control terminal server, further comprising:

the terminal sub-control server sends a device authentication command to the terminal to transmit authentication parameters;

The terminal sub-control server receives an equipment authentication response sent by the terminal after the terminal executes authentication operation by using the authentication parameters;

the terminal sub-control server judges whether the terminal is successfully authenticated; and if so, executing the terminal sub-control server to send a device network access command to the terminal so as to transmit network access parameters.

39. The method according to claim 37, wherein the sub-control terminal server in each autonomous cloud controls a sub-control terminal access to the sub-control terminal server, further comprising:

the terminal sub-control server sends a device heartbeat command to the terminal;

and the terminal sub-control server receives the equipment heartbeat response sent by the terminal.

40. The method of claim 39, wherein the sub-control terminal server in each autonomous cloud controls a sub-control terminal to access the sub-control terminal server, further comprising:

and if the terminal sub-control server does not receive the equipment heartbeat response of the terminal in a preset time period, setting the terminal in a non-network-access state.

41. The method as claimed in claim 21, 35 or 36, wherein the controlling of the border router to access the border sub-control server by the border sub-control server in each autonomous cloud comprises:

the boundary sub-control server sends a device connection command to the boundary router;

The boundary sub-control server receives an equipment connection response sent by the boundary router when the equipment connection command is verified to belong to the boundary sub-control server;

the boundary sub-control server sends a device network access command to the boundary router so as to transmit network access parameters;

and the boundary sub-control server receives the equipment network access response sent by the boundary router after the network access parameters are configured.

42. The method as claimed in claim 41, wherein the border sub-control server in each autonomous cloud controls the border router to access the border sub-control server, further comprising:

the boundary sub-control server sends an equipment authentication command to the boundary router to transmit authentication parameters;

the boundary sub-control server receives an equipment authentication response sent by the boundary router after the boundary router executes authentication operation by using the authentication parameters;

the boundary sub-control server judges whether the boundary router is successfully authenticated; and if so, executing the boundary sub-control server to send a device network access command to the boundary router so as to transmit network access parameters.

43. The method as claimed in claim 41, wherein the border sub-control server in each autonomous cloud controls the border router to access the border sub-control server, further comprising:

The boundary sub-control server sends a device heartbeat command to the boundary router;

and the boundary sub-control server receives the equipment heartbeat response sent by the boundary router.

44. The method as claimed in claim 43, wherein the border sub-control server in each autonomous cloud controls the border router to access the border sub-control server, further comprising:

and if the boundary sub-control server does not receive the equipment heartbeat response of the boundary router over the preset time period, setting the boundary router to be in a non-network-access state.

45. The method as claimed in claim 41, wherein the border sub-control server in each autonomous cloud controls the border router to access the border sub-control server, further comprising:

the boundary sub-control server sends a switching node information configuration command to the boundary router which just enters the network so as to transmit the physical port information of the boundary router which has entered the network;

and the boundary sub-control server receives the switching node information configuration response sent after the boundary router which just enters the network configures the physical port information of the boundary router which has already entered the network.

46. The method as claimed in claim 41, wherein the border sub-control server in each autonomous cloud controls the border router to access the border sub-control server, further comprising:

The boundary sub-control server sends a switching node information configuration command to the boundary router which has accessed the network so as to transmit the physical port information of the boundary router which has just accessed the network;

and the boundary sub-control server receives a switching node information configuration response sent after the boundary router which has accessed the network configures the physical port information of the boundary router which has just accessed the network.

47. The method as claimed in claim 41, wherein the border sub-control server in each autonomous cloud controls the border router to access the border sub-control server, further comprising:

the boundary sub-control server sends an exchange node information configuration command to the boundary router which has already accessed the network so as to transmit the physical port information of the boundary router which has just exited the network;

and the boundary sub-control server receives a switching node information configuration response sent by the boundary router which has accessed the network after deleting the physical port information of the boundary router which has just exited the network.

48. The method of claim 1 or 21, further comprising:

a master control server in the autonomous cloud controls the last layer of autonomous cloud to access the autonomous cloud;

and the master control server in the autonomous cloud controls the next autonomous cloud to access the autonomous cloud.

49. The method according to claim 48, wherein the master server in the autonomous cloud controls an upper layer autonomous cloud to access the autonomous cloud, and the method comprises the following steps:

The method comprises the steps that a main control server in the autonomous cloud receives an autonomous cloud network access configuration command of a boundary router multiplexed with an upper layer of autonomous cloud to transmit network parameters of the upper layer of autonomous cloud;

the master control server in the autonomous cloud checks whether the autonomous cloud network access configuration command belongs to the autonomous cloud network access configuration command; and if so, performing network access configuration on the previous layer of autonomous cloud according to the network parameters of the previous layer of autonomous cloud, and sending an autonomous cloud network access configuration response to the boundary router.

50. The method according to claim 48, wherein a master server in the autonomous cloud controls a next layer of autonomous cloud to access the autonomous cloud, and the method comprises:

the method comprises the steps that a main control server in the autonomous cloud receives an autonomous cloud network access configuration command of a boundary router multiplexed with the next layer of autonomous cloud to transmit network parameters of the next layer of autonomous cloud;

the master control server in the autonomous cloud checks whether the autonomous cloud network access configuration command belongs to the autonomous cloud network access configuration command; and if so, performing network access configuration on the next layer of autonomous cloud according to the network parameters of the next layer of autonomous cloud, and sending an autonomous cloud network access configuration response to the boundary router.

51. An autonomous network is characterized in that the autonomous network comprises a plurality of autonomous clouds distributed according to layers, each autonomous cloud comprises a main control server, a micro cloud server, a terminal and a switching network, each micro cloud server comprises a boundary router, a terminal sub-control server and a boundary sub-control server, and two adjacent layers of autonomous clouds are connected by multiplexing the same boundary router;

In each autonomous cloud, a main control server and a micro cloud server are connected into a switching network to form a main control micro cloud, a terminal sub-control server and a terminal are connected into another switching network to form a terminal sub-control micro cloud, and a boundary sub-control server and a boundary router are connected into another switching network to form a boundary sub-control micro cloud; the connection mode of the equipment in the master control micro cloud, the terminal sub-control micro cloud and the terminal sub-control micro cloud at least comprises one of tree type, star type and full connection type; the master server includes:

the service request receiving module is used for receiving a service request of the global data sink; the global data sink is a terminal, a terminal sub-control server or a boundary sub-control server;

52. The autonomous network of claim 51 wherein the global multicast link creation module comprises:

the first autonomous cloud attribution query sub-module is used for querying autonomous clouds to which a global data source and global data sink belong in an autonomous network according to the data sink adding request;

a first local source sink determining submodule, configured to determine, if the multicast data stream exists, a local data source and a local data sink in a local autonomous cloud according to the global data source and an autonomous cloud to which the global data sink belongs; the local data sink is a terminal, a terminal sub-control server, a boundary sub-control server or a boundary router;

53. The autonomous network of claim 52 wherein the global multicast link creation module further comprises:

the first off-site data sink adding command sending submodule is used for sending an off-site data sink adding command to a main control server in the previous-hop autonomous cloud so as to inform the main control server in the previous-hop autonomous cloud to establish a global multicast link for transmitting at least part of multicast data streams from the global data source to the global data sink in the previous-hop autonomous cloud;

54. The autonomous network of claim 51 wherein the global multicast link creation module comprises:

the command receiving submodule for adding the remote data sink is used for receiving a command for adding the remote data sink;

a second local source sink determining submodule, configured to determine, if the multicast data stream exists, a local data source and a local data sink in a local autonomous cloud according to the global data source and an autonomous cloud to which the global data sink belongs; the local data sink is a terminal, a terminal sub-control server, a boundary sub-control server or a boundary router;

55. The autonomous network of claim 54 wherein the global multicast link creation module further comprises:

56. The autonomous network of claim 54 wherein the global multicast link creation module further comprises:

And the second adding different-place data sink response waiting submodule is used for waiting for adding different-place data sink responses sent by the master control server of the previous-hop autonomous cloud.

57. The autonomous network of claim 51 wherein the global multicast link creation module comprises:

a third autonomous cloud attribution query sub-module, configured to query, according to the added allopatric data sink response, an autonomous cloud to which a global data source and a global data sink in an autonomous network belong;

the third multicast data stream judging submodule is used for judging whether a multicast data stream corresponding to the adding of the allopatric data convergence response exists in the autonomous cloud or not;

a third local source sink determining submodule, configured to determine, if the multicast data stream does not exist, a local data source and a local data sink in a local autonomous cloud according to the global data source and an autonomous cloud to which the global data sink belongs; the local data sink is a terminal, a terminal sub-control server, a boundary sub-control server or a boundary router;

58. The autonomous network of claim 57, wherein if the multicast data stream does not exist, the global multicast link creation module further comprises:

a first multicast data stream creating submodule, configured to create a multicast data stream in the local data source;

59. The autonomous network of claim 57, wherein the global multicast link creation module further comprises:

60. The autonomous network of claim 51 wherein the global multicast link creation module comprises:

the fourth autonomous cloud attribution inquiring sub-module is used for inquiring the autonomous cloud to which the global data source belongs in the autonomous network according to the created data source request;

61. The autonomous network of any one of claims 51-60 wherein the master server further comprises:

and the global multicast link closing module is used for closing a global multicast link from the global data source to the global data sink in the autonomous cloud to which the global multicast link belongs when the service communication is finished.

62. The autonomous network of claim 61, wherein the global multicast link shutdown module comprises:

a data sink deletion request receiving submodule, configured to receive a data sink deletion request by a master control server in the autonomous cloud;

a fifth autonomous cloud attribution query sub-module, configured to query, according to the request for deleting data sinks, an autonomous cloud to which a global data source and global data sink in an autonomous network belong;

a fifth multicast data stream judgment submodule, configured to judge whether a multicast data stream corresponding to the data sink deletion request exists in the autonomous cloud;

a fourth local source sink determining submodule, configured to determine, if the multicast data stream exists, a local data source and a local data sink in a local autonomous cloud according to the global data source and the autonomous cloud to which the global data sink belongs; the local data sink is a terminal, a terminal sub-control server, a boundary sub-control server or a boundary router;

63. The autonomous network of claim 62 wherein the global multicast link shutdown module further comprises:

64. The autonomous network of claim 61, wherein the global multicast link shutdown module comprises:

a sixth multicast data stream judgment submodule, configured to judge whether a multicast data stream corresponding to the remote data sink deletion command exists in the autonomous cloud;

a fifth local source sink determining submodule, configured to determine, if the multicast data stream exists, a local data source and a local data sink in a local autonomous cloud according to the global data source and an autonomous cloud to which the global data sink belongs; the local data sink is a terminal, a terminal sub-control server, a boundary sub-control server or a boundary router;

65. The autonomous network of claim 64 wherein the global multicast link shutdown module further comprises:

66. The autonomous network of claim 64 wherein the global multicast link shutdown module further comprises:

a fourth back-hop autonomous cloud query submodule, configured to query an autonomous cloud that is routable to the global data sink and is connected to the autonomous cloud, and obtain a back-hop autonomous cloud;

A fourth adding different-place data sink response sending submodule for sending a delete different-place data sink response to the main control server in the next-hop autonomous cloud so as to inform the main control server in the next-hop autonomous cloud of closing the multicast data stream;

67. The autonomous network of claim 61 wherein the global multicast link shutdown module comprises:

a seventh multicast data stream judging submodule, configured to judge whether a multicast data stream corresponding to the deleted remote data sink response exists in the autonomous cloud;

a third data sink judging submodule, configured to judge whether there is a data sink in the autonomous cloud to receive the multicast data stream if the multicast data stream exists; if yes, calling a delete remote data sink response ignoring submodule, and if not, calling a local source end determining submodule;

the local source end determining submodule is used for determining a local data source in the autonomous cloud according to the autonomous cloud to which the global data source belongs;

68. The autonomous network of claim 67 wherein the multicast data flow closure submodule comprises:

69. The autonomous network of claim 67 wherein the global multicast link shutdown module further comprises:

70. The autonomous network of claim 61, wherein the global multicast link shutdown module comprises:

an eighth multicast data stream judgment sub-module, configured to judge whether a multicast data stream corresponding to the data source creation request exists in the autonomous cloud if the global data source belongs to the autonomous cloud;

a fourth data sink judging sub-module, configured to judge whether there is a data sink in the autonomous cloud to receive the multicast data stream if there is the multicast data stream; if not, calling a multicast data stream destroying submodule;

and the destroy data source response generation submodule is used for generating a destroy data source response so as to inform the completion of the destroy of the multicast data stream.

71. The autonomous network of claim 61 wherein,

the master server further comprises:

the micro cloud server control access module is used for controlling the micro cloud server to access the master control server;

the terminal branch control server includes:

the terminal control access module is used for controlling the terminal to access the terminal sub-control server;

The boundary sub-control server comprises:

and the border router control access module is used for controlling the border router to access the border sub-control server.

72. The autonomous network of claim 71, wherein the micro cloud server control access module comprises:

and the first equipment network access response receiving submodule is used for receiving an equipment network access response sent by the micro cloud server after the network access parameters are configured.

73. The autonomous network of claim 72, wherein the micro cloud server control access module further comprises:

The first authentication judgment sub-module is used for judging whether the micro cloud server is successfully authenticated; if yes, the first equipment network access command sending submodule is called.

74. The autonomous network of claim 72, wherein the micro cloud server control access module further comprises:

75. The autonomous network of claim 74 wherein the device heartbeat responses include upper layer device presence information, lower layer device presence information;

76. The autonomous network of claim 75, wherein the micro-cloud server control access module further comprises:

and the first state setting submodule is used for setting the access state between the autonomous cloud where the main control server is located and the last autonomous cloud where the boundary router is located as a non-access state if the online information of the upper layer equipment indicates that the boundary router is not accessed to the boundary sub-control server in the last autonomous cloud.

77. The autonomous network of claim 75, wherein the micro-cloud server control access module further comprises:

and the second state setting submodule is used for setting the access state between the autonomous cloud where the main control server is located and the next autonomous cloud where the boundary router is located as a non-access state if the online information of the lower-layer equipment is that the boundary router accessing the boundary sub-control server is not online.

78. The autonomous network of claim 74, wherein the micro cloud server control access module further comprises:

and the third state setting submodule is used for setting the micro cloud server to be in a non-network-access state if the equipment heartbeat response of the micro cloud server is not received after the preset time period is exceeded.

79. The autonomous network of claim 78, wherein the micro cloud server control access module further comprises:

80. The autonomous network of claim 72, wherein the micro cloud server control access module further comprises:

81. The autonomous network of claim 72, wherein the micro cloud server control access module further comprises:

the second switching node information configuration command sending submodule is used for sending a switching node information configuration command to the micro cloud server which has accessed to the network so as to transmit the physical port information of the micro cloud server which has just accessed to the network;

and the second exchange node information configuration response receiving submodule is used for receiving an exchange node information configuration response sent by the newly-accessed micro cloud server after the micro cloud server is configured with the physical port information of the micro cloud server.

82. The autonomous network of claim 72, wherein the micro cloud server control access module further comprises:

the third exchange node information configuration command sending submodule is used for sending an exchange node information configuration command to the micro cloud server which has already accessed to the network so as to transmit the physical port information of the micro cloud server which has just exited the network;

83. The autonomous network of claim 72, wherein the micro cloud server control access module further comprises:

84. The autonomous network of claim 82, wherein the micro cloud server control access module further comprises:

and the second lower-layer equipment information configuration response receiving submodule is used for receiving a lower-layer equipment information configuration response sent by the terminal sub-control server after the terminal configuration information is changed.

85. The autonomous network of claim 72, wherein the micro cloud server control access module further comprises:

86. The autonomous network of claim 85, wherein the micro cloud server control access module further comprises:

a fourth lower-layer equipment information configuration command sending submodule, configured to send a lower-layer equipment information configuration command to the border sub-control server when the registration information of the border router changes, so as to transmit the changed registration information of the border router;

87. The autonomous network of claim 71 or 83 or 84 wherein the terminal control access module comprises:

88. The autonomous network of claim 87 wherein the terminal-controlled access module further comprises:

the second authentication judgment submodule is used for judging whether the terminal is successfully authenticated; and if so, executing and calling the second equipment connection command sending submodule.

89. The autonomous network of claim 87 wherein the terminal-controlled access module further comprises:

90. The autonomous network of claim 89 wherein the terminal control access module further comprises:

91. The autonomous network of claim 71 or 85 or 86 wherein the border router control access module comprises:

92. The autonomous network of claim 91 wherein the border router control access module further comprises:

93. The autonomous network of claim 91 wherein the border router control access module further comprises:

the third equipment heartbeat command sending submodule is used for sending an equipment heartbeat command to the boundary router;

94. The autonomous network of claim 93 wherein the border router control access module further comprises:

95. The autonomous network of claim 91 wherein the border router control access module further comprises:

a fourth switching node information configuration command sending submodule, configured to send a switching node information configuration command to the border router that has just entered the network, so as to transmit physical port information of the border router that has entered the network;

96. The autonomous network of claim 91 wherein the border router control access module further comprises:

and the fifth switching node information configuration response receiving submodule is used for receiving the switching node information configuration response sent by the boundary router which has accessed the network after the physical port information of the boundary router which has just accessed the network is configured.

97. The autonomous network of claim 91 wherein the border router control access module further comprises:

98. The autonomous network of claim 51 or 71 wherein the master server further comprises:

the upper-layer autonomous cloud access control module is used for controlling the upper-layer autonomous cloud to be accessed into the autonomous cloud;

and the lower autonomous cloud access control module is used for controlling the next autonomous cloud to access the autonomous cloud.

99. The autonomous network of claim 98, wherein the upper autonomous cloud access control module comprises:

100. The autonomous network of claim 98, wherein the lower autonomous cloud access control module comprises:

the second autonomous cloud network access configuration command checking submodule is used for checking whether the autonomous cloud network access configuration command belongs to the second autonomous cloud network access configuration command checking submodule; if yes, calling a lower-layer autonomous network access configuration submodule;

and the lower autonomous network access configuration submodule is used for carrying out network access configuration on the next autonomous cloud according to the network parameters of the next autonomous cloud and sending an autonomous cloud network access configuration response to the boundary router.