WO2020125524A1 - 一种光纤分布式接入系统及其管理方法 - Google Patents

一种光纤分布式接入系统及其管理方法 Download PDF

Info

Publication number
WO2020125524A1
WO2020125524A1 PCT/CN2019/124660 CN2019124660W WO2020125524A1 WO 2020125524 A1 WO2020125524 A1 WO 2020125524A1 CN 2019124660 W CN2019124660 W CN 2019124660W WO 2020125524 A1 WO2020125524 A1 WO 2020125524A1
Authority
WO
WIPO (PCT)
Prior art keywords
slave
station device
master
slave station
master station
Prior art date
Application number
PCT/CN2019/124660
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 WO2020125524A1 publication Critical patent/WO2020125524A1/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
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/27—Arrangements for networking
    • H04B10/272—Star-type networks or tree-type networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/645—Fibre channel identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/69—Types of network addresses using geographic information, e.g. room number

Definitions

  • the present application relates to the field of communication technology, in particular to an optical fiber distributed access system and its management method.
  • the optical fiber distributed access system is mainly composed of a main unit (MU), an extension unit (Extend Unit, EU) and a user unit (Remote Unit, RU).
  • MU main unit
  • EU Extension Unit
  • RU Remote Unit
  • the traditional optical fiber distributed access system adopts the master-slave structure, that is, the MU is the master station, and the EU and RU are the MU slave stations. In order to manage the slave stations, it is necessary to assign numbers to the master and slave stations to identify the corresponding master and slave stations by the numbers.
  • the master station and slave station are assigned numbers manually, that is, by manually assigning the slave station device number at the master station and setting the device number to the slave station, the slave station device number assignment is completed.
  • the slave station is removed from the optical fiber distributed access system, you need to manually delete the device number assigned to the slave station at the master station.
  • the slave station needs to report to the network management center after opening the station, it is necessary to manually trigger the slave station to access the network management center, that is, the management of the slave station needs to manually trigger the station opening and removal.
  • the embodiments of the present application provide an optical fiber distributed access system and a management method thereof, which are used to solve the technical problem of inflexible networking and low efficiency caused by manually configured device numbers in the prior art.
  • an embodiment of the present application provides a management method for an optical fiber distributed access system, which is applied to an optical fiber distributed access system.
  • the optical fiber distributed access system includes a master station device and multiple slave station devices, where , The multiple slave station devices are connected in a daisy chain to form multiple links; the master station device and the multiple links form a star topology, and the management method includes:
  • the master station device sends a request message to each slave station device, where the request message is used to request the serial number and routing address of each slave station device;
  • the master station device receives a response message from each slave station device, where the response message carries the serial number and routing address of each slave station device;
  • the master device determines whether the serial number and routing address in the response message are in the management list; wherein, the first slave device is any of the multiple slave devices One slave device;
  • the master station device determines that the serial number and the routing address are not in the management list, it allocates a new device number to the first slave station device to use the device number for each slave Station equipment.
  • the master station device automatically allocates the device number to the slave station device according to the information in the management list, such as the serial number or routing address. Compared with manual allocation, the allocation efficiency is improved, and it can be flexibly implemented according to the management list Networking.
  • an optical fiber distributed access system including a master station device and multiple slave station devices, wherein the multiple slave station devices are connected in a daisy chain manner to form multiple links;
  • the master station device and the multiple links form a star topology; wherein, the master station device includes:
  • a sending unit configured to send a request message to each slave device, wherein the request message is used to request to obtain the serial number and routing address of each slave device;
  • a receiving unit configured to receive a response message from each slave station device, where the response message carries the serial number and routing address of each slave station device;
  • the judging unit is used to judge whether the serial number and the routing address in the response message are in the management list for the first slave device; wherein, the first slave device is any of the multiple slave devices One slave device;
  • An allocation unit configured to allocate a new device number to the first slave device if it is determined that the serial number and the routing address are not in the management list, so that each slave Station equipment.
  • a fiber optic distributed access system including a master station device and multiple slave station devices, wherein the multiple slave station devices are connected in a daisy chain manner to form multiple links;
  • the master station device and the multiple links form a star topology; wherein, the master station device includes:
  • At least one processor and
  • a memory connected to the at least one processor
  • the memory stores instructions executable by the at least one processor, and the at least one processor implements the management method according to any one of the first aspects by executing the instructions stored in the memory.
  • a computer storage medium on which a computer program is stored, and when the computer program is executed by a processor, the method according to any one of the first aspect is implemented.
  • the master station device automatically allocates the device number to the slave station device according to the information in the management list, such as the serial number or routing address. Compared with manual allocation, the allocation efficiency is improved, and it can be flexibly implemented according to the management list Networking.
  • FIG 1 is an architecture diagram of an optical fiber distributed access system provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a management method of an optical fiber distributed access system provided by an embodiment of this application;
  • FIG. 3 is a schematic structural diagram of a master station device provided by an embodiment of this application.
  • FIG. 4 is a schematic structural diagram of a master station device provided by an embodiment of the present application.
  • each slave station is assigned a number manually, and a report is triggered for each slave station.
  • the efficiency of distribution is low. And it may cause the same number to be assigned to two different slave stations, which brings inconvenience to the management of the slave stations.
  • the embodiments of the present application provide a management method for an optical fiber distributed access system.
  • the master station device automatically allocates devices to the slave station devices based on information in the management list, such as serial numbers or routing addresses. Numbering, compared with manual allocation, improves allocation efficiency, and can be flexibly implemented according to the management list.
  • FIG. 1 includes a master station device and multiple slave station devices, where multiple slave station devices are daisy-chained Connected to form multiple links, the master station equipment and multiple links form a star topology.
  • Figure 1 takes 5 links as an example.
  • the master station device may be a MU device, and the slave station device may be an EU device and a RU device.
  • Figure 1 uses this as an example. Of course, it may also be other possible devices.
  • FIG. 2 is a method for managing an optical fiber distributed access system according to an embodiment of the present application. The flow of the method is described as follows.
  • Step S201 The master station device sends a request message to each slave station device, where the request message is used to request the serial number and routing address of each slave station device.
  • multiple slave devices and a master device are deployed in advance as the system shown in FIG. 1.
  • the master station device In order to manage the master station device and the slave station device, it is necessary to assign numbers to the master station device and the slave station device to identify the corresponding master station device and slave station device by the number.
  • the master station device automatically allocates a device number to the accessed slave station device.
  • the master station device may send a request message to each slave station device accessed to request the serial number and routing address of each slave station device to identify the corresponding slave station device by the serial number and/or routing address To assign device numbers to slave devices.
  • the master station device may obtain network topology address information of the optical fiber distributed access system, and the network topology address information is used to indicate the physical properties of the master station device and multiple slave station devices The connection location, and the correspondence between the master device or slave device corresponding to each physical connection location and its own IP address, so that the master device can determine the physical connection location and network topology address information of each slave device IP addresses of multiple slave devices.
  • the master station device sends a request message to each slave station device that has obtained an IP address.
  • the request messages may be sequentially sent to the slave station devices one by one, or the request messages may be sent to each slave station device that has obtained the IP address at the same time, so as to maximize the acquisition efficiency.
  • Step S202 The master station device receives a response message from each slave station device, where the response message carries the serial number and routing address of each slave station device.
  • the slave device After receiving the request message, the slave device can report its serial number to the master device, that is, generate a serial number, routing address, etc. Of course, if the slave device has been assigned a device number, the slave device can also send to the master The device reports the device number. If the master device sends request messages to multiple slave devices at the same time, it may cause multiple slave devices to send response messages to the master device at the same time, then the master device may miss some slave devices due to network congestion The response message is sent, so the master device can sequentially send request messages to the slave devices. Or, the master device can send request messages to some slave devices at the same time to ensure that the acquisition efficiency can be improved, and the master device can avoid the response message sent by the slave device as much as possible.
  • Step S203 For the first slave station device, the master station device determines whether the serial number and the routing address in the response message are in the management list, where the first slave station device is any slave station device among the multiple slave station devices.
  • the master station device may assign device numbers to the slave station devices according to the serial number and/or routing address carried in the response message. Specifically, taking an example of assigning a device number to any slave device, such as the first slave device, the master device can target the first slave device according to the serial number in the response message and whether the routing address is in the management list. The first slave device allocates the device number.
  • management list can be understood as a correspondence table of serial numbers, routing addresses, and device numbers of slave station devices, and the management list is maintained by the master station device.
  • Step S204 If the master station device determines that the serial number and the routing address are not in the management list, assign a new device number to the first slave station device to manage each slave station device by the device number.
  • the master station device When the master station device assigns a device number to the first slave device, it first determines whether the serial number and routing address in the response message are in the management list. If neither the production serial number nor the routing address are saved in the management list, the first slave device is considered to be a newly accessed slave device, and the master device can assign an unused device number to the first slave device And set the first slave device by setting the device number command. And the newly allocated device number is added to the management list together with the serial number and routing address of the first slave device to facilitate management of all slave devices.
  • the master device determines that the serial number of the first slave device is in the management list, it can be considered that the first slave device has been assigned before. At this time, the master device can determine the device number and management list carried in the response message. Whether the device numbers corresponding to the serial numbers of the first slave device are consistent. If they are consistent, the master device does not need to generate a new device number, and the device number assigned before the first slave device can be used. If the master device determines that the device number is not consistent with the device number corresponding to the serial number of the first slave device, it means that there are two device numbers for the first slave device.
  • the master device can add the management list
  • the device number corresponding to the serial number is assigned to the first slave device, and at the same time, the routing address of the first slave device is updated to the management list to limit the use of the device number in the management list as much as possible.
  • the master device can add the management list
  • the device number corresponding to the serial number is assigned to the first slave device, and at the same time, the routing address of the first slave device is updated to the management list to limit the use of the device number in the management list as much as possible.
  • the master device determines that the routing address is in the management list, the status of the device number corresponding to the routing address is determined. If the status of the device number corresponding to the routing address is determined to be unassigned, then it can be considered as The device number corresponding to the routing address has not yet been assigned. At this time, the device number corresponding to the routing address can be assigned to the first slave device, and at the same time the serial number of the first slave device is updated to the management list.
  • the embodiment of the present application considers that the slave device may be replaced, so the initial device number assigned to the slave device may continue to be assigned to the replaced slave device to ensure the reuse of the device number as much as possible.
  • the master device updates the management list if any of the serial number, routing address, and device number changes, and the management list can also indicate The device number is in the assigned state or unassigned state.
  • the slave station equipment may fail or be damaged during actual use, so it will involve replacement.
  • the replacement of the slave station equipment is in the system described in Figure 1.
  • the routing address or IP address is not Will change. Therefore, in the embodiment of the present application, when the master device determines that there is a certain slave device, and the second slave device is replaced as an example, the serial number of the second slave device may be removed from the management list, And set the status of the device number of the second slave device to the unassigned state. In this case, the master device can use the device number of the second slave device to assign the newly accessed slave device without regenerating a new one Device number to minimize the number of device numbers, reduce the burden on the master station, and facilitate the maintenance of multiple slave devices.
  • the master device determines that there is a slave device, and the third slave device is removed or fails, for example, the status of the device number of the third slave device is set to an abnormal state.
  • the three slave devices may not be replaced immediately, so the master device can set the status of the device number previously assigned to the third slave device to an abnormal state at this time, so that if the failure of the third slave device is eliminated later , Reset the status to the normal status, so that there is no need to change the device number, which is convenient for management.
  • the embodiments of the present application consider that the device numbers are initially assigned to all slave devices, but in reality some slave devices may be removed or malfunctioned, then in order to ensure that the number of device numbers is small, you can manage The device number with abnormal status in the list is assigned to the newly connected slave device for easy management. Therefore, in the embodiment of the present application, if the master station device determines that the number of actually accessed slave station devices is less than the full number of device numbers in the management list, it assigns the device number in the management list that is abnormal to the new connection Incoming slave devices, where the full amount is the total number of slave devices connected to the master device at the same time.
  • the number of slave devices accessed by the general master device is 32.
  • the device number in the management list is 32, that is, the device number assigned by the management list is full, but the actual number of slave devices accessed is less than 32.
  • the master station device can assign the device number in the management list with an abnormal state to the newly connected device in order.
  • the master station device may also report the status of the slave station device to the network management center. Specifically, the master station device may periodically query the status of the slave station device in the management list. If it is determined that the status of the slave station device is normal and the station has not been reported, a request to open the station is sent to the network management center to notify the network manager The center updates the slave device information. Of course, if there is a slave station device removed, the master station device can trigger and report the removal to the network management center.
  • the embodiment of the present application takes the two-level architecture shown in FIG. 1 as an example.
  • the embodiment of the present application can also be applied to a three-level architecture, that is, the expansion unit is connected to the master station device, and each expansion unit The remote device can also be accessed, where the remote device can be regarded as the slave device of the expansion unit, and the expansion unit is the slave device of the master device.
  • the master station device automatically allocates the device number to the slave station device according to the information in the management list, such as the serial number or the routing address. Compared with manual allocation, the allocation efficiency is improved, and it can be managed according to The list is flexible to achieve networking.
  • an embodiment of the present application provides an optical fiber distributed access system, including a master station device and multiple slave station devices, where multiple slave station devices are connected in a daisy chain manner , Forming multiple links; the master station device and multiple links form a star topology; where the master station device includes a sending unit 301, a receiving unit 302, a judging unit 303, and an allocation unit 304, where the sending unit 301 is used to Send a request message to each slave device, where the request message is used to request the serial number and routing address of each slave device; the receiving unit 302 is used to receive a response message from each slave device, where the response message Carrying the serial number and routing address of each slave device; the judging unit 303 is used to judge whether the serial number and routing address in the response message are in the management list for the first slave device; where the first slave device is Any slave device among multiple slave devices; the allocation unit 304 is used to assign a new device number to the first slave device if it is determined that the
  • the sending unit 301 is specifically used to:
  • the master device obtains the Internet protocol IP addresses of multiple slave devices
  • the master station device sends a request message to each slave station device according to the obtained IP address.
  • the sending unit 301 is specifically used to:
  • the master station device obtains the network topology address information of the optical fiber distributed access system; wherein, the network topology address information is used to indicate the correspondence between the physical connection position of the master station device and multiple slave station devices and the IP address;
  • the master device determines the IP addresses of multiple slave devices based on the physical connection location of each slave device and network topology address information.
  • the distribution unit 304 is also used for:
  • the master device determines that the serial number of the first slave device is in the management list, it is determined whether the device number carried in the response message is consistent with the device number corresponding to the serial number of the first slave device in the management list;
  • the master device determines that the device number does not match the device number corresponding to the serial number of the first slave device, it assigns the device number corresponding to the serial number to the first slave device.
  • the distribution unit 304 is also used for:
  • the master device determines that the routing address is in the management list, it determines the status of the device number corresponding to the routing address;
  • the master device determines that the state is unassigned, it assigns the device number corresponding to the routing address to the first slave device.
  • the distribution unit 304 is also used for:
  • the serial number of the second slave device is removed from the management list, and the state of the device number of the second slave device is set to the unassigned state
  • the master device determines that a third slave device has been removed or malfunctioned, the status of the device number of the third slave device is set to an abnormal state.
  • the distribution unit 304 is also used for:
  • the master device determines that the number of slave devices actually accessed is less than the full number of device numbers in the management list, the device number in the management list with an abnormal status is assigned to the newly accessed slave device; The number is the total number of slave devices connected to the master device at the same time.
  • the distribution unit 304 is also used for:
  • the master device periodically queries the status of slave devices in the management list
  • an embodiment of the present application provides an optical fiber distributed access system, including a master station device and multiple slave station devices, where multiple slave station devices are connected in a daisy chain manner , Forming multiple links; the master station device and the multiple links form a star topology; wherein, the master station device includes: at least one processor 401, which is used to implement the application when executing a computer program stored in a memory The steps of the management method for the optical fiber distributed access system shown in FIG. 2 provided in the embodiment.
  • the master station device further includes a memory 402 connected to at least one processor.
  • the memory 402 is used to store data required by the processor 401 during operation, that is, it stores instructions executable by at least one processor 401, and the at least one processor 401 executes the method shown in FIG. 2 by executing the instructions stored in the memory 402 .
  • the number of the memory 402 is one or more.
  • the memory 402 is shown together in FIG. 4, but it is necessary to know that the memory 402 is not a mandatory functional module, so it is shown with a dotted line in FIG. 4.
  • the physical devices corresponding to the sending unit 301, the receiving unit 302, the judging unit 303, and the allocating unit 304 may all be the aforementioned processor 401.
  • the ciphertext retrieval device can be used to execute the method provided by the embodiment shown in FIG. 2. Therefore, for the functions that can be realized by the functional modules in the device, reference may be made to the corresponding description in the embodiment shown in FIG. 2, and details are not described in detail.
  • An embodiment of the present application further provides a computer storage medium, wherein the computer storage medium stores computer instructions, and when the computer instructions run on the computer, the computer is caused to execute the method shown in FIG. 2.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the modules or units is only a division of logical functions.
  • there may be other divisions for example, multiple units or components may be The combination can either be integrated into another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or software function unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application may be essentially or part of the contribution to the existing technology or all or part of the technical solution may be embodied in the form of a software product, and the computer software product is stored in a storage medium It includes several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the embodiments of the present application.
  • the aforementioned storage media include: Universal Serial Bus flash disk (Universal Serial Bus flash disk), mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk Or various media such as optical discs that can store program codes.
  • Universal Serial Bus flash disk Universal Serial Bus flash disk
  • mobile hard disk read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM)
  • RAM Random Access Memory
  • magnetic disk or various media such as optical discs that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Small-Scale Networks (AREA)

