WO2015101100A1 - 网络设备及网络中的业务处理方法 - Google Patents

网络设备及网络中的业务处理方法 Download PDF

Info

Publication number
WO2015101100A1
WO2015101100A1 PCT/CN2014/090209 CN2014090209W WO2015101100A1 WO 2015101100 A1 WO2015101100 A1 WO 2015101100A1 CN 2014090209 W CN2014090209 W CN 2014090209W WO 2015101100 A1 WO2015101100 A1 WO 2015101100A1
Authority
WO
WIPO (PCT)
Prior art keywords
control unit
service
unit
working group
main control
Prior art date
Application number
PCT/CN2014/090209
Other languages
English (en)
French (fr)
Inventor
郑宗钊
柳强
张艳华
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2015101100A1 publication Critical patent/WO2015101100A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34Signalling channels for network management communication
    • H04L41/344Out-of-band transfers

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a network device and a service processing method in a network.
  • Network communication devices play an increasingly important role as carriers of data and information.
  • the network device provides an interface between the network side and the user side through different types of units, and is connected between the network side and the user side. According to the different functions of each unit, it is divided into control unit, business unit and uplink interface unit.
  • the service unit includes at least one service board.
  • the control unit is configured to control the service unit and the uplink interface unit to perform services corresponding to the service unit.
  • the network device can support only one type of service, and cannot support multiple different types of services.
  • the embodiment of the invention provides a network device and a service processing method in the network, so as to solve the problem that the network device cannot support multiple different types of services in the prior art.
  • an embodiment of the present invention provides a network device, which is used to connect multiple terminal devices.
  • the network device includes a first uplink interface unit (503), a main control unit (504), a first service unit (505), a second uplink interface unit (506), a standby control unit (507), and a second service unit (508).
  • the first uplink interface unit (503), the main control unit (504), and the first service unit (505) form a first working group (501) for connecting a part of the plurality of terminal devices;
  • the second uplink interface unit (506), the standby control unit (507), and the second service unit (508) form a second working group (502) for connecting the remaining part of the plurality of terminal devices;
  • the first working group (501) is configured to process a service between the connected terminal device and the network side under the control of the main control unit (504);
  • the second working group (502) is configured to process the service between the connected terminal device and the network side under the control of the standby control unit (507).
  • a management channel is disposed between the main control unit (504) and the standby control unit (507), and the management channel is used for The master unit (504) manages the second work group (502).
  • the first working group (501) and the second working group (502) are respectively connected to different network management devices.
  • a management channel is disposed between the main control unit (504) and the standby control unit (507)
  • the management channel is used by the main control unit (504) to manage the second working group (502).
  • the device identifier of the master control unit (504) is different from the device identifier of the standby control unit (507).
  • the device identifier includes an IP address or a media access control MAC address.
  • the first to the fifth possible implementation manners of the first aspect in the sixth possible implementation manner of the first aspect, the first working group (501) and the second working group (502) The type of business being processed is different.
  • the network device is a digital subscriber line access multiplexer DSLAM or an optical line Terminal OLT.
  • an embodiment of the present invention provides a service processing method in a network, where the network includes a network device and a plurality of terminal devices, where the network device includes a first uplink interface unit (503) and a main control unit (504). a first service unit (505), a second uplink interface unit (506), a standby control unit (507), and a second service unit (508), the method comprising:
  • the network device and the service processing method in the network in the embodiment of the present invention divide the network device into at least two working groups each including one control unit, and control the corresponding working groups to run different types through the control units in different working groups.
  • the business so that the network device can support a variety of different types of services.
  • FIG. 1 is a schematic structural diagram of a network device according to Embodiment 1 of the present invention.
  • FIG. 2 is a flowchart of a service processing method in a network according to Embodiment 2 of the present invention
  • FIG. 3 is a flowchart of a service processing method in a network according to Embodiment 3 of the present invention.
  • FIG. 4 is a flowchart of a service processing method in a network according to Embodiment 4 of the present invention.
  • FIG. 5 is a flowchart of a method for activating a work group according to Embodiment 4 of the present invention.
  • FIG. 6 is a flowchart of a service processing method in a network according to Embodiment 5 of the present invention.
  • FIG. 7 is a schematic structural diagram of a network device according to Embodiment 6 of the present invention.
  • FIG. 1 is a schematic structural diagram of a network device according to Embodiment 1 of the present invention.
  • the network device can be connected to multiple terminal devices, and the network device provided includes an uplink interface unit 503 and a main control unit 504.
  • the uplink interface unit 503, the main control unit 504, and the first service unit 505 are configured as a first working group 501, and a part of the plurality of terminal devices is connected through the first working group 501.
  • the service between the connected terminal device and the network side is processed by the first working group 501 under the control of the unit 504;
  • the uplink interface unit 506, the standby control unit 507, and the service unit 508 in the network device are configured as a second working group 502, and the remaining part of the plurality of terminal devices is connected through the second working group 502 under the control of the standby control unit 507.
  • the service between the connected terminal device and the network side is processed by the second working group 502.
  • the main control unit 504 can implement the control of the second working group by controlling the standby control unit 507.
  • the management channel can be set between the main control unit 504 and the standby control unit 507, and the main control unit 504 can be modified.
  • the management channel implements control of the second working group.
  • the first working group 501 can be separately managed from the second working group 502, for example, different network management devices and the like are separately connected, and in this architecture, the main control unit 504 and the standby device can also be used.
  • a management channel is set between the control unit 507, and the second working group 502 can also be managed by the main control unit 504, thereby implementing dual management of the second working group 502.
  • the first working group 501 and the second working group 502 can independently process the services of different users. Therefore, the device identifiers of the main control unit 504 and the standby control unit 507 can be different, and the device identifier can specifically include an IP address. Or MAC (Media Access Control) address, etc.
  • the service types processed by the first working group 501 and the second working group 502 may be different or the same.
  • the network device provided in this embodiment may be a DSLAM (Digital) Subscriber Line Access Multiplexer, Digital Subscriber Line Access Multiplexer, or OLT (Optical Line Terminal) access device, of course, other network devices, such as routing devices and terminal devices.
  • DSLAM Digital
  • OLT Optical Line Terminal
  • the network device provided in this embodiment can connect different terminal devices by setting the existing active and standby links into independent working groups, so that the hardware resources of the network device can be fully utilized, and different working groups can handle different types of services. Therefore, the ability of the network device to process the service can be improved.
  • FIG. 2 is a flowchart of a service processing method in a network according to Embodiment 2 of the present invention.
  • the method in this embodiment is applicable to a situation in which different users carried by a network device need to run different types of services.
  • the method in this embodiment specifically includes the following steps:
  • Step 201 The network device is divided into a first working group and a second working group according to the pre-configuration information, where the first working group and the second working group include a control unit, an uplink interface unit, and a service unit.
  • the working group and the second working group are connected to different users;
  • the control unit of the first working group is a master control unit, and the control unit of the second working group is a standby control unit;
  • the master control unit is configured to pass the standby control unit The unit performs control to control the second working group.
  • Step 202 The first working group and the second working group run different types of services under the control of respective control units.
  • the division of the working group by the network device according to the pre-configuration information is actually that the unit modules in the network device are connected and configured, so that the units in one working group are connected.
  • the division of the working group on the network device may be performed by online division or offline division.
  • online means that the corresponding control unit is connected to each control unit in the network device.
  • the unit module offline means that the corresponding unit module is not connected to each control unit in the network device.
  • the network is divided, the network device is connected and divided according to the pre-configuration information and the identifier of each unit module; if it is offline, according to the pre-configuration information and the reserved location of each unit module on the control unit,
  • the network device performs connection division. It should be noted that, for off-line division, before the two work groups after the division run different types of services, the corresponding unit modules need to be inserted in corresponding positions on the control unit.
  • the network device comprises two control units such that the divided working groups each have a control unit.
  • the first working group and the second working group, the two working groups each include a control unit, an uplink interface unit, and a service unit, that is, the two working groups are each equivalent to an independent device.
  • Each of the two working groups can provide service configuration parameter information of the work group to the service unit, and process, exchange, and aggregate the corresponding service data according to the service configuration information.
  • the control unit can also provide configuration and management of the routing protocol for the working group.
  • the first working group and the second working group respectively connect different users, and the business requirements of different users are provided by their respective control units due to the service configuration parameters of the two working groups, so that the first The working group and the second working group perform corresponding types of services according to the service configuration parameters of the respective control units.
  • the network device is divided into two working groups, which respectively include a control unit, an uplink interface unit, and a service unit, and the control units in the two working groups respectively control the corresponding working group to run different types of services. So that the network device can support a variety of different types of services.
  • FIG. 3 is a flowchart of a service processing method in a network according to Embodiment 3 of the present invention.
  • the network device includes a main control board and a standby control board.
  • the control unit is a control board
  • the standby control unit is a standby control board.
  • the device includes two uplink interface boards and at least two service boards.
  • the network device is divided into the first working group and the second working group according to the pre-configuration information in the step 201, as follows:
  • Step 301 Configure an interface board of the two uplink interface boards as the first uplink interface unit according to the service type, and configure the uplink interface unit of the first working group as another interface board of the two uplink interface boards.
  • the second uplink interface unit is configured as an uplink interface unit of the second working group; at least one service board of the at least two service boards is configured as a first service unit, and at least one of the at least two service boards is included
  • the service board outside the service board is configured as the second service unit.
  • network devices In order to maintain the stable operation requirements of network devices, network devices usually support active/standby mode.
  • the main control board and the standby control board are included. If the network device is in the active/standby mode, the main control board controls the network device to communicate with the outside to ensure normal operation of each unit module; the standby control board has no service communication with the outside and does not bear any traffic load.
  • the main control board and the standby control board have the same configuration information during normal operation. Once the main control board fails, the standby control board is replaced to maintain normal service. That is to say, the current network device has at least two control boards, that is, a main control board and a standby control board.
  • the solution in this embodiment preferably divides the network device into two working groups, namely, a first working group and a second working group.
  • the main control board can be used as a main control unit, and can be a control unit configured as the first working group or a control unit configured as the second network device. If the main control unit is the control unit of the first working group, the standby control unit is used as the control unit of the second working group, because the main control unit is in the working group On the basis of the control of the unit modules, the second working group can also perform service allocation, management and information configuration by controlling the standby control unit.
  • the network device is divided into a first working group and a second working group, where the first working group and the second working group respectively have different user groups, for example, the first working group corresponds to the enterprise user group, and the second The working group corresponds to the general user group.
  • the uplink interface board provides a network interface to connect with the network side; the service board provides a user interface to implement access, processing, and forwarding of user services.
  • a service board in the network device has at least one user interface, and can access at least one user, and the user service requirements of the user accessing the same service board are the same.
  • the control unit of the first working group is the main control unit
  • the control unit of the second working group is the standby control unit
  • an uplink interface unit is further configured for the first working group and the second working group respectively, according to
  • the service type is divided into two parts, that is, the first service unit and the second service unit, where the service type carried by the service board of the first service unit and the service board of the second service unit are The types of services carried are different.
  • the method further includes:
  • Step 302 Determine whether there is a coupling in the configuration corresponding to the first working group and the second working group in the pre-configuration information. If it is (Y), step 303 is performed; if not (N), step 304 is performed.
  • the configuration coupling determined in this step refers to the connection coupling of the unit modules in the pre-configuration information.
  • the same unit module such as an uplink interface unit or a service unit, can only correspond to one control unit.
  • the uplink interface unit that carries the different services has the service information and hardware configuration requirements corresponding to the different services, and the service units with different service requirements have the service transmission channels corresponding to the different services.
  • the service business unit and uplink interface unit need to be configured in the same work Within the group, if there is a cross configuration, there is a coupling.
  • Step 303 Modify the pre-configuration information to release the coupling; and divide the network device into the first working group and the second working group according to the modified pre-configuration information.
  • the network device needs to be divided into working groups after the contact coupling.
  • Step 304 According to the pre-configuration information, divide the network device into the first working group and the second working group.
  • the solution of the embodiment is to divide the working group on the basis of the internal structure and the network architecture of the existing network device, so as to better ensure the normal operation of the divided working group, and perform connection coupling before the working group runs the service. Judgment, so as to better guarantee the normal transmission of business data.
  • FIG. 4 is a flowchart of a service processing method in a network according to Embodiment 4 of the present invention. As shown in FIG. 4, before the first working group and the second working group run different types of services under the control of the respective control units, the method includes:
  • Step 401 Activate the first working group and the second working group.
  • At least the divided work group should be activated before running the corresponding service.
  • the method further includes:
  • Step 402 Determine whether the device identity conflict exists between the main control unit and the standby control unit.
  • Step 403 If the main control unit and the standby control unit have a device identifier conflict, the main control unit sends a new device identifier to the standby control unit.
  • the same device ID is configured for the main control board and the standby control board to ensure that the standby control board can work normally.
  • the connected uplink interface board and service board can be accurately identified to accurately process service information.
  • different work groups are identified according to different control boards, that is to say the device identification of the control unit. Therefore, in this embodiment, before the at least two work groups are activated to run the service, it is first ensured that the at least two work groups do not have an identity conflict.
  • the control unit corresponding to the at least two working groups has the same device identifier
  • the master control unit that is, the main control board
  • the standby control unit can be delivered to the standby control board through the active and standby management channels.
  • the device identifier includes an Internet Protocol (IP) address or a Media Access Control (MAC) address;
  • IP Internet Protocol
  • MAC Media Access Control
  • the main control unit sends a new device identifier to the standby control unit, which specifically includes:
  • the main control unit sends the identification change information to the standby control unit, so that the standby control unit acquires new IP address information according to the identification change information, or restores the default MAC of the standby control unit according to the identification change information. address.
  • the identification change message includes a new IP address, or a change indication message.
  • the master control unit may send the new IP address to the standby control unit by using the identifier change message, or the standby control unit may actively generate a new IP address after receiving the identifier change message. And inform the main control unit.
  • the identity change message further includes a default recovery indication message. Due to the MAC address of the device or unit, it is unique for the manufacturer to burn the hardware address inside it during the production process. However, for the network device in the active/standby mode, in order to make the main control board and the standby control board have the same MAC address, the standby control board virtualizes the same MAC address as the main control board. In this embodiment, the standby control unit receives the default recovery indication message sent by the main control unit, and restores the device identifier of the backup control unit to a default MAC address, that is, a unique factory MAC address. .
  • FIG. 5 is a flowchart of a method for activating a work group according to Embodiment 4 of the present invention. As shown in FIG. 5, further, the first working group and the second working group are activated in step 401 in the foregoing solution, which specifically includes:
  • Step 401a The main control unit sends the identification information of the standby control unit to the second uplink interface unit and the second service unit.
  • the identification information may be an IP address or a MAC address. Because the unit module in the divided working group has not been restarted at this time, the master control unit may send the identification information to the active/standby management channel between the main control unit and the standby control unit. The second uplink interface unit and the second service unit, so that after the unit module in the second working group is restarted, the second uplink interface unit and the second service unit can establish a communication connection with the standby unit.
  • Step 401b Restart the standby control unit, the second uplink interface unit, and the second service unit respectively.
  • the standby control unit, the second uplink interface unit, and the standby control board, the uplink interface board, and the service board corresponding to the second service unit are respectively connected as independent boards.
  • the restart function is implemented on each board by selecting the restart operation software to control the restart of the boards. You can also restart by pressing the restart button on each board.
  • Step 401c The main control unit closes a connection port with the second uplink interface unit and the second service unit.
  • each uplink interface unit and service unit in the network device are connected to the main control unit, but for the first working group and the second working group, the correct transmission of the service data is ensured.
  • the uplink interface unit and the service unit can only be connected to the control unit in the work group to which they are configured. Since the second uplink interface unit and the second service unit are units of the second working group, the main control unit needs to close the connection therewith.
  • Step 401d After the restarting of the standby control unit is completed, the standby control unit establishes a working group management channel with the main control unit; the working group management channel is used to deliver the service configuration information delivered by the main control unit to the The standby control unit is configured to close the connection port of the first uplink interface unit and the first service unit after receiving the service configuration information.
  • the standby control unit Since the standby control unit, the second uplink interface unit, and the second service unit are both restarted as boards, the restart time services of different boards are different due to different internal structures and restart processes.
  • the main control unit resumes communication with the standby control unit, that is, the main control unit can perform data transmission with the standby control unit.
  • the standby control unit interrupts the communication connection with the unit module during the restarting process.
  • the standby control unit attempts to re-establish a connection with the main control unit by sending a setup request message to the main control unit.
  • the main control unit receives the request message sent by the standby control unit, and establishes a two-way communication connection with the standby control unit, and the communication connection is the work management channel.
  • the main control unit can send the service configuration information to the standby control unit by using the work management channel, where the service configuration information includes the second work group running corresponding service, the standby control unit, the second uplink interface unit, and the second Parameter information to be configured for the business unit.
  • the control unit confirms that the service corresponding to the second working group is different from the service type corresponding to the first working group, and learns that the network device is in the working group burden mode, instead of the active/standby mode,
  • the standby control unit also needs to close the connection port of the first uplink interface unit and the first service unit, thereby ensuring accurate transmission of service data.
  • the standby control unit may periodically detect the status of the working management channel during the running of the service, such as discovering the interruption of the channel transmission, and recording and analyzing the The cause of the interruption occurred and retrying to establish a connection. Due to the relative independence of the first working group and the second working group, the second service unit establishes a communication connection with the standby control unit only in the second working group, and the standby control unit is only between the standby control unit and the main control unit There is a connection of the work group management channel; and the first uplink interface unit and the second service unit in the first work group only have a communication connection with the main control unit.
  • the main control unit may perform corresponding management control on the service run by the first working group, and may send service configuration information to the second working group, and after receiving the service configuration information, the second working group according to the service configuration The information is subject to corresponding management control of the business run by the second working group.
  • the configuration information in the second working group, the identification information of the main control unit and the standby control unit, and the like are reviewed.
  • the first working group and the second working group have achieved structural independence and business independence, that is, physical and logical independent, if the second working group is configured
  • the main control unit can send new service configuration information to the standby control unit, and modify the corresponding parameter according to the new service configuration information.
  • the first working group can run the service based on the traditional traffic deployment scheme
  • the second working group is based on the high-speed broadband.
  • the traffic deployment scenario to run high-rate required services.
  • the first working group and the second working group run corresponding types of services
  • the first working group and the second working are better ensured by the activation of the working group.
  • the independence of the group so as to better guarantee the accuracy of the business run by the first working group and the second working group.
  • independent software and hardware upgrades can be performed on the working group to meet the differentiated needs of users.
  • FIG. 6 is a flowchart of a service processing method in a network according to Embodiment 5 of the present invention. As shown in FIG. 6, the method is specifically described by upgrading the software to implement a new service, and specifically includes the following:
  • Step 601 The software having the new feature is separately sent to the second working group by the management system, and the running service is suspended.
  • Step 602 Activate the software of the new feature received by the second working group, and the standby control unit, the second uplink interface unit, and the second service unit in the second working group complete the upgrade.
  • the second working group After the second working group completes the upgrade of the software version, the configured user information does not change.
  • the second working group performs software upgrades, which can be implemented by automatic upgrade adaptation.
  • Step 603 The second working group runs the service according to the software of the new feature.
  • the second working group runs the service of the user configured before the software according to the new feature, and the service is an upgrade service of the previous service due to the software upgrade.
  • the main control board of the main control unit 504 needs to be replaced.
  • the new main control board is configured according to the configuration information of the original main control board, thereby reconfiguring the main control unit 504.
  • the standby control unit 507 records the cause of the interruption after detecting the interruption of the work group management channel, and periodically initiates a connection request. After the new main control board is inserted and the first work group resumes service, a new work group management channel is re-established.
  • the network device can be restored to the original active/standby mode by deleting the working group.
  • the method of deleting a work group can be implemented by the reverse process of establishing an independent working group. Reverting from the divided working group mode to the active/standby mode, the interface between the main control unit and the second uplink interface unit and the second service unit is actually opened, and the standby control unit is opened with the first uplink interface unit and The interface of the first service unit, so that the main control unit can establish a connection with all uplink interface units and the service unit. It should be noted that, when the network device is restored to the active/standby mode, the MAC address or IP address is sent to the standby control unit by the main control unit to ensure the MAC address or IP address of the standby control unit and the main control unit.
  • the configuration is delivered by the main control unit to the standby control unit of the second working group, and the standby control unit sends the configuration to the second uplink interface unit and the service unit, so that the second uplink interface unit and the second
  • the second service unit deletes the original control unit identification information and re-selects the control unit.
  • the solution in this embodiment can reduce the resource waste caused by deploying and configuring the entire network device by deploying and configuring a working group that runs a specific service.
  • the operator may lease one of the working groups, such as the second working group, to the enterprise or individual to realize independent management and operation of the service. At the same time, one of them can be upgraded first, providing a reliable test environment for new technology applications or network deployments.
  • FIG. 7 is a schematic structural diagram of a network device according to Embodiment 6 of the present invention.
  • the network device 701 specifically includes: a first working group 702 and a second working group 703.
  • the first working group 702 and the second working group 703 are connected to different users, and the control unit of the first working group 702.
  • the control unit of the second working group 703 is the standby control unit 705.
  • the main control unit 704 is configured to control the second working group 703 by controlling the standby unit 705;
  • the first working group 702 and the second working group 703 are respectively configured to run different types of services under the control of the respective control units.
  • the network device 701 includes a main control board and a standby control board; the main control unit 704 includes the main control board; the standby control unit 705 includes the standby control board; the network device 701 includes two uplink interface boards and at least two services. board;
  • One of the two uplink interface boards is a first uplink interface unit 706, and the two The other interface board of the uplink interface board is the second uplink interface unit 707;
  • At least one service board of the at least two service boards is a first service unit 708;
  • the service board except the at least one service board of the at least two service boards is a second service unit 709;
  • the first working group 701 includes: a main control unit 704, the first uplink interface unit 706, and the first service unit 708; the main control unit 704 and the first uplink interface unit 706 and the first service unit 708 connected;
  • the second working group 702 includes: the standby control unit 705, the second uplink interface unit 707, and the second service unit 709; the standby control unit 705 is opposite to the second uplink interface unit 707 and the second service unit 709 connection.
  • the main control unit is specifically configured to: before the activation of the first working group 701 and the second working group 702, if the main control unit 704 and the standby control unit 705 have device identification conflicts, the standby control unit is 705 issued a new device identification.
  • the device identifier includes an IP address or a MAC address.
  • the main control unit 704 is further configured to send the identifier change information to the backup unit 705, so that the backup unit 705 obtains new IP address information according to the identifier change information, or changes the information according to the identifier. Restore the default MAC address of the standby unit.
  • main control unit 704 is further configured to send the identification information of the standby control unit 705 to the second uplink interface unit 707 and the second service unit 709.
  • the standby control unit 705 and the second uplink interface After the unit 707 and the second service unit 709 are restarted, the connection ports with the second uplink interface unit 70 and the second service unit 709 are closed.
  • the standby control unit 705 is configured to complete the restart of the standby control unit 705, and establish a relationship with the main control unit 704.
  • the working group management channel is configured to send the service configuration information sent by the main control unit 704 to the standby control unit 705, so that the standby control unit 705 receives the service configuration information. Afterwards, the connection port with the first uplink interface unit 706 and the first service unit 708 is closed;
  • the second uplink interface unit 707 and the second service unit 709 are configured to wait for the second uplink interface unit 707 and the second service unit 709 to be restarted.
  • the standby control unit 705 Establish a communication connection.
  • the network device provided in this embodiment may implement the method in the foregoing embodiment, and the specific implementation process and the description thereof are similar to the foregoing embodiment, and details are not described herein again.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例提供一种网络设备及网络中的业务处理方法。该网络设备,用于连接多个终端设备,网络设备包括第一上行接口单元、主控单元、第一业务单元、第二上行接口单元、备控单元以及第二业务单元,第一上行接口单元、主控单元以及第一业务单元形成第一工作组,用于连接多个终端设备中的一部分;第二上行接口单元、备控单元以及第二业务单元形成第二工作组,用于连接多个终端设备中剩下的一部分;第一工作组用于在主控单元的控制下处理所连接的终端设备与网络侧之间的业务;第二工作组用于在所述备控单元的控制下处理所连接的终端设备与网络侧之间的业务。

Description

网络设备及网络中的业务处理方法
本申请要求于2013年12月31日提交中国专利局、申请号为201310754811.6、发明名称为“网络设备及网络中的业务处理方法”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信技术,尤其涉及一种网络设备及网络中的业务处理方法。
背景技术
在信息化高速发展的时代,随着移动互联网、物联网、云计算与智慧城市等概念的提出与实施,人类社会正面对着巨大的信息浪潮和数字洪流。网络通信设备(本文中简称“网络设备”)作为数据和信息的承载者,扮演着越来越重要的角色。
该网络设备通过不同类别的单元提供网络侧和用户侧的接口,供网络侧和用户侧连接。按照各单元作用的不同,分为控制单元、业务单元及上行接口单元等。其中,该业务单元包括至少一个业务板。该控制单元用于控制该业务单元及该上行接口单元执行该业务单元所对应的业务。
由于包括该至少一个业务板的业务单元均由该控制单元所控制,使得该网络设备仅能支持一种类型的业务,而无法支持多种不同类型的业务。
发明内容
本发明实施例提供一种网络设备及网络中的业务处理方法,以解决现有技术中网络设备无法支持多种不同类型的业务的问题。
第一方面,本发明实施例提供一种网络设备,用于连接多个终端设备,所 述网络设备包括第一上行接口单元(503)、主控单元(504)、第一业务单元(505)、第二上行接口单元(506)、备控单元(507)以及第二业务单元(508),所述第一上行接口单元(503)、主控单元(504)以及第一业务单元(505)形成第一工作组(501),用于连接所述多个终端设备中的一部分;所述第二上行接口单元(506)、备控单元(507)以及第二业务单元(508)形成第二工作组(502),用于连接所述多个终端设备中剩下的一部分;
所述第一工作组(501)用于在所述主控单元(504)的控制下处理所连接的终端设备与网络侧之间的业务;
所述第二工作组(502)用于在所述备控单元(507)的控制下处理所连接的终端设备与网络侧之间的业务。
结合第一方面,在第一方面的第一种可能实现的方式中,所述主控单元(504)和所述备控单元(507)之间设置有管理通道,所述管理通道用于所述主控单元(504)对所述第二工作组(502)进行管理。
结合第一方面,在第一方面的第二种可能实现的方式中,所述第一工作组(501)与所述第二工作组(502)分别连接不同的网络管理设备。
结合第一方面的第二种可能实现的方式,在第一方面的第三种可能实现的方式中,所述主控单元(504)和所述备控单元(507)之间设置有管理通道,所述管理通道用于所述主控单元(504)对所述第二工作组(502)进行管理。
结合第一方面,在第一方面的第四种可能实现的方式中,所述主控单元(504)的设备标识和所述备控单元(507)的设备标识不同。
结合第一方面的第四种可能实现的方式,在第一方面的第五种可能实现的方式中,所述设备标识包括IP地址或者媒体访问控制MAC地址。
结合第一方面、第一方面的第一~五种可能实现的方式,在第一方面的第六种可能实现的方式中,所述第一工作组(501)和第二工作组(502)处理的业务类型不同。
结合第一方面、第一方面的第一~五种可能实现的方式,在第一方面的第七种可能实现的方式中,所述网络设备为数字用户线接入复用器DSLAM或者光线路终端OLT。
第二方面,本发明实施例提供一种网络中的业务处理方法,所述网络包括一个网络设备和多个终端设备,所述网络设备包括第一上行接口单元(503)、主控单元(504)、第一业务单元(505)、第二上行接口单元(506)、备控单元(507)以及第二业务单元(508),所述方法包括:
将所述第一上行接口单元(503)、主控单元(504)以及第一业务单元(505)设置成第一工作组(501),通过所述第一工作组(501)连接所述多个终端设备中的一部分,在所述主控单元(504)的控制下通过所述第一工作组(501)处理所连接的终端设备与网络侧之间的业务;
将所述第二上行接口单元(506)、备控单元(507)以及第二业务单元(508)设置成第二工作组(502),通过所述第二工作组(502)连接所述多个终端设备中剩下的一部分,在所述备控单元(507)的控制下通过所述第二工作组(502)处理所连接的终端设备与网络侧之间的业务。
本发明实施例的网络设备及网络中的业务处理方法,通过将网络设备划分为各自包括一个控制单元的至少两个工作组,并通过不同工作组中的控制单元控制对应的工作组运行不同类型的业务,从而使得该网络设备可以支持多种不同类型的业务。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图做一简单地介绍,显而易见地,下面描述中的附图是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1为本发明实施例一所提供的网络设备的结构示意图;
图2为本发明实施例二所提供的网络中的业务处理方法的流程图;
图3为本发明实施例三所提供的网络中的业务处理方法的流程图;
图4为本发明实施例四所提供的网络中的业务处理方法的流程图;
图5为本发明实施例四中对工作组进行激活的方法流程图;
图6为本发明实施例五所提供的网络中的业务处理方法的流程图;
图7为本发明实施例六所提供的网络设备的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚,下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
实施例一
图1为本发明实施例一所提供的网络设备的结构示意图,如图1所示,该网络设备,可以连接多个终端设备,所提供的网络设备包括上行接口单元503、主控单元504、业务单元505、上行接口单元506、备控单元507以及业务单元508。
其中,在所述网络设备中,上行接口单元503、主控单元504以及第一业务单元505设置成第一工作组501,通过第一工作组501连接多个终端设备中的一部分,在主控单元504的控制下通过第一工作组501处理所连接的终端设备与网络侧之间的业务;
网络设备中的上行接口单元506、备控单元507以及业务单元508设置成第二工作组502,通过第二工作组502连接多个终端设备中剩下的一部分,在备控单元507的控制下通过第二工作组502处理所连接的终端设备与网络侧之间的业务。
作为一种实施方式,主控单元504可以通过控制备控单元507来实现对第二工作组的控制,主控单元504和备控单元507之间可以设置管理通道,主控单元504可以通过改管理通道实现对第二工作组的控制。
作为另一种实施方式,第一工作组501可以和第二工作组502分开管理,比如分别独立地连接不同的网络管理设备等,当然在这种架构下,也可以在主控单元504和备控单元507之间设置一个管理通道,也可以通过主控单元504对第二工作组502进行管理,从而实现第二工作组502的双重管理。
在本实施例中,由于第一工作组501和第二工作组502可以独立处理不同用户的业务,因此,主控单元504和备控单元507的设备标识可以不同,设备标识具体可以包括IP地址或者MAC(Media Access Control,媒体访问控制)地址等。
在本实施例中,第一工作组501和第二工作组502所处理的业务类型可以不同,也可以相同。
作为一种实施例,本实施例提供的网络设备可以是DSLAM(Digital  Subscriber Line Access Multiplexer,数字用户线接入复用器)或者OLT(Optical Line Terminal,光线路终端)等接入设备,当然也可以是其他网络设备,如路由设备、终端设备等。
本实施例提供的网络设备,通过将现有的主备链路设置成独立的工作组,连接不同的终端设备,从而可以充分利用网络设备的硬件资源,不同的工作组可以处理不同类型的业务,从而可以提高网络设备处理业务的能力。
实施例二
图2为本发明实施例二所提供的网络中的业务处理方法的流程图。本实施例的方法适用于网络设备所承载的不同用户需运行不同类型的业务的情况。本实施例的方法具体包括如下步骤:
步骤201、根据预配置信息,将网络设备划分为第一工作组和第二工作组,该第一工作组和该第二工作组包括控制单元、上行接口单元和业务单元;其中,该第一工作组和该第二工作组连接不同的用户;该第一工作组的控制单元为主控单元,该第二工作组的控制单元为备控单元;该主控单元用于通过对该备控单元进行控制,对该第二工作组进行控制。
步骤202、该第一工作组和该第二工作组在各自所具有的控制单元的控制下运行不同类型的业务。
具体地,根据该预配置信息对网络设备进行工作组的划分,实际是将该网络设备中各单元模块进行连接配置,使一个工作组内的单元相连接。根据该预配置信息,对网络设备进行工作组的划分,可以是通过在线划分,也可以是离线划分。在本申请中,在线指的是,该网络设备内各控制单元上已连插相应的 单元模块,离线指的是,该网络设备内各控制单元上还未连插相应的单元模块。若在线划分,根据该预配置信息和各个单元模块的标识等,对该网络设备进行连接划分;若为离线划分,根据该预配置信息和该控制单元上各单元模块的预留位置,对该网络设备进行连接划分。需要说明的是,对于离线划分,在根据划分之后的该两个工作组运行不同类型的业务之前,还需在其控制单元上对应位置,连插相应的单元模块。
该网络设备包括两个的控制单元,以使划分后的工作组各自具有一个控制单元。该第一工作组和该第二工作组,两个工作组各自包括控制单元、上行接口单元及业务单元,也就是说,该两个工作组各自相当于一个独立的设备。该两个工作组各组分别可通过其控制单元为该工作组内部各单元模块提供该工作组承担业务的业务配置参数信息、及根据该业务配置信息进行相应业务数据的处理、交换及汇聚,同时还可通过该控制单元为该工作组提供路由协议的配置及管理等。该第一工作组和该第二工作组分别连接不同的用户,而且不同用户的业务需求,由于该两个工作组的业务配置参数,可通过其各自的控制单元提供,从而可使得该第一工作组和该第二工作组根据各自控制单元的该业务配置参数执行对应类型的业务。
本实施例方案,通过将网络设备划分为各自包括控制单元、上行接口单元及业务单元的两个工作组,并通过该两个工作组中的控制单元分别控制对应的工作组运行不同类型的业务,从而使得该网络设备可以支持多种不同类型的业务。
实施例三
图3为本发明实施例三所提供的网络中的业务处理方法的流程图。如图3所示,该实施例方案,上述实施例方案中,优选的,该网络设备包括主控板和备控板,该控制单元为控制板,该备控单元为备控板,该网络设备包括两个上行接口板和至少两个业务板。
对应的,如上所述步骤201中根据预配置信息,将网络设备划分为第一工作组和第二工作组,具体包括:
步骤301、根据业务类型,将该两个上行接口板中一个接口板作为第一上行接口单元,配置为该第一工作组的上行接口单元,将该两个上行接口板中另一个接口板作为第二上行接口单元,配置为该第二工作组的上行接口单元;将该至少两个业务板中至少一个业务板作为配置为第一业务单元,将该至少两个业务板中除该至少一个业务板之外的业务板配置为第二业务单元。
为了维持网络设备的稳定运行需求,网络设备通常都支持主备模式。对于支持主备模式的网络设备来说,包括主控板、备控板。若该网络设备处于主备模式时,通过该主控板控制该网络设备和外部进行业务通信,保证各单元模块的正常运行;该备控板和外部没有业务通信,不承担任何业务负荷。该主控板和备控板在正常运行过程中,具有相同的配置信息,一旦主控板出现故障,便由该备控板进行接替以维持业务正常运行。也就是说,当前网络设备至少具有两个控制板,即主控板和备控板。在不改变现有网络设备的结构的基础上,本实施例方案优选的,将网络设备划分为两个工作组,即第一工作组和第二工作组。主控板可以作为主控单元,可以是配置为该第一工作组的控制单元,也可以是配置为该第二网络设备的控制单元。若该主控单元为该第一工作组的控制单元,备控单元作为第二工作组的控制单元,由于该主控单元在对本工作组内 个单元模块进行控制的基础上,还可通过对该备控单元的控制,对该第二工作组进行业务分配、管理及信息配置等。
将该网络设备划分为第一工作组和第二工作组的,该第一工作组和该第二工作组可分别具有不同的用户群,如该第一工作组对应企业用户群,该第二工作组对应普通用户群。
该上行接口板提供网络接口,以与网络侧相连接;该业务板提供用户接口,实现用户业务的接入、处理和转发等。该网络设备中的一个业务板具有至少一个用户接口,可以接入至少一个用户,而接入同一业务板的用户业务需求相同。
该第一工作组的控制单元为该主控单元,该第二工作组的控制单元为该备控单元,同时还为该第一工作组和该第二工作组分别配置一个上行接口单元,根据业务类型,将该网络设备的业务板分为两部分,即第一业务单元及第二业务单元;其中该第一业务单元的业务板所承载的业务类型与该第二业务单元的业务板所承载的业务类型不同。
进一步地,在上述方案中步骤301中根据预配置信息,将网络设备划分为第一工作组和第二工作组之前,还包括:
步骤302、判断该预配置信息中该第一工作组和该第二工作组对应的配置是否存在耦合。若是(Y),则执行步骤303;若否(N),则执行步骤304。
该步骤中所判断的配置耦合,指的是该预配置信息中单元模块的连接耦合。具体来说,同一单元模块,如上行接口单元或业务单元,只可以对应一个控制单元。而且,对于承载不同业务的上行接口单元具有该不同业务所对应的业务信息及硬件配置需求,具有不同业务需求的业务单元具有不同业务所对应的业务传输通道。对于相同或类似业务的业务单元及上行接口单元需配置在同一工 作组内,若出现交叉配置,即为存在耦合。
步骤303、修改该预配置信息,以解除该耦合;根据该修改后的该预配置信息,将该网络设备划分为该第一工作组和该第二工作组。
为保证,划分后的相互独立的各个工作组可以正常传输对应业务数据,若存在耦合,需待接触耦合之后,重新对该网络设备进行工作组的划分。
步骤304、根据该预配置信息,将该网络设备划分为该第一工作组和该第二工作组。
该实施例方案,在现有网络设备内部结构和网络架构的基础上,进行工作组的划分,可更好的保证所划分的工作组的正常运行,同时在工作组运行业务之前,进行连接耦合的判断,从而更好的保证业务数据的正常传输。
实施例四
图4为本发明实施例四所提供的网络中的业务处理方法的流程图。如图4所示,进一步地,上述方案的步骤202中该第一工作组和该第二工作组在各自所具有的控制单元的控制下运行不同类型的业务之前,还包括:
步骤401、对该第一工作组和该第二工作组进行激活。
为保证所划分的工作组各单元模块之间的连接有效,且可以正常通信,从而保证业务的正常进行,在运行对应业务之前,至少还应对该划分的工作组进行激活。
优选的,在上述步骤401中对该第一工作组和该第二工作组组进行激活之前,还包括:
步骤402、判断该主控单元和所述备控单元是否存在设备标识冲突。
步骤403、若该主控单元和该备控单元存在设备标识冲突,该主控单元向该备控单元下发新的设备标识。
具体地,对于常用的主备模式的网络设备,为保证备控板在接替主控板可以正常的工作,通常为该主控板和该备控板配置相同的设备标识,以使与控制板相连接的上行接口板及业务板可以准确识别,从而准确的进行业务信息的处理。然而在本实施例中根据不同的控制板,也就是控制单元的设备标识来识别不同的工作组。因而,在该实施例方案中,在对该至少两个工作组进行激活,从而运行业务之前,首先应确保该至少两个工作组不存在标识冲突。若该至少两个工作组存在标识冲突,即该至少两个工作组所对应的控制单元具有相同的设备标识,可通过主控单元,即主控板向该备控单元,即备控板下发新的标识。该主控板可以是通过主备管理通道向该备控板下发。
上述方案中,设备标识包括互联网协议(Internet Protocol,简称IP)地址或介质接入控制(Media Access Control,简称MAC)地址;
对应的,上述步骤403中主控单元向该备控单元下发新的设备标识,具体包括:
该主控单元向该备控单元下发标识更改信息,以使该备控单元根据该标识更改信息获取新的IP地址信息,或,根据该标识更改信息,恢复该备控单元的缺省MAC地址。
具体地,该标识更改消息包括新的IP地址,或更改指示消息。该主控单元可以是将重新动态生成新的IP地址通过该标识更改消息下发至该备控单元,也可以是,该备控单元在接收该标识更改消息之后,主动生成新的IP地址,并告知该主控单元。
可选的,该标识更改消息还包括缺省恢复指示消息。由于设备或单元的MAC地址,为生产商在制作过程中烧录在其内部的硬件地址,具有唯一性。然而,对于主备模式的网络设备来说,为使得其主控板和备控板具有相同的MAC地址,通常为备控板虚拟一个与主控板相同的MAC地址。在本实施例中,备控单元在接收到主控单元所下发的该缺省恢复指示消息,对该备控单元的设备标识恢复至默认的MAC地址,也就是具有唯一性的出厂MAC地址。
图5为本发明实施例四中对工作组进行激活的方法流程图。如图5所示,进一步地,上述方案中步骤401中对该第一工作组和该第二工作组进行激活,具体包括:
步骤401a、该主控单元将该备控单元的标识信息发送至该第二上行接口单元及该第二业务单元。
该标识信息可以是IP地址或MAC地址均可。由于,此时还未对划分后的工作组内的单元模块进行重启,因此,主控单元可以是通过该主控单元与该备控单元之间的主备管理通道将该标识信息下发至该该第二上行接口单元及该第二业务单元,以使该第二工作组内单元模块在重启之后,该第二上行接口单元及该第二业务单元可以与该备控单元建立通信连接。
步骤401b、分别对该备控单元、该第二上行接口单元及该第二业务单元进行重启。
具体地,在该网络设备内部,该备控单元、该第二上行接口单元及该第二业务单元所所对应的备控板、上行接口板及业务板均是作为独立的单板插接在该网络设备上。在各单板均具有重启功能,可以是通过选中重启操作软件控制该些单板重启,也可以是通过按下各单板上重启按钮,来实现重启。
步骤401c、该主控单元关闭与该第二上行接口单元及该第二业务单元的连接端口。
对于支持主备模式的网络设备,其网络设备内部各上行接口单元及业务单元均与该主控单元相连接,然而对于该第一工作组和该第二工作组,为保证业务数据的正确传输,上行接口单元和业务单元仅可以与其所配置的工作组内的控制单元相连接。由于该第二上行接口单元和该第二业务单元均为该第二工作组的单元,因此该主控单元需要关闭与其的连接。
步骤401d、待该备控单元重启完毕,该备控单元建立与该主控单元之间的工作组管理通道;该工作组管理通道用于将该主控单元下发的业务配置信息下发至该备控单元,以使该备控单元在接收到该业务配置信息之后,关闭与该第一上行接口单元及该第一业务单元的连接端口。
由于该备控单元、该第二上行接口单元及该第二业务单元均作为单板进行重启,对于不同的单板,由于其内部结构及重启进程的不同,其重启时间业务不尽相同。该备控单元重启完毕,该主控单元便恢复与该备控单元的通信,也就是说该主控单元可以和该备控单元进行数据传输。该备控单元在重启过程中,该备控单元中断与单元模块的通信连接。待重启完毕,该备控单元通过向该主控单元发送建立请求消息,尝试与该主控单元重新建立连接。该主控单元在接收到该备控单元所发送的请求消息,与该备控单元建立双向通信连接,该通信连接,即为该工作管理通道。
该主控单元可通过该工作管理通道向该备控单元下发业务配置信息,该业务配置信息包括该第二工作组运行对应业务,该备控单元、该第二上行接口单元及该第二业务单元需配置的参数信息。在该第二工作组的激活过程中,该备 控单元在接收到该业务配置信息之后,确认该第二工作组对应的业务与该第一工作组所对应的业务类型不同,获知该网络设备处于工作组负担模式,而非主备模式,因此该备控单元还需关闭该第一上行接口单元及该第一业务单元的连接端口,从而更高的保证业务数据的准确传输。
需要说明的是,该备控单元在该第二工作组进行激活建立连接之后,运行业务的过程中,还可周期性的检测该工作管理通道的状态,如发现通道传输中断等,记录分析该发生中断的原因,并重新尝试建立连接。由于该第一工作组与该第二工作组的相对独立性,在该第二工作组该第二业务单元仅与该备控单元建立通信连接,该备控单元仅与该主控单元之间存在工作组管理通道的连接;而对于,该第一工作组内部的该第一上行接口单元、该第二业务单元也仅与该主控单元存在通信连接。也就是说,该第一工作组和该第二工作组在实现物理上的结构独立的基础上,其各自的业务通信也相对独立,其互不干扰。该主控单元可对该第一工作组所运行业务进行相应的管理控制,可对该第二工作组下发业务配置信息,该第二工作组在接收该业务配置信息之后,根据该业务配置信息对该第二工作组所运行业务进行相应的管理控制。
在对该第二工作组进行激活之后,对该第二工作组内的配置信息、及该主控单元及该备控单元的标识信息等进行复查。在对该第二工作组进行激活之后,该第一工作组与该第二工作组已实现结构独立和业务独立,也就是物理和逻辑的独立的基础上,若该第二工作组所配置的用户业务发生变更或升级,可由该主控单元向该备控单元下发新的业务配置信息,并根据该新的业务配置信息进行对应参数的修订。
对于结构及业务独立的工作组,可以使用完全不同的网络部署和配置方案, 从而有针对性的为不同的用户群提供不同类型的业务体验。举例来说,对于普通的用户群可通过该第一工作组,基于传统的流量部署方案运行业务,而对于具有高宽带、高流量的特殊用户群,则通过该第二工作组,基于高速宽带的流量部署方案来运行高速率要求的业务。
本实施例方案在上述方案的基础上,在该第一工作组和该第二工作组运行相应类型的业务之前,通过工作组的激活,更好的保证该第一工作组和该第二工作组的独立性,从而更好的保证该第一工作组和该第二工作组所运行业务的准确性。同时,由于该网络设备划分后的工作组的物理和逻辑之间的独立,可对工作组进行独立软硬件升级,从而满足用户的差异化需求。
实施例五
图6为本发明实施例五所提供的网络中的业务处理方法的流程图。如图6所示,该方法,具体通过对软件进行升级以实现新业务进行具体说明,具体包括如下:
步骤601、通过管理***将具有新特性的软件单独下发至该第二工作组,并暂停所运行的业务。
需要说明的是,由于该新特性的软件仅下发至该第二工作组,因此该第一工作组正常运行已有业务,该第二工作组在接收到该新特性的软件后,需中断所运行的业务。
步骤602、激活该第二工作组所接收到的该新特性的软件,该第二工作组中该备控单元、该第二上行接口单元和该第二业务单元完成升级。
具体地,该第二工作组完成软件版本的升级后,其所配置的用户信息不变。 该第二工作组进行软件的升级,可以是通过自动升级适配来实现。
步骤603、该第二工作组根据该新特性的软件运行业务。
该第二工作组根据该新特性的软件运行之前所配置用户的业务,该业务由于软件的升级,为之前业务的升级业务。
若该主控单元504由于设备老化性能减弱已无法满足该第一工作组501所配置业务的需求,则需将该主控单元504的主控板替换掉即可。替换主控板之后,根据原主控板的配置信息通过对该新的主控板进行配置,从而对该主控单元504进行业务的重新配置。卸下原主控板,该备控单元507在检测到工作组管理通道中断后,记录该中断的原因,并周期性的发起连接请求。当***新主控板,且该第一工作组重新恢复业务之后,重新建立新的工作组管理通道。
然而,随着用户需求的不断变化,所有用户的需求都得到提高,从而使得用户需求不均衡化得到缓解。那么,还可通过删除工作组的方式,使得该网络设备恢复至原有的主备模式。
删除工作组的方法可以是该建立独立工作组的反过程来实现。从划分的工作组模式,恢复至主备模式,实际主要是打开该主控单元与该第二上行接口单元及该第二业务单元的接口,该备控单元打开与该第一上行接口单元及该第一业务单元的接口,从而使得该主控单元可以与所有的上行接口单元及该业务单元建立连接。需要说明的是,将该网络设备恢复至主备模式,还需通过该主控单元为备控单元下发MAC地址或IP地址,保证该备控单元与该主控单元的MAC地址或IP地址相同;通过该主控单元为第二工作组的该备控单元下发配置,备控单元将该配置发送至该第二上行接口单元及该业务单元,以使该第二上行接口单元和第二业务单元删除原有的控制单元标识信息,重新进行控制单元的选 择,与该主控单元建立连接。将该网络设备恢复至主备模式,还需对该网络设备各单元模块进行重启,并重新建立主备管理通道。
本实施例方案,在满足用户需求差异化的基础上,还可通过对运行特定业务的工作组进行部署配置,减少对该整个网络设备进行部署配置所造成的资源浪费。
需要说明的是,本发明实施例方案由于工作组之间物理及逻辑的独立,因此运营商可将其中一个工作组,如该第二工作组租赁给企业或个人,实现业务的独立管理和运营,同时还可优先升级其中一个,为新技术应用或网络部署的提供可靠的试验环境。
实施例六
图7为本发明实施例六所提供的网络设备的结构示意图。如图7所示,该网络设备701,具体包括:第一工作组702和第二工作组703,第一工作组702和第二工作组703连接不同的用户,第一工作组702的控制单元为主控单元704,第二工作组703的控制单元为备控单元705。主控单元704用于通过对备控单元705进行控制,对第二工作组703进行控制;
第一工作组702和第二工作组703,分别用于在各自所具有的控制单元的控制下运行不同类型的业务。
优选的,该网络设备701包括主控板和备控板;主控单元704包括该主控板;备控单元705包括该备控板;网络设备701包括两个上行接口板和至少两个业务板;
其中,该两个上行接口板中一个上行接口板为第一上行接口单元706,该两 个上行接口板中另一个接口板为第二上行接口单元707;
该至少两个业务板中至少一个业务板,为第一业务单元708;
该至少两个业务板中除该至少一个业务板之外的业务板,为第二业务单元709;
对应的,该第一工作组701包括:主控单元704、该第一上行接口单元706及该第一业务单元708;该主控单元704与该第一上行接口单元706和该第一业务单元708相连接;
该第二工作组702包括:该备控单元705、该第二上行接口单元707及该第二业务单元709;该备控单元705与该第二上行接口单元707和该第二业务单元709相连接。
上述方案中,该主控单元,具体用于在第一工作组701和第二工作组702进行激活之前,若该主控单元704和该备控单元705存在设备标识冲突,为该备控单元705下发新的设备标识。
其中,设备标识包括IP地址或MAC地址;
对应的,该主控单元704,还用于向该备控单元705下发标识更改信息,以使该备控单元705根据该标识更改信息获取新的IP地址信息,或,根据该标识更改信息,恢复该备控单元的缺省MAC地址。
进一步地,主控单元704,还用于将该备控单元705的标识信息发送至该第二上行接口单元707及该第二业务单元709;在对该备控单元705、该第二上行接口单元707及该第二业务单元709进行重启之后,关闭与该第二上行接口单元70及该第二业务单元709的连接端口。
该备控单元705,用于待该备控单元705重启完毕,建立与该主控单元704 之间的工作组管理通道;该工作组管理通道用于将该主控单元704下发的业务配置信息下发至该备控单元705,以使该备控单元705在接收到该业务配置信息之后,关闭与该第一上行接口单元706及该第一业务单元708的连接端口;
该第二上行接口单元707和该第二业务单元709,用于待该第二上行接口单元707及该第二业务单元709重启完毕,根据该备控单元的标识信息,与该备控单元705建立通信连接。
本实施例所提供的网络设备,可实施上述实施例所述的方法,其具体的实现过程及解释说明,与上述实施例类似,在此不再赘述。
本领域普通技术人员可以理解:实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一计算机可读取存储介质中。该程序在执行时,执行包括上述各方法实施例的步骤;而前述的存储介质包括:ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是:以上各实施例仅用以说明本发明的技术方案,而非对其限制;尽管参照前述各实施例对本发明进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分或者全部技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (9)

  1. 一种网络设备,用于连接多个终端设备,所述网络设备包括第一上行接口单元(503)、主控单元(504)、第一业务单元(505)、第二上行接口单元(506)、备控单元(507)以及第二业务单元(508),其特征在于,所述第一上行接口单元(503)、主控单元(504)以及第一业务单元(505)形成第一工作组(501),用于连接所述多个终端设备中的一部分;所述第二上行接口单元(506)、备控单元(507)以及第二业务单元(508)形成第二工作组(502),用于连接所述多个终端设备中剩下的一部分;
    所述第一工作组(501)用于在所述主控单元(504)的控制下处理所连接的终端设备与网络侧之间的业务;
    所述第二工作组(502)用于在所述备控单元(507)的控制下处理所连接的终端设备与网络侧之间的业务。
  2. 根据权利要求1所述的网络设备,其特征在于,所述主控单元(504)和所述备控单元(507)之间设置有管理通道,所述管理通道用于所述主控单元(504)对所述第二工作组(502)进行管理。
  3. 根据权利要求1所述的网络设备,其特征在于,所述第一工作组(501)与所述第二工作组(502)分别连接不同的网络管理设备。
  4. 根据权利要求3所述的网络设备,其特征在于,所述主控单元(504)和所述备控单元(507)之间设置有管理通道,所述管理通道用于所述主控单元(504)对所述第二工作组(502)进行管理。
  5. 根据权利要求1所述的网络设备,其特征在于,所述主控单元(504) 的设备标识和所述备控单元(507)的设备标识不同。
  6. 根据权利要求5所述的网络设备,其特征在于,所述设备标识包括IP地址或者媒体访问控制MAC地址。
  7. 根据权利要求1-6任意一项所述的网络设备,其特征在于,所述第一工作组(501)和第二工作组(502)处理的业务类型不同。
  8. 根据权利要求1-6任意一项所述的网络设备,其特征在于,所述网络设备为数字用户线接入复用器DSLAM或者光线路终端OLT。
  9. 一种网络中的业务处理方法,所述网络包括一个网络设备和多个终端设备,所述网络设备包括第一上行接口单元(503)、主控单元(504)、第一业务单元(505)、第二上行接口单元(506)、备控单元(507)以及第二业务单元(508),其特征在于,所述方法包括:
    将所述第一上行接口单元(503)、主控单元(504)以及第一业务单元(505)设置成第一工作组(501),通过所述第一工作组(501)连接所述多个终端设备中的一部分,在所述主控单元(504)的控制下通过所述第一工作组(501)处理所连接的终端设备与网络侧之间的业务;
    将所述第二上行接口单元(506)、备控单元(507)以及第二业务单元(508)设置成第二工作组(502),通过所述第二工作组(502)连接所述多个终端设备中剩下的一部分,在所述备控单元(507)的控制下通过所述第二工作组(502)处理所连接的终端设备与网络侧之间的业务。
