WO2018196671A1 - 一种虚拟端口的管理方法及装置 - Google Patents

一种虚拟端口的管理方法及装置 Download PDF

Info

Publication number
WO2018196671A1
WO2018196671A1 PCT/CN2018/083641 CN2018083641W WO2018196671A1 WO 2018196671 A1 WO2018196671 A1 WO 2018196671A1 CN 2018083641 W CN2018083641 W CN 2018083641W WO 2018196671 A1 WO2018196671 A1 WO 2018196671A1
Authority
WO
WIPO (PCT)
Prior art keywords
port
status
state
vport
virtual
Prior art date
Application number
PCT/CN2018/083641
Other languages
English (en)
French (fr)
Inventor
李玉峰
李明生
刁渊炯
陈爱民
袁立权
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP18790772.0A priority Critical patent/EP3618351A4/en
Publication of WO2018196671A1 publication Critical patent/WO2018196671A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2863—Arrangements for combining access network resources elements, e.g. channel bonding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
    • 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/07—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems
    • H04B10/075—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal
    • H04B10/079—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal using measurements of the data signal
    • H04B10/0793—Network aspects, e.g. central monitoring of transmission parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H04L41/065—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving logical or physical relationship, e.g. grouping and hierarchies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]

Definitions

  • the present disclosure relates to the field of communications, and in particular, to a method and an apparatus for managing a virtual port.
  • FTTH Fiber to the home
  • Traditional digital subscriber line xDSL, Any Digital Subscriber Line
  • Ethernet Passive Optical Network EPON
  • GPON Gigabit-Capable Passive Optical Network
  • N-PON2 Next Generation PON Version 2
  • Ethernet related services have many problems such as high maintenance and configuration costs and difficult maintenance of business models.
  • the access network standardization organization represented by the Broadband Forum has written a new access network network slice standard document WT-370 under the initiative of operators such as Vodafone.
  • the core issues of network slicing or network sharing are as follows: 1) Different slices of three services: home wide service, enterprise service, and mobile backhaul service.
  • the VLAN space, MAC space, and IP space can overlap, and can be independently planned without affecting each other; 2) Broadband Internet access, Voice over IP (VOIP, Voice Over IP), Digital Television (IPTV, IP Television) in the home wide service can use different network slices, and the slice granularity is an Optical Network Unit (ONU) network.
  • VOIP Voice over IP
  • IPTV IP Television
  • the network slice PON layer resources are uniformly managed and configured, and the L2/L3 layer management control and forwarding resources are independent, and the slice independence degree can be flexibly configured.
  • the virtual access network consists of a Layer 2 connection (an analog Layer 2 line) and a Layer 2 switching device (vSwitch).
  • a Layer 2 connection is provided by a physical network that spans multiple devices, such as an Ethernet service flow from a UNI port of an ONU to a GEM port under the PON port of an OLT, including bandwidth and quality of service (QoS, Quality of Service). ), etc., this service flow connection traverses multiple devices such as ONU and OLT.
  • a virtual switch (VSwitch) is a logical Layer 2 switch. It can be virtualized on a single OLT in a simple scenario.
  • an embodiment of the present disclosure provides a method and an apparatus for managing a virtual port.
  • a method for managing a virtual port includes:
  • the virtual port status is updated according to the status of the physical port, and the virtual port status is synthesized by one of the following:
  • the mapping of the physical port to the virtual port includes: for one optical network unit ONU, one home unit Home Unit corresponds to one vPORT.
  • the mapping of the physical port to the virtual port includes: configuring a mapping relationship between the vPORT and the physical resource by using the resource mapping table.
  • the mapping between the physical port and the virtual port is as follows: Configuring the PON interface in the OLT view, configuring the ONU in the PON interface view, and entering the ONU view to configure the vPORT.
  • the port management status is a port enabled or closed state from an operator or an administrator.
  • the updating the virtual port status according to the status of the physical port includes one of the following or any combination thereof:
  • the default port management state is up and the vPORT state is set to the PORTUP state.
  • the link operation status is set according to the alarm reporting status of the operation status.
  • the setting the link operation status according to the alarm reporting status of the operation status includes at least one of the following:
  • the vPORT status is set to the LINKUP state
  • the virtual port status is updated according to the status of the physical port, including:
  • the virtual port status is set to DOWN;
  • the link event includes one or any combination of the following:
  • the status of the virtual port is updated according to the status of the physical port, including: when the AIS or RDI alarm occurs on the physical port, the virtual port status is set to DOWN.
  • the virtual port status is updated according to the status of the physical port, including: when the status of the GPON TC physical layer is alarmed, the virtual port status is set to DOWN.
  • the updating the virtual port status according to the status of the physical port includes one of the following or any combination thereof:
  • the vPORT state is configured as the PORTUP state.
  • the method further includes one of the following before updating the virtual port status according to the status of the physical port:
  • a virtual port management device includes:
  • the update module is configured to update the virtual port status according to the status of the physical port, and the virtual port status is synthesized by one of the following:
  • the establishing module is configured to establish a mapping of the physical port to the virtual port, including: for one optical network unit ONU, one home unit Home Unit corresponds to one vPORT.
  • the establishing module is configured to establish a mapping of the physical port to the virtual port, including: configuring a mapping relationship between the vPORT and the physical resource by using the resource mapping table.
  • the establishing module is configured to establish a mapping from a physical port to a virtual port, including: configuring a PON port in the OLT view, configuring an ONU in the PON port view, and entering the ONU view to configure the vPORT.
  • the port management status is a port enabled or closed state from an operator or an administrator.
  • the update module is configured to update the virtual port status according to the status of the physical port, including one of the following or any combination thereof:
  • the default port management state is up and the vPORT state is set to the PORTUP state.
  • the link operation status is set according to the alarm reporting status of the operation status.
  • the setting of the link operation state according to the alarm reporting situation of the operation state includes at least one of the following:
  • the vPORT status is set to the LINKUP state
  • the update module is configured to update the virtual port status according to the status of the physical port, including:
  • the virtual port status is set to DOWN;
  • the link event includes one or any combination of the following:
  • the update module is configured to update the virtual port status according to the status of the physical port, including: when the physical port generates an AIS or RDI alarm, the virtual port status is set to DOWN.
  • the update module is configured to update the virtual port status according to the status of the physical port, including: when the status of the GPON TC physical layer is alarmed, the virtual port status is set to DOWN.
  • the update module is configured to update the virtual port status according to the status of the physical port, including one of the following or any combination thereof:
  • the vPORT state is configured as the PORTUP state.
  • the update module is configured to update the virtual port status according to the status of the physical port, and further includes one of the following:
  • a virtual port management device includes:
  • a memory that stores a virtual port manager
  • a processor configured to execute the virtual port management program to perform the operations of: establishing a mapping of a physical port to a virtual port vPORT; updating a virtual port state according to a state of the physical port, the virtual port state being synthesized by one of:
  • a computer readable storage medium having a virtual port management program stored thereon, the virtual port management program being implemented by a processor to implement the steps of the virtual port management method.
  • the SDN access network operation and maintenance management requirements help to solve the practical problems of the basic operator and virtual operator's responsibility definition, network operation and maintenance management.
  • FIG. 1 is a schematic structural diagram of a multi-service bearer isolation and independent management and maintenance using network slicing in the related art
  • FIG. 2 is a schematic flowchart of a virtual port management method according to an embodiment
  • FIG. 3 is a schematic diagram of a management model of a physical port abstraction based on different access hardware platforms as a virtual port and a service flow according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram showing a relationship between a virtual port and an Eth service flow in an ITU-T G.805 model according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of an example in which a service flow enters an upstream network after being encapsulated by a GPON;
  • FIG. 6 is a schematic diagram of virtual port state synthesis in an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of an xPON alarm reporting relationship according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a virtual port management apparatus in Embodiment 2.
  • the present application aims to simplify port management of different access network platform systems (such as GPON, EPON, XDSL, etc.) by abstracting a service-oriented virtual port.
  • the virtual port can be used for the base operator-based network sharing and network slicing service for the SDN-based new access network, that is, the virtual port can be created and managed by the virtual operator. Virtual operators can improve network management efficiency by monitoring and troubleshooting network problems through status monitoring of virtual ports.
  • a method for managing a virtual port may include:
  • Step 201 Establish a mapping of a physical port to a vPORT.
  • Step 202 Update a virtual port state according to a state of the physical port, where the virtual port state is synthesized by one of the following:
  • the method for managing the virtual port in this embodiment is to establish a mapping relationship between the physical port and the virtual port and monitor and manage the state of the virtual port, thereby facilitating network resource sharing and unified management of the interface of the SDN OLT.
  • it can help solve the practical problems of basic operators and virtual operators' definition of responsibility and network operation and maintenance management.
  • the management method of the virtual port in this embodiment may be performed by using an OLT.
  • the vPORT configuration is in the ONU view.
  • the physical and state changes of the vPORT are monitored by the OLT.
  • the vPORT can be configured offline when the ONU is not online, but the VPORT relationship is indeed in the view of the ONU. But the view of the ONU is actually under the PON port, which is below the OLT. Therefore, the virtual port management method in this embodiment can be used as the total executable body by the OLT.
  • mapping of the physical port to the virtual port may include: for one optical network unit ONU, one home unit Home Unit corresponds to one vPORT.
  • the mapping of the physical port to the virtual port may include: configuring a mapping relationship between the vPORT and the physical resource by using the resource mapping table.
  • the mapping between the physical port and the virtual port may include: configuring the PON interface in the OLT view, configuring the ONU in the PON interface view, and entering the ONU view to configure the vPORT.
  • the port management status may be a port enabled or closed state from an operator or an administrator.
  • updating the virtual port status according to the status of the physical port may include one or any combination of the following: 1) After the vPORT entity is not established, the default port management status is up, vPORT status. Set to the PORTUP state; 2) From the PORTUP state of the vPORT, set the link operation status according to the alarm reporting status of the operation status.
  • the setting of the link operation status according to the alarm status of the operation status may include at least one of the following: 1) when there is no alarm, the vPORT status is set to the LINKUP state; 2) any alarm is reported, and the vPORT status is set to LINKDOWN. status.
  • updating the virtual port status according to the state of the physical port in this embodiment may include: setting the virtual port status to DOWN when the link event occurs; wherein the link event may include one of the following or Any combination:
  • updating the virtual port status according to the state of the physical port in this embodiment may include: setting the virtual port status to DOWN when the physical port generates an AIS or RDI alarm.
  • the status of the virtual port is updated according to the state of the physical port in this embodiment, and may include: when the status of the GPON TC physical layer is alarmed, the virtual port status is set to DOWN.
  • the virtual port status is updated according to the status of the physical port in the embodiment, including one of the following or any combination thereof: 1) When the port management state of the vPORT is DOWN, the vPORT status changes to the PORTDOWN state; 2) When the port management state DOWN of the vPORT is released, configure the vPORT state to the PORTUP state.
  • the method may further include: 1) adding a virtual port to a specified virtual carrier; 2) from a specified virtual The operator deletes the virtual port; 3) sets the port management status of the virtual port to UP or DOWN. In this way, operations on the virtual port, such as adding, deleting, and updating status, can be implemented while managing the virtual port.
  • Unified modeling of physical port to virtual port Establish mapping of physical port to virtual port.
  • the mapping can be one-to-one, one-to-many, and so on.
  • the division of internal resources of the OLT can be allocated according to the Eth service flow. Referring to FIG. 4 and related descriptions.
  • the mapping relationship between the physical port and the virtual port in the one-to-one case is as shown in Table 1.
  • the uplink port of the OLT is assigned to the virtual one-to-one. Operator.
  • ONU user port number OLT on the joint Virtual carrier port number ONU1 user port 1 Upper joint 1 Port 1 of Carrier 1 ONU2 user port 1 Upper joint 2 Carrier 1 port 1
  • mapping relationship between physical ports and virtual ports in a one-to-many situation is as shown in Table 2, where the uplink ports of the OLT are allocated one-to-many. Virtual carrier.
  • ONU user port number OLT on the joint Virtual carrier port number ONU1 user port 1 Upper joint 1 Port 1 of Carrier 1 ONU2 user port 1 Upper joint 1 Carrier 1 port 1
  • the forwarding planes can be distinguished by tunnel ports, such as MPLS or Virtual Extensible LAN (VXLAN) tunnels.
  • tunnel ports such as MPLS or Virtual Extensible LAN (VXLAN) tunnels.
  • the uplink ports of the OLT are two.
  • the number is the uplink port 1 and the uplink port 2
  • the two tables can be divided into two OLT virtual slices by two uplink ports. The case, and the case where one uplink port is divided into two OLT virtual slices.
  • Virtual port state synthesis for virtual operator operation and maintenance can be synthesized through port management state, operation state, and protocol state.
  • the operation state is mainly synthesized by the associated physical port state, the Ethernet Operation Administration and Maintenance (Eth OAM) state, and the Transmission Convergence Layer (TC) state.
  • Eth OAM Ethernet Operation Administration and Maintenance
  • TC Transmission Convergence Layer
  • vPORT is defined as follows: vPORT is designed to provide a virtual interface for the virtual carrier to provide Ethernet services according to the link resources.
  • the port that serves as the data forwarding represents a business unit and only focuses on the service itself. Its creation, deletion, and state modification are maintained by the VNO (virtual carrier) to which it belongs.
  • the base operator can also create and delete vPORT entities, but its operations need to be synchronized at any time in the virtual resources and physical resource mapping tables.
  • vPORT The abstraction of vPORT is to abstract the service interface of the access network. According to different physical port types of the access network, such as physical port resources PVC, GEMPORT, LLID and other resources, a virtual port focusing on Ethernet services is abstracted. According to the FTTH/FTTB access network scenario, the abstract model of vPORT is that an ONU can be divided according to the Home Unit (home unit), corresponding to a vPORT.
  • home unit home unit
  • the abstraction of the virtual port vPORT:vPORT is described in accordance with the ITU-T G.805 data model.
  • the abstraction is intended to abstract the service interface of the access network.
  • the vPORT actually represents a service unit and only focuses on the service itself.
  • the mapping relationship (TC layer) of the service Through the decoupling of the mapping relationship (TC layer) of the service, the part below the TC layer is managed by the traditional access network, thereby realizing the hierarchical separation of the service layer interface and the underlying mapping.
  • a Home Unit corresponds to a vPORT, which is divided and deployed according to the requirements of the carrier (can be divided and configured based on VLAN, VLAN+priority, or other service requirements).
  • a Home Unit corresponds to a vPORT, which is divided and deployed according to the requirements of the carrier (can be divided and configured based on VLAN, VLAN+priority, or other service requirements).
  • three access network technologies are shown: GPON, EPON, and XDSL.
  • FIG. 5 shows a data flow adaptation process for a client Ethernet service to be transmitted to an upstream optical transport network through a Gigabit-Capable Passive Optical Network (GPON) package.
  • the Eth service flow can be distinguished by the VLAN or service class (COS) in the Eth data frame.
  • COS service class
  • the Eth data stream is mapped to the port identifier (PORT ID) to form the GEMPORT data frame.
  • PORT ID port identifier
  • the ONU puts the physical ONU ID identifier on the physical layer OAM (PLOAM) according to the LOID, so as to establish the correspondence between the physical PON port and the physical ONU. relationship.
  • PLOAM physical layer OAM
  • the data frame is mapped to the OLT through the GPON port and the ODN network through the GEMPORT mapping.
  • the OLT decapsulates the Eth data stream and then converges it through the uplink port. It can enter the upstream network through the aggregation switch.
  • an ONU corresponds to a Home Unit in an FTTH application; in an FTTB application, an ONU can further serve multiple home units, so some ONUs can correspond to a virtual interface abstracted by a home unit (vPORT). ).
  • vPORT home unit
  • an ONU may be different according to the manner in which the home unit is divided, and corresponds to one vPORT.
  • the business model of the home unit can be divided and deployed based on the VLAN, VLAN+priority, etc. according to the needs of the operator.
  • the outbound interface of the route entry needs to determine the explicit physical PON layer resources.
  • Table 3 below is an example of physical PON layer resources of the outbound interface of the route entry before the vPORT is introduced.
  • the outbound interface of the route entry only needs to fill in the vPORT interface.
  • Table 4 below shows an example of the outbound interface and physical PON layer resources of the route entry after the vPORT is introduced.
  • the mapping relationship between the vPORT and the physical resource can be implemented through the resource mapping table.
  • Table 5 below is an example of the resource mapping table. The advantage of this is that the basic operator can easily allocate physical resources to different virtual operators through resource distribution, thereby implementing multi-tenant applications. vPORT only needs to pay attention to the business layer itself.
  • the virtual port operation and maintenance management model is defined as follows:
  • the virtual interface is the service interface.
  • the total interface of the ETH data stream it can be used as the QoS rate-limiting unit of the total traffic of the user.
  • the virtual port can be used as the minimum unit for user data stream MAC learning.
  • GEMPORT and Ethernet data stream are mapped, and mapped according to traffic class (TC, Traffic Class).
  • traffic class Traffic Class
  • BBF TR-156 and TR-280 such as according to priority, or according to VLAN+priority.
  • mapping refer to G.988.
  • GEMPORT corresponds to the data stream TC
  • transport container T-CONT
  • T-CONT corresponds to the PON layer TC
  • GEMPORT and T-CONT are one-to-one correspondence, refer to (BBF TR-156).
  • GEMPORT and T-CONT are managed by the base operator or the base network PON layer. Home service management of virtual interfaces, for Ethernet related services.
  • Configure the OLT, ONU, and vPORT Configure the PON port in the OLT view, enter the PON port view to configure the ONU, and enter the ONU view to configure the vPORT.
  • interface gpon-onu_1/5/1:1 where gpon-onu_1/5/1 indicates GPON port 1/5/1, and ID "1" after colon is the ONU identifier under the PON port.
  • the vPORT configuration is configured in the ONU view of the interface gpon-onu_1/5/1:1.
  • the state of a virtual port can be synthesized by the following three types of states:
  • Port management status The port from the carrier or manager is enabled and disabled.
  • a LAN-LOS alarm is sent to notify the OLT; according to the LAN-LOS signal, the operation state of the virtual interface is changed to DOWN.
  • RDI Send Remote Fault Indication
  • the port status is set to DOWN.
  • the ETH-AIS function is enabled. After the connection is interrupted, the high-level AIS is sent. After the connection is restored, the AIS is stopped. After receiving the AIS from the remote end, the local high-level alarm is reported.
  • the port status is set to DOWN.
  • the protocol BLOCK/FORWARD requires a service protocol to set, for example, a port loopback, and a BLOCK port is required. Normally it is FORWARD. Specifically increase the status, look at the needs of the business, the scope is relatively wide.
  • Link DOWN – has the relevant operational status alarms defined above.
  • the state synthesis of the link DOWN needs to refer to the above operational state and protocol state to generate an alarm.
  • the port UP-port is the management-enabled UP. It is also the default state of the system. When the system is powered on, it will be converted to other states such as link UP/link DOWN/port DOWN.
  • Port DOWN–Port is the management enable to disable the DOWN state and will override any other state.
  • the virtual port state synthesizes the state machine.
  • the standard model is a virtual port transient event message, which cannot be queried on the integrated EMS platform, but can be recorded in the system log for later analysis.
  • transient event messages include: Add: Add a virtual port to a specified virtual carrier. Delete: Remove the virtual port from a specified virtual carrier. Modify: Set the virtual port to management UP or DOWN.
  • vPORT management There are two types of vPORT management, PORTUP and PORTDOWN. There are also two types of operational status, LINKUP and LINKDOWN.
  • the default state of the vPORT is UP and the vPORT state is set to the PORTUP state.
  • the link operation status is set according to the alarm reporting status of the operation status. If there is no alarm, the vPORT status is set to the LINKUP state.
  • vPORT has the management state down.
  • any vPORT state such as PORTUP, LINKUP, LINKDOWN state
  • the administrator sets the vPORT management state down, the vPORT state will change to the PORTDOWN state.
  • the vPORT is configured to be in the PORTUP state. Then the system repeats the above state change relationship with PORTUP as the starting point.
  • the vPORT entity needs to be set to manage down first to prevent the services carried by the vPORT from being affected.
  • the vPORT can be deleted only in the PORTDOWN state.
  • the xPON alarm reporting relationship modeling is demonstrated to facilitate NETCONF/YANG management of the new SDN network.
  • the management state of the vPORT is directly associated with the vPORT virtual port state.
  • vPORT and the analog Ethernet interface are 1:1 mapping relationship.
  • the EOAM-related alarms are reported to the operating state of the vPORT through the Ethernet interface.
  • the TC layer related alarms are related to the PON port, so they are synthesized through the state of the ONU uplink port. As a synthetic source of vPORT operational status.
  • a management device for a virtual port may include:
  • the establishing module 81 is configured to establish a mapping of the physical port to the virtual port vPORT;
  • the update module 82 is configured to update the virtual port status according to the status of the physical port, where the virtual port status is synthesized by one of the following:
  • the establishing module 81 is configured to establish a physical port to a virtual port mapping, and may include: for one optical network unit ONU, one home unit Home Unit corresponds to one vPORT.
  • the establishing module 81 is configured to establish a mapping between a physical port and a virtual port, and the method includes: configuring, by using a resource mapping table, a mapping relationship between the vPORT and the physical resource.
  • the establishing module 81 is configured to establish a mapping from a physical port to a virtual port, and may include: configuring a PON port in the OLT view, entering an ONU in the PON interface view, and entering the ONU view to configure the vPORT.
  • the port management status is a port enabled or closed state from an operator or an administrator.
  • the update module 82 is configured to update the virtual port status according to the status of the physical port, including one of the following or any combination thereof:
  • the default port management state is up and the vPORT state is set to the PORTUP state.
  • the link operation status is set according to the alarm reporting status of the operation status.
  • the updating module 82 is configured to set a link operation state according to an alarm reporting situation of the operating state, at least one of the following:
  • the vPORT status is set to the LINKUP state
  • the updating module 82 is configured to update the virtual port status according to the status of the physical port, including: when the link event occurs, the virtual port status is set to DOWN; the link event includes one of the following or Any combination: error frame event; period error frame event; error frame second level summary event; link failure event; sudden death alarm event.
  • the update module 82 is configured to update the virtual port status according to the status of the physical port, including: when the physical port generates an AIS or RDI alarm, the virtual port status is set to DOWN.
  • the update module 82 is configured to update the virtual port status according to the status of the physical port, including: when the status of the GPON TC physical layer is alarmed, the virtual port status is set to DOWN.
  • the update module 82 is configured to update the virtual port status according to the status of the physical port, including one or any combination thereof: when the port management state of the vPORT is DOWN, the vPORT status changes to the PORTDOWN state; When the port management state of the vPORT is DOWN, the vPORT state is configured as the PORTUP state.
  • the method further includes: adding a virtual port to a specified virtual carrier; deleting the virtual from a specified virtual carrier. Port; sets the port management status of the virtual port to UP or DOWN.
  • the management device of the virtual port in this embodiment can implement all the details of the method in the first embodiment, and can refer to the related description of the method.
  • the management device of the virtual port in the embodiment may implement the foregoing functions and the method in the first embodiment by being disposed on an OLT or other similar device, or the management device of the virtual port in the embodiment may directly pass the OLT or the like.
  • the establishing module 81 and the updating module 82 can be implemented by software, hardware, or a combination of the two.
  • the establishing module 81 and the updating module 82 can be implemented by executing a corresponding program by a processor of the OLT. There are no restrictions on this article.
  • Another virtual port management device includes:
  • a memory that stores a virtual port manager
  • a processor configured to execute the virtual port management program to perform the operations of: establishing a mapping of a physical port to a virtual port vPORT; updating a virtual port state according to a state of the physical port, the virtual port state being synthesized by one of:
  • the management device of the virtual port in this embodiment can implement all the details of the method in the first embodiment, and can refer to the related description of the method.
  • the management device of the virtual port in the embodiment may implement the foregoing functions and the method in the first embodiment by being disposed on an OLT or other similar device, or the management device of the virtual port in the embodiment may directly pass the OLT or the like.
  • the present application further provides a computer readable storage medium having a virtual port management program stored thereon, and the virtual port management program is implemented by a processor to implement the steps of the virtual port management method.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor executes the method steps of the above embodiments according to the stored program code in the storage medium.
  • each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function.
  • This application is not limited to any specific combination of hardware and software.
  • the present disclosure is applicable to the field of communication, and is used to establish a mapping relationship between a physical port and a virtual port and monitor and manage the state of the virtual port, thereby facilitating network resource sharing and unified management of the interface of the SDN OLT.
  • it can help solve the practical problems of basic operators and virtual operators' definition of responsibility and network operation and maintenance management.

