WO2024235251A1 - Network management method, communication apparatus, and storage medium - Google Patents

Abstract

Provided are a network management method, a communication apparatus, and a storage medium. The method is applied to a master ONU, the master ONU being connected to a plurality of slave ONUs. The network management method comprises: receiving port request information sent by a first slave ONU, the port request information comprising a device identifier of a first terminal connected to the first slave ONU, the port request information being used for requesting to allocate a port to the first terminal, and the first slave ONU being one of the plurality of slave ONUs; and in response to the port request information, sending first indication information to the plurality of slave ONUs, the first indication information being used for indicating a correspondence between the device identifier of the first terminal and a port identifier of a target port, the target port being a port allocated to the first terminal by the master ONU.

Description

Network management method, communication device, and storage medium

This disclosure claims priority to Chinese patent application No. 202310558327.X filed on May 16, 2023, the entire contents of which are incorporated by reference into this application.

Technical Field

The present disclosure relates to the field of communication technology, and in particular to a network management method, a communication device, and a storage medium.

Background Art

The communications industry has been continuously accelerating the upgrade of fiber optic bandwidth. Currently, most home networks have achieved fiber optic access. The continuous improvement of fiber optic access and other network infrastructure has provided a solid information foundation for the prosperity of Internet services. At the same time, innovative business applications are emerging in an endless stream, such as ultra-high-definition video, cloud virtual reality (VR), cloud gaming, online education, and remote office, which have put forward higher and higher requirements on network bandwidth, latency, and jitter.

Summary of the invention

In one aspect, a network management method is provided. The network management method is applied to a master optical network unit (ONU), where the master ONU is connected to a plurality of slave ONUs. The network management method comprises:

receiving port request information sent by a first slave ONU, the port request information including a device identifier of a first terminal connected to the first slave ONU, the port request information being used to request allocation of a port for the first terminal, the first slave ONU being one of the plurality of slave ONUs;

In response to the port request information, first indication information is sent to multiple slave ONUs, where the first indication information is used to indicate the correspondence between the device identifier of the first terminal and the port identifier of the target port, where the target port is the port allocated by the master ONU to the first terminal.

On the other hand, a network management method is provided. The network management method is applied to a first slave optical network unit (ONU), the first slave ONU is connected to a master ONU, the master ONU is connected to multiple slave ONUs, and the first slave ONU is one of the multiple slave ONUs. The network management method includes:

When detecting that the first terminal is connected, obtaining a device identifier of the first terminal;

In the case that the corresponding relationship related to the device identification of the first terminal is not stored in the master ONU, the port request information is sent to the master ONU, where the port request information includes the device identification of the first terminal, and the port request information is used to request allocation of a port for the first terminal;

Receive first indication information sent by the master ONU, where the first indication information is used to indicate a correspondence between a device identifier of the first terminal and a port identifier of a target port, where the target port is a port allocated by the master ONU to the first terminal;

The correspondence between the device identifier of the first terminal and the port identifier of the target port is stored, and the target port is enabled.

In another aspect, a network management method is provided. The network management method is applied to a second slave optical network unit (ONU), the second slave ONU is connected to a master ONU, the master ONU is connected to a plurality of slave ONUs, and the second slave ONU is one of the plurality of slave ONUs. The network management method comprises:

Receive first indication information sent by the master ONU, where the first indication information is used to indicate a correspondence between a device identifier of the first terminal and a port identifier of a target port, where the target port is a port allocated by the master ONU to the first terminal, where the first terminal is a terminal connected to a first slave ONU, and where the first slave ONU is one of the multiple slave ONUs except the second slave ONU;

The correspondence between the device identifier of the first terminal and the port identifier of the target port is stored.

In another aspect, a communication device is provided. The communication device comprises:

A receiving unit, configured to receive port request information sent by a first slave ONU, wherein the port request information includes a device identifier of a first terminal connected to the first slave ONU, and the port request information is used to request allocation of a port for the first terminal, wherein the first slave ONU is one of the plurality of slave ONUs;

A sending unit, configured to send first indication information to the plurality of slave ONUs in response to the port request information, wherein the first indication information is used to indicate a correspondence between a device identifier of the first terminal and a port identifier of a target port, wherein the target port is the master ONU. The port assigned to the first terminal.

In another aspect, a communication device is provided. The communication device comprises:

an acquiring unit, configured to acquire a device identification of the first terminal when detecting access of the first terminal;

a sending unit, configured to send port request information to the master ONU when the sending unit does not store a corresponding relationship related to the device identification of the first terminal, wherein the port request information includes the device identification of the first terminal, and the port request information is used to request allocation of a port for the first terminal;

The acquiring unit is further used to receive first indication information sent by the master ONU, where the first indication information is used to indicate a correspondence between a device identifier of the first terminal and a port identifier of a target port, where the target port is a port allocated by the master ONU to the first terminal;

The storage unit is used to store the correspondence between the device identifier of the first terminal and the port identifier of the target port, and enable the target port.

In another aspect, a communication device is provided. The communication device comprises:

A receiving unit, configured to receive first indication information sent by the master ONU, wherein the first indication information is used to indicate a correspondence between a device identifier of a first terminal and a port identifier of a target port, wherein the target port is a port allocated by the master ONU to the first terminal, wherein the first terminal is a terminal connected to a first slave ONU, and the first slave ONU is one of the multiple slave ONUs except the second slave ONU;

A storage unit is used to store the correspondence between the device identifier of the first terminal and the port identifier of the target port.

In another aspect, a communication device is provided, comprising: a processor and a memory, wherein the memory stores instructions executable by the processor, and when the processor is configured to execute the instructions, the communication device implements the method provided in any of the above aspects.

In yet another aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the computer executes the method provided in any one of the above aspects.

In another aspect, a computer program product comprising computer instructions is provided. When the computer instructions are executed on a computer, the computer is enabled to execute the method provided in any one of the above aspects.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are used to provide further understanding of the technical solution of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the technical solution of the present disclosure and do not constitute a limitation on the technical solution of the present disclosure.

FIG1 is a schematic diagram of roaming of a current terminal in a FTTR (fiber to the room) system according to some embodiments of the present disclosure.

FIG2 is a schematic diagram of the structure of an FTTR system according to some embodiments of the present disclosure.

FIG3 is a flow chart of a network management method according to some embodiments of the present disclosure.

FIG4 is a flow chart of another network management method according to some embodiments of the present disclosure.

FIG5 is a flow chart of yet another network management method according to some embodiments of the present disclosure.

FIG6 is a flow chart of yet another network management method according to some embodiments of the present disclosure.

FIG. 7 is a flow chart of yet another network management method according to some embodiments of the present disclosure.

FIG8 is a flow chart of yet another network management method according to some embodiments of the present disclosure.

FIG9 is a schematic diagram of a terminal roaming to other slave ONUs according to some embodiments of the present disclosure.

FIG10 is a flow chart of yet another network management method according to some embodiments of the present disclosure.

FIG. 11 is a schematic diagram of an interactive process of a network management method according to some embodiments of the present disclosure.

FIG. 12 is a schematic diagram showing the composition of a communication device according to some embodiments of the present disclosure.

FIG. 13 is a schematic diagram showing the composition of another communication device according to some embodiments of the present disclosure.

FIG. 14 is a schematic diagram of the composition of yet another communication device according to some embodiments of the present disclosure.

FIG. 15 is a schematic diagram of the structure of a communication device according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

