WO2016177187A1 - 业务处理方法及装置 - Google Patents

业务处理方法及装置 Download PDF

Info

Publication number
WO2016177187A1
WO2016177187A1 PCT/CN2016/077576 CN2016077576W WO2016177187A1 WO 2016177187 A1 WO2016177187 A1 WO 2016177187A1 CN 2016077576 W CN2016077576 W CN 2016077576W WO 2016177187 A1 WO2016177187 A1 WO 2016177187A1
Authority
WO
WIPO (PCT)
Prior art keywords
service board
service
interface
board
module
Prior art date
Application number
PCT/CN2016/077576
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 WO2016177187A1 publication Critical patent/WO2016177187A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure

Definitions

  • the present invention relates to the field of communications, and in particular to a service processing method and apparatus.
  • the decentralization of distributed services has become a trend.
  • the state calculation, message processing, and data area of the service are saved on the L-CPU to fully utilize the processing power of the L-CPU and the storage resources of the service board.
  • the burden on the main control R-CPU is reduced, and the processing speed of the user service and the capacity of accessing the user service are improved.
  • This problem is illustrated by taking the requirements of the DHCP (Dynamic Host Configuration Protocol) smartgroup (hereinafter collectively referred to as SG) interface as an inter-board.
  • DHCP Dynamic Host Configuration Protocol
  • SG Dynamic Host Configuration Protocol
  • the protocol processing of DHCP is distributed.
  • the state machine and message processing and the data area of the DHCP relay are saved on the L-CPU to fully utilize the processing power and storage space of the L-CPU to improve the access speed and access of the user.
  • User's capacity When the user-side interface is the inter-board SG interface, the DHCP protocol packets are delivered by the local device, that is, different packets of the same session of the same host user may be delivered to different L-CPUs through the same SG interface. This will cause the DHCP module state machine and data area to be abnormal.
  • the key to solving the above-mentioned cross-board problem is to deliver all the messages of the same host user to the same point to ensure the consistency of the state machine and the data area.
  • Two problems are involved here, one is the granularity of the user. The problem, one is the choice of concentration points.
  • the ideal state is to reduce the granularity to the real user, that is, the messages of different users of the same SG interface, which can be delivered to different centralized points for processing, and only need to ensure that the same user is delivered to the same centralized point.
  • the processing is complicated.
  • the device when the device receives the server packet, the device needs to deliver the server backhaul message to the processing point where the user originally located, and requires a large-volume table at the user level. High, the benefits are not very large, so consider the option of taking a step back: all users of the same SG interface are placed in a centralized point.
  • Concentration point selection problem The simplest and most intuitive point of concentration is of course the R-CPU, but the problem is that the number of user accesses and access rate are limited, and will affect the R-CPU to some extent.
  • the embodiment of the present invention provides a service processing method and device, which at least solves the problem that the service board is not able to be reused by the service board in the related art.
  • a service processing method includes: a main service board
  • the service board is selected for the interface.
  • the main service board collects the distributed services on the selected service boards.
  • the method further includes: the main service board writes all the service boards to the port attribute table of the interface, and synchronizes the port attribute table. Go to each service board.
  • the main service board selects a service board as an interface, and the main service board selects a service board as an interface according to the principle that the service is evenly distributed on the service board.
  • the method further includes: the main service board detects whether the service board is faulty by using a member interface of the port management to delete the notification message or the port inconsistency notification message; in the case that the service board is faulty, The main service board reselects the service board for the interface.
  • the method further includes: the main service board receiving an instruction for selecting an interface of the service card for the interface; the main service board selecting the specified service board as an interface according to the instruction.
  • a service processing apparatus is further provided, which is applied to a main service board, where the apparatus includes: a selection module configured to select a service board for an interface; and a processing module configured to be distributed The services are concentrated on the selected service boards for processing.
  • the device further includes: a synchronization module, configured to write all the service boards to the port attribute table of the interface, and synchronize the port attribute table to each service board.
  • a synchronization module configured to write all the service boards to the port attribute table of the interface, and synchronize the port attribute table to each service board.
  • the selecting module includes: a selecting unit, configured to select a service board for the interface according to the principle that the service is uniformly distributed on the granularity of the service board.
  • the device further includes: a detecting module, configured to detect, by using a member interface of the port management, a notification message or a port inconsistency notification message to detect whether the service board is faulty; and reselecting the module, and setting is performed on the service board. If the fault occurs, re-select the service board for the interface.
  • a detecting module configured to detect, by using a member interface of the port management, a notification message or a port inconsistency notification message to detect whether the service board is faulty.
  • the device further includes: a receiving module, configured to receive an instruction for selecting a service card for the interface; and selecting a designated module, configured to select the specified service card as an interface according to the instruction.
  • the service board is selected as the interface by using the main service board; the main service board collects the distributed service on the selected service board, and solves the problem in the related technologies.
  • the problem of the service board selection function that cannot be reused.
  • FIG. 1 is a flowchart of a service processing method according to an embodiment of the present invention.
  • FIG. 2 is a block diagram of a service processing apparatus according to an embodiment of the present invention.
  • FIG. 3 is a block diagram 1 of a service processing apparatus in accordance with a preferred embodiment of the present invention.
  • FIG. 4 is a block diagram 2 of a service processing apparatus in accordance with a preferred embodiment of the present invention.
  • FIG. 5 is a block diagram 3 of a service processing apparatus in accordance with a preferred embodiment of the present invention.
  • FIG. 6 is a block diagram 4 of a service processing apparatus in accordance with a preferred embodiment of the present invention.
  • FIG. 7 is a system architecture diagram of a main service board according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of interaction between service boards according to an embodiment of the present invention.
  • FIG. 1 is a flowchart of a service processing method according to an embodiment of the present invention. As shown in FIG.
  • Step S102 The main service board selects a service board for the interface.
  • step S104 the main service board collects distributed services on the selected service board for processing.
  • the main service card selects the service card for the interface, and the main service card collects the distributed service on the selected service card to solve the problem.
  • the board selection feature causes problems that cannot be reused.
  • the main service board after the main service board selects the service board for the interface, the main service board writes all the service boards to the port attribute table of the interface, and synchronizes the port attribute table to each Business board.
  • the main service board selects the service board for the interface.
  • the main service board selects the service board as the interface based on the principle that the service is evenly distributed on the service board.
  • the main service board is configured to remove the notification message or the port inconsistency notification message on the member interface of the port to check whether the service board is faulty. If the service board fails, the main service order is faulty. The board reselects the service board for the interface.
  • the main service card receives the command to select a service card for the interface.
  • the main service card selects the specified service card for the interface according to the command.
  • FIG. 2 is a block diagram of a service processing apparatus according to an embodiment of the present invention. As shown in FIG. 2, the apparatus includes:
  • the module 22 is configured to select a service board for the interface.
  • the processing module 24 is configured to collect distributed services on the selected service board for processing.
  • FIG. 3 is a block diagram of a service processing apparatus according to a preferred embodiment of the present invention. As shown in FIG. 3, the apparatus further includes: a synchronization module 32, configured to write all service boards to a port attribute table of the interface, and The port attribute table is synchronized to each service board.
  • a synchronization module 32 configured to write all service boards to a port attribute table of the interface, and The port attribute table is synchronized to each service board.
  • FIG. 4 is a block diagram 2 of a service processing apparatus according to a preferred embodiment of the present invention.
  • the selection module 24 includes: a selecting unit 42 configured to select a service according to the principle that the service is uniformly distributed on the granularity of the service board. veneer.
  • FIG. 5 is a block diagram 3 of a service processing apparatus according to a preferred embodiment of the present invention. As shown in FIG. 5, the apparatus further includes:
  • the detecting module 52 is configured to detect whether the service board is faulty by using a member interface of the port management to delete the notification message or the port inconsistency notification message.
  • the re-selection module 54 is configured to re-select the service board for the interface if the service board fails.
  • FIG. 6 is a block diagram 4 of a service processing apparatus according to a preferred embodiment of the present invention. As shown in FIG. 6, the apparatus further includes:
  • the receiving module 62 is configured to receive an instruction for selecting a service board for the interface
  • the specified module 64 is selected to be configured to select the specified service board for the interface according to the instruction.
  • the embodiment of the present invention provides a method for selecting a general-purpose service board, which can support the service board selection of various types of interfaces of various services, and concentrate the distributed services on the service board.
  • the existing service board selection function is implemented, and each service board is implemented separately.
  • the code logic is repeated and the implementation details are different and cannot be reused.
  • the main service board R-CPU includes an active/standby synchronization library, a service board selection module, and port management, where port management is performed.
  • the port is also included in the attribute table.
  • the service board selection module is planned to be located in the protocol stack process of the R-CPU. The function is to select a service card for the interface and focus the distributed service on the selected service board. Currently, the service is not only supported.
  • the SG interface can also be extended to other types of aggregate interfaces.
  • FIG. 8 is a schematic diagram of interaction between service boards according to an embodiment of the present invention.
  • the service board is notified by the port management module, and the service board selection module queries the port management to obtain One of the member interfaces of the SG interface is selected as the service board. If the member interface is not queried, the user may not be configured.
  • the service board selection module waits for the member interface of the port management to join the notification. In this case, the first member of the SG is selected as the service board. In this case, you need to configure the first member as a different board when configuring multiple SG interfaces. On the other hand, you can provide commands to the user and manually specify the service board.
  • the service card selection module After the configuration is complete, the service card selection module writes the service board to the port attribute table of the interface. The port management module synchronizes this attribute to each service board. The lifetime of the SG interface does not change after the selection is completed, even if the members of the SG interface change.
  • the selection of service boards should ensure the uniform distribution of services on the board granularity. If the service board is faulty, the service board needs to be re-selected.
  • the service board selection module deletes the notification message or the port inconsistency notification through the member interface of the port management. The message is faulty on the service board.
  • the service board selection module can delay the selection of the service board for the SG interface. The purpose of this is to wait for the service board to succeed. The same board. You can manually specify the service board of the SG interface.
  • the processing logic of the SG user needs to be determined at a fixed point. If the SG processing point is moved to the master, the implementation is the simplest, but the number of users is in the scenario of the switch vlan range port access. There are more, so there is a possibility that a large number of users will concentrate on the line or go offline. To prevent the aging of a large number of user-side packets from the R-CPU, you need to drop the SG user processing logic to the service board.
  • DHCP supports the SG interface on the inter-board.
  • the implementation steps of the service board selection module include:
  • Step 1 The port management module notifies the service board selection module of the addition and deletion of the SG interface.
  • Step 2 The service board selection module writes the service board selected by the SG interface as a port attribute to the port attribute table.
  • Step 3 The port management synchronizes the port attributes of the service card to the service board.
  • Step 4 The user side SG interface enters the packet, or the network side packet when the device functions as the DHCP relay;
  • Step 5 When the step 4 is the inbound packet of the user-side SG interface, the callback function of the service module (DHCP module) obtains the service board according to the inbound interface of the packet querying the port management module;
  • DHCP module the callback function of the service module
  • Step 6 When the step 4 is the network side packet, the callback function of the service module (DHCP module) queries the route according to the destination address of the packet, and obtains the outgoing interface of the packet, that is, the user-side interface. If the outgoing interface is the SG interface, the query is performed.
  • Service board of the port management module DHCP module
  • Step 7 Lpp delivers the packet to the service board according to the service board returned by the service module callback function.
  • the service board does not have the active/standby protection function and the service board is not selected on the interface. In this case, if the service board is offline, you need to re-select the board to cause the service to be in a certain interval.
  • the service board selection module provides the function of manually configuring a service card. In particular, when the reliability of the user is high (for example, the board is not interrupted), and the performance requirements are not very high. If the value is high, you can manually specify the service board as the R-CPU.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)
  • Hardware Redundancy (AREA)

