WO2016004635A1

WO2016004635A1 - Domain merging method, domain master node and node

Info

Publication number: WO2016004635A1
Application number: PCT/CN2014/082099
Authority: WO
Inventors: 姜彤; 董晨; 刘培
Original assignee: 华为技术有限公司
Priority date: 2014-07-11
Filing date: 2014-07-11
Publication date: 2016-01-14
Also published as: CN105453500A

Abstract

The present invention relates to the technical field of communications, and specifically relates to a domain merging method, a domain master (DM) and a node. In the solution, DM sends merging indication messages to local domain nodes with influences on service flows when DM would be merged into other domains, and only sends off-domain messages to nodes with influences on service flows when the nodes with influence on service flows join a second domain. Therefore, the defect of service interruption is avoided.

Description

Method for domain merging, domain master node and node

The present invention relates to the field of communications technologies, and in particular, to a domain merging method, a domain master node, and a class node. Background technique

With the development of communication technologies and the popularity of network technologies, the importance of home networks has become increasingly prominent. The home network may include one or more domains, wherein a network composed of the DM and all other nodes registered to the DM is called a domain, and each domain is a centralized management network, and each domain has one domain. DM (Domain Master) The DM is used to manage other nodes in the domain. The nodes can be in various forms, such as a home gateway, a power cat, or a set-top box, a smart TV, and the like.

In addition to the communication functions of common nodes, DM also has the management functions responsible for the entire domain, such as: domain establishment, registration of nodes included in the domain, bandwidth allocation and resource scheduling of the domain, and multiple neighboring domains or networks. Coordination, network power management, etc.

In order to improve the security of data transmitted in the domain, the domain working in the security mode also includes an SC (Security Controller), which is responsible for the authentication of the nodes in the domain and the management of the key management process, each registered. The nodes must obtain the key after completing the authentication to the SC, and transmit the data, thereby improving the security of the transmitted data.

The DM performs domain management and resource scheduling by transmitting a MAP (Media Access Plan) frame in each MAC (Media Access Control) cycle, and the node detects the existence of the domain by detecting the MAP frame. The domain is added to the domain by sending a registration request to the DM. After the registration is successful, the SC is authenticated to improve the security of the transmitted data. After the authentication succeeds, data transmission can be started.

In order to guarantee QoS (Quality of Service), the node needs to apply to the DM. The service flow, if the DM can support the establishment of the service flow, agrees to the application, and after the service flow is established, performs resource scheduling according to the TSpec (Traffic Specification). The scheduling mode of the DM for the service flow may be continuous scheduling or non-persistent scheduling. The persistent scheduling is effective for the resource scheduling information advertised by the DM in several MAC cycles, and the non-persistent scheduling is the resource scheduling information advertised by the DM. Only valid for the next MAC cycle.

For example: One (several) nodes in a certain domain that are working detect MAP-D from another domain (Media Access Plan - Default, Media Access Plan - Default) /RMAP-D

(Relayed Media Access Plan - Default, Forwarded Media Access Plan - Default) Frame or MAP-A (Media Access Plan - Active, Media Access Plan - Active) /RMAP-A

(Relayed Media Access Plan - Active, forwarded media access plan - valid) frame, and the domain name of another domain is the same as the domain name of the domain where the node is located, then the two domains need to be merged.

For example: As shown in FIG. 1A, there is only one domain: domain 1, domain 1 includes DM and node N1, node N2, node N3, node N4, node N5, but the channel changes between DM and node N2. Or other reasons, the DM cannot detect the existence of the node N2 and cannot communicate directly. According to the current regulations, the original domain 1 will be divided into two domains: domain 2 and domain 3, node N2, node N3, and node N4 will proceed. DM recovery, node N2, node N3, node 1-4 capable of DM capability will become the newly formed DM in domain 3 (node N2 in the figure). If node N2 can again hear the MAP-D/RMAP-D frame or MAP-A/RMAP-A frame sent by the DM, domain 2 and domain 3 need to be merged.

For another example, as shown in FIG. 1B, there is only one domain: domain 1, domain 1 includes DM and node N1, node N2, node N3, node N4, and node N5, but because the DM is offline, two cannot be connected. The part, node N1 and node N5, node N2, node N3 and node N4, according to the current regulations, the original domain 1 will be divided into two domains: domain 2 and domain 3, node N2, node N3, node N4 will perform DM recovery. One node of node N2, node N3, and node N4 with DM capability will become the DM in the newly formed domain 3 (node N2 in the figure). Node N1 and node N5 will also perform DM recovery. One node with node DM and node N5 with DM capability will become the newly formed DM in domain 2 (node N1 in the figure). When the original DM is back online, it will Join one of them Domain, if the nodes in another domain can detect the MAP-D/RMAP-D frame or the MAP-A/RMAP-A frame sent by the DM again, domain 2 and domain 3 need to be merged.

In the prior art, when domain merging is performed, the nodes in the domain may be defective in the interruption of service transmission carried by the service flow. As shown in FIG. 1A, if domain 3 is to be merged into domain 2, N2 sends a backoff message to N3 and N4. After leaving domain 3, N3 and N4 join domain 2, and at this time, between nodes of domain 3. The service flow will be disconnected and the services carried by the service flow will be interrupted.

In summary, the current domain merging method has the defect of service transmission interruption. Summary of the invention

The embodiment of the invention provides a domain merging method, a domain master node and a node, which are used to solve the problem of existing service transmission interruption in the domain merging process.

In a first aspect, a domain master node is provided, where the domain master node DM belongs to a first domain of a communication network, the first domain includes the DM, and a node managed by the DM, and the communication network further includes a a second domain, the second domain includes another DM, where the DM includes: a processing unit, configured to determine, from a node included in the first domain managed by the DM, a first type of node, where The first type of node is a node associated with at least one service flow of the first domain;

a sending unit, configured to send a merge indication message to the first type of node, where the merge indication message is used to indicate that the first type of node joins the second domain;

a receiving unit, configured to receive a completion merge response message returned by the first type of node, where the completion merge response message is used to feed back that the first type of node has joined the second domain;

The sending unit is further configured to send a de-local message to the first-type node, where the de-local message is used to indicate that the first-type node exits the first domain.

With reference to the first aspect, in a first possible implementation, the processing unit is specifically configured to: determine, according to the topology information and the service flow information of the first domain, from the nodes included in the first domain The first type of node.

Combining the first aspect, or the first possible implementation of the first aspect, in the second possibility In an implementation manner, the first type of node determined by the processing unit is a node that belongs to a service flow, and/or provides a media access plan MAP relay function for a node that belongs to the service flow.

With reference to the second possible implementation manner of the first aspect, in a third possible implementation manner, the first type of node determined by the processing unit is a node that belongs to the service flow and is not the other service flow. a node that provides MAP relay functionality; or

The first type of node is a node that belongs to the service flow and provides a MAP relay function for other nodes belonging to the service flow; or

The first type of node is a node that does not belong to the service flow and provides a MAP relay function for other nodes belonging to the service flow;

The node belonging to the service flow is a node for which the corresponding service transmission is carried by the service flow.

With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner, when the first type of node is a node that belongs to a service flow and does not provide a MAP relay function for other nodes belonging to the service flow Or, when the first type of node is a node that belongs to the service flow and provides a MAP relay function for the other node that belongs to the service flow, the completion merge response message received by the receiving unit is the first type of node. Any one of the nodes is added to the second domain managed by the another DM and returned after establishing a service flow with the another DM;

When the first type of node is a node that does not belong to the service flow and provides a MAP relay function for other nodes that belong to the service flow, the completion merge response message received by the receiving unit is any of the first type of nodes. A node returns after joining the second domain managed by the other DM.

With reference to the first aspect, or the first to fourth possible implementation manners of the first aspect, in a fifth possible implementation manner, the sending unit is specifically configured to:

Sending, to each node of the first type of node, a merge indication message carrying the node type identifier of the node to the node; or

A merge indication message carrying the node type identifiers corresponding to the respective nodes is sent to each node in the first type of node in a broadcast form.

Combining the third to fifth possible implementations of the first aspect, in the sixth possible implementation Wherein, the processing unit is further configured to:

Determining that the first type of node exits the first domain has no effect on the service flow in the first domain.

In conjunction with the third to sixth possible implementations of the first aspect, in a seventh possible implementation, if the first type of node is a node that belongs to a service flow, the processing unit is further configured to:

Determine that the priority of the service flow to which the node belongs is greater than or equal to the service flow priority threshold. In a second aspect, a node is provided, the node belongs to a first domain of a communication network, the node is managed by a first domain master node DM of the first domain, and the communication network further includes a second domain, The second domain includes a second DM, where the node includes:

a receiving unit, configured to receive a merge indication message sent by the first DM, where the merge indication message is used to indicate that the node joins the second domain;

a processing unit, configured to add to the second domain according to the merge indication message, and generate a complete merge response message, where the complete merge response message is used to feed back that the node has joined the second domain;

And a sending unit, configured to send the completion merge response message to the first DM.

With reference to the second aspect, in a first possible implementation, the node is a node that belongs to the service flow, and/or provides a media access plan MAP relay function for a node that belongs to the service flow.

With reference to the second aspect, or the first possible implementation manner of the second aspect, in a second possible implementation manner, the node provides a MAP that belongs to the service flow and does not belong to another node that belongs to the service flow. a node that relays functionality; or

The node is a node that belongs to the service flow and provides a MAP relay function for other nodes belonging to the service flow; or

The node is a node that does not belong to the service flow and provides a MAP relay function for other nodes belonging to the service flow;

With reference to the second possible implementation of the second aspect, in a third possible implementation, the processing unit is further configured to: when the class node belongs to a service flow, and not belongs to another service flow The node provides a node of the MAP relay function; or, when the node belongs to the service flow and provides the MAP relay function for other nodes belonging to the service flow, the service flow is established with the second DM.

With reference to the second aspect, or the first to third possible implementation manners of the second aspect, in a fourth possible implementation, the receiving unit is further configured to receive a de-local message returned by the first DM;

The processing unit is further configured to exit the first domain according to the delocalized message.

In a third aspect, a method for domain merging is provided, which is applied to a communication network, the communication network includes at least two domains, the first domain in the at least two domains includes a first domain master node DM, and the a node managed by the DM, and the second domain in the at least two domains includes a second DM, and the method includes:

Determining a first type of node from a node included in a first domain managed by the first DM, wherein the first type of node is a node associated with at least one service flow of the first domain;

Sending a merge indication message to the first type of node, where the merge indication message is used to indicate that the first type of node has joined the second domain;

Receiving a complete merge response message returned by the first type of node, where the complete merge response message is used to feed back the first type of node to join the second domain;

And sending a delocal message to the first type of node, where the delocalized message is used to indicate that the first type of node exits the first domain.

With reference to the third aspect, in a first possible implementation, the first type of node is determined from the nodes included in the first domain managed by the first DM, and specifically includes:

And determining, according to the topology information and the service flow information of the first domain, the first type of node from the nodes included in the first domain.

With reference to the third aspect, or the first possible implementation manner of the third aspect, in a second possible implementation manner, the first type of node belongs to a service flow, and/or provides media for a node that belongs to the service flow. Access to the node that plans the MAP relay function.

With reference to the second possible implementation manner of the third aspect, in a third possible implementation manner, the first type of node is provided by the node that belongs to the service flow and does not belong to another service flow. a node of the MAP relay function; or

With reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner, when the first type of node is a node that belongs to a service flow and does not provide a MAP relay function for other nodes belonging to the service flow Or, when the first type of node is a node that belongs to the service flow and provides a MAP relay function for other nodes that belong to the service flow, the completion merge response message is any one of the first type of nodes. Adding to the second domain managed by the second DM, and returning after establishing the service flow with the second DM;

When the first type of node is a node that does not belong to the service flow and provides a MAP relay function for other nodes that belong to the service flow, the completion merge response message is that any one of the first type of nodes is added to Returned after the second domain managed by the second DM.

With the third aspect, or the first to fourth possible implementation manners of the third aspect, in a fifth possible implementation, the sending the merge indication message to the first type of node, specifically: Each of the nodes of the class, sending a merge indication message carrying the node type identifier of the node to the node; or

With reference to the third to fifth possible implementation manners of the third aspect, in a sixth possible implementation manner, if the first type of node is a service flow, and a MAP relay function is provided for other nodes belonging to the service flow The node of the first type is a node that does not belong to the service flow and provides the MAP relay function for the other node that belongs to the service flow. Before sending the de-message message to the first-type node, the method further includes: Determining that the first type of node exits the first domain has no effect on the service flow in the first domain.

With reference to the third to sixth possible implementation manners of the third aspect, in a seventh possible implementation manner, if the first type of node is a node that belongs to a service flow, before sending the indication message to the node, Also includes:

Determine that the priority of the service flow to which the node belongs is greater than or equal to the service flow priority threshold. A fourth aspect provides a method for domain merging, which is applied to a communication network, the communication network includes at least two domains, the first domain in the at least two domains includes a first domain master node DM, and the a node managed by the DM, and the second domain in the at least two domains includes a second DM, and the method includes:

The first type of node in the first domain receives the merge indication message sent by the first DM, where the merge indication message is used to indicate that the first type of node joins the second domain, where the first type of node is a node associated with at least one service flow of the first domain;

The first type of node joins the second domain according to the merge indication message, and generates a complete merge response message, where the complete merge response message is used to feed back that the first type of node has joined the first Two domains;

The first type of node returns a completion merge response message to the first DM.

With reference to the fourth aspect, in a first possible implementation manner, the first type of node is a node that belongs to the service flow, and/or provides a media access plan MAP relay function for a node that belongs to the service flow. .

With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, in a second possible implementation, the first type of node belongs to the service flow, and is not belong to the service flow. a node that provides a MAP relay function; or

The node belonging to the service flow is a section corresponding to the service transmission carried by the service flow. Point.

With reference to the second possible implementation manner of the fourth aspect, in a third possible implementation manner, after receiving the merge indication message sent by the first DM, the first type of node returns a complete merge to the first DM. Before responding to the message, it also includes:

When the first type of node is a node that belongs to a service flow and does not provide a media access plan MAP relay function for other nodes belonging to the service flow; or, provides a MAP relay for belonging to the service flow and for other nodes belonging to the service flow. When the node is functional, the first type of node establishes a service flow with the second DM.

With reference to the fourth aspect, or the first to third possible implementation manners of the fourth aspect, in a fourth possible implementation manner, after the first type of node returns a complete merge response message to the first DM, Also includes:

The first type of node receives the delocalized message returned by the first DM, and exits the first domain according to the delocalized message.

The embodiment of the present invention is applied to a communication network, where the communication network includes at least two domains, the first domain in the at least two domains includes a first DM, and a node managed by the first DM, and a second in at least two domains. The domain includes a second DM, and the first type of node is determined from the nodes included in the first domain managed by the first DM, where the first type of node is a node associated with the at least one service flow of the first domain; A type of node sends a merge indication message, and the merge indication message is used to indicate that the first type of node joins the second domain; receives the completion merge response message returned by the first type of node, and completes the merge response message for feeding back the first type of node to join In the scenario, when the DM is to be merged into another domain, the merge indication message is sent to the first type node associated with the at least one service flow of the first domain in the local domain, and is returned in the first type node. When the merge response message is completed, the delocalized message is sent to the first type of node, thus avoiding the defect of the service transmission interruption. DRAWINGS

1A is a first schematic diagram of domain decomposition in the prior art;

FIG. 1B is a second schematic diagram of domain decomposition in the prior art 2 is a schematic diagram showing the functional structure of a DM in the implementation of the present invention;

3 is a schematic diagram of an entity structure of a DM in an implementation of the present invention;

4 is a schematic diagram showing the functional structure of a node in an implementation of the present invention;

5 is a schematic diagram of an entity structure of a node in an implementation of the present invention;

6 is a first detailed flowchart of domain merging in the implementation of the present invention;

7 is a second detailed flowchart of domain merging in the implementation of the present invention;

Figure 8 is an embodiment of domain consolidation in an implementation of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

In addition, the terms "system," and "network" are often used interchangeably herein. Terms used herein

"and / or" is just an association describing the associated object, indicating that there can be three relationships, for example, A and / or B, which can mean: A exists separately, A and B exist simultaneously, and B exists separately Kind of situation. In addition, the letter "/" in this article generally means that the contextual object is an "or" relationship.

The preferred embodiments of the present invention are described in detail below with reference to the accompanying drawings, and the preferred embodiments of the present invention are intended to illustrate and explain the invention, and not to limit the invention, and The embodiments in the application and the features in the embodiments may be combined with each other.

Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