Abstract

本申请公开了一种光纤分布式接入系统及其管理方法。该方法包括：主站设备向每个从站设备发送请求消息，其中，请求消息用于请求获取每个从站设备的序列号以及路由地址；主站设备接收来自每个从站设备的响应消息，其中，响应消息携带了每个从站设备的序列号以及路由地址；针对第一从站设备，主站设备判断响应消息中的序列号以及路由地址是否在管理列表中；其中，第一从站设备为多个从站设备中的任一从站设备；若主站设备确定序列号以及路由地址不在管理列表中，则为第一从站设备分配新的设备编号，以通过设备编号对每个从站设备进行管理。

Description

一种光纤分布式接入系统及其管理方法 技术领域
本申请涉及通信技术领域，特别涉及一种光纤分布式接入系统及其管理方法。
背景技术
光纤分布式接入系统主要由主单元(MU)、扩展单元(Extend Unit，EU)和用户单元(Remote Unit，RU)组成。当需要扩容升级时，只需要增加或者变更EU即可。传统的光纤分布式接入系统采用主从结构，也就是MU为主站，EU和RU为MU的从站。为了管理从站，就需要为主站和从站分配编号，以通过编号识别对应的主站和从站。
目前为主站和从站分配编号采用手动分配方式，也就是通过在主站手动分配从站的设备编号，并将该设备编号设置给从站，完成从站设备编号的分配。当从站从光纤分布式接入系统移除时，需要在主站手动删除为从站分配的设备编号。当从站开站需要上报给网管中心时，需要手动触发从站接入网管中心，即对从站的管理都是需要人为的触发开站和移除。
如果采用人工方式对每个从站分配编号，并对每个从站触发上报，随着接入光纤分布式接入系统的从站数量的增加，那么分配的效率较低。且可能会导致将同一个编号分配给两个不同的从站，为从站的管理带来不便。
发明内容
本申请实施例提供一种光纤分布式接入系统及其管理方法，用于解决现有技术中存在的人工配置设备编号导致组网不灵活且效率低下的技术问题。
第一方面，本申请实施例提供了光纤分布式接入系统的管理方法，应用于光纤分布式接入系统，所述光纤分布式接入系统包括一个主站设备以及多个从 站设备，其中，所述多个从站设备以菊花链的方式连接，形成多条链路；所述主站设备与所述多条链路构成星型拓扑结构，所述管理方法包括：
所述主站设备向每个从站设备发送请求消息，其中，所述请求消息用于请求获取所述每个从站设备的序列号以及路由地址；
所述主站设备接收来自所述每个从站设备的响应消息，其中，所述响应消息携带了所述每个从站设备的序列号以及路由地址；
针对第一从站设备，所述主站设备判断所述响应消息中的序列号以及路由地址是否在管理列表中；其中，所述第一从站设备为所述多个从站设备中的任一从站设备；
若所述主站设备确定所述序列号以及所述路由地址不在所述管理列表中，则为所述第一从站设备分配新的设备编号，以通过所述设备编号对所述每个从站设备进行管理。
本申请实施例中，主站设备根据管理列表中的信息，例如序列号或路由地址，自动为从站设备分配设备编号，相较于手动分配，提高了分配效率，且可以根据管理列表灵活实现组网。
第二方面，提供了一种光纤分布式接入系统，包括一个主站设备以及多个从站设备，其中，所述多个从站设备以菊花链的方式连接，形成多条链路；所述主站设备与所述多条链路构成星型拓扑结构；其中，主站设备包括：
发送单元，用于向每个从站设备发送请求消息，其中，所述请求消息用于请求获取所述每个从站设备的序列号以及路由地址；
接收单元，用于接收来自所述每个从站设备的响应消息，其中，所述响应消息携带了所述每个从站设备的序列号以及路由地址；
判断单元，用于针对第一从站设备，判断所述响应消息中的序列号以及路由地址是否在管理列表中；其中，所述第一从站设备为所述多个从站设备中的任一从站设备；
分配单元，用于若确定所述序列号以及所述路由地址不在所述管理列表中， 则为所述第一从站设备分配新的设备编号，以通过所述设备编号对所述每个从站设备进行管理。
第三方面，提供了一种光纤分布式接入系统，包括一个主站设备以及多个从站设备，其中，所述多个从站设备以菊花链的方式连接，形成多条链路；所述主站设备与所述多条链路构成星型拓扑结构；其中，主站设备包括：
至少一个处理器，以及
与所述至少一个处理器连接的存储器；
其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述至少一个处理器通过执行所述存储器存储的指令实现如第一方面任一项所述的管理方法。
第四方面，提供一种计算机存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如第一方面任一项所述的方法。
本申请实施例中，主站设备根据管理列表中的信息，例如序列号或路由地址，自动为从站设备分配设备编号，相较于手动分配，提高了分配效率，且可以根据管理列表灵活实现组网。
附图说明
图1是本申请实施例提供的光纤分布式接入系统的架构图；
图2为本申请实施例提供的光纤分布式接入系统的管理方法的流程示意图；
图3为本申请实施例提供的主站设备的一种结构示意图；
图4为本申请实施例提供的主站设备的一种结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚明白，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
现有技术中，采用人工方式对每个从站分配编号，并对每个从站触发上报， 随着接入光纤分布式接入系统的从站数量的增加，那么分配的效率较低。且可能会导致将同一个编号分配给两个不同的从站，为从站的管理带来不便。
鉴于此，本申请实施例提供了一种光纤分布式接入系统的管理方法，在该方法中，主站设备根据管理列表中的信息，例如序列号或路由地址，自动为从站设备分配设备编号，相较于手动分配，提高了分配效率，且可以根据管理列表灵活实现组网。
本申请实施例中，需要分配设备编号的设备称为从站设备，用于为从站设备分配编号的设备称为主站设备。请参见图1，介绍本申请实施例的一种应用场景，即光纤分布式接入系统，图1包括一个主站设备以及多个从站设备，其中，多个从站设备以菊花链的方式连接，形成多条链路，主站设备与多条链路构成星型拓扑结构。图1以包括5条链路为例。主站设备可以是MU设备，从站设备可以是EU设备和RU设备，图1以此为例，当然也可以是其他可能的设备。
下面结合说明书附图介绍本申请实施例提供的技术方案，在下面的描述中以图1所示的应用场景为例。
请参见图2，图2为本申请实施例提供的一种光纤分布式接入系统的管理方法，该方法的流程描述如下。
步骤S201、主站设备向每个从站设备发送请求消息，其中，请求消息用于请求获取每个从站设备的序列号以及路由地址。
在一种实施方式中，多个从站设备和一个主站设备事先部署成如图1所示的系统。为了管理主站设备和从站设备，就需要为主站设备和从站设备分配编号，以通过编号识别对应的主站设备和从站设备。本申请实施例通过主站设备自动为所接入的从站设备分配设备编号。
具体地，主站设备可以向接入的每个从站设备发送请求消息，以请求获取每个从站设备的序列号以及路由地址，以通过序列号和/或路由地址识别对应的从站设备，从而为从站设备分配设备编号。
可能的实施方式中，主站设备在上电或者复位启动后，可以获取光纤分布式接入系统的网络拓扑地址信息，该网络拓扑地址信息用于指示主站设备以及多个从站设备的物理连接位置，以及每个物理连接位置所对应的主站设备或从站设备与自身IP地址的对应关系，从而主站设备可以根据每个从站设备的物理连接位置以及网络拓扑地址信息，确定出多个从站设备的IP地址。这样主站设备向获取了IP地址的每个从站设备发送请求消息。本申请实施例可以依次逐个向从站设备发送请求消息，也可以同时向获取了IP地址的每个从站设备发送请求消息，以尽量提高获取效率。
步骤S202、主站设备接收来自每个从站设备的响应消息，其中，响应消息携带了每个从站设备的序列号以及路由地址。
从站设备接收到请求消息之后，可以向主站设备上报自身的序列号，也就是生成序列号、路由地址等，当然如果从站设备已经被分配了设备编号，从站设备还可以向主站设备上报设备编号。如果主站设备同时向多个从站设备发送请求消息，可能导致多个从站设备同时向主站设备发送响应消息，那么由于网络的拥堵，可能会导致主站设备漏接收某些从站设备发送的响应消息，所以主站设备可以依次逐个向从站设备发送请求消息。或者，主站设备可以同时向某些从站设备发送请求消息，以尽量保证既可以提高获取效率，又可以尽量避免主站设备漏接收从站设备发送的响应消息。
步骤S203、针对第一从站设备，主站设备判断响应消息中的序列号以及路由地址是否在管理列表中，其中，第一从站设备为多个从站设备中的任一从站设备。
主站设备接收到多个从站设备发送的响应消息之后，可以根据响应消息中携带的序列号和/或路由地址为从站设备分配设备编号。具体地，以为任一从站设备，例如第一从站设备分配设备编号为例，主站设备针对第一从站设备，可以根据响应消息中的序列号以及路由地址是否在管理列表中，为第一从站设备进行分配设备编号。
需要说明的是，管理列表可以理解是从站设备的序列号、路由地址以及设备编号的对应关系表，该管理列表由主站设备维护。
步骤S204、若主站设备确定序列号以及路由地址不在管理列表中，则为第一从站设备分配新的设备编号，以通过设备编号对每个从站设备进行管理。
主站设备在为第一从站设备分配设备编号时，首先判断响应消息中的序列号以及路由地址是否在管理列表中。如果生产序列号和路由地址都没有保存到管理列表中，则认为第一从站设备是新接入的从站设备，此时主站设备可以为第一从站设备分配一个未使用的设备编号，并通过设置设备编号命令，设置第一从站设备。且将新分配的设备编号与第一从站设备的序列号、路由地址一起添加到管理列表中，便于管理所有的从站设备。
而如果主站设备确定第一从站设备的序列号在管理列表中，则可以认为第一从站设备之前已经被分配过，此时主站设备可以判断响应消息携带的设备编号与管理列表中的第一从站设备的序列号对应的设备编号是否一致，如果一致，那么主站设备就不需要生成新的设备编号，采用第一从站设备之前分配的设备编号即可。而如果主站设备确定设备编号与第一从站设备的序列号对应的设备编号不一致，那么说明第一从站设备存在两个设备编号，此时为了便于维护，主站设备可以将管理列表中与序列号对应的设备编号分配给第一从站设备，同时将第一从站设备的路由地址更新到管理列表中，以尽量有限使用管理列表中的设备编号。这样即使第一从站设备是后面更换其他从站设备接入的，那么一台从站设备的序列号不变的话，为了便于管理，尽量保证为该序列号初始分配到设备编号也不变，从而设备编号的数量较少，便于维护。
可能的实施方式中，如果主站设备确定路由地址在管理列表中，则确定与路由地址对应的设备编号的状态，如果确定与路由地址对应的设备编号的状态为未分配状态，那么可以认为与路由地址对应的设备编号还未分配，此时可以将与路由地址对应的设备编号分配给第一从站设备，同时将第一从站设备的序列号更新到管理列表中。本申请实施例考虑到从站设备有可能被更换，那么为 从站设备分配的初始设备编号可以继续分配给更换后的从站设备，以尽量保证设备编号的重复利用。
需要说明的是，主站设备在为从站设备分配设备编号的过程中，如果涉及到序列号、路由地址以及设备编号中的任一发生改变时，均更新管理列表，且管理列表还可以指示设备编号处于分配状态或者未分配状态。
从站设备在实际使用过程中，可能会发生故障，也可能会损坏，那么就会涉及到被更换，而从站设备的更换在如图1所述的系统中，其路由地址或者IP地址不会改变。因此，在本申请实施例中，当主站设备确定有某一从站设备，以第二从站设备为例被更换时，可以将第二从站设备的序列号从管理列表中移除，并将第二从站设备的设备编号的状态设置为未分配状态，这样的话，主站设备可以利用第二从站设备的设备编号为新接入的从站设备分配，而不需要重新生成新的设备编号，以尽量减少设备编号的数量，减轻主站设的负担，便于维护多个从站设备。
当主站设备确定有某一从站设备，以第三从站设备为例被移除或者发生故障时，将第三从站设备的设备编号的状态设置为异常状态，有可能发生故障的第三从站设备还可以不会立即更换，所以此时主站设备可以将之前为第三从站设备分配的设备编号的状态设置为异常状态，以便于后期如果第三从站设备的故障排除以后，将状态重新设置为正常状态，这样就不需要变更设备编号，便于管理。
本申请实施例考虑到初始为所有的从站设备分配的了设备编号，但是实际中可能有的从站设备移除了或者发生故障了，那么为了尽量保证设备编号的数量较少，可以将管理列表中状态为异常的设备编号分配给新接入的从站设备，以便于管理。因此，在本申请实施例中，主站设备如果确定实际接入的从站设备的数量少于管理列表中的设备编号的满额数量，则将管理列表中状态为异常的设备编号分配给新接入的从站设备，其中，满额数量为同时连接主站设备的最多从站设备的总数量。
例如，目前一般主站设备接入的从站设备是32个，当管理列表中的设备编号为32个，即管理列表分配的设备编号满时，但实际接入的从站设备少于32个时，主站设备可以按照顺序，将管理列表中状态为异常状态的设备编号分配给新接入的设备。
在本申请实施例中，主站设备还可以向网管中心上报从站设备的状态等情况。具体的，主站设备可以周期性地查询管理列表中的从站设备的状态，如果确定从站设备的状态为正常状态且未开站上报，则向网管中心发送请求开站消息，以通知网管中心更新从站设备信息。当然如果有从站设备移除时，主站设备可以触发并向网管中心上报移除。
需要说明的是，本申请实施例以图1所示的二级架构为例，实质上本申请实施例还可以应用于三级架构，即主站设备接入的是扩展单元，每个扩展单元又可以接入远端设备，其中，远端设备可以认为是扩展单元的从站设备，扩展单元是主站设备的从站设备。
综上，本申请实施例中，主站设备根据管理列表中的信息，例如序列号或路由地址，自动为从站设备分配设备编号，相较于手动分配，提高了分配效率，且可以根据管理列表灵活实现组网。
下面结合附图说明介绍本申请实施例提供的设备。
请参见图3，基于同一发明构思，本申请一实施例提供一种光纤分布式接入系统，包括一个主站设备以及多个从站设备，其中，多个从站设备以菊花链的方式连接，形成多条链路；主站设备与多条链路构成星型拓扑结构；其中，主站设备包括发送单元301、接收单元302、判断单元303和分配单元304，其中，发送单元301用于向每个从站设备发送请求消息，其中，请求消息用于请求获取每个从站设备的序列号以及路由地址；接收单元302用于接收来自每个从站设备的响应消息，其中，响应消息携带了每个从站设备的序列号以及路由地址；判断单元303用于针对第一从站设备，判断响应消息中的序列号以及路由地址是否在管理列表中；其中，第一从站设备为多个从站设备中的任一从站 设备；分配单元304用于若确定序列号以及路由地址不在管理列表中，则为第一从站设备分配新的设备编号，以通过设备编号对每个从站设备进行管理。
可选的，发送单元301具体用于：
主站设备获取多个从站设备的网际协议IP地址；
主站设备根据获取的IP地址向每个从站设备发送请求消息。
可选的，发送单元301具体用于：
主站设备获取光纤分布式接入系统的网络拓扑地址信息；其中，网络拓扑地址信息用于指示主站设备以及多个从站设备的物理连接位置与IP地址的对应关系；
主站设备根据每个从站设备的物理连接位置以及网络拓扑地址信息，确定多个从站设备的IP地址。
可选的，分配单元304还用于：
若主站设备确定第一从站设备的序列号在管理列表中，则判断响应消息携带的设备编号与管理列表中的第一从站设备的序列号对应的设备编号是否一致；
若主站设备确定设备编号与第一从站设备的序列号对应的设备编号不一致，则将与序列号对应的设备编号分配给第一从站设备。
可选的，分配单元304还用于：
若主站设备确定路由地址在管理列表中，则确定与路由地址对应的设备编号的状态；
若主站设备确定状态为未分配状态，则将与路由地址对应的设备编号分配给第一从站设备。
可选的，分配单元304还用于：
当主站设备确定有第二从站设备被更换时，将第二从站设备的序列号从管理列表中移除，并将第二从站设备的设备编号的状态设置为未分配状态；
当主站设备确定有第三从站设备被移除或者发生故障时，将第三从站设备 的设备编号的状态设置为异常状态。
可选的，分配单元304还用于：
主站设备若确定实际接入的从站设备的数量少于管理列表中的设备编号的满额数量，则将管理列表中状态为异常的设备编号分配给新接入的从站设备；其中，满额数量为同时连接主站设备的最多从站设备的总数量。
可选的，分配单元304还用于：
主站设备周期性地查询管理列表中的从站设备的状态；
若确定从站设备的状态为正常状态且未开站上报，则向网管中心发送请求开站消息，以通知网管中心更新从站设备信息。
请参见图4，基于同一发明构思，本申请一实施例提供一种光纤分布式接入系统，包括一个主站设备以及多个从站设备，其中，多个从站设备以菊花链的方式连接，形成多条链路；主站设备与多条链路构成星型拓扑结构；其中，主站设备包括：至少一个处理器401，处理器401用于执行存储器中存储的计算机程序时实现本申请实施例提供的如图2所示的光纤分布式接入系统的管理方法的步骤。
可选的，该主站设备还包括与至少一个处理器连接的存储器402。存储器402用于存储处理器401运行时所需的数据，即存储有可被至少一个处理器401执行的指令，至少一个处理器401通过执行存储器402存储的指令，执行如图2所示的方法。其中，存储器402的数量为一个或多个。其中，存储器402在图4中一并示出，但需要知道的是存储器402不是必选的功能模块，因此在图4中以虚线示出。
其中，发送单元301、接收单元302、判断单元303和分配单元304所对应的实体设备均可以是前述的处理器401。该密文检索设备可以用于执行图2所示的实施例所提供的方法。因此关于该设备中各功能模块所能够实现的功能，可参考图2所示的实施例中的相应描述，不多赘述。
本申请实施例还提供一种计算机存储介质，其中，计算机存储介质存储有 计算机指令，当计算机指令在计算机上运行时，使得计算机执行如图2所示的方法。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本发明所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储 介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：通用串行总线闪存盘(Universal Serial Bus flash disk)、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (10)

  1. 一种光纤分布式接入系统的管理方法，应用于光纤分布式接入系统，所述光纤分布式接入系统包括一个主站设备以及多个从站设备，其中，所述多个从站设备以菊花链的方式连接，形成多条链路；所述主站设备与所述多条链路构成星型拓扑结构；所述管理方法包括：
    所述主站设备向每个从站设备发送请求消息，其中，所述请求消息用于请求获取所述每个从站设备的序列号以及路由地址；
    所述主站设备接收来自所述每个从站设备的响应消息，其中，所述响应消息携带了所述每个从站设备的序列号以及路由地址；
    针对第一从站设备，所述主站设备判断所述响应消息中的序列号以及路由地址是否在管理列表中；其中，所述第一从站设备为所述多个从站设备中的任一从站设备；
    若所述主站设备确定所述序列号以及所述路由地址不在所述管理列表中，则为所述第一从站设备分配新的设备编号，以通过所述设备编号对所述每个从站设备进行管理。
  2. 如权利要求1所述的方法，其特征在于，所述主站设备向每个从站设备发送请求消息，包括：
    所述主站设备获取所述多个从站设备的网际协议IP地址；
    所述主站设备根据获取的IP地址向每个从站设备发送请求消息。
  3. 如权利要求2所述的方法，其特征在于，所述主站设备获取所述多个从站设备的网际协议IP地址，包括：
    所述主站设备获取所述光纤分布式接入系统的网络拓扑地址信息；其中，所述网络拓扑地址信息用于指示所述主站设备以及所述多个从站设备的物理连接位置与所述IP地址的对应关系；
    所述主站设备根据每个从站设备的物理连接位置以及所述网络拓扑地址 信息，确定所述多个从站设备的IP地址。
  4. 如权利要求3所述的方法，其特征在于，所述响应消息还携带有所述每个从站设备的设备编号，所述管理方法还包括：
    若所述主站设备确定所述第一从站设备的序列号在所述管理列表中，则判断所述响应消息携带的所述设备编号与所述管理列表中的所述第一从站设备的序列号对应的设备编号是否一致；
    若所述主站设备确定所述设备编号与所述第一从站设备的序列号对应的设备编号不一致，则将与所述序列号对应的设备编号分配给所述第一从站设备。
  5. 如权利要求3所述的方法，其特征在于，所述管理方法还包括：
    若所述主站设备确定所述路由地址在所述管理列表中，则确定与所述路由地址对应的设备编号的状态；
    若所述主站设备确定所述状态为未分配状态，则将与所述路由地址对应的设备编号分配给所述第一从站设备。
  6. 如权利要求1-5任一所述的方法，其特征在于，所述管理方法还包括：
    当所述主站设备确定有第二从站设备被更换时，将所述第二从站设备的序列号从所述管理列表中移除，并将所述第二从站设备的设备编号的状态设置为未分配状态；
    当所述主站设备确定有第三从站设备被移除或者发生故障时，将所述第三从站设备的设备编号的状态设置为异常状态。
  7. 如权利要求6所述的方法，其特征在于，所述管理方法还包括：
    所述主站设备若确定实际接入的从站设备的数量少于所述管理列表中的设备编号的满额数量，则将所述管理列表中状态为异常的设备编号分配给新接入的从站设备；其中，所述满额数量为同时连接所述主站设备的最多从站设备的总数量。
  8. 一种光纤分布式接入系统，包括一个主站设备以及多个从站设备，其中，所述多个从站设备以菊花链的方式连接，形成多条链路；所述主站设备与 所述多条链路构成星型拓扑结构；所述主站设备包括：
    发送单元，用于向每个从站设备发送请求消息，其中，所述请求消息用于请求获取所述每个从站设备的序列号以及路由地址；
    接收单元，用于接收来自所述每个从站设备的响应消息，其中，所述响应消息携带了所述每个从站设备的序列号以及路由地址；
    判断单元，用于针对第一从站设备，判断所述响应消息中的序列号以及路由地址是否在管理列表中；其中，所述第一从站设备为所述多个从站设备中的任一从站设备；
    分配单元，用于若确定所述序列号以及所述路由地址不在所述管理列表中，则为所述第一从站设备分配新的设备编号，以通过所述设备编号对所述每个从站设备进行管理。
  9. 一种光纤分布式接入系统，包括一个主站设备以及多个从站设备，其中，所述多个从站设备以菊花链的方式连接，形成多条链路；所述主站设备与所述多条链路构成星型拓扑结构；所述主站设备包括：
    至少一个处理器，以及
    与所述至少一个处理器连接的存储器；
    其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述至少一个处理器通过执行所述存储器存储的指令实现如权利要求1-8任一项所述的管理方法。
  10. 一种计算机存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-7任一项所述的方法。