Abstract

本发明公开了一种业务处理方法及装置，其中，该方法包括：主业务单板为接口选择业务单板，该主业务单板将分布式的业务集中在选择的该业务单板上进行处理，解决了相关技术中由业务单板各自实现业务单板选择功能导致无法复用的问题。

Description

业务处理方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及业务处理方法及装置。
背景技术
运营商组网中，分布式业务的下放已经成为趋势，业务的状态计算、消息处理以及数据区等保存都在L-CPU上，以充分利用L-CPU的处理能力和业务单板的存储资源，减轻主控R-CPU的负担，提高用户业务的处理速度和接入用户业务的容量。以DHCP(动态主机配置协议)smartgroup(下文统称SG)接口跨板的需求为例来说明该问题。
DHCP的协议处理是分布式的，状态机和消息处理以及DHCP relay的数据区保存都在L-CPU上，以充分利用L-CPU的处理能力和存储空间，提高用户的接入速度和接入用户的容量。当用户侧接口是跨板SG接口时，DHCP协议报文是本板投递，也就是说同一个host用户的同一个会话的不同报文，经过同一个SG接口，可能投递到不同的L-CPU上，这会导致DHCP模块状态机和数据区异常。
解决上述跨板的问题的关键在于将同一host用户的同一会话的所有报文投递到同一个点处理，以保证状态机和数据区的一致性，这里涉及到两个问题，一个是用户的粒度问题，一个是集中点的选择问题。
用户粒度问题：理想状态是将粒度降低到真正的用户，即同一个SG接口的不同用户的报文，可以投递到不同的集中点处理，只需要保证同一个用户投递到同一集中点即可，但这样处理复杂，特别是考虑到作为DHCP relay时，设备接收到server报文，需要将server回程报文投递到用户原来所在处理点，需要一张用户级别的大容量的表，实现的代价太高，带来的益处却不是很大，故考虑退一步的选择：同一个SG接口的所有用户放在一个集中点处理。
集中点选择问题：最简单且最直观的集中点当然是R-CPU，但这样带来的问题是用户接入数量和接入速率都受限，并会在一定程度上影响R-CPU的其他模块的性能，在SG口接入时，DHCP就完全失去了分布式实现的功能。
针对相关技术中由业务单板各自实现业务单板选择功能导致无法复用的问题，还未提出有效的解决方案。
发明内容
本发明实施例提供了一种业务处理方法及装置，以至少解决了相关技术中由业务单板各自实现业务单板选择功能导致无法复用的问题。
根据本发明实施例的一个方面，提供了一种业务处理方法，所述方法包括：主业务单板 为接口选择业务单板；所述主业务单板将分布式的业务集中在选择的所述业务单板上进行处理。
进一步地，在主业务单板为接口选择业务单板之后，所述方法还包括：所述主业务单板将所有业务单板写入到接口的端口属性表，并将所述端口属性表同步到各个业务单板。
进一步地，所述主业务单板为接口选择业务单板包括：所述主业务单板根据业务在业务单板粒度上均匀分布的原则为接口选择业务单板。
进一步地，所述方法还包括：所述主业务单板通过端口管理的成员接口删除通知消息或端口不一致的通知消息检测业务单板是否发生故障；在所述业务单板发生故障的情况下，所述主业务单板为接口重新选择业务单板。
进一步地，所述方法还包括：所述主业务单板接收为接口选择指定业务单板的指令；所述主业务单板根据所述指令为接口选择所述指定业务单板。
根据本发明实施例的另一方面，还提供了一种业务处理装置，应用于主业务单板，所述装置包括：选择模块，设置为为接口选择业务单板；处理模块，设置为将分布式的业务集中在选择的所述业务单板上进行处理。
进一步地，所述装置还包括：同步模块，设置为将所有业务单板写入到接口的端口属性表，并将所述端口属性表同步到各个业务单板。
进一步地，所述选择模块包括：选择单元，设置为根据业务在业务单板粒度上均匀分布的原则为接口选择业务单板。
进一步地，所述装置还包括：检测模块，设置为通过端口管理的成员接口删除通知消息或端口不一致的通知消息检测业务单板是否发生故障；重新选择模块，设置为在所述业务单板发生故障的情况下，为接口重新选择业务单板。
进一步地，所述装置还包括：接收模块，设置为接收为接口选择指定业务单板的指令；选择指定模块，设置为根据所述指令为接口选择所述指定业务单板。
通过本发明，采用主业务单板为接口选择业务单板；所述主业务单板将分布式的业务集中在选择的所述业务单板上进行处理，解决了相关技术中由业务单板各自实现业务单板选择功能导致无法复用的问题。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的业务处理方法的流程图；
图2是根据本发明实施例的业务处理装置的框图；
图3是根据本发明优选实施例的业务处理装置的框图一；
图4是根据本发明优选实施例的业务处理装置的框图二；
图5是根据本发明优选实施例的业务处理装置的框图三；
图6是根据本发明优选实施例的业务处理装置的框图四；
图7是根据本发明实施例的主业务单板的系统架构图；
图8是根据本发明实施例的业务单板之间交互的示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
本发明实施例还提供了一种业务处理方法，图1是根据本发明实施例的业务处理方法的流程图，如图1所示，包括：
步骤S102，主业务单板为接口选择业务单板；
步骤S104，该主业务单板将分布式的业务集中在选择的该业务单板上进行处理。
通过上述步骤，主业务单板为接口选择业务单板，该主业务单板将分布式的业务集中在选择的该业务单板上进行处理，解决了相关技术中由业务单板各自实现业务单板选择功能导致无法复用的问题。
在一个可选的实施例中，在主业务单板为接口选择业务单板之后，该主业务单板将所有业务单板写入到接口的端口属性表，并将该端口属性表同步到各个业务单板。
主业务单板为接口选择业务单板可以包括：该主业务单板根据业务在业务单板粒度上均匀分布的原则为接口选择业务单板。
为了保证业务单板正常故障，主业务单板通过端口管理的成员接口删除通知消息或端口不一致的通知消息检测业务单板是否发生故障；在该业务单板发生故障的情况下，该主业务单板为接口重新选择业务单板。
为了更加灵活地选择业务单板，主业务单板接收为接口选择指定业务单板的指令，该主业务单板根据该指令为接口选择该指定业务单板。
本发明实施例还提供了一种业务处理装置，应用于主业务单板，图2是根据本发明实施例的业务处理装置的框图，如图2所示，该装置包括：
选择模块22，设置为为接口选择业务单板；
处理模块24，设置为将分布式的业务集中在选择的该业务单板上进行处理。
图3是根据本发明优选实施例的业务处理装置的框图一，如图3所示，该装置还包括：同步模块32，设置为将所有业务单板写入到接口的端口属性表，并将该端口属性表同步到各个业务单板。
图4是根据本发明优选实施例的业务处理装置的框图二，如图4所示，选择模块24包括：选择单元42，设置为根据业务在业务单板粒度上均匀分布的原则为接口选择业务单板。
图5是根据本发明优选实施例的业务处理装置的框图三，如图5所示，该装置还包括：
检测模块52，设置为通过端口管理的成员接口删除通知消息或端口不一致的通知消息检测业务单板是否发生故障；
重新选择模块54，设置为在该业务单板发生故障的情况下，为接口重新选择业务单板。
图6是根据本发明优选实施例的业务处理装置的框图四，如图6所示，该装置还包括：
接收模块62，设置为接收为接口选择指定业务单板的指令；
选择指定模块64，设置为根据该指令为接口选择该指定业务单板。
针对相关技术中存在的上述问题，下面结合具体的可选实施例进行进一步说明，下述可选实施例结合了上述可选实施例及其可选实施方式。
本发明实施例提供了一个通用业务单板选择方法，可以支持各种业务各种类型接口的业务单板选择，将分布式的业务集中在业务单板上处理。解决了现有的业务单板选择功能，是各业务单板各自实现，代码逻辑重复而实现细节各有差别，无法复用。
图7是根据本发明实施例的主业务单板的系统架构图，如图7所示，主业务单板R-CPU包括主备同步库、业务单板选择模块和端口管理，其中，端口管理里包括端口也属性表，业务单板选择模块规划位于R-CPU的协议栈进程，功能是为接口选择一个业务单板，将分布式的业务集中在选择的业务单板上处理，当前不仅支持SG接口，还可以扩展到其他类型的聚合接口。
图8是根据本发明实施例的业务单板之间交互的示意图，如图8所示，SG接口创建时，即由端口管理通知业务单板选择模块，业务单板选择模块查询端口管理，获得SG接口的成员接口，从中选取之一作为业务单板。如果没有查询到成员接口，可能是时序问题或者用户还没有配置，业务单板选择模块等待端口管理的成员接口加入通知，得到通知时再开始选择业务单板。这种选择方式会导致在大多数情况下会选择SG的第一个配置成员作为业务单板，因此这一方面需要用户在配置多个SG接口时尽量将第一个成员配置为不同的单板的接口，另外一个方面，为用户提供命令，手工指定业务单板。
选择完成后，业务单板选择模块将业务单板写入到接口的端口属性表，由端口管理模块将此属性同步到各个业务单板。选择完成后在SG接口的生存期不再改变，即使SG接口的成员变化。业务单板的选择要保证业务的在单板粒度上的均匀分布。业务单板故障需重新选择业务单板，业务单板选择模块通过端口管理的成员接口删除通知消息或者端口不一致的通知 消息感知业务单板的故障。在系统刚上电的时候，业务单板选择模块可以延时180秒后再为SG接口选择业务单板，这样做的目的是等待各个业务单板上电成功，尽量避免将业务单板选择为同一个单板。支持命令配置，可以手工指定SG接口的业务单板。
分布式架构中，SG用户的处理逻辑需要确定于固定的一点，如果将SG处理点上移至主控，从实现的角度讲最为简单，但由于交换机vlan range口接入等场景下，用户数目较多，因此存在大量用户集中上线或下线的可能。为了避免集中处理大量用户侧报文对R-CPU造成压力，仍需要将SG用户处理逻辑下放至业务单板。
如图8所示，DHCP支持跨板的SG接口为例，业务单板选择模块的实施步骤包括：
步骤1，端口管理模块将SG接口的增加，删除消息通知给业务单板选择模块；
步骤2，业务单板选择模块将为SG接口选择的业务单板作为端口属性写入到端口属性表；
步骤3，端口管理将业务单板的端口属性同步到业务单板；
步骤4，用户侧SG接口入向报文，或者设备作为DHCP relay时的网络侧报文；
步骤5，当步骤4为用户侧SG接口入向报文时，业务模块(DHCP模块)的回调函数根据报文入接口查询端口管理模块得到业务单板；
步骤6，当步骤4为网络侧报文时，业务模块(DHCP模块)的回调函数根据报文目的地址查询路由，得到报文出接口，即用户侧接口，如果出接口是SG接口，则查询端口管理模块的业务单板；
步骤7，Lpp根据业务模块回调函数返回的业务单板，将报文投递到业务单板。
因为业务单板没有主备保护，并且可能存在接口不再选择的业务单板上的情况，在这种情况下如果选择的业务单板离线，需要重新选择单板会导致业务在一定时间间隔内中断，所以业务单板选择模块提供了用户手工配置指定业务单板的功能，特别地，当用户对可靠性要求很高时(比如要求插拔单板业务不中断)并且用户对性能要求不是很高时，可以手工指定业务单板为R-CPU。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
上述的本发明实施例，可以应用于通信领域，解决了相关技术中由业务单板各自实现业务单板选择功能导致无法复用的问题。

