WO2011131087A1 - 日志管理方法、系统、主控板和本地单板 - Google Patents

日志管理方法、系统、主控板和本地单板 Download PDF

Info

Publication number
WO2011131087A1
WO2011131087A1 PCT/CN2011/072484 CN2011072484W WO2011131087A1 WO 2011131087 A1 WO2011131087 A1 WO 2011131087A1 CN 2011072484 W CN2011072484 W CN 2011072484W WO 2011131087 A1 WO2011131087 A1 WO 2011131087A1
Authority
WO
WIPO (PCT)
Prior art keywords
log
main control
control board
board
priority
Prior art date
Application number
PCT/CN2011/072484
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 WO2011131087A1 publication Critical patent/WO2011131087A1/zh

Links

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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H04L41/5022—Ensuring fulfilment of SLA by giving priorities, e.g. assigning classes of service

Definitions

  • the log management method, the system, the main control board, and the local board are submitted to the Chinese Patent Office on April 19, 2010.
  • the application number is 201010153026.1, and the invention name is "log management method, system, main control board, and local board.”
  • the priority of the Chinese Patent Application the entire contents of which is incorporated herein by reference.
  • the present invention relates to the field of computer technologies, and in particular, to a log management method, a system, a main control board, and a local board. BACKGROUND OF THE INVENTION When eNobeB is overloaded, congestion occurs and system resources are limited. System resources mainly focus on CPU usage and packet flow control. When these resources are overloaded, the system may crash.
  • the main control board manages the log according to whether it is overloaded. First, it detects whether the main control board is overloaded. If an overload occurs, the log is not written. If no overload occurs, the storage log continues to be received. The local board also logs the flow based on the overload of the system resources. The local board is faulty. If the overload occurs, the flow control log is sent. If no overload occurs, the log is sent to the main control board. SUMMARY OF THE INVENTION The embodiments of the present invention provide a log management method, a system main control board, and a local board.
  • the main board log management method according to claim 1 is provided.
  • the local board log management method according to claim 4 is provided.
  • the local board log management method according to claim 6 is provided.
  • a main control board as claimed in claims 7 and 17 is provided.
  • a log management system as claimed in claims 12, 19 is provided.
  • a log management method according to claims 15 and 16 is provided.
  • the embodiment of the present invention detects the overload level of the current system resource; determines whether the priority of the log on the main control board reaches the range that needs to be discarded according to the overload level indication; and discards the log when the determination is yes. Discard logs according to the priority and overload level of different logs. The higher the overload level, the larger the range to be discarded. The lower the overload level, the smaller the range of flow control. It is better to ensure that important high priority logs are sent first. According to the priority attribute of the log, it can provide a very good differentiated service for the management.
  • FIG. 1 is a flow chart of a first embodiment of a method for managing a log of a main control board of the present invention
  • FIG. 2 is a flow chart of a second embodiment of a method for managing a log of a main control board of the present invention
  • FIG. 3 is a flowchart of a third embodiment of a local board log management method according to the present invention.
  • FIG. 4 is a schematic structural diagram of a main control board according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a local board according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a log management system according to an embodiment of the present invention.
  • FIG. 7 is a schematic flow chart of an application scenario of the present invention.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS In the research and improvement of the prior art, the inventors of the present invention have found that when the main control board is congested, if the method of managing logs in the prior art is used, it is detected whether the main control board is overloaded. When the log is discarded when an overload occurs, the importance and priority of the log cannot be distinguished. That is, the same way is used to manage logs regardless of the level of overload. It is impossible to provide differentiated services with maximum capability for log management based on attributes such as priority and importance of logs.
  • the embodiment of the invention provides a local board that distinguishes the log priority and the resource overload degree.
  • Main control board log management method The embodiment of the invention further provides a corresponding log management system for executing the above log management method. The details are described below separately.
  • the basic process of the main control board log management method in the first embodiment of the present invention can be referred to FIG. 1.
  • the method mainly includes:
  • Step 101 Detect the current overload level of the main control board.
  • the overload level of the main control board is judged according to the respective overload thresholds of the overload level of the main control board preset by the user and the remaining space of the current main control board.
  • the corresponding overload level of the main control board is ⁇ . The less the remaining space, the higher the overload level of the main control board.
  • Step 102 Determine whether the priority of the log on the main control board is within the priority range of the log corresponding to the current overload level of the main control board; if yes, go to step 103, if no, go to step 104.
  • each overload level corresponds to the priority range of a log, which is preset by the user. Determine whether the priority of all logs on the main control board is within the priority of the log corresponding to the current overload level. If the priority of some logs on the main control board is within the priority of the log corresponding to the current overload level, then these logs are within the log range that can be discarded.
  • Step 103 Discard the log whose priority is within the priority range of the log corresponding to the current overload level.
  • the log can be: The priority of some logs is lower than the highest priority in the priority range of the log corresponding to the current overload level, and the logs are discarded.
  • Step 104 continue to save the log.
  • the priority of some logs is higher than the highest priority in the priority range of the log corresponding to the current overload level, and these logs are saved.
  • the embodiment of the present invention detects the overload level of the current system resource; determines whether the priority of the log on the main control board reaches the range that needs to be discarded according to the overload level indication; and discards the log when the determination is yes.
  • the logs are discarded according to the priority and overload level of different logs. The higher the overload level, the larger the range to be discarded. The lower the overload level, the smaller the discarded range. Can be more Good guarantees that important high-priority logs are sent first, and better differentiated services are provided.
  • the log management method in the embodiment of the present invention is described in detail below.
  • the maximum difference between the second embodiment of the log management method of the present invention and the first embodiment is: by sending a back pressure signal to the local single Board, which adds control of the local board.
  • the log management method includes:
  • preset the parameters of the main control board According to the overload thresholds of the main control board preset by the user, set the overload levels of the system resources corresponding to the respective overload thresholds, and set the logs to be discarded indicated by the respective overload levels.
  • the priority range, and the back pressure signal corresponding to each overload threshold indicates the range of logs that are rejected for reception.
  • Step 201 Detect an overload level of the current main control board.
  • the overload threshold of the main control board preset by the user and the overload condition of the current main control board, the overload level of the current system resource is obtained.
  • the corresponding overload level of the main control board is ⁇ . The less the remaining space, or the less the current system resources remain, the higher the overload level of the main control board.
  • Step 202 Determine whether the priority of the log on the main control board is within the priority range of the log corresponding to the current overload level of the main control board; if yes, go to step 203, if no, go to step 204.
  • each overload level corresponds to the priority range of a log, which is preset by the user. Determine whether the priority of all logs on the main control board is within the priority of the log corresponding to the current overload level. If the priority of some logs on the main control board is within the priority of the log corresponding to the current overload level, then these logs are within the log range that can be discarded.
  • Step 203 Discard the log whose priority is within the priority range of the log corresponding to the current overload level.
  • the log can be: The priority of some logs is lower than the highest priority in the priority range of the log corresponding to the current overload level, and the logs are discarded.
  • Step 204 continue to save the log.
  • the priority of some logs is higher than the log of the current overload level. These logs are saved with the highest priority in the range.
  • Step 205 Generate a back pressure signal corresponding to a current overload level of the main control board according to a current overload level of the main control board.
  • Step 206 Send the back pressure signal to the local board, so that the local board sends a log whose priority is not within the priority range of the log rejected by the back pressure signal, and the back pressure signal indicates that the main control board rejects The range of priorities for the received logs.
  • the embodiment of the present invention detects the overload level of the current system resource; determines whether the priority of the log on the main control board reaches the range that needs to be discarded according to the overload level; and discards the log when the determination is yes, Send a backpressure signal corresponding to the overload level to control the local board to send logs. Discard logs based on the priority and overload level of different logs. The higher the degree of overload, the larger the range that is discarded, and the lower the degree of overload, the smaller the range that is discarded. The back pressure signal can be reacted to the local board according to the overload level of the master.
  • the local board is not only affected by the overload of system resources, but also ensures that important high-priority logs are sent preferentially, which provides better differentiated services.
  • the basic process of the local board log management method in the third embodiment of the present invention can be referred to FIG. 3, and the method mainly includes:
  • Step 301 Detect an overload level of a current system resource.
  • Step 302 Determine whether the priority of the log on the board reaches the range of the priority of the log corresponding to the overload level, that is, determine whether the priority of the log is in the range to be flow controlled; if yes, go to step 303. If no, go to step 304.
  • Step 303 Perform flow control on the log.
  • the step may be: first, detecting an overload level of the current system resource; and then determining whether the priority of the log on the board is within a priority range of the log corresponding to the overload level; and finally, when the determination is no , send the log, when the judgment is yes, the log is not sent. In this way, only the logs that are not in the priority range of the log corresponding to the overload level are sent, so that the flow control is performed according to the priority of the log and the overload of the system resources, and the differentiated service is better provided.
  • the log itself carries a priority
  • each overload level corresponds to a priority range of a log, and the corresponding relationship is preset by the user. For example, the priority of the log is 1, 2, and 3, and the priority of the 3 is the highest.
  • the user can set the log priority range to 1 when the overload level is 1. 2, then when the system overload level is 1, only the log with priority 3 can be sent.
  • Step 304 Send, according to the received backpressure signal of the main control board, a log whose priority is not within the range of the priority of the log rejected by the back pressure signal to the main control board, where the back pressure signal indicates that the main control board rejects The priority range of the received logs.
  • the embodiment of the present invention detects the overload level of the current system resource, and determines whether the priority of the log on the system resource reaches the range that needs to be discarded according to the overload level; when the determination is yes, the flow is controlled by the log, and at the same time, according to
  • the backpressure signal corresponding to the overload level controls the local board to send logs.
  • the logs are discarded according to the priority and overload level of different logs. The higher the overload level, the larger the range to be discarded. The lower the overload level, the smaller the discarded range.
  • the backpressure signal can be reversed on the local board according to the overload level of the master.
  • the local board is not only affected by the overload of the system resources, but also can ensure that the important high-priority logs are sent preferentially, which provides better difference. Service.
  • the main control board for executing the above-mentioned main control board log management method will be described below, and its structure is shown in FIG.
  • the main control board includes:
  • the main control detection module 41 is configured to detect the current overload level of the main control board.
  • the main control judging module 42 is configured to determine whether the priority of the log on the main control board is within the priority range of the log corresponding to the current overload level, and the priority range of the log corresponding to the overload level is preset by the user.
  • the main control execution module 43 is configured to discard the message when the main control determination module determines to be YES, and save the message when the main control determination module determines to be no.
  • the main control board further includes:
  • the back pressure signal module 44 is configured to generate a back pressure signal corresponding to the current overload level of the main control board according to the current overload level of the main control board, and send the back pressure signal to the local board, where the back pressure signal indicates the main control board The priority range of logs that are rejected.
  • the main control board further includes:
  • the main control preset module 45 is configured to set, according to an overload threshold of each overload level of the corresponding main control board preset by the user, a priority range of the log corresponding to each overload level, and a rejection of the back pressure signal corresponding to each overload level.
  • the priority range of the log The embodiment of the present invention detects the overload level of the current system resource; determines whether the priority of the log on the main control board reaches the range that needs to be discarded according to the overload level indication; and discards the log when the determination is yes.
  • the back pressure signal corresponding to the overload level is sent to control the local board to send the log.
  • the logs are discarded according to the priority and overload level of different logs. The higher the overload level, the larger the range to be discarded.
  • the back pressure signal can be reacted to the local board according to the overload level of the master.
  • the local board is not only affected by the overload of the system resources, but also can ensure that the important high-priority logs are sent preferentially, and the differentiated services are better provided.
  • the local board for performing the above-mentioned local board log management method is described below.
  • the structure of the board is shown in Figure 5.
  • the local board includes:
  • the board detecting module 51 is configured to determine whether the system resource is overloaded.
  • the board execution module 52 is configured to: when the board detecting module 51 determines that the system resource is not overloaded, send a log whose priority is not within the log priority range of the rejected receiving signal indicated by the back pressure signal according to the back pressure signal of the main control board. Main control board.
  • the single board detecting module 51 includes:
  • the overload detecting unit 511 is configured to detect an overload level of the current system resource when the board detecting module 51 determines that the system resource is overloaded.
  • the overload determining unit 512 is configured to determine whether the priority of the log on the board is within the priority of the log corresponding to the overload level.
  • the board execution module 52 is further configured to send the message when the overload determining unit 512 determines to be no.
  • the embodiment of the present invention determines whether the priority of the log on the system resource reaches the range that needs to be discarded according to the overload level indication by detecting the overload level of the current system resource.
  • the log is flow-controlled.
  • the local board sends a log according to the backpressure signal corresponding to the overload level.
  • the logs are discarded according to the priority and overload level of different logs. The higher the overload level, the larger the range to be discarded. The lower the overload level, the smaller the discarded range.
  • the back pressure signal can be reacted to the local board according to the overload level of the master.
  • Local boards are not only affected by the degree of system resource overload. Can better ensure that important high priority logs are sent first, better For differentiated services.
  • FIG. 6 is a schematic structural diagram thereof.
  • the log management system includes a main control board 1 and a local single board 2, where:
  • the main control board 1 is configured to detect the current overload level of the main control board; determine whether the priority of the log on the main control board is within the priority range of the log corresponding to the current overload level preset by the user; If the determination is yes, the log is discarded, and when the main control determination module determines to be no, the log is saved;
  • the local board 2 is used to determine whether the system resources are overloaded. When the judgment is no, the log is sent to the main control board.
  • the main control board 1 is further configured to send a back pressure signal corresponding to the current overload level to the local board 2;
  • the local board 2 is further configured to: when the system resource is overloaded, the flow control log is used.
  • the system resource is not overloaded, according to the back pressure signal of the main control board, the priority of the log that refuses to receive the priority is not indicated by the back pressure signal.
  • the log in the range is given to the main control board.
  • the local board 2 is further configured to detect an overload level of the current system resource; determine whether the priority of the log on the local board is within a log priority range corresponding to the overload level; when the determination is negative, send The log.
  • main control board 1 and the local single board 2 have been described in detail above, and are not described herein again.
  • the overload level of system resources is divided into three levels: high, medium, and low.
  • the overload level of the main control board is also divided into three levels: high, medium, and low. The user sets the main control board to generate a back pressure signal.
  • the overload level of the main control board is medium. According to the overload level (middle), discard the priority levels of 1 and 2. According to the overload level (middle), the back pressure signal corresponding to the overload level is sent to the local board. The back pressure signal indicates that the local board does not send the priority levels of 1 and 2.
  • the detection system resources are not overloaded.
  • the counter-voltage signal sent by the main control board is received.
  • the back-pressure signal only the log with the priority of 3 is sent.
  • the local board sends only the log with the priority of 3 to the main control board.
  • the embodiment of the present invention detects the overload level of the current system resource, and determines whether the priority of the log on the system resource reaches the range that needs to be discarded according to the overload level; when the determination is yes, the log is flow-controlled.
  • the local board sends logs according to the back pressure signal corresponding to the overload level.
  • the logs are discarded according to the priority and overload level of different logs. The higher the overload level, the larger the range to be discarded. The lower the overload level, the smaller the discarded range.
  • the back pressure signal can be reacted to the local board according to the overload level of the master.
  • the local board is not only affected by the overload of system resources, but also ensures that important high-priority logs are sent preferentially, which provides better differentiated services.
  • the program can be stored in a computer readable storage medium.
  • the storage medium can include: ROM, RAM, disk or CD, etc.
  • the log management method, system, local board, and master control provided by the embodiment of the present invention are provided.