Based on the foregoing technical solution, as shown in FIG. 2, an embodiment of the present invention provides a functional structure diagram of a DM. The domain primary node DM belongs to a first domain of a communication network, and the first domain includes a DM, and a node managed by the DM. The communication network further includes a second domain, the second domain includes another DM, and the DM includes a processing unit 20, a sending unit 21, and a receiving unit 22, where:

The processing unit 20 is configured to determine, according to the node included in the first domain managed by the DM, the first type of section a point, where the first type of node is a node that is associated with the at least one service flow of the first domain, and the sending unit 21 is configured to send a merge indication message to the first type of node, where the merge indication message is used to indicate that the first type of node joins To the second domain;

The receiving unit 22 is configured to receive a completion merge response message returned by the first type of node, and complete a merge response message for feeding back that the first type of node has joined the second domain;

The sending unit 21 is further configured to send a delocalized message to the first type of node, where the delocalized message is used to indicate that the first type of node exits the first domain.

In the embodiment of the present invention, optionally, the processing unit 20 is specifically configured to:

The first type of node is determined from the nodes included in the first domain according to the topology information and the service flow information of the first domain.

In the embodiment of the present invention, optionally, the first type of node determined by the processing unit 20 is a node that belongs to the service flow, and/or provides a media access plan MAP relay function for the node that belongs to the service flow.

In the embodiment of the present invention, optionally, the first type of node determined by the processing unit 20 is a node that belongs to the service flow and does not provide the MAP relay function for other nodes belonging to the service flow; or

The first type of node is a node that belongs to the service flow and provides MAP relay function for other nodes belonging to the service flow; or

The first type of node is a node that does not belong to the service flow and provides MAP relay function for other nodes belonging to the service flow;

The node belonging to the service flow is a node that is corresponding to the service transmission and is carried by the service flow.

In the embodiment of the present invention, further, when the first type of node is a node that belongs to the service flow and does not provide a MAP relay function for other nodes that belong to the service flow; or, when the first type of node belongs to the service flow, When the node of the service flow provides the node of the MAP relay function, the completion merge response message received by the receiving unit 22 is that any one of the first type of nodes is joined to the second domain managed by another DM, and the other Returned by the DM after establishing the service flow;

When the first type of node is a node that does not belong to the service flow and provides the MAP relay function for other nodes belonging to the service flow, the completion merge response message received by the receiving unit 22 is any one of the first type of nodes added to the node. Returned by another DM managed by the second domain. In the embodiment of the present invention, optionally, the sending unit 21 is specifically configured to:

Sending, to each node of the first type of node, a merge indication message carrying the node type identifier of the node; or

A merge indication message carrying a node type identifier corresponding to each node is sent to each node in the first type of node in a broadcast form.

In the embodiment of the present invention, further, the processing unit 20 is further configured to:

In the embodiment of the present invention, further, if the first type of node is a node that belongs to the service flow, the processing unit 20 is further configured to:

Determine that the priority of the service flow to which the node belongs is greater than or equal to the service flow priority threshold. As shown in FIG. 3, it is a physical device diagram of a DM according to an embodiment of the present invention. The domain master node DM belongs to a first domain of a communication network, and the first domain includes a DM, and a node managed by the DM, and the communication network further includes The second domain is included, and the second domain includes another DM. The physical device includes a signal receiver 30, a signal transmitter 31, and a processor 32, where:

The processor 32 is configured to determine, from a node included in the first domain managed by the DM, a first type of node, where the first type of node is a node associated with the at least one service flow of the first domain;

The signal transmitter 31 is configured to send a merge indication message to the first type of node, where the merge indication message is used to indicate that the first type of node joins the second domain;

The signal receiver 30 is configured to receive a completion merge response message returned by the first type of node, and complete a merge response message for feeding back that the first type of node has joined the second domain;

The signal transmitter 31 is further configured to send a delocalized message to the first type of node, where the delocalized message is used to indicate that the first type of node exits the first domain.

In the embodiment of the present invention, optionally, the processor 32 is specifically configured to:

In the embodiment of the present invention, optionally, the first type of node determined by the processor 32 is a node that belongs to the service flow, and/or provides a media access plan MAP relay function for the node that belongs to the service flow. In the embodiment of the present invention, optionally, the first type of node determined by the processor 32 is a node that belongs to the service flow and does not provide a MAP relay function for other nodes that belong to the service flow; or

In the embodiment of the present invention, further, when the first type of node is a node that belongs to the service flow and does not provide a MAP relay function for other nodes that belong to the service flow; or, when the first type of node belongs to the service flow, When the node of the service flow provides the node of the MAP relay function, the completion merge response message received by the signal receiver 30 is that any one of the first type of nodes is joined to the second domain managed by another DM, and the other Returned after a DM establishes a service flow;

When the first type of node is a node that does not belong to the service flow and provides the MAP relay function for other nodes belonging to the service flow, the completion merge response message received by the signal receiver 30 is added to any one of the first type of nodes. Returned to the second domain managed by another DM.

In the embodiment of the present invention, optionally, the signal transmitter 31 is specifically configured to:

In the embodiment of the present invention, further, the processor 32 is further configured to:

In the embodiment of the present invention, further, if the first type of node is a node that belongs to the service flow, the processor 32 is further configured to:

Determine that the priority of the service flow to which the node belongs is greater than or equal to the service flow priority threshold. Based on the foregoing technical solution, referring to FIG. 4, an embodiment of the present invention provides a functional structure diagram of a node, where the node belongs to a first domain of a communication network, and the node is a first domain of the first domain. The master node DM manages, the communication network further includes a second domain, and the second domain includes a second DM, the node includes a receiving unit 40, a processing unit 41, and a sending unit 42, wherein:

