WO2015154458A1 - 一种节点逻辑id的分配装置、方法及通信系统 - Google Patents

一种节点逻辑id的分配装置、方法及通信系统 Download PDF

Info

Publication number
WO2015154458A1
WO2015154458A1 PCT/CN2014/091015 CN2014091015W WO2015154458A1 WO 2015154458 A1 WO2015154458 A1 WO 2015154458A1 CN 2014091015 W CN2014091015 W CN 2014091015W WO 2015154458 A1 WO2015154458 A1 WO 2015154458A1
Authority
WO
WIPO (PCT)
Prior art keywords
logical
node
switch
physical identifier
configuration request
Prior art date
Application number
PCT/CN2014/091015
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 华为技术有限公司
Publication of WO2015154458A1 publication Critical patent/WO2015154458A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a node logical ID allocation apparatus, method, and communication system.
  • a telecommunication system is often a logical whole composed of multiple devices. This logic provides services such as clusters as a whole.
  • This logic provides services such as clusters as a whole.
  • a plurality of switches, management devices, and nodes are often used. Each device needs to be assigned a logical ID. The user can manage and maintain the device based on the ID. The logical ID is planned and allocated by the user.
  • the number of nodes is usually much larger than the number of switches.
  • the disadvantage of this scheme is that due to the large number of nodes, for example, dozens or even hundreds, the efficiency of the logic ID being set to the device at the near end is too low, and the requirements for the near-end station engineers are very high. In addition, it is also required that the near end must be portable (currently the base station is portable free).
  • Solution 2 Automatic allocation based on physical identification: After the device is installed on the site, manually copy the physical ID (MAC address or serial number) of all devices, notify the background, and complete the binding of the logical ID and the physical ID in the background. In the system, thus the automatic assignment of logical IDs is completed.
  • physical ID MAC address or serial number
  • the disadvantage of this scheme is that the near-end engineer needs to transcribe the MAC or serial number of all devices, and the near-end needs to record the physical installation location corresponding to the device. Due to the large number of nodes, the workload is still large, and in addition, if the corresponding error occurs, This problem is difficult to locate.
  • Solution 3 Automatic allocation based on physical topology: The user completes the installation on site, powers on, and the system completes the allocation of the logical ID according to the physical topology of the Node.
  • scheme 3 does not require a near-end portable setup, and does not require near-end transcription of MAC or The serial number simplifies the near-end operation.
  • the interconnect topology of the switch is complex. There may be multiple topologies between any two nodes. In addition, the topology may change frequently. The requirements of the entire network are too high, and can only be used in a stable and simple networking environment. The actual networking is complex and variable, and the solution has difficulties in practical applications.
  • the technical problem to be solved by the embodiments of the present invention is to provide a device, a method, and a communication system for allocating a logical ID of a node, and implementing efficient allocation of node logical IDs.
  • An embodiment of the present invention provides a device for allocating a node logical ID, including:
  • a receiving unit configured to receive a configuration request sent by the node;
  • the configuration request carries a physical identifier of a switch connected to the node, and a port number of the switch connecting the node;
  • a parsing unit configured to parse the configuration request, and obtain the physical identifier and a port number carried in the configuration request;
  • a first acquiring unit configured to acquire a logical ID of the switch according to the physical identifier
  • an allocating unit configured to allocate a logical ID of the node according to a predetermined rule according to the logical ID of the switch and the port number.
  • the embodiment of the present invention further provides a method for allocating a node logical ID, including:
  • the configuration request carries a physical identifier of a switch connected to the node, and a port number of the switch connecting the node;
  • the logical ID of the node is allocated according to a predetermined rule according to the logical ID of the switch and the port number.
  • an embodiment of the present invention further provides a communication system, including a node, a switch, and a node logical ID allocation device as described above.
  • the device, the method and the communication system for assigning the logical ID of the node provided in the embodiment of the present invention provide an efficient allocation scheme of the node logical ID, and obtain the physical identifier and port of the switch connected to the node by using the configuration request initiated by the node. Number, obtain the logical ID of the switch according to the physical ID of the switch, and then assign the logical ID of the node according to the logical ID and port number of the switch.
  • the matching scheme overcomes the drawbacks of the existing allocation scheme that need to manually set the node logical ID or transcribe the physical identifier of a large number of nodes, greatly simplifying the on-site open operation and reducing the probability of error; and additionally, the topology of the switch connected to the node is determined. Therefore, the allocation scheme can be applied to the allocation of node logical IDs in telecommunication systems with complex topologies.
  • Figure 1 is a schematic diagram of a typical architecture of a Cloud BB system
  • FIG. 2 is a schematic structural diagram of a node logical ID allocation apparatus according to Embodiment 1 of the present invention.
  • FIG. 3 is a first schematic diagram of a flow of a method for allocating a node logical ID according to Embodiment 2 of the present invention
  • FIG. 4 is a second schematic diagram of a flow of a method for allocating a node logical ID according to Embodiment 2 of the present invention.
  • a device, a method, and a communication system for allocating a node logic ID are provided, which are respectively described in detail below.
  • Cloud BB Cloud Base Station
  • Cloud BB Cloud Base Station
  • the value of Cloud BB lies in the business collaboration between nodes. This requires a large amount of business data interaction between nodes, due to the large amount of business data ( Dozens of G), a set of switches need to be interconnected to provide higher switching bandwidth.
  • Figure 1 The typical scenario of the current Cloud BB telecom equipment interconnection network is shown in Figure 1, including:
  • a converged switch (Switch) for interconnecting access switches generally configured as a CLOS network (a theoretically non-blocking multi-level interconnected network, proposed by Charles Clos in 1953);
  • An access switch (Switch) is used to access the telecommunication device
  • Cloud BB management unit (Mgr for short), connected to the access switch;
  • An access node which represents a telecommunication device, connects to the network through an access switch.
  • the number of access nodes generally far exceeds the number of access switches, and due to the complex interconnection topology of the switch in the Cloud BB scenario, the aggregation switch forms a CLOS network, and there are many between any two Nodes.
  • the bandwidth between the access switch and the aggregation switch may be configured as a trunk. The bandwidth of the trunk can be adjusted as required. As a result, the topology may change. If the switch is configured as a master/slave relationship, the complexity of the topology is further increased. The allocation scheme of the node logical ID in the prior art is difficult to apply to the Cloud BB system.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • FIG. 2 is a schematic structural diagram of a node logical ID allocation apparatus according to an embodiment of the present invention. As shown in FIG. 2, the node logical ID allocation apparatus 200 includes:
  • the receiving unit 201 is configured to receive a configuration request sent by the node, where the configuration request carries a physical identifier of a switch connected to the node, and a port number of the switch connecting the node;
  • the parsing unit 202 is configured to parse the configuration request, and obtain the physical identifier and the port number carried in the configuration request.
  • the first obtaining unit 203 is configured to acquire a logical ID (logical identifier) of the switch according to the foregoing physical identifier;
  • the allocating unit 204 is configured to allocate the logical ID of the node according to a predetermined rule according to the logical ID of the switch and the port number.
  • the device for assigning the logical ID of the node utilizes the configuration request initiated by the node to obtain The physical ID and port number of the switch connected to the node, obtain the logical ID of the switch according to the physical ID of the switch, and then allocate the logical ID of the node according to the logical ID and port number of the switch.
  • the distribution device overcomes the existing allocation. In the solution, the disadvantages of manually setting the node logical ID or copying the physical identifier of a large number of nodes are greatly simplified, which greatly simplifies the on-site open operation and reduces the probability of error. In addition, since the topology of the node and the switch to which it is connected is determined, the distribution device can be applied.
  • the allocation of node logical IDs in telecommunication systems with complex topologies is applicable, for example, to the allocation of node logical IDs in the Cloud BB system.
  • the above configuration request may be preferably: a DHCP (Dynamic Host Configuration Protocol) request; of course, the configuration request may also be a BOOTP (Bootstrap Protocol) request, or other suitable type of configuration request. There are no specific restrictions here.
  • dispensing device 200 can further include:
  • a second acquiring unit (not shown) is configured to obtain a correspondence between a physical identifier of the switch and a logical ID thereof.
  • the physical identifier of the switch may be transcribed by the user when the switch is installed, and the physical of the switch
  • the correspondence between the identifier and the logical ID may also be manually set by the user and recorded in the distribution device.
  • the correspondence between the physical identifier of the switch and its logical ID may also be obtained by other means, for example, by using an external interface to be imported into the distribution device. of.
  • the first acquiring unit may acquire the logical ID of the switch according to the physical identifier of the switch and the correspondence between the physical identifier and its logical ID.
  • the node can obtain the physical address (Management Address) and the port number (PortID) of the switch connected to the switch before the configuration request is initiated.
  • the node can receive the LLDP (Link Layer Discovery Protocol) link sent by the switch.
  • the layer discovery protocol is configured to obtain the port number and the physical identification information of the switch carried in the LLDP frame by parsing the LLDP frame.
  • the node can obtain the physical identifier and port number of the switch connected to it by other means, and does not specifically limit the obtaining mode.
  • the physical identifier of the switch may be the MAC address (physical address) of the switch, or a serial number, and the like.
  • the foregoing predetermined rule may include: the logical ID of the above switch and the above port The numbers are combined to form the logical ID of the above node.
  • the system includes two access switches, namely Switch1 and Switch2, and each access switch has two nodes connected to it, respectively using port 0 and port 1.
  • the allocation unit can each node according to the above topology relationship.
  • the logical ID is assigned.
  • the logical ID of the node connected to Switch1 through port 0 is assigned as Node10
  • the logical ID of the node connected to Switch1 through port 1 is assigned as Node11
  • the logical ID of the node connected to Switch2 through port 0 is assigned as Node 20 assigns the logical ID of the node connected to Switch 2 through port 1 to Node 21. That is, the logical ID of the switch is combined with the port number to form the logical ID of the node.
  • the predetermined rule may further include: allocating the logical ID of the node according to the logical ID of the switch in the order of small to large and the port number being small to large.
  • the system includes two access switches, namely Switch1 and Switch2, and each access switch has two nodes connected to it, respectively using port 0 and port 1.
  • the allocation unit can each node according to the above topology relationship.
  • the logical ID is assigned. For example, the logical ID of the node connected to Switch1 through port 0 is assigned as Node1, the logical ID of the node connected to Switch1 through port 1 is assigned as Node2, and the logical ID of the node connected to Switch2 through port 0 is assigned as Node3 assigns the logical ID of the node connected to Switch2 through port 1 to Node4.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • FIG. 3 is a schematic flowchart diagram of a method for allocating a node logic ID according to an embodiment of the present invention. As shown in FIG. 3, the method may include:
  • the configuration request sent by the receiving node where the configuration request carries a physical identifier of a switch connected to the node, and a port number of the switch connecting the node.
  • the method for allocating the logical ID of the node obtains the physical identifier and the port number of the switch connected to the node by using the configuration request initiated by the node, obtains the logical ID of the switch according to the physical identifier of the switch, and then according to the logical ID of the switch.
  • the port number allocates the logical ID of the node.
  • the allocation method overcomes the disadvantages of manually setting the node logical ID or copying the physical identifier of a large number of nodes in the existing allocation scheme, greatly simplifying the on-site open operation and reducing the probability of error;
  • the topology of the node and the switch to which it is connected is determined, so the allocation method can be applied to the allocation of node logical IDs in a telecommunications system with complex topology, for example, applicable to the allocation of node logical IDs in the Cloud BB system.
  • the above configuration request may be preferably: a DHCP (Dynamic Host Configuration Protocol) request; of course, the configuration request may also be a BOOTP (Bootstrap Protocol) request, or other suitable type of configuration request. There are no specific restrictions here.
  • the method may further include:
  • the physical identifier of the switch may be transcribed by the user when the switch is installed.
  • the correspondence between the physical identifier of the switch and its logical ID may also be manually set by the user and recorded in the distribution device.
  • the physical identifier of the switch may also be obtained by other means, for example, through an external interface.
  • the workload of copying the physical identifier of the switch and setting its correspondence with the logical ID is much smaller than the manual setting of the logical ID of the node or the physical identification of the transcribed node in the prior art. the amount.
  • the foregoing 303 may specifically include: determining, according to a physical identifier of the switch, a correspondence between a physical identifier of the switch, and a logical ID, a logical ID of the switch to which the node is connected.
  • the physical identifier of the switch has a one-to-one correspondence with the logical ID, the physical ID of the switch is obtained, and the logical ID of the switch can be obtained according to the corresponding relationship.
  • the node can obtain the physical address (Management Address) and the port number (PortID) of the switch connected to the switch before the DHCP request is initiated.
  • the node can receive the LLDP (Link Layer Discovery Protocol) link sent by the switch. Layer discovery protocol) frame,
  • the physical identification information of the switch carried in the port number and the LLDP frame is obtained by parsing the LLDP frame.
  • the node can obtain the physical identifier and port number of the switch connected to it by other means, and does not specifically limit the obtaining mode.
  • the predetermined rule may include combining the logical ID of the switch and the port number to form a logical ID of the node.
  • the system includes two access switches, namely Switch1 and Switch2, and each access switch has two nodes connected to it, respectively using port 0 and port 1.
  • the allocation unit can each node according to the above topology relationship.
  • the logical ID is assigned.
  • the logical ID of the node connected to Switch1 through port 0 is assigned as Node10
  • the logical ID of the node connected to Switch1 through port 1 is assigned as Node11
  • the logical ID of the node connected to Switch2 through port 0 is assigned as Node 20 assigns the logical ID of the node connected to Switch 2 through port 1 to Node 21. That is, the logical ID of the switch is combined with the port number to form the logical ID of the node.
  • the predetermined rule may include: allocating the logical ID of the node according to the logical ID of the switch in the order of small to large and the port number being small to large.
  • the system includes two access switches, namely Switch1 and Switch2, and each access switch has two nodes connected to it, respectively using port 0 and port 1.
  • the allocation unit can each node according to the above topology relationship.
  • the logical ID is assigned. For example, the logical ID of the node connected to Switch1 through port 0 is assigned as Node1, the logical ID of the node connected to Switch1 through port 1 is assigned as Node2, and the logical ID of the node connected to Switch2 through port 0 is assigned as Node3 assigns the logical ID of the node connected to Switch2 through port 1 to Node4.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the embodiment of the present invention further provides a communication system, including: a node, a switch, and a distribution device of the node logical ID as described in Embodiment 1.
  • the system may be a Cloud BB system, and Mgr in the Cloud BB system corresponds to a distribution device of a node logical ID, and a logical ID is assigned to each node connected to the switch.
  • the program may be stored in a computer readable storage medium, and the storage medium may include: Flash disk, Read-Only Memory (ROM), Random Access Memory (RAM), disk or optical disk.
  • the device, the method and the communication system for allocating the logical ID of the node provided by the embodiment of the present invention are described in detail.
  • the principle and the embodiment of the present invention are described in the following.
  • the description of the above embodiment is only used for the description.