Landscapes

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

Description

日志管理方法、 系统、 主控板和本地单板 本申请要求于 2010 年 04 月 19 日提交中国专利局、 申请号为 201010153026.1、 发明名称为 "日志管理方法、 系统、 主控板和本地单板" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域 本发明涉及计算机技术领域， 具体涉及一种日志管理方法、 系统、 主 控板和本地单板。 背景技术 eNobeB超负荷运载时会出现拥塞， 系统资源是有限的， 系统资源主要 关注于 CPU的占用率和消息包流控等， 当这些资源过载时， 可能会导致系 统的崩溃。
目前， 主控板会根据是否过载来管理日志， 首先， 检测主控板是否过 载， 若发生过载则不写日志， 若没有发生过载， 则继续接收保存日志。 本 地单板也会根据系统资源的过载情况来流控日志， 首先检测本地单板是否 过载， 若发生过载则流控日志， 若不发生过载， 则发送日志给主控板。 发明内容 本发明实施例提供一种日志管理方法、 系统主控板和本地单板。
一方面提供了如权利要求 1所述的主控板日志管理方法。
一方面提供了如权利要求 4所述的本地单板日志管理方法。
一方面提供了如权利要求 6所述的本地单板日志管理方法。
一方面提供了如权利要求 7、 17所述的主控板。
一方面提供了如权利要求 10、 18所述的单板。
一方面提供了如权利要求 12、 19所述的日志管理系统。 一方面提供了如权利要求 15、 16所述的日志管理方法。
本发明实施例通过检测当前系统资源的过载级别； 判断主控板上的日 志的优先级是否达到所述过载级别指示的需要被丟弃的范围； 在判断为是 时丟弃该日志。 根据不同日志的优先级和过载级别丟弃日志， 过载程度越 高， 被丟弃的范围就越大， 过载程度越低， 被流控的范围就越小。 可以更 好的保证重要的高优先级日志优先被发送。 可以根据日志的优先级属性， 对曰志管理提供很好的差异化服务。 附图说明 为了更清楚地说明本发明实施例中的技术方案， 下面将对实施例或现 有技术描述中所需要使用的附图作一简单地介绍， 显而易见地， 下面描述 中的附图是本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付 出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1是本发明主控板日志管理方法的第一实施例流程图；
图 2是本发明主控板日志管理方法的第二实施例流程图；
图 3是本发明本地单板日志管理方法的第三实施例流程图；
图 4是本发明实施例提供的主控板的结构示意图；
图 5是本发明实施例提供的本地单板的结构示意图；
图 6是本发明实施例提供的日志管理系统的结构示意图；
图 7是本发明应用场景的流程示意图。 具体实施方式 在对现有技术的研究和改进过程中， 本发明的发明人发现， 当主控板 发生拥塞时， 若采用现有技术中管理日志的方法， 检测主控板是否发生过 载， 在发生过载的时候丟弃日志， 则不能区分日志的重要性和优先级。 即 无论过载程度高低都采用同样的方式来管理日志， 无法根据日志的优先级 和重要性等属性， 对日志管理提供最大能力的差异化服务。
本发明实施例提供一种区分日志优先级和资源过载程度的本地单板和 主控板日志管理方法。 本发明实施例还提供执行上述日志管理方法的相应 的日志管理系统。 以下分别进行详细说明。 本发明实施例一的主控板日志管理方法基本流程可参考图 1， 该方法主 要包括：
步骤 101， 检测主控板当前的过载级别。
根据用户预置的主控板过载级别的各个过载门限值和当前主控板的剩 余空间， 判断主控板的过载级别。
比如说： 主控板的剩余空间为 Y， 小于某个过载门限值 X， 则主控板当 前对应的过载级别为 ζ。 剩余空间越少， 主控板当前对应的过载级别可能越 高。
步骤 102， 判断主控板上的日志的优先级是否在所述主控板的当前过载 级别对应的日志的优先级范围内； 若是， 则进入步骤 103， 若否， 则进入步 骤 104。
曰志本身携带有优先级， 每个过载级别都对应一个日志的优先级的范 围， 这个对应关系是由用户预置的。 判断主控板上的所有日志的优先级是 否在当前过载级别对应的日志的优先级的范围内。 如果主控板上的某些日 志的优先级是在当前过载级别对应的日志的优先级的范围内， 则这些日志 是在可以被丟弃的日志范围内。
步骤 103， 丟弃优先级在当前过载级别对应的日志的优先级范围内的日 志
比如说可以是： 某些日志的优先级低于当前过载级别对应的日志的优 先级范围中的最高优先级， 则这些日志被丟弃。
步骤 104， 继续保存日志。
比如说可以是： 某些日志的优先级高于当前过载级别对应的日志的优 先级范围中的最高优先级， 则这些日志被保存。
本发明实施例通过检测当前系统资源的过载级别； 判断主控板上的日 志的优先级是否达到所述过载级别指示的需要被丟弃的范围； 在判断为是 时丟弃该日志。 根据不同日志的优先级和过载级别丟弃日志， 过载程度越 高， 被丟弃的范围就越大， 过载程度越低， 被丟弃的范围就越小。 可以更 好的保证重要的高优先级日志优先发送， 更好的提供了差异化服务。
为便于理解， 下面对本发明实施例中的日志管理方法进行详细描述， 请参阅图 2， 本发明日志管理方法第二实施例与第一实施例的最大不同是： 通过发送反压信号给本地单板， 增加了对本地单板的控制。
该日志管理方法包括：
首先要对主控板各参数进行预置： 根据用户预置的主控板各个过载门 限， 设置对应各个过载门限的系统资源的各个过载级别， 以及设置各个过 载级别指示的要被丟弃的日志的优先级范围， 和各个过载门限对应的反压 信号指示的拒绝接收的日志的范围。
步骤 201， 检测当前主控板的过载级别。
根据用户预置的主控板过载门限， 和当前主控板过载情况， 获得当前 系统资源的过载级别。
比如说： 主控板的剩余空间为 Y， 小于某个过载门限值 X， 则主控板当 前对应的过载级别为 Ζ。 剩余空间越少， 或者当前系统资源剩余越少， 主控 板当前对应的过载级别可能越高。
步骤 202， 判断主控板上的日志的优先级是否在所述主控板的当前过载 级别对应的日志的优先级的范围内； 若是， 则进入步骤 203， 若否， 则进入 步骤 204。
曰志本身携带有优先级， 每个过载级别都对应一个日志的优先级的范 围， 这个对应关系是由用户预置的。 判断主控板上的所有日志的优先级是 否在当前过载级别对应的日志的优先级的范围内。 如果主控板上的某些日 志的优先级是在当前过载级别对应的日志的优先级的范围内， 则这些日志 是在可以被丟弃的日志范围内。
步骤 203， 丟弃优先级在当前过载级别对应的日志的优先级范围内的日 志
比如说可以是： 某些日志的优先级低于当前过载级别对应的日志的优 先级范围中的最高优先级， 则这些日志被丟弃。
步骤 204， 继续保存日志。
比如说可以是： 某些日志的优先级高于当前过载级别对应的日志的优 先级范围中的最高优先级， 则这些日志被保存。
步骤 205， 根据主控板当前过载级别， 生成与主控板当前过载级别对应 的反压信号；
步骤 206， 发送所述反压信号给本地单板， 以使本地单板发送优先级不 在反压信号指示的拒绝接收的日志的优先级范围内的日志， 所述反压信号 指示主控板拒绝接收的日志的优先级的范围。
本发明实施例通过检测当前系统资源的过载级别； 判断主控板上的日 志的优先级是否达到所述过载级别指示的需要被丟弃的范围； 在判断为是 时丟弃该日志， 同时， 发送与过载级别对应的反压信号反控制本地单板发 送日志。 根据不同日志的优先级和过载级别丟弃日志。 过载程度越高， 被 丟弃的范围就越大， 过载程度越低， 被丟弃的范围就越小。 反压信号可以 根据主控的过载程度来反作用于本地单板。 本地单板不仅仅受系统资源过 载程度的影响， 可以更好的保证重要的高优先级日志优先发送， 更好的提 供了差异化服务。 本发明实施例三的本地单板日志管理方法基本流程可参考图 3， 该方法 主要包括：
步骤 301， 检测当前系统资源的过载级别；
步骤 302， 判断单板上的日志的优先级是否达到所述过载级别对应的曰 志的优先级的范围， 即判断日志的优先级是否在要被流控的范围； 若是则 进入步骤 303。 若否， 则进入步骤 304。
步骤 303， 对日志进行流控。 该步骤具体可以为： 首先， 检测当前系统 资源的过载级别； 然后， 判断单板上的日志的优先级是否在所述过载级别 对应的日志的优先级的范围内； 最后， 在判断为否时， 发送日志， 在判断 为是时， 则不发送该日志。 这样只发送不在过载级别对应的日志的优先级 范围内的日志， 从而实现了根据日志的优先级和系统资源的过载情况来对 曰志进行流控， 更好的提供了差异化的服务。
其中， 日志本身携带有优先级， 每个过载级别都对应一个日志的优先 级的范围， 这个对应关系是由用户预置的。 例如， 日志的优先级有 1、 2和 3， 3的优先级最高， 用户可以设置当过载级别为 1的时候日志优先级范围为 1和 2, 那么当系统过载级别为 1的时候， 只能发送优先级为 3的日志。
步骤 304， 根据收到的主控板的反压信号， 发送优先级不在反压信号指 示的拒绝接收的日志的优先级的范围内的日志给主控板， 该反压信号指示 主控板拒绝接收的日志的优先级范围。
本发明实施例通过检测当前系统资源的过载级别； 判断系统资源上的 日志的优先级是否达到所述过载级别指示的需要被丟弃的范围； 在判断为 是时流控该日志， 同时， 根据过载级别对应的反压信号反控制本地单板发 送日志。 根据不同日志的优先级和过载级别丟弃日志， 过载程度越高， 被 丟弃的范围就越大， 过载程度越低， 被丟弃的范围就越小。 反压信号可以 根据主控的过载程度来反作用于本地单板， 本地单板不仅仅受系统资源过 载程度的影响， 可以更好的保证重要的高优先级日志优先发送， 更好的提 供了差异化服务。 下面对用于执行上述主控板日志管理方法的主控板进行说明， 其结构 示意图参考图 4。
该主控板包括：
主控检测模块 41， 用于检测主控板当前的过载级别。
主控判断模块 42， 用于判断主控板上的日志的优先级是否在当前过载 级别对应的日志的优先级范围内， 过载级别对应的日志的优先级范围由用 户预置。
主控执行模块 43， 用于在主控判断模块判断为是时， 丟弃所述曰志， 在主控判断模块判断为否时， 保存所述曰志。
优选的， 主控板还包括：
反压信号模块 44， 用于根据主控板当前过载级别， 生成与主控板当前 过载级别对应的反压信号， 发送所述反压信号给本地单板， 所述反压信号 指示主控板拒绝接收的日志的优先级范围。
优选的， 主控板还包括：
主控预置模块 45， 用于根据用户预置的对应主控板各个过载级别的过 载门限， 设置各个过载级别对应的日志的优先级范围， 和各个过载级别对 应的反压信号指示的拒绝接收的日志的优先级范围。 本发明实施例通过检测当前系统资源的过载级别； 判断主控板上的日 志的优先级是否达到所述过载级别指示的需要被丟弃的范围； 在判断为是 时丟弃该日志。 同时， 发送与过载级别对应的反压信号反控制本地单板发 送日志。 根据不同日志的优先级和过载级别丟弃日志， 过载程度越高， 被 丟弃的范围就越大， 过载程度越低， 被丟弃的范围就越小。 反压信号可以 根据主控的过载程度来反作用于本地单板。 本地单板不仅仅受系统资源过 载程度的影响， 可以更好的保证重要的高优先级日志优先发送， 更好的提 供了差异化服务。
下面对用于执行上述本地单板日志管理方法的本地单板进行说明， 其 结构示意图参考图 5。
该本地单板包括：
单板检测模块 51， 用于判断系统资源是否过载。
单板执行模块 52， 用于在单板检测模块 51判断系统资源没有过载时， 根据主控板的反压信号， 发送优先级不在反压信号指示的拒绝接收的日志 优先级范围内的日志给主控板。
优选的， 单板检测模块 51包括：
过载检测单元 511， 用于在单板检测模块 51判断系统资源过载时， 检测 当前系统资源的过载级别。
过载判断单元 512， 用于判断单板上的日志的优先级是否在所述过载级 别对应的日志的优先级的范围内。
所述单板执行模块 52还用于在过载判断单元 512判断为否时， 发送所述 曰志。
本发明实施例通过检测当前系统资源的过载级别， 判断系统资源上的 日志的优先级是否达到所述过载级别指示的需要被丟弃的范围。 在判断为 是时流控该日志， 同时， 根据过载级别对应的反压信号反控制本地单板发 送日志。 根据不同日志的优先级和过载级别丟弃日志， 过载程度越高， 被 丟弃的范围就越大， 过载程度越低， 被丟弃的范围就越小。 反压信号可以 根据主控的过载程度来反作用于本地单板。 本地单板不仅仅受系统资源过 载程度的影响。 可以更好的保证重要的高优先级日志优先发送， 更好的提 供了差异化服务。 下面对用于执行上述本地单板日志管理方法和主控板日志管理方法的 日志管理系统进行说明， 其结构示意图参考图 6。 该日志管理系统包括， 主 控板 1和本地单板 2， 其中：
主控板 1， 用于检测主控板当前的过载级别； 判断主控板上的日志的优 先级是否在用户预置的与当前过载级别对应的日志的优先级范围内； 在主 控判断模块判断为是时， 丟弃所述日志， 在主控判断模块判断为否时， 保 存所述日志；
本地单板 2， 用于判断系统资源是否过载， 在判断为否时， 发送日志给 主控板。
优选地， 该主控板 1还用于发送与当前过载级别对应的反压信号给本地 单板 2;
该本地单板 2还用于在在判断系统资源过载时流控日志， 在系统资源没 有过载时， 根据主控板的反压信号， 发送优先级不在反压信号指示的拒绝 接收的日志优先级范围内的日志给主控板。
优选地， 该本地单板 2还用于检测当前系统资源的过载级别； 判断本地 单板上的日志的优先级是否在所述过载级别对应的日志优先级范围内； 在 判断为否时， 发送所述日志。
主控板 1和本地单板 2的结构和功能已经在上面进行详细描述， 在此 不再赘述。
为便于理解， 下面以具体的应用场景对上述实施例进行详细描述， 具 体的： 可同样参见图 7。
假设， 用户预先把日志分为优先级为 1、 2和 3， 相同优先级的日志存储 于相同的緩存。 本地单板发送日志时， 会优先发送优先级高的日志。 系统 资源的过载级别分为高、 中和低三个级别。 主控单板的过载级别也分为高、 中和低三个级别。 用户设置为主控板会产生反压信号。
对于主控板 1 :
检测主控板过载级别为中， 根据过载级别 （中）， 丟弃优先级为 1和 2的 曰志； 根据过载级别 （中）， 发送与过载级别对应的反压信号给本地单板， 该 反压信号指示本地单板不要发送优先级为 1和 2的曰志。
对于本地单板 2:
检测系统资源没有过载， 接收主控板发送的反压信号， 根据反压信号 指示只能发送优先级为 3的日志， 本地单板只发送优先级为 3的日志给主控 板。
本发明实施例通过检测当前系统资源的过载级别； 判断系统资源上的 日志的优先级是否达到所述过载级别指示的需要被丟弃的范围； 在判断为 是时流控该日志。 同时， 根据过载级别对应的反压信号反控制本地单板发 送日志。 根据不同日志的优先级和过载级别丟弃日志， 过载程度越高， 被 丟弃的范围就越大， 过载程度越低， 被丟弃的范围就越小。 反压信号可以 根据主控的过载程度来反作用于本地单板。 本地单板不仅仅受系统资源过 载程度的影响， 可以更好的保证重要的高优先级日志优先发送， 更好的提 供了差异化服务。 本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分 步骤是可以通过程序来指令相关的硬件来完成， 该程序可以存储于一计算 机可读存储介质中， 存储介质可以包括： ROM、 RAM, 磁盘或光盘等。
以上对本发明实施例所提供的日志管理方法、 系统、 本地单板和主控
行了阐述， 以上实施例的说明只是用于帮助理解本发明的方法及其核心思 想； 同时， 对于本领域的一般技术人员， 依据本发明的思想， 在具体实施 方式及应用范围上均会有改变之处， 综上所述， 本说明书内容不应理解为 对本发明的限制。