PCT/CN2014/090209 2013-12-31 2014-11-04 网络设备及网络中的业务处理方法 WO2015101100A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310754811.6 2013-12-31
CN201310754811.6A CN104753714B (zh) 2013-12-31 2013-12-31 网络设备及网络中的业务处理方法

Publications (1)

Publication Number Publication Date
WO2015101100A1 true WO2015101100A1 (zh) 2015-07-09

Family

ID=53493156

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/090209 WO2015101100A1 (zh) 2013-12-31 2014-11-04 网络设备及网络中的业务处理方法

Country Status (2)

Country Link
CN (1) CN104753714B (zh)
WO (1) WO2015101100A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106452913A (zh) * 2016-11-22 2017-02-22 卡斯柯信号有限公司 一种终端网络设备复用快速切换的方法
CN112462664A (zh) * 2020-11-30 2021-03-09 广州仪速安电子科技有限公司 一种仪器接口数据监测***
WO2023283809A1 (zh) * 2021-07-13 2023-01-19 北京小米移动软件有限公司 接入控制处理方法、装置、通信设备及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106850262B (zh) * 2016-12-27 2020-03-24 郑州云海信息技术有限公司 一种服务器网络管理方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1482769A (zh) * 2002-09-13 2004-03-17 华为技术有限公司 基于以太网接入平台的主备倒换与负荷分担***及方法
ES2244891T3 (es) * 2002-06-06 2005-12-16 Siemens Aktiengesellschaft Cluster de pasarela tolerante a fallos.
CN102546222A (zh) * 2010-12-07 2012-07-04 中国电信股份有限公司 备份***及故障检测处理方法
CN103457774A (zh) * 2013-09-05 2013-12-18 深圳市共进电子股份有限公司 实现网络双上行自动切换备份的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2244891T3 (es) * 2002-06-06 2005-12-16 Siemens Aktiengesellschaft Cluster de pasarela tolerante a fallos.
CN1482769A (zh) * 2002-09-13 2004-03-17 华为技术有限公司 基于以太网接入平台的主备倒换与负荷分担***及方法
CN102546222A (zh) * 2010-12-07 2012-07-04 中国电信股份有限公司 备份***及故障检测处理方法
CN103457774A (zh) * 2013-09-05 2013-12-18 深圳市共进电子股份有限公司 实现网络双上行自动切换备份的方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106452913A (zh) * 2016-11-22 2017-02-22 卡斯柯信号有限公司 一种终端网络设备复用快速切换的方法
CN112462664A (zh) * 2020-11-30 2021-03-09 广州仪速安电子科技有限公司 一种仪器接口数据监测***
CN112462664B (zh) * 2020-11-30 2022-03-18 广州仪速安电子科技有限公司 一种仪器接口数据监测***
WO2023283809A1 (zh) * 2021-07-13 2023-01-19 北京小米移动软件有限公司 接入控制处理方法、装置、通信设备及存储介质

