CN105453500A - Domain merging method, domain master node and node - Google Patents
Domain merging method, domain master node and node Download PDFInfo
- Publication number
- CN105453500A CN105453500A CN201480007120.2A CN201480007120A CN105453500A CN 105453500 A CN105453500 A CN 105453500A CN 201480007120 A CN201480007120 A CN 201480007120A CN 105453500 A CN105453500 A CN 105453500A
- Authority
- CN
- China
- Prior art keywords
- node
- service flow
- domain
- nodes
- class
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
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
Domain merging method, domain master node and node technical field
The invention relates to the technical field of communication, in particular to a domain merging method, a domain master node and a class node. Background
With the development of communication technology and the popularization of network technology, the importance of home networks is increasingly highlighted. The home network may include one or more domains (domains), where a network formed by a DM and all other nodes registered to the DM is called a Domain, each Domain is a centralized management network, each Domain has a DM (Domain Master) DM for managing other nodes in the Domain, and the nodes have various forms, such as a home gateway, a power modem, or a set-top box, a smart television, and the like.
The DM has, in addition to the communication function of the common node, a management function in charge of the entire domain, for example: establishment of a domain, registration of nodes included in the domain, bandwidth allocation and resource scheduling of the domain, coordination with multiple neighboring domains or networks, network power consumption management, and the like.
In order to improve the Security of data transmitted in the domain, the domain operating in the Security mode further includes an SC (Security Controller), the SC is responsible for authentication of nodes in the domain and management of a key management process, and each registered node can acquire a key after completing authentication with the SC to transmit data, thereby improving the Security of data transmission.
DM performs domain management and resource scheduling by transmitting a MAP (Media Access Plan) frame every MAC (Media Access Control) period, a node discovers the existence of a domain by detecting the MAP frame, joins the domain by transmitting a registration request to DM, authenticates SC after the registration is successful in order to improve the security of transmitted data, and can start data transmission after the authentication is successful.
In order to guarantee QoS (Quality of Service), a node needs to apply for establishing a Service flow to a DM, and if the DM can support establishment of the Service flow, the node agrees to the application, and performs resource scheduling according to Traffic Specification (TSpec) after the Service flow is established. The DM may adopt persistent scheduling or non-persistent scheduling, where the persistent scheduling is that the resource scheduling information issued by the DM is valid in a plurality of MAC periods, and the non-persistent scheduling is that the resource scheduling information issued by the DM is valid only in a next MAC period.
For example: a node(s) in a domain that is working detects MAP-D (Media Access Plan-Default)/RMAP-D from another domain
(MediｃA Access Plan-Default for Forward) frame or MAP-A (MediｃA Access Plan-Active)/RMAP-A
A (forwarded Media Access Plan-Active) frame, and the domain name of the other domain is the same as the domain name of the domain where the node is located, the two domains need to be merged.
For example: as shown in fig. 1A, originally there are only 1 domain: domain 1, domain 1 includes DM and node Nl, node N2, node N3, node N4, and node N5, but because the channel between DM and node N2 changes or other reasons, DM cannot detect the existence of node N2, and cannot directly communicate, according to the current regulations, original domain 1 is divided into two domains: domain 2 and domain 3, node N2, node N3, and node N4 will perform DM restoration, and one of the nodes N2, node N3, and node N4 with DM capability will become a newly formed DM in domain 3 (node N2 in the figure). If node N2 can again hear the MAP-D/RMAP-D frame or the MAP-A/RMAP-A frame sent by DM, then domain 2 and domain 3 need to be merged.
Another example is: as shown in fig. 1B, originally there are only 1 domain: domain 1, domain 1 includes DM and node Nl, node N2, node N3, node N4, and node N5, but because DM is offline, two parts that cannot be connected are formed, a part formed by node N1 and node N5, and a part formed by node N2, node N3, and node N4, according to the current regulations, original domain 1 is divided into two domains: domain 2 and domain 3, node N2, node N3, and node N4 will recover DM, and one of node N2, node N3, and node N4 with DM capability will become DM in newly formed domain 3 (node N2 in the figure). The node N1 and the node N5 also recover the DM, and one of the nodes N1 and N5 that has the DM capability will become ｃA newly formed DM (in the figure, the node N1) in the domain 2, and when the original DM comes online again, the node will join one of the domains, and if the nodes in the other domain can again listen to the MAP-D/RMAP-D frame or the MAP- ｃA/RMAP- ｃA frame sent by the DM, the domain 2 and the domain 3 need to be merged.
In the prior art, when domain merging is performed, a node in a domain has a defect that service transmission carried by a service flow is interrupted. As shown in fig. 1A, if domain 3 is to be merged into domain 2, N2 sends a logout message to N3 and N4, and N3 and N4 leave domain 3 and join domain 2, at which time the service flow between the nodes of domain 3 will be disconnected and the traffic carried by the service flow will be interrupted.
In summary, the current domain merging method has the defect of service transmission interruption. Disclosure of Invention
The embodiment of the invention provides a domain merging method, a domain master node and a node, which are used for solving the problem of service transmission interruption in the existing domain merging process.
In a first aspect, a domain master node DM is provided, which belongs to a first domain of a communication network, the first domain including the DM and nodes managed by the DM, the communication network further including a second domain including another DM, the DM comprising: a processing unit, configured to determine a first type of node from nodes 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;
a sending unit, configured to send a merge indication message to the first class node, where the merge indication message is used to indicate that the first class node joins the second domain;
a receiving unit, configured to receive a completion merging response message returned by the first-class node, where the completion merging response message is used to feed back that the first-class node has been added to the second domain;
the sending unit is further configured to send a delocalization message to the first-class node, where the delocalization message is used to instruct the first-class node to exit the first domain.
With reference to the first aspect, in a first possible implementation manner, the processing unit is specifically configured to: and 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.
With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, the first class node determined by the processing unit is a node that belongs to a service flow and/or provides a medium 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 class node determined by the processing unit 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
The first type of node is a node which belongs to the service flow and provides an MAP relay function for other nodes belonging to the service flow; or
The first type of node is a node which does not belong to the service flow and provides an MAP relay function for other nodes belonging to the service flow;
wherein the nodes belonging to the service flow are nodes for which the corresponding service is transmitted and 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 that belong to the service flow; or, when the first-class node is a node that belongs to a service flow and provides an MAP relay function for other nodes that belong to the service flow, the completion merging response message received by the receiving unit is returned after any one node in the first-class node joins a second domain managed by the other DM and establishes a service flow with the other DM;
when the first-class node is a node that does not belong to a service flow and provides an MAP relay function for other nodes belonging to the service flow, the completion combining response message received by the receiving unit is returned by any one of the first-class nodes 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:
aiming at each node in the first class of nodes, sending a merging indication message carrying a node type identifier of the node to the node; or
And sending a merging indication message carrying node type identifiers respectively corresponding to the nodes to each node in the first class of nodes in a broadcasting mode.
With reference to the third to fifth possible implementation manners of the first aspect, in a sixth possible implementation manner, the processing unit is further configured to:
determining that a first class of nodes exiting the first domain has no impact on service flows in the first domain.
With reference to the third to sixth possible implementation manners of the first aspect, in a seventh possible implementation manner, if the first class node is a node belonging to a service flow, the processing unit is further configured to:
and determining that the priority of the service flow to which the node belongs is greater than or equal to a service flow priority threshold value. In a second aspect, a node is provided, belonging to a first domain of a communication network, said node being managed by a first domain master node DM of said first domain, said communication network further comprising a second domain, said second domain comprising a second DM, characterized in that said node comprises:
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 join the node to the second domain according to the merge indication message, and generate a merge completion response message, where the merge completion response message is used to feed back that the node has joined the second domain;
a sending unit, configured to send the completion coalescing response message to the first DM.
With reference to the second aspect, in a first possible implementation manner, the node is a node that belongs to the service flow and/or provides a medium 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 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
The node provides MAP relay function for other nodes belonging to the service flow; or
The node is a node which does not belong to the service flow and provides an MAP relay function for other nodes belonging to the service flow;
wherein the nodes belonging to the service flow are nodes for which the corresponding service is transmitted and carried by the service flow.
With reference to the second possible implementation manner of the second aspect, in a third possible implementation manner, the processing unit is further configured to: when the class node is a node which belongs to the service flow and does not provide the MAP relay function for other nodes which belong to the service flow; or, when a node providing the MAP relay function is provided for a node belonging to a service flow and 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 manner, the receiving unit is further configured to receive a delocalization message returned by the first DM;
the processing unit is further configured to exit the first domain according to the delocalization message.
In a third aspect, a method for domain mergence is provided, which is applied to a communication network including at least two domains, a first domain of the at least two domains includes a first domain master node DM and a node managed by the first DM, and a second domain of the at least two domains includes a second DM, and the method includes:
determining a first type of node from nodes included in a first domain managed by a 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 class node, where the merge indication message is used to indicate that the first class node has joined to the second domain;
receiving a completion combination response message returned by the first-class node, wherein the completion combination response message is used for feeding back that the first-class node is added to the second domain;
and sending a delocalization message to the first class of nodes, wherein the delocalization message is used for indicating the first class of nodes to exit the first domain.
With reference to the third aspect, in a first possible implementation manner, determining a first class node from nodes included in a first domain managed by a first DM includes:
and 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.
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 node is a node that belongs to a service flow and/or provides a medium access plan MAP relay function for a node that belongs to the service flow.
With reference to the second possible implementation manner of the third aspect, in a third possible implementation manner, the first 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
The first type of node is a node which belongs to the service flow and provides an MAP relay function for other nodes belonging to the service flow; or
The first type of node is a node which does not belong to the service flow and provides an MAP relay function for other nodes belonging to the service flow;
wherein the nodes belonging to the service flow are nodes for which the corresponding service is transmitted and carried by the service flow.
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 that belong to the service flow; or, when the first type node is a node that belongs to a service flow and provides an MAP relay function for other nodes that belong to the service flow, the completion merge response message is returned after any one node in the first type node joins a second domain managed by a second DM and establishes a service flow with the second DM;
when the first-class node is a node that does not belong to a service flow and provides an MAP relay function for other nodes belonging to the service flow, the completion-merging response message is returned after any one node in the first-class node joins a second domain managed by a second DM.
With reference to the third aspect, or the first to fourth possible implementation manners of the third aspect, in a fifth possible implementation manner, the sending a merge indication message to the first class node specifically includes: aiming at each node in the first class of nodes, sending a merging indication message carrying a node type identifier of the node to the node; or
And sending a merging indication message carrying node type identifiers respectively corresponding to the nodes to each node in the first class of nodes in a broadcasting mode.
With reference to the third to fifth possible implementation manners of the third aspect, in a sixth possible implementation manner, if the first type node is a node that belongs to a service flow and provides an MAP relay function for other nodes that belong to the service flow; or, the first type of 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, and before sending the delocalization message to the first type of node, the method further includes: determining that a first class of nodes exiting the first domain has no impact on service flows 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 node is a node belonging to a service flow, before sending a combined indication message to the node, the method further includes:
and determining that the priority of the service flow to which the node belongs is greater than or equal to a service flow priority threshold value. In a fourth aspect, a method for domain mergence is provided, which is applied to a communication network including at least two domains, a first domain of the at least two domains includes a first domain master node DM and a node managed by the first DM, and a second domain of the at least two domains includes a second DM, and the method includes:
a first-class node in a first domain receives a merge indication message sent by a first DM, wherein the merge indication message is used for indicating the first-class node to join the second domain, and the first-class node is a node associated with at least one service flow of the first domain;
the first class node joins the second domain according to the merging indication message and generates a merging completion response message, wherein the merging completion response message is used for feeding back that the first class node is joined to the second domain;
the first type 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 medium 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 manner, the first type 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
The first type of node is a node which belongs to the service flow and provides an MAP relay function for other nodes belonging to the service flow; or
The first type of node is a node which does not belong to the service flow and provides an MAP relay function for other nodes belonging to the service flow;
wherein the nodes belonging to the service flow are nodes for which the corresponding service is transmitted and carried by the service flow.
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, before returning a merge completion response message to the first DM, the method further includes:
when the first type of node belongs to the service flow and does not provide the node with the media access plan MAP relay function for other nodes belonging to the service flow; or, when the node provides the MAP relay function for the node belonging to the service flow and other nodes belonging to the service flow, the first class node and the second DM establish the service flow.
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 returning, by the first class node, a completion merge response message to the first DM, the method further includes:
and the first class node receives the delocalization message returned by the first DM and exits the first domain according to the delocalization message.
The embodiment of the invention is applied to a communication network, which comprises at least two domains, wherein a first domain of the at least two domains comprises a first DM and nodes managed by the first DM, a second domain of the at least two domains comprises a second DM, and a first type of nodes are determined from the nodes managed by the first DM, wherein the first type of nodes are nodes associated with at least one service flow of the first domain; sending a merging indication message to the first-class node, wherein the merging indication message is used for indicating the first-class node to join the second domain; in the scheme, when DM needs to be merged into other domains, a merging indication message is sent to a first-class node in the domain, which is associated with at least one service flow of the first domain, first, and when the first-class node returns a merging completion response message, a delocalization message is sent to the first-class node, so that the defect of service transmission interruption is avoided. Drawings
FIG. 1A is a first diagram of domain decomposition in the prior art;
FIG. 1B is a second schematic diagram of domain decomposition in the prior art, FIG. 2 is a functional structure diagram of a DM in the implementation of the present invention;
FIG. 3 is a schematic diagram of the physical structure of a DM in accordance with the present invention;
FIG. 4 is a functional block diagram of a node in accordance with the present invention;
FIG. 5 is a schematic physical structure diagram of a node in the practice of the present invention;
FIG. 6 is a first detailed flow chart of domain merging in the implementation of the present invention;
FIG. 7 is a second detailed flow chart of domain merging in the implementation of the present invention;
fig. 8 is an embodiment of domain merging in the practice of the present invention. Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, 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 merely an association describing an associated object, indicating that three relationships may exist, e.g., a and/or B, may indicate: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the letter "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.
The preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings, it being understood that the preferred embodiments described herein are merely for illustrating and explaining the present invention and are not intended to limit the present invention, and that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
Based on the above technical solution, referring to fig. 2, an embodiment of the present invention provides a schematic functional structure diagram of a domain master node DM, where the domain master node DM belongs to a first domain of a communication network, the first domain includes a DM and nodes managed by the DM, the communication network further includes a second domain, the second domain includes another DM, the DM includes a processing unit 20, a sending unit 21, and a receiving unit 22, where:
a processing unit 20, configured to determine a first type of node from nodes included in a first domain managed by a DM, where the first type of node is a node associated with at least one service flow of the first domain; a sending unit 21, configured to send a merge indication message to the first-class node, where the merge indication message is used to indicate that the first-class node joins the second domain;
a receiving unit 22, configured to receive a completion merging response message returned by the first-class node, where the completion merging response message is used to feed back that the first-class node has been added to the second domain;
the sending unit 21 is further configured to send a delocalization message to the first-class node, where the delocalization message is used to instruct the first-class node to exit the first domain.
In this embodiment of the present invention, optionally, the processing unit 20 is specifically configured to:
and 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.
In this embodiment of the present invention, optionally, the first type node determined by the processing unit 20 is a node belonging to a service flow, and/or a node providing a medium access plan MAP relay function for a node belonging to a service flow.
In this embodiment of the present invention, optionally, the first type node determined by the processing unit 20 is a node that belongs to a service flow and does not provide an MAP relay function for other nodes that belong to the service flow; or
The first type of nodes are nodes which belong to service flows and provide MAP relay functions for other nodes which belong to the service flows; or
The first type of nodes are nodes which do not belong to the service flow and provide the MAP relay function for other nodes belonging to the service flow;
wherein, the nodes belonging to the service flow are the nodes which are carried by the service flow for the corresponding service transmission.
In the embodiment of the present invention, further, when the first type node is a node that belongs to a service flow and does not provide an MAP relay function for other nodes that belong to the service flow; or, when the first-class node is a node that belongs to a service flow and provides an MAP relay function for other nodes that belong to the service flow, the receiving unit 22 receives the completion merging response message that is returned after any one node in the first-class node joins a second domain managed by another DM and establishes a service flow with another DM;
when the first-class 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 combining response message received by the receiving unit 22 is returned by any one of the first-class nodes after joining the second domain managed by another DM. In this embodiment of the present invention, optionally, the sending unit 21 is specifically configured to:
aiming at each node in the first class of nodes, sending a merging indication message carrying a node type identifier of the node to the node; or
And sending a merging indication message carrying the node type identifiers respectively corresponding to the nodes to each node in the first class of nodes in a broadcasting mode.
In this embodiment of the present invention, the processing unit 20 is further configured to:
determining that the exit of the first type of node from the first domain has no impact on the service flow in the first domain.
In this embodiment of the present invention, further, if the first type node is a node belonging to a service flow, the processing unit 20 is further configured to:
and determining that the priority of the service flow to which the node belongs is greater than or equal to a service flow priority threshold value. As shown in fig. 3, a diagram of an entity apparatus of a DM according to an embodiment of the present invention is provided, where the domain master node DM belongs to a first domain of a communication network, the first domain includes a DM and nodes managed by the DM, the communication network further includes a second domain, the second domain includes another DM, and the entity apparatus includes a signal receiver 30, a signal transmitter 31 and a processor 32, where:
a processor 32, configured to determine a first type of node from nodes 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;
a signal transmitter 31, configured to transmit a merge indication message to the first-class node, where the merge indication message is used to indicate that the first-class node joins the second domain;
the signal receiver 30 is configured to receive a completion combining response message returned by the first-class node, where the completion combining response message is used to feed back that the first-class node has been added to the second domain;
the signal transmitter 31 is further configured to transmit a delocalization message to the first-class node, where the delocalization message is used to instruct the first-class node to exit the first domain.
In this embodiment of the present invention, optionally, the processor 32 is specifically configured to:
and 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.
In this embodiment of the present invention, optionally, the first type node determined by the processor 32 is a node belonging to a service flow, and/or a node providing a medium access plan MAP relay function for a node belonging to a service flow. In this embodiment of the present invention, optionally, the first type of node determined by the processor 32 is a node that belongs to a service flow and does not provide an MAP relay function for other nodes that belong to the service flow; or
The first type of nodes are nodes which belong to service flows and provide MAP relay functions for other nodes which belong to the service flows; or
The first type of nodes are nodes which do not belong to the service flow and provide the MAP relay function for other nodes belonging to the service flow;
wherein, the nodes belonging to the service flow are the nodes which are carried by the service flow for the corresponding service transmission.
In the embodiment of the present invention, further, when the first type node is a node that belongs to a service flow and does not provide an MAP relay function for other nodes that belong to the service flow; or, when the first-class node is a node that belongs to a service flow and provides an MAP relay function for other nodes that belong to the service flow, the completion combining response message received by the signal receiver 30 is returned after any one node in the first-class node joins a second domain managed by another DM and establishes a service flow with another DM;
when the first-class 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 combining response message received by the signal receiver 30 is returned by any one of the first-class nodes after joining the second domain managed by another DM.
In this embodiment of the present invention, optionally, the signal transmitter 31 is specifically configured to:
aiming at each node in the first class of nodes, sending a merging indication message carrying a node type identifier of the node to the node; or
And sending a merging indication message carrying the node type identifiers respectively corresponding to the nodes to each node in the first class of nodes in a broadcasting mode.
In this embodiment of the present invention, further, the processor 32 is further configured to:
determining that the exit of the first type of node from the first domain has no impact on the service flow in the first domain.
In this embodiment of the present invention, further, if the first type node is a node belonging to a service flow, the processor 32 is further configured to:
and determining that the priority of the service flow to which the node belongs is greater than or equal to a service flow priority threshold value. Based on the above technical solution, referring to fig. 4, an embodiment of the present invention provides a functional structure schematic diagram of a node, where 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, the communication network further includes a second domain, the second domain includes a second DM, the node includes a receiving unit 40, a processing unit 41, and a sending unit 42, where:
a receiving unit 40, configured to receive a merge indication message sent by the first DM, where the merge indication message is used to indicate that a node joins the second domain;
a processing unit 41, configured to add the merging indication message to the second domain and generate a merging completion response message, where the merging completion response message is used to feed back that the node has added to the second domain;
a transmitting unit 42 for transmitting a completion combining response message to the first DM.
In the embodiment of the present invention, optionally, the node is a node belonging to a service flow and/or providing a medium access plan MAP relay function for the node belonging to the service flow.
In the embodiment of the present invention, optionally, the node is a node that belongs to a service flow and does not provide an MAP relay function for other nodes that belong to the service flow; or
The node provides the MAP relay function for the nodes belonging to the service flow and other nodes belonging to the service flow; or
The node provides the MAP relay function for the nodes which do not belong to the service flow and other nodes which belong to the service flow;
wherein, the nodes belonging to the service flow are the nodes which are carried by the service flow for the corresponding service transmission.
In this embodiment of the present invention, further, the processing unit 41 is further configured to: when the class node is a node which belongs to the service flow and does not provide the MAP relay function for other nodes which belong to the service flow; or, when the node providing the MAP relay function is a node belonging to the service flow and providing the MAP relay function to another node belonging to the service flow, the service flow is established with the second DM.
As shown in fig. 5, a physical device diagram of a node is provided in an embodiment of the present invention, 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, the communication network further includes a second domain, 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:
a signal receiver 50, 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 instruction message, and generate a merge completion response message, where the merge completion response message is used to feed back that the node has joined the second domain; a signal transmitter 51 for transmitting a completion combining response message to the first DM.
In the embodiment of the present invention, optionally, the node is a node belonging to a service flow and/or providing a medium access plan MAP relay function for the node belonging to the service flow.
In the embodiment of the present invention, optionally, the node is a node that belongs to a service flow and does not provide an MAP relay function for other nodes that belong to the service flow; or
The node provides the MAP relay function for the nodes belonging to the service flow and other nodes belonging to the service flow; or
The node provides the MAP relay function for the nodes which do not belong to the service flow and other nodes which belong to the service flow;
wherein, the nodes belonging to the service flow are the nodes which are carried by the service flow for the corresponding service transmission.
In this embodiment of the present invention, further, the processor 52 is further configured to: when the class node is a node which belongs to the service flow and does not provide the MAP relay function for other nodes which belong to the service flow; or, when the node providing the MAP relay function is provided for a node belonging to the service flow and other nodes belonging to the service flow, the service flow is established with the second DM.
The first detailed flow application provided below is applied to a communication network including at least two domains, a first domain of the at least two domains including a first DM and a node managed by the first DM, and a second domain of the at least two domains including a second DM.
Referring to fig. 6, in the embodiment of the present invention, a first detailed flow of domain merging is as follows: step 600: determining a first type of node from nodes included in a first domain managed by a first DM, wherein the first type of node is a node associated with at least one service flow of the first domain;
determining a first type of node from nodes included in a first domain according to the topological information and the service flow information of the first domain; or
And determining a first type of node from the nodes included in the first domain according to the topology information, the service flow information and the information of the MAP relay node of the first domain.
Of course, in practical applications, there are other ways, which will not be described in detail herein.
Of course, 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 a first type of node from the nodes included in the first domain according to the topology information, the service flow information and the information of the MAP relay node of the first domain, the topology information, the service flow information and the information of the MAP relay node of the first domain are also determined.
In practical application, there may be a case where part of nodes operate in multiple domains simultaneously, and in order to facilitate coordination of bandwidth resources for nodes operating in multiple domains, in this embodiment of the present invention, before sending the merge indication message to the first type of node, the following operations are further included:
adjusting a transmission clock frequency of the first DM to be synchronous with a transmission 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 invention, the first type of nodes have various forms: for example, the first type of node is a node belonging to a service flow and/or providing a MAP relay function for nodes belonging to a service flow.
When the first type of node is a node belonging to a service flow and/or providing an MAP relay function for a node belonging to the service flow, optionally, the first type of node may be divided into at least the following nodes:
for example, the first type of node is a node belonging to a service flow and not providing a MAP relay function for other nodes belonging to the service flow; or
For another example, the first type node is a node belonging to a service flow and providing a MAP relay function for other nodes belonging to the service flow; or
For example, the first type node provides a MAP relay function for other nodes that do not belong to the service flow;
the node belonging to the service flow is a node for transmitting the service flow carried by the corresponding service, and specifically may be a node for initiating 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 invention, when the first type of node is a node which belongs to the service flow and does not provide the MAP relay function for other nodes which belong to the service flow; or, when the first-class node is a node that belongs to the service flow and provides the MAP relay function for other nodes that belong to the service flow, the completion of the merging response message is returned after any one node in the first-class node joins the second domain managed by the second DM and establishes the service flow with the second DM;
when the first-class node is a node which does not belong to the service flow and provides the MAP relay function for other nodes belonging to the service flow, the completion of the merging response message is returned after any one node in the first-class node is added into the second domain managed by the second DM.
In the embodiment of the present invention, there are various ways to send the merge indication message to the first-class node, and optionally, the following ways may be adopted:
aiming at each node in the first class of nodes, sending a merging indication message carrying a node type identifier of the node to the node; or
And sending a merging indication message carrying the node type identifiers respectively corresponding to the nodes to each node in the first class of nodes in a broadcasting mode.
For example: when a first domain is merged into a second domain, three nodes are in a first class of nodes of the first domain, wherein a node 1 is a node (corresponding node type is marked as '00') which belongs to a service flow and does not provide a MAP relay function for other nodes belonging to the service flow, is marked as a class I node, a node 2 is a node (corresponding node type is marked as '01') which belongs to the service flow and provides a MAP relay function for other nodes belonging to the service flow, is marked as a class II node, and a node 3 is a node (corresponding node type is marked as '10') which does not belong to the service flow and provides the MAP relay function for other nodes belonging to the service flow, is marked as a class III node, so that when a merging indication message is sent to the node 1, the merging indication message carries a node type identification corresponding to the node 1, at this time, the format of the merge indication message is as follows:
bit description under field
DM registration identification number 0:5 [47:0] MAC address information node type 6 [ 1: 0 type identification of node set to 00 for indicating node to reserve 6 [7:2] reserved bit for I type node
When sending the merge instruction message to the node 2, the merge instruction message carries the node type identifier corresponding to the node 2, and at this time, the format of the merge instruction message is as follows:
when sending the merge instruction message to the node 3, the merge instruction message carries the node type identifier corresponding to the node 3, and at this time, the format of the merge instruction message is as follows:
for example: when a first domain is merged into a second domain, the first domain comprises nodes of a first type and nodes of a second type, wherein, there are three nodes in the first class of nodes, where node 1 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, and is labeled as a class I node, node 2 is a node that belongs to the service flow and provides a MAP relay function for other nodes that belong to the service flow, and is labeled as a class II node, node 3 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, and is labeled as a class III node, and the node type identifier corresponding to the second class node is "2" and is labeled as a class IV node, then when sending a merge indication message to these three nodes in a broadcast form, the process is as follows: when sending a merge indication message to a node 1, what is carried in the merge indication message is an equipment identifier corresponding to the node 1, an equipment identifier corresponding to the node 2, and an equipment identifier corresponding to the node 3, when sending the merge indication message to the node 2, what is carried in the merge indication message is an equipment identifier corresponding to the node 1, an equipment identifier corresponding to the node 2, and an equipment identifier corresponding to the node 3, and when sending the merge indication message to the node 1, the node 2, and the node 3, what is carried in the merge indication message is an equipment identifier corresponding to the node 1, an equipment identifier corresponding to the node 2, and an equipment identifier corresponding to the node 3, and at this time, the format of the merge indication message is as follows: field sub "P bit description
MAC address information of DM registration identification number 0:5 [47:0] second domain
Number of class I nodes 6 [7:0] number of class I nodes
Class I node 17 [7:0] device identification of the 1 st node in the class I node
... ... [7:0] ...
Class I node N Var [7:0] device identification of Nth node of class I nodes
Number of class II nodes 7 [7:0] number of class II nodes
n
Class II node 17 [7:0] device identification of the 1 st node of the class II nodes
... ... [7:0] ...
Class II node N variable [7:0] device identification of Nth node of class II nodes
Number of class III nodes 7 [7:0] number of class III nodes
n
Class III node 17 [7:0] device identification of the 1 st node in the class III node
... ... [7:0] ...
Class III node N variable [7:0] device identification of Nth node of class III nodes
Number of class IV nodes 7 [7:0] number of class IV nodes
n
Class IV node 17 [7:0] device identification of the 1 st node in the class IV node
... ... [7:0] ...
Class IV node N variable [7:0] device identification of Nth node of class IV nodes
In order to avoid service interruption of node transmission, in the embodiment of the present invention, if a first type node is a node that belongs to a service flow and provides an MAP relay function for other nodes that belong to the service flow; or, the first type of node is a node which does not belong to the service flow and provides the MAP relay function for other nodes belonging to the service flow, and before sending the delocalization message to the first type of node, the method further includes the following operations:
determining that the node exiting the first domain has no impact on the service flow in the first domain. In the embodiment of the present invention, after determining a first type of node from nodes included in a first domain, the following operations are further included: taking other nodes except the first-class nodes in the nodes included in the first domain as second-class nodes; and aiming at each node in the second class of nodes, respectively executing:
sending a delocalized message to the node;
wherein, the delocalization message is used for indicating the node to exit the first domain; or, the delocalization message is used for indicating the node to exit the first domain and join the second domain.
That is, for a second class node other than the first class node among nodes included in the first domain, since the node among the second class nodes does not belong to the service flow and does not provide for the node belonging to the service flow
A node of the MAP relay function, whereby, for a node of such nodes, a delocalization message is sent directly to the node, wherein the delocalization message is used to instruct the node to exit the first domain; or, the delocalization message is used for indicating the node to exit the first domain and join the second domain.
Certainly, in order to reduce implementation complexity and signaling overhead, in the embodiment of the present invention, if the first type node is a node belonging to a service flow, before sending a combined indication message to the node, the following operations are further included: and determining that the priority of the service flow to which the node belongs is greater than or equal to a service flow priority threshold value. For example: if the preset service flow priority threshold value is 3 and the priority of the service flow to which the node belonging to the service flow belongs is 2, the node directly sends the delocalization message without sending the merging indication message, and if the priority of the service flow to which the node belonging to the service flow belongs is 4, the node firstly sends the merging indication message, and then sends the delocalization message after receiving the merging completion response message.
In this embodiment of the present invention, the merge indication message is further used to indicate the first type node to join the second domain, and establish a service flow with the second DM in the second domain.
The embodiment of the present invention mainly solves the problems existing in the background art based on the technical point that "sending a delocalization message to a first-type node after receiving a merge completion response message returned by the first-type node", and therefore, in the embodiment of the present invention, step 630 is executed after step 620, which can solve the problems existing in the background art.
Referring to fig. 7, in the embodiment of the present invention, the second detailed process of domain mergence is applied to a communication network, the communication network includes at least two domains, a first domain of the at least two domains includes a first DM and a node managed by the first DM, a second domain of the at least two domains includes a second DM, and the specific process is as follows:
a first-class node in a first domain receives a merging indication message sent by a first DM, wherein the merging indication message is used for indicating the first-class node to join a second domain, and the first-class node is a node associated with at least one service flow of the first domain;
When the first type of node is a node belonging to a service flow and/or providing an MAP relay function for a node belonging to the service flow, optionally, the first type of node may be divided into at least the following nodes:
for example, the first type of node is a node belonging to a service flow and not providing a MAP relay function for other nodes belonging to the service flow; or
For another example, the first type node is a node belonging to a service flow and providing a MAP relay function for other nodes belonging to the service flow; or
For example, the first type node provides a MAP relay function for other nodes that do not belong to the service flow;
the node belonging to the service flow is a node for transmitting the service flow carried by the corresponding service, and specifically may be a node for initiating 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, there are multiple ways for the first-class node to receive the merge indication message sent by the first DM, and optionally, the following ways may be adopted:
the first type node receives a merging indication message aiming at the first type node; or
The first type node receives a merge indication message transmitted by the first DM transmitted in a broadcast form. In this embodiment of the present invention, after receiving the merge indication message sent by the first DM, before returning a merge completion response message to the first DM, the first type node further includes the following operations:
when the first type of node belongs to the service flow and does not provide the node with the media access plan MAP relay function for other nodes belonging to the service flow; or, when the node provides the MAP relay function for the nodes belonging to the service flow and other nodes belonging to the service flow, the first type node establishes the service flow with the second DM.
In this embodiment of the present invention, after the first type node returns the merge completion response message to the first DM, the following operations are further included:
and the first type node receives the delocalization message returned by the first DM and exits the first domain according to the delocalization message. For better understanding of the embodiment of the present invention, the following provides a specific application scenario, and further detailed description is made for the process of domain merging, as shown in fig. 8:
a first domain managed by DM1 is merged into a second domain managed by DM2, where node 1, node 2, and node 3 all belong to the first domain, and node 1 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; the node 3 is a node that belongs to the service flow and provides a MAP relay function for other nodes belonging to the service flow, and the node 2 belongs to the second class of nodes.
Step 800, DM1 adjusts the emission clock frequency of DM1 to be synchronous with the emission clock frequency of DM 2; and adjusting the MAC period of DM2 to align with the MAC period of DM 2;
DM1 sends merge indication message to node 1 and node 3 in broadcast form, and sends out delocalization message to node 2;
in this step, the merging indication message carries the node type identifier corresponding to the node 1 and the node type identifier corresponding to the node 3.
DM1 receives the completion merge response messages returned by node 1 and node 3; DM1 sends a delocalization message to node 1 and sends a delocalization message to node 3 when it is determined that node 3 exits the first domain without impact on the service flow in the first domain, step 830.
In summary, in an embodiment of the present invention, a domain merging method is provided, where the method is applied to a communication network, the communication network includes at least two domains, a first domain of the at least two domains includes a first DM and nodes managed by the first DM, a second domain of the at least two domains includes a second DM, and a first type of node is determined from nodes included in the first domain managed by the first DM, where the first type of node is a node associated with at least one service flow of the first domain; sending a merging indication message to the first-class node, wherein the merging indication message is used for indicating the first-class node to join the second domain; in the scheme, when DM needs to be merged into other domains, a merging indication message is sent to a first-class node in the domain and related to at least one service flow of the first domain, and a delocalization message is sent to the first-class node when the first-class node returns a merging completion response message, so that the defect of service transmission interruption is avoided.
The present invention is 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 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 apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks and/or flowchart 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 apparatus 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 apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus 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 invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the appended claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the scope of the invention. Without departing from the spirit and scope of embodiments of the present invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.
Claims (1)
- Claims to follow1. A domain master node, DM, belonging to a first domain of a communication network, said first domain comprising said DM, and nodes managed by said DM, the communication network further comprising a second domain comprising a further DM, characterized in that said DM comprises:a processing unit, configured to determine a first type of node from nodes 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;a sending unit, configured to send a merge indication message to the first class node, where the merge indication message is used to indicate that the first class node joins the second domain;a receiving unit, configured to receive a completion merging response message returned by the first-class node, where the completion merging response message is used to feed back that the first-class node has been added to the second domain;the sending unit is further configured to send a delocalization message to the first-class node, where the delocalization message is used to instruct the first-class node to exit the first domain.2. The domain master node of claim 1, wherein the processing unit is specifically configured to: and 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.3. The domain master node according to claim 1 or 2, wherein the processing unit determines that the first type of node is a node belonging to a service flow and/or providing a medium access plan, MAP, relay function for nodes belonging to a service flow.4. The domain master of claim 3, wherein the first type of node determined by the processing unit is a node belonging to the service flow that does not provide a MAP relay function for other nodes belonging to the service flow; orThe first type of node is a node which belongs to the service flow and provides an MAP relay function for other nodes belonging to the service flow; orThe first type of node is a node which does not belong to the service flow and provides an MAP relay function for other nodes belonging to the service flow; wherein the nodes belonging to the service flow are nodes for which the corresponding service is transmitted and carried by the service flow.5. The domain master node of claim 4, wherein when the first type node is a node belonging to a service flow that does not provide a MAP relay function for other nodes belonging to the service flow; or, when the first-class node is a node that belongs to a 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 returned after any one node in the first-class node joins a second domain managed by the other DM and establishes a service flow with the other DM;when the first-class node is a node that does not belong to a service flow and provides an MAP relay function for other nodes belonging to the service flow, the completion combining response message received by the receiving unit is returned by any one of the first-class nodes after joining the second domain managed by the other DM.6. The domain master node of any one of claims 1 to 5, wherein the sending unit is specifically configured to:aiming at each node in the first class of nodes, sending a merging indication message carrying a node type identifier of the node to the node; orAnd sending a merging indication message carrying node type identifiers respectively corresponding to the nodes to each node in the first class of nodes in a broadcasting mode.7. The domain master node of any of claims 4-6, wherein the processing unit is further to:determining that a first class of nodes exiting the first domain has no impact on service flows in the first domain.8. The domain master of any of claims 4 to 7, wherein if the node of the first type is a node belonging to a service flow, the processing unit is further configured to:and determining that the priority of the service flow to which the node belongs is greater than or equal to a service flow priority threshold value.9. A node belonging to a first domain of a communication network, said node being managed by a first domain master node, DM, of said first domain, said communication network further comprising a second domain, said second domain comprising a second DM, characterized in that said node comprises: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 join the node to the second domain according to the merge indication message, and generate a merge completion response message, where the merge completion response message is used to feed back that the node has joined the second domain;a sending unit, configured to send the completion coalescing response message to the first DM.10. The node according to claim 9, wherein the node is a node belonging to the service flow and/or providing a medium access plan, MAP, relay function for nodes belonging to the service flow.11. The node according to claim 9 or 10, wherein the node is a node belonging to the service flow that does not provide a MAP relay function for other nodes belonging to the service flow; orThe node provides MAP relay function for other nodes belonging to the service flow; orThe node is a node which does not belong to the service flow and provides an MAP relay function for other nodes belonging to the service flow;wherein the nodes belonging to the service flow are nodes for which the corresponding service is transmitted and carried by the service flow.12. The node of claim 11, wherein the processing unit is further configured to: when the class node is a node which belongs to the service flow and does not provide the MAP relay function for other nodes which belong to the service flow; or, when a node providing the MAP relay function for a node belonging to a service flow and for another node belonging to the service flow, establishing a service flow with the second DM.13. The node according to any of claims 9-12, wherein the receiving unit is further configured to receive a delocalized message returned by the first DM;the processing unit is further configured to exit the first domain according to the delocalization message.14. A method for domain mergence, applied to a communication network comprising at least two domains, a first domain of the at least two domains comprising a first domain master node DM and a node managed by the first DM, and a second domain of the at least two domains comprising a second DM, the method comprising: determining a first type of node from nodes included in a first domain managed by a 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 class node, where the merge indication message is used to indicate that the first class node has joined to the second domain;receiving a completion combination response message returned by the first-class node, wherein the completion combination response message is used for feeding back that the first-class node is added to the second domain;and sending a delocalization message to the first class of nodes, wherein the delocalization message is used for indicating the first class of nodes to exit the first domain.15. The method as claimed in claim 14, wherein the determining the first type of node from the nodes included in the first domain managed by the first DM comprises:and 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.16. The method according to claim 14 or 15, wherein the first type of node is a node belonging to a service flow and/or a node providing a media access plan, MAP, relay function for nodes belonging to a service flow.17. The method of claim 16, wherein the first type of node is a node belonging to the service flow that does not provide a MAP relay function for other nodes belonging to the service flow; or the first type node provides a MAP relay function for the service flow and other nodes belonging to the service flow; orThe first type of node is a node which does not belong to the service flow and provides an MAP relay function for other nodes belonging to the service flow;wherein the nodes belonging to the service flow are nodes for which the corresponding service is transmitted and carried by the service flow.18. The method of claim 17, wherein when the first type node is a node belonging to a service flow and not providing a MAP relay function for other nodes belonging to the service flow; or, when the first-class node is a node that belongs to a service flow and provides an MAP relay function for other nodes that belong to the service flow, the completion-merging response message is returned after any one node in the first-class node joins a second domain managed by a second DM and establishes a service flow with the second DM;when the first-class node is a node that does not belong to a service flow and provides an MAP relay function for other nodes belonging to the service flow, the completion-merging response message is returned after any one node in the first-class node joins a second domain managed by a second DM.19. The method according to any of claims 14 to 18, wherein sending a merge indication message to the first type node specifically comprises:aiming at each node in the first class of nodes, sending a merging indication message carrying a node type identifier of the node to the node; orAnd sending a merging indication message carrying node type identifiers respectively corresponding to the nodes to each node in the first class of nodes in a broadcasting mode.20. The method according to any of claims 17-19, characterized in that if the first type of node is a node belonging to a service flow providing 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 a service flow and provides a MAP relay function for other nodes belonging to the service flow, and before sending the delocalization message to the first type of node, the method further includes:determining that a first class of nodes exiting the first domain has no impact on service flows in the first domain.21. The method according to any of claims 17-20, wherein if the first type node is a node belonging to a service flow, before sending a close indication message to the node, further comprising:and determining that the priority of the service flow to which the node belongs is greater than or equal to a service flow priority threshold value.22. A method for domain mergence, applied to a communication network comprising at least two domains, a first domain of the at least two domains comprising a first domain master node DM and a node managed by the first DM, and a second domain of the at least two domains comprising a second DM, the method comprising: a first-class node in a first domain receives a merge indication message sent by a first DM, wherein the merge indication message is used for indicating the first-class node to join the second domain, and the first-class node is a node associated with at least one service flow of the first domain;the first class node joins the second domain according to the merging indication message and generates a merging completion response message, wherein the merging completion response message is used for feeding back that the first class node is joined to the second domain;the first type node returns a completion merge response message to the first DM.23. The method according to claim 22, wherein the first type of node is a node belonging to the service flow and/or providing a media access plan, MAP, relay function for nodes belonging to the service flow.24. The method according to claim 22 or 23, wherein the first type of node is a node belonging to the service flow that does not provide a MAP relay function for other nodes belonging to the service flow; orThe first type of node is a node which belongs to the service flow and provides an MAP relay function for other nodes belonging to the service flow; orThe first type of node is a node which does not belong to the service flow and provides an MAP relay function for other nodes belonging to the service flow;wherein the nodes belonging to the service flow are nodes for which the corresponding service is transmitted and carried by the service flow.25. The method as claimed in claim 24, wherein the first type node, after receiving the merge indication message sent by the first DM and before returning a merge complete response message to the first DM, further comprises:when the first type of node belongs to the service flow and does not provide the node with the media access plan MAP relay function for other nodes belonging to the service flow; or, when the node provides the MAP relay function for the node belonging to the service flow and other nodes belonging to the service flow, the first class node and the second DM establish the service flow.26. The method according to any of claims 22-25, wherein after the first type node returns a completion merge response message to the first DM, further comprising:and the first class node receives the delocalization message returned by the first DM and exits the first domain according to the delocalization message.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2014/082099 WO2016004635A1 (en) | 2014-07-11 | 2014-07-11 | Domain merging method, domain master node and node |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105453500A true CN105453500A (en) | 2016-03-30 |
Family
ID=55063535
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201480007120.2A Pending CN105453500A (en) | 2014-07-11 | 2014-07-11 | Domain merging method, domain master node and node |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105453500A (en) |
| WO (1) | WO2016004635A1 (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101184087A (en) * | 2006-11-16 | 2008-05-21 | 华为技术有限公司 | Field transforming method, equipment and system |
| WO2013037625A1 (en) * | 2011-09-16 | 2013-03-21 | Alcatel Lucent | Method and apparatus for exchanging data signals over a plurality of domains in a home network |
| CN103200059A (en) * | 2013-04-08 | 2013-07-10 | 中兴通讯股份有限公司南京分公司 | Secure network access processing method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7971261B2 (en) * | 2007-06-12 | 2011-06-28 | Microsoft Corporation | Domain management for digital media |
| CN101364871B (en) * | 2007-08-10 | 2011-12-21 | 华为技术有限公司 | Method, system and apparatus for domain manager to carry out domain management to user equipment |
| CN102088450B (en) * | 2009-12-08 | 2014-03-19 | 中兴通讯股份有限公司南京分公司 | Method for splitting and merging domains in multi-domain peer-to-peer network and system thereof |
-
2014
- 2014-07-11 WO PCT/CN2014/082099 patent/WO2016004635A1/en active Application Filing
- 2014-07-11 CN CN201480007120.2A patent/CN105453500A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101184087A (en) * | 2006-11-16 | 2008-05-21 | 华为技术有限公司 | Field transforming method, equipment and system |
| WO2013037625A1 (en) * | 2011-09-16 | 2013-03-21 | Alcatel Lucent | Method and apparatus for exchanging data signals over a plurality of domains in a home network |
| CN103200059A (en) * | 2013-04-08 | 2013-07-10 | 中兴通讯股份有限公司南京分公司 | Secure network access processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2016004635A1 (en) | 2016-01-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110167051B (en) | Communication method and communication equipment under centralized unit-distributed unit architecture | |
| CN110326345B (en) | Method, device and system for configuring network slice | |
| CN102340434B (en) | Multihoming access-based loop avoidance method and edge devices | |
| US10194472B2 (en) | Group communication method, device and system | |
| CN109391490B (en) | Network slice management method and device | |
| CN107342925B (en) | Message transmission method and device | |
| EP3402130A1 (en) | Information transmission method and device | |
| CN110536300B (en) | Communication control method, network control entity and system | |
| CN103297560A (en) | Data flow classification method and data flow classification server | |
| CN106161171B (en) | Method and device for establishing network service instance | |
| CN104468408A (en) | Method for adjusting dynamically service bandwidth and control center server | |
| CN112887117B (en) | Method, equipment and medium for accessing and configuring network slice | |
| WO2014206354A1 (en) | Method, device and system for establishing traffic engineering label switch path | |
| CN111682968B (en) | Network access management method and system for communication equipment | |
| CN102882555B (en) | Domain access control method, domain searching method and communication apparatus | |
| CN103765819A (en) | Data configuration method and network management server | |
| CN111328040A (en) | Communication mode indication method and device of Internet of vehicles V2X | |
| CN109429184B (en) | Method and device for establishing MBMS multicast session | |
| CN105453500A (en) | Domain merging method, domain master node and node | |
| WO2022042483A1 (en) | Information processing method and apparatus, server and internet-of-vehicles terminals | |
| WO2021012939A1 (en) | Method and device for sidelink | |
| CN110635986B (en) | Network access method and equipment | |
| CN109246796A (en) | A kind of communication means and device | |
| WO2016201860A1 (en) | Data transmission method and apparatus | |
| CN104052527A (en) | Network merging method and system, and stations |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| AD01 | Patent right deemed abandoned | ||
| AD01 | Patent right deemed abandoned |
Effective date of abandoning: 20190809 |