Claims

权利要求
1、 一种主控板日志管理方法， 其特征在于， 所述方法还包括： 检测主控板当前的过载级别；
判断主控板上的日志的优先级是否在所述主控板的当前过载级别对应 的日志的优先级范围内；
若是， 则丟弃所述主控板上的日志。
2、 如权利要求 1所述的方法， 其特征在于， 在检测当前主控的过载级 别之后还包括：
根据所述主控板当前的过载级别， 生成与所述主控板当前过载级别对 应的反压信号；
发送所述反压信号给本地单板， 所述反压信号指示所述主控板拒绝接 收的日志的优先级范围。
3、 如权利要求 1所述的方法， 其特征在于， 在检测所述当前的过载级 别之前还包括：
根据用户预置的对应主控板过载级别的过载门限， 设置所述过载级别 与日志的优先级范围的对应关系， 和所述过载级别对应的反压信号所指示 的日志的优先级范围。
4、 一种本地单板日志管理方法， 其特征在于， 包括：
检测当前系统资源的过载级别；
判断单板上的日志的优先级是否在所述过载级别对应的日志的优先级 的范围内；
根据判断结果， 对所述单板上的日志进行流控。
5、 如权利要求 4所述的方法， 其特征在于， 所述流控具体包括： 在判断为是时， 不发送所述单板上的曰志；
在判断为否时， 发送所述单板上的曰志。
6、 一种本地单板日志管理方法， 其特征在于， 包括：
检测当前系统资源的过载级别；
判断单板上的日志的优先级是否在所述过载级别对应的日志的优先级 的范围内； 在判断为否时， 根据接收的主控板的反压信号， 判断所述单板上的曰 志的优先级是否在所述反压信号指示的日志的优先级的范围内，
如果所述单板上的日志的优先级不在所述反压信号指示的日志的优先 级的范围内， 则发送所述单板上的日志给主控板。
7、 一种主控板， 其特征在于， 所述主控板包括：
主控检测模块， 用于检测主控板当前的过载级别；
主控判断模块， 用于判断主控板上的日志的优先级是否在用户预置的 所述主控板的当前过载级别对应的日志的优先级范围内；
主控执行模块， 用于在主控判断模块判断为是时， 丟弃所述曰志。
8、 如权利要求 7所述的主控板， 其特征在于， 所述主控板还包括： 反压信号模块， 用于根据主控板当前过载级别， 生成与主控板当前过 载级别对应的反压信号， 发送所述反压信号给本地单板， 所述反压信号指 示主控板拒绝接收的日志的优先级范围。
9、 如权利要求 8所述的主控板， 其特征在于， 所述主控板还包括： 主控预置模块， 用于根据用户预置的主控板各个过载门限， 设置各个 过载级别对应的日志优先级的范围， 和各个过载级别对应的反压信号指示 的拒绝接收的日志的优先级的范围。
10、 一种本地单板， 其特征在于， 包括：
单板检测模块， 用于判断系统资源是否过载，
单板执行模块， 用于在所述单板检测模块判断系统资源没有过载时， 根据主控板的反压信号， 发送优先级不在反压信号指示的拒绝接收的日志 优先级范围内的日志给主控板。
11、 如权利要求 10所述的本地单板， 其特征在于， 所述单板检测模块 包括：
过载检测单元， 用于在所述单板检测模块判断系统资源过载时， 检测 当前系统资源的过载级别；
过载判断单元， 用于判断单板上的日志的优先级是否在所述过载级别 对应的日志的优先级的范围内；
所述单板执行模块还用于在所述过载判断单元判断为否时， 发送所述 曰志。
12、 一种日志管理系统， 其特征在于， 包括：
主控板， 用于检测主控板当前的过载级别； 判断主控板上的日志的优 先级是否在所述主控板的当前过载级别对应的日志的优先级的范围内； 在 判断为是时， 丟弃所述日志；
本地单板， 用于判断系统资源是否过载， 在判断为否时， 发送日志给 所述主控板。
13、 如权利要求 12所述的日志管理系统， 其特征在于， 所述主控板还 用于发送与所述当前过载级别对应的反压信号给所述本地单板；
所述本地单板还用于根据主控板的反压信号， 发送优先级不在所述反 压信号指示的拒绝接收的日志的优先级范围内的日志给主控板。
14、 如权利要求 13所述的日志管理系统， 其特征在于， 所述本地单板 还用于检测当前系统资源的过载级别； 判断所述本地单板上的日志的优先 级是否在所述过载级别对应的日志的优先级的范围内； 在判断为否时， 发 送所述日志。
15. 一种日志管理方法， 其特征在于， 包括：
检测主控板过载级别， 根据所述过载级别丟弃日志， 所述日志落在可 以丟弃的日志范围之内， 所述可以丟弃的日志范围与所述过载级别对应； 根据所述过载级别， 发送与所述过载级别对应的反压信号给本地单板， 所述反压信号指示本地单板不要发送的日志的优先级范围。
16. 一种日志管理方法， 其特征在于， 包括：
检测系统资源是否过载；
如果检测结果为否， 接收主控板发送的反压信号， 所述反压信号指示 本地单板不要发送的日志的优先级范围；
根据所述反压信号向主控板发送日志。
17. 一种主控板， 其特征在于， 包括：
一装置， 用于检测主控板过载级别， 根据所述过载级别丟弃日志， 所 述日志落在可以丟弃的日志范围之内， 所述可以丟弃的日志范围与所述过 载级别对应； 和 一装置， 用于根据所述过载级别， 发送与所述过载级别对应的反压信 号给本地单板， 所述反压信号指示本地单板不要发送的日志的优先级范围。
18. 一种单板， 其特征在于， 包括：
一装置， 用于检测系统资源是否过载；
一装置， 用于如果检测结果为否， 接收主控板发送的反压信号， 所述 反压信号指示本地单板不要发送的日志的优先级范围； 和
一装置， 用于根据所述反压信号向主控板发送日志。
19. 一种日志管理系统，包括如权利要求 17所述的主控板和如权利要求
18所述的单板。
PCT/CN2011/072484 2010-04-19 2011-04-07 日志管理方法、系统、主控板和本地单板 WO2011131087A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN 201010153026 CN101859270A (zh) 2010-04-19 2010-04-19 日志管理方法、系统、主控板和本地单板
CN201010153026.1 2010-04-19