In order to enable those skilled in the art to better understand the technical solutions of the embodiments of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present disclosure.

The terms "first", "second", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined by the terms "first", "second", etc. may explicitly or implicitly include one or more of the features. In the description of the present disclosure, unless otherwise specified, "plurality" means two or more.

In the embodiments of the present disclosure, words such as "exemplarily" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of the present disclosure should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a specific way.

Gigabit-capable passive optical networks (GPON) technology is a passive optical network access technology based on the ITU-T G.988 standard. The GPON system includes an optical line terminal (OLT) and an optical network unit (ONU). In the GPON system, data is transmitted between the OLT and the ONU in the link layer in the form of uplink time division and downlink broadcast. That is, each ONU can receive data from other ONUs in the downstream direction. In order to distinguish data belonging to different ONUs/different stream categories, the GPON system adds a GPON encapsulation method port (Gemport) identifier (identity document, ID) to the link layer message to distinguish them. Only when the ONU enables the Gemport corresponding to the Gemport ID can it send and receive data from the specified Gemport.

In FTTR scenarios, terminals will roam between different slave ONUs, and the latency and network resource consumption required during this period have a significant impact on user experience. GPON networks were previously commonly used in fiber to the home (FTTH) scenarios, and terminals do not roam between ONUs. The optimization of FTTR scenarios was not considered at the GPON level, and when terminals roam between different slave ONUs, the master/slave ONU occupies too much bandwidth at the GPON layer, resulting in high latency.

At present, the Gemport between the master and slave ONUs of the FTTR system is configured and enabled when the slave ONU accesses the network. The terminal connected to the slave ONU needs to use the allocated Gemport to send and receive information with the master ONU. In the upstream direction, the slave ONU forwards the upstream message of the terminal to the Gemport specified by the master ONU according to the forwarding rules sent by the master ONU. In the downstream direction, the forwarder of the master ONU learns the device identification of the terminal in the Gemport, such as the physical address (media access control, MAC) of the terminal, to correctly forward the downstream message belonging to the terminal to the Gemport used when the slave ONU forwards the upstream message of the terminal, so that the terminal can receive the downstream message belonging to the terminal.

FIG1 is a schematic diagram of a current terminal roaming in an FTTR system provided by an embodiment of the present disclosure. When the terminal accesses slave ONU1, the master ONU and slave ONU1 forward messages through Gemport1. When the terminal roams from the coverage of slave ONU1 to the coverage of slave ONU2, it accesses slave ONU2, and the master ONU and slave ONU2 forward messages through Gemport2.

This roaming method has the following disadvantages: After the terminal roams to slave ONU2, the terminal needs to send an uplink message so that the master ONU's forwarder can learn the terminal's device identifier on Gemport2, generate a new forwarding rule, and correctly forward the terminal's downlink message to Gemport2. Therefore, the delay required for the terminal to successfully roam and for data services to be forwarded normally is: the time it takes for the terminal to send the uplink message for the first time after roaming + the time it takes for the master ONU to learn the terminal's device identifier and generate a new forwarding rule, resulting in a relatively long delay for the terminal to perform data services after roaming between slave ONUs. The device ID of the terminal will be aged on Gemport1 only after the terminal roams to ONU2 for a period of time, so that during this period of time, the downstream messages belonging to the terminal will still be forwarded to Gemport1, resulting in a waste of downstream bandwidth.

Based on this, the embodiment of the present disclosure provides a network management method, after a terminal accesses a slave ONU, the slave ONU sends a port request information to the master ONU to request the master ONU to allocate a port for the terminal, that is, to allocate a Gemport for the terminal. After the master ONU allocates a target port for the terminal, it establishes a correspondence between the port identifier of the target port and the device identifier of the terminal, generates a forwarding rule for the data service belonging to the terminal for the terminal, and then broadcasts the correspondence between the port identifier of the target port and the device identifier of the terminal to all slave ONUs, so that when the terminal roams from the currently accessed slave ONU to other slave ONUs, other slave ONUs can enable the corresponding target port based on the correspondence between the port identifier of the received target port and the device identifier of the terminal, and can correctly forward the downlink message belonging to the terminal, thereby reducing the waste of downlink bandwidth, and there is no need for the terminal to send an uplink message again so that the master ONU learns the device identifier of the terminal to generate a new forwarding rule, thereby reducing the delay of the terminal sending the uplink message again and the time consuming of the master ONU learning the device identifier of the terminal to generate a new forwarding rule, thereby reducing the delay required for the terminal to perform data services after roaming between slave ONUs.

The following describes the solutions of the embodiments of the present disclosure in conjunction with the accompanying drawings.

FIG2 is a schematic diagram of the structure of an FTTR system provided by an embodiment of the present disclosure. As shown in FIG2 , the FTTR system includes a master ONU 11 , an optical splitter 21 , a plurality of slave ONUs (eg, slave ONU 31 , slave ONU 32 , and slave ONU 33 ) and a terminal 41 .

The master ONU 11 is a home device, which is connected to multiple slave ONUs through an optical splitter 21 and is the main gateway of the FTTR system.

In some embodiments, the master ONU 11 includes a device management module (master), which is a logic/software node inside the master ONU 11 and is responsible for allocating ports (i.e., allocating Gemports) to each terminal accessing the FTTR network, generating a dedicated port identifier (i.e., Gemport ID), establishing a correspondence between the device identifier and the port identifier of the terminal (also referred to as a mapping relationship), and synchronously sending this correspondence to each slave ONU. At the same time, a forwarding rule between the terminal's message and the port identifier is constructed, and the forwarding rule includes a forwarding rule between a downstream message belonging to the terminal and the port identifier.

In some embodiments, the optical splitter 21 is a passive optical transmission device that connects the master ONU 11 and multiple slave ONUs.

In some embodiments, for each slave ONU among the multiple slave ONUs, the slave ONU is arranged in each room, connected to the master ONU 11 through the optical splitter 21, and is an access point of the terminal 41 in the FTTR system.

In some embodiments, the slave ONU includes a device management module (slave), which is a logical/software node inside the slave ONU and is responsible for sending the device identifier of the terminal to the device management module (master) of the master ONU when a terminal accesses the slave ONU, and constructing a forwarding rule between the uplink message of the terminal and the port identifier of the port according to the correspondence between the device identifier of the terminal and the port identifier issued by the device management module (master) of the master ONU.

In some embodiments, the device management module (master) and the device management module (slave) exchange information through protocols including but not limited to the optical network unit management and control interface (ONU management and control interface, OMCI) and the transmission control protocol (transmission control protocol, TCP), thereby achieving synchronization of the correspondence between the device identifier of the terminal and the port identifier of the port within the GPON system.

In some embodiments, the terminal 41 can access the slave ONU wirelessly. In the case of wirelessly accessing the slave ONU, the slave ONU can be accessed through a wireless local area network (WLAN).

In some embodiments, the terminal 41 may be a device with wireless transceiver function, which may be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted. The terminal 41 may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of the present disclosure do not limit the application scenarios. Sometimes the terminal It may also be called user, user equipment (UE), access terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal, mobile device, UE terminal, wireless communication equipment, UE agent or UE device, etc., but the embodiments of the present disclosure are not limited to this.

It should be understood that Fig. 2 is an exemplary structural diagram, and the number of devices included in the FTTR system shown in Fig. 2 is not limited, for example, the number of terminals is not limited. In addition, in addition to the devices shown in Fig. 1, the FTTR system shown in Fig. 2 may also include other devices, which is not limited.