Abstract

本发明实施例涉及通信技术领域，公开了一种节点逻辑ID的分配装置、方法和通信系统。其中，该装置包括：接收单元，用于接收节点发送的配置请求；所述配置请求中携带与所述节点连接的交换机的物理标识以及所述交换机连接所述节点的端口号；解析单元，用于解析所述配置请求，获取所述配置请求中携带的所述物理标识及端口号；第一获取单元，用于根据所述物理标识获取所述交换机的逻辑ID；分配单元，用于根据所述交换机的逻辑ID和所述端口号，按照预定规则分配所述节点的逻辑ID。实施本发明实施例，可以实现高效的节点逻辑ID的分配。

Description

一种节点逻辑ID的分配装置、方法及通信系统
本申请要求于2014年04月09日提交中国专利局、申请号为201410140323.0、发明名称为“一种节点逻辑ID的分配装置、方法及通信系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，具体涉及一种节点逻辑ID的分配装置、方法及通信系统。
背景技术
电信系统往往是多个设备组成的一个逻辑整体，这个逻辑整体对外统一提供服务，比如集群等。电信系统中往往由多个交换机、管理设备、节点等设备组成，每一个设备都需要分配一个逻辑ID，用户可以基于该ID对设备进行管理与维护，逻辑ID是用户规划并分配的。一般的，由于一个接入交换机可连接多个节点，因此在电信系统中，节点数量通常远远大于交换机的数量。
现有技术中，存在以下几种逻辑ID的分配方案：
方案1、近端手动分配：近端通过便携登录到设备，用户手动设置节点的逻辑ID。
这种方案的缺点在于：由于节点数量众多，例如可达到几十个甚至上百个，近端一个一个登录到设备设置逻辑ID效率太低，对近端开站工程师要求很高。另外，还要求近端必须带便携(目前基站是免便携开站的)。
方案2、基于物理标识的自动分配：用户现场安装完设备后，手工抄录所有设备的物理标识(MAC地址或者序列号)，通知后台，后台完成逻辑ID与物理标识的绑定后，下发到系统中，从而完成逻辑ID的自动分配。
这种方案的缺点在于：需要近端工程师抄录所有设备的MAC或者序列号，并且近端需要记录该设备对应的物理安装位置，由于节点数量众多，工作量还是很大，另外，一旦对应出错，该问题难以定位。
方案3、基于物理拓扑的自动分配：用户现场完成安装，上电，系统根据Node的物理拓扑，完成逻辑ID的分配。
方案3相比前两种方案，无需近端带便携设置，无需近端抄录MAC或者 序列号，简化了近端操作，但仍然存在如下缺点：在一些复杂场景下，交换机的互联拓扑比较复杂，任意两个Node之间可能存在多条拓扑，另外，拓扑还可能经常发生变化。方案3对整个组网的要求过高，仅可使用于稳定、简单的组网环境，而实际的组网是复杂多变的，该方案在实际应用中存在困难。
发明内容
本发明实施例所要解决的技术问题是提供一种节点逻辑ID的分配装置、方法及通信系统，实现高效的节点逻辑ID的分配。
本发明实施例提供一种节点逻辑ID的分配装置，包括：
接收单元，用于接收节点发送的配置请求；所述配置请求中携带与所述节点连接的交换机的物理标识以及所述交换机连接所述节点的端口号；
解析单元，用于解析所述配置请求，获取所述配置请求中携带的所述物理标识及端口号；
第一获取单元，用于根据所述物理标识获取所述交换机的逻辑ID；
分配单元，用于根据所述交换机的逻辑ID和所述端口号，按照预定规则分配所述节点的逻辑ID。
相应的，本发明实施例还提供一种节点逻辑ID的分配方法，包括：
接收节点发送的配置请求；所述配置请求中携带与所述节点连接的交换机的物理标识以及所述交换机连接所述节点的端口号；
解析所述配置请求，获取所述配置请求中携带的所述物理标识及端口号；
根据所述物理标识获取所述交换机的逻辑ID；
根据所述交换机的逻辑ID和所述端口号，按照预定规则分配所述节点的逻辑ID。
相应的，本发明实施例还提供一种通信系统，包括节点、交换机以及如前所述的节点逻辑ID的分配装置。
本发明实施例中提供的节点的逻辑ID的分配装置、方法和通信系统，提供了一种高效的节点逻辑ID的分配方案，利用节点发起的配置请求获取与节点连接的交换机的物理标识和端口号，根据交换机的物理标识获取到交换机的逻辑ID，再根据交换机的逻辑ID和端口号对节点的逻辑ID进行分配，该分 配方案克服了现有的分配方案中需要手动设置节点逻辑ID或抄录大量节点的物理标识的弊端，大大简化现场开站操作，降低错误概率；另外由于节点与其所连接的交换机的拓扑结构是确定的，因此该分配方案可适用于对拓扑结构复杂的电信系统中节点逻辑ID的分配。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是Cloud BB系统的典型架构示意图；
图2是本发明实施例一提供的节点逻辑ID的分配装置的结构示意图；
图3是本发明实施例二提供的节点逻辑ID的分配方法的流程第一示意图；
图4是本发明实施例二提供的节点逻辑ID的分配方法的流程第二示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明实施例中提供了一种节点逻辑ID的分配装置、方法及通信系统，以下分别进行详细说明。
本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本发明的实施例例如能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
Cloud BB(云基站)是目前业界比较新的一种LTE领域的通信系统，Cloud BB的价值在于节点间的业务协同，这就需要节点间进行大量的业务数据交互，由于业务数据量很大(几十个G)，节点间需要一组交换机进行互联从而提供更高的交换带宽，当前Cloud BB电信设备互联组网典型场景如图1所示，包括：
汇聚交换机(Switch)，用于互联接入交换机，一般配置成CLOS网络(一种理论上的严格无阻塞的多级互连网络，由Charles Clos于1953年提出)；
接入交换机(Switch)用于接入电信设备；
Cloud BB管理单元(简称Mgr)，与接入交换机连接；
接入节点(Node)，可代表一个电信设备，通过接入交换机连接网络。
在Cloud BB系统中，接入节点的数量一般远远超过接入交换机的数量，并且由于Cloud BB场景下，交换机的互联拓扑比较复杂，汇聚交换机形成一个CLOS网络，任意两个Node之间存在多条拓扑，另外，接入交换机与汇聚交换机之间可能配置成TRUNK(主干)，TRUNK的带宽可以根据需要进行调整，由此导致拓扑可能发生变化。如果交换机配置成主备关系，进一步增加了拓扑的复杂度。现有技术中的节点逻辑ID的分配方案均难以应用到Cloud BB系统中。
实施例一：
请参考图2，图2是本发明实施例提供的一种节点逻辑ID的分配装置的结构示意图；如图2所示，该节点逻辑ID的分配装置200包括：
接收单元201，用于接收节点发送的配置请求；上述配置请求中携带与上述节点连接的交换机的物理标识以及上述交换机连接上述节点的端口号；
解析单元202，用于解析上述配置请求，获取上述配置请求中携带的上述物理标识及端口号；
第一获取单元203，用于根据上述物理标识获取上述交换机的逻辑ID(逻辑标识)；
分配单元204，用于根据上述交换机的逻辑ID和上述端口号，按照预定规则分配上述节点的逻辑ID。
本实施例提供的节点的逻辑ID的分配装置利用节点发起的配置请求获取 与节点连接的交换机的物理标识和端口号，根据交换机的物理标识获取到交换机的逻辑ID，再根据交换机的逻辑ID和端口号对节点的逻辑ID进行分配，该分配装置克服了现有的分配方案中需要手动设置节点逻辑ID或抄录大量节点的物理标识的弊端，大大简化现场开站操作，降低错误概率；另外由于节点与其所连接的交换机的拓扑结构是确定的，因此该分配装置可适用于对拓扑结构复杂的电信系统中节点逻辑ID的分配，例如可适用于Cloud BB系统中节点逻辑ID的分配。
举例来说，上述配置请求可以优选为：DHCP(Dynamic Host Configuration Protocol，动态主机配置协议)请求；当然上述配置请求还可以为BOOTP(Bootstrap Protocol，引导程序协议)请求，或者其它合适类型的配置请求，在此不作具体的限制。
进一步地，该分配装置200还可包括：
第二获取单元(图中未示出)，用于获取上述交换机的物理标识与其逻辑ID的对应关系；举例来说，交换机的物理标识可以是由用户在安装交换机时抄录下来的，交换机的物理标识与其逻辑ID的对应关系也可以是用户手动设置并记录在分配装置中的，当然，交换机的物理标识与其逻辑ID的对应关系也可以是通过其它方式获取的，例如通过外接接口导入分配装置中的。
具体来说，第一获取单元可以根据交换机的物理标识、以及物理标识与其逻辑ID的对应关系来获取交换机的逻辑ID。
本实施例中，节点可在启动配置请求之前获取与其连接的交换机的物理标识(Management Address)和端口号(PortID)，举例来说，节点可以接收交换机发送的LLDP(Link Layer Discovery Protocol，链路层发现协议)帧，通过解析LLDP帧，获取端口号和LLDP帧携带的交换机的物理标识信息。当然节点还可以通过其他方式获取与其连接的交换机的物理标识和端口号，在此不对获取方式做具体的限制。
举例来说，交换机的物理标识可以是交换机的MAC地址(物理地址)，或者序列号等。
举例来说，上述预定规则可以包括：将上述交换机的逻辑ID和上述端口 号组合以形成上述节点的逻辑ID。
例如，系统中包括2个接入交换机，分别为Switch1和Switch2，每个接入交换机下接入了2个节点，分别使用交换机的端口0和端口1，分配单元可以根据上述拓扑关系对各个节点的逻辑ID进行分配，例如将通过端口0连接Switch1的节点的逻辑ID分配为Node10，将通过端口1连接Switch1的节点的逻辑ID分配为Node11，将通过端口0连接Switch2的节点的逻辑ID分配为Node20，将通过端口1连接Switch2的节点的逻辑ID分配为Node21，即是将交换机的逻辑ID与端口号组合起来形成节点的逻辑ID。
举例来说，上述预定规则还可以包括：按照上述交换机的逻辑ID由小到大的顺序以及上述端口号由小到大的顺序分配上述节点的逻辑ID。
例如，系统中包括2个接入交换机，分别为Switch1和Switch2，每个接入交换机下接入了2个节点，分别使用交换机的端口0和端口1，分配单元可以根据上述拓扑关系对各个节点的逻辑ID进行分配，例如将通过端口0连接Switch1的节点的逻辑ID分配为Node1，将通过端口1连接Switch1的节点的逻辑ID分配为Node2，将通过端口0连接Switch2的节点的逻辑ID分配为Node3，将通过端口1连接Switch2的节点的逻辑ID分配为Node4。
当然，上述的预定规则不限于此，本领域技术人员还可以设置其它合适的分配节点逻辑ID的方案，在此不作具体的限制。
实施例二：
请参考图3，图3是本发明实施例提供的一种节点逻辑ID的分配方法的流程示意图。如图3所示，该方法可以包括：
301、接收节点发送的配置请求；上述配置请求中携带与上述节点连接的交换机的物理标识以及上述交换机连接上述节点的端口号；
302、解析上述配置请求，获取上述配置请求中携带的上述物理标识及端口号；
303、根据上述物理标识获取上述交换机的逻辑ID；
304、根据上述交换机的逻辑ID和上述端口号，按照预定规则分配上述节点的逻辑ID。
本实施例提供的节点的逻辑ID的分配方法利用节点发起的配置请求获取与节点连接的交换机的物理标识和端口号，根据交换机的物理标识获取到交换机的逻辑ID，再根据交换机的逻辑ID和端口号对节点的逻辑ID进行分配，该分配方法克服了现有的分配方案中需要手动设置节点逻辑ID或抄录大量节点的物理标识的弊端，大大简化现场开站操作，降低错误概率；另外由于节点与其所连接的交换机的拓扑结构是确定的，因此该分配方法可适用于对拓扑结构复杂的电信系统中节点逻辑ID的分配，例如可适用于Cloud BB系统中节点逻辑ID的分配。
举例来说，上述配置请求可以优选为：DHCP(Dynamic Host Configuration Protocol，动态主机配置协议)请求；当然上述配置请求还可以为BOOTP(Bootstrap Protocol，引导程序协议)请求，或者其它合适类型的配置请求，在此不作具体的限制。
如图4所示，在上述301之前，该方法还可包括：
401、获取上述交换机的物理标识和逻辑ID的对应关系；
举例来说，交换机的物理标识可以是由用户在安装交换机时抄录下来的，交换机的物理标识与其逻辑ID的对应关系也可以是用户手动设置并记录在分配装置中的，当然，交换机的物理标识与其逻辑ID的对应关系也可以是通过其它方式获取的，例如通过外接接口导入的。
由于交换机的数量要远远小于节点的数量，因此抄录交换机的物理标识并设置其与逻辑ID的对应关系的工作量要远远小于现有技术中手动设置节点逻辑ID或者抄录节点物理标识的工作量。
相应的，上述303可具体包括：根据上述交换机的物理标识、上述交换机的物理标识和逻辑ID的对应关系确定上述节点所连接的交换机的逻辑ID。
由于交换机的物理标识与其逻辑ID存在一一对应关系，在获取了交换机的物理标识，可根据该对应关系得到交换机的逻辑ID。
本实施例中，节点可在启动DHCP请求之前获取与其连接的交换机的物理标识(Management Address)和端口号(PortID)，举例来说，节点可以接收交换机发送的LLDP(Link Layer Discovery Protocol，链路层发现协议)帧， 通过解析LLDP帧，获取端口号和LLDP帧携带的交换机的物理标识信息。当然节点还可以通过其他方式获取与其连接的交换机的物理标识和端口号，在此不对获取方式做具体的限制。
举例来说，上述预定规则可以包括：将上述交换机的逻辑ID和上述端口号组合以形成上述节点的逻辑ID。
例如，系统中包括2个接入交换机，分别为Switch1和Switch2，每个接入交换机下接入了2个节点，分别使用交换机的端口0和端口1，分配单元可以根据上述拓扑关系对各个节点的逻辑ID进行分配，例如将通过端口0连接Switch1的节点的逻辑ID分配为Node10，将通过端口1连接Switch1的节点的逻辑ID分配为Node11，将通过端口0连接Switch2的节点的逻辑ID分配为Node20，将通过端口1连接Switch2的节点的逻辑ID分配为Node21，即是将交换机的逻辑ID与端口号组合起来形成节点的逻辑ID。
举例来说，上述预定规则也可以包括：按照上述交换机的逻辑ID由小到大的顺序以及上述端口号由小到大的顺序分配上述节点的逻辑ID。
例如，系统中包括2个接入交换机，分别为Switch1和Switch2，每个接入交换机下接入了2个节点，分别使用交换机的端口0和端口1，分配单元可以根据上述拓扑关系对各个节点的逻辑ID进行分配，例如将通过端口0连接Switch1的节点的逻辑ID分配为Node1，将通过端口1连接Switch1的节点的逻辑ID分配为Node2，将通过端口0连接Switch2的节点的逻辑ID分配为Node3，将通过端口1连接Switch2的节点的逻辑ID分配为Node4。
当然，上述的预定规则不限于此，本领域技术人员还可以设置其它合适的分配节点逻辑ID的方案，在此不作具体的限制。
实施例三：
本发明实施例还提供一种通信系统，该通信系统包括：节点、交换机以及如实施例一上述的节点逻辑ID的分配装置。
该系统可以是Cloud BB系统，Cloud BB系统中的Mgr对应于节点逻辑ID的分配装置，为连接交换机的各个节点分配逻辑ID。
需要说明的是，以上各实施例均属于同一发明构思，各实施例的描述各有 侧重，在个别实施例中描述未详尽之处，可参考其他实施例中的描述。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读存储介质中，存储介质可以包括：闪存盘、只读存储器(Read-Only Memory，ROM)、随机存取器(Random Access Memory，RAM)、磁盘或光盘等。
以上对本发明实施例所提供的节点逻辑ID的分配装置、方法和通信系统进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本发明的限制。