The receiving unit 40 is configured to receive a merge indication message sent by the first DM, where the merge indication message is used to indicate that the node joins the second domain;

The processing unit 41 is configured to join the second domain according to the merge indication message, and generate a completion merge response message, where the merge response message is used for the feedback node to join the second domain;

The sending unit 42 is configured to send the completion merge response message to the first DM.

In the embodiment of the present invention, optionally, the node is a node that belongs to the service flow, and/or provides a media access plan MAP relay function for the node that belongs to the service flow.

In the embodiment of the present invention, optionally, the node is a node that belongs to the service flow and does not provide the MAP relay function for other nodes that belong to the service flow; or

A node is a node that belongs to a service flow and provides MAP relay functionality for other nodes that belong to the service flow; or

A node is a node that does not belong to a service flow and provides a MAP relay function for other nodes belonging to the service flow;

In the embodiment of the present invention, the processing unit 41 is further configured to: when the class node is a node that belongs to the service flow and does not provide a MAP relay function for other nodes that belong to the service flow; or, belongs to the service flow, and belongs to the other When the node of the service flow provides the node of the MAP relay function, the service flow is established with the second DM.

As shown in FIG. 5, it is a physical device diagram of a node according to an embodiment of the present invention. The node belongs to a first domain of a communication network, and the node is managed by a first domain master node DM of the first domain, and the communication network further includes The second domain includes a second DM, and the physical device includes a signal receiver 50, a signal transmitter 51, and a processor 52, wherein:

The signal receiver 50 is configured to receive a merge indication message sent by the first DM, where the merge indication message is used to indicate that the node joins the second domain;

The processor 52 is configured to join the second domain according to the merge indication message, and generate a complete merge response. a message, wherein the completion merge response message is used by the feedback node to join the second domain; and the signal transmitter 51 is configured to send the complete merge response message to the first DM.

In the embodiment of the present invention, the processor 52 is further configured to: when the class node is a node that belongs to the service flow, does not provide a MAP relay function for other nodes that belong to the service flow; or, belongs to the service flow, and belongs to the other When the node of the service flow provides the node of the MAP relay function, the service flow is established with the second DM.

The first detailed process application provided below is applied to a communication network, the communication network includes at least two domains, the first domain in at least two domains includes a first DM, and a node managed by the first DM, at least two domains The second domain in the second domain includes a second DM.

Referring to FIG. 6, in the embodiment of the present invention, a first detailed process of domain merging is as follows: Step 600: Determine a first type of node from a node included in a first domain managed by a first DM, where the first type The node is a node associated with at least one service flow of the first domain;

Step 610: Send a merge indication message to the first type node, where the merge indication message is used to indicate that the first type node joins the second domain.

Step 620: Receive a completion merge response message returned by the first type of node, complete a merge response message, and use the feedback that the first type of node has joined the second domain.

Step 630: Send a delocalized message to the first type of node, where the delocalized message is used to indicate that the first type of node exits the first domain. In the embodiment of the present invention, there are multiple ways to determine the first type of nodes from the nodes included in the first domain managed by the first DM, and optionally, the following manners may be used:

Determining a first type of node from the nodes included in the first domain according to the topology information and the service flow information of the first domain; or

The first type of node is determined from the nodes included in the first domain according to the topology information of the first domain, the service flow information, and the information of the MAP relay node.

Of course, there are other ways in the actual application, which are not carried out here - detailed.

Certainly, before determining the first type of node from the nodes included in the first domain according to the topology information and the service flow information of the first domain, the topology information and the service flow information of the first domain are also determined.

Before determining the first type of node from the nodes included in the first domain according to the topology information of the first domain, the service flow information, and the information of the MAP relay node, determining the topology information and the service flow of the first domain Information, information of the MAP relay node.

In an actual application, there may be a case where a part of the nodes work in a plurality of domains at the same time. In order to facilitate the coordination of the bandwidth resources for the nodes working in the multiple domains, in the embodiment of the present invention, the merge indication message is sent to the first type of node. Previously, it also included the following operations:

Adjusting the transmit clock frequency of the first DM to be synchronized with the transmit clock frequency of the second DM; and/or

The MAC period of the first DM is adjusted to be aligned with the MAC period of the second DM.

In the embodiment of the present invention, the first type of node has multiple forms: for example, the first type of node is a node that belongs to a service flow, and/or provides a MAP relay function for a node that belongs to the service flow.

The first type of node is a node that belongs to the service flow, and/or provides a MAP relay function for the node that belongs to the service flow, and optionally, may be divided into the following types of nodes:

For example, the first type of node is a node that belongs to the service flow and does not provide MAP relay function for other nodes belonging to the service flow; or

For another example, the first type of node is a node that belongs to the service flow and provides MAP relay function for other nodes belonging to the service flow; or

Also for example, the first type of node provides a MAP for nodes that are not part of the service flow that are not part of the service flow. a node of the relay function;

The node belonging to the service flow is a node that is corresponding to the service transmission and is carried by the service flow, and may be a node that initiates the establishment of the service flow, a final destination node of the service flow, or a relay node of the service flow.

In the embodiment of the present invention, when the first type of node is a node that belongs to a service flow and does not provide a MAP relay function to other nodes that belong to the service flow; or, when the first type of node belongs to the service flow, and belongs to the service flow, When the node provides the node of the MAP relay function, the completion merge response message is that any one of the first type of nodes is added to the second domain managed by the second DM, and is returned after establishing the service flow with the second DM;