Next, as shown in FIG. 3 , an embodiment of the present disclosure provides a network management method, which is applied to a master ONU. The master ONU may be the master ONU 11 shown in FIG. 2 . The method includes the following S101 - S102 .

S101. Receive port request information sent by a first slave ONU.

The port request information includes a device identifier of a first terminal connected to the first slave ONU, and the port request information is used to request allocation of a port to the first terminal, where the first slave ONU is one of a plurality of slave ONUs connected to the master ONU. Exemplarily, the port may be a Gemport, that is, the port request information is used to request allocation of a Gemport to the first terminal.

In some embodiments, when the first slave ONU detects that the first terminal is connected, the first slave ONU obtains the device identification of the first terminal, and then based on the device identification of the first terminal, queries whether it has stored a corresponding relationship related to the device identification of the first terminal. In the case that the corresponding relationship related to the device identification of the first terminal is not stored in itself, it represents that the first terminal is a terminal newly connected to the FTTR system, and the first slave ONU sends a port request message to the master ONU to request the master ONU to allocate a port to the first terminal. The device identification of the first terminal is used to uniquely indicate the first terminal, for example, it can be the MAC address of the first terminal. Then, the master ONU receives the port request information sent by the first ONU.

S102: In response to the port request information, send first indication information to multiple slave ONUs.

The first indication information is used to indicate the corresponding relationship between the device identifier of the first port and the port identifier of the target port, and the target port is a port allocated by the master ONU to the first terminal.

In some embodiments, the master ONU may allocate a port to the first terminal in the following situations.

Case 1: The master ONU has at least one unassigned port.

In some embodiments, the master ONU may include multiple ports. After receiving the port request information, the master ONU may query whether there is at least one unallocated port among its multiple ports. When there is at least one unallocated port among its multiple ports, the master ONU may allocate a port to the first terminal from the at least one unallocated port.

As an example, the master ONU may randomly select a port from at least one unallocated port and allocate it to the first terminal, that is, the target port is one of the at least one unallocated port.

Case 2: The master ONU does not have at least one unassigned port.

It should be understood that the master ONU does not have at least one unallocated port, which means that multiple ports of the master ONU have been allocated. The master ONU can allocate a port to the first port from the allocated ports.

As an example, the master ONU may allocate the earliest allocated port among the allocated ports to the first terminal, that is, the target port is the earliest allocated port among the allocated ports.

As another example, the master ONU may also randomly select a port from the allocated ports and allocate it to the first terminal, that is, the target port is one of the allocated ports.

After determining the target port, the master ONU sends first indication information to the multiple slave ONUs.

In some embodiments, when the master ONU does not have at least one unallocated port, the master ONU may also send a prompt message to the first slave ONU to prompt that the master ONU does not have at least one unallocated port and cannot allocate a port to the first terminal. After receiving the prompt message, the first slave ONU learns that all ports of the master ONU have been allocated, and the first slave ONU actively disconnects from the first terminal.

It should be understood that when the master ONU does not have at least one unassigned port, the master ONU sends a prompt message to the first slave ONU, which can ensure that when a terminal exceeding the access capacity of the FTTR system accesses the FTTR system, it will not affect the terminals that have already accessed the FTTR system. Normal use.

Based on the embodiment shown in FIG3 , after the terminal accesses a slave ONU, the slave ONU sends a port request message to the master ONU to request the master ONU to allocate a port to the terminal, that is, to allocate a Gemport to the terminal. After the master ONU allocates a target port to the terminal, it establishes a correspondence between the port identifier of the target port and the device identifier of the terminal, that is, it generates a forwarding rule for the data service belonging to the terminal for the terminal, and then broadcasts the correspondence between the port identifier of the target port and the device identifier of the terminal to all slave ONUs, so that when the terminal roams from the currently accessed slave ONU to other slave ONUs, other slave ONUs can enable the corresponding target port based on the correspondence between the port identifier of the received target port and the device identifier of the terminal, and can correctly forward the downlink message belonging to the terminal, thereby reducing the waste of downlink bandwidth, and there is no need for the terminal to send an uplink message again so that the master ONU learns the device identifier of the terminal to generate a new forwarding rule, thereby reducing the delay of the terminal sending the uplink message again and the time consuming of the master ONU learning the device identifier of the terminal to generate a new forwarding rule, thereby reducing the delay required for the terminal to perform data services after roaming between slave ONUs.

In some embodiments, as shown in FIG. 4 , the method further includes the following S201 .

S201: If no message from a first terminal is received within a preset time period, a corresponding relationship related to a device identifier of the first terminal is deleted, and second indication information is sent to a plurality of slave ONUs.

The second indication information is used to instruct to delete the corresponding relationship related to the device identification of the first terminal from the ONU, and the preset time length may be preset by a network administrator, for example, the preset time length is 10 minutes.

In some embodiments, the preset duration may also be called by other names, for example, the preset duration may also be called aging duration.

It should be understood that if no message is received from the first terminal within the preset time period, it means that the first terminal may have left the coverage of the FTTR system. In order to release the port allocated to the first terminal, the correspondence related to the device identifier of the first terminal can be deleted, and a second indication message can be sent to multiple slave ONUs to instruct the multiple slave ONUs to delete the correspondence related to the device identifier of the first terminal. In this way, the correspondence between the device identifier of the terminal stored in the master ONU and the multiple slave ONUs and the port identifier of the port is consistent.

It should be noted that the message of the first terminal may be uplink traffic sent by the first terminal.

In some embodiments, after the master ONU deletes the corresponding relationship related to the device identifier of the first terminal, it can disable the port corresponding to the device identifier of the first terminal and delete the downlink forwarding rule of the port corresponding to the device identifier of the first terminal, so that the state of the port corresponding to the device identifier of the first terminal is converted from the allocated state to the unallocated state. At this point, the resources of the port corresponding to the device identifier of the first terminal are released and can be allocated to the terminal newly connected to the FTTR system.

In some embodiments, as shown in FIG5 , an embodiment of the present disclosure provides a network management method, which is applied to a first slave ONU. The first slave ONU may be one of the multiple slave ONUs shown in FIG2 . For example, the first slave ONU may be slave ONU31. The method includes the following S301-S304.

S301: When detecting that a first terminal has accessed, obtain a device identifier of the first terminal.

In some embodiments, when the first terminal accesses the first slave ONU wirelessly (eg, WLAN), the first slave ONU detects the access of the first terminal. When the access of the first terminal is detected, the first slave ONU may obtain the device identification of the first terminal.

In some embodiments, when the first terminal accesses the first slave ONU, the first terminal actively reports its own device identification, and then the first slave ONU obtains the device identification of the first terminal.

S302: When the corresponding relationship related to the device identification of the first terminal is not stored in the master ONU, the master ONU sends port request information to the master ONU.

After the first slave ONU obtains the device identification of the first terminal, it may use the device identification of the first terminal as an index to query whether it has stored a corresponding relationship related to the device identification of the first terminal.

As an example, in the case where the corresponding relationship related to the device identification of the first terminal is not stored in the first ONU, it represents that the first terminal is a terminal newly connected to the FTTR system. In order to enable the message of the first terminal to be forwarded in the FTTR system, the first slave ONU sends a The port request information is used to request the master ONU to allocate a port to the first terminal. The port request information includes a device identifier of the first terminal.

