WO2016197322A1 - 域合并方法及媒介间桥接器、节点 - Google Patents

域合并方法及媒介间桥接器、节点 Download PDF

Info

Publication number
WO2016197322A1
WO2016197322A1 PCT/CN2015/081063 CN2015081063W WO2016197322A1 WO 2016197322 A1 WO2016197322 A1 WO 2016197322A1 CN 2015081063 W CN2015081063 W CN 2015081063W WO 2016197322 A1 WO2016197322 A1 WO 2016197322A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
domain
device identifier
domains
conflict
Prior art date
Application number
PCT/CN2015/081063
Other languages
English (en)
French (fr)
Inventor
姜彤
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2015/081063 priority Critical patent/WO2016197322A1/zh
Priority to CN201580024650.2A priority patent/CN106464576A/zh
Publication of WO2016197322A1 publication Critical patent/WO2016197322A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Definitions

  • the present invention relates to the field of communications, and in particular, to a domain merging method and an inter-carrier bridge and node.
  • the G.hn standard approved by the International Telecommunication Union (ITU-T) in 2010 can support three transmission media: power line, coaxial cable and telephone line, and unifies the home network standard.
  • This technology enables the distribution of multiple data or video streams, including high-definition television (HDTV) and standard definition television (SDTV) throughout the home, supporting home entertainment applications and broadband high-speed Internet access.
  • HDMI high-definition television
  • SDTV standard definition television
  • a home network can contain one or more domains, each of which is typically a centralized management network.
  • Each domain has a domain master node (DM).
  • the DM is responsible for the management of the entire domain, including domain establishment, node registration, domain bandwidth allocation, and resource scheduling. Coordination with multiple adjacent domains or networks, network power management, etc.
  • each domain also contains a security controller (SC), which is responsible for the authentication of the nodes in the domain and the management of the key management process. After the authentication is completed to the SC, the key can be obtained and the secure data can be transmitted.
  • SC security controller
  • the DM performs domain management and resource scheduling by transmitting a Media Access Plan (MAP) in each Media Access Control (MAC) cycle.
  • MAP Media Access Plan
  • MAC Media Access Control
  • the MAP indicates the start time of the next MAC period, the allocation of transmission opportunities for resource scheduling for the node, and the relevant parameters required for other domain operations.
  • the node discovers the existence of the domain by detecting the MAP frame and joins the domain.
  • the node joins the domain by sending a registration request to the DM. After the registration is successful, the node authenticates to the SC. After the authentication succeeds, data transmission can begin.
  • the node In order to guarantee the quality of service (QoS), the node needs to establish a service flow to the DM. If the DM can support the establishment of the service flow, the application is agreed, and after the service flow is established, according to the transmission characteristics (Traffic SPECification, TSpec) performs resource scheduling.
  • the scheduling mode of the service flow of the DM may be continuous scheduling or non-persistent scheduling.
  • the resource scheduling information advertised by the DM is valid in several MAC cycles, and the persistent scheduling is the resource scheduling information advertised by the DM. A MAC cycle is valid.
  • the Inter-Medium Bridge (IMB) function is defined in G.hn. Since G.hn supports multiple transmission media such as power lines, coaxial cables, and telephone lines, it can be implemented below the A-interface through the IMB. Interworking of domains of different transmission media, or the same domain operating on multiple transmission media.
  • IMB Inter-Medium Bridge
  • MAP-D/RMAP-D Default Media Access Plan/Relayed Default Medium Access Plan
  • MAP-A/RMAP-A Active Medium Access Plan
  • domain name of another domain is the same as the domain name of the domain, then the two domains need to be merged.
  • domain A works in both the power line and the telephone line, and can communicate with each other through the IMB, where the IMB is the DM of the domain A.
  • domain B works on the power line
  • domain C works on the telephone line.
  • N0 and N1 parts are added to the domain B and the domain C respectively. That is, the N0 part performs the function in the domain B, and the N1 part performs the function in the domain C.
  • domain B and domain C need to be merged.
  • a DM that can be a domain that needs to be merged needs to determine which domain is to be merged into another domain according to a predetermined rule. After determining that its own domain B is to be merged into another domain, the DM will All nodes are set up. After each node is set, it can join another domain by itself. It can also be that all the nodes in the two domains are reset, all nodes are set from the domain and re-networked; or one domain needs to be merged. When another domain is reached, if the domain B determines that it needs to be merged into the domain C, it sends a merge request message to the domain C.
  • the domain C After receiving the merge request, the domain C determines whether it can support and accept the merge, and if so, returns a merge confirmation message. After receiving the merge confirmation message, it broadcasts a merge indication message to all nodes of the domain C, which should contain all the useful information in the confirmation message. It can be seen that the domain merging method in the prior art has a large delay, which causes interruption of node service transmission, or high complexity.
  • the embodiments of the present invention provide a domain merging method and an inter-carrier bridge and a node, which ensure seamless domain merging, and do not affect the traffic service transmission, and reduce the implementation complexity.
  • the first aspect provides an inter-carrier bridge, including: a conflict analysis module, configured to analyze a conflict condition of device identifiers in two domains with the same domain name; a conflict processing module, connected to the conflict analysis module, When a conflict of device identifiers in two domains is used, a new device identifier is assigned to one of the nodes of each pair of device identification conflicts; a broadcast module is connected to the conflict processing module, a new device identifier is broadcast, and an effective time is obtained. In order for the node to work according to the new device identifier, the effective time is the time point when the new device identifier takes effect.
  • the inter-mediated bridge further includes a detection module and a sending module, where the detecting module is configured to detect whether the domain names of the two domains are the same, and the sending module is used to When the domain name of the domain is the same, a node switching indication message is sent to the domain master node in the two domains, and the node switching indication message is used to switch the domain master node in the two domains to the inter-mediated bridge and synchronize.
  • the handover indication information includes a handover reason.
  • the conflict analysis module is further configured to: pass the previous topology maintenance process or pass the The node switching process obtains the device identification of the nodes in the two domains.
  • the conflict processing module is configured to: if the conflict analysis module determines that the device identifiers in the two domains do not conflict, the conflict processing module passes The effective media access plan is sent for resource scheduling and management; if the conflict analysis module determines that the device identifiers in the two domains are in conflict, the conflict handling module allocates a new device identifier for one of the nodes of each pair of device identification conflicts.
  • the conflict processing module further It is used to compare the total number of flows established by the nodes with conflicts of device IDs in the two domains, and assign new device IDs to the nodes with conflicting device IDs in the domain with smaller total number of flows.
  • the conflict processing module further Used to: If the total number of flows established by the nodes that conflict with the device IDs in the two domains is the same, the nodes with the device ID conflicts in any of the domains are randomly assigned a new device ID.
  • the conflict processing module is used by The total length of the allocated time slot of the flow established by the node whose device identifier conflicts in the two domains is compared, and the new device identifier is assigned to the node whose device identifier conflicts in the domain with the smaller total length of the total time slot allocation.
  • the conflict processing module further For: if the total length of the time slot allocated by the number of flows established by the node whose device identifier conflicts in the two domains is the same is the same, the node that conflicts with the device identifier in any one of the domains is randomly assigned a new device identifier.
  • the conflict processing module is used by And: comparing the nodes of each pair of device identification conflicts in the two domains, and replacing the device identifiers with the nodes with fewer flows according to the number of flows established by each pair of device identification conflicting nodes.
  • the broadcast module is configured to: update the supplementary sub-domain by adding a device identifier in the broadcast media access plan frame, or The new device identifier is sent to the node with the device ID conflict by sending a device identifier update message.
  • the inter-mediated bridge further includes a scheduling module, configured to perform scheduling and management according to the new device identifier.
  • the second aspect provides a domain merging method, including: analyzing a conflict situation of device identifiers in two domains with the same domain name; and identifying one of two conflicting nodes for each pair of devices when the device identifiers in the two domains conflict
  • the node assigns a new device ID; broadcasts the new device ID and the effective time so that the node works according to the new device ID, where the effective time is the point in time when the new device ID takes effect.
  • the domain names in the two domains before analyzing the conflict situation of the device identifiers in the two domains with the same domain name, detecting whether the domain names of the two domains are the same, the domain names in the two domains.
  • a node switching indication message is sent to the domain master nodes in the two domains, and the node switching indication message is used to switch the domain master nodes in the two domains to the inter-mediated bridge and synchronize.
  • the handover indication information includes a handover reason.
  • the conflicting situation of the device identifiers in the two domains with the same domain name is analyzed:
  • the device IDs of the nodes in the two domains are obtained by switching the previous topology maintenance process or by the node switching process.
  • the method further includes: sending a valid media access plan if the device identifiers in the two domains do not conflict Perform resource scheduling and management; if there is a conflict between device IDs in the two domains, assign a new device ID to one of the nodes that conflict with each pair of device IDs.
  • a node in the node that identifies the conflict is assigned a new device identifier, including: comparing the total number of flows established by the node with the device ID conflict in the two domains, and allocating the new node with the device ID conflict in the domain with a smaller total number of flows. Device identification.
  • the first possible, the second possible, the third possible, the fourth possible implementation of the second aspect, in the sixth possible implementation for each pair of devices A node in the node that identifies the conflict allocates a new device identifier, and further includes: if the total number of flows established by the node that conflicts with the device identifiers in the two domains is the same, the node that is in conflict with the device identifier in any one of the domains is randomly Assign a new device ID.
  • the first possible, the second possible, the third possible, the fourth possible implementation of the second aspect, in the seventh possible implementation, for each pair of devices Assigning a new device identifier to one of the nodes identifying the conflict includes: comparing the total length of the allocated time slots of the flow established by the node with the device identity conflict in the two domains, and allocating the total length of the total time slot to the total time slot The device ID conflicts with the node assigned a new device ID.
  • a node in the node that identifies the conflict is assigned a new device identifier, including: comparing the nodes with conflicting device identifiers in the two domains, and the number of flows established according to the number of nodes established by each pair of device identifier conflicts The node replaces the device ID.
  • the eighth possible, ninth possible implementation manner in the tenth possible implementation manner, broadcasting a new device identifier and an effective time, including: adding a device identifier in a broadcast media access plan frame Update
  • the new device ID is sent to the node with the device ID conflict by sending a device identifier update message.
  • the method further includes: scheduling and managing according to the new device identifier.
  • the third aspect provides a node, including: a receiving module, configured to receive a node switching indication message, where a domain where the node is located is the same as a domain name of another domain; and the switching module is connected to the receiving module, and is configured to: according to the node switching indication message
  • the domain master node of the domain in which the node resides switches to the inter-media bridge and synchronizes to complete the domain merge with the other domain.
  • the receiving module is further configured to: receive a new device identifier allocated by the inter-carrier bridge; and the switching module works according to the new device identifier.
  • a second possible implementation manner if the node with the device identifier conflicting in the domain of the node has a total number of flows established by the node in the domain is smaller than the node with the device identifier conflict in the other domain The total number of times of the established flow, or the total length of the allocated time slots of the flow established by the node whose device identifier conflicts in the domain in which the node is located is smaller than the total length of the allocated time slot of the flow established by the node with the device identity conflict in the other domain, and the receiving module Receives a new device ID assigned by the inter-media bridge.
  • a third possible implementation manner if the total number of flows established by the node whose device identifier conflicts in the domain of the node is established conflicts with the device identifier of another domain, If the total number of time slots allocated by the node established by the node whose device identifier conflicts in the domain in which the node is located is the same as the total length of the time slot allocated by the node established by the node in the other domain, The receiving module of the node in the node or another domain that conflicts with the node device identity receives the new device identity.
  • the receiving module receives the inter-carrier bridge assignment. New device identification.
  • the fourth aspect provides a domain merging method, including: receiving, by a domain master node of a domain where a node is located, a node switching indication message, where a domain where the node is located is the same as a domain name of another domain; and a domain master node of the domain where the node is located is switched according to the node
  • the indication message switches to the inter-mediated bridge and synchronizes to complete the domain merge with another domain.
  • the method further includes: the node receiving the new device identifier allocated by the inter-carrier bridge, and working according to the new device identifier.
  • the section The total number of flows established by the node with the device ID conflict in the domain is smaller than the total number of flows established by the node with the device ID conflict in the other domain, or the time slot allocated by the node established by the node with the device ID conflict in the domain where the node is located.
  • the total length is less than the total length of the allocated time slots of the flow established by the node with the device identity conflict in the other domain.
  • the node receives the new device identifier, including: if the node in the domain where the device identifier conflicts, the total number of flows established by the node and the other The total number of flows established by the node with the device ID conflict in one domain is the same, or the total length of the time slot allocated by the node established by the node with the device ID conflict in the domain where the node is located is the one established by the node with the device ID conflict in the other domain. The total length of the allocated time slots is the same, and the node in the node or another domain that conflicts with the node device identity receives the new device identity.
  • the node receives the new device identifier, including: the number of flows established by the node is smaller than the number of flows established by the node in the other domain that conflicts with the identifier of the node device.
  • the invention analyzes the conflict situation of the device identifiers in the two domains with the same domain name; when the device identifiers in the two domains collide, assign a new device identifier to one of the nodes of each pair of device identifier conflicts; The device ID and the effective time are set so that the node works according to the new device identifier. This ensures that the domain is seamlessly merged without affecting the traffic service transmission and reduces the implementation complexity.
  • FIG. 1 is a schematic diagram of a domain merging method in the prior art
  • FIG. 2 is a schematic diagram of a domain merging method of the present invention
  • FIG. 3 is a schematic structural view of an inter-vehicle bridge according to a first embodiment of the present invention
  • FIG. 4 is a schematic structural view of an inter-vehicle bridge according to a second embodiment of the present invention.
  • FIG. 5 is a schematic flowchart diagram of a domain merging method according to a first embodiment of the present invention
  • FIG. 6 is a schematic structural diagram of a node according to a first embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a node according to a second embodiment of the present invention.
  • FIG. 8 is a schematic flowchart diagram of a domain merging method according to a second embodiment of the present invention.
  • FIG. 2 is a schematic flowchart diagram of a domain merging method of the present invention.
  • the domain names of domain B and domain C are the same, that is, domain B and domain C need to be merged.
  • the domain B includes at least nodes N0, N2, and N3, and the domain C includes at least nodes N1, N4, N5, and N6.
  • the number of nodes and the number of nodes specifically included in domain B and domain C are determined on a case-by-case basis, and are not limited herein.
  • the domain B can operate on at least one of a power line, a telephone line, or a coaxial cable, etc.
  • the domain C can also work on at least one of a telephone line, a power line, or a coaxial cable, but the domain B and the domain C work differently.
  • the inter-mediated bridge IMB includes a node N0 and a node N1, which operate in domain B and domain C, respectively. When the inter-carrier bridge IMB goes online, it detects whether the domain names located in domain B and domain C are the same. Specifically, the inter-mediated bridge IMB detects whether the domain names of the node N2 located in the domain B and the node N4 located in the domain C are the same.
  • the node N0 and the node N1 respectively send a node switching indication message to the domain primary node DM1 in the domain B and the domain primary node DM2 in the domain C.
  • the domain master node DM1 is the node N2
  • the domain master node DM2 is the node N4.
  • the domain master node DM1 may not be the node N2, and the domain master node DM4 is not the node N1.
  • the domain master nodes DM1 and DM2 After receiving the node handover indication message, the domain master nodes DM1 and DM2 perform the node handover procedure according to G.9961, that is, switch the domain master node to the inter-mediated bridge IMB.
  • the node switching indication message may use an existing message in G.9961, that is, increase the reason for the handover in the existing DM_Handover Request.ind.
  • the format of the node switching indication message is as shown in Table 1.
  • the inter-media bridge IMB is obtained by the topology maintenance process before the handover or by the node switching process. Device identification information for all nodes in both domains.
  • the inter-media bridge IMB analyzes the conflicts of device identifications in the two domains. If there is no conflict between the nodes in the two domains, the domain master node function is directly executed, and resource scheduling and management are performed by sending MAP-A. If there is a conflict between the nodes in the two domains, a new device identity is assigned to one of the nodes that conflict with each pair of device identifications.
  • the inter-media bridge IMB can compare the total number of flows established by the nodes whose device identifiers conflict in the two domains, and assign new device identifiers to the nodes whose device identifiers conflict in the domain with a smaller total number of flows. If the total number of flows established by the nodes that conflict with the device IDs in the two domains is the same, the nodes with the device ID conflicts in any of the domains are randomly assigned a new device ID.
  • the inter-mediated bridge IMB can also compare the total length of the allocated time slots of the flow established by the node with the device identification conflict in the two domains, and assign a new node to the node with the device identification conflict in the domain with the smaller total length of the total time slot allocation. Equipment Identity.
  • the node with the device identity conflict in any of the domains is randomly assigned a new device identity.
  • the inter-media bridge IMB can also compare the nodes of each pair of device identification conflicts in the two domains, and replace the device identifiers with the nodes with fewer flows according to the number of flows established by each pair of device identification conflicting nodes. If the number of flows established by the two device ID conflicting nodes is equal, the node with the smaller MAC address is assigned a new device identifier.
  • a new device identifier may also be received for a node with a larger MAC address.
  • the inter-media bridge IMB is scheduled and managed according to the new device identification. At the same time, optionally, the domain master node is switched back to the higher ranked node.
  • the inter-media bridge IMB also determines a uniform device identifier for the portions of the media corresponding to the different domains, and is embodied in the MAP.
  • the inter-media bridge IMB sends the assigned new device ID to the node with the device ID conflict, that is, broadcasts the new device ID, and the effective time, so that the node works according to the new device identifier, where the effective time is the new device.
  • the inter-media bridge IMB may send the assigned new device identifier to the node with the device identifier conflict by adding a device identifier update supplement sub-domain in the broadcast media access plan frame, or by sending a device identifier update message.
  • the inter-media bridge IMB can broadcast a new device identifier in one of three ways, and the effective time:
  • Table 2 Add the first format of the "Device Identity Update Supplement Subdomain" to the broadcast MAP frame.
  • the supplementary sub-domains of the device identification update added in the broadcast MAP frame include the modification flag bit, the number of nodes that re-allocate the device identification, the 48-bit MAC address, and the assigned device identification.
  • the supplemental subfield of the device identification update of each node includes a 48-bit MAC address and an assigned 8-bit device identifier.
  • the device identification update added in the broadcast MAP frame in Table 3 The sub-domain includes the modification of the flag bit, the number of nodes that reassign the device identification, the 48-bit MAC address of the domain master node of the domain to which the node to which the new device identifier is newly assigned, the original device identifier of the node, and the new device identifier of the node.
  • the supplementary sub-domain of the device identification update of each node includes the original device identifier of the 8-bit node and the new device identifier of the assigned 8-bit node.
  • the message may be sent by means of broadcast or by unicasting to the node to which the new device identifier is assigned.
  • the format of the message when the broadcast is sent is similar to the previous 1) and 2), where it is necessary to indicate the effective time of the new device identification.
  • the format of the message is as shown in Table 4 or Table 5.
  • the method of sending the device identity update message to the node to which the new device identifier is assigned is unicast only needs to directly send the new device identifier and the effective time, or add the original on the basis of this.
  • the device identifier and the MAC address of the domain master node of the domain to which the node that needs to reassign the new device identifier does not need to include other identifiers such as the modified identifier bit and the length, and the message format is simple and easy, which can reduce the implementation complexity.
  • the node After the node receives the new device ID, it works according to the new device ID.
  • a unified device identifier may be determined for the media portion corresponding to the different domains and embodied in the MAP. This ensures that the domain is seamlessly merged without affecting the flow of traffic. At the same time reduce implementation complexity.
  • FIG. 3 is a schematic view showing the structure of an inter-vehicle bridge according to a first embodiment of the present invention.
  • the inter-mediated bridge 10 includes a conflict analysis module 11, a conflict processing module 12, and a broadcast module 13.
  • the conflict analysis module 11 is configured to analyze the conflict situation of the device identifiers in the two domains with the same domain name.
  • the conflict processing module 12 is connected to the detecting module, and is configured to allocate a new device identifier to one of the nodes of each pair of device identifier conflicts when the device identifiers of any pair of nodes in the two domains collide.
  • the broadcast module 13 is connected to the conflict handling module 12 to broadcast a new device identification and an effective time so that the node operates in accordance with the new device identification. The effective time is the time when the new device ID is valid.
  • the handover indication information includes a handover reason.
  • the conflict processing module 12 is configured to obtain device identifiers of nodes in the two domains by using a topology maintenance process before switching or by a node switching process. The conflict handling module 12 needs to analyze the conflicting situation of the device identifiers in the two domains before assigning a new device identifier to one of the nodes of each pair of device identification conflicts. If the device identifications in the two domains do not conflict, the conflict handling module 12 is configured to perform resource scheduling and management by transmitting a valid media access plan. If the device identifiers in the two domains have conflicts, the conflict handling module 12 is configured to assign a new device identifier to one of the nodes that each pair of device identification conflicts.
  • the conflict processing module 12 can have two methods for assigning a new device identifier to the node with the device identification conflict.
  • the first method is: the conflict processing module 12 compares the total number of flows established by the nodes whose device identifiers conflict in the two domains, and assigns a new device identifier to the nodes whose device identifiers conflict in the domain with a smaller total number of flows. If the total number of flows established by the nodes that conflict with the device identification in the two domains is the same, the conflict handling module 12 randomly assigns a new device identity to the node with the device identity conflict in any of the domains.
  • the second method is: comparing the total length of the allocated time slots of the flow established by the node with the device identifier conflict in the two domains, and the conflict processing module 12 allocates the node with the device identifier conflict in the domain with the smaller total length for the total time slot. Assign a new device ID. If the total length of the time slot allocated by the number of flows established by the node in which the device identification conflicts in the two domains is the same is the same, the conflict processing module 12 randomly assigns a new device identity to the node whose device identification conflicts in any of the domains. In this way, in the process of domain merging, there is no need to interrupt the service transmission, and the seamless integration of the domains can be ensured, and the traffic transmission is not affected, and the implementation complexity is reduced.
  • the conflict processing module 12 may also compare the nodes that conflict with each pair of device identifiers in the two domains, and replace the device identifiers with the nodes with fewer established flows according to the number of flows established by the node. That is, the number of flows established by the node whose device identifier conflicts is sorted, and the device identifier update is performed on the node with fewer flows, which can reduce the implementation complexity. If the number of flows established by the two nodes is equal, a new device identifier is assigned to the node with the smaller MAC address. Of course, in other embodiments of the invention, It is also possible to receive a new device identifier for a node with a larger MAC address.
  • the broadcast module 13 is configured to: send a new device identifier to the device identifier by adding a device identifier update supplementary sub-domain in the broadcast media access plan frame, or by sending a device identifier update message.
  • the node of the conflict Broadcasting a new device identifier also sends a new device identifier to the node whose device identifier conflicts, so that the node works according to the new device identifier. This can be done in one of three ways:
  • the supplemental subfield of the device identification update added in the broadcast MAP frame includes a modification flag bit, a number of nodes that reassign the device identification, a 48-bit MAC address, and an assigned device identification.
  • the supplemental subfield of the device identification update of each node includes a 48-bit MAC address and an assigned 8-bit device identifier.
  • the supplementary sub-domain of the device identification update added in the broadcast MAP frame by adding the "device identification update supplement sub-domain" in the broadcast MAP frame includes modifying the flag bit, reassigning the number of nodes of the device identifier, and reallocating the new one.
  • the supplementary sub-domain of the device identification update of each node includes the original device identifier of the 8-bit node and the new device identifier of the assigned 8-bit node.
  • the message may be sent by means of broadcast or by unicasting to the node to which the new device identifier is assigned.
  • the format of the message when the broadcast is sent is similar to the previous 1) and 2), where it is necessary to indicate the effective time of the new device identification.
  • the device identifier update message is sent to the node to which the new device identifier is unicast separately. You only need to directly send the new device ID and the effective time, or add the original device ID.
  • the MAC address of the domain master node of the domain to which the node to which the new device identifier needs to be re-allocated does not need to include other identifiers such as the modified identifier bit and the length, and the message format is simple and easy, which can reduce the implementation complexity.
  • the inter-mediated bridge 10 further includes a scheduling module 14 for scheduling and managing according to the new device identifier.
  • a scheduling module 14 for scheduling and managing according to the new device identifier.
  • a unified device identifier may also be determined for the media portion corresponding to the different domains and embodied in the MAP.
  • the inter-carrier bridge 20 includes a transceiver 21, a processor 22, a memory 23, and a data bus 24, wherein the receiver 21, the processor 22, and the memory 23 are respectively connected to the data bus 24 for data communication via the data bus 24. mutual.
  • the processor 22 detects whether the domain names of the two domains are the same. When the domain names of the two domains are the same, the transceiver 21 sends a node switching indication message to the domain master node in the two domains, and the node switching indication message is sent. Used to switch domain masters in both domains to the inter-mediated bridge and synchronize.
  • the processor 22 analyzes the conflict condition of the device identifiers in the two domains, and assigns a new device identifier to one of the nodes that conflict with each pair of device identifiers when the device identifiers of any of the two nodes in the two domains collide.
  • the transceiver 21 broadcasts a new device identification and an effective time to cause the node to operate in accordance with the new device identification.
  • the switching indication information includes the reason for the switching, and the effective time is the time point when the new device identifier is valid.
  • the processor 22 obtains the device identifier of any node in the two domains by using the topology maintenance process before the handover or by the node handover process.
  • the processor 22 needs to analyze the conflict situation of the device identifiers in the two domains before assigning a new device identifier to one of the nodes identifying each pair of device identification conflicts. If the device identifications in the two domains do not conflict, the processor 22 performs resource scheduling and management by sending a valid media access plan. If the device identifications in the two domains have conflicts, the processor 22 is configured to assign a new device identification to one of the nodes identifying each of the pair of device identification conflicts.
  • the memory 23 is used to store device identification and handover indication information.
  • the processor 22 can have two methods for assigning a new device identification to a node whose device identification conflicts.
  • the first method is: the processor 22 compares the total number of flows established by the nodes with conflicting device identifiers in the two domains, and allocates new device identifiers to the nodes with conflicting device identifiers in the domain with a smaller total number of flows. If the total number of flows established by the nodes that conflict with the device identification in the two domains is the same, the processor 22 randomly assigns a new device identity to the node with the device identity conflict in any of the domains.
  • the second method is: comparing the total length of the allocated time slots of the flow established by the node with the device identification conflict in the two domains, and the processor 22 assigning the node identification of the device identification conflict in the domain with the smaller total length for the total time slot allocation. New device identification. If the total length of the allocated time slots of the flow number established by the node in which the device identification conflicts in the two domains is the same is the same, the processor 22 randomly assigns a new device identification to the node whose device identification conflicts in any of the domains. In this way, in the process of domain merging, there is no need to interrupt the service transmission, and the seamless integration of the domains can be ensured, and the traffic transmission is not affected, and the implementation complexity is reduced.
  • the processor 22 may also compare the nodes that conflict with each pair of device identifiers in the two domains, and replace the device identifiers with the nodes with fewer established flows according to the number of flows established by the node. That is, the number of flows established by the node whose device identifier conflicts is sorted, and the device identifier update is performed on the node with fewer flows, which can reduce the implementation complexity. If the number of streams established by the two nodes is equal, the processor 22 assigns a new device identification to the node with the smaller MAC address. Of course other embodiments of the invention In the middle, a node with a larger MAC address can also receive a new device identifier.
  • the processor 22 sends a new device identifier to the node with the device identifier conflict by adding a device identifier update supplementary sub-domain in the broadcast media access plan frame, or by sending a device identifier update message.
  • Broadcasting a new device identifier also sends a new device identifier to the node whose device identifier conflicts, so that the node works according to the new device identifier. This can be done in one of three ways:
  • the supplemental subfield of the device identification update added in the broadcast MAP frame includes a modification flag bit, a number of nodes that reassign the device identification, a 48-bit MAC address, and an assigned device identification.
  • the supplemental subfield of the device identification update of each node includes a 48-bit MAC address and an assigned 8-bit device identifier.
  • the supplementary sub-domain of the device identification update added in the broadcast MAP frame by adding the "device identification update supplement sub-domain" in the broadcast MAP frame includes modifying the flag bit, reassigning the number of nodes of the device identifier, and reallocating the new one.
  • the supplementary sub-domain of the device identification update of each node includes the original device identifier of the 8-bit node and the new device identifier of the assigned 8-bit node.
  • the message may be sent by means of broadcast or by unicasting to the node to which the new device identifier is assigned.
  • the format of the message when the broadcast is sent is similar to the previous 1) and 2), where it is necessary to indicate the effective time of the new device identification.
  • the device identifier update message is sent to the node to which the new device identifier is unicast separately. You only need to directly send the new device ID and the effective time, or add the original device ID.
  • the MAC address of the domain master node of the domain to which the node to which the new device identifier needs to be re-allocated does not need to include other identifiers such as the modified identifier bit and the length, and the message format is simple and easy, which can reduce the implementation complexity.
  • the processor 22 also performs scheduling and management according to the new device identifier.
  • a unified device identifier may also be determined for the media portion corresponding to the different domains and embodied in the MAP.
  • FIG. 5 is a schematic flowchart diagram of a domain merging method according to a first embodiment of the present invention. As shown in FIG. 5, the domain merging method of the first embodiment includes:
  • S11 Send a node switch indication message to the domain master node in the two domains when the domain names of the two domains are the same, and the node switch indication message is used to switch the domain master node in the two domains to the inter-mediated bridge and synchronize.
  • the node switching indication message may use an existing message in G.9961, that is, increase the reason for the handover in the existing DM_Handover Request.ind.
  • S12 Analyze the conflict situation of the device identifiers in the two domains, and assign a new device identifier to one of the nodes of each pair of device identifier conflicts.
  • the device identifiers of the nodes in the two domains are obtained by the topology maintenance process before the handover or by the node handover procedure. Before assigning a new device ID to one of the nodes that identify the conflicts for each pair of devices, it is necessary to analyze the conflicts of the device IDs in the two domains. If the device IDs in the two domains do not conflict, resource scheduling and management are performed by sending a valid media access plan; if the device IDs in the two domains are in conflict, the conflicting nodes are identified for each pair of devices in the two domains. A node in the middle assigns a new device ID. Specifically, there are two ways to assign a new device identity to a node with a device identity conflict.
  • the first method is to compare the total number of flows established by the nodes with conflicting device identifiers in the two domains, and assign new device identifiers to the nodes with conflicting device identifiers in the domain with a smaller total number of flows.
  • the device IDs of N2 and N4, N3, and N6 conflict, where N2 has established 2 flows, N4 has established 0 flows, N3 has established 2 flows, N6 has established 1 flow, and then 2
  • the total number of flows established by the node with the device ID conflict in the domain is 4 for domain B and 1 for domain C. Therefore, new device IDs are assigned to N4 and N6 in domain C.
  • the second method is: comparing the total length of the allocated time slots of the flow established by the node with the device identification conflict in the two domains, and allocating the new device identifier to the node with the device identification conflict of the domain with the smaller total length of the total time slot allocation. . As shown in FIG.
  • the device identifiers of N2 and N4, N3, and N6 conflict wherein the slot lengths allocated for N2 and N3 are 5 ms and 8 ms, respectively, and the slot lengths allocated for N4 and N6 are 0 ms and 6 ms, respectively.
  • the total length of the allocated time slot of the flow established by the node whose device identifier conflicts in the two domains is 13 ms and the domain C is 6 ms. Therefore, new device identifiers are assigned to N4 and N6 in the domain C. In this way, in the process of domain merging, there is no need to interrupt the service transmission, and the seamless integration of the domains can be ensured, and the traffic transmission is not affected, and the implementation complexity is reduced. If the total length of the time slot allocated by the number of flows established by the node whose device identifier conflicts in the two domains is the same is the same, the node with the device identity conflict in any of the domains is randomly assigned a new device identity.
  • the conflict situation of the device identifiers in the two domains is analyzed, and when the device identifiers in the two domains have conflicts, the conflicts may be identified for each pair of devices in the two domains.
  • Festival Point comparison according to the number of flows established by the node, replace the device identifier with the node with fewer flows. That is, the number of flows established by the node whose device identifier conflicts is sorted, and the device identifier update is performed on the node with fewer flows, which can reduce the implementation complexity. As shown in FIG.
  • N2 and N4, N3, and N6 conflict, where N2 has established 2 flows, N4 has established 0 flows, N3 has established 2 flows, and N6 has established 1 flow, and then is a domain.
  • N4 and N6 in B are assigned new device identification. If the number of flows established by the two nodes is equal, a new device identifier is assigned to the node with the smaller MAC address. Of course, in other embodiments of the present invention, a new device identifier may also be received for a node with a larger MAC address.
  • the new device identifier is sent to the node whose device identifier conflicts by adding a device identifier update supplementary sub-domain in the broadcast media access plan frame, or by sending a device identifier update message.
  • the new device identifier is also sent to the node where the device identifier conflicts, so that the node works according to the new device identifier, which can be implemented in one of three ways:
  • the supplementary subfield of the device identity update added in the broadcast MAP frame includes the modification flag bit, the number of nodes that reassign the device identity, and 48 bits. MAC address and assigned device ID, etc.
  • the supplemental subfield of the device identification update of each node includes a 48-bit MAC address and an assigned 8-bit device identifier.
  • the supplementary sub-domain of the device identity update added in the broadcast MAP frame includes modifying the flag bit, reassigning the number of nodes of the device identity, and reallocating new
  • the device identifies the 48-bit MAC address of the domain master node of the domain to which the node belongs, the original device identifier of the node, and the new device identifier of the node.
  • the supplementary sub-domain of the device identification update of each node includes the original device identifier of the 8-bit node and the new device identifier of the assigned 8-bit node.
  • the message may be sent by means of broadcast or by unicasting to the node to which the new device identifier is assigned.
  • the format of the message when the broadcast is sent is similar to the previous 1) and 2), where it is necessary to indicate the effective time of the new device identification.
  • the device identifier update message is sent to the node to which the new device identifier is unicast separately. You only need to directly send the new device ID and the effective time, or add the original device ID.
  • the message format is simple and easy, which can reduce the complexity of the implementation.
  • the node After the node works according to the new device identifier, it can be scheduled according to the new device identifier. Alternatively, if the DM function is switched back to a higher-order node, a unified device identifier can be determined for the media parts on both sides. Reflected in the MAP.
  • FIG. 6 is a block diagram showing the structure of a node in the first embodiment of the present invention.
  • the node 30 includes a receiving module 31 and a switching module 32.
  • the receiving module 31 is configured to receive a node switching indication message, where the domain where the node is located is the same as the domain name of another domain.
  • the switching module 31 is connected to the receiving module 31, and is configured to switch the domain master node of the domain in which the node is located to the inter-carrier bridge according to the node switching indication message and perform synchronization to complete domain merging with another domain.
  • the node switch indication message can use the existing message DM_HandoverRequest.ind in G.9961.
  • the reason for the handover is added to the node switching indication message.
  • the receiving module 31 is further configured to: receive a new device identifier allocated by the inter-carrier bridge, and the switching module 32 operates according to the new device identifier.
  • the inter-carrier bridge obtains the device identifiers of all the nodes in the two domains by the topology maintenance process before the handover or through the node handover process; and then analyzes the two domains. The conflict condition of the device ID in .
  • the receiving module 31 receives the new device identifier allocated by the inter-carrier bridge.
  • the total number of flows established by the node with the device ID conflict in the domain where the node is located is the same as the total number of flows established by the node with the device ID in the other domain, or the flow established by the node with the device ID conflict in the domain where the node is located is allocated.
  • the total length of the slot is the same as the total length of the allocated slot of the stream established by the node whose device identifier conflicts in another domain, and the receiving module 31 of the node that conflicts with the node device identifier in the node or another domain receives the new device identifier. .
  • the receiving module 31 receives the new device identity assigned by the inter-mediated bridge. If the number of streams established by the two nodes whose device identifier conflicts is equal, the receiving module 31 of the node with the smaller MAC address receives the new device identifier. Of course, in other embodiments of the present invention, the receiving module 31 of the node with a larger MAC address may also receive the new device identifier. In this way, there is no need to interrupt the service transmission during the process of domain merging. Ensuring seamless integration of domains does not affect the flow of traffic services, while reducing implementation complexity.
  • the receiving module 31 can receive the new device identifier and the effective time allocated by the inter-carrier bridge in one of three ways:
  • the supplemental sub-domain of the device identity update added in the broadcasted MAP frame includes a modified flag bit, a number of nodes that re-allocate the device identity, 48 bits MAC address and assigned device ID, etc.
  • the supplemental subfield of the device identification update of each node includes a 48-bit MAC address and an assigned 8-bit device identifier.
  • the supplemental sub-domain of the device identity update added in the broadcast MAP frame includes modifying the flag bit, reassigning the number of nodes of the device identity, reallocating The 48-bit MAC address of the domain master node of the domain to which the new device identifier belongs, the original device identifier of the node, and the new device identifier of the node.
  • the supplementary sub-domain of the device identification update of each node includes the original device identifier of the 8-bit node and the new device identifier of the assigned 8-bit node.
  • the message may be sent by means of broadcast or by unicasting to the node to which the new device identifier is assigned.
  • the format of the message when the broadcast is sent is similar to the previous 1) and 2), where it is necessary to indicate the effective time of the new device identification.
  • the node works according to the new device identifier.
  • the inter-carrier bridge performs resource scheduling according to the new device identifier. For example, the DM function is switched back to the node with higher ranking, and a unified device identifier can be determined for the media portion corresponding to the different domains and embodied in the MAP.
  • FIG. 7 is a schematic structural diagram of a node according to a second embodiment of the present invention.
  • the node 40 includes a transceiver 41, a processor 42, a memory 43, and a data bus 44, wherein the receiver 41, the processor 42, and the memory 43 are respectively connected to the data bus 44 to perform data through the data bus 44. Interaction.
  • the transceiver 41 receives the node handover indication message, where the domain where the node is located is the same as the domain name of another domain.
  • the processor 42 switches the domain master node of the domain in which the node is located to the inter-mediated bridge according to the node switching indication message and synchronizes to complete domain merging with another domain.
  • Node cut The change indication message can use the existing message DM_HandoverRequest.ind in G.9961.
  • the reason for the handover is added to the node switching indication message.
  • the transceiver 41 also receives a new device identification assigned by the inter-mediated bridge, and the processor 42 operates in accordance with the new device identification. Before the transceiver 41 receives the new device identifier assigned by the inter-carrier bridge, the inter-carrier bridge obtains the device identifiers of all the nodes in the two domains through the topology maintenance process before the handover or through the node handover process; and then analyzes the two domains. The conflict condition of the device ID in .
  • the memory 43 is used to store device identification and node switching indication messages.
  • the transceiver 41 receives the new device identity assigned by the inter-carrier bridge.
  • the total number of flows established by the node with the device ID conflict in the domain where the node is located is the same as the total number of flows established by the node with the device ID in the other domain, or the flow established by the node with the device ID conflict in the domain where the node is located is allocated.
  • the total length of the slot is the same as the total length of the allocated slot of the stream established by the node whose device identifier conflicts in another domain, and the transceiver 41 of the node in the node or another domain that conflicts with the node device identifier receives the new device identifier. .
  • the transceiver 41 receives the new device identity assigned by the inter-mediated bridge. If the number of flows established by the two nodes whose device identification conflicts is equal, the transceiver 41 of the node with the smaller MAC address receives the new device identification. Of course, in other embodiments of the present invention, the transceiver 41 of the node with a larger MAC address may also receive the new device identifier. In this way, in the process of domain merging, there is no need to interrupt the service transmission, and the seamless integration of the domains can be ensured, and the traffic transmission is not affected, and the implementation complexity is reduced.
  • the transceiver 41 can receive the new device identifier and the effective time allocated by the inter-carrier bridge in one of three ways:
  • the supplemental sub-domain of the device identity update added in the broadcasted MAP frame includes a modified flag bit, a number of nodes that re-allocate the device identity, 48 bits MAC address and assigned device ID, etc.
  • the supplemental subfield of the device identification update of each node includes a 48-bit MAC address and an assigned 8-bit device identifier.
  • the supplemental sub-domain of the device identity update added in the broadcast MAP frame includes modifying the flag bit, reassigning the number of nodes of the device identity, reallocating The 48-bit MAC address of the domain master node of the domain to which the new device identifier belongs, the original device identifier of the node, and the new device identifier of the node.
  • the supplementary sub-domain of the device identification update of each node includes the original device identifier of the 8-bit node and the new device identifier of the assigned 8-bit node.
  • the message may be sent by means of broadcast or by unicasting to the node to which the new device identifier is assigned.
  • the format of the message when the broadcast is sent is similar to the previous 1) and 2), where it is necessary to indicate the effective time of the new device identification.
  • the node works according to the new device identification.
  • the inter-carrier bridge performs resource scheduling according to the new device identifier. For example, the DM function is switched back to the node with higher ranking, and a unified device identifier can be determined for the media portion corresponding to the different domains and embodied in the MAP.
  • FIG. 8 is a schematic flowchart diagram of a domain merging method according to a second embodiment of the present invention. As shown in FIG. 8, the domain merging method of the second embodiment includes:
  • S20 The domain master node of the domain where the node is located receives the node handover indication message, where the domain where the node is located is the same as the domain name of another domain.
  • the domain names of the nodes in the domain B and the domain C in FIG. 2 are the same, and the two need to be merged into one domain.
  • the node switch indication message can use the existing message DM_HandoverRequest.ind in G.9961.
  • the reason for the handover is added to the node switching indication message.
  • S21 The domain master node of the domain in which the node is located switches to the inter-mediated bridge according to the node switching indication message and performs synchronization to complete domain merging with another domain.
  • the domain master node of the domain in which the node is located is switched to the inter-media bridge, and the original domain master node in the domain is transformed into a common node.
  • the node receives the new device identifier assigned by the inter-media bridge and works according to the new device identifier, where the node can be all nodes in the merged domain.
  • the inter-mediated bridge Before the node receives the new device identifier assigned by the inter-carrier bridge, the inter-mediated bridge obtains the device label of all nodes in the two domains by the topology maintenance process before the handover or through the node handover procedure. Knowledge; and then analyze the conflicts of device IDs in the two domains. If the device identifications in the two domains have conflicts, the node following the predetermined rule receives the new device identification assigned by the inter-mediated bridge.
  • the predetermined rule includes: the total number of flows established by the node whose device identifier conflicts in the domain of the node is smaller than the total number of flows established by the node whose device identifier conflicts in another domain, or the flow established by the node whose device identifier conflicts in the domain of the node
  • the total length of the allocated time slots is smaller than the total length of the allocated time slots of the flow established by the node whose device identifier conflicts in another domain, or the number of flows established by the node is smaller than the flow established by the node in the other domain that conflicts with the node device identifier. number.
  • the total number of flows established by the node with the device ID conflict in the domain where the node is located is the same as the total number of flows established by the node with the device ID in the other domain, or the flow established by the node with the device ID conflict in the domain where the node is located is allocated.
  • the total length of the slot is the same as the total length of the slot allocated by the node established by the node in the other domain, and the node in the node or another domain that conflicts with the node device identifier receives the new device identifier. If the number of flows established by the two nodes whose device ID conflicts is equal, the node with the smaller MAC address receives the new device identifier.
  • a node with a larger MAC address may also receive a new device identifier.
  • a new device identifier In this way, in the process of domain merging, there is no need to interrupt the service transmission, and the seamless integration of the domains can be ensured, and the traffic transmission is not affected, and the implementation complexity is reduced.
  • the node receives the new device identifier and the effective time allocated by the inter-carrier bridge in one of three ways:
  • the supplemental sub-domain of the device identity update added in the broadcasted MAP frame includes a modified flag bit, a number of nodes that re-allocate the device identity, 48 bits MAC address and assigned device ID, etc.
  • the supplemental subfield of the device identification update of each node includes a 48-bit MAC address and an assigned 8-bit device identifier.
  • the supplemental sub-domain of the device identity update added in the broadcast MAP frame includes modifying the flag bit, reassigning the number of nodes of the device identity, reallocating The 48-bit MAC address of the domain master node of the domain to which the new device identifier belongs, the original device identifier of the node, and the new device identifier of the node.
  • the supplementary sub-domain of the device identification update of each node includes the original device identifier of the 8-bit node and the new device identifier of the assigned 8-bit node.
  • the message may be sent by means of broadcast or by unicasting to the node to which the new device identifier is assigned.
  • the format of the message when the broadcast is sent is similar to the previous 1) and 2), where it is necessary to indicate the effective time of the new device identification.
  • sending unicast you only need to send the new device ID and the effective time directly, or add the original settings based on this.
  • the identifier and the MAC address of the domain master node of the domain to which the node to which the new device identifier needs to be reassigned does not need to include other identifiers such as the modified identifier bit and the length as in the broadcast message.
  • the message format is simple and easy to implement, and the implementation can be reduced. the complexity.
  • the node works according to the new device ID.
  • the inter-carrier bridge performs resource scheduling according to the new device identifier. For example, the DM function is switched back to the node with higher ranking, and a unified device identifier can be determined for the media portion corresponding to the different domains and embodied in the MAP.
  • the present invention analyzes the conflict condition of the device identifiers in the two domains; when the device identifiers in the two domains collide, assign a new device identifier to one of the nodes of each pair of device identifier conflicts; The new device ID and the effective time are set so that the node works according to the new device ID. This ensures that the domain is seamlessly merged without affecting the traffic service transmission and reduces the implementation complexity.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种域合并方法及媒介间桥接器、节点，媒介间桥接器包括：冲突分析模块用于分析域名相同的两个域中的设备标识的冲突情况；冲突处理模块用于在两个域中的设备标识冲突时，为每对设备标识冲突的节点中的一个节点分配新的设备标识；广播模块与冲突处理模块连接，用于广播新的设备标识以及生效时间，以使节点按照新的设备标识进行工作，其中生效时间为新的设备标识生效的时间点。通过以上公开内容，本发明能够保证域无缝合并，不影响流业务传输，同时降低实现复杂度。

Description

域合并方法及媒介间桥接器、节点 【技术领域】
本发明涉及通信领域，特别是涉及一种域合并方法及媒介间桥接器、节点。
【背景技术】
随着家庭网络应用对带宽需求的日益增长以及用户对服务多样化要求的增多，任何一种单一的家庭网络技术已不能同时满足上述需求。2010年国际电信联盟(ITU-T)批准的G.hn标准，可以支持电力线、同轴电缆和电话线三种传输介质，统一了家庭网络标准。通过该技术，可以支持多个数据或者视频流的分配，包括遍布整个家庭的高清电视(HDTV)和标清电视(SDTV)，支持家庭娱乐应用和宽带高速上网。
家庭网络可以包含一个或者多个域(domain)，每个域一般是一个集中式管理网络。每个域中有一个域主节点(Domain Master，DM)，DM除了具备普通的节点的通信功能，还要负责整个域的管理，包括域的建立、节点注册、域的带宽分配和资源调度、与多个相邻域或网络的协调、网络功耗管理等。对于工作于安全模式的域来说，每个域中还包含一个安全控制器(security controller，SC)，SC负责域中节点的认证和密钥管理流程的管理，每个已注册的节点都要在向SC完成认证后才能获取密钥，进行安全的数据的传输。
DM通过在每个媒体接入控制(Media Access Control，MAC)周期发送媒体接入计划(Media Access Plan，MAP)来进行域的管理和资源调度。MAP中指示了下一个MAC周期的起始时间，以及为节点进行资源调度的传输机会的分配，以及其他域工作所需的相关参数。节点通过检测MAP帧来发现域的存在，并加入域。节点通过向DM发送注册请求来加入域，并在注册成功后，向SC进行认证，在认证成功后，才能开始进行数据传输。
为了保证服务质量(Quality of Service，QoS)，节点需要向DM申请建立服务流，若DM可以支持该服务流的建立，则同意该申请，并在服务流建立后，按照传送特性(Traffic SPECification，TSpec)进行资源调度。DM对服务流的调度方式可以采取持续性调度或非持续性调度，持续性调度为DM所发布的资源调度信息在若干个MAC周期内有效，持续性调度为DM所发布的资源调度信息仅在下一个MAC周期有效。
在G.hn中定义了媒介间桥接(Inter-Medium Bridge，IMB)功能，由于G.hn支持电力线、同轴电缆和电话线等多种传输介质，可通过IMB实现在A-接口以下，进行不同传输介质的域的互通，或同一个域工作于多种传输介质。
在应用G.hn的家庭网络中，可能存在如下场景：正在工作的G.hn域中的某1个或几个节点检测到来自另外的一个域的缺省媒体接入计划/转发的缺省媒体接入计划(Default Media Access Plan/Relayed Default Medium Access Plan，MAP-D/RMAP-D)帧或有效媒体接入计划/转发的有效媒体接入计划(Active Medium Access Plan/Relayed Active Medium Access Plan，MAP-A/RMAP-A)帧，且另一个域的域名与本域的域名相同，则需要对两个域进行合并。如图1所示，域A工作于电力线和电话线两种传输介质，并可以通过IMB实现互通，其中IMB为域A的DM。当IMB由于某种原因离线或掉线后，工作于电力线的部分和工作于电话线的部分将无法连通，原域A则分为了域B和域C两个独立的域，但域名会保持不变。其中域B工作于电力线，域C工作于电话线。当IMB设备重新上线后，会发现其N0和N1两个部分会分别加入域B和域C，即其N0部分执行域B中的功能，其N1部分执行域C中的功能，成功加入后，会发现域B和域C需要合并。
现有技术中，可以是两个需要合并的域的DM需要按照预定的规则判断哪个域要合并到另一个域，DM在确定自己的域B要合并到另一个域后，将自己域中的所有节点进行设置，各个节点设置之后，自行加入另一个域；也可以是两个域中的节点全部重置，所有节点从所在域中进行设置，并重新组网；或者一个域在判断需要合并到另一个域时，如域B判断其需要合并到域C时，向域C发送合并请求消息，域C收到合并请求后，确定是否能够支持及接受合并，如果可以，则返回合并确认消息，在收到合并确认消息后，向域C的所有节点广播一个合并指示消息，应包含确认消息中的所有有用信息。可见现有技术中的域合并方法时延较大，造成节点业务传输的中断，或者复杂度较高。
【发明内容】
有鉴于此，本发明实施例提供了一种域合并方法及媒介间桥接器、节点，保证域无缝合并，不影响流业务传输，同时降低实现复杂度。
第一方面提供一种媒介间桥接器，包括：冲突分析模块，用于分析域名相同的两个域中的设备标识的冲突情况；冲突处理模块，与冲突分析模块连接， 用于在两个域中的设备标识的冲突时，为每对设备标识冲突的节点中的一个节点分配新的设备标识；广播模块，与冲突处理模块连接，广播新的设备标识以及生效时间，以使节点按照新的设备标识进行工作，其中生效时间为新的设备标识生效的时间点。
结合第一方面的实现方式，在第一种可能的实现方式中，媒介间桥接器还包括检测模块和发送模块，检测模块用于检测两个域的域名是否相同，发送模块用于在两个域的域名相同时向两个域中的域主节点发送节点切换指示消息，节点切换指示消息用于将两个域中的域主节点切换至媒介间桥接器并进行同步。
结合第一方面的第一种可能的实现方式，在第二种可能的实现方式中，切换指示信息中包括切换原因。
结合第一方面的、第一方面的第一种可能的、第二种可能的实现方式，在第三种可能的实现方式中，冲突分析模块还用于：通过切换之前的拓扑维护过程或通过节点切换过程获得两个域中的节点的设备标识。
结合第一方面的第三种可能的实现方式，在第四种可能的实现方式中，冲突处理模块用于：如果冲突分析模块判断到两个域中的设备标识没有冲突，则冲突处理模块通过发送有效媒体接入计划进行资源调度和管理；如果冲突分析模块判断到两个域中的设备标识有冲突，则冲突处理模块为每对设备标识冲突的节点中的一个节点分配新的设备标识。
结合第一方面的、第一方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的实现方式，在第五种可能的实现方式中，冲突处理模块还用于：对比两个域中设备标识冲突的节点所建立的总流数，为总流数较小的域中的设备标识冲突的节点分配新的设备标识。
结合第一方面的、第一方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的实现方式，在第六种可能的实现方式中，冲突处理模块还用于：如果对比两个域中设备标识冲突的节点所建立的总流数相同，则随机为其中任一域中的设备标识冲突的节点分配新的设备标识。
结合第一方面的、第一方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的实现方式，在第七种可能的实现方式中，冲突处理模块用于：对比两个域中设备标识冲突的节点建立的流所分配时隙的总长度，为总的时隙分配总长度较小的域中的设备标识冲突的节点分配新的设备标识。
结合第一方面的、第一方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的实现方式，在第八种可能的实现方式中，冲突处理模块还用于：如果对比两个域中设备标识冲突的节点建立的流数分配的时隙的总长度相同，则随机为其中任一域中的设备标识冲突的节点分配新的设备标识。
结合第一方面的、第一方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的实现方式，在第九种可能的实现方式中，冲突处理模块用于：对两个域中的每对设备标识冲突的节点进行对比，根据每对设备标识冲突的节点建立的流数，对建立的流数较少的节点更换设备标识。
结合第一方面的、第一方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的、第五种可能的、第六种可能的、第七种可能的、第八种可能的、第九种可能的实现方式，在第十种可能的实现方式中，广播模块用于：通过在广播的媒体接入计划帧中增加设备标识更新补充子域，或者通过发送设备标识更新消息的方式将新的设备标识下发至设备标识冲突的节点。
结合第一方面的实现方式，在第十一种可能的实现方式中，媒介间桥接器还包括调度模块，用于按照新的设备标识进行调度和管理。
第二方面提供一种域合并方法，包括：分析域名相同两个域中的设备标识的冲突情况；在两个域中的设备标识冲突时，为每对设备标识冲突的两个节点中的一个节点分配新的设备标识；广播新的设备标识以及生效时间，以使节点按照新的设备标识进行工作，其中生效时间为新的设备标识生效的时间点。
结合第二方面的实现方式，在第一种可能的实现方式中，在分析域名相同的两个域中的设备标识的冲突情况之前，检测两个域的域名是否相同，在两个域的域名相同时向两个域中的域主节点发送节点切换指示消息，节点切换指示消息用于将两个域中的域主节点切换至媒介间桥接器并进行同步。
结合第二方面的第一种可能的实现方式，在第二种可能的实现方式中，切换指示信息中包括切换原因。
结合第二方面的、第二方面的第一种可能的、第二种可能的实现方式，在第三种可能的实现方式中，分析域名相同的两个域中的设备标识的冲突情况包括：通过切换之前的拓扑维护过程或通过节点切换过程获得两个域中的节点的设备标识。
结合第二方面的第三种可能的实现方式，在第四种可能的实现方式中，方法还包括：如果两个域中的设备标识没有冲突，则通过发送有效媒体接入计划 进行资源调度和管理；如果两个域中的设备标识有冲突，则为每对设备标识冲突的节点中的一个节点分配新的设备标识。
结合第二方面的、第二方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的实现方式，在第五种可能的实现方式中，为每对设备标识冲突的节点中的一个节点分配新的设备标识，包括：对比两个域中设备标识冲突的节点所建立的总流数，为总流数较小的域中的设备标识冲突的节点分配新的设备标识。
结合第二方面的、第二方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的实现方式，在第六种可能的实现方式中，为每对设备标识冲突的节点中的一个节点分配新的设备标识，还包括：如果对比两个域中设备标识冲突的节点所建立的总流数相同，则随机为其中任一域中的设备标识冲突的节点分配新的设备标识。
结合第二方面的、第二方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的实现方式，在第七种可能的实现方式中，为每对设备标识冲突的节点中的一个节点分配新的设备标识，包括：对比两个域中设备标识冲突的节点建立的流所分配时隙的总长度，为总的时隙分配总长度较小的域中的设备标识冲突的节点分配新的设备标识。
结合第二方面的、第二方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的实现方式，在第八种可能的实现方式中，为每对设备标识冲突的节点中的一个节点分配新的设备标识，还包括：如果对比两个域中设备标识冲突的节点建立的流数分配的时隙的总长度相同，则随机为其中任一域中的设备标识冲突的节点分配新的设备标识。
结合第二方面的、第二方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的实现方式，在第九种可能的实现方式中，为每对设备标识冲突的节点中的一个节点分配新的设备标识，包括：对两个域中的设备标识冲突的节点进行对比，根据每对设备标识冲突的节点建立的流数，对建立的流数较少的节点更换设备标识。
结合第二方面的、第二方面的第一种可能的、第二种可能的、第三种可能的、第四种可能的、第五种可能的、第六种可能的、第七种可能的、第八种可能的、第九种可能的实现方式，在第十种可能的实现方式中，广播新的设备标识以及生效时间，包括：通过在广播的媒体接入计划帧中增加设备标识更新补 充子域，或者通过发送设备标识更新消息的方式将新的设备标识下发至设备标识冲突的节点。
结合第二方面的实现方式，在第十一种可能的实现方式中，方法还包括：按照所述新的设备标识进行调度和管理。
第三方面提供一种节点，包括：接收模块，用于接收节点切换指示消息，其中节点所在的域与另一个域的域名相同；切换模块，与接收模块连接，用于根据节点切换指示消息将节点所在的域的域主节点切换至媒介间桥接器并进行同步以完成与另一个域的域合并。
结合第三方面的实现方式，在第一种可能的实现方式中，接收模块还用于：接收媒介间桥接器分配的新的设备标识；切换模块按照新的设备标识进行工作。
结合第三方面的第一种可能的实现方式，在第二种可能的实现方式中，如果节点所在域中设备标识冲突的节点所建立的总流数小于另一个域中设备标识冲突的节点所建立的总流数，或节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度小于另一个域中设备标识冲突的节点建立的流所分配时隙的总长度，则接收模块接收媒介间桥接器分配的新的设备标识。
结合第三方面的第一种可能的实现方式，在第三种可能的实现方式中，如果节点所在域中设备标识冲突的节点所建立的总流数与另一个域中设备标识冲突的节点所建立的总流数相同，或节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度与另一个域中设备标识冲突的节点建立的流所分配时隙的总长度相同，则节点或另一个域中与该节点设备标识冲突的节点的接收模块接收新的设备标识。
结合第三方面的实现方式，在第四种可能的实现方式中，如果节点建立的流数小于另一个域中与节点设备标识冲突的节点建立的流数，则接收模块接收媒介间桥接器分配的新的设备标识。
第四方面提供一种域合并方法，包括：节点所在的域的域主节点接收节点切换指示消息，其中节点所在的域与另一个域的域名相同；节点所在的域的域主节点根据节点切换指示消息切换至媒介间桥接器并进行同步以完成与另一个域的域合并。
结合第四方面的实现方式，在第一种可能的实现方式中，方法还包括：节点接收媒介间桥接器分配的新的设备标识，并按照新的设备标识进行工作。
结合第四方面的第一种可能的实现方式，在第二种可能的实现方式中，节 点所在域中设备标识冲突的节点所建立的总流数小于另一个域中设备标识冲突的节点所建立的总流数，或节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度小于另一个域中设备标识冲突的节点建立的流所分配时隙的总长度。
结合第四方面的第二种可能的实现方式，在第三种可能的实现方式中，节点接收新的设备标识，包括：如果节点所在域中设备标识冲突的节点所建立的总流数与另一个域中设备标识冲突的节点所建立的总流数相同，或节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度与另一个域中设备标识冲突的节点建立的流所分配时隙的总长度相同，则节点或另一个域中与该节点设备标识冲突的节点接收新的设备标识。
结合第四方面的实现方式，在第四种可能的实现方式中，节点接收新的设备标识，包括：节点建立的流数小于另一个域中与节点设备标识冲突的节点建立的流数。
本发明通过分析域名相同的两个域中的设备标识的冲突情况；在两个域中的设备标识冲突时，为每对设备标识冲突的节点中的一个节点分配新的设备标识；广播新的设备标识以及生效时间，以使节点按照新的设备标识进行工作，能够保证域无缝合并，不影响流业务传输，同时降低实现复杂度。
【附图说明】
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是现有技术中的域合并方法示意图；
图2是本发明的域合并方法的示意图；
图3本发明第一实施例的媒介间桥接器的结构示意图；
图4本发明第二实施例的媒介间桥接器的结构示意图；
图5本发明第一实施例的域合并方法的流程示意图；
图6是本发明第一实施例的节点的结构示意图；
图7是本发明第二实施例的节点的结构示意图；
图8是本发明第二实施例的域合并方法的流程示意图。
【具体实施方式】
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
请参阅图2，图2是本发明的域合并方法的流程示意图。如图2所示，域B和域C的域名相同，即域B和域C需要进行合并。其中域B至少包括节点N0、N2、N3，域C至少包括节点N1、N4、N5、N6。当然域B和域C具体包括的节点以及节点数量视具体情况而定，在此并不作限制。域B可以工作于电力线、电话线、或同轴电缆等的至少之一，域C也可以工作于电话线、电力线、或同轴电缆等的至少之一，但域B和域C工作于不同的线缆。媒介间桥接器IMB包括节点N0和节点N1，分别工作于域B和域C。媒介间桥接器IMB上线时，检测位于域B和域C的域名是否相同。具体地，媒介间桥接器IMB检测位于域B中的节点N2和位于域C中的节点N4的域名是否相同。在位于域B中的节点N2和位于域C中的节点N4的域名相同时，节点N0和节点N1分别向域B中的域主节点DM1和域C中的域主节点DM2发送节点切换指示消息。在本发明实施例中，域主节点DM1即为节点N2，域主节点DM2即为节点N4。当然在本发明的其他实施例中，域主节点DM1可以不是节点N2，域主节点DM4不是节点N1。域主节点DM1和DM2收到节点切换指示消息后按照G.9961规定，执行节点切换流程，即将域主节点切换至媒介间桥接器IMB。其中，节点切换指示消息可使用G.9961中的现有消息，即在现有的DM_Handover Request.ind中增加切换原因。节点切换指示消息的格式如表1所示。
表1
Figure PCTCN2015081063-appb-000001
媒介间桥接器IMB通过切换之前的拓扑维护过程或通过节点切换过程获得 两个域的所有节点的设备标识信息。媒介间桥接器IMB分析两个域中的设备标识的冲突情况。如果两个域中的节点没有冲突，则直接执行域主节点功能，通过发送MAP-A进行资源调度和管理。如果两个域中的节点有冲突，则为每对设备标识冲突的节点中的一个节点分配新的设备标识。具体地，媒介间桥接器IMB可以对比两个域中设备标识冲突的节点所建立的总流数，为总流数较小的域中的设备标识冲突的节点分配新的设备标识。如果对比两个域中设备标识冲突的节点所建立的总流数相同，则随机为其中任一域中的设备标识冲突的节点分配新的设备标识。媒介间桥接器IMB也可以对比两个域中设备标识冲突的节点建立的流所分配时隙的总长度，为总的时隙分配总长度较小的域中的设备标识冲突的节点分配新的设备标识。如果对比两个域中设备标识冲突的节点建立的流数分配的时隙的总长度相同，则随机为其中任一域中的设备标识冲突的节点分配新的设备标识。或者媒介间桥接器IMB也可以对两个域中的每对设备标识冲突的节点进行对比，根据每对设备标识冲突的节点建立的流数，对建立的流数较少的节点更换设备标识。如果两个设备标识冲突的节点建立的流数相等，则为MAC地址较小的节点分配新的设备标识。当然在本发明的其他实施例中，也可以为MAC地址较大的节点接收新的设备标识。
媒介间桥接器IMB按照新的设备标识进行调度和管理。同时可选地，将域主节点切换回排序更高的节点。媒介间桥接器IMB还为分别对应不同域的媒介的部分确定一个统一的设备标识，并在MAP中体现。
媒介间桥接器IMB将分配的新的设备标识下发至设备标识冲突的节点，即广播新的设备标识，以及生效时间，以使节点按照新的设备标识进行工作，其中生效时间为新的设备标识生效的时间点。媒介间桥接器IMB可以通过在广播的媒体接入计划帧中增加设备标识更新补充子域，或者通过发送设备标识更新消息的方式将分配的新的设备标识下发至设备标识冲突的节点。具体地媒介间桥接器IMB可以通过以下三种方式之一实现广播新的设备标识，以及生效时间：
1)通过在广播的MAP帧中增加“设备标识更新补充子域”，第一种格式如表2所示。
表2 广播的MAP帧中增加“设备标识更新补充子域”的第一种格式
Figure PCTCN2015081063-appb-000002
Figure PCTCN2015081063-appb-000003
从表2中可知，在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、48比特的MAC地址以及分配的设备标识等。其中每一个节点的设备标识更新的补充子域包括48比特的MAC地址以及分配的对应的8比特的设备标识。
2)通过在广播的MAP帧中增加“设备标识更新补充子域”，第二种格式如表3所示。
表3 广播的MAP帧中增加“设备标识更新补充子域”的第二种格式
Figure PCTCN2015081063-appb-000004
与表2中的格式不同，表3中在广播的MAP帧中增加的设备标识更新的补 充子域包括修改标志位、重新分配设备标识的节点数、重新分配新的设备标识的节点原来所属的域的域主节点的48比特的MAC地址、节点原来的设备标识以及节点新的设备标识等。其中每一个节点的设备标识更新的补充子域包括8比特的节点原来的设备标识以及分配的8比特的节点新的设备标识。
3)采用发送设备标识更新消息的方式，该消息可以通过广播的方式发送或通过向被分配新的设备标识的节点分别单播的方式发送。广播发送时消息格式与前面的1)和2)类似，其中需指示新的设备标识的生效时间。单播发送时，消息的格式如表4或表5所示。
表4
Figure PCTCN2015081063-appb-000005
表5
Figure PCTCN2015081063-appb-000006
从表4和表5可知，向被分配新的设备标识的节点分别单播的方式发送设备标识更新消息的方式只需要直接发送新的设备标识和生效时间即可，或者在此基础上增加原来的设备标识以及需重新分配新的设备标识的节点所属域的域主节点的MAC地址，而不需要包括修改标识位、长度等其他标识，消息格式简单易行，可以降低实现的复杂度。
节点接收到新的设备标识后，按照新的设备标识工作。，可选的，如将DM功能切换回排序更高的节点，也可以为分别对应不同域的媒介部分确定一个统一的设备标识并在MAP中体现。如此可以保证域无缝合并，不影响流业务传输， 同时降低实现复杂度。
图3本发明第一实施例的媒介间桥接器的结构示意图。媒介间桥接器10包括：冲突分析模块11、冲突处理模块12以及广播模块13。冲突分析模块11用于分析域名相同的两个域中的设备标识的冲突情况。冲突处理模块12与检测模块连接，用于在两个域中的任一对节点的设备标识冲突时，并为每对设备标识冲突的节点中的一个节点分配新的设备标识。广播模块13与冲突处理模块12连接，广播新的设备标识以及生效时间，以使节点按照新的设备标识进行工作。其中生效时间为新的设备标识生效的时间点。
在更具体的实施例中，切换指示信息中包括切换原因。冲突处理模块12用于：通过切换之前的拓扑维护过程或通过节点切换过程获得两个域中的节点的设备标识。冲突处理模块12在为每对设备标识冲突的节点中的一个节点分配新的设备标识之前，需要分析两个域中的设备标识的冲突情况。如果两个域中的设备标识没有冲突，则冲突处理模块12用于通过发送有效媒体接入计划进行资源调度和管理。如果两个域中的设备标识有冲突，则冲突处理模块12用于为每对设备标识冲突的节点中的一个节点分配新的设备标识。
具体地，冲突处理模块12可以有两种方法为设备标识冲突的节点分配新的设备标识。第一种方法为：冲突处理模块12对比两个域中设备标识冲突的节点所建立的总流数，为总流数较小的域中的设备标识冲突的节点分配新的设备标识。如果对比两个域中设备标识冲突的节点所建立的总流数相同，则冲突处理模块12随机为其中任一域中的设备标识冲突的节点分配新的设备标识。第二种方法为：对比两个域中设备标识冲突的节点建立的流所分配时隙的总长度，冲突处理模块12为总的时隙分配总长度较小的域中的设备标识冲突的节点分配新的设备标识。如果对比两个域中设备标识冲突的节点建立的流数分配的时隙的总长度相同，则冲突处理模块12随机为其中任一域中的设备标识冲突的节点分配新的设备标识。如此在进行域合并的过程中无需中断业务传输，能够保证域无缝合并，不影响流业务传输，同时降低实现复杂度。
在本发明实施例中，冲突处理模块12还可以对两个域中的每对设备标识冲突的节点进行对比，根据节点建立的流数，对建立的流数较少的节点更换设备标识。也即根据设备标识冲突的节点建立的流数进行排序，对流数较少的节点进行设备标识更新，可以降低实现的复杂度。如果两个节点建立的流数相等，则为MAC地址较小的节点分配新的设备标识。当然在本发明的其他实施例中， 也可以为MAC地址较大的节点接收新的设备标识。
在本发明实施例中，广播模块13用于：通过在广播的媒体接入计划帧中增加设备标识更新补充子域，或者通过发送设备标识更新消息的方式将新的设备标识下发至设备标识冲突的节点。广播新的设备标识也即将分配的新的设备标识下发至设备标识冲突的节点，以便节点按照新的设备标识工作。可通过以下三种方式之一实现：
1)通过在广播的MAP帧中增加“设备标识更新补充子域”。在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、48比特的MAC地址以及分配的设备标识等。其中每一个节点的设备标识更新的补充子域包括48比特的MAC地址以及分配的对应的8比特的设备标识。
2)通过在广播的MAP帧中增加“设备标识更新补充子域”在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、重新分配新的设备标识的节点原来所属的域的域主节点的48比特的MAC地址、节点原来的设备标识以及节点新的设备标识等。其中每一个节点的设备标识更新的补充子域包括8比特的节点原来的设备标识以及分配的8比特的节点新的设备标识。
3)采用发送设备标识更新消息的方式，该消息可以通过广播的方式发送或通过向被分配新的设备标识的节点分别单播的方式发送。广播发送时消息格式与前面的1)和2)类似，其中需指示新的设备标识的生效时间。单播发送时，向被分配新的设备标识的节点分别单播的方式发送设备标识更新消息的方式只需要直接发送新的设备标识和生效时间即可，或者在此基础上增加原来的设备标识以及需重新分配新的设备标识的节点所属域的域主节点的MAC地址，而不需要包括修改标识位、长度等其他标识，消息格式简单易行，可以降低实现的复杂度。
在本发明实施例中，媒介间桥接器10还包括调度模块14，用于按照新的设备标识进行调度和管理。可选的，如将DM功能切换回排序更高的节点，也可以为分别对应不同域的媒介部分确定一个统一的设备标识并在MAP中体现。
图4本发明第二实施例的媒介间桥接器的结构示意图。媒介间桥接器20包括：收发器21、处理器22、存储器23以及数据总线24，其中接收器21、处理器22以及存储器23分别与数据总线24连接，以通过数据总线24进行数据交 互。
在本发明实施例中，处理器22检测两个域的域名是否相同，收发器21在两个域的域名相同时，向两个域中的域主节点发送节点切换指示消息，节点切换指示消息用于将两个域中的域主节点切换至媒介间桥接器并进行同步。处理器22分析两个域中的设备标识的冲突情况，并在两个域中的任一对节点的设备标识冲突时，为每对设备标识冲突的节点中的一个分配新的设备标识。收发器21广播新的设备标识以及生效时间，以使节点按照新的设备标识进行工作。其中切换指示信息中包括切换原因，生效时间为新的设备标识生效的时间点。
在本发明实施例中，处理器22通过切换之前的拓扑维护过程或通过节点切换过程获得两个域中的任一节点的设备标识。处理器22在为每对设备标识冲突的节点中的一个节点分配新的设备标识之前，需要分析两个域中的设备标识的冲突情况。如果两个域中的设备标识没有冲突，则处理器22通过发送有效媒体接入计划进行资源调度和管理。如果两个域中的设备标识有冲突，则处理器22用于为每对设备标识冲突的节点中的一个节点分配新的设备标识。存储器23用于存储设备标识以及切换指示信息。
具体地，处理器22可以有两种方法为设备标识冲突的节点分配新的设备标识。第一种方法为：处理器22对比两个域中设备标识冲突的节点所建立的总流数，为总流数较小的域中的设备标识冲突的节点分配新的设备标识。如果对比两个域中设备标识冲突的节点所建立的总流数相同，则处理器22随机为其中任一域中的设备标识冲突的节点分配新的设备标识。第二种方法为：对比两个域中设备标识冲突的节点建立的流所分配时隙的总长度，处理器22为总的时隙分配总长度较小的域中的设备标识冲突的节点分配新的设备标识。如果对比两个域中设备标识冲突的节点建立的流数分配的时隙的总长度相同，则处理器22随机为其中任一域中的设备标识冲突的节点分配新的设备标识。如此在进行域合并的过程中无需中断业务传输，能够保证域无缝合并，不影响流业务传输，同时降低实现复杂度。
在本发明实施例中，处理器22还可以对两个域中的每对设备标识冲突的节点进行对比，根据节点建立的流数，对建立的流数较少的节点更换设备标识。也即根据设备标识冲突的节点建立的流数进行排序，对流数较少的节点进行设备标识更新，可以降低实现的复杂度。如果两个节点建立的流数相等，则处理器22为MAC地址较小的节点分配新的设备标识。当然在本发明的其他实施例 中，也可以为MAC地址较大的节点接收新的设备标识。
在本发明实施例中，处理器22通过在广播的媒体接入计划帧中增加设备标识更新补充子域，或者通过发送设备标识更新消息的方式将新的设备标识下发至设备标识冲突的节点。广播新的设备标识也即将分配的新的设备标识下发至设备标识冲突的节点，以便节点按照新的设备标识工作。可通过以下三种方式之一实现：
1)通过在广播的MAP帧中增加“设备标识更新补充子域”。在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、48比特的MAC地址以及分配的设备标识等。其中每一个节点的设备标识更新的补充子域包括48比特的MAC地址以及分配的对应的8比特的设备标识。
2)通过在广播的MAP帧中增加“设备标识更新补充子域”在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、重新分配新的设备标识的节点原来所属的域的域主节点的48比特的MAC地址、节点原来的设备标识以及节点新的设备标识等。其中每一个节点的设备标识更新的补充子域包括8比特的节点原来的设备标识以及分配的8比特的节点新的设备标识。
3)采用发送设备标识更新消息的方式，该消息可以通过广播的方式发送或通过向被分配新的设备标识的节点分别单播的方式发送。广播发送时消息格式与前面的1)和2)类似，其中需指示新的设备标识的生效时间。单播发送时，向被分配新的设备标识的节点分别单播的方式发送设备标识更新消息的方式只需要直接发送新的设备标识和生效时间即可，或者在此基础上增加原来的设备标识以及需重新分配新的设备标识的节点所属域的域主节点的MAC地址，而不需要包括修改标识位、长度等其他标识，消息格式简单易行，可以降低实现的复杂度。
在本发明实施例中，处理器22还按照新的设备标识进行调度和管理。可选的，如将DM功能切换回排序更高的节点，也可以为分别对应不同域的媒介部分确定一个统一的设备标识并在MAP中体现。
图5是本发明第一实施例的域合并方法的流程示意图。如图5所示，第一实施例的域合并方法包括：
S10：检测到两个域的域名是否相同。如图2中域B和域C中的节点域名相 同，两者需要合并成一个域。
S11：在两个域的域名相同时向两个域中的域主节点发送节点切换指示消息，节点切换指示消息用于将两个域中的域主节点切换至媒介间桥接器并进行同步。其中，节点切换指示消息可使用G.9961中的现有消息，即在现有的DM_Handover Request.ind中增加切换原因。
S12：分析两个域中的设备标识的冲突情况，并为每对设备标识冲突的节点中的一个节点分配新的设备标识。
在S12中，通过切换之前的拓扑维护过程或通过节点切换过程获得两个域中的节点的设备标识。在为每对设备标识冲突的节点中的一个分配新的设备标识之前，需要分析两个域中的设备标识的冲突情况。如果两个域中的设备标识没有冲突，则通过发送有效媒体接入计划进行资源调度和管理；如果两个域中的设备标识有冲突，则为两个域中的每对设备标识冲突的节点中的一个节点分配新的设备标识。具体地，可以有两种方法为设备标识冲突的节点分配新的设备标识。第一种方法为：对比两个域中设备标识冲突的节点所建立的总流数，为总流数较小的域中的设备标识冲突的节点分配新的设备标识。如图2中，假设N2和N4、N3和N6的设备标识冲突，其中N2已建立2个流，N4已建立0个流，N3已建立2个流，N6已建立1个流，则两个域中设备标识冲突的节点建立的总流数，域B为4个，域C为1个，因此为域C中的N4和N6分配新的设备标识。如果对比两个域中设备标识冲突的节点所建立的总流数相同，则随机为其中任一域中的设备标识冲突的节点分配新的设备标识。第二种方法为：对比两个域中设备标识冲突的节点建立的流所分配时隙的总长度，为总的时隙分配总长度较小的域的设备标识冲突的节点分配新的设备标识。如图2中，假设N2和N4、N3和N6的设备标识冲突，其中为N2和N3分配的时隙长度分别为5ms和8ms，为N4和N6分配的时隙长度分别为0ms和6ms，则两个域中设备标识冲突的节点建立的流所分配时隙的总长度，域B为13ms，域C为6ms，因此为域C中的N4和N6分配新的设备标识。如此在进行域合并的过程中无需中断业务传输，能够保证域无缝合并，不影响流业务传输，同时降低实现复杂度。如果对比两个域中设备标识冲突的节点建立的流数分配的时隙的总长度相同，则随机为其中任一域中的设备标识冲突的节点分配新的设备标识。
在本发明的实施例中，在S12中，分析两个域中的设备标识的冲突情况，在两个域中的设备标识有冲突时，还可以对两个域中的每对设备标识冲突的节 点进行对比，根据节点建立的流数，对建立的流数较少的节点更换设备标识。也即根据设备标识冲突的节点建立的流数进行排序，对流数较少的节点进行设备标识更新，可以降低实现的复杂度。如图2中，假设N2和N4、N3和N6的设备标识冲突，其中N2已建立2个流，N4已建立0个流，N3已建立2个流，N6已建立1个流，则为域B中的N4和N6分配新的设备标识。如果两个节点建立的流数相等，则为MAC地址较小的节点分配新的设备标识。当然在本发明的其他实施例中，也可以为MAC地址较大的节点接收新的设备标识。
S13：广播新的设备标识以及生效时间，以使节点按照新的设备标识进行工作。
在S13中，通过在广播的媒体接入计划帧中增加设备标识更新补充子域，或者通过发送设备标识更新消息的方式将所述新的设备标识下发至所述设备标识冲突的节点。广播新的设备标识也即将分配的新的设备标识下发至设备标识冲突的节点，以便节点按照新的设备标识工作，具体地可通过以下三种方式之一实现：
1)通过在广播的MAP帧中增加“设备标识更新补充子域”，在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、48比特的MAC地址以及分配的设备标识等。其中每一个节点的设备标识更新的补充子域包括48比特的MAC地址以及分配的对应的8比特的设备标识。
2)通过在广播的MAP帧中增加“设备标识更新补充子域”，在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、重新分配新的设备标识的节点原来所属的域的域主节点的48比特的MAC地址、节点原来的设备标识以及节点新的设备标识等。其中每一个节点的设备标识更新的补充子域包括8比特的节点原来的设备标识以及分配的8比特的节点新的设备标识。
3)采用发送设备标识更新消息的方式，该消息可以通过广播的方式发送或通过向被分配新的设备标识的节点分别单播的方式发送。广播发送时消息格式与前面的1)和2)类似，其中需指示新的设备标识的生效时间。单播发送时，向被分配新的设备标识的节点分别单播的方式发送设备标识更新消息的方式只需要直接发送新的设备标识和生效时间即可，或者在此基础上增加原来的设备标识以及需重新分配新的设备标识的节点所属域的域主节点的MAC地址，而不 需要包括修改标识位、长度等其他标识，消息格式简单易行，可以降低实现的复杂度。
节点按照新的设备标识进行工作后，可以按照新的设备标识进行调度，可选的，如将DM功能切换回排序更高的节点，也可以为两侧媒介部分确定一个统一的设备标识并在MAP中体现。
图6是本发明第一实施例的节点的结构示意图。如图6所示，节点30包括：接收模块31和切换模块32。接收模块31用于接收节点切换指示消息，其中节点所在的域与另一个域的域名相同。切换模块31与接收模块31连接，用于根据节点切换指示消息将节点所在的域的域主节点切换至媒介间桥接器并进行同步以完成与另一个域的域合并。节点切换指示消息可使用G.9961中的现有消息DM_HandoverRequest.ind。可选地，节点切换指示消息中增加切换原因。
切换模块32将节点30所在的域的域主节点切换至媒介间桥接器后，域中原来的域主节点转变成普通节点。因此后续过程可以是针对合并域中所有的节点。接收模块31还用于：接收媒介间桥接器分配的新的设备标识，切换模块32按照新的设备标识进行工作。接收模块31在接收媒介间桥接器分配的新的设备标识之前，媒介间桥接器通过切换之前的拓扑维护过程或通过节点切换过程获得两个域中的所有节点的设备标识；进而分析两个域中的设备标识的冲突情况。
如果节点所在域中设备标识冲突的节点所建立的总流数小于另一个域中设备标识冲突的节点所建立的总流数，或节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度小于另一个域中设备标识冲突的节点建立的流所分配时隙的总长度，则接收模块31接收媒介间桥接器分配的新的设备标识。如果节点所在域中设备标识冲突的节点所建立的总流数与另一个域中设备标识冲突的节点所建立的总流数相同，或节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度与另一个域中设备标识冲突的节点建立的流所分配时隙的总长度相同，则节点或另一个域中与该节点设备标识冲突的节点的接收模块31接收新的设备标识。
如果节点建立的流数小于另一个域中与节点设备标识冲突的节点建立的流数，则接收模块31接收媒介间桥接器分配的新的设备标识。如果设备标识冲突的两个节点建立的流数相等，则MAC地址较小的节点的接收模块31接收新的设备标识。当然在本发明的其他实施例中，也可以MAC地址较大的节点的接收模块31接收新的设备标识。如此在进行域合并的过程中无需中断业务传输，能 够保证域无缝合并，不影响流业务传输，同时降低实现复杂度。
在本发明实施例中，接收模块31可以三种方式之一接收媒介间桥接器分配的新的设备标识以及生效时间：
1)通过在广播的MAP帧中增加“设备标识更新补充子域”，其中在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、48比特的MAC地址以及分配的设备标识等。其中每一个节点的设备标识更新的补充子域包括48比特的MAC地址以及分配的对应的8比特的设备标识。
2)通过在广播的MAP帧中增加“设备标识更新补充子域”，其中在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、重新分配新的设备标识的节点原来所属的域的域主节点的48比特的MAC地址、节点原来的设备标识以及节点新的设备标识等。其中每一个节点的设备标识更新的补充子域包括8比特的节点原来的设备标识以及分配的8比特的节点新的设备标识。
3)采用发送设备标识更新消息的方式，该消息可以通过广播的方式发送或通过向被分配新的设备标识的节点分别单播的方式发送。广播发送时消息格式与前面的1)和2)类似，其中需指示新的设备标识的生效时间。单播发送时，只需要直接发送新的设备标识和生效时间即可，或者在此基础上增加原来的设备标识以及需重新分配新的设备标识的节点所属域的域主节点的MAC地址，而不需要如广播消息中那样包括修改标识位、长度等其他标识，消息格式简单易行，可以降低实现的复杂度。
接收模块31接收新的设备标识后，节点按照新的设备标识进行工作。媒介间桥接器按照新的设备标识进行资源调度，如将DM功能切换回排序更高的节点，也可以为分别对应不同域的媒介部分确定一个统一的设备标识并在MAP中体现。
图7是本发明第二实施例的节点的结构示意图。如图7所示，节点40包括：收发器41、处理器42、存储器43以及数据总线44，其中接收器41、处理器42以及存储器43分别与数据总线44连接，以通过数据总线44进行数据交互。
在本发明实施例中，收发器41接收节点切换指示消息，其中节点所在的域与另一个域的域名相同。处理器42根据节点切换指示消息将节点所在的域的域主节点切换至媒介间桥接器并进行同步以完成与另一个域的域合并。节点切 换指示消息可使用G.9961中的现有消息DM_HandoverRequest.ind。可选地，节点切换指示消息中增加切换原因。
处理器42将节点40所在的域的域主节点切换至媒介间桥接器后，域中原来的域主节点转变成普通节点。因此后续过程可以是针对合并域中所有的节点。收发器41还接收媒介间桥接器分配的新的设备标识，处理器42按照新的设备标识进行工作。收发器41在接收媒介间桥接器分配的新的设备标识之前，媒介间桥接器通过切换之前的拓扑维护过程或通过节点切换过程获得两个域中的所有节点的设备标识；进而分析两个域中的设备标识的冲突情况。存储器43用于存储设备标识以及节点切换指示消息。
如果节点所在域中设备标识冲突的节点所建立的总流数小于另一个域中设备标识冲突的节点所建立的总流数，或节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度小于另一个域中设备标识冲突的节点建立的流所分配时隙的总长度，则收发器41接收媒介间桥接器分配的新的设备标识。如果节点所在域中设备标识冲突的节点所建立的总流数与另一个域中设备标识冲突的节点所建立的总流数相同，或节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度与另一个域中设备标识冲突的节点建立的流所分配时隙的总长度相同，则节点或另一个域中与该节点设备标识冲突的节点的收发器41接收新的设备标识。
如果节点建立的流数小于另一个域中与节点设备标识冲突的节点建立的流数，则收发器41接收媒介间桥接器分配的新的设备标识。如果设备标识冲突的两个节点建立的流数相等，则MAC地址较小的节点的收发器41接收新的设备标识。当然在本发明的其他实施例中，也可以MAC地址较大的节点的收发器41接收新的设备标识。如此在进行域合并的过程中无需中断业务传输，能够保证域无缝合并，不影响流业务传输，同时降低实现复杂度。
在本发明实施例中，收发器41可以三种方式之一接收媒介间桥接器分配的新的设备标识以及生效时间：
1)通过在广播的MAP帧中增加“设备标识更新补充子域”，其中在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、48比特的MAC地址以及分配的设备标识等。其中每一个节点的设备标识更新的补充子域包括48比特的MAC地址以及分配的对应的8比特的设备标识。
2)通过在广播的MAP帧中增加“设备标识更新补充子域”，其中在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、重新分配新的设备标识的节点原来所属的域的域主节点的48比特的MAC地址、节点原来的设备标识以及节点新的设备标识等。其中每一个节点的设备标识更新的补充子域包括8比特的节点原来的设备标识以及分配的8比特的节点新的设备标识。
3)采用发送设备标识更新消息的方式，该消息可以通过广播的方式发送或通过向被分配新的设备标识的节点分别单播的方式发送。广播发送时消息格式与前面的1)和2)类似，其中需指示新的设备标识的生效时间。单播发送时，只需要直接发送新的设备标识和生效时间即可，或者在此基础上增加原来的设备标识以及需重新分配新的设备标识的节点所属域的域主节点的MAC地址，而不需要如广播消息中那样包括修改标识位、长度等其他标识，消息格式简单易行，可以降低实现的复杂度。
收发器41接收新的设备标识后，节点按照新的设备标识进行工作。媒介间桥接器按照新的设备标识进行资源调度，如将DM功能切换回排序更高的节点，也可以为分别对应不同域的媒介部分确定一个统一的设备标识并在MAP中体现。
图8是本发明第二实施例的域合并方法的流程示意图。如图8所示，第二实施例的域合并方法包括：
S20：节点所在的域的域主节点接收节点切换指示消息，其中节点所在的域与另一个域的域名相同。
在S20中，如图2中域B和域C中的节点域名相同，两者需要合并成一个域。节点切换指示消息可使用G.9961中的现有消息DM_HandoverRequest.ind。可选地，节点切换指示消息中增加切换原因。
S21：节点所在的域的域主节点根据节点切换指示消息切换至媒介间桥接器并进行同步以完成与另一个域的域合并。
在S21中，节点所在的域的域主节点切换至媒介间桥接器，域中原来的域主节点转变成普通节点。节点接收媒介间桥接器分配的新的设备标识，并按照新的设备标识进行工作，此处的节点可以是合并域中所有的节点。
在节点接收媒介间桥接器分配的新的设备标识之前，媒介间桥接器通过切换之前的拓扑维护过程或通过节点切换过程获得两个域中的所有节点的设备标 识；进而分析两个域中的设备标识的冲突情况。如果两个域中的设备标识有冲突，则遵循预定规则的节点接收媒介间桥接器分配的新的设备标识。其中预定规则包括：节点所在域中设备标识冲突的节点所建立的总流数小于另一个域中设备标识冲突的节点所建立的总流数，或节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度小于另一个域中设备标识冲突的节点建立的流所分配时隙的总长度，或节点建立的流数小于另一个域中与该节点设备标识冲突的节点建立的流数。如果节点所在域中设备标识冲突的节点所建立的总流数与另一个域中设备标识冲突的节点所建立的总流数相同，或节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度与另一个域中设备标识冲突的节点建立的流所分配时隙的总长度相同，则节点或另一个域中与该节点设备标识冲突的节点接收新的设备标识。如果设备标识冲突的两个节点建立的流数相等，则MAC地址较小的节点接收新的设备标识。当然在本发明的其他实施例中，也可以MAC地址较大的节点接收新的设备标识。如此在进行域合并的过程中无需中断业务传输，能够保证域无缝合并，不影响流业务传输，同时降低实现复杂度。
在本发明实施例中，节点以三种方式之一接收媒介间桥接器分配的新的设备标识以及生效时间：
1)通过在广播的MAP帧中增加“设备标识更新补充子域”，其中在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、48比特的MAC地址以及分配的设备标识等。其中每一个节点的设备标识更新的补充子域包括48比特的MAC地址以及分配的对应的8比特的设备标识。
2)通过在广播的MAP帧中增加“设备标识更新补充子域”，其中在广播的MAP帧中增加的设备标识更新的补充子域包括修改标志位、重新分配设备标识的节点数、重新分配新的设备标识的节点原来所属的域的域主节点的48比特的MAC地址、节点原来的设备标识以及节点新的设备标识等。其中每一个节点的设备标识更新的补充子域包括8比特的节点原来的设备标识以及分配的8比特的节点新的设备标识。
3)采用发送设备标识更新消息的方式，该消息可以通过广播的方式发送或通过向被分配新的设备标识的节点分别单播的方式发送。广播发送时消息格式与前面的1)和2)类似，其中需指示新的设备标识的生效时间。单播发送时，只需要直接发送新的设备标识和生效时间即可，或者在此基础上增加原来的设 备标识以及需重新分配新的设备标识的节点所属域的域主节点的MAC地址，而不需要如广播消息中那样包括修改标识位、长度等其他标识，消息格式简单易行，可以降低实现的复杂度。
节点按照新的设备标识进行工作。媒介间桥接器按照新的设备标识进行资源调度，如将DM功能切换回排序更高的节点，也可以为分别对应不同域的媒介部分确定一个统一的设备标识并在MAP中体现。
综上所述，本发明通过分析两个域中的设备标识的冲突情况；在两个域中的设备标识冲突时，为每对设备标识冲突的节点中的一个节点分配新的设备标识；广播新的设备标识以及生效时间，以使节点按照新的设备标识进行工作，能够保证域无缝合并，不影响流业务传输，同时降低实现复杂度。
以上所述仅为本发明的实施例，并非因此限制本发明的专利范围，凡是利用本发明说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本发明的专利保护范围内。