When the first type of node is a node that does not belong to the service flow and provides the MAP relay function for other nodes that belong to the service flow, the completion of the merge response message is that any one of the first type of nodes is added to the management managed by the second DM. Returned after the second domain.

In the embodiment of the present invention, there are multiple ways to send a merge indication message to a first type of node, and optionally, the following manner may be used:

For example, when the first domain is merged into the second domain, there are three nodes in the first type of node in the first domain, and node 1 is a node that belongs to the service flow and does not provide MAP relay function for other nodes belonging to the service flow (corresponding The node type identifier is "00"), marked as a type I node, and node 2 is a node that belongs to the service flow and provides MAP relay function for other nodes belonging to the service flow (the corresponding node type identifier is "01"), For the class II node, the node 3 is a node that does not belong to the service flow and provides the MAP relay function for other nodes belonging to the service flow (the corresponding node type identifier is "10"), and is marked as the type III node, then, When the merge indication message is sent to the node 1, the merge indication message carries the node type identifier corresponding to the node 1. In this case, the format of the merge indication message is as follows:

Field sub-bit bit description

DM registration identification number 0:5 [47:0] MAC address information of the DM of the second domain Node Type 6 [1:0] The type identifier of the node, set to 00, to indicate that the node reserves 6 for the Type I node [7:2] Reserved bits

When the merge indication message is sent to the node 2, the merge indication message carries the node type identifier corresponding to the node 2, and the format of the merge indication message is as follows:

When the merge indication message is sent to the node 3, the merge indication message carries the node type identifier corresponding to the node 3. In this case, the format of the merge indication message is as follows:

For example, when the first domain is merged into the second domain, the first domain includes the first type node and the second type node, wherein the first type node has three nodes, and the node 1 belongs to the service flow, and the other belongs to the service flow. The node that provides the MAP relay function is labeled as the type I node, the node 2 is the node that belongs to the service flow, and the MAP relay function is provided for other nodes belonging to the service flow, and is marked as the type II node, and the node 3 is not. A node that belongs to a service flow and provides a MAP relay function for other nodes belonging to the service flow, and is marked as a type III node, and a node type identifier corresponding to the second type node is "2", and is marked as a type IV node, then, The broadcast form sends a merge indication message to the three nodes. The process is as follows: When the merge indication message is sent to the node 1, the merge indication message carries the device identifier corresponding to the node 1, the device identifier corresponding to the node 2, and the node 3 Corresponding device identifier, when the merge indication message is sent to the node 2, the device indication corresponding to the node 1 and the device identifier corresponding to the node 2 are carried in the merge indication message. The device identifier corresponding to the node 3, when the merge indication message is sent to the node 1, the node 2, and the node 3, the device identifier corresponding to the node 1 and the device identifier corresponding to the node 2 and the node 3 corresponding to the node indication message are carried in the merge indication message. Device ID. At this time, the format of the merge indication message is as follows: Domain sub-"P bit description

DM registration number 0:5 [47:0] DM MAC address information of the second domain

Number of Class I Nodes 6 [7:0] Number of Class I Nodes

Class I Node 1 7 [7:0] Device ID of the first node in the Type I node

... [7:0] ...

Class I node N Var [7:0] Device ID of the Nth node in the Type I node

Number of nodes in class II 7 [7:0] Number of nodes in class II

n

Class II Node 1 7 [7:0] Device ID of the first node in the Type II node

... [7:0] ...

Class II Node N Variable [7:0] Device ID of the Nth node in the Type II node

Number of nodes in class III 7 [7:0] Number of nodes in class III

n

Class III Node 1 7 [7:0] Device ID of the first node in the Type III node

... [7:0] ...

Class III Node N Variable [7:0] Device ID of the Nth node in the Type III node

Number of nodes in class IV 7 [7:0] Number of nodes in class IV

n

Class IV Node 1 7 [7:0] Device ID of the first node in the Type IV node

... [7:0] ...

Class IV Node N Variable [7:0] Device ID of the Nth Node in the Type IV Node

In order to avoid the service interruption of the node transmission, in the embodiment of the present invention, if the first type of node is a node that belongs to the service flow and provides a MAP relay function for other nodes belonging to the service flow; or, the first type of node is not belonging to the service flow. The node that provides the MAP relay function for other nodes belonging to the service flow further includes the following operations before sending the delocalized message to the first type of node:

Determining that the node exits the first domain has no effect on the service flow in the first domain. In the embodiment of the present invention, after determining the first type of node from the node included in the first domain, the method further includes: using, as the second class, the node other than the first type of node included in the first domain Node; for each node in the second type of node, execute separately:

Sending a delocalized message to the node;

The delocalized message is used to indicate that the node exits the first domain; or the delocalized message is used to indicate that the node exits the first domain and joins the second domain.

That is, for the second type of nodes other than the first type of nodes among the nodes included in the first domain, Since the nodes in the second type of node do not belong to the service flow and are not provided for the nodes belonging to the service flow

a node of the MAP relay function, therefore, for a node in such a node, a delocalized message is directly sent to the node, where the delocalized message is used to indicate that the node exits the first domain; or, the delocalized message is used to indicate the The node exits the first domain and joins the second domain.

Of course, in order to reduce the implementation complexity and the signaling overhead, in the embodiment of the present invention, if the first type of node is a node that belongs to the service flow, before sending the indication message to the node, the method further includes the following operations: determining the node to which the node belongs The priority of the service flow is greater than or equal to the service flow priority threshold. For example, the preset service flow priority threshold is 3, and the service flow to which the node belonging to the service flow belongs has a priority of 2. If the node sends a delocalized message directly, the merge indication message is not sent, and the service flow belongs to the service flow. The priority of the service flow to which the node belongs is 4, then the merge indication message is sent first for such a node, and then the de-message message is sent after receiving the completion merge response message.