As another example, when the first slave ONU itself stores the corresponding relationship related to the device identifier of the first terminal, representing that the first terminal is a terminal that has been connected to the FTTR system, the first slave ONU can enable the port corresponding to the device identifier of the first terminal based on the corresponding relationship related to the device identifier of the first terminal, so that the message of the first terminal can be forwarded in the FTTR system.

S303: Receive first indication information sent by the master ONU.

For the description of the first indication information, reference may be made to the above description of the first indication information in S102, which will not be repeated here.

S304: Store the correspondence between the device identifier of the first terminal and the port identifier of the target port, and enable the target port.

As an example, storing the correspondence between the device identifier of the first terminal and the port identifier of the target port may include the following situations.

Scenario 1: The corresponding relationship related to the port identifier of the target port is not stored.

It should be understood that if the corresponding relationship related to the port identifier of the target port is not stored, it means that the target port has not been allocated and can be directly allocated to the first terminal. Therefore, if the corresponding relationship related to the target port is not stored, the corresponding relationship between the device identifier of the first terminal and the port identifier of the target port is stored.

Scenario 2: The corresponding relationship related to the port identifier of the target port is stored in the device itself.

It should be understood that if the corresponding relationship related to the port identifier of the target port is stored, it means that the target port has been allocated to other terminals before. In order to avoid the situation where the port identifier of the target port has a corresponding relationship with the device identifiers of multiple terminals at the same time, which leads to the subsequent message forwarding disorder, when the corresponding relationship related to the port identifier of the target port is stored, the corresponding relationship related to the port identifier of the target port is updated to the corresponding relationship between the device identifier of the first terminal and the port identifier of the target port, so that the corresponding relationship between the device identifier of the first terminal and the port identifier of the target port is unique, thereby avoiding the situation of message forwarding disorder.

When the first slave ONU stores the correspondence between the device identifier of the first terminal and the port identifier of the target port, the first slave ONU may also enable the target port so that the message of the first terminal can be forwarded through the target port.

In some embodiments, if no message from the first terminal is received within a preset time period, the first slave ONU disables the target port.

It should be understood that if no message from the first terminal is received within a preset time period, it means that the first terminal may have left the coverage of the first slave ONU, and the first slave ONU may disable the target port to release its own bandwidth resources.

In some embodiments, when the first slave ONU detects that the first terminal is connected to the first slave ONU, the first slave ONU disables the target port according to the correspondence between the device identifier of the first terminal and the port identifier of the target port.

In some embodiments, as shown in FIG. 6 , the method further includes the following S401 - S402 .

S401. Receive second indication information sent by a master ONU.

The second indication information is used to instruct to delete the corresponding relationship related to the device identifier of the first terminal from the ONU.

S402: In response to the second indication information, delete the corresponding relationship related to the device identification of the first terminal.

As an example, after the first slave ONU receives the second indication information sent by the master ONU, in response to the second indication information, the first slave ONU uses the device identifier of the first terminal as an index, determines the corresponding relationship related to the device identifier of the first terminal, and then deletes the corresponding relationship related to the device identifier of the first terminal.

In some embodiments, after the first slave ONU deletes the corresponding relationship related to the device identifier of the first terminal, the uplink forwarding rule of the port corresponding to the device identifier of the first terminal is deleted. At this point, the resources of the port corresponding to the device identifier of the first terminal are released, that is, the state of the port corresponding to the device identifier of the first terminal is switched from an allocated state to an unallocated state, and can be allocated as a newly accessed terminal.

In some embodiments, as shown in FIG. 7 , an embodiment of the present disclosure provides a network management method, which is applied to a second slave ONU. The second slave ONU may be one of the plurality of slave ONUs shown in FIG. 2 except the first slave ONU. For example, the first slave ONU may be a slave ONU31, the second slave ONU may be slave ONU32, and the method includes the following S501-S502.

S501. Receive first indication information sent by a master ONU.

The first indication information is used to indicate the correspondence between the device identifier of the first terminal and the port identifier of the target port, the target port is a port allocated by the master ONU to the first terminal, the first terminal is a terminal connected to the first slave ONU, and the first slave ONU is one of the multiple slave ONUs except the second slave ONU.

S502: Store the correspondence between the device identifier of the first terminal and the port identifier of the target port.

Regarding the description of the correspondence between the device identifier of the first terminal stored in the second slave ONU and the port identifier of the target port, reference can be made to the description of the correspondence between the device identifier of the first terminal stored in the first slave ONU and the port identifier of the target port in S304 above, which will not be repeated here.

In some embodiments, after S502 , as shown in FIG8 , the method further includes the following S503 .

S503: When the first terminal moves from the coverage of the first slave ONU to the coverage of the second slave ONU, enable the target port according to the correspondence between the device identifier of the first terminal and the port identifier of the target port.

It should be understood that one slave ONU corresponds to one room. When the first terminal moves from the room where the first slave ONU is located to the room where the second slave ONU is located, it means that the first terminal moves from the coverage range of the first slave ONU to the coverage range of the second slave ONU. The first terminal disconnects from the first slave ONU and accesses the second slave ONU. When the second slave ONU detects the access of the first terminal, it determines that the port corresponding to the first terminal is the target port according to the correspondence between the device identifier of the first terminal and the port identifier of the target port stored in itself, thereby enabling the target port, so that the uplink message of the first terminal can continue to be sent by the target port, so that the master ONU can continue to forward the downlink message belonging to the first terminal to the target port, and then the target port forwards the downlink message belonging to the first terminal to the first terminal, so that when the port corresponding to the first terminal is not switched, the uplink and downlink messages of the first terminal can be forwarded normally in the FTTR system.

Exemplarily, as shown in FIG9 , a schematic diagram of a terminal roaming to other slave ONUs is provided in an embodiment of the present disclosure. Referring to FIG9 , terminal 41 moves from the coverage of slave ONU 31 to the coverage of slave ONU 32. When slave ONU 32 detects that terminal 41 is connected, it obtains the device identification of terminal 41, and then determines that the port corresponding to terminal 41 is Gem1 according to the correspondence between the device identification of the terminal stored in itself and the port identification of the port, and then slave ONU 32 enables its own Gem1, so that the message of terminal 41 can continue to be sent by Gem1, so that the message belonging to terminal 41 can still be forwarded by master ONU 11 to Gem1, and Gem1 forwards the message belonging to terminal 41 to terminal 41.

In some embodiments, when the second slave ONU enables the target port, if no message from the first terminal is received within a preset time period, it means that the first terminal may have left the coverage of the second slave ONU, and the second slave ONU disables the target port to release its own bandwidth resources.

In some embodiments, as shown in FIG. 10 , the method further includes the following S601 - S602 .

S601. Receive second indication information sent by a master ONU.

S602: In response to the second indication information, delete the corresponding relationship related to the device identification of the first terminal.

For the description of S601-S602, reference may be made to the above description of S401-S402, which will not be repeated here.

The following describes a network management method provided by the embodiment of the present disclosure from the perspective of the interaction between the master ONU, the first slave ONU and the second slave ONU. FIG11 shows a schematic diagram of the interaction flow of a network management method provided by the embodiment of the present disclosure, as shown in FIG11 , including the following S701-S712.

S701. A first terminal accesses an FTTR network and connects to a first slave ONU.

S702: The first slave ONU senses access of the first terminal and queries whether it has stored a corresponding relationship related to the device identification of the first terminal.

It should be understood that when the device management module (slave) 1 of the first slave ONU senses the access of the first terminal, the device management module (slave) 1 queries whether it has stored a corresponding relationship related to the device identification of the first terminal. If the query fails, the following S703 is executed. If successful, enable the target port corresponding to the device identifier of the first terminal.

