WO2021129024A1 - 识别通讯设备状态的方法、通讯系统及存储介质 - Google Patents

识别通讯设备状态的方法、通讯系统及存储介质 Download PDF

Info

Publication number
WO2021129024A1
WO2021129024A1 PCT/CN2020/118840 CN2020118840W WO2021129024A1 WO 2021129024 A1 WO2021129024 A1 WO 2021129024A1 CN 2020118840 W CN2020118840 W CN 2020118840W WO 2021129024 A1 WO2021129024 A1 WO 2021129024A1
Authority
WO
WIPO (PCT)
Prior art keywords
rule tree
rule
log file
tree table
tested
Prior art date
Application number
PCT/CN2020/118840
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 WO2021129024A1 publication Critical patent/WO2021129024A1/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/0677—Localisation of faults
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/33—Querying
    • 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/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H04L41/0636—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis based on a decision tree analysis
    • 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/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • the embodiments of the present application relate to but are not limited to the communication field, and specifically relate to but not limited to a method for identifying the state of a communication device, a communication system, and a storage medium.
  • the business data scale of the communication system has exploded with the increase of business, and its emergence The probability of failure will also increase. More uncertain factors will cause the communication service program to reset or abnormal during the operation process, which will interrupt the communication service. In severe cases, the entire communication network will be paralyzed for a long time. It brings troubles to users such as no signal, weak signal, inability to call the caller or caller, or communication equipment unable to access the Internet, and the user experience is affected.
  • the method for identifying the state of a communication device, a communication system, and a storage medium mainly solve the technical problem that the detection of the communication device requires personnel familiar with the business process and cannot quickly locate the problem.
  • an embodiment of the present application provides a method for identifying the state of a communication device, the method includes: extracting the content of a preset number of observation point information in the source code library to form a key attribute including the rule tree ID Model library list; create a rule tree table including preset specific behaviors of at least one node according to the model library list of the key attributes of the rule tree ID; store the rule tree table in the model library; when the log file to be tested matches In the above rule tree table, the information of the rule tree table matched by the log file to be tested is obtained.
  • the embodiment of the application also provides a communication system, the system includes: a generation module, an acquisition module, and an analysis module; the generation module includes an extraction module and a creation module; the extraction module is used to extract the source code library
  • the content of the preset number of observation point information forms a model library list including the preset key attributes of the rule tree ID; the creation module is used to create a model library list including at least one node according to the model library list including the key attributes of the rule tree ID Preset a rule tree table of a specific behavior; store the rule tree table in the model library; the collection module is used to collect log files to be tested; the parsing module is used to parse the log files to be tested When the log file to be tested matches the rule tree table, obtain the information of the rule tree table on which the log file matches.
  • the embodiment of the present application also provides a communication system, the system includes a processor, a memory, and a communication bus; the communication bus is used to realize the connection and communication between the processor and the memory; the processor is used to execute the storage in the memory
  • One or more computer programs to implement the steps of the above-mentioned method of identifying the state of a communication device.
  • the embodiments of the present application also provide a computer-readable storage medium, wherein the computer-readable storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors , In order to realize the steps of the above-mentioned method of identifying the state of the communication device.
  • FIG. 1 is a basic flowchart of a method for identifying the state of a communication device according to Embodiment 1 of this application;
  • FIG. 3 is a detailed flowchart of the method for identifying the state of a communication device according to the third embodiment of this application;
  • FIG. 5 is a schematic structural diagram of a communication system according to Embodiment 5 of this application.
  • this application provides a method for identifying the state of the communication equipment.
  • the method proposed in this application will be described below in conjunction with embodiments.
  • FIG. 1 is a basic flowchart of a method for identifying the state of a communication device according to Embodiment 1 of the present application. The method includes the following steps.
  • the application scenario is not limited to the time and place where the base station is abnormal, whether it is real-time log information or historical log information several months ago; it can be used in both the laboratory and the field.
  • the preset interface is a preset number of observation points inserted by the programmer when compiling the business code.
  • the preset interface includes, but is not limited to, behavior characteristic output methods, keywords used to mark behavior characteristic attributes, and so on. Scan the source code in the source code library, and use regular expressions to filter out all the observation point information according to the filter conditions including at least the four elements of module name, time, level and content.
  • the content of the observation point information includes the time sequence and path of the business code running, and the preset information in the running of the business code.
  • the preset information is the key information. The preset information can be set or judged by the programmer in advance as the key information.
  • the source code library may include all the source code of the business code running or the new source code of the business code running that is updated at a preset time; in this embodiment, the content of the preset number of observation point information in the source code library is extracted
  • the latter may also include: correcting duplicate information and/or error information of the observation point information. This step can correct the execution of the code and improve the correctness of the code.
  • S102 Create a rule tree table including at least one node's preset specific behavior according to the model library list of the key attributes of the rule tree ID.
  • other key attributes in the list of the model library may also include at least one of the following: rule tree detection type, rule tree name, rule tree time type, and rule tree description.
  • the rule tree detection type includes the first rule tree detection type and the second rule tree detection type.
  • the first rule tree detection type is also the normal detection type: using nested rule references, starting from the matching item with a timeout period of 0, meeting all the matching items is considered normal, and the matching item and the matching item are used more Two nested rules refer to (options) to connect, and each option contains a branch connecting the matching item and the matching item. As long as one of the branches is satisfied, the previous match can be moved from the previous match to the next match.
  • the LOG information is considered to be a match, but this match is a weak match.
  • the format string and rule parameters of the log file to be tested are the same as the format string and rule parameters of the model library, it is a strong match. If it is a strong match, you can continue to match the next matching item, otherwise the search will time out. If the detection time of the matching item is exceeded, the detection result means failure; if the detection time of the matching item is not exceeded, but multiple options If the branch is not detected, the detection result means incomplete.
  • the second rule tree detection type is also an abnormal detection type, which means that all regulatory matching items are satisfied as a failure. Once any other matching items are not satisfied, it will be ignored and will not be recorded in the model library. If you do not know whether it is faulty or not, you can use the first rule tree detection type to detect it. When the first rule tree detection type detects a fault, use the second rule tree detection type to detect the specific location of the fault. Directly use the second rule tree detection type to detect the faulty log file to see where the specific fault is.
  • the number of rule tree tables that preset specific behaviors corresponds to extracting the preset number of observation point information in the source code library.
  • the preset rule field of the node of the rule tree table includes a format string and a rule parameter. These two fields, wherein the format string refers to the preset information and path of the content of the observation point information, and the rule parameter refers to the observation point.
  • the time sequence of the content of the point information; the preset information is the key information.
  • the timing value of the rule parameter item can be composed of a union or an OR relationship.
  • the formatted string refers to the content of the observation point information, and the content of the observation point information is quoted as a rule match item according to the logical sequence of code execution.
  • the preset rule field of the node of the rule tree table may further include: a rule matching type, and the rule matching type may include a first matching type and a second matching type.
  • the tree table of the second matching type may also include a rule reference field, and the rule reference field is filled with other rule tree IDs that need to be associated.
  • the rule tree table of the first matching type there may be no rule reference fields, or there may be rule reference fields but the content in the rule reference fields is empty.
  • Each rule tree table in this embodiment also includes an ultra-long duration field, where the ultra-long duration is 0-preset time (n), where a timeout duration of 0 represents the 0th standard matching item [0], It is the beginning of the matching item.
  • n which means that the matching item [n] has an ultra-long duration relative to the matching item [0], that is, if the log file to be tested detects the matching item [n], if the log file to be tested is n seconds If it occurs within, it will proceed to the next match or the end of the match, otherwise the detection result will fail to match.
  • the developer sorts out whether the code with the rule tree table is valid.
  • the source code may include all the source code that the business code runs or the new source code that is updated at the preset time when the business code runs; when the source code library is the updated new source code, the rule tree table is stored in
  • the model library also includes: updating the preset model library to form a new model library according to the model library of multiple tree tables with the preset characteristic behaviors, wherein the preset model library represents an old version of the model library.
  • the log file to be tested may be running data or historical data.
  • the log file to be tested matching the rule tree table includes: collecting business log files to be tested. After reading a line of LOG, it will traverse all the matching items in the model library rule tree table that have a timeout period of 0. When the log file to be tested matches When any one of the matching items with a timeout period of 0 in the above model library, look at whether the format string and rule parameters of the test log file can match the rule tree table with this timeout period of 0 matching items, and when it matches, get The log file to be tested matches the information of the rule tree table.
  • the log file to be tested includes several fields of the definition node of the rule tree table in the model library: timeout duration, format string, rule parameters, etc., enter the first rule tree detection type, and match a long duration as
  • the match item is 0
  • the rule parameter of the business of the log file to be tested (that is, the time when the business occurs) is 20ms of the entire business behavior in the log to be tested, and the rule parameter of the log file to be tested is matched with the rule parameter in the rule tree table.
  • the preset 10ms-40ms in the rule parameter field and then match the format string of 10ms-40ms in the rule tree table.
  • the format string of the business behavior that occurs in 20ms is divided into multiple timeout format strings from the corresponding root node to match the rule tree table in the model library, and the format string from the rule tree table The matching of the corresponding timeout duration match.
  • the rule parameter of the business of the log file to be tested (that is, the time when the business occurred) is the occurrence of the test 5ms of the entire business behavior in the log, match the rule parameter of the log file to be tested with the preset 5ms in the rule parameter field in the rule tree table, and then match the 5ms format string in the rule tree table to obtain the log file to be tested
  • the information of the matched rule tree table does not limit the value of the rule parameter in the rule tree table.
  • the value of the rule parameter in the rule tree table can be set as required, and the value can be composed of a union or an OR relationship.
  • the method for identifying the state of a communication device extracts the content of a preset number of observation point information in the source code library to form a model library list including the key attributes of the rule tree ID, and then calculates according to the rule tree ID
  • the model library list of key attributes creates a rule tree table that includes at least one node with preset specific behaviors; stores the rule tree table in the model library, and when the log file to be tested matches the rule tree table, the log file to be tested is matched
  • the information of the rule tree table It realizes the rapid identification of the state of the communication equipment and the location of the fault state of the communication equipment.
  • the method for identifying the state of the communication device of the present application realizes the rapid identification of the state of the communication device and locates the position of the normal state or the fault state of the communication device.
  • This application scenario is to detect the 5G Docker container log of the wireless base station under 5GNR.
  • Fig. 2 is a detailed flowchart of the method provided in the second embodiment of the application. The method includes the following steps.
  • S201 Scan the observation point information in the source code library under the preset interface.
  • the source code library is all the source code of the business code, including the old source code and the updated source code.
  • the preset interface is a preset number of observation points inserted by the programmer when compiling the business code, and the preset interface includes, but is not limited to, behavior characteristic output methods, keywords used to mark behavior characteristic attributes, and so on. Scan the source code in the source code library, and use regular expressions to filter out all the observation point information according to the filter conditions including at least the four elements of module name, time, level and content.
  • S202 Extract the content of the preset number of observation point information in the source code library, and form a list of model libraries including the preset number of rule tree IDs, the first rule tree detection type, and the second rule tree detection type.
  • the content of the preset number of observation point information includes the time sequence and path of the business code running, and the preset information in the running of the business code.
  • the preset information is the key information, which can be set or set by the programmer in advance. It is determined that the preset information is key information.
  • the first rule tree detection type is: using nested rule references, starting from the matching item with a timeout period of 0, meeting all the matching items is considered normal, and the matching item and the matching item are more frequently used.
  • Two nested rules refer to (option) to connect, and each option contains a branch that connects the match item to the match item. As long as the other branch is satisfied, the previous match item can be moved from the previous match item to the next match item. Once it does not meet any of the other matching items, it will be recorded in the model library. If the detection time of the matching item is exceeded, the detection result is the meaning of failure; if the detection time of the matching item is not exceeded, but the branch in multiple options is not If it is detected, the result of the detection means unfinished.
  • the second rule tree detection type is that all regulatory matching items are satisfied as a failure. Once any other matching items are not satisfied, it will be ignored and will not be recorded in the model library.
  • S203 Correct the repeated information and/or error information of the observation point information.
  • S204 Create a rule tree table including a predetermined specific behavior of at least one node according to the model library list of the key attributes of the rule tree ID.
  • the key attributes of the model library list include the rule tree ID, the first rule detection type, and the second rule detection type.
  • the preset rule fields of the nodes of the rule tree table include timeout duration, formatted string, rule parameter, first rule matching type, and second rule matching type.
  • the super long duration is 0-the preset time, where the timeout duration is 0, which means the 0th standard match item [0], which is the beginning of the match item.
  • the root node in the rule tree table can only satisfy this unique rule Only when the matching item is [0], the detection of the log file to be tested is started.
  • the formatted character string refers to the preset information and path of the content of the observation point information, and the rule parameter refers to the time sequence of the content of the observation point information; the preset information is key point information.
  • the timing value of the rule parameter item can be composed of a union or an OR relationship.
  • the format string refers to the content of the observation point information, and these key points are referenced as rule matching items according to the logical sequence of code execution.
  • the tree table of the second matching type may also include a rule reference field, and the rule reference field is filled with a rule tree table of other rule tree IDs that need to be associated. For the rule tree table of the first matching type, there may be no rule reference fields, or there may be rule reference fields but the content in the rule reference fields is empty.
  • the developer sorts out whether the code with the rule tree table is valid.
  • the log file to be tested matches a rule tree table in the model library with a timeout period of 0 matches, and it is detected whether the first rule tree detection type can be used to match the formatted string and rule parameters in the rule tree table. .
  • the first rule tree detection type is: using nested rule references, starting from the root node of the tree of matching items with a timeout period of 0, satisfying all matching items is considered normal, and matching items and matching items
  • the items are connected by multiple nested rule references (options), and each option contains a branch that connects the matched item and the matched item. As long as the other branch is satisfied, it can go from the previous match to the next. A match. Once it does not meet any of the other matching items, it will be recorded in the model library. If the detection time of the matching item is exceeded, the detection result is the meaning of failure; if the detection time of the matching item is not exceeded, but the branch in multiple options is not If it is detected, the result of the detection means unfinished.
  • the log file to be tested is the code data of the running 5G base station.
  • the first rule tree detection type matches the format in the rule tree table. For string and rule parameters, execute S210; otherwise, execute 207.
  • S207 Detect whether the formatted character string and the rule parameter in the rule tree table can be matched according to the second rule tree detection type.
  • S209 Export information that the log file to be tested does not match the rule tree table of the first rule tree detection type and/or the second rule tree detection type.
  • the method for identifying the state of a communication device scans the observation point information of the preset interface in the source code library under the preset interface, and extracts the content of the preset number of observation point information in the source code library to form A list of model libraries including a preset number of rule tree IDs, first rule tree detection types, and second rule tree detection types. Correct the duplicate information and/or wrong information of the observation point information. Then, according to the model library list of the key attributes of the rule tree ID, a rule tree table including several specific behaviors of at least one node is created, and the several rule tree tables are stored in the model library.
  • the first rule tree detection type can be used to match the format string in the rule tree table corresponding to the root node when the log file to be tested matches the match item of the root node whose timeout period is 0 in the previous rule tree table And rule parameters, when matched, it is normal.
  • the second rule tree detection type is used to match the format string and rule parameters in the rule tree table, and the second rule tree detection type is matched.
  • the exported log file does not match the information of the rule tree table of the first rule tree detection type and/or the second rule tree detection type.
  • This positioning tool can save 75%-85% of the time for locating faults for field technicians, making it easier for technicians to solve faults more quickly and quickly, shortening the delay of faults, greatly improving the efficiency of locating faults, and providing long-term efficiency for 5GNR base stations.
  • the reliable and stable operation of the ground provides a strong guarantee, which saves the cost of maintaining the human resources of the enterprise.
  • the source code can be checked twice, whether there are errors or duplications in the code of the tree table, etc.
  • the instant messaging system information storage method of the present application is implemented.
  • the method of the present application will be described below in conjunction with an application scenario.
  • This application scenario is to detect log files of historical failures of the communication system.
  • FIG. 3 is a detailed flowchart of the method provided in Embodiment 3 of the application, and the method includes the following steps.
  • S301 Scan the observation point information in the source code library under the preset interface.
  • the source code library is a new source code that is updated at a preset time when the business code runs.
  • the preset interface is a preset number of observation points inserted by the programmer when compiling the business code, and the preset interface includes, but is not limited to, behavior characteristic output methods, keywords used to mark behavior characteristic attributes, and so on. Scan the source code in the source code library, and use regular expressions to filter out all the observation point information according to the filter conditions including at least the four elements of module name, time, level and content.
  • the content of the observation point information in this embodiment includes the time sequence and path of the service code running, and the preset information in the running of the service code.
  • the preset information is the key information, which can be set or judged by the programmer in advance.
  • Information is the key information.
  • the second rule tree detection type in this embodiment is that all regulatory matching items are satisfied as a fault. Once any other matching items are not satisfied, it will be ignored and will not be recorded in the model library.
  • S303 Create a rule tree table including at least one node of preset specific behaviors according to the model library list of the key attributes of the rule tree ID.
  • the preset rule fields of each node of the rule tree table include several fields of timeout duration, formatted string, rule parameter, first rule matching type, and second rule matching type.
  • the ultra-long duration is 0-the preset time, where the timeout duration is 0, which means the 0th standard match item [0], which is the start of the match item and the root node of the rule tree table, and only the only rule match is satisfied Item [0], it starts to detect the log file to be tested.
  • the formatted character string refers to the preset information and path of the content of the observation point information
  • the rule parameter refers to the time sequence of the content of the observation point information; the preset information is key point information.
  • the timing value of the rule parameter item can be composed of a union or an OR relationship.
  • the format string refers to the content of the observation point information, and these key points are referenced as rule matching items according to the logical sequence of code execution.
  • the tree table of the second matching type may also include a rule reference field, and the rule reference field is filled with a rule tree table of other rule tree IDs that need to be associated.
  • the rule tree table of the first matching type there may be no rule reference fields, or there may be rule reference fields but the content in the rule reference fields is empty.
  • the log file to be tested matches a rule tree table in the model library with a timeout period of 0, and the second rule tree detection type is used to match the formatted string and rule parameters in the rule tree table, and the to-be-tested log file is exported.
  • the log file matches the information in the rule tree table.
  • the method for identifying the state of a communication device scans the observation point information in the source code library under a preset interface, extracts the content of the observation point information in the source code library, and forms the key attribute including the rule tree ID
  • the model library list is used to create a rule tree table including the preset specific behavior of at least one node according to the model library list of the key attribute of the rule tree ID; the rule tree table is stored in the model library, and the old model library is updated according to the model library.
  • the log file to be tested matches a rule tree table in the model library whose timeout period is 0.
  • Use the second rule tree detection type to match the format string and rule parameters in the rule tree table to export the test
  • the log file matches the information in the rule tree table.
  • the old model library is updated, regardless of the code error of the communication equipment or other reasons, it can quickly locate the position of the communication equipment failure state, and improve the speed and efficiency of the base station failure or abnormal location. It avoids the long-term strike of the base station and affects the user experience, and ensures the rapid recovery and stable operation of the entire communication system in case of failure.
  • this application provides a communication system.
  • the communication system proposed by this application will be described below in conjunction with embodiments.
  • FIG. 4 is a schematic diagram of the composition of the communication system provided in the fourth embodiment of the application.
  • the communication system includes: a generation module 401, an acquisition module 402, and an analysis module 403; wherein the generation module 401 includes an extraction module 4011 and a creation module 4012 .
  • the extraction module 4011 is used to extract the content of the preset number of observation point information in the source code library to form a model library list including the preset key attributes of the rule tree ID; the content of the observation point information includes the pre-determined operation of the business code Set information, timing and path; among them, preset information is the key information point.
  • the creation module 4012 is used to create a rule tree table including at least one node with preset specific behaviors according to the model library list including the key attributes of the rule tree ID.
  • the rule tree table includes format strings and rule parameters, and format string references Preset information and paths, and rule parameters refer to time sequence; store the rule tree table of preset specific behaviors in the model library.
  • the collection module 402 is used to collect log files to be tested.
  • the parsing module 403 is used to parse the log file to be tested, and when the log file to be tested matches the rule tree table, obtain the information of the rule tree table matched by the log file.
  • the model library list further includes the rule tree detection type; the creation module is also used to match the log file to be tested on the rule tree table according to the rule detection type.
  • the collection module 402 is also used to collect observation point information in the source code library.
  • the observation point information includes the module name, time, level, and the content.
  • the rule tree table includes: a rule matching type, the rule matching type includes a first matching type and a second matching type, and the rule tree table of the first matching type has no rule references or rule references, but there is no content in the rule references,
  • the second type of rule tree table has a rule reference field, and the rule reference field includes other rule tree IDs that need to be associated.
  • the rule reference field of the first type has no content, and the rule reference field of the second type includes other rule tree IDs that need to be associated.
  • the rule tree table includes: fields with a long duration; the parsing module includes a matching module and a rule checking module.
  • the matching module is used to use the log file to be tested to match the root node of the rule tree table with a timeout period of 0, that is, the matching item [ 0];
  • the rule checking module is used to check that the format string and rule parameters of the log file to be tested can match the content of other matching items and other matching items in the rule tree table and the contents of other nodes except the root node to obtain the log to be tested
  • the information of the rule tree table on the file match.
  • the matching module has the 0th matching item among all the rule matching items of all the tree tables in the model library, that is, the root node of all the tree tables.
  • the content of the observation point information in the source code library is extracted through the extraction module to form a model library list including the preset key attributes of the rule tree ID, and then the creation module is based on the key attributes including the rule tree ID.
  • the model library list creates a rule tree table that includes at least one node’s preset specific behavior; stores the rule tree table in the model library; the collection module collects the log file to be tested, the parsing module parses the log file to be tested, and when the log file to be tested When the file matches the rule tree table, the information of the rule tree table matched by the log file to be tested is obtained. It realizes the rapid identification of the state of the communication equipment and the location of the fault state of the communication equipment.
  • This embodiment provides a communication system, as shown in FIG. 5, which includes a processor 51, a memory 52, and a communication bus 53, wherein: the communication bus 53 is used to implement connection and communication between the processor 51 and the memory 52; processing The device 51 is configured to execute one or more computer programs stored in the memory 52 to implement at least one step in the method for identifying the state of a communication device in any one of the first to third embodiments.
  • This embodiment also provides a computer-readable storage medium, which is included in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data). Volatile or non-volatile, removable or non-removable media.
  • Computer readable storage media include but are not limited to RAM (Random Access Memory), ROM (Read-Only Memory, read-only memory), EEPROM (Electrically Erasable Programmable read only memory, charged Erasable Programmable Read-Only Memory) ), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, Or any other medium that can be used to store desired information and that can be accessed by a computer.
  • the computer-readable storage medium in this embodiment can be used to store one or more computer programs, and the stored one or more computer programs can be executed by a processor to realize the identification communication in any one of the first to third embodiments. At least one step in the method of device status.
  • a model library list including the key attributes of the rule tree ID is formed; then according to the model library list of the key attributes of the rule tree ID, a preset specific model including at least one node is created.
  • the rule tree table of the behavior; the rule tree table is stored in the model library, and finally when the log file to be tested matches the rule tree table, the information of the rule tree table matched by the log file to be tested is obtained.
  • technical effects including but not limited to quickly identifying the state of the communication device and locating the location of the communication device's fault state can be achieved.
  • the beneficial effects of this application are: according to the method for identifying the state of the communication device, the communication system, and the storage medium provided by the embodiments of the application, the content of the observation point information in the source code library is extracted to form a model including the key attributes of the rule tree ID Database list, create a rule tree table including at least one node’s preset specific behavior based on the model library list of the key attributes of the rule tree ID, store the rule tree table in the model library, and finally when the log file to be tested matches the rule tree In the table, obtain the information of the rule tree table matched by the log file to be tested.
  • technical effects including but not limited to quickly identifying the state of the communication device and locating the position of the normal state or fault state of the communication device can be achieved.
  • communication media usually contain computer-readable instructions, data structures, computer program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery medium. Therefore, this application is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Computational Linguistics (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Debugging And Monitoring (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供一种识别通讯设备状态的方法、通讯系统及存储介质，通过提取出源码库中的预设数量的观测点信息的内容，形成包括规则树ID的关键属性的模型库列表，然后根据规则树ID的关键属性的模型库列表创建包括至少一节点的预设特定行为的规则树表；将规则树表存储在模型库中，当待测日志文件匹配上规则树表时，获取待测日志文件匹配上的规则树表的信息。

Description

识别通讯设备状态的方法、通讯系统及存储介质
相关申请的交叉引用
本申请要求享有2019年12月24日提交的名称为“识别通讯设备状态的方法、通讯系统及存储介质”的中国专利申请CN201911341778.8的优先权，其全部内容通过引用并入本文中。
技术领域
本申请实施例涉及但不限于通信领域，具体而言，涉及但不限于一种识别通讯设备状态的方法、通讯系统及存储介质。
背景技术
随着通讯设备集成度越来越高，功能越来越复杂，业务模型更加多样化，然而在实际通讯系统应用过程中，通讯系统的业务数据规模随着业务的增多呈爆发式增长，其出现故障的概率也会随之增多，更多不确定的因素会导致通讯业务程序在运行过程中出现复位或者异常的现象，从而使通讯业务受到中断，严重时会导致整个通讯网络长时间瘫痪，会给用户带来如无信号、信号弱、无法主被叫或通讯设备无法上网等问题的困扰，用户体验受到影响。
相关技术中针对该问题有利用串口打印、调试函数或单步跟踪的方法进行设备维护和故障检测及定位，这种方式严重依赖熟悉业务流程的技术人员，工作量大且无法远程定位。
发明内容
本申请的实施例提供的识别通讯设备状态的方法、通讯系统及存储介质，主要解决的技术问题是检测通讯设备需要依赖熟悉业务流程的人员，无法快速定位的问题。
为解决上述技术问题，本申请实施例提供一种识别通讯设备状态的方法，所述方法包括：提取出源码库中的预设数量的观测点信息的内容，形成包括规则树ID的关键属性的模型库列表；根据规则树ID的关键属性的模型库列表创建包括至少一个节点的预设特定行为的规则树表；将所述规则树表存储在所述模型库中；当待测日志文件匹配上所述规则树表时，获取所述待测日志文件匹配上的所述规则树表的信息。
本申请的实施例还提供一种通讯系统，所述系统包括：生成模块、采集模块及解析模块；所述生成模块包括提取模块和创建模块；所述提取模块，用于提取出源码库中的预设 数量的观测点信息的内容，形成包括规则树ID的预设关键属性的模型库列表；所述创建模块，用于根据包括规则树ID的关键属性的模型库列表创建包括至少一个节点的预设特定行为的规则树表；将所述规则树表存储在所述模型库中；所述采集模块，用于采集待测日志文件；所述解析模块，用于解析所述待测日志文件，当待测日志文件匹配上所述规则树表时，获取所述日志文件匹配上的所述规则树表的信息。
本申请的实施例还提供一种通讯系统，所述系统包括处理器、存储器及通信总线；所述通信总线用于实现处理器和存储器之间的连接通信；所述处理器用于执行存储器中存储的一个或者多个计算机程序，以实现上述的识别通讯设备状态方法的步骤。
本申请的实施例还提供一种计算机可读存储介质，其中，所述计算机可读存储介质存储有一个或者多个计算机程序，所述一个或者多个计算机程序可被一个或者多个处理器执行，以实现上述的识别通讯设备状态方法的步骤。
本申请其他特征和相应的有益效果在说明书的后面部分进行阐述说明，且应当理解，至少部分有益效果从本申请说明书中的记载变的显而易见。
附图说明
图1为本申请实施例一的识别通讯设备状态的方法的基本流程图；
图2为本申请实施例二的识别通讯设备状态的方法的细化流程图；
图3为本申请实施例三的识别通讯设备状态的方法的细化流程图；
图4为本申请实施例四的通讯系统的组成示意图；
图5为本申请实施例五的通讯系统的结构示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，下面通过具体实施方式结合附图对本申请实施例作进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
实施例一
为了解决的检测通讯设备需要依赖熟悉业务流程的人员，无法快速定位的问题，本申请提供一种识别通讯设备状态的方法，下面结合实施例对本申请提出的方法进行说明。
请参见图1，图1为本申请实施例一提供的识别通讯设备状态的方法的基本流程图，该方法包括以下步骤。
S101、提取出源码库中的预设数量的观测点信息的内容，形成包括规则树ID的关键属性的模型库列表。
在本实施例中，应用场景不限于基站出异常的时间和地点，无论是实时的日志信息，还是好几个月前的历史日志信息；无论是实验室还是外场都可以使用。
在本实施例中，提取出源码库中的预设数量的观测点信息的内容之前还可以包括：扫描预设接口下的源码库中的观测点信息，其中扫描的观测点信息预设接口的观测点信息。其中预设接口是程序员在编制业务代码时插入的预设数量的观察点，其中预设接口包括但不限于与行为特征输出方式、用于标示行为特征属性的关键字等。扫描源码库中的源码，利用正则表达式根据过滤条件至少包括模块名、时间、级别及内容这四个要素，过滤出所有观测点信息。其中观测点信息的内容包括业务代码运行的时序和路径，业务代码运行中的预设信息，其中预设信息为关键信息，可根据程序员提前自行设定或判断该预设信息为关键信息。
其中，源码库可以包括业务代码运行的所有源码或业务代码运行的在预设时间进行更新的新的源码；在本实施例中，在提取出源码库中的预设数量的观测点信息的内容后还可以包括：修正观测点信息的重复信息和/或错误信息。该步骤可以对代码的执行修正，提高代码的正确性。
S102、根据规则树ID的关键属性的模型库列表创建包括至少一个节点的预设特定行为的规则树表。
在本实施例中，模型库的列表中的其他关键属性还可以包括以下至少一种：规则树检测类型、规则树名称、规则树时间类型及规则树描述。其中规则树检测类型包括第一规则树检测类型和第二规则树检测类型。其中第一规则树检测类型亦为正常的检测类型：采用嵌套的规则引用，先从超时时长为0的匹配项开始，满足所有的匹配项就算正常，而匹配项与匹配项之间用多个嵌套的规则引用(option)来连接，其中每个option里面都嵌套有匹配项与匹配项之间连接的分支，只要满足其中一个分支即可从前一个匹配项到后一个匹配项。一旦不满足其中任何一个匹配项就会记录在模型库中，考虑到匹配过程是顺序查找的，所以需在时间范围内，都认为这些LOG信息是匹配的，但是这个匹配是一个弱匹配。当遇到待测日志文件的格式化字符串和规则参数与模型库的格式化字符串和规则参数相同的话，就是一个强匹配。若为强匹配，就可以继续匹配下一个匹配项，否则查找超时，若超过匹配项的检测时长，则检测结果为表示故障的含义；若未超过匹配项的检测时长，但多个option中的分支没检测到，则检测结果为表示未完的含义。其中第二规则树检测类型亦为异常的检测类型，是所有的规制匹配项都满足算故障，一旦不满足其他任何一个匹配项， 则会被忽略，不会记录在模型库中，在检测健康程度或不知道是否故障时，可以先用第一规则树检测类型来检测，用第一规则树检测类型检测出有故障时，再用第二规则树检测类型进行检测看故障具体位置，也可以在针对有故障的日志文件直接利用第二规则树检测类型进行检测，看具体故障位置在何处。
在本实施例中，预设特定行为的规则树表的数量对应提取出源码库中的预设数量的观测点信息。其中规则树表节点的预设规则字段包括格式化字符串和规则参数，这两个字段，其中所述格式化字符串引用观测点信息的内容的预设信息和路径，所述规则参数引用观测点信息的内容的时序；该预设信息为关键信息。规则参数项的时序值可以由并、或的关系组成。格式化字符串引用观测点信息的内容，按照代码运行的逻辑顺序引用观测点信息的内容作为规则匹配项。其中，规则树表节点的预设规则字段还可以包括：规则匹配类型，而规则匹配类型可以包括第一匹配类型和第二匹配类型。其中第二匹配类型的树表还可以包括规则引用字段，该规则引用字段填写着需要关联的其他规则树ID。对于第一匹配类型的规则树表可以无规则引用字段，也可以有规则引用字段但规则引用字段里面的内容为空。在本实施例中的各规则树表中还包括超长时长的字段，其中超长时长为0-预设的时间(n)，其中超时时长为0表示第0条标准匹配项[0],即是匹配项的开始，只有满足这个唯一的规则匹配项[0]，才开始对待测日志文件进行检测。而后面的超出时长为n表示匹配项[n]相对于匹配项[0]发生的超长时长，即若待测日志文件在检测到匹配项[n]时，若待测日志文件再n秒内发生，则进行到下一个匹配项或匹配结束，否则检测结果匹配失败。
S103、将规则树表存储在模型库中。
在本实施例中，在讲规则树表存储前还可以包括：由开发人员梳理带规则树表的代码是否有效。
而在本实施例中的源代码可以包括业务代码运行的所有源码或业务代码运行的在预设时间进行更新的新的源码；当源码库为更新的新的源码时，将规则树表存储在模型库中还包括：根据有这预设特征行为的多个树表的模型库对预设模型库进行更新形成新的模型库，其中预设模型库代表旧的版本的模型库。
S104、当待测日志文件匹配上模型库中规则树表时，获取待测日志文件匹配上的该规则树表的信息。
在本实施例中，待测日志文件可以为正运行的数据也可以为历史的数据。待测日志文件匹配上规则树表包括：采集业务的待测日志文件，读取一行LOG后，会遍历模型库规则树表中的所有的超时时长为0的匹配项，当待测日志文件匹配上模型库中的任意一个超时时长为0的匹配项时，看待测日志文件的格式字符串和规则参数是否能匹配到有这个超时 时长为0的匹配项的规则树表，匹配时，则获取待测日志文件匹配上的规则树表的信息。比如：待测日志文件中包括模型库中规则树表的定义节点的几个字段：超时时长、格式化字符串、规则参数等，进入到第一规则树检测类型，匹配到一个超长时长为0的匹配项时，待测日志文件的业务的规则参数(即业务发生的时间)是发生于待测日志中整个业务行为的20ms，匹配上待测日志文件的规则参数与规则树表中的规则参数字段中预设的10ms-40ms，然后匹配规则树表中10ms-40ms的格式化字符串，当匹配上时，获取待测日志文件匹配上的该规则树表的信息，其中匹配的过程是在20ms发生的业务行为的格式化字符串分为多个超时时长的格式化字符串从对应根节点匹配上这个模型库中的规则树表，在从规则树表里面的格式化字符串的对应的超时时长匹配项的匹配。又比如：待测日志文件进入到第二规则树检测类型，匹配到一个超长时长为0的匹配项时，待测日志文件的业务的规则参数(即业务发生的时间)是发生于待测日志中整个业务行为的5ms，匹配上待测日志文件的规则参数与规则树表中的规则参数字段中预设的5ms，然后匹配规则树表中5ms的格式化字符串，获取待测日志文件匹配上的该规则树表的信息。上述举例并非限定规则树表中规则参数的值，规则树表的规则参数的值可以根据需要进行设定，值可以由并、或的关系组成。
本申请的实施例提供的识别通讯设备状态的方法，通过提取出源码库中的预设数量的观测点信息的内容，形成包括规则树ID的关键属性的模型库列表，然后根据规则树ID的关键属性的模型库列表创建包括至少一节点的预设特定行为的规则树表；将规则树表存储在模型库中，当待测日志文件匹配上规则树表时，获取待测日志文件匹配上的规则树表的信息。实现了快速识别到通讯设备的状态，定位到通讯设备故障状态的位置。
实施例二
本申请的识别通讯设备状态的方法实现了快速识别到通讯设备的状态，定位到通讯设备正常状态或故障状态的位置，为了便于理解，下面结合一种应用场景对本申请的方法进行说明。该应用场景是对5GNR下的无线基站5G Docker容器日志进行检测。
图2为本申请实施例二提供的方法的细化流程图，该方法包括以下步骤。
S201、扫描预设接口下的源码库中的观测点信息。
在本实施例中，源码库为业务代码运行的所有源码，其中包括旧的源码及更新的源码。其中的预设接口是程序员在编制业务代码时插入的预设数量的观察点，其中预设接口包括但不限于与行为特征输出方式、用于标示行为特征属性的关键字等。扫描源码库中的源码，利用正则表达式根据过滤条件至少包括模块名、时间、级别及内容这四个要素，过滤出所有观测点信息。
S202、提取出源码库中的预设数量的观测点信息的内容，形成包括预设数量的规则树ID、第一规则树检测类型、第二规则树检测类型的模型库的列表。
在本实施例中，预设数量的观测点信息的内容包括业务代码运行的时序和路径，业务代码运行中的预设信息，其中预设信息为关键信息，可根据程序员提前自行设定或判断该预设信息为关键信息。
在本实施例中，第一规则树检测类型为：采用嵌套的规则引用，先从超时时长为0的匹配项开始，满足所有的匹配项就算正常，而匹配项与匹配项之间用多个嵌套的规则引用(option)来连接，其中每个option里面都嵌套有匹配项与匹配项之间连接的分支，只要满足其他一个分支即可从前一个匹配项到后一个匹配项。一旦不满足其他任何一个匹配项就会记录在模型库中，若超过匹配项的检测时长，则检测结果为表示故障的含义；若未超过匹配项的检测时长，但多个option中的分支没检测到，则检测结果为表示未完的含义。其中第二规则树检测类型是所有的规制匹配项都满足算故障，一旦不满足其他任何一个匹配项，则会被忽略，不会记录在模型库中，在检测健康程度或不知道是否故障时，可以先用第一规则树检测类型来检测，在用第一规则树检测类型检测出有故障时，在用第二规则树检测类型进行检测看故障具体位置，也可以在针对有故障的日志文件直接利用第二规则树检测类型进行检测，看具体故障位置在何处。
S203、修正观测点信息的重复信息和/或错误信息。
S204、根据规则树ID的关键属性的模型库列表创建包括至少一节点的预设特定行为的规则树表。
在本实施例中，模型库列表的关键属性包括规则树ID、第一规则检测类型、第二规则检测类型。其中规则树表的节点的预设规则字段包括超时时长、格式化字符串、规则参数、第一规则匹配类型、第二规则匹配类型这几个字段。其中超长时长为0-预设的时间，其中超时时长为0表示第0条标准匹配项[0],即是匹配项的开始，该规则树表中的根节点，只有满足这个唯一的规则匹配项[0]，才开始对待测日志文件进行检测。其中所述格式化字符串引用观测点信息的内容的预设信息和路径，所述规则参数引用观测点信息的内容的时序；该预设信息为关键点信息。规则参数项的时序值可以由并、或的关系组成。格式化字符串引用观测点信息的内容，按照代码运行的逻辑顺序引用这些关键点作为规则匹配项。其中第二匹配类型的树表还可以包括规则引用字段，该规则引用字段填写着需要关联的其他规则树ID的规则树表。对于第一匹配类型的规则树表可以无规则引用字段，也可以有规则引用字段但规则引用字段里面的内容为空。
S205、将规则树表存储在模型库中。
在本实施例中，在将规则树表存储前还可以包括：由开发人员梳理带规则树表的代码是否有效。
S206、待测日志文件匹配上模型库中的一个规则树表的超时时长为0的匹配项，检测是否可以用第一规则树检测类型匹配上该规则树表中的格式化字符串和规则参数。
在本实施例中，第一规则树检测类型为：采用嵌套的规则引用，先从超时时长为0的匹配项的树的根节点开始，满足所有的匹配项就算正常，而匹配项与匹配项之间用多个嵌套的规则引用(option)来连接，其中每个option里面都嵌套有匹配项与匹配项之间连接的分支，只要满足其他一个分支即可从前一个匹配项到后一个匹配项。一旦不满足其他任何一个匹配项就会记录在模型库中，若超过匹配项的检测时长，则检测结果为表示故障的含义；若未超过匹配项的检测时长，但多个option中的分支没检测到，则检测结果为表示未完的含义。待测日志文件为正运行5G基站的代码数据，当匹配上一个规则树表的超时时长为0的匹配项时，并匹配上用第一规则树检测类型匹配上该规则树表中的格式化字符串和规则参数时，执行S210，否则执行207。
S207、检测是否可以根据第二规则树检测类型匹配上该规则树表中的格式化字符串和规则参数。
在本实施例中，根据第二规则树检测类型匹配上该规则树表中的格式化字符串和规则参数时，则执行S208，否则执行S209。
S208、导出待测日志文件匹配上的规则树表的信息。
S209、导出待测日志文件未匹配上第一规则树检测类型和/或第二规则树检测类型的规则树表的信息。
S210、结束。
本申请的实施例提供的识别通讯设备状态的方法，通过扫描预设接口下的源码库中的预设接口的观测点信息，提取出源码库中的预设数量的观测点信息的内容，形成包括预设数量的规则树ID、第一规则树检测类型、第二规则树检测类型的模型库的列表。修正观测点信息的重复信息和/或错误信息。然后根据规则树ID的关键属性的模型库列表创建包括至少一个节点的若干个特定行为的规则树表，将这若干个规则树表存储在模型库中。然后检测待测日志文件匹配上一个规则树表的超时时长为0的根节点的匹配项时，是否可以用第一规则树检测类型匹配上该根节点对应的规则树表中的格式化字符串和规则参数，在匹配上时，说明为正常的，在没有匹配上时用第二规则树检测类型匹配上该规则树表中的格式化字符串和规则参数，匹配上第二规则树检测类型的规则树表时，导出待测日志文件匹 配上的该规则树表的信息。未匹配上第二规则树检测类型的规则树表时，导出待测日志文件未匹配上第一规则树检测类型和/或第二规则树检测类型的规则树表的信息。实现了快速识别到通讯设备的状态，定位到通讯设备故障状态的位置，若是自动化定位不出来的话，再施预人工定位方式。该定位工具可以为外场技术人员节约75％～85％的定位故障的时间，便于技术人员更加及时快速地解决故障，缩短故障延时，极大地提高了定位故障的效率，为5GNR基站的长期高效地可靠稳定运行提供有力保障，节约了企业维护人力资源投入的成本。同时在扫描出观测点信息后，创建规则树表后还可以二次检查该源代码，树表的代码是否存在错误或重复等。
实施例三
本申请的即时通讯系统信息保存方法实现了，为了便于理解，下面结合一种应用场景对本申请的方法进行说明。该应用场景是对通讯系统的历史故障的日志文件进行检测。
图3为本申请实施例三提供的方法的细化流程图，该方法包括以下步骤。
S301、扫描预设接口下的源码库中的观测点信息。
在本实施例中，源码库为业务代码运行的在预设时间进行更新的新的源码。其中的预设接口是程序员在编制业务代码时插入的预设数量的观察点，其中预设接口包括但不限于与行为特征输出方式、用于标示行为特征属性的关键字等。扫描源码库中的源码，利用正则表达式根据过滤条件至少包括模块名、时间、级别及内容这四个要素，过滤出所有观测点信息。
S302、提取出源码库中的预设数量的观测点信息的内容，形成包括预设数量的规则树ID、第一规则树检测类型、第二规则树检测类型的模型库的列表。
在本实施例中的观测点信息的内容包括业务代码运行的时序和路径，业务代码运行中的预设信息，其中预设信息为关键信息，可根据程序员提前自行设定或判断该预设信息为关键信息。
在本实施例中的第二规则树检测类型是所有的规制匹配项都满足算故障，一旦不满足其他任何一个匹配项，则会被忽略，不会记录在模型库中。
S303、根据规则树ID的关键属性的模型库列表创建包括至少一节点的预设特定行为的规则树表。
在本实施例中，规则树表的各个节点的预设规则字段包括超时时长、格式化字符串、规则参数、第一规则匹配类型、第二规则匹配类型这几个字段。其中超长时长为0-预设的时间，其中超时时长为0表示第0条标准匹配项[0],即是匹配项的开始，也是规则树表的根 节点，只有满足这个唯一的规则匹配项[0]，才开始对待测日志文件进行检测。其中所述格式化字符串引用观测点信息的内容的预设信息和路径，所述规则参数引用观测点信息的内容的时序；该预设信息为关键点信息。规则参数项的时序值可以由并、或的关系组成。格式化字符串引用观测点信息的内容，按照代码运行的逻辑顺序引用这些关键点作为规则匹配项。其中第二匹配类型的树表还可以包括规则引用字段，该规则引用字段填写着需要关联的其他规则树ID的规则树表。对于第一匹配类型的规则树表可以无规则引用字段，也可以有规则引用字段但规则引用字段里面的内容为空。
S304、将规则树表存储在模型库中，根据该模型库更新旧的模型库。
S305、待测日志文件匹配上模型库中的一个规则树表的超时时长为0的匹配项，用第二规则树检测类型匹配上该规则树表中的格式化字符串和规则参数，导出待测日志文件匹配上的该规则树表的信息。
本申请的实施例提供的识别通讯设备状态的方法，通过扫描预设接口下的源码库中的观测点信息，提取出源码库中的观测点信息的内容，形成包括规则树ID的关键属性的模型库列表，根据规则树ID的关键属性的模型库列表创建包括至少一个节点的预设特定行为的规则树表；将规则树表存储在模型库中，根据该模型库更新旧的模型库。最后待测日志文件匹配上模型库中的一个规则树表的超时时长为0的匹配项，用第二规则树检测类型匹配上该规则树表中的格式化字符串和规则参数，导出待测日志文件匹配上的该规则树表的信息。实现了因为业务增多，对旧模型库的更新，无论通讯设备是代码错误还是其他原因导致的依次，都可实现快速定位到通讯设备故障状态的位置，提高基站故障或异常定位的速度及效率，避免基站长时间罢工而影响用户体验，保证了整个通讯系统在故障时的快速恢复稳定运行。
实施例四
为了解决的检测通讯设备需要依赖熟悉业务流程的人员，无法快速定位的问题，本申请提供一种通讯系统，下面结合实施例对本申请提出的通讯系统进行说明。
请参见图4，图4为本申请实施例四提供的通讯系统的组成示意图，该通讯系统包括：生成模块401、采集模块402及解析模块403；其中生成模块401包括提取模块4011和创建模块4012。
提取模块4011，用于提取出源码库中的预设数量的观测点信息的内容，形成，形成包括规则树ID的预设关键属性的模型库列表；观测点信息的内容包括业务代码运行的预设信息、时序和路径；其中预设信息为关键信息点。
创建模块4012，用于根据包括规则树ID的关键属性的模型库列表创建包括至少一个节点的预设特定行为的规则树表，规则树表包括格式化字符串和规则参数，格式化字符串引用预设信息和路径，规则参数引用时序；将预设特定行为的规则树表存储在模型库中。
采集模块402，用于采集待测日志文件。
解析模块403，用于解析待测日志文件，当待测日志文件匹配上规则树表时，获取日志文件匹配上的规则树表的信息。
在本实施例中，模型库列表还包括规则树检测类型；创建模块还用于根据规则检测类型将待测日志文件匹配上规则树表。
采集模块402，还用于采集源码库中的观测点信息，观测点信息包括模块名、时间、级别和所述内容。
规则树表包括：规则匹配类型，所述规则匹配类型包括第一匹配类型和第二匹配类型，所述第一匹配类型的规则树表无规则引用或有规则引用，但规则引用中无内容，所述第二类型的的规则树表有规则引用字段，所述规则引用字段包括需要关联的其他规则树ID。所述第一类型的规则引用字段无内容，所述第二类型的规则引用字段包括需要关联的其他规则树ID。
规则树表包括：超长时长的字段；解析模块包括匹配模块和规则检查模块，匹配模块用于使用所述待测日志文件匹配到超时时长为0的规则树表的根节点，即匹配项[0]；所述规则检查模块用于检查待测日志文件的格式字符串和规则参数能匹配到该规则树表的其他匹配项其他匹配项及除根节点的其他节点的内容时，获取待测日志文件匹配上的该规则树表的信息。其中匹配模块中有取出模型库中所有树表的所有的规则匹配项中的第0个匹配项，即所有树表的根节点。
本实施例提供的通讯系统，通过提取模块提取出源码库中的观测点信息的内容，形成包括规则树ID的预设关键属性的模型库列表，然后创建模块根据包括规则树ID的关键属性的模型库列表创建包括至少一个节点的预设特定行为的规则树表；将规则树表存储在所述模型库中；采集模块采集待测日志文件，解析模块解析待测日志文件，当待测日志文件匹配上规则树表时，获取待测日志文件匹配上的所述规则树表的信息。实现了快速识别到通讯设备的状态，定位到通讯设备故障状态的位置。
实施例五
本实施例提供了一种通讯系统，参见图5所示，其包括处理器51、存储器52及通信总线53，其中：通信总线53用于实现处理器51和存储器52之间的连接通信；处理器51 用于执行存储器52中存储的一个或者多个计算机程序，以实现上述实施例一至实施例三中任一个的识别通讯设备状态的方法中的至少一个步骤。
本实施例还提供了一种计算机可读存储介质，该计算机可读存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、计算机程序模块或其他数据)的任何方法或技术中实施的易失性或非易失性、可移除或不可移除的介质。计算机可读存储介质包括但不限于RAM(Random Access Memory，随机存取存储器),ROM(Read-Only Memory，只读存储器),EEPROM(Electrically Erasable Programmable read only memory，带电可擦可编程只读存储器)、闪存或其他存储器技术、CD-ROM(Compact Disc Read-Only Memory，光盘只读存储器)，数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。
本实施例中的计算机可读存储介质可用于存储一个或者多个计算机程序，其存储的一个或者多个计算机程序可被处理器执行，以实现上述实施例一至实施例三中任一个的识别通讯设备状态的方法中的至少一个步骤。
本实施例通过提取出源码库中的观测点信息的内容，形成包括规则树ID的关键属性的模型库列表；然后根据规则树ID的关键属性的模型库列表创建包括至少一个节点的预设特定行为的规则树表；将规则树表存储在模型库中，最后当待测日志文件匹配上规则树表时，获取待测日志文件匹配上的规则树表的信息。在某些实施过程中可实现包括但不限于的快速识别到通讯设备的状态，定位到通讯设备故障状态的位置的技术效果。
本申请的有益效果是：根据本申请实施例提供的识别通讯设备状态的方法、通讯系统及存储介质，通过提取出源码库中的观测点信息的内容，形成包括规则树ID的关键属性的模型库的列表，根据规则树ID的关键属性的模型库列表创建包括至少一个节点的预设特定行为的规则树表，将规则树表存储在模型库中，最后当待测日志文件匹配上规则树表时，获取待测日志文件匹配上的规则树表的信息。在某些实施过程中可实现包括但不限于的快速识别到通讯设备的状态，定位到通讯设备正常状态或故障状态的位置的技术效果。
可见，本领域的技术人员应该明白，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件(可以用计算装置可执行的计算机程序代码来实现)、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。
此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、计算机程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。所以，本申请不限制于任何特定的硬件和软件结合。
以上内容是结合具体的实施方式对本申请实施例所作的进一步详细说明，不能认定本申请的具体实施只局限于这些说明。对于本申请所属技术领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本申请的保护范围。

Claims (10)

  1. 一种识别通讯设备状态的方法，所述方法包括：
    提取出源码库中的预设数量的观测点信息的内容，形成包括规则树ID的关键属性的模型库列表；
    根据规则树ID的关键属性的模型库列表创建包括至少一个节点的预设指定行为的规则树表；将所述规则树表存储在所述模型库中；
    当待测日志文件匹配上所述规则树表时，获取所述待测日志文件匹配上的所述规则树表的信息。
  2. 如权利要求1所述的识别通讯设备状态的方法，其中，所述模型库列表的关键属性还包括规则树检测类型；所述待测日志文件匹配上所述规则树表包括：所述待测日志文件根据所述规则树检测类型匹配上所述规则树表。
  3. 如权利要求2所述的识别通讯设备状态的方法，其中，所述规则树检测类型包括第一规则树检测类型和第二规则树检测类型，所述待测日志文件根据规则树检测类型匹配上所述规则树表包括：所述待测日志文件根据第一规则树检测类型和/或第二规则树检测类型匹配上所述规则树表。
  4. 如权利要求1所述的识别通讯设备状态的方法，其中，所述节点包括：规则匹配类型，所述规则匹配类型包括第一匹配类型和第二匹配类型，所述第一匹配类型的规则树表无规则引用或有规则引用，但规则引用中无内容，所述第二类型的规则树表有规则引用字段，所述规则引用字段包括需要关联的其他规则树ID的规则树表。
  5. 如权利要求1所述的识别通讯设备状态的方法，其中，所述源码库包括所述业务代码运行的所有源码或所述业务代码运行的在预设时间进行更新的新的源码；当源码库为所述新的源码时，所述将所述规则树表存储在所述模型库中还包括：根据所述模型库对预设模型库进行更新形成新的模型库。
  6. 如权利要求1所述的识别通讯设备状态的方法，其中，所述节点包括：超长时长为0的根节点；所述当待测日志文件匹配上所述规则树表时，获取所述待测日志文件匹配上的所述规则树表的信息包括：当待测日志文件匹配上所述模型库中的任意一个有所述根节点的规则树表时，待测日志文件的格式字符串和规则参数能匹配到所述有所述根节点的规则树表中的格式字符串和规则参数时，则获取待测日志文件匹配上的规则树表的信息。
  7. 如权利要求1-6任一项所述的识别通讯设备状态的方法，其中，所述观测点信息为预设接口的观测点信息，所述提取出源码库中的预设数量的观测点信息还包括： 修正所述观测点信息的重复信息和/或错误信息。
  8. 一种通讯系统，所述系统包括：生成模块、采集模块及解析模块；所述生成模块包括提取模块和创建模块；
    所述提取模块，用于提取出源码库中的预设数量的观测点信息的内容，形成包括规则树ID的预设关键属性的模型库列表；
    所述创建模块，用于根据包括规则树ID的关键属性的模型库列表创建包括至少一个节点的预设指定行为的规则树表；将所述规则树表存储在所述模型库中；
    所述采集模块，用于采集待测日志文件；
    所述解析模块，用于解析所述待测日志文件，当所述待测日志文件匹配上所述规则树表时，获取所述待测日志文件匹配上的所述规则树表的信息。
  9. 一种通讯系统，所述系统包括处理器、存储器及通信总线；
    所述通信总线用于实现处理器和存储器之间的连接通信；
    所述处理器用于执行存储器中存储的一个或者多个计算机程序，以实现如权利要求1至7中任一项所述的识别通讯设备状态方法的步骤。
  10. 一种计算机可读存储介质，其中，所述计算机可读存储介质
    存储有一个或者多个计算机程序，所述一个或者多个计算机程序可被一个或者多个处理器执行，以实现如权利要求1至7中任一项所述的识别通讯设备状态方法的步骤。
PCT/CN2020/118840 2019-12-24 2020-09-29 识别通讯设备状态的方法、通讯系统及存储介质 WO2021129024A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911341778.8A CN113037521B (zh) 2019-12-24 2019-12-24 识别通讯设备状态的方法、通讯系统及存储介质
CN201911341778.8 2019-12-24

Publications (1)

Publication Number Publication Date
WO2021129024A1 true WO2021129024A1 (zh) 2021-07-01

Family

ID=76451270

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/118840 WO2021129024A1 (zh) 2019-12-24 2020-09-29 识别通讯设备状态的方法、通讯系统及存储介质

Country Status (2)

Country Link
CN (1) CN113037521B (zh)
WO (1) WO2021129024A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115941546A (zh) * 2022-11-29 2023-04-07 重庆长安汽车股份有限公司 系统接口的监控方法、装置、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050081106A1 (en) * 2003-10-08 2005-04-14 Henry Chang Software testing
CN101425064A (zh) * 2007-10-29 2009-05-06 英业达股份有限公司 测试日志处理方法及系统
CN103337113A (zh) * 2013-07-17 2013-10-02 广州广电运通金融电子股份有限公司 电子流水日志智能分析方法、装置及处理器
CN109558309A (zh) * 2018-10-19 2019-04-02 中国平安财产保险股份有限公司 代码测试结果分析方法、装置、计算机设备和存储介质
CN109614469A (zh) * 2018-12-03 2019-04-12 郑州云海信息技术有限公司 一种日志分析方法和装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060436A (zh) * 2007-06-05 2007-10-24 杭州华三通信技术有限公司 一种用于通信设备的故障分析方法及装置
JP2011170724A (ja) * 2010-02-22 2011-09-01 Hitachi Ltd 故障診断システム、故障診断装置および故障診断プログラム
CN105335488A (zh) * 2015-10-16 2016-02-17 中国南方电网有限责任公司电网技术研究中心 一种知识库构建方法
CN107832196B (zh) * 2017-11-28 2021-07-06 广东金赋科技股份有限公司 一种用于实时日志异常内容的监测装置及监测方法
CN108984332A (zh) * 2018-06-22 2018-12-11 郑州云海信息技术有限公司 一种定位服务器宕机故障的装置及方法
CN110046073B (zh) * 2019-03-29 2022-10-18 厦门网宿有限公司 一种日志采集方法及装置、设备、存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050081106A1 (en) * 2003-10-08 2005-04-14 Henry Chang Software testing
CN101425064A (zh) * 2007-10-29 2009-05-06 英业达股份有限公司 测试日志处理方法及系统
CN103337113A (zh) * 2013-07-17 2013-10-02 广州广电运通金融电子股份有限公司 电子流水日志智能分析方法、装置及处理器
CN109558309A (zh) * 2018-10-19 2019-04-02 中国平安财产保险股份有限公司 代码测试结果分析方法、装置、计算机设备和存储介质
CN109614469A (zh) * 2018-12-03 2019-04-12 郑州云海信息技术有限公司 一种日志分析方法和装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115941546A (zh) * 2022-11-29 2023-04-07 重庆长安汽车股份有限公司 系统接口的监控方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN113037521A (zh) 2021-06-25
CN113037521B (zh) 2024-01-19

Similar Documents

Publication Publication Date Title
JP5791698B2 (ja) アバップソースコードのコード検査遂行システム
US20180365092A1 (en) Knowledge-based system for diagnosing errors in the execution of an operation
CN103257919B (zh) 脚本程序检查方法和装置
US20110029539A1 (en) Metadata as comments for search problem determination and analysis
CN111190807B (zh) 一种埋点测试方法及设备
CN107766353B (zh) 一种数据库统计信息迁移的方法和设备
Nagy et al. Where was this SQL query executed? a static concept location approach
CN109271315B (zh) 脚本代码检测方法、装置、计算机设备及存储介质
CN108920140A (zh) 一种前后端统一校验方法
WO2017164856A1 (en) Comparable user interface object identifications
WO2021129024A1 (zh) 识别通讯设备状态的方法、通讯系统及存储介质
CN116431476A (zh) 一种基于代码上下文变异的jvm模糊测试方法
CN115408370A (zh) 数据库迁移评估方法和系统、计算机设备、存储介质
CN114185791A (zh) 一种数据映射文件的测试方法、装置、设备及存储介质
CN111767213B (zh) 数据库检查点的测试方法、装置、电子设备及存储介质
CN112256575A (zh) 一种代码质量管理方法、系统及相关设备
CN114610385B (zh) 一种运行环境适配系统及方法
CN113868137A (zh) 埋点数据的处理方法、装置、系统和服务器
CN115238655A (zh) 一种json数据编辑方法和装置
CN110795142B (zh) 一种配置文件的生成方法及装置
CN110321130B (zh) 基于系统调用日志的不可重复编译定位方法
CN113326046A (zh) 获取编译时长的方法和装置
CN113742213A (zh) 一种用于数据分析的方法、系统和介质
CN111736848A (zh) 包冲突定位方法、装置、电子设备及可读存储介质
CN111338956A (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: 20908328

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

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 200223)

122 Ep: pct application non-entry in european phase

Ref document number: 20908328

Country of ref document: EP

Kind code of ref document: A1