PCT/CN2019/124660 2018-12-20 2019-12-11 一种光纤分布式接入系统及其管理方法 WO2020125524A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811577580.5A CN109698871B (zh) 2018-12-20 2018-12-20 一种光纤分布式接入系统及其管理方法
CN201811577580.5 2018-12-20

Publications (1)

Publication Number Publication Date
WO2020125524A1 true WO2020125524A1 (zh) 2020-06-25

Family

ID=66232079

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/124660 WO2020125524A1 (zh) 2018-12-20 2019-12-11 一种光纤分布式接入系统及其管理方法

Country Status (2)

Country Link
CN (1) CN109698871B (zh)
WO (1) WO2020125524A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109698871B (zh) * 2018-12-20 2020-08-28 京信通信系统（中国）有限公司 一种光纤分布式接入系统及其管理方法
CN113587393B (zh) * 2021-08-05 2022-11-29 青岛海信日立空调系统有限公司 中央空调控制系统
CN114097588B (zh) * 2021-10-29 2023-10-31 瀚云科技有限公司 一种灌溉装置的组网方法及装置
CN114095082B (zh) * 2021-11-23 2023-07-25 普罗斯通信技术（苏州）有限公司 分布式天线系统的光纤检测方法、控制模块和计算机介质
CN114143825B (zh) * 2021-12-13 2023-09-12 中信科移动通信技术股份有限公司 基于多模基站的rru管理方法及系统
CN114301731B (zh) * 2021-12-31 2023-12-22 德力西电气有限公司 地址管理方法、主设备及从设备
CN115037721A (zh) * 2022-06-15 2022-09-09 南华机电(太仓)有限公司 从机地址分配方法、装置、通信地址获取方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102420699A (zh) * 2011-11-22 2012-04-18 京信通信系统（中国）有限公司 数字射频拉远系统的设备编号分配方法及系统
WO2014030213A1 (ja) * 2012-08-21 2014-02-27 富士通株式会社 Ｍａｃアドレス管理装置、及び方法
CN105007340A (zh) * 2015-06-30 2015-10-28 苏州汇川技术有限公司 支持即插即用的分布式can网络及其节点地址自动分配方法
CN105099562A (zh) * 2015-07-15 2015-11-25 武汉虹信通信技术有限责任公司 一种主设备给从设备自动编号的方法及系统
CN109698871A (zh) * 2018-12-20 2019-04-30 京信通信系统（中国）有限公司 一种光纤分布式接入系统及其管理方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19614238C1 (de) * 1996-04-10 1997-12-11 Siemens Ag Kommunikationssystem mit einer Meisterstation und mindestens einer Sklavenstation
CN103826252B (zh) * 2014-01-16 2017-05-10 京信通信系统（中国）有限公司 主从设备之间获取及发送序列号的方法和系统
CN104093156B (zh) * 2014-07-24 2017-11-14 京信通信系统（中国）有限公司 分布式基站系统的从站设备地址分配方法和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102420699A (zh) * 2011-11-22 2012-04-18 京信通信系统（中国）有限公司 数字射频拉远系统的设备编号分配方法及系统
WO2014030213A1 (ja) * 2012-08-21 2014-02-27 富士通株式会社 Ｍａｃアドレス管理装置、及び方法
CN105007340A (zh) * 2015-06-30 2015-10-28 苏州汇川技术有限公司 支持即插即用的分布式can网络及其节点地址自动分配方法
CN105099562A (zh) * 2015-07-15 2015-11-25 武汉虹信通信技术有限责任公司 一种主设备给从设备自动编号的方法及系统
CN109698871A (zh) * 2018-12-20 2019-04-30 京信通信系统（中国）有限公司 一种光纤分布式接入系统及其管理方法