S703: The first slave ONU sends port request information to the master ONU.

As an example, the device management module (slave) 1 of the first slave ONU sends port request information to the device management module (master) of the master ONU, and the port request information includes the device identifier of the first terminal.

Exemplarily, the device management module (slave) 1 sends a message with sequence number ① to the device management module (master), and the content is "new Device device identification 1".

S704: The master ONU allocates a target port to the first terminal, and generates a correspondence between the port identifier of the target port and the device identifier of the first terminal.

The device management module (master) receives message ①, takes device ID 1 as input parameter, calls the mapping algorithm, obtains the port ID Gemport ID1 of an unassigned port, and then generates the corresponding relationship between device ID 1 and Gemport ID1.

S705: The master ONU sends the correspondence between the port identifier of the target port and the device identifier of the first terminal to the first slave ONU and the second slave ONU.

The device management module (master) sends a message with sequence number ② to the device management modules (slaves) 1 and 2. The content is "map device identifier 1 Gemport ID1". At the same time, the downstream forwarding rule is configured: message with device identifier 1->Gemport ID1. Accordingly, the first slave ONU and the second slave ONU receive the correspondence between the port identifier of the target port and the device identifier of the first terminal.

S706: The first slave ONU enables the target port and configures a forwarding rule.

Device management modules (slave) 1 and 2 receive message ②. Device management module (slave) 1 enables Gemport ID1, caches the correspondence between device identifier 1<->Gemport ID1, and configures the upstream forwarding rule: message of device identifier 1->Gemport ID1. Device management module (slave) 2 does not need to enable Gemport ID1. So far, the message of the first terminal can be forwarded normally in the FTTR system by slave ONU1.

S707: The first terminal roams to the second slave ONU.

After the first terminal enters the coverage area of the second slave ONU from the coverage area of the first slave ONU, the first terminal roams to the second slave ONU.

S708: The second slave ONU determines the target port according to the correspondence between the device identifier of the first terminal and the port identifier of the target port.

The second slave ONU senses the access of the first terminal, and queries the cache of the device management module (slave) 2 with the device identification 1 of the first terminal. The device management module (slave) 2 receives the correspondence of device identification 1<->Gemport ID1 issued by the device management module (master) in S705, so it is found that device identification 1 corresponds to Gemport ID1, that is, the target port is determined to be Gemport 1.

S709: The second slave ONU enables the target port.

After the second slave ONU enables the target port Gemport1, the message sent by the first terminal to the master ONU is sent out by Gemport1; for the message belonging to the first terminal, the master ONU continues to forward it to Gemport1. So far, the message of the first terminal continues to be forwarded normally in the FTTR system without Gemport ID switching.

S710: The first slave ONU senses that the first terminal is disconnected, and disables the target port.

The first slave ONU senses that the first terminal has been disconnected from itself, and according to the correspondence between the device identifier 1<->Gemport ID1 of the first terminal, it enables Gemport 1 corresponding to Gemport ID1, thereby releasing its own bandwidth resources.

In some embodiments, if the first terminal is disconnected from the FTTR system, all ONUs disable the target ports.

Exemplarily, when power is off, the network is shut down, or the first terminal leaves the network coverage of the FTTR system, the first terminal is disconnected from the FTTR system, and all ONUs disable the target port Gemport1.

S711. If no message from the first terminal is received within a preset time, the master ONU disables the target port and sends instruction information to the first slave ONU and the second slave ONU to instruct the first slave ONU and the second slave ONU to delete the correspondence between the device identifier of the first terminal and the port identifier of the target port.

In some embodiments, after a preset time, the device management module (master) does not sense the message of the first terminal, and then deletes the corresponding relationship of device identifier 1<->Gemport ID1 in the cache, disables Gemport 1, and deletes the downlink forwarding rule of Gemport ID1. And sends a sequence number ③ message to device management modules (slaves) 1 and 2; the content is "del map (delete mapping) device identifier 1 Gemport ID1".

S712: The first slave ONU and the second slave ONU delete the correspondence between the device identifier of the first terminal and the port identifier of the target port.

The device management modules (slaves) 1 and 2 receive the sequence number ③ message, delete the correspondence between device ID 1 and Gemport ID 1, and delete the uplink forwarding rule of Gemport ID 1. At this point, the resources of Gemport 1 are released and can be allocated to new terminals.

The functions of the device management module (master) and the device management module (slave) are introduced below.

The following is an example of a message list between device management modules. The message content can be transmitted by multiple protocols.

The following example uses the TCP protocol to transmit messages between device management modules, and takes the terminal's device identifier as the terminal's MAC address. A network management method provided by an embodiment of the present disclosure is illustrated by way of example.

Assume that an FTTR network is deployed in a house with three rooms. In addition to the master ONU at the entrance, a slave ONU is deployed in each room. The rooms are numbered 1-3, and the corresponding slave ONUs are also numbered 1-3.

S1. The master/slave ONU starts, and the device management module inserts a hook into the MAC learning module of the ONU. When the WLAN port learns a new MAC address or a MAC address ages, the device management module can receive a notification.

S2. After the device management module (main) is started, it listens to TCP port 18992, which is the pre-agreed device management module communication port. At the same time, Gemport ID1000-3999 is used as the dedicated Gemport ID for terminal wireless access. A bit map is allocated for these 3000 Gemport IDs. Each bit represents the usage of the Gemport ID. If bit x is set, it means that this Gemport IDx has been used by a terminal. All bits are not set in the initialization stage.

S3. After the slave ONU default gateway is UP, the device management module (slave) connects to the gateway's TCP 18992 port and establishes a link with the device management module (master) to prepare for subsequent message sending and receiving.

S4. After a period of time, a user in room 1 connects a terminal to the FTTR network via WLAN and connects to slave ONU 1. The MAC address of the terminal network card is dc:6a:e7:0d:7f:30, which is learned from the MAC learning module of ONU 1 and notified to the device management module (slave) 1.

S5. The device management module (slave) 1 queries whether it has stored the corresponding relationship related to the MAC address of the terminal, and sends the message "new Device dc:6a:e7:0d:7f:30" to the device management module (master).

S6. The device management module (master) receives the message, traverses the bit map of Gemport ID, and finds that bit 100 is not set. It then sets bit 100 and generates a mapping relationship: dc:6a:e7:0d:7f:30<->Gemport ID100, and adds the mapping relationship to its own mapping cache. It also configures the MAC-based downlink forwarding rule dc:6a:e7:0d:7f:30->Gemport ID100.

S7. The device management module (master) sends a message to each device management module (slave) connected to itself: "map dc:6a:e7:0d:7f:30 100".

S8. The device management modules (from) 1, 2, and 3 receive the message and cache the mapping relationship, and configure the uplink forwarding rule dc:6a:e7:0d:7f:30->Gemport ID100.

S9. Device management module (slave) 1 enables Gemport ID100. At this point, the terminal's messages can be forwarded through Gemport ID100.

S10. The user moves to room 2, and the user's terminal also roams to ONU 2.

S11. Learn this MAC from the MAC learning module of ONU 2 and notify the device management module (slave) 2.

S12. Device management module (slave) 2 queries its own mapping cache and finds the mapping entry: dc:6a:e7:0d:7f:30<->Gemport ID100. Then, Gemport ID100 is enabled and the terminal's message is forwarded normally.