In the embodiment of the present invention, the merge indication message is further used to indicate that the first type of node joins the second domain, and establishes a service flow with the second DM of the second domain.

The embodiment of the present invention is mainly based on "sending the de-domain message to the first-type node after receiving the merge completion response message returned by the first-type node", which solves the problems in the background art, and thus solves the problems in the background art. In the embodiment of the present invention, step 630 is performed after step 620, so that the problems in the background art can be solved.

Referring to FIG. 7, in the embodiment of the present invention, a second detailed process of domain merging is applied to a communication network, where the communication network includes at least two domains, and the first domain in at least two domains includes a first DM, and A node managed by a DM, and a second domain of at least two domains includes a second DM, in a specific process:

Step 700: The first type of node in the first domain receives the merge indication message sent by the first DM, where the merge indication message is used to indicate that the first type of node joins the second domain, and the first type of node is the first domain At least one node associated with the service flow;

Step 710: The first type of node joins the second domain according to the merge indication message, and generates a complete merge response message, where the merge response message is used to feedback that the first type of node has joined the second domain; Step 720: The node returns a completion merge response message to the first DM. The first type of node has various forms: For example, the first type of node is a node that belongs to a service flow, and/or provides a MAP relay function for a node that belongs to the service flow.

Also for example, the first type of node is a node that does not belong to the service flow and provides a MAP relay function for other nodes belonging to the service flow;

In the embodiment of the present invention, there are multiple ways for the first type of node to receive the merge indication message sent by the first DM, and optionally, the following manner can be used:

The first type of node receives a merge indication message for itself; or

The first type of node receives the merge indication message sent by the first DM sent in broadcast form. In the embodiment of the present invention, after receiving the merge indication message sent by the first DM, the first type of node further includes the following operations before returning the completion merge response message to the first DM:

When the first type of node is a node that belongs to the service flow and does not provide the media access plan MAP relay function for other nodes belonging to the service flow; or, for the service flow, provides the MAP relay function for other nodes belonging to the service flow. At the time of the node, the first type of node establishes a service flow with the second DM.

In the embodiment of the present invention, after the first type of node returns the completion merge response message to the first DM, the method further includes the following operations:

The first type of node receives the delocalized message returned by the first DM and exits the first domain according to the delocalized message. For a better understanding of the embodiments of the present invention, a specific application scenario is given below, and a further detailed description is made for the process of domain merging, as shown in FIG. 8:

The first domain managed by DM1 is to be merged into the second domain managed by DM2, where node 1 and Node 2 and node 3 belong to the first domain, where node 1 is a node that belongs to the service flow and does not provide MAP relay function for other nodes belonging to the service flow; node 3 belongs to the service flow and belongs to other nodes belonging to the service flow. A node that provides a MAP relay function, and node 2 belongs to a second type of node.

Step 800: The DM1 adjusts the transmit clock frequency of the DM1 to be synchronized with the transmit clock frequency of the DM2; and adjusts the MAC period of the DM2 to be aligned with the MAC cycle of the DM2;

Step 810: The DM1 sends a merge indication message to the node 1 and the node 3 in a broadcast form, and directly sends the delocalization message to the node 2;

In this step, the merge indication message carries the node type identifier corresponding to the node 1 and the node type identifier corresponding to the node 3.

Step 820: The DM1 receives the completion merge response message returned by the node 1 and the node 3 respectively; Step 830: The DM1 sends the delocalization message to the node 1, and when it is determined that the node 3 exits the first domain and has no influence on the service flow in the first domain, Send a delocalized message to node 3.

In summary, in the embodiment of the present invention, a domain merging method is provided, where the method is applied to a communication network, where the communication network includes at least two domains, and the first domain in at least two domains includes a first DM, and The node managed by the first DM, the second domain in the at least two domains includes a second DM, and the first type of node is determined from the nodes included in the first domain managed by the first DM, where the first type of node is a node associated with the at least one service flow of the first domain; sending a merge indication message to the first type of node, the merge indication message is used to indicate that the first type of node joins the second domain; and receiving the completed merge response returned by the first type of node The message, the completion merge response message is used to feed back the first type of node to join the second domain. In this solution, when the DM is to be merged into other domains, the DM is first associated with at least one service flow of the first domain. The first type of node sends a merge indication message, and when the first type of node returns the completion merge response message, the off-domain message is sent to the first type node, thereby avoiding the defect of the service transmission interruption.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, a special purpose computer, an embedded processor or other programmable data processing device to produce a machine The instructions executed by a processor of a computer or other programmable data processing device generate means for implementing the functions in one or more blocks of the flowchart or in a flow or block of the flowchart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus functions in one or more blocks of a flow or a flow diagram and/or block diagram of a flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions in one or more blocks of the flowchart or in a flow or block of the flowchart.

Although the preferred embodiment of the invention has been described, it will be apparent to those skilled in the < Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and modifications The spirit and scope of the embodiments of the present invention are departed. Thus, it is intended that the present invention cover the modifications and modifications of the embodiments of the invention.

Claims

Rights request

A domain master node, the domain master node DM belongs to a first domain of a communication network, the first domain includes the DM, and a node managed by the DM, and the communication network further includes a second domain, The second domain includes another DM, where the DM includes:

a processing unit, configured to determine a first type of node from a node included in a first domain managed by the DM, where the first type of node is a node associated with at least one service flow of the first domain ;