Landscapes

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

Abstract

本文公布了一种虚拟端口的管理方法及装置，包括：建立物理端口到虚拟端口vPORT的映射；根据物理端口的状态更新虚拟端口状态，所述虚拟端口状态通过端口管理状态、操作状态和协议状态进行合成。本申请便于实现SDN化OLT的网络资源共享和接口的统一管理。

Description

一种虚拟端口的管理方法及装置 技术领域
本公开涉及通信领域，具体涉及一种虚拟端口的管理方法及装置。
背景技术
随着接入网技术的成熟及“光进铜退”成为全球宽带网络建设不可阻挡的事实。光纤到户(FTTH，Fiber to the home)逐步成为网络发展的热点和网络建设的终极目标。传统各种数字用户线(xDSL，Any Digital Subscriber Line)，以太网无源光网络(EPON，Ethernet Passive Optical Network)，千兆无源光网络(GPON，Gigabit-Capable Passive Optical Network)以及未来1OG PON,下一代PON(NG-PON2，Next Generation PON Version2)需要研究面向光纤到户(FTTH，Fiber to the home)的管理模型，从而简化传统接入网的运营管理，面向用户业务，为用户提供更好、更灵活的服务。
在接入网的不同发展阶段，引入了不同的接入网设备，造成各种物理端口和与之相关的业务配置模型繁杂，不便于维护。尤其是以太网的相关业务，存在着维护配置成本较高、业务模型维护困难等诸多问题。
如图1所示，在传统接入网络面向软件定义网络(SDN，Software Defined Network)/网络功能虚拟化(NFV)新型接入网转型之际，有运营商提出采用光线路终端(OLT，optical line terminal)网络切片来解决多业务承载隔离和独立管理维护的问题。
以BBF宽带论坛(BroadBand Forum)为代表的接入网标准化组织，在沃达丰等运营商的倡导下撰写了新型接入网网络切片标准文档WT-370。其网络切片或网络共享的核心问题如下：1)家宽业务、企业业务、移动回程业务这三种业务的不同切片，VLAN空间、MAC空间和IP空间可以重叠，可以独立规划而不相互影响；2)家宽业务中的宽带上网、语音IP服务(VOIP，Voice Over IP)、数字电视(IPTV，IP Television)可以采用不同的网络切片，切片粒度是光网络单元(ONU，Optical Network Unit)网络唯一标识(UNI，Unique Network Identifier)口、千兆无源光网络封装端口(GEMPORT，GPON Encapsulation Method Port)/永久虚电路(LLID，Logic Link Identifier)、或虚拟端口(vPORT，Virtual Port)，这些网络切片PON层资源统一管理和配置，L2/L3层管理控制和转发资源独立，切片独立程度可以灵活配置。
接入网络虚拟化在一个物理网络上按需快速构建一个或多个逻辑上的虚拟接入网。虚拟接入网络由二层连接(模拟二层线路)和二层交换设备(vSwitch)组成。二层连接由跨多个设备的物理网络提供，比如从一个ONU的某个UNI口到一个OLT的PON口下的一个GEMPORT的一条以太网业务流，包括带宽、业务质量(QoS，Quality of Service)等配置，这条业务流连接穿越了ONU、OLT等多个设备。虚拟交换机(vSwitch，Virtual Switch)是逻辑上的二层交换机，简单的场景下可以在单台OLT上虚拟化实现。
由上可知，迫切需要将接入网络中各种纷杂的硬件平台进行统一端口运维管理，实现面向基础运营商管理的ONU UNI物理端口和面向虚拟运营商管理的业务虚拟端口之间的统一建模，以便满足未来新型SDN接入网运维管理需求。
发明内容
为了解决上述技术问题，本公开实施例提供了一种虚拟端口的管理方法及装置。
本申请提供了如下技术方案：
一种虚拟端口的管理方法，包括：
建立物理端口到虚拟端口vPORT的映射；
根据物理端口的状态更新虚拟端口状态，所述虚拟端口状态通过如下之一进行合成：
端口管理状态和操作状态；
端口管理状态、操作状态和协议状态。
其中，所述建立物理端口到虚拟端口的映射，包括：针对一个光网络单元ONU，一个家庭单元Home Unit对应一个vPORT。
其中，所述建立物理端口到虚拟端口的映射，包括：通过资源映射表配置vPORT和物理资源的映射关系。
其中，所述建立物理端口到虚拟端口的映射，包括：在OLT视图下配置PON口，进入PON口视图配置ONU，进入ONU视图配置vPORT。
其中，所述端口管理状态为来自运营商或管理者的端口使能、关闭状态。
其中，所述根据物理端口的状态更新虚拟端口状态，包括如下之一或其任意组合：
从没有vPORT实体到建立vPORT后，默认端口管理状态为up，vPORT状态置为PORTUP状态；
从vPORT的PORTUP状态，根据操作状态的告警上报情况设置链路操作状态。
其中，所述根据操作状态的告警上报情况设置链路操作状态至少包括如下之一：
没有任何告警时，vPORT状态置为LINKUP状态；
有任何一个告警上报，vPORT状态置为LINKDOWN状态。
其中，根据物理端口的状态更新虚拟端口状态，包括：
在链路事件发生时，虚拟端口状态设置为DOWN；
所述链路事件包括如下之一或其任意组合：
错误帧事件；
期间错误帧事件；
错误帧秒级汇总事件；
链路故障事件；
濒死告警事件。
其中，根据物理端口的状态更新虚拟端口状态，包括：在物理端口发生AIS、RDI告警时，虚拟端口状态设置为DOWN。
其中，根据物理端口的状态更新虚拟端口状态，包括：GPON TC物理层的状态告警时，虚拟端口状态设置为DOWN。
其中，所述根据物理端口的状态更新虚拟端口状态，包括如下之一或其任意组合：
在vPORT的端口管理状态DOWN时，vPORT状态会变为PORTDOWN状态；
在vPORT的端口管理状态DOWN解除时，配置vPORT状态为PORTUP状态。
其中，所述根据物理端口的状态更新虚拟端口状态之前，还包括如下之一：
添加虚拟端口到一个指定的虚拟运营商；
从一个指定的虚拟运营商删除虚拟端口；
将虚拟端口的端口管理状态置为UP或者DOWN。
一种虚拟端口的管理装置，包括：
建立模块，设置为建立物理端口到虚拟端口vPORT的映射；
更新模块，设置为根据物理端口的状态更新虚拟端口状态，所述虚拟端口状态通过如下之一进行合成：
端口管理状态和操作状态；
端口管理状态、操作状态和协议状态。
其中，所述建立模块设置为建立物理端口到虚拟端口的映射，包括：针对一个光网络单元ONU，一个家庭单元Home Unit对应一个vPORT。
其中，所述建立模块设置为建立物理端口到虚拟端口的映射，包括：通过资源映射表配置vPORT和物理资源的映射关系。
其中，所述建立模块设置为建立物理端口到虚拟端口的映射，包括：在OLT视图下配置PON口，进入PON口视图配置ONU，进入ONU视图配置vPORT。
其中，所述端口管理状态为来自运营商或管理者的端口使能、关闭状态。
其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态，包括如下之一或其任意组合：
从没有vPORT实体到建立vPORT后，默认端口管理状态为up，vPORT状态置为PORTUP状态；
从vPORT的PORTUP状态，根据操作状态的告警上报情况设置链路操作状态。
其中，所述更新模块设置为根据操作状态的告警上报情况设置链路操作状态至少包括如下之一：
没有任何告警时，vPORT状态置为LINKUP状态；
有任何一个告警上报，vPORT状态置为LINKDOWN状态。
其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态，包括：
在链路事件发生时，虚拟端口状态设置为DOWN；
所述链路事件包括如下之一或其任意组合：
错误帧事件；
期间错误帧事件；
错误帧秒级汇总事件；
链路故障事件；
濒死告警事件。
其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态，包括：在物理端口发生AIS、RDI告警时，虚拟端口状态设置为DOWN。
其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态，包括：GPON TC物理层的状态告警时，虚拟端口状态设置为DOWN。
其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态，包括如下之一或其任意组合：
在vPORT的端口管理状态DOWN时，vPORT状态会变为PORTDOWN状态；
在vPORT的端口管理状态DOWN解除时，配置vPORT状态为PORTUP状态。
其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态之前，还包括如下之一：
添加虚拟端口到一个指定的虚拟运营商；
从一个指定的虚拟运营商删除虚拟端口；
将虚拟端口的端口管理状态置为UP或者DOWN。
一种虚拟端口的管理装置，包括：
存储有虚拟端口管理程序的存储器；
处理器，配置为执行所述虚拟端口管理程序以执行下述操作：建立物理端口到虚拟端口vPORT的映射；根据物理端口的状态更新虚拟端口状态，所述虚拟端口状态通过如下之一进行合成：
端口管理状态和操作状态；
端口管理状态、操作状态和协议状态。
一种计算机可读存储介质，所述计算机可读存储介质上存储有虚拟端口管理程序，所述虚拟端口管理程序被处理器执行时实现所述的虚拟端口管理方法的步骤。
本公开实施例中，通过在物理端口和虚拟端口之间建立映射关系并针对虚拟端口的状态进行监控、管理，便于实现SDN化OLT的网络资源共享和接口的统一管理，一方面可以满足未来新型SDN接入网运维管理需求，另一方面有助于解决基础运营商和虚拟运营商的责任界定、网络运维管理等现实问题。
本公开的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本公开而了解。本公开的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本公开技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本公开的技术方案，并不构成对本公开技术方案的限制。
图1为相关技术中利用网络切片解决多业务承载隔离和独立管理维护的架构示意图；
图2为实施例一种虚拟端口管理方法的流程示意图；
图3为本公开实施例基于不同接入硬件平台的物理端口抽象为虚拟端口和业务流的管理模型示意图；
图4为本公开实施例中ITU-T G.805模型描述虚拟端口和Eth业务流之间关系的示意图；
图5为业务流从GPON接入经过封装后进入上游网络的实例的示意图；
图6为本公开实施例中虚拟端口状态合成的示意图；
图7为本公开实施例中xPON告警上报关系的示意图。图8为实施例二中虚拟端口管理装置的结构示意图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚明白，下文中将结合附图对本公开的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
本申请，旨在通过抽象出一种面向业务的虚拟端口，从而简化不同接入网平台系统(如GPON,EPON,XDSL等)的端口管理。此外，虚拟端口可以用于面向SDN化新型接入网络的基于基础运营商的网络共享、网络切片服务，即虚拟端口可以由虚拟运营商创建和管理。虚拟运营商可通过虚拟端口的状态监测来定位、排查网络问题，从而提高网络管理的效率。
实施例一
一种虚拟端口的管理方法，如图2所示，可以包括：
步骤201，建立物理端口到vPORT的映射；
步骤202，根据物理端口的状态更新虚拟端口状态，所述虚拟端口状态通过如下之一进行合成：
端口管理状态和操作状态；
端口管理状态、操作状态和协议状态。
本实施例虚拟端口的管理方法，通过在物理端口和虚拟端口之间建立映射关系并针对虚拟端口的状态进行监控、管理，便于实现SDN化OLT的网络资源共享和接口的统一管理，一方面可以满足未来新型SDN接入网运维管理需求，另一方面有助于解决基础运营商和虚拟运营商的责任界定、网络运维管理等现实问题。
实际应用中，本实施例中虚拟端口的管理方法可以通过OLT来执行。虽然如下描述，vPORT配置是在ONU视图下。但是vPORT的实体和状态变化都是有OLT来监控，在ONU没有上线时可以通过离线方式配置vPORT，只不过VPORT的关系确实是在ONU的视图下。但是ONU的视图其实也是在PON口下，也就是OLT下面。因此，本实施例中虚拟端口管 理方法可以OLT作为总的执行体。
一种实现方式中，所述建立物理端口到虚拟端口的映射，可以包括：针对一个光网络单元ONU，一个家庭单元Home Unit对应一个vPORT。
一种实现方式中，所述建立物理端口到虚拟端口的映射，可以包括：通过资源映射表配置vPORT和物理资源的映射关系。
一种实现方式中，所述建立物理端口到虚拟端口的映射，可以包括：在OLT视图下配置PON口，进入PON口视图配置ONU，进入ONU视图配置vPORT。
本实施例中，所述端口管理状态可以为来自运营商或管理者的端口使能、关闭状态。
一种实现方式中，本实施例中根据物理端口的状态更新虚拟端口状态，可以包括如下之一或其任意组合：1)从没有vPORT实体到建立vPORT后，默认端口管理状态为up，vPORT状态置为PORTUP状态；2)从vPORT的PORTUP状态，根据操作状态的告警上报情况设置链路操作状态。其中，所述根据操作状态的告警上报情况设置链路操作状态至少可以包括如下之一：1)没有任何告警时，vPORT状态置为LINKUP状态；2)有任何一个告警上报，vPORT状态置为LINKDOWN状态。
一种实现方式中，本实施例中根据物理端口的状态更新虚拟端口状态，可以包括：在链路事件发生时，虚拟端口状态设置为DOWN；其中，所述链路事件可以包括如下之一或其任意组合：
错误帧事件；
期间错误帧事件；
错误帧秒级汇总事件；
链路故障事件；
濒死告警事件。
一种实现方式中，本实施例中根据物理端口的状态更新虚拟端口状态，可以包括：在物理端口发生AIS、RDI告警时，虚拟端口状态设置为DOWN。
一种实现方式中，本实施例中根据物理端口的状态更新虚拟端口状态，可以包括：GPON TC物理层的状态告警时，虚拟端口状态设置为DOWN。
一种实现方式中，本实施例中所述根据物理端口的状态更新虚拟端口状态，包括如下之一或其任意组合：1)在vPORT的端口管理状态DOWN时，vPORT状态会变为PORTDOWN状态；2)在vPORT的端口管理状态DOWN解除时，配置vPORT状态为PORTUP状态。
一种实现方式中，本实施例中所述根据物理端口的状态更新虚拟端口状态之前，还可以包括如下之一：1)添加虚拟端口到一个指定的虚拟运营商；2)从一个指定的虚拟运营商删除虚拟端口；3)将虚拟端口的端口管理状态置为UP或者DOWN。如此，可以在对虚拟端口进行管理的同时实现对虚拟端口的操作，如添加、删除、更新状态等。
本实施例的上述方法可以分为两个主要部分：
1)物理端口到虚拟端口的统一建模：建立物理端口到虚拟端口的映射，该映射可以是一对一、一对多等。
实际应用中，OLT内部资源的划分可以按照Eth业务流进行分配，可参考附图4及其相关描述。
例如，针对一个OLT和两个ONU(ONU1，ONU2)的场景，一对一的情况下物理端口到虚拟端口的映射关系如下表1所示，其中OLT的上联口为一对一分配给虚拟运营商。
ONU用户口端口号 OLT上联口 虚拟运营商端口号
ONU1用户口1 上联口1 运营商1的端口1
ONU2用户口1 上联口2 运营商2的端口1
表1
再例如，针对一个OLT和两个ONU(ONU1，ONU2)的场景，一对多的情况下物理端口到虚拟端口的映射关系如下表2所示，其中OLT的上联口为一对多分配给虚拟运营商。
ONU用户口端口号 OLT上联口 虚拟运营商端口号
ONU1用户口1 上联口1 运营商1的端口1
ONU2用户口1 上联口1 运营商2的端口1
表2
针对上联口1分配给不同的虚拟运营商，转发面可以通过隧道端口进行区分，如MPLS或虚拟可扩展局域网(VXLAN，Virtual Extensible LAN)隧道。结合图3所示场景，OLT的上联口为两个，比如编号为上联口1，上联口2，则对照上述两个表格，可以分两个上联口划分到两个OLT虚拟切片的情况，和一个上联口划分到两个OLT虚拟切片的情况。
2)面向虚拟运营商运维的虚拟端口状态合成：所述虚拟端口状态可以通过端口管理状态、操作状态和协议状态进行合成。其中，所述操作状态主要可通过关联的物理端口状态、以太网操作管理维护(Eth OAM，Ethernet Operation Administration and Maintenance)状态、传输汇聚子层(TC，Transmission convergence layer)状态进行合成。
实例1
从图3可以看出，因不同时代引入的接入网接口类型繁多，并不利于后续SDN化OLT的网络资源共享、接口的统一管理，这是当前一个突出的矛盾。此外，面向SDN的网络管理趋向采用NETCONF/YANG新型管理工具，这与传统的网管模型有着较大差距。所以，如图3所示，需要定义基于不同接入硬件平台的物理端口抽象为虚拟端口和业务流的资源管理模型。
vPORT定义如下:vPORT旨在为虚拟运营商根据链路资源提供的一个专注以太网业务的虚拟接口，作为数据转发的端口代表一个业务单位，只关注业务本身。其创建、删除、状态修改由其所属的VNO(虚拟运营商)进行维护。基础运营商也可以创建、删除vPORT实体，但其操作需要在虚拟资源和物理资源映射表中随时保持同步。
vPORT的抽象旨在抽象出接入网的业务接口，根据接入网不同物理端口类型，如物理端口资源PVC，GEMPORT，LLID等资源，抽象出一个关注以太网业务的虚拟端口。根据FTTH/FTTB接入网场景，vPORT的抽象模型为，一个ONU可以根据Home Unit(家庭单元)的划分方式不同，对应一个vPORT。
如图4所示，按照ITU-T G.805数据模型进行描述虚拟端口vPORT：vPORT的抽象旨在抽象出接入网的业务接口，vPORT实际上代表一个业务单位，只关注业务本身。通过对业务的映射关系(TC层)去耦合，TC层以下的部分由传统接入网进行管理，从而实现业务层面接口和底层映射的层次剥离。
如图4所示，一个Home Unit对应一个vPORT，按照运营商需求进行划分和部署(可基于VLAN，VLAN+优先级，或者其他业务需求进行划分和配置)。图4中分别展示了三种接入网技术：GPON,EPON,XDSL，其中，通过统一的抽象，可以看出vPORT可以完全剥离底层的TC映射或实现，抽象成只关注业务的逻辑端口。
图5展示了一个客户端以太网业务经过千兆无源光网络(GPON，Gigabit-Capable Passive Optical Network)封装传送至上游光传输网络的数据流适配流程。如图5所示，Eth业务流可以通过Eth数据帧中VLAN或业务分类(COS，Class of Service)进行区分，Eth数据流经过GEM映射打上端口身份标识(PORT ID)构成GEMPORT数据帧，OLT侧会根据逻辑ONU ID(命令行配置ONU时候的ONU ID)和上线后ONU根据LOID在物理层OAM管理(PLOAM，Physical layer OAM)打上物理ONU ID标识，从而在物理PON口建立和实体ONU的对应关系。数据帧经过GEMPORT映射通过GPON端口和ODN网络到达OLT。OLT解封装Eth数据流可以经过汇聚出上联口，可经过汇聚交换机，进入上游网络。
关注以太网业务层与GPON数据封装层的隔离点，目标是抽象出以太网的业务层面。图5中，在FTTH应用中一个ONU对应一个家庭单元(Home Unit)；在FTTB应用中一个ONU可以进一步服务多个家庭单元，所以有的ONU可以对应一个家庭单元抽象而成的虚拟接口(vPORT)。具体的，一个ONU可以根据家庭单元的划分方式不同，对应一个vPORT。家庭单元的业务模型按照运营商需求，可基于VLAN、VLAN+优先级等进行划分和部署。
引入vPORT之前，路由条目的出接口需要确定明确的物理PON层资源。如下表3为引入vPORT之前路由条目的出接口的物理PON层资源示例。
目的IP 目的IP掩码 出接口 COST值
2.2.2.2 255.255.255.0 gpon-onu_1/5/1_GEMPORT10 10
表3
引入vPORT之后，路由条目的出接口只需要填写vPORT接口，如下表4为引入vPORT之后路由条目的出接口与物理PON层资源示例。vPORT和物理资源的映射关系可通过资源映射表实现，如下表5为资源映射表的示例。这样做的好处是，基础运营商可以比较容易通过资源分发的方式，把物理资源划分给不同的虚拟运营商，从而实现多租户的应用。vPORT只需要关注业务层自身。
目的IP 目的IP掩码 出接口 COST值
2.2.2.2 255.255.255.0 vport1 10
表4
vPORT 物理接口资源
vPORT1 GEMPORT10
vPORT2 GEMPORT11,12,13
vPORT3 GEMPORT14
表5
其中，虚拟端口的运维管理模型定义如下：
1)QoS模型中，虚拟接口因为是业务接口，作为ETH数据流的总接口，可以作为用户总流量的QoS限速单位。
2)虚拟端口可作为用户数据流MAC学习的最小单位。
3)GEMPORT和以太网数据流(ETH FLOW)进行映射，根据流量等级(TC，Traffic Class)进行映射，具体可参考BBF TR-156和TR-280，如按照优先级、或按照VLAN+优先级等进行映射，参考G.988。
4)GEMPORT对应数据流TC，传输容器(T-CONT)对应PON层TC。GEMPORT和T-CONT一比一对应，可参考(BBF TR-156)。GEMPORT和T-CONT由基础运营商管理或基础网络PON层管理。虚拟接口的归属业务管理，面向以太网相关的服务。
5)OLT、ONU和vPORT的配置关系:在OLT视图下配置PON口，进入PON口视图配置ONU，进入ONU视图配置vPORT。例如，interface gpon-onu_1/5/1：1，其中gpon-onu_1/5/1表示GPON口1/5/1,冒号后的ID“1”为该PON口下的ONU标识。vPORT配置是在配置完interface gpon-onu_1/5/1：1的ONU视图下进行配置。
实例2
虚拟端口的状态可以通过如下三类状态进行合成：
1)端口管理状态：来自运营商或管理者的端口使能、关闭状态。
2)操作状态：
a)物理链路的状态，虚拟端口关联的UNI物理端口状态。
物理端口关闭(DOWN)之后，根据OMCI定义，会发送LAN-LOS告警，通知OLT；根据LAN-LOS信号，把虚拟接口的操作状态改成DOWN。
b)使能Ethernet OAM的端口的OAM相关状态告警。
B1、IEEE 802.3ah EFM功能使能，端口支持链路监控和检测。
支持一般链路事件：Errored Frame Event(错误帧事件)、Errored Frame Period Event(期间错误帧事件)、Errored Frame Seconds Summary Event(错误帧秒级汇总事件)，支持RDI(发送远端故障指示)报文，同时支持处理对端发送的远端故障指示报文，并将对端故障信息送给上层协议处理。
支持紧急链路事件：Link Fault(链路故障)、Dying Gasp(濒死告警)。
当上述事件发生，端口状态设置为DOWN。
B2、IEEE 802.1ag/Y.1731CFM功能，支持ETH CCM。
支持ETH-AIS功能，连接中断后发送高级别AIS，连接恢复后停止发送AIS，接收远端发来的AIS后，抑制本端高级别告警上报；
支持ETH-RDI功能，接收处理和发送处理RDI；
当端口发生AIS、RDI告警，端口状态设置为DOWN。
c)GPON TC物理层的状态告警：ONU(PON口级)检测到的信号：LOS、LOF、SF、SD。当端口发出这些告警，端口状态设置为DOWN。
3)协议状态。
如某个IP协议的要求对端信息才能够协议UP的状态，协议的BLOCK/FORWARD，需要业务协议来设置例如发现了端口环回，就需要BLOCK端口。正常都是FORWARD。具体增加状态，看业务的需要，范围比较宽。
针对虚拟端口状态，定义如下：
链路UP–操作状态没有任何告警，vPORT链路状态为UP，没有任何导致链路DOWN的告警。
链路DOWN–有上述定义的相关操作状态告警。链路DOWN的状态合成需要参考上述的操作状态和协议状态是否有告警产生。
端口UP–端口为管理使能UP，也是系统默认状态，当系统上电后将转换为链路UP/链路DOWN/端口DOWN等其他状态。
端口DOWN–端口为管理使能关闭DOWN状态，将覆盖其他任何状态。
如图6，虚拟端口状态合成状态机。其中，标型号的为虚拟端口瞬时事件消息，该事件在集成EMS平台不能够查询到，但可以记录在系统日志供以后分析。
这些瞬时事件消息包括：添加：添加虚拟端口到一个指定的虚拟运营商。删除：从一个指定的虚拟运营商删除虚拟端口。修改：将虚拟端口置为管理UP或者DOWN。
vPORT状态转换关系：
vPORT管理有两种类型，PORTUP和PORTDOWN。操作状态也有两种类型，LINKUP和LINKDOWN。
从没有vPORT实体到建立vPORT后，vPORT建立后默认状态为UP，vPORT状态置为PORTUP状态。
从vPORT的PORTUP状态，根据操作状态的告警上报情况设置链路操作状态。如没有任何告警，则将vPORT状态置为LINKUP状态。
从vPORT的PORTUP状态，根据操作状态的告警上报情况设置链路状态。如有任何一个告警上报，则将vPORT状态置为LINKDOWN状态。
LINKUP状态下，如有任何告警发生就置为LINKDOWN状态。反之，LINKDOWN状态下所有告警消失，则又置为LINKUP状态。
vPORT有管理状态down，在任何vPORT状态下，如PORTUP，LINKUP，LINKDOWN状态下，如果管理员设置vPORT管理状态down，则vPORT状态会变为PORTDOWN状态。
如果管理状态down解除，即配置vPORT为PORTUP状态。则系统会以PORTUP为起 点重复上述的状态变化关系。
如果要删除vPORT，则需要vPORT实体先置位管理down，防止vPORT承载的业务受到影响。只有在PORTDOWN状态下，vPORT才能删除。
如图7所示，展示了xPON告警上报关系建模，以便于应用于新型SDN网络的NETCONF/YANG管理。如图7所示，vPORT的管理状态直接跟vPORT虚拟端口状态关联。其中，vPORT与模拟的以太网接口是1:1的映射关系。EOAM相关的告警通过以太网接口上报再合成到vPORT的操作状态。TC层相关告警与PON口相关，所以通过ONU上联口的状态合成。作为vPORT操作状态的另一合成来源。
实施例二
一种虚拟端口的管理装置，如图8所示，可以包括：
建立模块81，用于建立物理端口到虚拟端口vPORT的映射；
更新模块82，用于根据物理端口的状态更新虚拟端口状态，所述虚拟端口状态通过如下之一进行合成：
端口管理状态和操作状态；
端口管理状态、操作状态和协议状态。
一种实现方式中，所述建立模块81用于建立物理端口到虚拟端口的映射，可以包括：针对一个光网络单元ONU，一个家庭单元Home Unit对应一个vPORT。
一种实现方式中，所述建立模块81用于建立物理端口到虚拟端口的映射，可以包括：通过资源映射表配置vPORT和物理资源的映射关系。
一种实现方式中，所述建立模块81用于建立物理端口到虚拟端口的映射，可以包括：在OLT视图下配置PON口，进入PON口视图配置ONU，进入ONU视图配置vPORT。
本实施例中，所述端口管理状态为来自运营商或管理者的端口使能、关闭状态。
一种实现方式中，所述更新模块82用于根据物理端口的状态更新虚拟端口状态，包括如下之一或其任意组合：
从没有vPORT实体到建立vPORT后，默认端口管理状态为up，vPORT状态置为PORTUP状态；
从vPORT的PORTUP状态，根据操作状态的告警上报情况设置链路操作状态。
一种实现方式中，所述更新模块82用于根据操作状态的告警上报情况设置链路操作状态至少包括如下之一：
没有任何告警时，vPORT状态置为LINKUP状态；
有任何一个告警上报，vPORT状态置为LINKDOWN状态。
一种实现方式中，所述更新模块82用于根据物理端口的状态更新虚拟端口状态，包括：在链路事件发生时，虚拟端口状态设置为DOWN；所述链路事件包括如下之一或其任意组合：错误帧事件；期间错误帧事件；错误帧秒级汇总事件；链路故障事件；濒死告警事件。
一种实现方式中，所述更新模块82用于根据物理端口的状态更新虚拟端口状态，包括： 在物理端口发生AIS、RDI告警时，虚拟端口状态设置为DOWN。
一种实现方式中，所述更新模块82用于根据物理端口的状态更新虚拟端口状态，包括：GPON TC物理层的状态告警时，虚拟端口状态设置为DOWN。
一种实现方式中，所述更新模块82用于根据物理端口的状态更新虚拟端口状态，包括如下之一或其任意组合：在vPORT的端口管理状态DOWN时，vPORT状态会变为PORTDOWN状态；在vPORT的端口管理状态DOWN解除时，配置vPORT状态为PORTUP状态。
一种实现方式中，所述更新模块82用于根据物理端口的状态更新虚拟端口状态之前，还包括如下之一：添加虚拟端口到一个指定的虚拟运营商；从一个指定的虚拟运营商删除虚拟端口；将虚拟端口的端口管理状态置为UP或者DOWN。
本实施例中虚拟端口的管理装置可以实现实施例一所述方法的所有细节，可参照方法的相关说明。实际应用中，本实施例中虚拟端口的管理装置可以通过设置于OLT或其他类似设备上来实现上述功能以及实施例一的方法，或者本实施例中虚拟端口的管理装置可以直接通过OLT或其他类似设备实现。
实际应用中，建立模块81、更新模块82分别可以通过软件、硬件或两者结合的方式实现。例如，建立模块81、更新模块82可以通过OLT的处理器执行相应程序来实现。对此本文不作限制。
实施例三
又一种虚拟端口的管理装置，包括：
存储有虚拟端口管理程序的存储器；
处理器，配置为执行所述虚拟端口管理程序以执行下述操作：建立物理端口到虚拟端口vPORT的映射；根据物理端口的状态更新虚拟端口状态，所述虚拟端口状态通过如下之一进行合成：
端口管理状态和操作状态；
端口管理状态、操作状态和协议状态。
本实施例中虚拟端口的管理装置可以实现实施例一所述方法的所有细节，可参照方法的相关说明。实际应用中，本实施例中虚拟端口的管理装置可以通过设置于OLT或其他类似设备上来实现上述功能以及实施例一的方法，或者本实施例中虚拟端口的管理装置可以直接通过OLT或其他类似设备实现。
此外，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有虚拟端口管理程序，所述虚拟端口管理程序被处理器执行时实现上述虚拟端口管理方法的步骤。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行上述实施例的方 法步骤。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储于存储器中的程序/指令来实现其相应功能。本申请不限制于任何特定形式的硬件和软件的结合。
以上显示和描述了本申请的基本原理和主要特征和本申请的优点。本申请不受上述实施例的限制，上述实施例和说明书中描述的只是说明本申请的原理，在不脱离本申请精神和范围的前提下，本申请还会有各种变化和改进，这些变化和改进都落入要求保护的本申请范围内。
工业实用性
本公开适用于通信领域，用以通过在物理端口和虚拟端口之间建立映射关系并针对虚拟端口的状态进行监控、管理，便于实现SDN化OLT的网络资源共享和接口的统一管理，一方面可以满足未来新型SDN接入网运维管理需求，另一方面有助于解决基础运营商和虚拟运营商的责任界定、网络运维管理等现实问题。

Claims (26)

  1. 一种虚拟端口的管理方法，包括：
    建立物理端口到虚拟端口vPORT的映射；
    根据物理端口的状态更新虚拟端口状态，所述虚拟端口状态通过如下之一进行合成：
    端口管理状态和操作状态；
    端口管理状态、操作状态和协议状态。
  2. 根据权利要求1所述的管理方法，其中，所述建立物理端口到虚拟端口的映射，包括：
    针对一个光网络单元ONU，一个家庭单元Home Unit对应一个vPORT。
  3. 根据权利要求1所述的管理方法，其中，所述建立物理端口到虚拟端口的映射，包括：
    通过资源映射表配置vPORT和物理资源的映射关系。
  4. 根据权利要求1所述的管理方法，其中，所述建立物理端口到虚拟端口的映射，包括：
    在OLT视图下配置PON口，进入PON口视图配置ONU，进入ONU视图配置vPORT。
  5. 根据权利要求1所述的管理方法，其中，
    所述端口管理状态为来自运营商或管理者的端口使能、关闭状态。
  6. 根据权利要求1所述的管理方法，其中，所述根据物理端口的状态更新虚拟端口状态，包括如下之一或其任意组合：
    从没有vPORT实体到建立vPORT后，默认端口管理状态为up，vPORT状态置为PORTUP状态；
    从vPORT的PORTUP状态，根据操作状态的告警上报情况设置链路操作状态。
  7. 根据权利要求6所述的管理方法，其中，所述根据操作状态的告警上报情况设置链路操作状态至少包括如下之一：
    没有任何告警时，vPORT状态置为LINKUP状态；
    有任何一个告警上报，vPORT状态置为LINKDOWN状态。
  8. 根据权利要求1所述的管理方法，其中，根据物理端口的状态更新虚拟端口状态，包括：
    在链路事件发生时，虚拟端口状态设置为DOWN；
    所述链路事件包括如下之一或其任意组合：
    错误帧事件；
    期间错误帧事件；
    错误帧秒级汇总事件；
    链路故障事件；
    濒死告警事件。
  9. 根据权利要求1所述的管理方法，其中，根据物理端口的状态更新虚拟端口状态，包括：
    在物理端口发生AIS、RDI告警时，虚拟端口状态设置为DOWN。
  10. 根据权利要求1所述的管理方法，其中，根据物理端口的状态更新虚拟端口状态，包括：
    GPON TC物理层的状态告警时，虚拟端口状态设置为DOWN。
  11. 根据权利要求1所述的管理方法，其中，所述根据物理端口的状态更新虚拟端口状态，包括如下之一或其任意组合：
    在vPORT的端口管理状态DOWN时，vPORT状态会变为PORTDOWN状态；
    在vPORT的端口管理状态DOWN解除时，配置vPORT状态为PORTUP状态。
  12. 根据权利要求1所述的管理方法，其中，所述根据物理端口的状态更新虚拟端口状态之前，还包括如下之一：
    添加虚拟端口到一个指定的虚拟运营商；
    从一个指定的虚拟运营商删除虚拟端口；
    将虚拟端口的端口管理状态置为UP或者DOWN。
  13. 一种虚拟端口的管理装置，包括：
    建立模块，设置为建立物理端口到虚拟端口vPORT的映射；
    更新模块，设置为根据物理端口的状态更新虚拟端口状态，所述虚拟端口状态通过如下之一进行合成：
    端口管理状态和操作状态；
    端口管理状态、操作状态和协议状态。
  14. 根据权利要求13所述的管理装置，其中，所述建立模块设置为建立物理端口到虚拟端口的映射，包括：
    针对一个光网络单元ONU，一个家庭单元Home Unit对应一个vPORT。
  15. 根据权利要求13所述的管理装置，其中，所述建立模块设置为建立物理端口到虚拟端口的映射，包括：
    通过资源映射表配置vPORT和物理资源的映射关系。
  16. 根据权利要求13所述的管理装置，其中，所述建立模块设置为建立物理端口到虚拟端口的映射，包括：
    在OLT视图下配置PON口，进入PON口视图配置ONU，进入ONU视图配置vPORT。
  17. 根据权利要求13所述的管理装置，其中，
    所述端口管理状态为来自运营商或管理者的端口使能、关闭状态。
  18. 根据权利要求13所述的管理装置，其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态，包括如下之一或其任意组合：
    从没有vPORT实体到建立vPORT后，默认端口管理状态为up，vPORT状态置为 PORTUP状态；
    从vPORT的PORTUP状态，根据操作状态的告警上报情况设置链路操作状态。
  19. 根据权利要求13所述的管理装置，其中，所述更新模块设置为根据操作状态的告警上报情况设置链路操作状态至少包括如下之一：
    没有任何告警时，vPORT状态置为LINKUP状态；
    有任何一个告警上报，vPORT状态置为LINKDOWN状态。
  20. 根据权利要求13所述的管理装置，其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态，包括：
    在链路事件发生时，虚拟端口状态设置为DOWN；
    所述链路事件包括如下之一或其任意组合：
    错误帧事件；
    期间错误帧事件；
    错误帧秒级汇总事件；
    链路故障事件；
    濒死告警事件。
  21. 根据权利要求13所述的管理装置，其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态，包括：
    在物理端口发生AIS、RDI告警时，虚拟端口状态设置为DOWN。
  22. 根据权利要求13所述的管理装置，其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态，包括：
    GPON TC物理层的状态告警时，虚拟端口状态设置为DOWN。
  23. 根据权利要求13所述的管理装置，其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态，包括如下之一或其任意组合：
    在vPORT的端口管理状态DOWN时，vPORT状态会变为PORTDOWN状态；
    在vPORT的端口管理状态DOWN解除时，配置vPORT状态为PORTUP状态。
  24. 根据权利要求13所述的管理装置，其中，所述更新模块设置为根据物理端口的状态更新虚拟端口状态之前，还包括如下之一：
    添加虚拟端口到一个指定的虚拟运营商；
    从一个指定的虚拟运营商删除虚拟端口；
    将虚拟端口的端口管理状态置为UP或者DOWN。
  25. 一种虚拟端口的管理装置，包括：
    存储有虚拟端口管理程序的存储器；
    处理器，配置为执行所述虚拟端口管理程序以执行下述操作：建立物理端口到虚拟端口vPORT的映射；根据物理端口的状态更新虚拟端口状态，所述虚拟端口状态如下之一进行合成：
    端口管理状态和操作状态；
    端口管理状态、操作状态和协议状态。
  26. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有虚拟端口管理程序，所述虚拟端口管理程序被处理器执行时实现如权利要求1至12中任一项所述的虚拟端口管理方法的步骤。
PCT/CN2018/083641 2017-04-26 2018-04-19 一种虚拟端口的管理方法及装置 WO2018196671A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP18790772.0A EP3618351A4 (en) 2017-04-26 2018-04-19 VIRTUAL PORT MANAGEMENT PROCESS AND DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710283962.6 2017-04-26
CN201710283962.6A CN108809672B (zh) 2017-04-26 2017-04-26 一种虚拟端口的管理方法及装置

Publications (1)

Publication Number Publication Date
WO2018196671A1 true WO2018196671A1 (zh) 2018-11-01

Family

ID=63919474

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/083641 WO2018196671A1 (zh) 2017-04-26 2018-04-19 一种虚拟端口的管理方法及装置

Country Status (3)

Country Link
EP (1) EP3618351A4 (zh)
CN (1) CN108809672B (zh)
WO (1) WO2018196671A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109743215A (zh) * 2019-03-05 2019-05-10 重庆邮电大学 一种多区域故障下基于灾难预测的蚁群优化虚拟网络映射方法
CN110730126A (zh) * 2019-10-22 2020-01-24 迈普通信技术股份有限公司 链路汇聚系统、数据帧的发送或接收方法及其装置
CN111954100A (zh) * 2019-05-17 2020-11-17 中兴通讯股份有限公司 一种接口升级方法、装置以及光网络单元管理方法、装置
EP4047876A4 (en) * 2019-10-21 2022-11-23 ZTE Corporation METHOD FOR ENABLING NETWORK SLOTS TO SHARE AN UPLINK PORT, DEVICE, AND STORAGE MEDIA

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11665012B2 (en) * 2017-08-11 2023-05-30 Harmonic, Inc. Virtual access hub
US20220021744A1 (en) * 2019-04-08 2022-01-20 Sterlite Technologies Limited System for continuous and integrated isolation through disparate technology implementations over fttx infrastructure
CN112152899B (zh) * 2019-06-28 2023-04-07 中兴通讯股份有限公司 一种基于网络切片的数据处理方法及装置
CN114189768A (zh) * 2020-09-14 2022-03-15 中兴通讯股份有限公司 无源光纤网络的业务管理方法、装置、光线路终端及介质
US11997026B2 (en) * 2021-03-22 2024-05-28 Nokia Solutions And Networks Oy Safe port removal
CN113259791B (zh) * 2021-07-02 2021-09-14 武汉长光科技有限公司 信息配置方法、电子设备及计算机可读存储介质
CN114244745B (zh) * 2021-12-23 2023-05-02 安徽皖通邮电股份有限公司 实现以太型设备的网元管理的方法、存储介质及设备
CN114741343B (zh) * 2022-02-28 2024-09-13 惠州华阳通用电子有限公司 一种控制器端口扩展装置及方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100322252A1 (en) * 2009-06-22 2010-12-23 Josephine Suganthi Systems and methods for handling a multi-connection protocol between a client and server traversing a multi-core system
CN102137169A (zh) * 2011-01-30 2011-07-27 华为技术有限公司 一种绑定物理网口的方法、网卡及通信系统
CN105007180A (zh) * 2015-07-02 2015-10-28 广州珠江数码集团有限公司 一种分布式ccmts管理系统及方法
CN106169982A (zh) * 2015-05-27 2016-11-30 中兴通讯股份有限公司 扩展端口的处理方法、装置及系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101299698B (zh) * 2007-04-30 2012-05-23 华为技术有限公司 通信代理的方法及装置及系统
JP5937424B2 (ja) * 2012-05-29 2016-06-22 株式会社日立製作所 通信装置及びそれを制御する方法
US9009349B2 (en) * 2013-02-08 2015-04-14 Dell Products, Lp System and method for dataplane extensibility in a flow-based switching device
CN104426731B (zh) * 2013-08-23 2018-01-12 新华三技术有限公司 一种生成树计算的方法和装置
CN103501275B (zh) * 2013-09-30 2017-04-12 杭州华三通信技术有限公司 一种邻居多链路处理方法及装置
CN104582004B (zh) * 2015-01-13 2018-04-06 成都西加云杉科技有限公司 基于sdn的wlan分层组网系统及方法
CN105721566B (zh) * 2016-01-29 2019-05-24 华为技术有限公司 一种端口重定向的方法、服务器

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100322252A1 (en) * 2009-06-22 2010-12-23 Josephine Suganthi Systems and methods for handling a multi-connection protocol between a client and server traversing a multi-core system
CN102137169A (zh) * 2011-01-30 2011-07-27 华为技术有限公司 一种绑定物理网口的方法、网卡及通信系统
CN106169982A (zh) * 2015-05-27 2016-11-30 中兴通讯股份有限公司 扩展端口的处理方法、装置及系统
CN105007180A (zh) * 2015-07-02 2015-10-28 广州珠江数码集团有限公司 一种分布式ccmts管理系统及方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3618351A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109743215A (zh) * 2019-03-05 2019-05-10 重庆邮电大学 一种多区域故障下基于灾难预测的蚁群优化虚拟网络映射方法
CN111954100A (zh) * 2019-05-17 2020-11-17 中兴通讯股份有限公司 一种接口升级方法、装置以及光网络单元管理方法、装置
CN111954100B (zh) * 2019-05-17 2023-03-24 中兴通讯股份有限公司 一种接口升级方法、装置以及光网络单元管理方法、装置
EP4047876A4 (en) * 2019-10-21 2022-11-23 ZTE Corporation METHOD FOR ENABLING NETWORK SLOTS TO SHARE AN UPLINK PORT, DEVICE, AND STORAGE MEDIA
CN110730126A (zh) * 2019-10-22 2020-01-24 迈普通信技术股份有限公司 链路汇聚系统、数据帧的发送或接收方法及其装置

Also Published As

Publication number Publication date
CN108809672B (zh) 2022-04-19
EP3618351A4 (en) 2021-01-20
EP3618351A1 (en) 2020-03-04
CN108809672A (zh) 2018-11-13

Similar Documents

Publication Publication Date Title
WO2018196671A1 (zh) 一种虚拟端口的管理方法及装置
TWI555355B (zh) 一種同軸電纜媒體轉換器及流量交換的方法
CN107294753B (zh) 一种sdn/nfv开放接入网系统及管理onu/ont的方法
US9455785B2 (en) Unified network management of hybrid fiber coaxial (HFC) network
US8818188B2 (en) Traffic generation and analysis for ONU emulation
WO2019237521A1 (zh) 一种基于onu粒度的接入网olt切片的方法及系统
US7991872B2 (en) Vertical integration of network management for ethernet and the optical transport
CN102611519B (zh) 一种对无源光网络进行链路保护的方法和装置
US8184640B2 (en) Compact virtual local area network mapper for the gigabit-passive optical network optical network management and control interface
JP2018129011A (ja) データ処理装置、基盤及びデータ出力方法
CN102480319A (zh) 一种对pon终端进行维护管理的方法
WO2011066772A1 (zh) 一种无源光网络业务的配置方法及装置
Zhang et al. Architectural design and life cycle management of network slicing for software-defined optical access networks
JP6829023B2 (ja) 通信装置、情報通知方法及びコンピュータプログラム
JP7277828B2 (ja) 設定装置及び設定方法
KR20180055645A (ko) 복수의 이기종 수동형 광네트워크를 소프트웨어 정의 네트워크에 연동하는 장치 및 방법
JP7098272B2 (ja) 通信装置、通信方法及び通信プログラム
JP7048911B2 (ja) 通信装置、情報通知方法及びコンピュータプログラム
JP7348129B2 (ja) 通信装置、情報通知方法及びコンピュータプログラム
US20240244356A1 (en) Apparatus and method for slicing resources in passive optical network systems
Zhang et al. Research on metro intelligent optical network planning and optimization
Wang et al. Automated service provisioning in hybrid fiber copper access networks
Sassi et al. Integrated management of 10G-PON network element using NETCONF and OpenFlow
Elragaiee Residential CO Re-Architected Datacenter, Services, Platforms, Architecture and Use Cases
Maricato Redes de Acesso Definidas por Software

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018790772

Country of ref document: EP

Effective date: 20191126