S13. After ONU1 has not received any uplink message of dc:6a:e7:0d:7f:30 for an aging period, the MAC has aged and the information is sent to the device management module (slave) 1. Then the device management module (slave) 1 enables Gemport ID100.

S14. The user leaves the house and the random terminal is disconnected from slave ONU 2. Slave ONU 2 does not receive the uplink message of dc:6a:e7:0d:7f:30 for an aging period, and the MAC ages. The MAC is notified to the device management module (slave) 2, and then the device management module (slave) 2 de-enables Gemport ID100.

S15. The master ONU does not receive the upstream message of dc:6a:e7:0d:7f:30 within the aging time of Gemport ID100. The MAC is aged and the device management module (master) is notified. The device management module (master) then deletes the mapping relationship in the cache: dc:6a:e7:0d:7f:30<->Gemport ID100. It also sends a message to each device management module (slave) connected to itself: "del map dc:6a:e7:0d:7f:30 100", setting bit 100 in the internal bit map to 0. Delete the downstream rule: dc:6a:e7:0d:7f:30->Gemport ID100.

S16. The device management module (slave) 1-3 receives the message from the master ONU and deletes the upstream forwarding rule dc:6a:e7:0d:7f:30->Gemport ID100.

In some embodiments, after S5, the following S17-S20 may also be included.

S17, the device management module (main) receives the message, traverses the bit map of Gemport ID, and finds that bits 1-3000 are all set, indicating that the terminal has used up the Gemport ID assigned by the FTTR system. Then the device management module (main) traverses the MAC in the MAC learning table, finds the entry with the earliest timestamp, and finds that its MAC and mapping relationship are 00:0d:b6:0d:7f:00<->Gemport ID1.

S18. The device management module (master) updates the mapping relationship to dc:6a:e7:0d:7f:30<->Gemport ID1, and sends a message to each device management module (slave) connected to itself: "update map 00:0d:b6:0d:7f:00dc:6a:e7:0d:7f:30 1", and updates the downstream forwarding rules: 00:0d:b6:0d:7f:00->Gemport ID1 is dc:6a:e7:0d:7f:30->Gemport ID1.

S19, the device management module (slave) 1-3 receives the message from the master ONU, updates the mapping relationship in the cache: dc:6a:e7:0d:7f:30<->Gemport ID1, and updates the upstream forwarding rule: 00:0d:b6:0d:7f:00->Gemport ID1 is dc:6a:e7:0d:7f:30->Gemport ID1. At this time, the message of the terminal with MAC dc:6a:e7:0d:7f:30 can be forwarded normally.

S20. The device management module (slave) 1-3 checks its own MAC learning table. If there is still an entry of 00:0d:b6:0d:7f:00, it deletes this entry so that 00:0d:b6:0d:7f:00 can re-trigger the process of joining the FTTR network.

This process ensures that the latest terminals joining the FTTR network can be assigned a Gemport ID.

In some embodiments, after S5, the following S21-S23 may also be included.

S21, the device management module (master) receives the message, traverses the bit map of Gemport ID, and finds that bits 1-3000 are all set, indicating that the terminal has used up all the Gemport IDs of the FTTR system. Then the device management module (master) sends a message to the device management module (slave) 1: "mapdc:6a:e7:0d:7f:30NULL", indicating that the Gemport ID cannot be allocated to this terminal at present.

S22, the device management module (slave) 1 receives the message sent by the master ONU and actively disconnects from the terminal.

S23. The terminal disconnects and reconnects, and repeats this process until the device management module (master) has an idle Gemport ID available.

This process ensures that the access of terminals exceeding the system access capacity will not affect the normal use of the terminals that have been connected.

The above-described embodiment is described by taking the transmission of messages between the device management modules by the TCP protocol as an example, and it should be understood that since the communication between the device management modules is inside the primary PON system, it is end-to-end communication, so the message transmission can also be carried out by the OMCI bearer message between the device management modules. When using the OMCI bearer device management module to communicate messages, it is necessary to redefine the entity.

When defining an entity, you need to create a device mapping table, which includes attributes and actions.

The attributes include the management entity identification number, the MAC address of the new device, and the device mapping table. The management entity identification number indicates that this attribute uniquely identifies each instance of this management entity. The device mapping table indicates the Gemport ID bound to the MAC. Each row of the table contains the following fields: Gemport ID, action, and the MAC address of the device (Device MAC). Gemport ID indicates that the Gemport ID is also the key part of each row. Device MAC indicates that the MAC address of the terminal is bound to the Gemport ID.

The specific English includes as follows:

Device map table

Attributes

Managed entity id:This attribute uniquely identifies each instance of this managed entity.(R,Set-by-create)(mandatory)(2bytes)

(1)New Device MAC:This attribute specifies the device MAC need to be map to a Gemport ID(6bytes)

(2)Device Map table:The table is the device map that indicates the Gemport IDbind to a MAC

Each row of the table comprises the following fields:

Gemport ID:The Gemport ID,Also as key part of each row(2byte).

Action:Remove(0)or add(1)this Map(set action)(1byte).

Device MAC:The device bind to Gemport ID.(6bytes)

(R,W)(mandatory)(9*N bytes,where N is the number of device map)

Actions

Create,delete,get,get next,set

Set table;

Among them, Device map table represents the device mapping table, Attributes represents attributes, and Managed entity id represents the identity document (identity document, id) of the managed entity. "This attribute uniquely identifies each instance of this managed entity. (R, Set by create) (mandatory) (2 bytes)" means "This attribute uniquely identifies each instance of this managed entity. (R, Set by create) (mandatory) (2 bytes)". New Device MAC represents the MAC address of the new device. "The table is the device map that indicates the Gemport ID bind to a MAC" means "The table is the device mapping table, indicating the Gemport ID bound to a MAC". "Each row of the table comprises the following fields" means "Each row of the table comprises the following fields". “Gemport ID:The Gemport ID,Also as key part of each row(2byte)” means “Gemport ID is also the key part of each row(2byte)”. “Action:Remove(0)or add(1)this Map(set action)(1byte)” means “Action:Remove(0)or add(1)this Map(set action)(1byte)” means “Action:Remove(0)or add(1)this Map(set action)(1byte)”. “Device MAC:The device bind to Gemport ID.(6bytes)” means “MAC address of the terminal: the device bound to Gemport ID, (6 bytes)”. “(R,W)(mandatory)(9*N bytes,where N is the number of device map)” means “(R,W)(mandatory)(9*N bytes,where N is the number of device map)”. Actions means action, Create means create, delete means delete, get means obtain, get next means get next, set means setting, and Set table means setting table.

When OMCI is used to carry messages communicated between device management modules, the following A1-A5 may be included.

A1. When the slave ONU is connected to the master ONU, the master ONU creates an OMCI ME Device map table for the slave ONU.

A2. When the device management module (slave) needs to send sequence ① message, it writes the terminal's MAC address into the New Device MAC attribute of the Device map table, and notifies the master ONU through the OMCI attribute value change (AVC) message; after the master ONU receives the OMCI AVC message, it sends an OMCI GET message to obtain this MAC and notifies the device management module (master).

A3. When the device management module (master) needs to send sequence ② message, it sends OMCI Set Table message to set the Device map table attributes of the Device map table entity, the Gemport ID field is set to the Gemport ID mapped by the device, Action is set to 1, and Device MAC is set to the MAC address of the terminal. The OMCI of the ONU notifies the device management module (slave) of this mapping relationship.

A4. When the device management module (master) needs to send sequence ③ message, it sends OMCI Set Table message to set the Device map table attributes of the Device map table entity, the Gemport ID field is set to the Gemport ID mapped by the device, Action is set to 0, and Device MAC is set to the MAC address of the terminal. The OMCI of the ONU notifies the device management module (slave) of this mapping relationship.

A5. When the device management module (master) needs to send sequence ④ messages, it sends OMCI Set Table message to set the Device map table attributes of the Device map table entity, the Gemport ID field is set to the Gemport ID mapped by the device, Action is set to 1, Device MAC is set to the MAC address of the terminal, and the OMCI from the ONU finds that the Row key sent is repeated, performs an overwrite operation, and notifies the new and old entries to the device management module (slave).

The above mainly introduces the solution provided by the present disclosure from the perspective of the interaction between various nodes. It is understandable that in order to realize the above functions, each node, such as a terminal, includes a hardware structure and/or software module corresponding to the execution of each function. It should be easy for those skilled in the art to realize that, in combination with the algorithm steps of each example described in the embodiments disclosed in this article, the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific technical solution. Application and Design Constraints. A skilled person may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

FIG12 is a schematic diagram showing the composition of a communication device provided by an embodiment of the present disclosure. As shown in FIG12 , the communication device 30 includes a receiving unit 301 and a sending unit 302 .

The communication device 30 may be the master ONU. When the communication device 30 is used to implement the function of the master ONU in the above embodiment, each unit is specifically used to implement the following functions.

The receiving unit 301 is used to receive port request information sent by a first slave ONU, the port request information includes a device identifier of a first terminal connected to the first slave ONU, and the port request information is used to request allocation of a port for the first terminal. The first slave ONU is one of multiple slave ONUs.

The sending unit is used to send first indication information to multiple slave ONUs in response to the port request information, wherein the first indication information is used to indicate the correspondence between the device identifier of the first terminal and the port identifier of the target port, and the target port is the port allocated by the master ONU to the first terminal.

In some embodiments, when there is at least one unassigned port in the master ONU, the target port is one of the at least one unassigned port.

In some embodiments, when the master ONU does not have at least one unallocated port, the target port is the earliest allocated port among the allocated ports of the master ONU.

In some embodiments, the sending unit 302 is also used to delete the corresponding relationship related to the device identifier of the first terminal if no message is received from the first terminal within a preset time period, and send a second indication message to multiple slave ONUs, where the second indication message is used to instruct the slave ONU to delete the corresponding relationship related to the device identifier of the first terminal.

Fig. 13 is a schematic diagram showing the composition of another communication device provided by an embodiment of the present disclosure. As shown in Fig. 13, the communication device 40 includes an acquisition unit 401, a storage unit 402, and a sending unit 403. As an example, the communication device 40 may also include a processing unit 404.

The communication device 40 may be the first slave ONU. When the communication device 40 is used to implement the function of the first slave ONU in the above embodiment, each unit is specifically used to implement the following functions.

The acquisition unit 401 is configured to acquire a device identification of the first terminal when detecting that the first terminal has accessed.

The sending unit 403 is used to send port request information to the master ONU when the corresponding relationship related to the device identification of the first terminal is not stored in the sending unit 403. The port request information includes the device identification of the first terminal and is used to request allocation of a port for the first terminal.

The acquisition unit 401 is further used to receive first indication information sent by the master ONU, where the first indication information is used to indicate the correspondence between the device identifier of the first terminal and the port identifier of the target port, where the target port is the port allocated by the master ONU to the first terminal.

The storage unit 402 is used to store the correspondence between the device identifier of the first terminal and the port identifier of the target port, and enable the target port.

In some embodiments, the storage unit 402 is specifically configured to store the correspondence between the device identifier of the first terminal and the port identifier of the target port when the storage unit 402 does not store the correspondence related to the port identifier of the target port.

In some embodiments, the storage unit 402 is specifically configured to update the corresponding relationship related to the port identifier of the target port to the corresponding relationship between the device identifier of the first terminal and the port identifier of the target port when the corresponding relationship related to the port identifier of the target port is stored in the storage unit 402.

In some embodiments, the processing unit 404 is configured to disable the target port if no message from the first terminal is received within a preset time period.

In some embodiments, the acquisition unit 401 is further used to receive second indication information sent by the master ONU, where the second indication information is used to instruct the slave ONU to delete the corresponding relationship related to the device identifier of the first terminal;

The processing unit is further configured to delete the corresponding relationship related to the device identification of the first terminal in response to the second indication information.

FIG14 is a schematic diagram showing the composition of another communication device provided by an embodiment of the present disclosure. As shown in FIG14 , the communication device 50 includes a receiving unit 501 , a storage unit 502 and a processing unit 503 .

The communication device 50 may be the second slave ONU. When the communication device 50 is used to implement the function of the second slave ONU in the above embodiment, Each unit is specifically used to implement the following functions.

The receiving unit 501 is used to receive the first indication information sent by the master ONU, where the first indication information is used to indicate the correspondence between the device identifier of the first terminal and the port identifier of the target port, where the target port is the port allocated by the master ONU to the first terminal, the first terminal is a terminal connected to the first slave ONU, and the first slave ONU is one of the multiple slave ONUs except the second slave ONU.

The storage unit 502 is configured to store a correspondence between a device identifier of the first terminal and a port identifier of the target port.

In some embodiments, the storage unit 502 is specifically configured to store the correspondence between the device identifier of the first terminal and the port identifier of the target port when the storage unit 502 does not store the correspondence related to the port identifier of the target port.

In some embodiments, the storage unit 502 is specifically configured to update the corresponding relationship related to the port identifier of the target port to the corresponding relationship between the device identifier of the first terminal and the port identifier of the target port when the corresponding relationship related to the port identifier of the target port is stored in the storage unit 502.

In some embodiments, the processing unit 503 is further configured to enable the target port according to the correspondence between the device identifier of the first terminal and the port identifier of the target port when the first terminal moves from the coverage of the first slave ONU to the coverage of the second slave ONU.

In some embodiments, the processing unit 503 is further configured to disable the target port if no message from the first terminal is received within a preset time period.

In some embodiments, the receiving unit 501 is further used to receive second indication information sent by the master ONU, where the second indication information is used to instruct the slave ONU to delete the corresponding relationship related to the device identifier of the first terminal.

The processing unit 503 is further configured to delete the corresponding relationship related to the device identification of the first terminal in response to the second indication information.

It should be noted that the units in FIG. 12, FIG. 13 and FIG. 14 may also be referred to as modules, for example, the sending unit may be referred to as a sending module. In addition, in the embodiments shown in FIG. 12, FIG. 13 and FIG. 14, the names of the various units may not be the names shown in the figures, for example, the sending unit may also be referred to as a communication unit, and the receiving unit may also be referred to as a communication unit.

If the various units in FIG. 12 , FIG. 13 and FIG. 14 are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the methods of various embodiments of the present disclosure. The storage medium for storing computer software products includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc. Various media that can store program codes.

When the communication device 30, the communication device 40 or the communication device 50 implements the functions of the integrated modules in the form of hardware, the present disclosure provides a schematic diagram of the structure of a communication device. As shown in FIG15 , the communication device 60 includes: a memory 601, a processor 602, a communication interface 603, and a bus 604.

The memory 601 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store dynamic information and instructions, an electrically erasable programmable read-only memory (EEPROM), a disk storage medium or other magnetic storage devices, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

The processor 602 may be a device that implements or executes various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of the present disclosure. The processor 602 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The processor 602 may be a device that implements or executes various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of the present disclosure. The processor 602 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

The communication interface 603 is used to connect with other devices through a communication network. The communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

In some embodiments, the memory 601 may exist independently of the processor 602, and the memory 601 may be connected to the processor 602 via a bus 604 to store instructions or program codes. When the processor 602 calls and executes the instructions or program codes stored in the memory 601, the network management method provided in the embodiment of the present disclosure can be implemented.

In some embodiments, the memory 601 may also be integrated with the processor 602 .

The bus 604 may be an extended industry standard architecture (EISA) bus, etc. The bus 604 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, FIG15 only uses one thick line, but does not mean that there is only one bus or one type of bus.

Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and conciseness of the description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the base station or terminal is divided into different functional modules to complete all or part of the functions described above.

The disclosed embodiment also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be completed by computer instructions to instruct the relevant hardware, and the program can be stored in the above computer-readable storage medium. When the program is executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be an internal storage unit of the communication device of any of the above embodiments, such as a hard disk or memory of a computer device. The above computer-readable storage medium can also be an external storage device of the above communication device, such as a plug-in hard disk, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, a flash card (flash card), etc. equipped on the above communication device. Further, the above computer-readable storage medium can also include both the internal storage unit of the above base station or terminal and an external storage device. The above computer-readable storage medium is used to store the above computer program and other programs and data required by the above communication device. The above computer-readable storage medium can also be used to temporarily store data that has been output or is to be output. The above computer-readable storage medium includes a non-transitory computer-readable storage medium.

The embodiments of the present disclosure also provide a computer program product, which includes a computer program. When the computer program product is run on a computer, the computer is enabled to execute any one of the network management methods provided in the above embodiments.

Although the present disclosure is described herein in conjunction with various embodiments, in the process of implementing the claimed disclosure, those skilled in the art may understand and implement other variations of the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

Although the present disclosure has been described in conjunction with specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present disclosure. Accordingly, this specification and the drawings are merely exemplary illustrations of the present disclosure as defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present disclosure. Obviously, those skilled in the art may make various modifications and variations to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is also intended to include these modifications and variations.

The above are only specific implementation methods of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present disclosure shall be covered by the protection scope of the present disclosure.

Claims (17)

A network management method is applied to a master optical network unit (ONU), wherein the master ONU is connected to a plurality of slave ONUs, wherein the method comprises: Receiving port request information sent by a first slave ONU, the port request information including a device identifier of a first terminal connected to the first slave ONU, the port request information being used to request allocation of a port for the first terminal, the first slave ONU being one of the multiple slave ONUs; In response to the port request information, first indication information is sent to the multiple slave ONUs, wherein the first indication information is used to indicate the correspondence between the device identifier of the first terminal and the port identifier of the target port, and the target port is the port allocated by the master ONU to the first terminal. The method according to claim 1, wherein, in the case where there is at least one unallocated port in the master ONU, the target port is one of the at least one unallocated port. The method according to claim 1, wherein, when the master ONU does not have at least one unallocated port, the target port is the earliest allocated port among the allocated ports of the master ONU. The method according to any one of claims 1 to 3, further comprising: If no message from the first terminal is received within a preset time period, the corresponding relationship related to the device identifier of the first terminal is deleted, and second indication information is sent to the multiple slave ONUs, where the second indication information is used to instruct the slave ONU to delete the corresponding relationship related to the device identifier of the first terminal. A network management method is applied to a first slave optical network unit (ONU), wherein the first slave ONU is connected to a master ONU, the master ONU is connected to a plurality of slave ONUs, and the first slave ONU is one of the plurality of slave ONUs, wherein the method comprises: When detecting that a first terminal is connected, obtaining a device identification of the first terminal; In the case where the corresponding relationship related to the device identification of the first terminal is not stored in the master ONU, sending port request information to the master ONU, where the port request information includes the device identification of the first terminal, and the port request information is used to request allocation of a port for the first terminal; Receive first indication information sent by the master ONU, where the first indication information is used to indicate a correspondence between a device identifier of the first terminal and a port identifier of a target port, where the target port is a port allocated by the master ONU to the first terminal; The correspondence between the device identifier of the first terminal and the port identifier of the target port is stored, and the target port is enabled. The method according to claim 5, wherein storing the correspondence between the device identifier of the first terminal and the port identifier of the target port comprises: In the case that the corresponding relationship related to the port identifier of the target port is not stored in the device, the corresponding relationship between the device identifier of the first terminal and the port identifier of the target port is stored. The method according to claim 5, wherein storing the correspondence between the device identifier of the first terminal and the port identifier of the target port comprises: In the case where the corresponding relationship related to the port identifier of the target port is stored in the device, the corresponding relationship related to the port identifier of the target port is updated to the corresponding relationship between the device identifier of the first terminal and the port identifier of the target port. The method according to any one of claims 5 to 7, further comprising: If no message from the first terminal is received within a preset time period, the target port is disabled. The method according to any one of claims 5 to 7, further comprising: Receiving second indication information sent by the master ONU, where the second indication information is used to instruct the slave ONU to delete a corresponding relationship related to a device identifier of the first terminal; In response to the second indication information, the corresponding relationship related to the device identification of the first terminal is deleted. A network management method is applied to a second slave optical network unit (ONU), wherein the second slave ONU is connected to a master ONU, the master ONU is connected to a plurality of slave ONUs, and the second slave ONU is one of the plurality of slave ONUs, wherein the method comprises: Receive first indication information sent by the master ONU, where the first indication information is used to indicate a correspondence between a device identifier of a first terminal and a port identifier of a target port, where the target port is a port allocated by the master ONU to the first terminal, where the first terminal is a terminal connected to a first slave ONU, and where the first slave ONU is one of the multiple slave ONUs except the second slave ONU; The correspondence between the device identifier of the first terminal and the port identifier of the target port is stored. The method according to claim 10, wherein storing the correspondence between the device identifier of the first terminal and the port identifier of the target port comprises: In the case that the corresponding relationship related to the port identifier of the target port is not stored in the device, the corresponding relationship between the device identifier of the first terminal and the port identifier of the target port is stored. The method according to claim 10, wherein storing the correspondence between the device identifier of the first terminal and the port identifier of the target port comprises: In the case where the corresponding relationship related to the port identifier of the target port is stored in the device, the corresponding relationship related to the port identifier of the target port is updated to the corresponding relationship between the device identifier of the first terminal and the port identifier of the target port. The method according to any one of claims 10 to 12, further comprising: When the first terminal moves from the coverage of the first slave ONU to the coverage of the second slave ONU, the target port is enabled according to the correspondence between the device identifier of the first terminal and the port identifier of the target port. The method according to claim 13, further comprising: If no message from the first terminal is received within a preset time period, the target port is disabled. The method according to any one of claims 10 to 12, further comprising: Receiving second indication information sent by the master ONU, where the second indication information is used to instruct the slave ONU to delete a corresponding relationship related to a device identifier of the first terminal; In response to the second indication information, the corresponding relationship related to the device identification of the first terminal is deleted. A communication device, comprising: a processor and a memory; wherein The memory stores instructions executable by the processor; When the processor is configured to execute the instructions, the communication device implements the method according to any one of claims 1 to 15. A computer-readable storage medium, wherein the computer-readable storage medium comprises computer instructions, and when the computer instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 15.