US10374711B2 - Communications system, method for managing communications system, and controller - Google Patents

Communications system, method for managing communications system, and controller Download PDF

Info

Publication number
US10374711B2
US10374711B2 US15/667,100 US201715667100A US10374711B2 US 10374711 B2 US10374711 B2 US 10374711B2 US 201715667100 A US201715667100 A US 201715667100A US 10374711 B2 US10374711 B2 US 10374711B2
Authority
US
United States
Prior art keywords
cmc
controller
eqam
protocol
service
Prior art date
Legal status (The legal status 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 status listed.)
Active, expires
Application number
US15/667,100
Other languages
English (en)
Other versions
US20170331554A1 (en
Inventor
Bo KE
Guangsheng WU
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of US20170331554A1 publication Critical patent/US20170331554A1/en
Assigned to HUAWEI TECHNOLOGIES CO., LTD. reassignment HUAWEI TECHNOLOGIES CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KE, BO, WU, Guangsheng
Application granted granted Critical
Publication of US10374711B2 publication Critical patent/US10374711B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • 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/25—Arrangements specific to fibre transmission
    • H04B10/2575—Radio-over-fibre, e.g. radio frequency signal modulated onto an optical carrier
    • H04B10/25751—Optical arrangements for CATV or video distribution
    • G—PHYSICS
    • G08—SIGNALLING
    • G08C—TRANSMISSION SYSTEMS FOR MEASURED VALUES, CONTROL OR SIMILAR SIGNALS
    • G08C23/00—Non-electrical signal transmission systems, e.g. optical systems
    • G08C23/04—Non-electrical signal transmission systems, e.g. optical systems using light waves, e.g. infrared
    • 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/25—Arrangements specific to fibre transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J14/00—Optical multiplex systems
    • H04J14/02—Wavelength-division multiplex systems
    • H04J14/0227—Operation, administration, maintenance or provisioning [OAMP] of WDM networks, e.g. media access, routing or wavelength allocation
    • H04J14/0228—Wavelength allocation for communications one-to-all, e.g. broadcasting wavelengths
    • H04J14/023—Wavelength allocation for communications one-to-all, e.g. broadcasting wavelengths in WDM passive optical networks [WDM-PON]
    • H04J14/0232—Wavelength allocation for communications one-to-all, e.g. broadcasting wavelengths in WDM passive optical networks [WDM-PON] for downstream transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J14/00—Optical multiplex systems
    • H04J14/02—Wavelength-division multiplex systems
    • H04J14/0227—Operation, administration, maintenance or provisioning [OAMP] of WDM networks, e.g. media access, routing or wavelength allocation
    • H04J14/0241—Wavelength allocation for communications one-to-one, e.g. unicasting wavelengths
    • H04J14/0242—Wavelength allocation for communications one-to-one, e.g. unicasting wavelengths in WDM-PON
    • H04J14/0245—Wavelength allocation for communications one-to-one, e.g. unicasting wavelengths in WDM-PON for downstream transmission, e.g. optical line terminal [OLT] to ONU
    • H04J14/0247—Sharing one wavelength for at least a group of ONUs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter
    • H04L7/0008—Synchronisation information channels, e.g. clock distribution lines
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/61—Network physical structure; Signal processing
    • H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
    • H04N21/6118—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving cable transmission, e.g. using a cable modem
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/61—Network physical structure; Signal processing
    • H04N21/6156—Network physical structure; Signal processing specially adapted to the upstream path of the transmission network
    • H04N21/6168—Network physical structure; Signal processing specially adapted to the upstream path of the transmission network involving cable transmission, e.g. using a cable modem

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a communications system, a method for managing a communications system, and a controller.
  • a conventional multiple system operator (MSO) network uses a system architecture including a front end/sub-front end, an edge equipment room, a fiber node, and a user.
  • the edge equipment room and the fiber node are connected using a point-to-point analog fiber, and the fiber node and the user are connected using a coaxial cable network in a tree topology.
  • An access network that combines a fiber and a coaxial cable is referred to as a hybrid fiber coaxial (HFC) network.
  • HFC hybrid fiber coaxial
  • An MSO provides a video service and a broadband data service for the user using the HFC network.
  • a broadband access device and a video modulation device of the HFC network are installed in the edge equipment room.
  • the broadband access device and the video modulation device modulate an Internet Protocol (IP) signal into an analog radio frequency (RF) signal and are connected to the fiber node using the analog fiber.
  • IP Internet Protocol
  • RF radio frequency
  • the fiber node converts an optical signal into an RF electrical signal, and then is connected to the user using the coaxial cable.
  • the broadband access device is a cable modem termination system (CMTS) device
  • the video modulation device is an edge quadrature amplitude modulation (EQAM) device.
  • CMTS cable modem termination system
  • EQAM edge quadrature amplitude modulation
  • a digital video broadcasting service and a video on demand (VOD) service undergo frequency mixing performed by an RF combiner at an edge equipment room, are transmitted to a fiber node using an analog fiber, converted to an electrical signal at the fiber node, and then transmitted to a user using a coaxial cable.
  • VOD video on demand
  • a conventional HFC network has shortcomings such as an insufficient broadband data access capability.
  • DOCSIS data over cable service interface specification
  • a physical layer and/or data link layer interface of a DOCSIS front-end module (for example, a CMTS device) is moved to a coverage area of a coaxial cable at a same location as a remote node.
  • DOCSIS front-end module for example, a CMTS device
  • some functions of the EQAM device are retained at a front-end device side, or all functions of the EQAM device are implemented by a remote fiber node.
  • EQAM device If some functions of the EQAM device are retained at the front-end device side, a new protocol needs to be specified between the front-end device side and the remote node, and there is a need to support a clock synchronization function and control and manage, at the remote node, the EQAM device. As a result, network deployment becomes quite complex.
  • Embodiments of the present disclosure provide a communications system, a method for managing a communications system, and a controller in order to reduce complexity of network deployment.
  • a communications system including a front-end device and a remote node device, where the front-end device is configured to manage the remote node device and transmit a service to the remote node device, where the service includes a broadband access service and a video service.
  • the remote node device includes at least one coaxial media converter (CMC), where each of the at least one CMC includes a DOCSIS front-end module that supports the broadband access service and an EQAM module that supports the video service, and the at least one CMC and the front-end device are connected using a digital fiber, and the front-end device includes a controller, where the controller is configured to manage the at least one CMC.
  • CMC coaxial media converter
  • the communications system further includes a service management platform that manages the at least one CMC according to the controller, and the controller is further configured to implement a conversion function for an interface configuration protocol between the service management platform and the at least one CMC, and implement a proxy function for a resource management protocol between the service management platform and the EQAM module.
  • the controller is further configured to obtain a first correspondence between the controller and the at least one CMC, and convert, according to the first correspondence, a first interface configuration protocol between the service management platform and the controller into a second interface configuration protocol between the controller and the at least one CMC.
  • the controller is further configured to obtain a second correspondence between the controller and at least one EQAM module corresponding to the at least one CMC, and enable, according to the second correspondence, the controller and the at least one EQAM module to perform communication according to the resource management protocol.
  • the resource management protocol includes an edge resource management interface (ERMI) protocol
  • the ERMI protocol includes an ERMI-1 registration protocol, an ERMI-2 control protocol, and an ERMI-3 control protocol
  • the ERMI-1 registration protocol is used for the service management platform to register the at least one EQAM module using the controller
  • the ERMI-2 control protocol is used for the service management platform to control the at least one EQAM module using the controller
  • the ERMI-3 control protocol is used for the service management platform to control, using the controller, at least one DOCSIS module corresponding to the at least one CMC.
  • the controller includes a logical CMC obtained after the at least one CMC is simulated, the logical CMC includes at least one logical port identity (ID), and the first correspondence includes a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one CMC.
  • the controller includes a logical EQAM module obtained after the at least one EQAM module is simulated, the logical EQAM module includes at least one logical port ID, and the second correspondence includes a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one EQAM module.
  • each CMC further includes a remote out of band (R-OOB) module and a proactive network maintenance (PNM) module.
  • R-OOB remote out of band
  • PPM proactive network maintenance
  • a method for managing a communications system includes a front-end device and a remote node device, where the front-end device is configured to manage the remote node device and transmit a service to the remote node device, where the service includes a broadband access service and a video service.
  • the remote node device includes at least one CMC, where each of the at least one CMC includes a DOCSIS front-end module that supports the broadband access service and an EQAM module that supports the video service, and the at least one CMC and the front-end device are connected using a digital fiber.
  • the front-end device includes a controller, and the method includes managing, by the controller, the at least one CMC.
  • the communications system further includes a service management platform that manages the at least one CMC according to the controller, and managing, by the controller, the at least one CMC includes implementing a conversion function for an interface configuration protocol between the service management platform and the at least one CMC, and implementing a proxy function for a resource management protocol between the service management platform and the EQAM module.
  • implementing a conversion function for an interface configuration protocol between the service management platform and the at least one CMC includes obtaining a first correspondence between the controller and the at least one CMC, and converting, according to the first correspondence, a first interface configuration protocol between the service management platform and the controller into a second interface configuration protocol between the controller and the at least one CMC.
  • implementing a proxy function for a resource management protocol between the service management platform and the EQAM module includes obtaining a second correspondence between the controller and at least one EQAM module corresponding to the at least one CMC, and enabling, according to the second correspondence, the controller and the at least one EQAM module to perform communication according to the resource management protocol.
  • the resource management protocol includes an ERMI protocol
  • the ERMI protocol includes an ERMI-1 registration protocol, an ERMI-2 control protocol, and an ERMI-3 control protocol
  • the ERMI-1 registration protocol is used for the service management platform to register the at least one EQAM module using the controller
  • the ERMI-2 control protocol is used for the service management platform to control the at least one EQAM module using the controller
  • the ERMI-3 control protocol is used for the service management platform to control, using the controller, at least one DOCSIS module corresponding to the at least one CMC.
  • the controller includes a logical CMC obtained after the at least one CMC is simulated, the logical CMC includes at least one logical port ID, and the first correspondence includes a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one CMC.
  • the controller includes a logical EQAM module obtained after the at least one EQAM module is simulated, the logical EQAM module includes at least one logical port ID, and the second correspondence includes a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one EQAM module.
  • each CMC further includes an R-OOB module and a PNM module.
  • a controller configured to manage the remote node device and transmit a service to the remote node device, where the service includes a broadband access service and a video service.
  • the remote node device includes at least one CMC, where each of the at least one CMC includes a DOCSIS front-end module that supports the broadband access service and an EQAM module that supports the video service, and the at least one CMC and the front-end device are connected using a digital fiber, and the controller includes a management unit configured to manage the at least one CMC.
  • the communications system further includes a service management platform that manages the at least one CMC according to the controller, and the management unit is further configured to implement a conversion function for an interface configuration protocol between the service management platform and the at least one CMC, and implement a proxy function for a resource management protocol between the service management platform and the EQAM module.
  • the management unit is further configured to obtain a first correspondence between the controller and the at least one CMC, and convert, according to the first correspondence, a first interface configuration protocol between the service management platform and the controller into a second interface configuration protocol between the controller and the at least one CMC.
  • the management unit is further configured to obtain a second correspondence between the controller and at least one EQAM module corresponding to the at least one CMC, and enable, according to the second correspondence, the controller and the at least one EQAM module to perform communication according to the resource management protocol.
  • the resource management protocol includes an ERMI protocol
  • the ERMI protocol includes an ERMI-1 registration protocol, an ERMI-2 control protocol, and an ERMI-3 control protocol
  • the ERMI-1 registration protocol is used for the service management platform to register the at least one EQAM module using the controller
  • the ERMI-2 control protocol is used for the service management platform to control the at least one EQAM module using the controller
  • the ERMI-3 control protocol is used for the service management platform to control, using the controller, at least one DOCSIS module corresponding to the at least one CMC.
  • the management unit includes a logical CMC obtained after the at least one CMC is simulated, the logical CMC includes at least one logical port ID, and the first correspondence includes a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one CMC.
  • the management unit includes a logical EQAM module obtained after the at least one EQAM module is simulated, the logical EQAM module includes at least one logical port ID, and the second correspondence includes a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one EQAM module.
  • each CMC further includes an R-OOB module and a PNM module.
  • the EQAM module supporting the video service and the DOCSIS front-end module configured for broadband access are disposed in a same CMC, and the CMC is controlled and managed by a same front-end controller. In this way, no new interface configuration protocol is needed between the EQAM module and the remote node, no clock synchronization is needed, and remote control and management is avoided. Therefore, complexity of network deployment can be reduced according to the present disclosure.
  • FIG. 1 is a schematic diagram of a distributed communications system architecture
  • FIG. 2 is a schematic block diagram of a communications system according to an embodiment of the present disclosure
  • FIG. 3 is a schematic block diagram of a communications system according to another embodiment of the present disclosure.
  • FIG. 4 is a schematic block diagram of CMC management according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic block diagram of EQAM management according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic block diagram of EQAM management according to another embodiment of the present disclosure.
  • FIG. 7 is a schematic flowchart of a method for managing a communications system according to an embodiment of the present disclosure
  • FIG. 8 is a schematic flowchart of a process for managing a communications system according to an embodiment of the present disclosure
  • FIG. 9 is a schematic block diagram of a controller according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic block diagram of a controller according to another embodiment of the present disclosure.
  • GSM Global System for Mobile Communications
  • CDMA Code Division Multiple Access
  • WCDMA Wideband CDMA
  • GPRS general packet radio service
  • LTE Long Term Evolution
  • FDD frequency division duplex
  • TDD Time division duplex
  • UMTS Universal Mobile Telecommunications System
  • WIMAX Worldwide Interoperability for Microwave Access
  • FIG. 1 is a schematic diagram of a distributed communications system architecture.
  • the distributed communications system architecture shown in FIG. 1 includes a front-end device side 110 , a remote node 120 , and a user side 130 .
  • the distributed communications system architecture may further include another device.
  • another device For ease of understanding and description, only devices related to the present disclosure are described in this embodiment of the present disclosure. It should further be understood that an equipment room in this embodiment of the present disclosure may be classified as a front-end device side.
  • the front-end device side 110 includes a router 111 , an optical line terminal (OLT) 112 , and an EQAM device 113 .
  • the router 111 and the OLT 112 may be connected using a Gigabit Ethernet.
  • the remote node 120 may be a fiber node.
  • the remote node 120 and the OLT 112 may be connected using a passive optical network (PON) or an Ethernet.
  • PON passive optical network
  • the remote node 120 and the user side 130 may be connected using a coaxial cable.
  • the remote node 120 and the EQAM device 113 may be connected using the PON or the Ethernet.
  • the remote node 120 may include only a physical layer interface of a CMTS device, or may include all data link layer interfaces and all physical layer interfaces of a CMTS device, or may include some data link layer interfaces and some physical layer interfaces of a CMTS device. This embodiment of the present disclosure may be applied to the three distributed system architectures.
  • a data link layer interface of the EQAM device 113 in the foregoing distributed system architecture is located in the front-end device side 110 .
  • a new interface configuration protocol is needed between the EQAM device 113 and the remote node 120 .
  • a currently used interface configuration protocol may be an upstream external physical layer interface (UEPI)/downstream external physical layer interface (DEPI) protocol or a Real-Time Transport Protocol (RTP).
  • UEPI upstream external physical layer interface
  • DEPI downstream external physical layer interface
  • RTP Real-Time Transport Protocol
  • clock synchronization is also needed between the EQAM device 113 and the remote node 120 .
  • network deployment becomes quite complex.
  • FIG. 2 is a schematic block diagram of a communications system according to an embodiment of the present disclosure.
  • the communications system shown in FIG. 2 includes a front-end device 210 and a remote node device 220 .
  • the front-end device 210 transmits a service to the remote node device 220 .
  • the service includes a broadband access service and a video service.
  • the remote node device 220 includes at least one CMC 221 .
  • Each of the at least one CMC 221 includes a DOCSIS front-end module 222 that supports the broadband access service and an EQAM module 223 that supports the video service, and the at least one CMC 221 and the front-end device 210 are connected using a digital fiber.
  • the front-end device 210 may include a controller 211 that is configured to manage the at least one CMC 221 .
  • the EQAM module 223 supporting the video service and the DOCSIS front-end module 222 configured for broadband access are disposed in the same CMC 221 , and the CMC 221 is controlled and managed by a same front-end controller.
  • the CMC 221 is controlled and managed by a same front-end controller.
  • the front-end device 210 may further include a device in an equipment room.
  • the controller 211 in this embodiment of the present disclosure may be located in the equipment room.
  • the front-end device 210 may further include another device.
  • the front-end device may further include a scrambler, a router, an RF combiner, and the like.
  • the front-end device 210 in FIG. 2 may be understood as the front-end device side 110 in FIG. 1 .
  • the remote node may be a fiber node.
  • a CMTS function and an EQAM function are integrated in a front-end device. Therefore, the fiber node performs optical-to-electrical signal conversion only.
  • the remote node device 220 may include multiple CMCs 221 , and each CMC 221 includes a DOCSIS front-end module 222 and an EQAM module 223 .
  • the front-end device 210 may transmit a service to the remote node device 220 .
  • the service may include a broadband access service and a video service.
  • the DOCSIS front-end module 222 may support the broadband access service, and the EQAM module 223 may be configured to support the video service.
  • the video service may include a digital video broadcasting service and a VOD service.
  • the DOCSIS front-end module 222 that supports the broadband access service may be a broadband access device, for example, a CMTS device.
  • the EQAM module 223 that supports the video service may be a video modulation device, for example, an EQAM device.
  • the EQAM device may include an EQAM device that is based on the digital video broadcasting service, or may include an EQAM device that is based on the VOD service.
  • Functions of the EQAM device may include Moving Picture Experts Group (MPEG) video stream processing (functions such as scrambling and video stream multiplexing), quadrature amplitude modulation, and the like.
  • MPEG Moving Picture Experts Group
  • the DOCSIS front-end module 222 may include a physical layer interface of a CMTS device, or may include all data link layer interfaces and all physical layer interfaces of a CMTS device, or may include some data link layer interfaces and some physical layer interfaces of a CMTS device. This embodiment of the present disclosure may be applied to the three distributed system architectures.
  • the DOCSIS front-end module 222 may be equivalent to the CMTS device. For ease of description, an example in which all data link layer interfaces and all physical layer interfaces are included is used in this embodiment of the present disclosure.
  • the CMC 221 may further include another module, for example, an R-OOB module and a PNM module.
  • the CMC 221 and the front-end device 210 may be connected using a digital fiber.
  • the digital fiber may include at least one of a PON or an Ethernet.
  • an EQAM device that needs to perform transmission with the remote node device 220 using an analog fiber is integrated into the remote node device 220 such that a digital fiber can be used for transmission, thereby improving transmission quality.
  • the front-end device 210 may include a controller 211 , and the controller 211 is configured to manage the at least one CMC 221 .
  • the controller 211 may manage the at least one CMC 221 , that is, the controller 211 may manage modules of the CMC 221 .
  • the controller 211 may manage the EQAM module 223 of the CMC 221 , and may also manage the DOCSIS front-end module 222 of the CMC 221 .
  • the controller may manage the at least one CMC using a software defined network (SDN) and a virtual private network (VPN).
  • SDN software defined network
  • VPN virtual private network
  • the controller 211 may simulate the at least one CMC 221 into a logical CMC.
  • Each CMC 221 may be equivalent to a port, or a board, or a remote subrack of the logical CMC. That is, the controller may be considered as a logical CMC including the at least one CMC.
  • the logical CMC is equivalent to a conventional converged cable access platform (CCAP) device.
  • the CCAP device may include the CMTS device and the EQAM device.
  • the communications system may further include a service management platform (not shown) that is configured to manage the EQAM module 223 .
  • the controller 211 may implement a conversion function for an interface configuration protocol between the service management platform and the at least one CMC 221 , and implement a proxy function for a resource management protocol between the service management platform and the EQAM module 223 .
  • the service management platform may be an operation support system (OSS), a network management system (NMS), or an edge resource manager (ERM) platform.
  • OSS operation support system
  • NMS network management system
  • ERP edge resource manager
  • an Extensible Markup Language (XML)-based network configuration (Netconf) protocol, a Simple Network Management Protocol (SNMP), or a Layer 2 management protocol (for example, a gigabit-capable PON (GPON) optical network unit (ONU) management and control interface (OMCI) protocol, an Ethernet PON (EPON) operation administration and management (OAM) protocol, or an Ethernet-based OAM protocol) may be supported between the controller 211 and the CMC 221
  • an interface configuration protocol such as a command line interface (CLI) configuration protocol, the SNMP, or the Netconf protocol may be supported between the service management platform and the controller 211 .
  • the interface configuration protocol between the service management platform and the controller 211 is converted into the interface configuration protocol between the controller 211 and the CMC 221 .
  • the interface configuration protocol between the service management platform and the controller 211 may be converted into the interface configuration protocol between the controller 211 and the CMC 221 . It should be understood that a protocol conversion method used by the controller 211 is not limited in this embodiment of the present disclosure.
  • An existing resource management protocol between the service management platform (for example, an ERM) and the EQAM module 223 may be an ERMI protocol.
  • the ERM may manage a resource of the EQAM module 223 .
  • the controller 211 in this embodiment of the present disclosure may implement a protocol proxy function, that is, perform communication between the ERM and the EQAM module 223 using the ERMI protocol. It should be understood that a method for implementing protocol proxy by the controller 223 is not limited in this embodiment of the present disclosure.
  • FIG. 3 is a schematic block diagram of a communications system according to another embodiment of the present disclosure.
  • the communications system shown in FIG. 3 includes an application layer 310 , a control layer 320 , and an infrastructure layer 330 .
  • the application layer 310 includes a first application 311 , a second application 312 , and a service management platform 313 .
  • the first application 311 may be connected to a network function virtualization orchestration (NFV Orchestration) 321
  • the second application 312 may be connected to an SDN controller 322 .
  • the NFV Orchestration 321 and the SDN controller 322 are connected to a virtual CCAP controller 323 of the control layer 320 .
  • the virtual CCAP controller 323 is the controller 211 shown in FIG. 2 of the foregoing embodiment of the present disclosure.
  • the infrastructure layer 330 may include an OLT 331 , a router 332 , a switch 333 , or another device, and may further include a remote node 334 .
  • the virtual CCAP controller 323 may communicate with the remote node 334 using an interface configuration protocol, for example, a Netconf protocol or an SNMP.
  • An interface configuration protocol such as a CLI configuration protocol, the SNMP, or the Netconf protocol, may be supported between the virtual CCAP controller 323 and the service management platform 313 .
  • the virtual CCAP controller 323 may obtain a first correspondence between the CCAP controller 323 and the at least one CMC, and convert, according to the first correspondence, a first interface configuration protocol between the service management platform 313 and the virtual CCAP controller 323 into a second interface configuration protocol between the virtual CCAP controller 323 and the at least one CMC.
  • the virtual CCAP controller 323 may simulate at least one CMC into a logical CMC, the logical CMC may include at least one logical port, and each logical port ID corresponds to a physical port ID of one CMC of the at least one CMC.
  • the first correspondence may include a one-to-one correspondence between the logical port ID of the logical CMC of the virtual CCAP controller 323 and the physical port ID of the at least one CMC.
  • FIG. 4 is a schematic block diagram of CMC management according to an embodiment of the present disclosure. As shown in FIG. 4 , an OSS/NMS 410 , a controller 420 , a CMC 430 , and an optical network device 440 are included.
  • the CMC 430 may include a DOCSIS front-end module 431 , an EQAM module 432 , an R-OOB module 433 , a PNM module 434 , an upstream module 435 , and the like.
  • the optical network device 440 may include an OLT 441 , a router 442 , or a switch 443 .
  • a management protocol between the optical network device 440 and the upstream module 435 of the CMC 430 may be the same as that in other approaches. That is, the management protocol is an original GPON OMCI protocol, an EPON OAM protocol, or an Ethernet-based OAM protocol.
  • the controller 420 may simulate multiple CMCs 430 into a logical CMC 421 .
  • the logical CMC 421 is equivalent to a CCAP device, and the CCAP device includes a CMTS module and an EQAM module.
  • Each CMC 430 may be equivalent to a port, or a board, or a remote subrack.
  • the logical CMC 421 may include multiple logical port IDs (not shown), and each logical port ID may be corresponding to a physical port ID (not shown) of the CMC 430 .
  • a method for performing protocol conversion by the controller 420 may be as follows.
  • the controller 420 receives a first message sent by the OSS/NMS 410 according to the first interface configuration protocol.
  • the first message includes an IP address of the controller 420 .
  • the controller 420 parses the first message according to the second interface configuration protocol, and generates a second message.
  • the second message includes an IP address of the CMC 430 .
  • the controller 420 sends the second message to the CMC 430 .
  • the parsing procedure may be performed by the controller 420 according to a correspondence between the logical port ID of the logical CMC 421 and the physical port ID of the CMC 430 .
  • the controller 420 may determine a physical port ID of a corresponding CMC 430 according to a logical port ID carried in the first message, and will generate a second message that carries an IP address corresponding to the physical port ID of the CMC 430 .
  • the controller 420 may obtain a second correspondence between the controller 420 and at least one EQAM module 432 corresponding to at least one CMC 430 , and enable, according to the second correspondence, the controller 420 and the at least one EQAM module 432 to perform communication according to a resource management protocol.
  • the controller 420 may simulate the at least one CMC 430 into the logical CMC 421 , the logical CMC 421 may include at least one logical port, and each logical port ID corresponds to a physical port ID of one CMC 430 of the at least one CMC 430 .
  • the first correspondence may include a one-to-one correspondence between the logical port ID of the logical CMC 421 of the controller 420 and the physical port ID of the at least one CMC 430 .
  • FIG. 5 is a schematic block diagram of EQAM management according to an embodiment of the present disclosure. As shown in FIG. 5 , a front-end device 510 and a fiber node 520 are included.
  • FIG. 5 It should be understood that another device may be included in FIG. 5 .
  • FIG. 5 For ease of understanding and description, only devices related to the present disclosure are described in this embodiment of the present disclosure.
  • the front-end device 510 may include an EQAM controller 511 .
  • the EQAM controller 511 may be a function module of the controller 420 shown in FIG. 4 .
  • the EQAM controller 511 is a logically independent module, but may be present as an independent device in a product, or may be located inside an OLT. In this embodiment shown in FIG. 5 , the EQAM controller 511 may be located inside an OLT 512 .
  • the OLT 512 may be located in an equipment room.
  • the fiber node 520 may include a CMC 521 . It should be understood that, although only one CMC 521 is shown in FIG. 5 , the fiber node may include multiple CMCs 521 . Each CMC 521 may include an EQAM module 522 . The EQAM module 522 is an EQAM device.
  • the EQAM module 522 and the front-end device 510 may be connected using a digital fiber.
  • the EQAM controller 511 of the front-end device 510 may manage the EQAM module 522 of the fiber node 520 .
  • the following details an embodiment of how the EQAM controller 511 manages the EQAM module 522 .
  • the EQAM controller 511 may obtain a second correspondence between the EQAM controller 511 and at least one EQAM module 522 corresponding to at least one CMC 521 , and enable, according to the second correspondence, the EQAM controller 511 and the at least one EQAM module 522 to perform communication according to a resource management protocol.
  • the EQAM controller 511 may include a logical EQAM module (not shown) obtained after the at least one EQAM module 522 is simulated, the logical EQAM module includes at least one logical port ID, and the second correspondence includes a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one EQAM module 522 .
  • a resource management protocol includes an ERMI protocol
  • the ERMI protocol includes an ERMI-1 registration protocol, an ERMI-2 control protocol, and an ERMI-3 control protocol.
  • the ERMI-1 registration protocol is used for a service management platform to register at least one EQAM module 522 using the EQAM controller 511
  • the ERMI-2 control protocol is used for the service management platform to control the at least one EQAM module 522 using the EQAM controller 511
  • the ERMI-3 control protocol is used for the service management platform to control, using the EQAM controller 511 , at least one DOCSIS module (not shown) corresponding to the at least one CMC 521 .
  • FIG. 6 is a schematic block diagram of EQAM management according to another embodiment of the present disclosure. As shown in FIG. 6 , an ERM 610 , a controller 620 , and a CMC 630 are included.
  • the CMC 630 includes a DOCSIS front-end module 631 and an EQAM module 632 .
  • FIG. 6 It should be understood that another device may be included in FIG. 6 .
  • FIG. 6 For ease of understanding and description, only devices related to the present disclosure are described in this embodiment of the present disclosure.
  • CMC 630 Although only one CMC 630 is shown in FIG. 6 , at least one CMC 630 may be included in this embodiment of the present disclosure. For ease of description, only one CMC 630 is described in the present disclosure.
  • the controller 620 may simulate multiple EQAM modules 632 corresponding to multiple CMCs 630 into a logical EQAM module, and each EQAM module 632 may be equivalent to a port, or a board, or a remote subrack of the logical EQAM module. That is, the controller 620 may include a logical function module (not shown), and the logical function module is the logical EQAM module.
  • the controller 620 may control the DOCSIS front-end module 631 using an ERMI-3, may complete a registration procedure of the EQAM module 632 using an ERMI-1, and may further control the EQAM module 632 using an ERMI-2.
  • the controller 620 communicates with the ERM 610 using the ERMI protocols, that is, according to the ERMI-1, the ERMI-2, and the EMRI-3.
  • the logical EQAM module may include multiple logical port IDs, and each logical port ID may be corresponding to a physical port ID of the EQAM module 632 .
  • the logical EQAM module may further include a management IP address.
  • Each EQAM module may further include an IP address.
  • the EQAM module 632 When registering with the logical EQAM module of the controller 620 , the EQAM module 632 reports its physical resource to the logical EQAM module using an ERMI-1 update message.
  • the controller 620 may include the reported physical resource and a correspondence between a logical port ID and a physical port ID.
  • a method for implementing protocol proxy by the controller 620 may be as follows.
  • the logical EQAM module of the controller 620 receives a first message sent by the ERM 610 using the ERMI protocols.
  • the first message includes a first IP address and an RF port ID.
  • the first IP address may be corresponding to the management IP address of the logical EQAM module
  • the RF port ID may be corresponding to the logical port ID of the logical EQAM module.
  • the logical EQAM module modifies the first IP address in the first message to an IP address of an EQAM module whose physical port ID corresponds to the logical port ID, and generates a second message.
  • the logical EQAM module sends the second message to the EQAM module 632 .
  • FIG. 7 is a schematic flowchart of a method for managing a communications system according to an embodiment of the present disclosure.
  • the method shown in FIG. 7 may be performed by a controller.
  • the method shown in FIG. 7 may be implemented by the controllers in FIG. 2 to FIG. 6 . To avoid repetition, details are not further described herein.
  • the communications system includes a front-end device (not shown) and a remote node device (not shown).
  • the front-end device is configured to transmit a service to the remote node device.
  • the service includes a broadband access service and a video service.
  • the remote node device includes at least one CMC, where each of the at least one CMC includes a DOCSIS front-end module (not shown) that supports the broadband access service and an EQAM module (not shown) that supports the video service, and the at least one CMC and the front-end device are connected using a digital fiber.
  • the front-end device includes a controller. The method includes the following step.
  • Step 710 The controller manages the at least one CMC.
  • the EQAM module supporting the video service and the DOCSIS front-end module configured for broadband access are disposed in a same CMC, and the CMC is controlled and managed by a same front-end controller.
  • the CMC is controlled and managed by a same front-end controller.
  • the communications system further includes a service management platform (not shown) that manages the at least one CMC according to the controller.
  • the controller may implement a conversion function for an interface configuration protocol between the service management platform and the at least one CMC, and implement a proxy function for a resource management protocol between the service management platform and the EQAM module.
  • the controller may obtain a first correspondence between the controller and the at least one CMC, and convert, according to the first correspondence, a first interface configuration protocol between the service management platform and the controller into a second interface configuration protocol between the controller and the at least one CMC.
  • the controller may obtain a second correspondence between the controller and at least one EQAM module corresponding to the at least one CMC, and enable, according to the second correspondence, the controller and the at least one EQAM module to perform communication according to the resource management protocol.
  • the resource management protocol includes an ERMI protocol
  • the ERMI protocol includes an ERMI-1 registration protocol, an ERMI-2 control protocol, and an ERMI-3 control protocol.
  • the ERMI-1 registration protocol is used for the service management platform to register the at least one EQAM module using the controller
  • the ERMI-2 control protocol is used for the service management platform to control the at least one EQAM module using the controller
  • the ERMI-3 control protocol is used for the service management platform to control, using the controller, at least one DOCSIS module corresponding to the at least one CMC.
  • the controller may include a logical CMC obtained after the at least one CMC is simulated, the logical CMC may include at least one logical port ID, and the first correspondence may include a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one CMC.
  • the controller may include a logical EQAM module obtained after the at least one EQAM module is simulated, the logical EQAM module may include at least one logical port ID, and the second correspondence may include a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one EQAM module.
  • FIG. 8 is a schematic flowchart of a process for managing a communications system according to an embodiment of the present disclosure.
  • the process shown in FIG. 8 may be performed by a controller.
  • the process shown in FIG. 8 may be described with reference to the schematic block diagrams in FIG. 4 and FIG. 6 .
  • Step 801 Simulate multiple CMCs into a logical CMC.
  • the logical CMC is equivalent to a CCAP device, and the CCAP device includes a CMTS module and an EQAM module.
  • Each CMC may be equivalent to a port, or a board, or a remote subrack.
  • the logical CMC may include multiple logical port IDs, and each logical port ID may be corresponding to a physical port ID of a CMC.
  • Step 802 Implement protocol conversion between a service management platform and a CMC.
  • the method for performing protocol conversion by the controller may be as follows.
  • the controller 420 receives a first message sent by the OSS/NMS 410 according to the first interface configuration protocol.
  • the first message includes an IP address of the controller 420 .
  • the controller 420 parses the first message according to the second interface configuration protocol, and generates a second message.
  • the second message includes an IP address of the CMC 430 .
  • the controller 420 sends the second message to the CMC 430 .
  • the parsing procedure may be performed by the controller 420 according to a correspondence between the logical port ID of the logical CMC 421 and the physical port ID of the CMC 430 .
  • the controller 420 may determine a physical port ID of a corresponding CMC 430 according to a logical port ID carried in the first message, and will generate a second message that carries an IP address corresponding to the physical port ID of the CMC 430 .
  • Step 803 Simulate multiple EQAM modules into a logical EQAM module.
  • the controller 620 may simulate the multiple EQAM modules 632 corresponding to the multiple CMCs 630 into a logical EQAM module, and each EQAM module 632 may be equivalent to a port, or a board, or a remote subrack of the logical EQAM module. That is, the controller 620 may include a logical function module, and the logical function module is the logical EQAM module.
  • Step 804 Implement protocol proxy between the service management platform and the CMC.
  • the controller 620 may control the DOCSIS front-end module 631 using the ERMI-3, may complete the registration procedure of the EQAM module 632 using the ERMI-1, and may further control the EQAM module 632 using the ERMI-2.
  • the controller 620 communicates with the ERM 610 using the ERMI protocols, that is, according to the ERMI-1, the ERMI-2, and the EMRI-3.
  • the logical EQAM module may include multiple logical port IDs, and each logical port ID may be corresponding to a physical port ID of the EQAM module 632 .
  • the logical EQAM module may further include a management IP address.
  • Each EQAM module 632 may further include an IP address.
  • the EQAM module 632 When registering with the logical EQAM module of the controller 620 , the EQAM module 632 reports its physical resource to the logical EQAM module using an ERMI-1 update message.
  • the controller 620 may include the reported physical resource and a correspondence between a logical port ID and a physical port ID.
  • a method for implementing protocol proxy by the controller 620 may be as follows.
  • the logical EQAM module of the controller 620 receives a first message sent by the ERM 610 using the ERMI protocol.
  • the first message includes a first IP address and an RF port ID.
  • the first IP address may be corresponding to the management IP address of the logical EQAM module, and the RF port ID may be corresponding to the logical port ID.
  • the logical EQAM module modifies the first IP address in the first message to an IP address of an EQAM module whose physical port ID corresponds to the logical port ID, and generates a second message.
  • the logical EQAM module sends the second message to the EQAM module 632 .
  • FIG. 9 is a schematic block diagram of a controller 90 according to an embodiment of the present disclosure.
  • a communications system in which the controller 90 is located includes a front-end device (not shown) and a remote node device (not shown).
  • the front-end device is configured to transmit a service to the remote node device.
  • the service includes a broadband access service and a video service.
  • the remote node device includes at least one CMC (not shown), where each of the at least one CMC includes a DOCSIS front-end module (not shown) that supports the broadband access service and an EQAM module (not shown) that supports the video service, and the at least one CMC and the front-end device are connected using a digital fiber.
  • the controller 90 includes a management unit 91 .
  • the management unit 91 manages the at least one CMC.
  • the EQAM module supporting the video service and the DOCSIS front-end module configured for broadband access are disposed in a same CMC, and the CMC is controlled and managed by a same front-end controller.
  • the CMC is controlled and managed by a same front-end controller.
  • the communications system further includes a service management platform (not shown) that manages the at least one CMC according to the controller 90 .
  • the management unit 91 may implement a conversion function for an interface configuration protocol between the service management platform and the at least one CMC, and implement a proxy function for a resource management protocol between the service management platform and the EQAM module.
  • the management unit 91 may obtain a first correspondence between the controller and the at least one CMC, and convert, according to the first correspondence, a first interface configuration protocol between the service management platform and the controller 90 into a second interface configuration protocol between the controller 90 and the at least one CMC.
  • the management unit 91 may obtain a second correspondence between the controller 90 and at least one EQAM module corresponding to the at least one CMC, and enable, according to the second correspondence, the controller 90 and the at least one EQAM module to perform communication according to the resource management protocol.
  • the resource management protocol includes an ERMI protocol
  • the ERMI protocol includes an ERMI-1 registration protocol, an ERMI-2 control protocol, and an ERMI-3 control protocol.
  • the ERMI-1 registration protocol is used for the service management platform to register the at least one EQAM module using the controller 90
  • the ERMI-2 control protocol is used for the service management platform to control the at least one EQAM module using the controller 90
  • the ERMI-3 control protocol is used for the service management platform to control, using the controller 90 , at least one DOCSIS module corresponding to the at least one CMC.
  • the management unit 91 may include a logical CMC obtained after the at least one CMC is simulated, the logical CMC includes at least one logical port ID, and the first correspondence may include a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one CMC.
  • the management unit 91 may include a logical EQAM module obtained after at least one EQAM module is simulated, the logical EQAM module includes at least one logical port ID, and the second correspondence includes a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one EQAM module.
  • each CMC further includes an R-OOB module and a PNM module.
  • FIG. 10 is a schematic block diagram of a controller 100 according to another embodiment of the present disclosure.
  • the controller 100 in FIG. 10 may be configured to implement steps and methods in the foregoing method embodiments.
  • the controller 100 in FIG. 10 includes a processor 101 and a memory 102 .
  • the processor 101 and the memory 102 are connected using a bus system 109 .
  • the processor 101 controls operations of the controller 100 .
  • the memory 102 may include a read-only memory (ROM) and a random access memory (RAM), and provides instructions and data for the processor 101 .
  • a part of the memory 102 may further include a non-volatile RAM (NVRAM).
  • Components in the controller 100 are coupled together using the bus system 109 .
  • the bus system 109 includes not only a data bus, but also a power supply bus, a control bus, and a status signal bus. However, for clear description, various buses are denoted by the bus system 109 in the diagram.
  • the processor 101 may be an integrated circuit chip with a signal processing capability.
  • the foregoing processor 101 may be a general purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute methods, steps and logical block diagrams disclosed in the embodiments of the present disclosure.
  • the general purpose processor may be a microprocessor, or the processor 101 may be any conventional processor or the like.
  • the processor 101 reads information in the memory 102 and controls each component of the controller 100 in combination with hardware of the processor 101 .
  • the method in FIG. 7 may be implemented in the controller 100 in FIG. 10 . To avoid repetition, details are not further described.
  • the communications system includes a front-end device (not shown) and a remote node device (not shown).
  • the front-end device is configured to transmit a service to the remote node device.
  • the service includes a broadband access service and a video service.
  • the remote node device includes at least one CMC (not shown), where each of the at least one CMC includes a DOCSIS front-end module (not shown) that supports the broadband access service and an EQAM module (not shown) that supports the video service, and the at least one CMC and the front-end device are connected using a digital fiber.
  • the front-end device includes the controller 100 .
  • the controller 100 completes the operation of managing the at least one CMC.
  • the EQAM module supporting the video service and the DOCSIS front-end module configured for broadband access are disposed in a same CMC, and the CMC is controlled and managed by a same front-end controller 100 .
  • the CMC is controlled and managed by a same front-end controller 100 .
  • the processor 101 may implement a conversion function for an interface configuration protocol between the service management platform and the at least one CMC, and implement a proxy function for a resource management protocol between the service management platform and the EQAM module.
  • the processor 101 may obtain a first correspondence between the controller 100 and the at least one CMC, and convert, according to the first correspondence, a first interface configuration protocol between the service management platform and the controller 100 into a second interface configuration protocol between the controller 100 and the at least one CMC.
  • a processor 101 may obtain a second correspondence between the controller 100 and at least one EQAM module corresponding to the at least one CMC, and enable, according to the second correspondence, the controller 100 and the at least one EQAM module to perform communication according to a resource management protocol.
  • the resource management protocol includes an ERMI protocol
  • the ERMI protocol includes an ERMI-1 registration protocol, an ERMI-2 control protocol, and an ERMI-3 control protocol.
  • the ERMI-1 registration protocol is used for the service management platform to register the at least one EQAM module using the controller 100
  • the ERMI-2 control protocol is used for the service management platform to control the at least one EQAM module using the controller 100
  • the ERMI-3 control protocol is used for the service management platform to control, using the controller 100 , at least one DOCSIS module corresponding to the at least one CMC.
  • the controller 100 includes a logical CMC obtained after the at least one CMC is simulated, the logical CMC includes at least one logical port ID, and the first correspondence may include a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one CMC.
  • the controller 100 includes a logical EQAM module obtained after the at least one EQAM module is simulated, the logical EQAM module includes at least one logical port ID, and the second correspondence includes a one-to-one correspondence between the at least one logical port ID and at least one physical port ID corresponding to the at least one EQAM module.
  • each CMC further includes an R-OOB module and a PNM module.
  • system and “network” may be used interchangeably in this specification.
  • network may be used interchangeably in this specification.
  • the term “and/or” in this specification describes only an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: only A exists, both A and B exist, and only B exists.
  • the character “/” in this specification generally indicates an “or” relationship between the associated objects.
  • B corresponding to A indicates that B is associated with A, and B may be determined according to A.
  • determining B according to A does not mean that B is determined according to A only, that is, B may also be determined according to A and/or other information.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the described apparatus embodiment is only an example.
  • the unit division is merely logical function division and may be other division in actual implementation.
  • a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed.
  • the displayed or discussed mutual couplings or direct couplings or communication connections may be indirect couplings or communication connections between some interfaces, apparatuses, and units, or may be implemented in electronic, mechanical, or other forms.
  • the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on a plurality of network units. A part or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present disclosure.
  • functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit.
  • the integrated unit may be implemented in a form of hardware, or may be implemented in a form of a software functional unit.
  • the present disclosure may be implemented by hardware, firmware or a combination thereof.
  • the foregoing functions may be stored in a computer-readable medium or transmitted as one or more instructions or code in the computer-readable medium.
  • the computer-readable medium includes a computer storage medium and a communications medium.
  • the communications medium includes any medium that enables a computer program to be transmitted from one place to another.
  • the storage medium may be any available medium accessible to a computer.
  • the computer-readable medium may include a RAM, a ROM, an electrically erasable programmable ROM (EEPROM), a compact disc ROM (CD-ROM), or another optical disc storage or disk storage medium, or another magnetic storage device, or any other medium that can carry or store expected program code in a form of an instruction or a data structure and can be accessed by a computer.
  • any connection may be appropriately defined as a computer-readable medium.
  • a disk and disc used by the present disclosure includes a compact disc (CD), a laser disc, an optical disc, a digital versatile disc (DVD), a FLOPPY DISK and a BLU-RAY DISC.
  • the disk generally copies data by a magnetic means, and the disc copies data optically by a laser means.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Electromagnetism (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)
  • Communication Control (AREA)
  • Small-Scale Networks (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
US15/667,100 2015-02-02 2017-08-02 Communications system, method for managing communications system, and controller Active 2035-05-07 US10374711B2 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/072118 WO2016123739A1 (fr) 2015-02-02 2015-02-02 Système de communication, procédé de gestion du système de communication, et dispositif de commande

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/072118 Continuation WO2016123739A1 (fr) 2015-02-02 2015-02-02 Système de communication, procédé de gestion du système de communication, et dispositif de commande

Publications (2)

Publication Number Publication Date
US20170331554A1 US20170331554A1 (en) 2017-11-16
US10374711B2 true US10374711B2 (en) 2019-08-06

Family

ID=56563289

Family Applications (1)

Application Number Title Priority Date Filing Date
US15/667,100 Active 2035-05-07 US10374711B2 (en) 2015-02-02 2017-08-02 Communications system, method for managing communications system, and controller

Country Status (5)

Country Link
US (1) US10374711B2 (fr)
EP (1) EP3252969B1 (fr)
CN (1) CN106063156B (fr)
PL (1) PL3252969T3 (fr)
WO (1) WO2016123739A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190196452A1 (en) * 2017-12-21 2019-06-27 Fanuc Corporation Numerical controller
US20190268037A1 (en) * 2018-02-28 2019-08-29 Maxlinear, Inc. Full-Duplex Cable Modem Calibration

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018068238A1 (fr) * 2016-10-12 2018-04-19 华为技术有限公司 Système, appareil et procédé de gestion de convertisseur de support de câble
WO2018072077A1 (fr) * 2016-10-18 2018-04-26 华为技术有限公司 Procédé de transmission de données, et dispositif associé
CN110073672B (zh) * 2016-12-30 2021-10-15 华为技术有限公司 一种管理光网络单元onu的方法、装置及系统
US10637740B2 (en) * 2017-07-07 2020-04-28 Howard Pfeffer Apparatus and methods for management, configuration and provisioning of communication devices in a distributed access architecture
CN111988205B (zh) * 2019-05-24 2022-03-04 上海诺基亚贝尔股份有限公司 一种服务远程物理设备的方法和核心代理设备
BR112022018498A2 (pt) * 2020-03-20 2022-11-01 Arris Entpr Llc Gerenciamento eficiente do plano de dados phy remoto para um sistema de cabos
KR20250174223A (ko) * 2024-06-05 2025-12-12 현대자동차주식회사 차량용 라디오 장치 및 이의 제어방법

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007009938A1 (fr) 2005-07-20 2007-01-25 Nokia Siemens Networks Gmbh & Co. Kg. Coupleur trois voies pour reseau optique passif
EP1965561A2 (fr) 2007-02-28 2008-09-03 General instrument Corporation Système et procédé de transmission de contenu numérique en utilisant une architecture de dérivation de système de terminaison de modem à câble (CMTS)
US20100309783A1 (en) 2009-06-08 2010-12-09 Arris Group, Inc. Latency based Random Early Discard for Network Packets
US20110078755A1 (en) 2009-09-25 2011-03-31 Futurewei Technologies, Inc. Passive Optical Network Data Over Cable Service Interface Specification Upstream Proxy Architecture Over the Next Generation Hybrid Fiber-Coaxial Networks
US20110085481A1 (en) 2009-10-13 2011-04-14 Cisco Technology, Inc. Reducing energy consumption of an edge device
US20110138434A1 (en) 2009-12-09 2011-06-09 General Instrument Corporation System and method for a digital tv converter with iptv capabilities
US20110137434A1 (en) 2009-12-04 2011-06-09 Industrial Technology Research Corporation Apparatus and Method of Synchronizing and Interpolating Axes of Multi-System
US20110200325A1 (en) * 2010-02-15 2011-08-18 Andrey Kobyakov Dynamic Cell Bonding (DCB) for Radio-over-Fiber (RoF)-Based Networks and Communication Systems and Related Methods
US20110268446A1 (en) * 2010-05-02 2011-11-03 Cune William P Providing digital data services in optical fiber-based distributed radio frequency (rf) communications systems, and related components and methods
US20120134673A1 (en) * 2009-02-03 2012-05-31 Rajeshkannan Palanisamy Optical fiber-based distributed antenna systems, components, and related methods for calibration thereof
CN102726005A (zh) 2011-11-17 2012-10-10 华为技术有限公司 一种基于docsis协议的接入方法、装置及系统
US20130111536A1 (en) 2011-10-27 2013-05-02 Bruce McClelland Terminal adapter for enabling non-ip-encapsulated videos to be received at subscriber premises for playback on an ip devices
US20160328252A1 (en) * 2015-05-04 2016-11-10 Cisco Technology, Inc. Virtual modem termination system migration in a cable modem network environment
US20180332359A1 (en) * 2012-08-28 2018-11-15 Time Warner Cable Enterprises Llc Apparatus and methods for controlling digital video recorders

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7130466B2 (en) * 2000-12-21 2006-10-31 Cobion Ag System and method for compiling images from a database and comparing the compiled images with known images
US11625971B2 (en) * 2016-07-27 2023-04-11 United Parcel Service Of America, Inc. Secure lockers for use as item exchange points

Patent Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007009938A1 (fr) 2005-07-20 2007-01-25 Nokia Siemens Networks Gmbh & Co. Kg. Coupleur trois voies pour reseau optique passif
EP1965561A2 (fr) 2007-02-28 2008-09-03 General instrument Corporation Système et procédé de transmission de contenu numérique en utilisant une architecture de dérivation de système de terminaison de modem à câble (CMTS)
US20120134673A1 (en) * 2009-02-03 2012-05-31 Rajeshkannan Palanisamy Optical fiber-based distributed antenna systems, components, and related methods for calibration thereof
US20100309783A1 (en) 2009-06-08 2010-12-09 Arris Group, Inc. Latency based Random Early Discard for Network Packets
CN102577181A (zh) 2009-09-25 2012-07-11 华为技术有限公司 经由下一代光纤-同轴电缆混合网络的无源光网络电缆数据业务接口规范上游代理架构
US20110078755A1 (en) 2009-09-25 2011-03-31 Futurewei Technologies, Inc. Passive Optical Network Data Over Cable Service Interface Specification Upstream Proxy Architecture Over the Next Generation Hybrid Fiber-Coaxial Networks
US20110085481A1 (en) 2009-10-13 2011-04-14 Cisco Technology, Inc. Reducing energy consumption of an edge device
US20110137434A1 (en) 2009-12-04 2011-06-09 Industrial Technology Research Corporation Apparatus and Method of Synchronizing and Interpolating Axes of Multi-System
US20110138434A1 (en) 2009-12-09 2011-06-09 General Instrument Corporation System and method for a digital tv converter with iptv capabilities
US20110200325A1 (en) * 2010-02-15 2011-08-18 Andrey Kobyakov Dynamic Cell Bonding (DCB) for Radio-over-Fiber (RoF)-Based Networks and Communication Systems and Related Methods
US20110268446A1 (en) * 2010-05-02 2011-11-03 Cune William P Providing digital data services in optical fiber-based distributed radio frequency (rf) communications systems, and related components and methods
US20130111536A1 (en) 2011-10-27 2013-05-02 Bruce McClelland Terminal adapter for enabling non-ip-encapsulated videos to be received at subscriber premises for playback on an ip devices
CN102726005A (zh) 2011-11-17 2012-10-10 华为技术有限公司 一种基于docsis协议的接入方法、装置及系统
US20140248054A1 (en) 2011-11-17 2014-09-04 Huawei Technologies Co., Ltd. Docsis protocol-based access method, apparatus, and system
US20180332359A1 (en) * 2012-08-28 2018-11-15 Time Warner Cable Enterprises Llc Apparatus and methods for controlling digital video recorders
US20160328252A1 (en) * 2015-05-04 2016-11-10 Cisco Technology, Inc. Virtual modem termination system migration in a cable modem network environment

Non-Patent Citations (15)

* Cited by examiner, † Cited by third party
Title
"CMAP Architecture Technical Report," Data-Over-Cable Service Interface Specification, CM-TR-CMAP-V01-101222, Dec. 22, 2010, 48 pages.
"Edge QAM Video Stream Interface Specification," Data-Over-Cable-Service-Interface Specifications Modular Headend Architecture, CM-SP-EQAM-VSI-101-081107, Nov. 7, 2008, 39 pages.
"Edge Resource Manager Interface Specification," Data-Over-Cable-Service-Interface Specifications Modular Headend Architecture, CM-SP-ERMI-103-081107, Nov. 7, 2008, 127 pages.
"IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems," IEEE Instrumentation and Measurement Society, IEEE Std 1588, Jul. 24, 2008, 289 pages.
‘Physical Layer Specification,’ Data Over Cable Service Interface Specifications DOCSIS 3.0, CM-SP-PHYv3.0-I11-130808, Aug. 8, 2013, 200 pages.
Chapman, J., "DOCSIS Remote PHY Modular Headend Architecture (MHAv2) A Technical Paper prepared for the Society of Cable Telecommunications Engineers by," XP055518636, Oct. 21, 2013, 22 pages.
English Translation of Pantelias, N., "Using C-DOCSIS technology to build video on demand and network video service," Broadcom Corporation, May 29, 2013, 10 pages.
Foreign Communication From a Counterpart Application, Chinese Application No. 201580000293.6, Chinese Office Action dated Mar. 26, 2018, 3 pages.
Foreign Communication From a Counterpart Application, Chinese Application No. 201580000293.6, Chinese Search Report dated Mar. 14, 2018, 2 pages.
Foreign Communication From a Counterpart Application, European Application No. 15880695.0, European Office Action dated Oct. 31, 2018, 9 pages.
Foreign Communication From a Counterpart Application, European Application No. 15880695.0, Extended European Search Report dated Jan. 15, 2018, 9 pages.
Foreign Communication From a Counterpart Application, PCT Application No. PCT/CN2015/072118, English Translation of International Search Report dated Oct. 29, 2015, 2 pages.
Foreign Communication From a Counterpart Application, PCT Application No. PCT/CN2015/072118, English Translation of Written Opinion dated Oct. 29, 2015, 5 pages.
Pantelias, N., "Using C-DOCSIS technology to build video on demand and network video service," Broadcom Corporation, May 29, 2013, 10 pages.
'Physical Layer Specification,' Data Over Cable Service Interface Specifications DOCSIS 3.0, CM-SP-PHYv3.0-I11-130808, Aug. 8, 2013, 200 pages.

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190196452A1 (en) * 2017-12-21 2019-06-27 Fanuc Corporation Numerical controller
US10866577B2 (en) * 2017-12-21 2020-12-15 Fanuc Corporation Numerical controller
US20190268037A1 (en) * 2018-02-28 2019-08-29 Maxlinear, Inc. Full-Duplex Cable Modem Calibration
US11502723B2 (en) * 2018-02-28 2022-11-15 Maxlinear, Inc. Full-duplex cable modem calibration
US20230188179A1 (en) * 2018-02-28 2023-06-15 Maxlinear, Inc. Full-Duplex Cable Modem Calibration

Also Published As

Publication number Publication date
CN106063156B (zh) 2019-09-03
CN106063156A (zh) 2016-10-26
WO2016123739A1 (fr) 2016-08-11
EP3252969A1 (fr) 2017-12-06
EP3252969A4 (fr) 2018-02-14
US20170331554A1 (en) 2017-11-16
PL3252969T3 (pl) 2020-07-27
EP3252969B1 (fr) 2020-03-18

Similar Documents

Publication Publication Date Title
US20170331554A1 (en) Communications System, Method for Managing Communications System, and Controller
CN102082684B (zh) 业务配置转换方法、装置及系统
US11025487B2 (en) Service distribution method, device and system
US11038751B2 (en) Information processing method, network node, authentication method, and server
US10880196B2 (en) Bi-directional speed test method and system for customer premises equipment (CPE) devices
TWI555355B (zh) 一種同軸電纜媒體轉換器及流量交換的方法
US8818188B2 (en) Traffic generation and analysis for ONU emulation
US10021000B2 (en) Provisioning in support of an embedded cable modem MAC address
US10848244B2 (en) Data provisioning
CN102739421A (zh) 控制同轴宽带接入终端的方法和系统
US9497076B2 (en) Dual-stack support for demarc auto configuration (DAC) mechanism in DOCSIS provisioning of EPON (DPOE) network
US10797942B2 (en) Provisioning network services for cable systems
CN104219089A (zh) 一种pon网管自动发现onu设备并自动生成拓扑方法
CN104954313A (zh) 一种分布式ipqam系统
US20190238361A1 (en) Cable Media Converter Management Method, Apparatus, and System
US20160277141A1 (en) Systems and Methods of Generalized DOCSIS Provisioning over Passive Optical Network
CN109600682B (zh) 网络系统
FENG et al. A NETWORK MANAGEMENT SYSTEM FOR EPON BASED ON SNMP
HK1189111A (en) Dual-stack support for demarc auto configuration (dac) mechanism in docsis provisioning of epon (dpoe) network
HK1189111B (en) Dual-stack support for demarc auto configuration (dac) mechanism in docsis provisioning of epon (dpoe) network

Legal Events

Date Code Title Description
AS Assignment

Owner name: HUAWEI TECHNOLOGIES CO., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KE, BO;WU, GUANGSHENG;SIGNING DATES FROM 20171105 TO 20171106;REEL/FRAME:044811/0259

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4