Claims (10)

  1. 一种业务处理方法，所述方法包括：
    主业务单板为接口选择业务单板；
    所述主业务单板将分布式的业务集中在选择的所述业务单板上进行处理。
  2. 根据权利要求1所述的方法，其中，在主业务单板为接口选择业务单板之后，所述方法还包括：
    所述主业务单板将所有业务单板写入到接口的端口属性表，并将所述端口属性表同步到各个业务单板。
  3. 根据权利要求1所述的方法，其中，所述主业务单板为接口选择业务单板包括：
    所述主业务单板根据业务在业务单板粒度上均匀分布的原则为接口选择业务单板。
  4. 根据权利要求3所述的方法，其中，所述方法还包括：
    所述主业务单板通过端口管理的成员接口删除通知消息或端口不一致的通知消息检测业务单板是否发生故障；
    在所述业务单板发生故障的情况下，所述主业务单板为接口重新选择业务单板。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述方法还包括：
    所述主业务单板接收为接口选择指定业务单板的指令；
    所述主业务单板根据所述指令为接口选择所述指定业务单板。
  6. 一种业务处理装置，应用于主业务单板，所述装置包括：
    选择模块，设置为为接口选择业务单板；
    处理模块，设置为将分布式的业务集中在选择的所述业务单板上进行处理。
  7. 根据权利要求6所述的装置，其中，所述装置还包括：
    同步模块，设置为将所有业务单板写入到接口的端口属性表，并将所述端口属性表同步到各个业务单板。
  8. 根据权利要求6所述的装置，其中，所述选择模块包括：
    选择单元，设置为根据业务在业务单板粒度上均匀分布的原则为接口选择业务单板。
  9. 根据权利要求7所述的装置，其中，所述装置还包括：
    检测模块，设置为通过端口管理的成员接口删除通知消息或端口不一致的通知消息检测业务单板是否发生故障；
    重新选择模块，设置为在所述业务单板发生故障的情况下，为接口重新选择业务单板。
  10. 根据权利要求6至9中任一项所述的装置，其中，所述装置还包括：
    接收模块，设置为接收为接口选择指定业务单板的指令；
    选择指定模块，设置为根据所述指令为接口选择所述指定业务单板。