Also Published As

Publication number Publication date
CN109698871A (zh) 2019-04-30
CN109698871B (zh) 2020-08-28

Similar Documents

Publication Publication Date Title
WO2020125524A1 (zh) 一种光纤分布式接入系统及其管理方法
US7848327B2 (en) Methods and apparatus for creating addresses
US20220019469A1 (en) Method for Associating NS with VNF, Apparatus, and System
TWI568231B (zh) 自動產生伺服器網路拓撲的方法與系統
US9547502B2 (en) Rebooting InfiniBand clusters
JP5860320B2 (ja) 仮想マシン環境のためのクラスタシステム提供の方法及び装置
CN109995641B (zh) 一种信息处理方法、计算节点和存储介质
WO2019237588A1 (zh) Linux虚拟服务器的创建方法、装置、计算机设备及存储介质
CN109451088A (zh) 一种数据访问方法及装置
TWI448127B (zh) 取得遠端網路位址的方法及其網路協定系統
CN110247997B (zh) Das系统中ip地址分配和拓扑管理的方法、装置和存储介质
JP2004030642A (ja) 監視される機器に関する機器オブジェクトを作成することで遠隔的に機器を監視する方法及び装置
WO2015074396A1 (zh) 一种软件定义网络sdn的自动配置方法、设备及系统
CN114070822B (zh) 一种Kubernetes Overlay IP地址管理方法
CN112416969B (zh) 分布式数据库中的并行任务调度系统
CN105579983A (zh) 提供对等系统标识的基板管理控制器
CN103516547A (zh) 一种网络参数分配方法及装置
CN104506654A (zh) 云计算系统及动态主机配置协议服务器备份方法
CN105704042A (zh) 报文处理方法、bng及bng集群系统
JP2016116184A (ja) 網監視装置および仮想ネットワーク管理方法
CN110365524B (zh) 服务器节点固件的镜像升级方法及系统
CN107547622B (zh) 一种资源调整方法及装置
US20160234257A1 (en) Reusable zone
WO2016110099A1 (zh) 组资源的管理方法及装置
US20140122676A1 (en) Method and Apparatus For Web Based Storage On Demand

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 05/11/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19900948

Country of ref document: EP

Kind code of ref document: A1