Publications (1)

Publication Number Publication Date
WO2011131087A1 true WO2011131087A1 (zh) 2011-10-27

Family

ID=42945189

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/072484 WO2011131087A1 (zh) 2010-04-19 2011-04-07 日志管理方法、系统、主控板和本地单板

Country Status (2)

Country Link
CN (1) CN101859270A (zh)
WO (1) WO2011131087A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101859270A (zh) * 2010-04-19 2010-10-13 上海华为技术有限公司 日志管理方法、系统、主控板和本地单板
CN102185710A (zh) * 2011-04-26 2011-09-14 中兴通讯股份有限公司 一种单板日志的管理方法及日志管理系统
CN102385632A (zh) * 2011-12-02 2012-03-21 苏州阔地网络科技有限公司 一种日志自动分类通知方法及系统
CN103838659B (zh) * 2014-02-17 2017-09-01 大唐移动通信设备有限公司 一种系统日志的控制方法和装置
CN108897663B (zh) * 2018-06-19 2022-08-26 新华三技术有限公司 日志输出控制方法和装置
CN112994924B (zh) * 2019-12-18 2022-03-08 中国科学院声学研究所 一种网络业务日志在线归并方法
CN114002987A (zh) * 2021-11-03 2022-02-01 杭州和利时自动化有限公司 一种获取日志信息的方法、装置、电子设备及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030163562A1 (en) * 2002-02-26 2003-08-28 Ford Daniel E. Remote information logging and selective reflections of loggable information
CN101437015A (zh) * 2007-11-15 2009-05-20 中兴通讯股份有限公司 用于ip多媒体子系统的消息分级控制方法
CN101505245A (zh) * 2009-03-06 2009-08-12 成都市华为赛门铁克科技有限公司 一种发送日志信息的方法及装置
US20090282297A1 (en) * 2008-05-09 2009-11-12 Gary Anna Leveled Logging Data Automation for Virtual Tape Server Applications
CN101859270A (zh) * 2010-04-19 2010-10-13 上海华为技术有限公司 日志管理方法、系统、主控板和本地单板

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100464600C (zh) * 2007-02-08 2009-02-25 华为技术有限公司 告警处理方法和后台管理装置
CN101547113B (zh) * 2008-03-27 2011-10-26 中兴通讯股份有限公司 告警信息过滤系统、装置及方法
CN101515246B (zh) * 2008-12-29 2012-05-30 卡斯柯信号有限公司 Its自动列车监控系统的多级日志消息处理方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030163562A1 (en) * 2002-02-26 2003-08-28 Ford Daniel E. Remote information logging and selective reflections of loggable information
CN101437015A (zh) * 2007-11-15 2009-05-20 中兴通讯股份有限公司 用于ip多媒体子系统的消息分级控制方法
US20090282297A1 (en) * 2008-05-09 2009-11-12 Gary Anna Leveled Logging Data Automation for Virtual Tape Server Applications
CN101505245A (zh) * 2009-03-06 2009-08-12 成都市华为赛门铁克科技有限公司 一种发送日志信息的方法及装置
CN101859270A (zh) * 2010-04-19 2010-10-13 上海华为技术有限公司 日志管理方法、系统、主控板和本地单板