Claims (11)

  1. 一种节点逻辑ID的分配装置，其特征在于，包括：
    接收单元，用于接收节点发送的配置请求；所述配置请求中携带与所述节点连接的交换机的物理标识以及所述交换机连接所述节点的端口号；
    解析单元，用于解析所述配置请求，获取所述配置请求中携带的所述物理标识及端口号；
    第一获取单元，用于根据所述物理标识获取所述交换机的逻辑ID；
    分配单元，用于根据所述交换机的逻辑ID和所述端口号，按照预定规则分配所述节点的逻辑ID。
  2. 根据权利要求1所述的装置，其特征在于，所述设备还包括：
    第二获取单元，用于获取所述交换机的物理标识与其逻辑ID的对应关系；
    所述第一获取单元具体用于根据所述交换机的物理标识、所述交换机的物理标识与其逻辑ID的对应关系来获取所述交换机的逻辑ID。
  3. 根据权利要求1所述的装置，其特征在于，所述配置请求中携带的所述物理标识和端口号是由所述节点解析所述交换机发送的链路层发现协议LLDP帧获得的。
  4. 根据权利要求1-3任一项所述的装置，其特征在于，所述预定规则包括：
    将所述交换机的逻辑ID和所述端口号组合以形成所述节点的逻辑ID。
  5. 根据权利要求1-3任一项所述的装置，其特征在于，所述预定规则包括：
    按照所述交换机的逻辑ID由小到大的顺序以及所述端口号由小到大的顺序分配所述节点的逻辑ID。
  6. 一种节点逻辑ID的分配方法，其特征在于，包括：
    接收节点发送的配置请求；所述配置请求中携带与所述节点连接的交换机的物理标识以及所述交换机连接所述节点的端口号；
    解析所述配置请求，获取所述配置请求中携带的所述物理标识及端口号；
    根据所述物理标识获取所述交换机的逻辑ID；
    根据所述交换机的逻辑ID和所述端口号，按照预定规则分配所述节点的逻辑ID。
  7. 根据权利要求6所述的方法，其特征在于，在所述接收节点发送的配置请求之前，所述方法还包括：
    获取所述交换机的物理标识和逻辑ID的对应关系；
    所述根据所述物理标识获取所述交换机的逻辑ID包括：
    根据所述交换机的物理标识、所述交换机的物理标识和逻辑ID的对应关系来获取所述节点所连接的交换机的逻辑ID。
  8. 根据权利要求1所述的方法，其特征在于，所述配置请求中携带的所述物理标识和端口号是由所述节点解析所述交换机发送的链路层发现协议LLDP帧获得的。
  9. 根据权利要求6-8任一项所述的方法，其特征在于，所述预定规则包括：
    将所述交换机的逻辑ID和所述端口号组合以形成所述节点的逻辑ID。
  10. 根据权利要求6-8任一项所述的方法，其特征在于，所述预定规则包括：
    按照所述交换机的逻辑ID由小到大的顺序以及所述端口号由小到大的顺序分配所述节点的逻辑ID。
  11. 一种通信系统，其特征在于，包括节点、交换机以及如权利要求1-5任一项所述的节点逻辑ID的分配装置。