PCT/CN2016/077576 2015-07-27 2016-03-28 业务处理方法及装置 WO2016177187A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510448020.X 2015-07-27
CN201510448020.XA CN106411544A (zh) 2015-07-27 2015-07-27 业务处理方法及装置

Publications (1)

Publication Number Publication Date
WO2016177187A1 true WO2016177187A1 (zh) 2016-11-10

Family

ID=57217516

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/077576 WO2016177187A1 (zh) 2015-07-27 2016-03-28 业务处理方法及装置

Country Status (2)

Country Link
CN (1) CN106411544A (zh)
WO (1) WO2016177187A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114978868A (zh) * 2022-07-01 2022-08-30 杭州迪普科技股份有限公司 基于oam环路自检网络报文加速芯片功能异常的方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119208A (zh) * 2007-08-28 2008-02-06 福建星网锐捷网络有限公司 交换机、业务处理单板及交换单板
CN101127930A (zh) * 2007-09-10 2008-02-20 中兴通讯股份有限公司 一种通过单个空闲开销字节复用传输多种业务数据的方法
CN101247557A (zh) * 2008-01-21 2008-08-20 中兴通讯股份有限公司 一种业务处理方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119208A (zh) * 2007-08-28 2008-02-06 福建星网锐捷网络有限公司 交换机、业务处理单板及交换单板
CN101127930A (zh) * 2007-09-10 2008-02-20 中兴通讯股份有限公司 一种通过单个空闲开销字节复用传输多种业务数据的方法
CN101247557A (zh) * 2008-01-21 2008-08-20 中兴通讯股份有限公司 一种业务处理方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114978868A (zh) * 2022-07-01 2022-08-30 杭州迪普科技股份有限公司 基于oam环路自检网络报文加速芯片功能异常的方法和装置
CN114978868B (zh) * 2022-07-01 2023-04-25 杭州迪普科技股份有限公司 基于oam环路自检网络报文加速芯片功能异常的方法和装置