Also Published As

Publication number Publication date
CN101859270A (zh) 2010-10-13

Similar Documents

Publication Publication Date Title
WO2011131087A1 (zh) 日志管理方法、系统、主控板和本地单板
US10904118B2 (en) Background task execution over a network
KR101344395B1 (ko) 액세스 단말에 대한 우선순위 표시 및 큐잉을 용이하게 하기 위한 장치 및 방법
CN109067571B (zh) 电子装置及其网络配置方法、存储介质
WO2015103818A1 (zh) 无线接入点接入通信终端管理方法、装置及无线接入终端
CN107547442B (zh) 数据传输缓存队列分配方法及装置
WO2016202092A1 (zh) 基于多层队列流控反压的传送方法及装置
RU2012118521A (ru) Способ и устройство для определения шлюза, способ и система для отправки сообщения
KR101749200B1 (ko) 무선 통신 네트워크의 허용 제어를 위한 방법 및 장치
WO2016011576A1 (zh) 网络优化的方法、装置和基站
WO2014169716A1 (zh) 一种语音业务单通检测的方法及装置
WO2015168834A1 (zh) 虚拟网络功能中网络资源的分配方法、编排器及管理器
CN111565098B (zh) 一种确定harq反馈资源的方法、装置及系统
US10412006B2 (en) Bandwith sentinel
WO2011110104A1 (zh) 终端接入方法、设备及系统
KR20140119656A (ko) 데이터 전송 방법, 장치, 및 시스템
US11115857B2 (en) Bandwidth sentinel
WO2012139466A1 (zh) 一种资源的管理方法和设备
US20120083220A1 (en) Determining the quality of service in a communication terminal device
CN113709776A (zh) 一种通信方法、装置及系统
JP2016502825A (ja) アクセス制御方法及び装置
WO2018082655A1 (zh) 一种确定数据传输路径的方法、装置
JP5827719B2 (ja) 基地局装置、及び呼受付判定方法
CN114500544A (zh) 一种节点间负载均衡方法、系统、设备以及介质
JP5940171B2 (ja) ドロップ接続を判断するための方法、ネットワークノード、コンピュータプログラム、およびコンピュータプログラム製品

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

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

Country of ref document: EP

Kind code of ref document: A1