PCT/CN2014/091015 2014-04-09 2014-11-13 一种节点逻辑id的分配装置、方法及通信系统 WO2015154458A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410140323.0 2014-04-09
CN201410140323.0A CN103945015A (zh) 2014-04-09 2014-04-09 一种节点逻辑id的分配装置、方法及通信系统

Publications (1)

Publication Number Publication Date
WO2015154458A1 true WO2015154458A1 (zh) 2015-10-15

Family

ID=51192495

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/091015 WO2015154458A1 (zh) 2014-04-09 2014-11-13 一种节点逻辑id的分配装置、方法及通信系统

Country Status (2)

Country Link
CN (1) CN103945015A (zh)
WO (1) WO2015154458A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112601141A (zh) * 2020-12-29 2021-04-02 广东省广播电视网络股份有限公司 一种epon/gpon局端设备网络工程割接方法

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103945015A (zh) * 2014-04-09 2014-07-23 上海华为技术有限公司 一种节点逻辑id的分配装置、方法及通信系统
CN104219337B (zh) * 2014-09-11 2017-08-11 新华三技术有限公司 应用于sdn中的ip地址分配方法和设备
CN109286527B (zh) * 2018-10-10 2022-02-22 广东信通通信有限公司 关联交换机逻辑和实物图端口的方法及网管系统
CN113836055B (zh) * 2021-09-24 2023-10-17 展讯通信(天津)有限公司 一种设备节点配置方法、装置和电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103476023A (zh) * 2013-09-11 2013-12-25 福建星网锐捷网络有限公司 接入点设备的配置方法、接入控制器及通信系统
CN103535068A (zh) * 2013-05-29 2014-01-22 华为技术有限公司 数据传输的方法、装置、设备及基站
CN103945015A (zh) * 2014-04-09 2014-07-23 上海华为技术有限公司 一种节点逻辑id的分配装置、方法及通信系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8798056B2 (en) * 2007-09-24 2014-08-05 Intel Corporation Method and system for virtual port communications
CN101227404B (zh) * 2008-02-05 2010-12-08 中兴通讯股份有限公司 一种对无网管以太网交换机进行带内管理的方法及装置
CN101272292A (zh) * 2008-05-14 2008-09-24 杭州华三通信技术有限公司 一种在流量监控中识别用户身份的方法及设备
CN101917305B (zh) * 2010-08-20 2012-01-11 迈普通信技术股份有限公司 自动化测试中拓扑自动检查方法以及自动化测试系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103535068A (zh) * 2013-05-29 2014-01-22 华为技术有限公司 数据传输的方法、装置、设备及基站
CN103476023A (zh) * 2013-09-11 2013-12-25 福建星网锐捷网络有限公司 接入点设备的配置方法、接入控制器及通信系统
CN103945015A (zh) * 2014-04-09 2014-07-23 上海华为技术有限公司 一种节点逻辑id的分配装置、方法及通信系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112601141A (zh) * 2020-12-29 2021-04-02 广东省广播电视网络股份有限公司 一种epon/gpon局端设备网络工程割接方法