Also Published As

Publication number Publication date
CN106411544A (zh) 2017-02-15

Similar Documents

Publication Publication Date Title
CN110113441B (zh) 实现负载均衡的计算机设备、系统和方法
US11005752B2 (en) Packet transmission
US9071508B2 (en) Distributed fabric management protocol
US9960923B2 (en) Handling of digital certificates
CN103607430A (zh) 一种网络处理的方法和系统及网络控制中心
CN106911648B (zh) 一种环境隔离方法及设备
CN102185718A (zh) 一种系统升级方法及其装置
WO2018024121A1 (zh) 一种网络功能nf管理方法及nf管理设备
US20190370376A1 (en) High-availability network device database synchronization
CN103631652A (zh) 虚拟机迁移的实现方法及系统
CN104092746A (zh) 一种运维审计系统及用在其系统中的网络负载均衡方法
WO2020057445A1 (zh) 一种通信系统、方法及装置
CN109962806B (zh) 一种传送网子切片管理方法和装置
CN104753707A (zh) 一种系统维护方法及网络交换设备
WO2016180156A1 (zh) 路由器集群的升级系统、方法及装置
CN108366087B (zh) 一种基于分布式文件系统的iscsi服务实现方法和装置
US20120284274A1 (en) Method and device for service management
WO2021077940A1 (zh) 一种虚拟化方法及装置
CN112995335A (zh) 一种位置感知的容器调度优化系统及方法
WO2016177187A1 (zh) 业务处理方法及装置
CN108833613B (zh) 一种动态主机配置协议的实现方法及系统
WO2016188081A1 (zh) 扩展端口的处理方法、装置及系统
CN115022261B (zh) 一种基于堆叠环境的组播表项同步方法、设备及介质
WO2015154504A1 (zh) 一种基站、基站负荷分担装置及方法
US10516625B2 (en) Network entities on ring networks

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

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

Country of ref document: EP

Kind code of ref document: A1