Also Published As

Publication number Publication date
CN104753714A (zh) 2015-07-01
CN104753714B (zh) 2018-06-15

Similar Documents

Publication Publication Date Title
US11159362B2 (en) System and method for managing configuration of virtual switches in a virtual machine network
US9203865B2 (en) Cluster architecture for network security processing
CN103583063B (zh) 用于地理冗余网关处的故障恢复的***和方法
US20170289791A1 (en) Communication method and apparatus using network slice
US10791458B2 (en) Transferring information to a mobile device
EP1779590B1 (en) Port aggregation for fibre channel interfaces
CN110086652B (zh) 一种针对5g核心网中服务网元的管理***及其方法
US9071508B2 (en) Distributed fabric management protocol
JP5366177B2 (ja) スロットインターフェースアクセス装置、その方法及びそのプログラム並びに主装置の冗長構成及び代替方法
WO2015074396A1 (zh) 一种软件定义网络sdn的自动配置方法、设备及***
CN104935672A (zh) 负载均衡服务高可用实现方法和设备
WO2017000832A1 (zh) Mac地址的同步方法、装置及***
WO2015101100A1 (zh) 网络设备及网络中的业务处理方法
CN103259685A (zh) 检测链路故障的方法及网络设备
WO2011091696A1 (zh) 相邻基站连接的建立方法、建立设备和建立***
WO2014201692A1 (zh) 选择移动管理实体的方法、装置和***
JP2013030190A (ja) スロットインターフェースアクセス装置、その方法及びそのプログラム並びに主装置の冗長構成及び代替方法
WO2015066894A1 (zh) 转发面迁移方法、控制器及网关
US20240106708A1 (en) Fabric availability and synchronization
CN108900441B (zh) 网络切换方法、第一电子设备及可读存储介质
CN105763442A (zh) 主备倒换lacp聚合链路不中断的pon***及方法
CN107465582B (zh) 数据发送方法、装置、***、物理家庭网关及接入节点
US11907253B2 (en) Secure cluster pairing for business continuity and disaster recovery
CN114531337A (zh) 一种宽带连接方法及装置
WO2017084411A1 (zh) 软件定义网络管理方法及通信***

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14876583

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14876583

Country of ref document: EP

Kind code of ref document: A1