Also Published As

Publication number Publication date
CN103945015A (zh) 2014-07-23

Similar Documents

Publication Publication Date Title
CN112737690B (zh) 一种光线路终端olt设备虚拟方法及相关设备
CN111669362B (zh) 信息处理方法、网络节点、验证方法和服务器
CN104202266B (zh) 一种通信方法、交换机、控制器及通信系统
WO2015154458A1 (zh) 一种节点逻辑id的分配装置、方法及通信系统
CN106878480B (zh) 一种dhcp服务进程共享方法及装置
US10523464B2 (en) Multi-homed access
CN103297353A (zh) 用户终端设备的接入方法、系统和宽带网络网关
CN109121026B (zh) 一种基于逻辑端口实现volt的方法及系统
EP3493483A1 (en) Virtual broadband access method, controller, and system
EP2940938A1 (en) Method and device for establishing multicast data channel in network virtualization system
CN107204907B (zh) 云数据中心互联方法及装置
CN110855809B (zh) 报文处理方法及装置
WO2012109849A1 (zh) Mac地址分配方法和设备
CN102291259B (zh) 基于多主站模式的低压电力线通信网络层管理方法
KR101786620B1 (ko) 소프트웨어 정의 네트워크에서 서브넷을 지원하는 방법, 장치 및 컴퓨터 프로그램
EP3883257B1 (en) Data communication and communication management method based on distributed processing unit (dpu) and dpu
CN108234270B (zh) 实现虚拟可扩展局域网多域并存的方法和系统
US9900804B2 (en) Method and device for processing to share network resources, and method, device and system for sharing network resources
CN103684861A (zh) 网络配置的处理方法和装置以及通信系统
CN106330511B (zh) 网元设备及数据通信网络开通的方法
WO2016095142A1 (zh) 软件定义网络sdn中数据转发的方法、设备和系统
CN104104749A (zh) 一种隧道ip地址的分配方法及装置
CN108259633B (zh) 实现管理报文三层通信的方法、系统及装置
WO2023056856A1 (zh) 光网络中的设备管理的方法、装置以及设备
CN108259345B (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: 14888941

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: 14888941

Country of ref document: EP

Kind code of ref document: A1