Claims (34)

  1. 一种媒介间桥接器，其特征在于，所述媒介间桥接器包括：
    冲突分析模块，用于分析域名相同的两个域中的设备标识的冲突情况；
    冲突处理模块，与所述冲突分析模块连接，用于在所述两个域中的设备标识冲突时，为每对所述设备标识冲突的节点中的一个节点分配新的设备标识；
    广播模块，与所述冲突处理模块连接，广播所述新的设备标识以及生效时间，以使所述节点按照所述新的设备标识进行工作，其中所述生效时间为所述新的设备标识生效的时间点。
  2. 根据权利要求1所述的媒介间桥接器，其特征在于，所述媒介间桥接器还包括检测模块和发送模块，所述检测模块用于检测两个域的域名是否相同，所述发送模块用于在所述两个域的域名相同时向所述两个域中的域主节点发送节点切换指示消息，所述节点切换指示消息用于将所述两个域中的域主节点切换至所述媒介间桥接器并进行同步。
  3. 根据权利要求2所述的媒介间桥接器，其特征在于，所述切换指示信息中包括切换原因。
  4. 根据权利要求1-3任一项所述的媒介间桥接器，其特征在于，所述冲突分析模块还用于：通过切换之前的拓扑维护过程或通过节点切换过程获得所述两个域中的节点的设备标识。
  5. 根据权利要求4所述的媒介间桥接器，其特征在于，如果所述冲突分析模块判断到所述两个域中的设备标识没有冲突，则所述冲突处理模块通过发送有效媒体接入计划进行资源调度和管理；
    如果所述冲突分析模块判断到所述两个域中的设备标识有冲突，则所述冲突处理模块为每对所述设备标识冲突的节点中的一个节点分配所述新的设备标识。
  6. 根据权利要求1-5任一项所述的媒介间桥接器，其特征在于，所述冲突处理模块还用于：
    对比两个域中所述设备标识冲突的节点所建立的总流数，为所述总流数较小的域中的所述设备标识冲突的节点分配所述新的设备标识。
  7. 根据权利要求1-5任一项所述的媒介间桥接器，其特征在于，所述冲突 处理模块还用于：
    如果对比两个域中所述设备标识冲突的节点所建立的总流数相同，则随机为其中任一域中的所述设备标识冲突的节点分配新的设备标识。
  8. 根据权利要求1-5任一项所述的媒介间桥接器，其特征在于，所述冲突处理模块用于：
    对比两个域中设备标识冲突的节点建立的流所分配时隙的总长度，为所述总的时隙分配总长度较小的域中的设备标识冲突的节点分配所述新的设备标识。
  9. 根据权利要求1-5任一项所述的媒介间桥接器，其特征在于，所述冲突处理模块还用于：
    如果对比两个域中所述设备标识冲突的节点建立的流所分配的时隙的总长度相同，则随机为其中任一域中的所述设备标识冲突的节点分配新的设备标识。
  10. 根据权利要求1-5任一项所述的媒介间桥接器，其特征在于，所述冲突处理模块用于：对所述两个域中的每对设备标识冲突的节点进行对比，根据每对所述设备标识冲突的节点建立的流数，对建立的流数较少的节点更换设备标识。
  11. 根据权利要求1-10任一项所述的媒介间桥接器，其特征在于，所述广播模块用于：通过在广播的媒体接入计划帧中增加设备标识更新补充子域，或者通过发送设备标识更新消息的方式将所述新的设备标识下发至所述设备标识冲突的节点。
  12. 根据权利要求1所述的媒介间桥接器，其特征在于，所述媒介间桥接器还包括调度模块，用于按照所述新的设备标识进行调度和管理。
  13. 一种域合并方法，其特征在于，所述方法包括：
    分析域名相同的两个域中的设备标识的冲突情况；
    在所述两个域中的设备标识冲突时，为每对所述设备标识冲突的节点中的一个节点分配新的设备标识；
    广播所述新的设备标识以及生效时间，以使所述节点按照所述新的设备标识进行工作，其中所述生效时间为所述新的设备标识生效的时间点。
  14. 根据权利要求13所述的方法，其特征在于，在所述分析域名相同的两个域中的设备标识的冲突情况之前，
    检测两个域的域名是否相同，
    在所述两个域的域名相同时向所述两个域中的域主节点发送节点切换指示消息，所述节点切换指示消息用于将所述两个域中的域主节点切换至所述媒介间桥接器并进行同步。
  15. 根据权利要求14所述的方法，其特征在于，所述切换指示信息中包括切换原因。
  16. 根据权利要求13-15任一项所述的方法，其特征在于，所述分析域名相同的两个域中的设备标识的冲突情况包括：通过切换之前的拓扑维护过程或通过节点切换过程获得所述两个域中的节点的设备标识。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    如果所述两个域中的设备标识没有冲突，则通过发送有效媒体接入计划进行资源调度和管理；
    如果所述两个域中的设备标识有冲突，则为每对所述设备标识冲突的节点中的一个节点分配所述新的设备标识。
  18. 根据权利要求13-17任一项所述的方法，其特征在于，所述为每对所述设备标识冲突的节点中的一个节点分配所述新的设备标识，包括：
    对比两个域中所述设备标识冲突的节点所建立的总流数，为所述总流数较小的域中的所述设备标识冲突的节点分配所述新的设备标识。
  19. 根据权利要求13-17任一项所述的方法，其特征在于，所述为每对所述设备标识冲突的节点中的一个节点分配所述新的设备标识，还包括：
    如果对比两个域中所述设备标识冲突的节点所建立的总流数相同，则随机为其中任一域中的所述设备标识冲突的节点分配新的设备标识。
  20. 根据权利要求13-17任一项所述的方法，其特征在于，所述为每对所述设备标识冲突的节点中的一个节点分配所述新的设备标识，包括：
    对比两个域中设备标识冲突的节点建立的流所分配时隙的总长度，为所述总的时隙分配总长度较小的域中的设备标识冲突的节点分配所述新的设备标识。
  21. 根据权利要求13-17任一项所述的方法，其特征在于，所述为每对所述设备标识冲突的节点中的一个节点分配所述新的设备标识，还包括：
    如果对比两个域中所述设备标识冲突的节点建立的流数所述分配的时隙的总长度相同，则随机为其中任一域中的所述设备标识冲突的节点分配新的设备标识。
  22. 根据权利要求13-17任一项所述的方法，其特征在于，所述为每对所述设备标识冲突的节点中的一个节点分配所述新的设备标识，包括：对所述两个域中的每对设备标识冲突的节点进行对比，根据每对所述设备标识冲突的节点建立的流数，对建立的流数较少的节点更换设备标识。
  23. 根据权利要求13-22任一项所述的方法，其特征在于，所述广播所述新的设备标识以及生效时间，包括：通过在广播的媒体接入计划帧中增加设备标识更新补充子域，或者通过发送设备标识更新消息的方式将所述新的设备标识下发至所述设备标识冲突的节点。
  24. 根据权利要求13所述的方法，其特征在于，所述方法还包括：按照所述新的设备标识进行调度和管理。
  25. 一种节点，其特征在于，所述节点包括：
    接收模块，用于接收节点切换指示消息，其中所述节点所在的域与另一个域的域名相同；
    切换模块，与所述接收模块连接，用于根据所述节点切换指示消息将所述节点所在的域的域主节点切换至媒介间桥接器并进行同步以完成与所述另一个域的域合并。
  26. 根据权利要求25所述的节点，其特征在于，所述接收模块还用于：接收媒介间桥接器分配的新的设备标识；
    所述切换模块按照所述新的设备标识进行工作。
  27. 根据权利要求26所述的节点，其特征在于，
    如果所述节点所在域中设备标识冲突的节点所建立的总流数小于所述另一个域中设备标识冲突的节点所建立的总流数，或所述节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度小于所述另一个域中设备标识冲突的节点建立的流所分配时隙的总长度，
    则所述接收模块接收媒介间桥接器分配的新的设备标识。
  28. 根据权利要求26所述的节点，其特征在于，
    如果所述节点所在域中设备标识冲突的节点所建立的总流数与所述另一个域中设备标识冲突的节点所建立的总流数相同，或所述节点所在域中的设备标识冲突的节点建立的流所分配时隙的总长度与所述另一个域中的设备标识冲突的节点建立的流所分配时隙的总长度相同，
    则所述节点或所述另一个域中与所述节点设备标识冲突的节点的所述接收 模块接收所述新的设备标识。
  29. 根据权利要求25所述的节点，其特征在于，
    如果所述节点建立的流数小于所述另一个域中与所述节点设备标识冲突的节点建立的流数，则所述接收模块接收媒介间桥接器分配的新的设备标识。
  30. 一种域合并方法，其特征在于，所述方法包括：
    节点所在的域的域主节点接收节点切换指示消息，其中所述节点所在的域与另一个域的域名相同；
    所述节点所在的域的域主节点根据所述节点切换指示消息切换至媒介间桥接器并进行同步以完成与所述另一个域的域合并。
  31. 根据权利要求30所述的方法，其特征在于，所述方法还包括：所述节点接收所述媒介间桥接器分配的新的设备标识，并按照所述新的设备标识进行工作。
  32. 根据权利要求31所述的方法，其特征在于，所述节点所在域中设备标识冲突的节点所建立的总流数小于所述另一个域中设备标识冲突的节点所建立的总流数，或所述节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度小于所述另一个域中设备标识冲突的节点建立的流所分配时隙的总长度。
  33. 根据权利要求32所述的方法，其特征在于，所述节点接收新的设备标识，包括：
    对比所述节点所在域中设备标识冲突的节点所建立的总流数与所述另一个域中设备标识冲突的节点所建立的总流数相同，或所述节点所在域中设备标识冲突的节点建立的流所分配时隙的总长度与所述另一个域中设备标识冲突的节点建立的流所分配时隙的总长度相同，则所述节点或所述另一个域中与所述节点设备标识冲突的节点接收所述新的设备标识。
  34. 根据权利要求30所述的方法，其特征在于，所述节点接收新的设备标识，包括：
    所述节点建立的流数小于所述另一个域中与所述节点设备标识冲突的节点建立的流数。
PCT/CN2015/081063 2015-06-09 2015-06-09 域合并方法及媒介间桥接器、节点 WO2016197322A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2015/081063 WO2016197322A1 (zh) 2015-06-09 2015-06-09 域合并方法及媒介间桥接器、节点
CN201580024650.2A CN106464576A (zh) 2015-06-09 2015-06-09 域合并方法及媒介间桥接器、节点

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/081063 WO2016197322A1 (zh) 2015-06-09 2015-06-09 域合并方法及媒介间桥接器、节点

Publications (1)

Publication Number Publication Date
WO2016197322A1 true WO2016197322A1 (zh) 2016-12-15

Family

ID=57502891

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/081063 WO2016197322A1 (zh) 2015-06-09 2015-06-09 域合并方法及媒介间桥接器、节点

Country Status (2)

Country Link
CN (1) CN106464576A (zh)
WO (1) WO2016197322A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115941383B (zh) * 2022-11-28 2023-12-22 北京神经元网络技术有限公司 宽带现场总线多域交换系统网络域分配方法、装置和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101184087A (zh) * 2006-11-16 2008-05-21 华为技术有限公司 域变换的方法、设备及系统
EP1971039A2 (en) * 2007-03-15 2008-09-17 Infineon Technologies AG Multi-domain network with centralized management
CN101364871A (zh) * 2007-08-10 2009-02-11 华为技术有限公司 域管理器对用户设备进行域管理的方法、系统及装置
US20130051220A1 (en) * 2011-08-22 2013-02-28 Igor Ryshakov Method and Apparatus for Quick-Switch Fault Tolerant Backup Channel

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9408249B2 (en) * 2013-12-03 2016-08-02 Cisco Technology, Inc. Wireless mesh network including resilient backhaul links and WLAN traffic local switching

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101184087A (zh) * 2006-11-16 2008-05-21 华为技术有限公司 域变换的方法、设备及系统
EP1971039A2 (en) * 2007-03-15 2008-09-17 Infineon Technologies AG Multi-domain network with centralized management
CN101364871A (zh) * 2007-08-10 2009-02-11 华为技术有限公司 域管理器对用户设备进行域管理的方法、系统及装置
US20130051220A1 (en) * 2011-08-22 2013-02-28 Igor Ryshakov Method and Apparatus for Quick-Switch Fault Tolerant Backup Channel

Also Published As

Publication number Publication date
CN106464576A (zh) 2017-02-22

Similar Documents

Publication Publication Date Title
AU2013351670B2 (en) Business scheduling method and apparatus and convergence device
US8488603B2 (en) Method, apparatus, and system for implementing multicast services
CN110912835B (zh) 业务分流方法、装置及系统
US8310939B2 (en) Method, system, and device for configuring operation, administration and maintenance properties
CN102201999B (zh) 一种实现组播业务负荷分担的方法和系统
EP2654250A2 (en) Virtual local area network identity transformation method and apparatus
US8601138B2 (en) Method for processing request for network address/port translation in communication network
JP2005073230A (ja) ネットワーク用スイッチ装置及び経路管理サーバ、ネットワークインタフェース装置、及びそれらの制御方法、及び、経路管理サーバ用コンピュータプログラム及びコンピュータ可読記憶媒体
WO2012065531A1 (zh) 实现中继选择的方法及装置、系统
US20120102213A1 (en) Information providing method, home gateway, and home network system
CN113993118A (zh) 数据分流方法、装置、设备、功能实体及存储介质
US7327729B2 (en) System and method for communications with reservation of network resources, and terminal therefore
WO2019029485A1 (zh) 视频会议多点控制方法、装置、存储介质和计算机设备
CN103561388A (zh) 移动通信系统、控制站、基站、通信方法和程序
CN109495593A (zh) 地址分配方法及系统
CN108234270B (zh) 实现虚拟可扩展局域网多域并存的方法和系统
CN114095388B (zh) RTC / RTE设备与WiFi接入点间交换数据包分类标识符的方法以及无线接入点
CN109104309B (zh) Cdn网络的边缘服务器管理系统及方法
US20120300776A1 (en) Method for creating virtual link, communication network element, and ethernet network system
WO2016197322A1 (zh) 域合并方法及媒介间桥接器、节点
US20110136526A1 (en) Apparatus and method for allocating multicast connection indetifier in wireless access system
WO2012126435A2 (zh) 一种带宽资源的分配方法及装置
CN101150466B (zh) 组播广播业务的传输方法、系统及终端
CN107124307B (zh) 一种管理vlan切换方法及装置
WO2016091186A1 (zh) 一种防止逻辑交换机所占用资源发生冲突的方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15894592

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15894592

Country of ref document: EP

Kind code of ref document: A1