The domain master node according to claim 1, wherein the processing unit is configured to: determine, according to the topology information and the service flow information of the first domain, from nodes included in the first domain The first type of node is out.

3. The domain master node according to claim 1 or 2, wherein the first type of node determined by the processing unit belongs to a service flow, and/or provides a media access plan MAP relay for a node belonging to the service flow. Functional node.

The domain master node according to claim 3, wherein the first type of node determined by the processing unit is a MAP relay function that belongs to the service flow and does not provide other nodes belonging to the service flow. Node; or

The first type of node is a node that does not belong to the service flow and provides a MAP relay function for other nodes belonging to the service flow; The node belonging to the service flow is a node that is carried by the service flow for a corresponding service transmission.

The domain master node according to claim 4, wherein when the first type of node is a node that belongs to a service flow and does not provide a MAP relay function for other nodes belonging to the service flow; When a type of node is a node that belongs to a service flow and provides a MAP relay function for other nodes belonging to the service flow, the completion merge response message received by the receiving unit is that any one of the first type of nodes is added to The second domain managed by the another DM, and returned after establishing a service flow with the another DM;

The domain master node according to any one of claims 1 to 5, wherein the sending unit is specifically configured to:

The domain master node according to any one of claims 4-6, wherein the processing unit is further configured to:

The domain master node according to any one of claims 4 to 7, wherein, if the first type of node is a node belonging to a service flow, the processing unit is further configured to:

Determine that the priority of the service flow to which the node belongs is greater than or equal to the service flow priority threshold.

A node, the node belongs to a first domain of a communication network, the node is managed by a first domain master node DM of the first domain, and the communication network further includes a second domain, the second The domain includes a second DM, where the node includes:

a receiving unit, configured to receive a merge indication message sent by the first DM, where And indicating that the message is used to indicate that the node joins to the second domain;

10. The node of claim 9, wherein the node is a node belonging to the service flow, and/or providing a media access plan MAP relay function for a node belonging to the service flow.

The node according to claim 9 or 10, wherein the node is a node that belongs to the service flow and does not provide a MAP relay function for other nodes belonging to the service flow; or

The node according to claim 11, wherein the processing unit is further configured to: when the class node is a node that belongs to a service flow and does not provide a MAP relay function for other nodes that belong to the service flow; or When a node belonging to a service flow and providing a MAP relay function for other nodes belonging to the service flow, a service flow is established with the second DM.

The node according to any one of claims 9 to 12, wherein the receiving unit is further configured to receive a delocalized message returned by the first DM;

14. A method of domain merging, applied to a communication network, the communication network comprising at least two domains, the first domain in the at least two domains comprising a first domain master node DM, and the first DM office The managed node, the second domain in the at least two domains, including the second DM, the method includes: determining, by the node included in the first domain managed by the first DM, the first type of node, where The first type of node is a node associated with at least one service flow of the first domain; Sending a merge indication message to the first type of node, where the merge indication message is used to indicate that the first type of node has joined the second domain;

The method of claim 14, wherein the determining the first type of nodes from the nodes included in the first domain managed by the first DM comprises:

The method according to claim 14 or 15, wherein the first type of node is a node belonging to a service flow, and/or providing a media access plan MAP relay function for a node belonging to the service flow.

The method according to claim 16, wherein the first type of node is a node that belongs to the service flow and does not provide a MAP relay function for other nodes belonging to the service flow; or the a type of node is a node that belongs to the service flow and provides a MAP relay function for other nodes belonging to the service flow; or

18. The method according to claim 17, wherein: when the first type of node is a node that belongs to a service flow and does not provide a MAP relay function for other nodes belonging to the service flow; or, when the first type When the node is a node that belongs to the service flow and provides the MAP relay function for other nodes belonging to the service flow, the completion merge response message is that the node of the first type of node is added to the second DM. a second domain, and returned after establishing a service flow with the second DM;

When the first type of node is not belonging to the service flow, providing MAP for other nodes belonging to the service flow When the node of the relay function is used, the completion merge response message is returned after any node of the first type of node joins the second domain managed by the second DM.

The method according to any one of claims 14 to 18, wherein the sending the merge indication message to the first type of node includes:

The method according to any one of claims 17 to 19, wherein, if the first type of node is a node that belongs to a service flow and provides a MAP relay function for other nodes belonging to the service flow; The node of the first type is a node that does not belong to the service flow and provides the MAP relay function for the other node that belongs to the service flow. Before sending the de-local message to the first-type node, the method further includes:

The method according to any one of claims 17 to 20, wherein, if the first type of node is a node that belongs to a service flow, before sending the indication message to the node, the method further includes:

22. A method of domain merging, applied to a communication network, the communication network comprising at least two domains, the first domain in the at least two domains comprising a first domain master node DM, and the first DM office The managed node, the second domain in the at least two domains, including the second DM, the method includes: receiving, by the first type of node in the first domain, a merge indication message sent by the first DM, where the merging The indication message is used to indicate that the first type of node joins the second domain, and the first type of node is a node that is associated with at least one service flow of the first domain;

The method of claim 22, wherein the first type of node belongs to the A service flow, and/or a node that provides media access plan MAP relay functionality for nodes belonging to the service flow.

The method according to claim 22 or 23, wherein the first type of node is a node that belongs to the service flow and does not provide a MAP relay function for other nodes belonging to the service flow; or

The method of claim 24, wherein: after receiving the merge indication message sent by the first DM, the first type of node, before returning the completion merge response message to the first DM, further includes:

The method according to any one of claims 22-25, wherein, after the first type of node returns a complete merge response message to the first DM, the method further includes: