CN111741501B - Method, device and apparatus for switching core device and computer readable medium - Google Patents
Method, device and apparatus for switching core device and computer readable medium Download PDFInfo
- Publication number
- CN111741501B CN111741501B CN201910229411.0A CN201910229411A CN111741501B CN 111741501 B CN111741501 B CN 111741501B CN 201910229411 A CN201910229411 A CN 201910229411A CN 111741501 B CN111741501 B CN 111741501B
- Authority
- CN
- China
- Prior art keywords
- core
- core device
- backup
- remote device
- remote
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/12—Reselecting a serving backbone network switching or routing node
Abstract
Embodiments of the present disclosure provide a method, device, apparatus, and computer-readable medium for switching core devices. In the method, at an active core device managing a remote device, receiving information about a backup core device of the remote device from the remote device; establishing a connection between the active core device and the backup core device; and sending device state information associated with the remote device to the backup core device via the connection to enable the backup core device to manage the remote device based on the device state information upon a handover of the remote device from the active core device to the backup core device. According to the embodiment of the disclosure, after the active core device is switched to the backup core device, the initialization process of the remote device consuming a large amount of time is not required to be performed at the backup core device, so that the switching time is reduced, the influence on the operation service is avoided to the maximum extent, the remote device is quickly switched to the new auxiliary core device, and the time cost for recovering the original service is remarkably reduced.
Description
Technical Field
Embodiments of the present disclosure relate generally to the field of communications, and more particularly, to a method, device, apparatus, and computer-readable medium for switching core devices.
Background
A Converged Cable Access Platform (CCAP) core device includes a Cable Modem Termination System (CMTS) core device for Data Over Cable Service Interface Specification (DOCSIS) and an Edge Quadrature Amplitude Modulation (EQAM) core device for video. The CMTS core devices contain DOCSIS MAC and upper layer DOCSIS protocols. The EQAM core device contains all the video processing functions currently provided by the EQAM.
The remote physical device is a physical layer converter that converts downstream DOCSIS, moving Picture Experts Group (MPEG) video, and out-of-band (OOB) signals received from the CCAP core device on a digital medium, such as an ethernet or passive optical network, to analog signals for transmission over Radio Frequency (RF) or linear optical systems. And on the other hand, upstream DOCSIS and OOB signals received from analog media such as RF or linear optics are converted into digital signals for transmission to the CCAP core device over ethernet or PON. The RPD has a resource set List (ResourceSet List) that identifies which secondary core devices may control which RPD object. The RPD establishes connection with both CCAP main core equipment and at least one CCAP auxiliary core equipment. When an RPD is handed over from one secondary core device (active core device) connected thereto to another secondary core device (backup core device), device state information associated with the RPD needs to be re-registered on the backup core device.
Disclosure of Invention
Embodiments of the present disclosure relate to a method, device, apparatus, and computer-readable medium for switching core devices.
In a first aspect of the present disclosure, a method is provided. The method comprises the following steps: receiving, at an active core device managing a remote device, information from the remote device regarding a backup core device of the remote device; establishing a connection between the active core device and the backup core device; and sending device state information associated with the remote device to the backup core device via the connection to enable the backup core device to manage the remote device based on the device state information after the remote device switches from the active core device to the backup core device.
In a second aspect of the disclosure, a method of communication is provided. The method comprises the following steps: receiving, at a backup core device of a remote device, device state information associated with the remote device from an active core device managing the remote device in response to a connection between the backup core device and the active core device having been established; and managing the remote device based on the device status information after the remote device switches from the active core device to the backup core device.
In a third aspect of the disclosure, an apparatus is provided. The core device includes at least one processor and at least one memory including computer program instructions. The at least one memory and the computer program instructions are configured to, with the at least one processor, cause the remote device to perform the method of the first aspect of the disclosure.
In a fourth aspect of the disclosure, an apparatus is provided. The core device includes at least one processor and at least one memory including computer program instructions. The at least one memory and the computer program instructions are configured, with the at least one processor, to cause the core device to perform the method of the second aspect of the disclosure.
In a fifth aspect of the present disclosure, an apparatus for switching a core device is provided. The apparatus comprises means for receiving, at an active core device managing a remote device, information from the remote device regarding a backup core device of the remote device; means for establishing a connection between the active core device and the backup core device; and means for sending device state information associated with the remote device to the backup core device via the connection to enable the backup core device to manage the remote device based on the device state information upon a handover of the remote device from the active core device to the backup core device.
In a sixth aspect of the present disclosure, an apparatus for switching a core device is provided. The apparatus includes means for receiving, at a backup core device of a remote device, device state information associated with the remote device from an active core device managing the remote device in response to a connection between the backup core device and the active core device having been established; and means for managing the remote device based on the device state information after the remote device switches from the active core device to the backup core device.
In a seventh aspect of the disclosure, a computer-readable medium is provided. The computer readable medium comprises machine executable instructions which, when executed, cause a machine to perform a method according to the first aspect.
In an eighth aspect of the disclosure, a computer-readable medium is provided. The computer readable medium comprises machine executable instructions which, when executed, cause a machine to perform a method according to the second aspect.
It should be understood that the statements herein reciting aspects are not intended to limit the critical or essential features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The above and other objects, features and advantages of the embodiments of the present disclosure will become readily apparent from the following detailed description read in conjunction with the accompanying drawings. Several embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which:
fig. 1 illustrates a schematic diagram of a communication system in which embodiments of the present disclosure may be implemented.
Fig. 2 shows a schematic diagram of a process 200 of a communication method according to an embodiment of the disclosure.
Fig. 3 shows a flow diagram of a communication method 300 according to an embodiment of the present disclosure.
Fig. 4 shows a flow diagram of a communication method 400 according to an embodiment of the present disclosure.
Fig. 5 illustrates a simplified block diagram of a device suitable for implementing embodiments of the present disclosure.
FIG. 6 illustrates a schematic diagram of a computer-readable medium suitable for implementing embodiments of the present disclosure.
Throughout the drawings, the same or similar reference numerals are used to designate the same or similar components.
Detailed Description
The principles and spirit of the present disclosure will be described with reference to a number of exemplary embodiments shown in the drawings. It is understood that these specific embodiments are described merely to enable those skilled in the art to better understand and implement the present disclosure, and are not intended to limit the scope of the present disclosure in any way.
As used herein, the terms "comprises," comprising, "and the like are to be construed as open-ended inclusions, i.e.," including, but not limited to. The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first," "second," and the like may refer to different or the same objects. Other explicit and implicit definitions are also possible below.
As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" can include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Further, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Further, "determining" may include resolving, selecting, choosing, establishing, and the like.
The term "circuitry" as used herein refers to one or more of the following: (a) Hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry); and (b) a combination of hardware circuitry and software, such as (if applicable): (i) A combination of analog and/or digital hardware circuitry and software/firmware, and (ii) any portion of a hardware processor and software (including a digital signal processor, software, and memory that work together to cause an apparatus, such as an OLT or other computing device, to perform various functions); and (c) hardware circuitry and/or a processor, such as a microprocessor or a portion of a microprocessor, that requires software (e.g., firmware) for operation, but may be software-free when software is not required for operation.
The definition of circuit applies to all usage scenarios of this term in this application, including any claims. As another example, the term "circuitry" as used herein also covers an implementation of merely a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor, or software or firmware accompanying it. For example, the term "circuitry" would also cover a baseband integrated circuit or processor integrated circuit or a similar integrated circuit in an OLT or other computing device, as applicable to the particular claim element.
Fig. 1 illustrates a schematic diagram of a communication system 100 in which embodiments of the present disclosure may be implemented. As shown in fig. 1, communication system 100 may include a remote device 110 connected to a core device 120-1 through a communication link 112. In addition, remote device 110 is connected to core device 120-2 via communication link 113, and to more core devices 120-3 via more communication links (not shown), and so on. In some embodiments, communication links 112 and 113, etc. between remote device 110 and core device 120 may include a Converged Interconnect Network (CIN).
The term "core device" in this disclosure relates to a Converged Cable Access Platform (CCAP) core device, which includes a Cable Modem Termination System (CMTS) core device for Data Over Cable Service Interface Specification (DOCSIS) and an Edge Quadrature Amplitude Modulation (EQAM) core device for video. The CMTS core devices contain DOCSIS MAC and upper layer DOCSIS protocols. This includes all signaling functions, downstream and upstream bandwidth scheduling and DOCSIS framing. The DOCSIS functionality of the CMTS core device is defined by mulpiv3.0. The EQAM core device contains all the video processing functions currently provided by the EQAM.
The term "remote device" refers in this disclosure to a remote physical device (hereinafter also referred to as "RPD"). RPD is a physical layer translator that can consist in converting downstream DOCSIS, moving Picture Experts Group (MPEG) video, and Out of band (OOB) signals received from a CCAP core device over a digital medium such as an Ethernet or a Passive Optical Network (PON) to analog signals for transmission over a Radio Frequency (RF) or linear optical system on the one hand, RPD converts upstream DOCSIS and OOB signals received from an analog medium such as RF or linear optics to digital signals for transmission over the Ethernet or PON to the CCAP core device.
The modular front end architecture version 2 (MHAv 2) architecture allows multiple RPDs to be managed by more than one CCAP core device. The RPD is controlled by one active primary CCAP core device and zero or more active secondary CCAP core devices. The active master CCAP core device is the final controlling entity of the RPD. The active master CCAP core device controls RPD, resource allocation, software upgrade and reset or restart operations. The secondary CCAP core device manages a subset of RPD resources, such as a particular channel or RF port. Each secondary CCAP core device establishes its own Generic Control Plane (GCP) session and layer two tunneling protocol version 3 (L2 TPv 3) control session with the RPD.
Potential secondary CCAP core devices include, but are not limited to, the following: the broadcast EQAM CCAP core device controls only the downstream video broadcast channel; SCTE 55-1 and SCTE 55-2CCAP core devices provide traditional Set-Top-Box (STB) control; the 'narrow-cast EQAM' CCAP core device only controls a downstream video narrow-cast channel; a "forward OOB" CCAP core device that controls and acquires NDF, typically broadcasting to multiple RPD ports; a "reverse OOB" CCAP core device that controls and receives the NDR channel, one for each RPD port; a CMTS CCAP to control downstream and upstream channels of the individual MAC domains; CMTS core devices are programmed or configured in a vendor specific manner to operate as primary or secondary core devices.
The core devices may have different roles, such as active core devices, backup core devices, DOCSIS core devices, EQAM core devices, and the like. The specific role of each core device is determined during the GCP configuration phase.
For example, in the example depicted in fig. 1, core device 120-1 may be the primary core device of remote device 110, i.e., the ultimate controlling entity of remote device 110. The core devices 120-2 through 120-3 may act as secondary core devices for the remote device 110, and they may manage a subset of the remote device 110 resources, e.g., a particular channel or RF port, etc. In the context of this disclosure, core devices 120-1, 120-2, and 120-3 may be collectively referred to as core device 120.
In addition to the primary core device, the remote device 110 may be managed by a secondary core device, which may be considered an active secondary core device (also referred to as active core device in the following) of the remote device 110, such as the core device 120-2. In addition, core device 120 may include at least one backup secondary core device (also referred to as a backup core device hereinafter), such as core device 120-3, to enable switching to other secondary core devices in the event of an interruption in the connection of remote device 110 to the active secondary core device. A candidate backup secondary core device table, "CandidateBackupCoreTable," may be stored, for example, at the remote device 120.
It should be appreciated that although fig. 1 depicts communication network 100 as having a particular number of remote devices 110 and core devices 120, and as communicating over particular communication links 112-113, in other embodiments, communication network 100 may have any number of remote devices and core devices, which may communicate in any suitable manner using any suitable communication links.
The GCP connection between remote device 110 and secondary core device 120-2 may fail for a variety of reasons, including failure of the secondary core device itself. In the event of a failure of a currently active core device (e.g., core device 120-2), the GCP connection needs to be switched to a designated backup core device (e.g., core device 120-3). The GCP handover procedure may be initiated by the remote device 110 or the core device (any of 120-1 to 120-3). For example, if a currently active secondary core device (e.g., core device 120-2) requires a maintenance window, the operator may wish to initiate a GCP handover procedure from core device 120-2.
Switching the GCP connection to the backup core device itself does not affect the configuration or data plane processing of the RPD. The RPD must maintain all configuration and status information related to the disconnected active core device throughout the handoff process. Throughout the handoff process, the RPD must maintain L2TPv3 control and data plane operations and related functions with the core device independent of the state of the GCP connection.
After the RPD control is successfully taken over by the backup core device, the new controlling CCAP core device (i.e., the backup core device) may reconfigure the RPD as needed. After successfully taking over RPD control through the backup core device, the CCAP core device may control the L2TPv3 connection or instruct the RPD to tear down the existing L2TPv3 connection and establish a new L2TPv3 connection. The decision whether to reconfigure the RPD and control the L2TPv3 connection is internal (e.g., it may depend on the vendor of the core device). After successfully taking over the RPD control connection through the backup core, the new controlling CCAP core device must control any resources previously allocated to the failed core device (i.e., the active core device). The core device must update its resource set index resourcesettindex field in an entry of the CCAP core device ID CcapCoreIdentification table of the core device group CoreSet and update the CCAP core device owner CcapCoreOwner field in a corresponding entry of the resource set ResourceSet table.
Furthermore, after successfully taking over RPD control by the backup core device, the new controlling CCAP core device must set the core device mode to Active, e.g., "CoreMode = Active", in the entry of its CCAP core device ID table. The new controlling CCAP core device may also update other fields in the entry of its CCAP core device ID table after successfully taking over RPD control through the backup core. How the new values selected for these additional fields are selected depends on the vendor of the core device. The new controlling CCAP core device must set the fields InitialConfigurationComplete and movetoaoperationality to True (True) indicating that the core device initial configuration is complete and is made operational.
If the RPD is initiating the handover procedure using the backup core device 120-3, it must send a secondary core device GCP status notification auxcordpstatatus message to the primary core device 120-1. The RPD must set the secondary core device GCP connection status auxcordecpconnectionstatus to "switchover to backup core device initiated by RPD" in the notification message.
In a cable network, a Cable Modem (CM) must be initialized or re-initialized in numerous steps before it can fully operate on a DOCSIS network. This process requires a significant time cost and hardware cost. For example, CM initialization is currently divided into the following sequence of steps:
1. scanning a downstream channel and establishing synchronization with the CMTS;
2. acquiring transmission parameters;
3. measuring the distance;
4. establishing an IP connection;
5. determining the time of day;
6. transmitting operating parameters (downloading configuration files);
7. the CM registers with the CMTS.
Furthermore, if the connection 113 between the remote device 110 and the secondary core device 120-2 is lost, the secondary core device 120-3 does not have the necessary state data and configuration data to manage the RPD of the new connection after the connection is switched to the secondary core device 120-3 because there is no communication channel between the active core device and the backup core device according to the conventional scheme.
As a result, once the GCP handover is completed after the L2TPv3 connection handover, the service will be serviced and all CMSs initially registered with secondary core device 120-2 will have to re-initialize the MAC after detecting the L2TPv3 connection loss. CM MAC initialization time and delay time for detecting L2TPv3 connection loss will be as long as tens of minutes due to contention, RF conditions and large message exchanges, etc. As the number of CMs increases, a significant impact is given to system performance, resulting in connection failure to recover for a long time after switching of the secondary core device.
In view of the above-mentioned problems, as well as other potential problems, existing in conventional approaches, embodiments of the present disclosure provide a method of switching a secondary core device, a core device, and a computer-readable medium. According to the embodiment of the disclosure, the communication channel is established between the active core device and the backup core device, and the device state information associated with the remote device is synchronized to the backup core device, so that after the active core device is switched to the backup core device, the initialization process of the remote device consuming a large amount of time overhead is not required to be performed at the backup core device, thereby reducing the switching time and further improving the system performance. Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.
The principles and implementations of the present disclosure will be described in detail below with reference to fig. 2, which illustrates a process 200 according to an example embodiment of the present disclosure. For discussion purposes, process 200 will be described with reference to fig. 1. Process 200 may involve a handover of a secondary core device.
As described above, the remote device 110 may establish a connection with an active core device (e.g., core device 120-2) and be managed by core device 120-2. A candidate backup secondary core device table, "CandidateBackupCoreTable," is stored at the remote device 110. The remote device 110 can select a core device from the table as a backup core device for the remote device 110, e.g., the remote device 110 may select the first core device in the table as the backup core device. It should be appreciated that the remote device 110 may select any one of the core devices in the table as the backup core device.
For example, the remote device 110 selects the core device 120-3 as its backup core device. To establish a connection between the active core device and the backup core device, the remote device 110 sends 205 information about the backup core device of the remote device 110 to the core device 120-2. For example, the remote device 110 may notify the core device 120-2 that the backup core device of the remote device 110 is the core device 120-3.
Once the core device 120-2 knows the information about the backup core device of the remote device 110, the core device 120-2 establishes a connection with the backup core device, i.e., the core device 120-3. Herein, the term "connected" may be regarded as the above-mentioned GCP. The GCP encapsulation protocol ([ CM-SP-GCP ]) is introduced into the remote physical layer protocol for initial configuration from the CCAP core device to the remote device ([ CM-SP-R-PHY ]). It is reliable and efficient enough to synchronize state data between CCAP core devices because the data size is small and not overloaded often.
After establishing the connection, core device 120-2 may send 210 device status information associated with remote device 110 to core device 120-3 via the connection. In some embodiments, the device state information may include at least one of a cable modem registration status, a cable modem media access control address, a security identifier, a traffic flow list, a set of cable modem transmission channels, and a multicast data set identification forwarding mode.
In some embodiments, the core device 120-2 sending device state information associated with the remote device to the core device 120-3 may be after the core device 120-2 becomes aware of the change in state of the remote device 110. For example, core device 120-2 detects that a cable modem registration or deregistration occurs with remote device 110; at least one of a change, an addition, and a deletion of a dynamic service, and a dynamic channel change.
In some embodiments, core device 120-2 may send a notification message "notify message" to core device 120-3 to indicate that core device 120-2 is sending device status information to core device 120-3 to enable core device 120-3 to synchronize regarding the device status information. The message may include, for example, an event code of "0x02", which indicates that the state synchronization of the cable modem is started or is in progress. The message may also include, for example, a Status indication "Status = Nst" indicating that the remote device is connected.
In some embodiments, if the state data to be synchronized by the core device 120-2 is multiple GCP notification messages, an event code of "0x02" needs to be sent. In the last GCP notification message with synchronization status data, the core device 120-2 may set an event code "0x03" to indicate that synchronization has been completed.
In some embodiments, the core device 120-3 may synchronize only device state information that changes, such as affected CM state data.
Upon failure of the connection between the remote device 110 and the core device 120-2 or loss of power to the core device 120-2 itself, the remote device 110 will perform a handoff from the core device 120-2 to the core device 120-3. For example, the remote device 110 sends 215 a handoff notification to the core device 120-3. Once the core device 120-3 accepts the switch operation and sends 220 a corresponding indication of acceptance of the switch to the remote device, the core device 120-3 may then manage the remote device 110 based on the device state information associated with the remote device 110 that was previously synchronized from the core device 120-2.
In some embodiments, the core device 120-3 can receive reference information associated with the remote device 110 from the remote device 110, which may indicate, for example, target state information after the remote device switches from a backup core device to an active core device. Based on the target status information, the core device 120-3 may determine 225 whether previously received device status information is available. For example, the core device 120-3 may determine whether the CM status data in the target reference information matches the device status information previously received from the core device 120-2. Due to the abrupt interruption of the connection between the remote device 110 and the core device 120-2, there may be a change in the state of the remote device 110 after the interruption of the connection, as described above, and the change in these states cannot be synchronized to the core device 120-3 through the core device 120-2. If the core device 120-3 determines that previously received device status information is available, the core device 120-3 activates the status data in the device status information and processes the affected CM into a registered state. If the core device 120-3 determines that the previously received device state information is not available, i.e., the state data in the previously received device state information is in a non-synchronized state with the state data in the target state information, the core device 120-3 retains the state data but discards all data traffic. While the core device 120-3 sends error responses to or receives MAC messages from the affected CMs.
Once the core device 120-3 determines that previously received device status information is available and activates the status data in the device status information, the core device 120-3 may send 230 an initial configuration complete indication to the remote device. The remote device 110 may notify 235 the primary core device 120-1 that the handoff of the secondary core device has been completed.
In some embodiments, core device 120-2 may be restarted and remote device 110 is to be switched back from core device 120-3 to core device 120-2. For example, remote device 110 may notify core device 120-3 that core device 120-2 is the first backup core device in the backup secondary core list and instruct to switch the connection back to core device 120-2.
Similar to the handover procedure described above, the core device 120-3 may establish a GCP connection with the core device 120-2. Via this connection, the core device 120-2 may obtain state data existing at the core device 120-3 from the core device 120-3. The device status information may be sent 240 by the core device 120-3 to the core device 120-2 via a notification message "NotifyMessage," for example. An event code "0x00" may be added to the message, for example, indicating that state data existing at the core device 120-3 is beginning or proceeding with state data existing at the core device 120-3. In addition, an event code "0x01" may be added to the message, for example, indicating that the existing state data synchronization at the core device 120-3 is completed.
In some embodiments, once the device state information associated with the remote device 110 changes, it may be sent 245 by the core device 120-3 to the core device 120-2 via a notification message "NotifyMessage". This process is the same as the synchronization of the device status information sent by the core device 120-2, and therefore will not be described again.
In this way, the huge time overhead and hardware cost caused by synchronizing the device state information related to the remote device in the switching process of the auxiliary core device can be effectively reduced.
Fig. 3 shows a flow diagram of a communication method 300 according to an embodiment of the present disclosure. In some embodiments, the method 300 may be implemented by the core device 120-2 in the communication network 100, e.g., may be implemented by a processor or processing unit of the core device 120-2. In other embodiments, method 300 may also be implemented by a computing device separate from core device 120-2, or may be implemented by other elements in communication network 100. For ease of discussion, the method 300 will be discussed in conjunction with FIG. 1.
At 310, the core device 120-2 receives information about the core device 120-3 from the remote device 110. At 320, core device 120-2 establishes a connection with core device 120-3.
At 330, the core device 120-2 sends device state information associated with the remote device 110 to the core device 120-3 via the connection to enable the core device 120-3 to manage the remote device 110 based on the device state information after the remote device 110 is handed off from the core device 120-2 to the core device 120-3.
In some embodiments, the device state information may include at least one of a cable modem registration status, a cable modem media access control address, a security identifier, a traffic flow list, a set of cable modem transmission channels, and a multicast data set identification forwarding mode.
In some embodiments, device status information is sent to the core device 120-3 if the core device 120-2 detects at least one of a status change of the remote device 110, which may include the cable modem being registered or unregistered; at least one of a change, an addition, and a deletion of a dynamic service, and a dynamic channel change.
In some embodiments, core device 120-2 may add a start indication at a start position of the device status information to indicate a start of transmission of the device status information or an end indication at an end position of the device status information to indicate an end of transmission of the device status information.
In some embodiments, if the core device 120-2 is re-enabled, the core device 120-2 can receive device state information associated with the remote device 110 from the core device 120-3 to enable the core device 120-2 to re-manage the remote device 110 based on the device state information after the remote device 110 is handed off from the core device 120-3 to the core device 120-2.
In some embodiments, core device 120-2 and core device 120-3 are secondary core devices that are converged with a wired access platform.
Fig. 4 shows a flow diagram of a communication method 400 according to an embodiment of the present disclosure. In some embodiments, the method 400 may be implemented by the core device 120-3 in the communication network 100, e.g., may be implemented by a processor or processing unit of the core device 120-3. In other embodiments, method 400 may also be implemented by a computing device separate from core device 120-3, or may be implemented by other elements in communication network 100. For ease of discussion, the method 400 will be discussed in conjunction with FIG. 1.
At 410, the core device 120-3 determines whether a connection with the core device 120-2 is established. If the core device 120-3 determines that a connection with the core device 120-2 has been established, the core device 120-3 receives device status information associated with the remote device 110 from the core device 120-2 at 420.
In some embodiments, the device state information may include at least one of a cable modem registration status, a cable modem media access control address, a security identifier, a traffic flow list, a set of cable modem transmission channels, and a multicast data set identification forwarding mode.
In some embodiments, the core device 120-3 may receive a start indication at a start position of the device status information to indicate a start of transmission of the device status information or an end indication at an end position of the device status information to indicate an end of transmission of the device status information.
At 430, the core device 120-3 manages the remote device 110 based on the device state information after the remote device 110 is handed off from the core device 120-2 to the core device 120-3.
In some embodiments, the core device 120-3 may receive reference information associated with the remote device 110 from the remote device 110, the reference information indicating target state information after the remote device 110 hands off from the core device 120-3 to the core device 120-2. The core device 120-3 may determine whether the received device status information is available based on the reference information and if it is determined that the received device status information is available, the core device 120-3 may manage the remote device 110 based on the received device status information.
In some embodiments, if core device 120-2 is re-enabled, core device 120-3 may send device status information associated with remote device 110 to core device 120-2 via the connection.
In some embodiments, core device 120-2 and core device 120-3 are secondary core devices that are converged with a wired access platform.
In some embodiments, an apparatus (e.g., remote device 120-2) capable of performing method 300 may include respective means for performing the steps of method 300. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit or a software module.
In some embodiments, the apparatus includes means for receiving information about the core device 120-3 from the remote device 110. The apparatus also includes means for establishing a connection with the core device 120-3 and means for sending device status information associated with the remote device 110 to the core device 120-3 via the connection.
In some embodiments, the device state information may include at least one of a cable modem registration status, a cable modem media access control address, a security identifier, a traffic list, a set of cable modem transmission channels, and a multicast data set identification forwarding pattern.
In some embodiments, the means for sending device state information associated with the remote device 110 to the core device 120-3 via the connection includes means for sending device state information to the core device 120-3 if a state change of the remote device 110 is detected, which may include the cable modem being registered or deregistered; at least one of a change, an addition, and a deletion of a dynamic service, and a dynamic channel change.
In some embodiments, the means for sending device status information associated with the remote device 110 to the core device 120-3 via the connection comprises means for adding a start indication at a start position of the device status information or means for adding an end indication at an end position of the device status information.
In some embodiments, the apparatus capable of performing the method 300 further comprises means capable of receiving device state information associated with the remote device 110 from the core device 120-3 if the core device 120-2 is re-enabled, such that the core device 120-2 is capable of re-managing the remote device 110 based on the device state information after the remote device 110 is handed off from the core device 120-3 to the core device 120-2.
In some embodiments, core device 120-2 and core device 120-3 are secondary core devices that are converged with a wired access platform.
In some embodiments, an apparatus (e.g., remote device 120-3) capable of performing method 400 may include respective means for performing the steps of method 400. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit or a software module.
In some embodiments, the apparatus includes means for determining whether a connection with core device 120-2 is established. The apparatus includes means for receiving device state information associated with the remote device 110 from the core device 120-2 if the core device 120-3 determines that a connection with the core device 120-2 has been established, and means for managing the remote device 110 based on the device state information after the remote device 110 is handed off from the core device 120-2 to the core device 120-3.
In some embodiments, the device state information may include at least one of a cable modem registration status, a cable modem media access control address, a security identifier, a traffic list, a set of cable modem transmission channels, and a multicast data set identification forwarding pattern.
In some embodiments, means for receiving device status information associated with the remote device 110 from the core device 120-2 includes means for receiving a start indication at a start location of the device status information or means for receiving an end indication at an end location of the device status information.
In some embodiments, the means for managing the remote device 110 based on the device state information comprises means for receiving, from the remote device 110, reference information associated with the remote device 110, the reference information indicating target state information after a handover of the remote device 110 from the core device 120-3 to said core device 120-2. The means for managing the remote device 110 based on the device state information further comprises means for determining whether the received device state information is available based on the reference information and means for managing the remote device 110 based on the received device state information if it is determined that the received device state information is available.
In some embodiments, an apparatus capable of performing method 400 also includes means for sending device state information associated with remote device 110 to core device 120-2 via the connection if core device 120-2 is re-enabled.
In some embodiments, core device 120-2 and core device 120-3 are secondary core devices that are converged with a wired access platform.
Fig. 5 is a simplified block diagram of a device 500 suitable for implementing embodiments of the present disclosure. Device 500 may be provided to implement communication devices such as remote device 110, core devices 120-2 and 120-3 as shown in fig. 1. As shown, device 500 includes one or more processors 510, one or more memories 540 coupled to processor 510, and one or more transmitters and/or receivers (TX/RX) 540 coupled to processor 510.
TX/RX 540 is used for bi-directional communication. TX/RX 540 has at least one antenna to facilitate communication. A communication interface may represent any interface necessary to communicate with other network elements.
The processors 510 may be of any type suitable to the local technology network, and may include, but are not limited to, one or more of general purpose computers, special purpose computers, microcontrollers, digital signal controllers (DSPs), and controller-based multi-core controller architectures. The device 500 may have multiple processors, such as application specific integrated circuit chips, that are time dependent from a clock synchronized with the main processor.
The computer programs 530 include computer-executable instructions that are executed by the associated processor 510. The program 530 may be stored in the ROM 520. Processor 510 may perform any suitable actions and processes by loading program 530 into RAM 520.
Embodiments of the present disclosure may be implemented by way of program 530 such that device 500 may perform any of the processes of the present disclosure as discussed with reference to fig. 2-4. Embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
In some embodiments, program 530 may be tangibly embodied in a computer-readable medium, which may be included in device 500 (such as in memory 520) or other storage device accessible by device 500. The program 530 may be loaded from a computer-readable medium into the RAM 522 for execution. The computer readable medium may include any type of tangible, non-volatile memory, such as ROM, EPROM, flash memory, a hard disk, a CD, a DVD, etc. Fig. 6 shows an example of a computer-readable medium 600 in the form of a CD or DVD. The computer readable medium has program 530 stored thereon.
In general, the various embodiments of the disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device. While various aspects of the embodiments of the disclosure are illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product comprises computer executable instructions, such as instructions included in program modules, that are executed in a device on a target real or virtual processor to perform the methods 300 and 400 described above with reference to fig. 2-4. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as desired. Machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed facility, program modules may be located in both local and remote memory storage media.
Computer program code for implementing the methods of the present disclosure may be written in one or more programming languages. These computer program codes may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the computer or other programmable data processing apparatus, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. The program code may execute entirely on the computer, partly on the computer, as a stand-alone software package, partly on the computer and partly on a remote computer or entirely on the remote computer or server.
In the context of the present disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations described above. Examples of a carrier include a signal, computer readable medium, and the like. Examples of signals may include electrical, optical, radio, acoustic, or other forms of propagated signals, such as carrier waves, infrared signals, and the like.
The computer readable medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More detailed examples of a computer-readable storage medium include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical storage device, a magnetic storage device, or any suitable combination thereof.
Further, while the operations of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Rather, the steps depicted in the flowcharts may change order of execution. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions. It should also be noted that the features and functions of two or more devices according to the present disclosure may be embodied in one device. Conversely, the features and functions of one apparatus described above may be further divided into embodiments by a plurality of apparatuses.
While the present disclosure has been described with reference to several particular embodiments, it is to be understood that the disclosure is not limited to the particular embodiments disclosed. The disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (18)
1. A method for switching core devices of a converged cable access platform, wherein the core devices include an active core device and one or more backup core devices, the method comprising:
receiving, at the active core device managing a remote device that is signaling a physical layer translator, information from the remote device regarding a backup core device of the remote device, wherein the one or more backup core devices are stored in a list at the remote device, the remote device selecting one backup core device from the list as a backup core device for the remote device;
establishing a connection between the active core device and the backup core device; and
sending device state information associated with the remote device to the backup core device via the connection to enable the backup core device to manage the remote device based on the device state information after the remote device switches from the active core device to the backup core device.
2. The method of claim 1, wherein the device status information comprises at least one of:
the status of the cable modem registration is such that,
the cable modem media access control address,
the security identifier is a unique identifier that is unique to the security identifier,
a list of the service flows is displayed,
set of cable modem transmission channels, and
the multicast data set identifies the forwarding mode.
3. The method of claim 1, wherein sending the device state information comprises:
in response to detecting a change in state of the remote device of at least one of:
the cable modem is registered;
the cable modem is logged off;
dynamic service change;
dynamic service addition;
dynamic service deletion; and
dynamic channel changes.
4. The method of claim 1, wherein sending the device status information comprises at least one of:
adding a start indication at a start position of the device status information to indicate a start of transmission of the device status information; and
adding an end indication at an end location of the device status information to indicate an end of the transmission of the device status information.
5. The method of claim 1, further comprising:
in response to the active core device being re-enabled, receiving device state information associated with the remote device from the backup core device via the connection to enable the active core device to re-manage the remote device based on the device state information upon a handover of the remote device from the backup core device to the active core device.
6. The method of any preceding claim, wherein the active core device and the backup core device are secondary core devices of a converged wired access platform.
7. A method for switching core devices of a converged cable access platform, wherein the core devices include an active core device and one or more backup core devices, the method comprising:
receiving, at a backup core device that is a physical layer translator transmitting a signal remote device, device state information associated with the remote device from the active core device in response to a connection between the backup core device and the active core device managing the remote device having been established, wherein the one or more backup core devices are stored in a list at the remote device, the remote device selecting a backup core device from the list as a backup core device for the remote device; and
managing the remote device based on the device state information after the remote device switches from the active core device to the backup core device.
8. The method of claim 7, wherein synchronizing the device state information comprises synchronizing at least one of:
the cable modem is in a registration state and,
the cable modem media access control address,
the security identifier is a unique identifier that is unique to the security identifier,
a list of the service flows is displayed,
set of cable modem transmission channels, and
the multicast data set identifies a forwarding mode.
9. The method of claim 7, wherein receiving the device state information comprises:
receiving a start indication at a start position of the device status information, the start indication indicating a start of transmission of the device status information; and
receiving an end indication at an end location of the device status information, the end indication indicating an end of the transmission of the device status information.
10. The method of claim 7, wherein managing the remote device comprises:
receiving reference information associated with the remote device from the remote device, the reference information indicating target state information after the remote device switches from the backup core device to the active core device;
determining whether the received device status information is available based on the reference information; and
in response to determining that the received device state information is available, managing the remote device based on the received device state information.
11. The method of claim 7, further comprising:
sending device state information associated with the remote device to the active core device via the connection in response to the active core device being re-enabled.
12. The method of any of the preceding claims, wherein the active core device and the backup core device are secondary core devices that are converged cable access platforms.
13. An apparatus for switching a core device converged cable access platform, comprising:
at least one processor; and
at least one memory including computer program instructions, the at least one memory and the computer program instructions configured to, with the at least one processor, cause the apparatus to perform the method of any of claims 1-6.
14. An apparatus for switching core devices of a converged cable access platform, comprising:
at least one processor; and
at least one memory including computer program instructions, the at least one memory and the computer program instructions configured to, with the at least one processor, cause the apparatus to perform the method of any of claims 7-12.
15. An apparatus for switching core devices converged with a wired access platform, wherein the core devices include an active core device and one or more backup core devices, the apparatus comprising:
means for receiving, at the active core device managing a remote device as a physical layer translator transmission signal, information from the remote device regarding a backup core device of the remote device, wherein the one or more backup core devices are stored in a list at the remote device, the remote device selecting one backup core device from the list as a backup core device for the remote device;
means for establishing a connection between the active core device and the backup core device; and
means for sending device state information associated with the remote device to the backup core device via the connection to enable the backup core device to manage the remote device based on the device state information upon a handover of the remote device from the active core device to the backup core device.
16. An apparatus for switching core devices converged with a wired access platform, wherein the core devices include an active core device and one or more backup core devices, the apparatus comprising:
means for receiving, at a remote device backup core device that is transmitting a signal as a physical layer translator, device state information associated with the remote device from the active core device in response to a connection between the backup core device and the active core device that manages the remote device having been established, wherein the one or more backup core devices are stored in a list at the remote device, the remote device selecting one backup core device from the list as a backup core device for the remote device; and
means for managing the remote device based on the device state information after the remote device switches from the active core device to the backup core device.
17. A computer-readable medium having stored thereon computer-executable instructions for execution by a processor to implement the method of any one of claims 1-6.
18. A computer-readable medium having stored thereon computer-executable instructions for execution by a processor to implement the method of any one of claims 7-12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910229411.0A CN111741501B (en) | 2019-03-25 | 2019-03-25 | Method, device and apparatus for switching core device and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910229411.0A CN111741501B (en) | 2019-03-25 | 2019-03-25 | Method, device and apparatus for switching core device and computer readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111741501A CN111741501A (en) | 2020-10-02 |
| CN111741501B true CN111741501B (en) | 2023-02-28 |
Family
ID=72646253
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910229411.0A Active CN111741501B (en) | 2019-03-25 | 2019-03-25 | Method, device and apparatus for switching core device and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111741501B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN201690566U (en) * | 2010-06-03 | 2010-12-29 | 中兴通讯股份有限公司 | Video monitoring apparatus and integrated service access network |
| CN102185842A (en) * | 2011-04-25 | 2011-09-14 | 工业和信息化部电信传输研究所 | Communication system and method of converged network |
| CN102255892A (en) * | 2011-06-17 | 2011-11-23 | 苏州汉明科技有限公司 | Enterprise network system supporting wireless access and remote access |
| CN103414919A (en) * | 2013-08-05 | 2013-11-27 | 中延联科技(北京)有限责任公司 | Method for overall conversion and three-network integration of digital television |
| CN103535016A (en) * | 2011-05-09 | 2014-01-22 | 瑞典爱立信有限公司 | Hitless switchover from active tcp application to standby tcp application |
| CN103765931A (en) * | 2011-08-26 | 2014-04-30 | 高通股份有限公司 | Methods and apparatus for improving management of NFC logical connections |
| CN103843448A (en) * | 2011-10-07 | 2014-06-04 | 诺基亚公司 | Method and apparatus for managing terminals |
| CN104885449A (en) * | 2012-11-12 | 2015-09-02 | 加速有限公司 | Virtual converged cable access platforms for HFC cable networks |
| CN106575971A (en) * | 2014-08-01 | 2017-04-19 | 华为技术有限公司 | Interference cancellation in coaxial cable connected data over cable service interface specification (DOCSIS) system or cable network |
| WO2018013443A1 (en) * | 2016-07-11 | 2018-01-18 | Harmonic, Inc. | Multiple core software forwarding |
| CN108809615A (en) * | 2017-04-10 | 2018-11-13 | 思科技术公司 | Full duplex resource allocation in cable network environment |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8935739B1 (en) * | 2010-01-22 | 2015-01-13 | Gainespeed, Inc. | Distributed CCAP cable modem termination system |
| US8311412B2 (en) * | 2010-01-22 | 2012-11-13 | Selim Shlomo Rakib | Distributed cable modem termination system |
| US9584869B2 (en) * | 2010-01-22 | 2017-02-28 | Gainspeed, Inc. | Virtual CCAP cable modem termination system with software reconfigurable MAC |
| US20130125194A1 (en) * | 2011-11-15 | 2013-05-16 | Harmonic Inc. | Converged Cable Access Platform for Provision of Video and Data Services |
| US9032468B2 (en) * | 2013-03-15 | 2015-05-12 | Arris Technology, Inc. | CATV video and data transmission system with automatic dispersion compensation |
| US9614618B2 (en) * | 2013-03-15 | 2017-04-04 | Arris Enterprises, Inc. | CATV video and data transmission system with hybrid input |
| WO2017147086A1 (en) * | 2016-02-22 | 2017-08-31 | Harmonic, Inc. | Virtual converged cable access platform (ccap) core |
-
2019
- 2019-03-25 CN CN201910229411.0A patent/CN111741501B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN201690566U (en) * | 2010-06-03 | 2010-12-29 | 中兴通讯股份有限公司 | Video monitoring apparatus and integrated service access network |
| CN102185842A (en) * | 2011-04-25 | 2011-09-14 | 工业和信息化部电信传输研究所 | Communication system and method of converged network |
| CN103535016A (en) * | 2011-05-09 | 2014-01-22 | 瑞典爱立信有限公司 | Hitless switchover from active tcp application to standby tcp application |
| CN102255892A (en) * | 2011-06-17 | 2011-11-23 | 苏州汉明科技有限公司 | Enterprise network system supporting wireless access and remote access |
| CN103765931A (en) * | 2011-08-26 | 2014-04-30 | 高通股份有限公司 | Methods and apparatus for improving management of NFC logical connections |
| CN103843448A (en) * | 2011-10-07 | 2014-06-04 | 诺基亚公司 | Method and apparatus for managing terminals |
| CN104885449A (en) * | 2012-11-12 | 2015-09-02 | 加速有限公司 | Virtual converged cable access platforms for HFC cable networks |
| CN103414919A (en) * | 2013-08-05 | 2013-11-27 | 中延联科技(北京)有限责任公司 | Method for overall conversion and three-network integration of digital television |
| CN106575971A (en) * | 2014-08-01 | 2017-04-19 | 华为技术有限公司 | Interference cancellation in coaxial cable connected data over cable service interface specification (DOCSIS) system or cable network |
| WO2018013443A1 (en) * | 2016-07-11 | 2018-01-18 | Harmonic, Inc. | Multiple core software forwarding |
| CN108809615A (en) * | 2017-04-10 | 2018-11-13 | 思科技术公司 | Full duplex resource allocation in cable network environment |
Non-Patent Citations (2)
| Title |
|---|
| Daniel R. McMahill ; Dwaine S. Hurta ; Brian Brandt ; Miaochen Wu ; ."A 160 Channel QAM Modulator With 4.6 Gsps 14 Bit DAC".《IEEE Journal of Solid-State Circuits》.2014,全文. * |
| 李丹 ; 陈贵海 ; 任丰原 ; 蒋长林 ; 徐明伟."数据中心网络的研究进展与趋势".《计算机学报》.2014,全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111741501A (en) | 2020-10-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10140112B2 (en) | Update management system and update management method | |
| EP1220467B1 (en) | Reliability enhancement for cable modem service | |
| CN110545138A (en) | Information indication method and device and computer readable storage medium | |
| CN102143138A (en) | Method and device for configuring virtual local area network (VLAN) in live migration process of virtual machine | |
| US20200022195A1 (en) | Association Management Method And Network Node | |
| US11611787B1 (en) | Systems and methods for signaling host devices via a broadcast channel with grouping filters | |
| CN110611690B (en) | Method for master core device reselection, remote device and computer readable medium | |
| US20210119866A1 (en) | Configuration Control for Network | |
| US20120151532A1 (en) | Sdv quick tune algorithm | |
| US9485527B2 (en) | Hybrid resource management system and method | |
| CN111741501B (en) | Method, device and apparatus for switching core device and computer readable medium | |
| WO2017063445A1 (en) | Method of redirecting terminal equipment to dedicated network, terminal equipment and base station | |
| CN104507054A (en) | Group member information updating method and related devices | |
| US9832535B2 (en) | Remote control video modulator | |
| CN110958280B (en) | Method for switching auxiliary core device, remote device and computer readable medium | |
| CN114143569B (en) | Webpage recording and live broadcasting method and system | |
| CN113783768B (en) | Group control method, group control device and communication system | |
| US20070254617A1 (en) | Method and device for power management | |
| KR101982333B1 (en) | Access point apparatus, and control method thereof | |
| CN111988205B (en) | Method for serving remote physical equipment and core proxy equipment | |
| US9479353B2 (en) | Selective reestablishment of cable modem internet protocol connectivity | |
| CN102438170B (en) | Audio and video service on demand method applied to broadcast television network, system thereof and apparatus | |
| EP3032824B1 (en) | Method for automatic tracking of hybrid fiber coaxial upstream service upgrades | |
| CN104852837B (en) | Method and device for switching multiple control centers in home network and control center | |
| Kim et al. | ATSC 3.0 broadcast gateway virtualization system based on VNF |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |