WO2023024854A1 - 根因定位方法、根因定位设备及存储介质 - Google Patents

根因定位方法、根因定位设备及存储介质 Download PDF

Info

Publication number
WO2023024854A1
WO2023024854A1 PCT/CN2022/109896 CN2022109896W WO2023024854A1 WO 2023024854 A1 WO2023024854 A1 WO 2023024854A1 CN 2022109896 W CN2022109896 W CN 2022109896W WO 2023024854 A1 WO2023024854 A1 WO 2023024854A1
Authority
WO
WIPO (PCT)
Prior art keywords
serving cell
root cause
abnormal
primary serving
primary
Prior art date
Application number
PCT/CN2022/109896
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 WO2023024854A1 publication Critical patent/WO2023024854A1/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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • This application relates to but not limited to the field of communication technology.
  • the present application provides a root cause location method, a root cause location device and a storage medium.
  • the present application provides a method for locating the root cause, including: obtaining the primary serving cell where the abnormal service occurs, and determining the grid corresponding to the primary serving cell; extending the grid to obtain a grid group, and Determining the serving cell group corresponding to the grid group; performing anomaly detection on the serving cell group and the primary serving cell to obtain the root cause of the service anomaly.
  • the present application also provides a root cause locating device, the root cause locating device includes a processor, a memory, a computer program stored on the memory and executable by the processor, and used to realize the A data bus connecting and communicating between the processor and the memory, wherein when the computer program is executed by the processor, the steps of any root cause location method as described herein are implemented.
  • the present application also provides a storage medium for computer-readable storage, the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to Implement the steps of any one of the root cause location methods as described herein.
  • Fig. 1 is a schematic flow chart of a root cause localization method provided by the present application
  • Figure 2 is a schematic diagram of the scope of the grid group obtained after the grid is expanded provided by the present application;
  • Fig. 3 is a schematic flow chart of the root cause localization method provided by the present application.
  • FIG. 4 is a schematic diagram of the read user face bill provided by the present application.
  • FIG. 5 is a schematic diagram of extracted wireless data provided by the present application.
  • Fig. 6 is another schematic flowchart of the root cause location method provided by the present application.
  • FIG. 7 is a schematic diagram of another user face bill read provided by the present application.
  • FIG. 8 is a schematic diagram of another extracted wireless data provided by the present application.
  • FIG. 9 is a schematic structural block diagram of a root cause location device provided in the present application.
  • embodiments of the present application provide a root cause location method, a root cause location device, and a storage medium.
  • the root cause location method can be applied to mobile terminals, and the mobile terminals can be electronic devices such as mobile phones, tablet computers, notebook computers, desktop computers, personal digital assistants and wearable devices.
  • the technical solutions of the embodiments of the present application can at least realize automatic root cause location and obtain the comprehensiveness of the root cause.
  • FIG. 1 is a schematic flowchart of a root cause location method provided in the present application.
  • the root cause location method includes steps S101 to S103.
  • Step S101 Obtain a primary serving cell where a service exception occurs, and determine a grid corresponding to the primary serving cell.
  • the primary serving cell where the abnormal business behavior occurs is first acquired.
  • the primary serving cell where the abnormal business behavior occurs is first acquired.
  • the wireless base station and the UPF (User Plane Function) of the core network 5GC (5G Core Network) the original signaling of the user plane can be collected.
  • the user-side bill is obtained, and the user-side bill includes the cell where the service behavior occurs.
  • the collected user face bill can be formatted as the following data structure data_cn:
  • ⁇ imsi, msisdn> can uniquely mark a user information
  • ⁇ starttime> indicates the start time of the service
  • ⁇ gnb_length, gnbid, cellid> indicates the 5G cell where the service occurs
  • ⁇ ulflux, dlflux> indicates the uplink and downlink traffic of the service
  • ⁇ duration> indicates the duration of the service
  • ⁇ ultimeusage, dltimeusage> indicates the actual uplink and downlink service duration of the service
  • ⁇ pause_duration> indicates the waiting time for video service playback
  • ⁇ buffer_duration> indicates the buffering duration of the video service
  • ⁇ pause_cnt> indicates the video service The number of business freezes.
  • the main serving cell where the abnormal service behavior occurs can be determined through the ⁇ gnb_length, gnbid, cellid> in the user plane bill.
  • the grid can be pre-planned, such as dividing the map of a province or city into multiple grids of the same size, such as dividing the map into grids of 50cm*50cm .
  • the step of determining the grid corresponding to the primary serving cell may include: acquiring wireless data with abnormal services, the wireless data including cell data with abnormal services and the grid data with abnormal services; The primary serving cell, the cell data of the abnormal service and the grid data of the abnormal service determine a grid corresponding to the primary serving cell.
  • the start time of the abnormal business behavior can be determined according to the ⁇ starttime> in the user-side bill, and then the wireless data at the corresponding time can be obtained according to the start time of the abnormal business behavior. Since the wireless data includes the cell where the business abnormality occurred and the grid where the business abnormality occurred, after obtaining the wireless data, it can be based on the determined primary serving cell, the cell where the business grid to determine the grid corresponding to the primary serving cell. If the main serving cell and the abnormal cell are the same cell, it can be considered that the grid corresponding to the main serving cell is the grid where the abnormal service occurs in the wireless data.
  • the wireless data at the corresponding time can be obtained only according to the ⁇ starttime> in the bill on the user plane, but considering the time difference between the base station and the wireless side, the Wireless data within a preset offset time can be acquired. For example, if the start time of the abnormal business behavior is determined to be 2021-04-22 12:35:09.883 according to ⁇ starttime> in the user-side bill, and the preset offset time is 2 minutes, then when acquiring wireless data , you can get wireless data from 2021-04-22 12:33:09.883 to 2021-04-22 12:37:09.883. It can be understood that the preset offset time is an empirical value and can be modified according to actual application conditions.
  • the collected wireless data can also be formatted to obtain the following data structure data_ran:
  • ⁇ msi_ran, msisdn_ran> can uniquely mark a user information
  • ⁇ starttime_ran> indicates the start time of the service
  • ⁇ gnb_length_ran, gnbid_ran, cellid_ran> indicates the cell where the service occurs
  • ⁇ ssb_rsrp> indicates the ssb_rsrp value of the cell
  • ⁇ regionid, x_offset , y_offset> indicates the grid where the service is located
  • ⁇ ssb_rsrq> indicates the ssb_rsrq value of the cell
  • ⁇ is_dlweakcover> indicates whether the current cell is a weak coverage cell
  • ⁇ pci> indicates the physical flag of the cell
  • ⁇ avgrip> indicates the RIP (Received Interference Power, received interference power)
  • ⁇ isrrcuser_overload> indicates whether the maximum number of activated users is too high
  • the wireless data can also be associated with the user plane bill according to the cell where the service abnormality occurs in the wireless data, and then the ⁇ regionid, x_offset, y_offset representing the grid in the wireless data >The data is backfilled into the extended call list on the user plane.
  • association conditions when associating wireless data with user face bill data can be:
  • data_cn.imsi in the user plane bill is equivalent to data_ran.imsi_ran in the wireless data
  • data_cn.gnb_length in the user plane bill is equivalent to data_ran.gnb_length_ran in the wireless data
  • data_cn.gnbid in the user plane bill is equivalent to the wireless data_ran.gnbid_ran in the data
  • data_cn.cellid in the user-side bill is equivalent to data_ran.cellid in the user-side bill
  • the root cause location method may further include: obtaining a user-side bill, which includes a bill quality parameter and a cell; if the user-side bill is determined according to the bill quality parameter If it is only an abnormal bill, the cell will be taken as the main serving cell where the abnormal service occurs.
  • the user-side bill includes the bill quality parameter, it can be determined whether the currently acquired user-side bill is an abnormal bill according to the bill quality parameter in the user-side bill, wherein the abnormal bill may be a case of poor service perception one.
  • the parameter value corresponding to the bill quality parameter exceeds the preset index threshold, it can be considered that the current user-side bill is an abnormal bill, and the cell in the abnormal bill is an occurrence The main serving cell with abnormal business.
  • the bill quality parameter may include at least one of video playback duration, video service buffering duration, and video service freeze times.
  • Step S102 expand the grid to obtain a grid group, and determine a serving cell group corresponding to the grid group.
  • grid extension is performed based on the grid to obtain a grid group.
  • the grid where the business exception currently occurs may be centered and extended to four quadrants respectively, and the extended range may be set according to experience values.
  • three grids can be expanded outward, as shown in Figure 2, which is a schematic diagram of the range of the expanded grid group.
  • the grid marked with a five-pointed star in the figure is the grid with business exceptions, and the rest
  • the abnormal grid is expanded as the center, and these expanded grids and the grid with business exceptions are used as a grid group.
  • the grid size is 50cm*50cm
  • the size of the expanded grid group is 350cm *350cm.
  • the serving cells corresponding to each grid in the grid group can be determined according to the grid and the original planning file of the cell, so as to obtain the serving cell group.
  • the serving cell corresponding to the grid multiple different grids may correspond to the same serving cell, and the same grid may also correspond to different serving cells.
  • the corresponding relationship between the grid and the serving cell can be formatted and described as:
  • ⁇ regionid_n, x_offset_n, y_offset_n> indicates the grid position
  • ⁇ gnb_length_n, gnb_id_n, cellid_n> indicates the location of the serving cell
  • ⁇ regionid_n, x_offset_n, y_offset_n, gnb_length_n, gnb_id_n, cellid_n> indicates the location is ⁇ regionid_n, x_offset_n, y_offset_n>
  • the serving cell corresponding to the grid of is ⁇ gnb_length_n, gnb_id_n, cellid_n>.
  • the resulting extended grid group includes 49 grids, which can be expressed as:
  • the serving cell corresponding to each grid is:
  • deduplication processing can be performed on the cells in the set of serving cells, and the set of deduplicated serving cells can be used as the serving cell group corresponding to the grid group, and the obtained serving cell group is:
  • Step S103 performing anomaly detection on the serving cell group and the primary serving cell to obtain the root cause of the service anomaly.
  • anomaly detection and root cause location can be performed on the serving cell group and the main serving cell at this time, so as to obtain the root cause of the abnormal business.
  • the step of performing anomaly detection on the serving cell group and the primary serving cell to obtain the root cause of the service anomaly may include: performing anomaly detection on the serving cells in the serving cell group, Obtaining a first root cause corresponding to the serving cell group; performing anomaly detection on the primary serving cell to obtain a second root cause corresponding to the primary serving cell.
  • the serving cell group includes multiple serving cells, traversing each serving cell in the serving cell group, and performing anomaly detection on all the serving cells in the serving cell group, so as to obtain the first root cause corresponding to the serving cell group, and, Anomaly detection is also performed on the primary serving cell to obtain the second root cause corresponding to the primary serving cell. Combine the first root cause and the second root cause to get the root cause of the business exception.
  • the detection content of the abnormality detection of the primary serving cell may be different from the detection content of the abnormality detection of the serving cells in the serving cell group.
  • first root causes or multiple second root causes may be obtained during anomaly detection, and all first or second root causes obtained may be used as root causes
  • the step of performing anomaly detection on the serving cells in the serving cell group and obtaining the first root cause corresponding to the serving cell group may include: obtaining the alarm time of the serving cells in the serving cell group , and determine whether the occurrence time of the service anomaly is within the warning period; if the occurrence time of the service anomaly is within the warning period, an alarm of the existence of the serving cell is obtained.
  • the serving cell group Traverse each serving cell in the serving cell group, and judge the alarm category for each serving cell in the serving cell group respectively.
  • the time when the business anomaly occurs is within the alarm period, you can get a first One reason is that an alarm occurs in the serving cell.
  • the occurrence time of the service exception can be determined according to the ⁇ starttime> in the user face bill.
  • the alarms are divided into out-of-service alarms and non-out-of-service alarms.
  • the out-of-service alarms can include the out-of-service of the serving cell, the out-of-service of the base station, the shutdown of the closed area of the serving cell, and the power failure of the equipment, etc.
  • the out-of-service alarms can include the alarm of network element disconnection, abnormal synchronization of the base station, and wireless interference detection. Abnormal, no available air interface clock source, antenna feeder link failure, etc.
  • service_starttime indicates the time when the service occurs
  • alarm_starttime indicates the time when the alarm occurs
  • ⁇ t indicates the time deviation
  • [alarm_starttime- ⁇ t, alarm_starttime+ ⁇ t] indicates the alarm period
  • service_starttime indicates the time when the service occurs
  • alarm_starttime indicates the time when the alarm occurs
  • alarm_cleartime indicates the time when the alarm is cleared
  • [alarm_starttime, alarm_cleartime] indicates the alarm period
  • the step of performing anomaly detection on the serving cells in the serving cell group, and obtaining the first root cause corresponding to the serving cell group may include: obtaining the bearer link of the serving cell in the serving cell group link parameters, and determine whether the bearer link is abnormal according to the link parameters; if the bearer link of the serving cell in the serving cell group is abnormal, it is obtained that the bearer link of the serving cell is abnormal.
  • Each serving cell in the serving cell group is traversed, and the link parameters of the bearer links of each serving cell in the serving cell group are obtained respectively, so as to judge the abnormality of the bearer link according to the link parameters.
  • a first root cause can be obtained, which is that the bearer link of the serving cell is abnormal.
  • a bearer link can be uniquely identified by the transmitter network element ME_OID, the transmitter port InBoundInf, the reflector network element ReflectorMe, and the reflector port ReflectorPort, and the bearer link can be recorded as a hearer_link. Then acquire link parameters of the bearer link, where the link parameters may include at least one of jitter, delay and packet loss rate. When at least one of the link parameters exceeds the corresponding preset threshold value, it can be considered that the bearer link is abnormal, and a first root cause can be obtained, which is that the bearer link is abnormal in the serving cell. In addition, when the first root cause is obtained, the specific link where the abnormality occurs and the parameters of the link where the abnormality occurs can be given at the same time.
  • the step of performing anomaly detection on the serving cells in the serving cell group, and obtaining the first root cause corresponding to the serving cell group may include: obtaining the configuration of the base station corresponding to the serving cell in the serving cell group parameters and reference parameters; if the configuration parameters are inconsistent with the reference parameters, it is obtained that configuration parameters of the base station are changed.
  • the reference parameters are also suggested values.
  • the current configuration parameters are different from the reference parameters, it can be considered that the base station has a parameter configuration change, that is, a The first root cause is that the configuration parameters of the base station are changed.
  • the obtained multiple first root causes may be output, or each first root cause may be Depending on the priority of the cause, select the one with a higher priority as the first root cause of the final output.
  • the priority may be alarm>bearer link abnormality>configuration parameter change, and among the alarms, the priority of out-of-service alarms is higher than that of non-out-of-service alarms.
  • the cell closest to the grid corresponding to the primary serving cell can be selected from the multiple serving cells as the output .
  • the step of performing anomaly detection on the primary serving cell and obtaining the second root cause corresponding to the primary serving cell may include: determining whether the serving cell group includes the primary serving cell; if the The serving cell group does not include the primary serving cell, and the primary serving cell is over-covered.
  • the primary serving cell group When performing anomaly detection on the primary serving cell, determine whether the primary serving cell is included in the serving cell group. Normally, the primary serving cell should be included in the serving cell group, but if the primary serving cell is over-covered, the primary serving cell may appear The cell is no longer in the serving cell group, therefore, it can be judged whether the serving cell group includes the primary serving cell to determine whether the primary serving cell has been covered. If the primary serving cell is not in the serving cell group, that is, the primary serving cell is not included in the serving cell group, it is considered that the primary serving cell is over-covered, and a second root cause can be obtained, which is that the primary serving cell has over-covered.
  • the step of performing anomaly detection on the primary serving cell and obtaining the second root cause corresponding to the primary serving cell may include: obtaining capacity parameters of the primary serving cell, and performing The primary serving cell performs capacity judgment; if the capacity judgment of the primary serving cell is abnormal, it is obtained that the capacity of the primary serving cell is abnormal; and/or the coverage parameters of the primary serving cell are acquired, and the Perform coverage judgment on the primary serving cell; if the coverage judgment of the primary serving cell is abnormal, obtain weak coverage or overlapping coverage of the primary serving cell.
  • the capacity parameter includes the maximum number of activated users of the primary serving cell, uplink traffic, downlink traffic, uplink PRB utilization rate, downlink PRB utilization rate, and the like. If the maximum number of activated users in the primary serving cell is too high, a second root cause is obtained, that is, the maximum number of activated users in the primary serving cell is too high; if the uplink traffic of the primary serving cell is large, a second root cause is obtained, which is The uplink traffic of the primary serving cell is too large; if the downlink traffic of the primary serving cell is large, the second root cause of excessive downlink traffic of the primary serving cell is obtained; if the uplink PRB utilization rate of the primary serving cell is high, a second root cause is obtained , the uplink PRB utilization rate of the primary serving cell is high; if the downlink PRB utilization rate of the primary serving cell is high, a second root cause is obtained, that is, the downlink PRB utilization rate of the primary serving cell is high.
  • the coverage parameter includes the rsrp (Reference Signal Received Power) value of the primary serving cell.
  • rsrp Reference Signal Received Power
  • the step of performing anomaly detection on the primary serving cell and obtaining the second root cause corresponding to the primary serving cell may include: performing interference judgment on the primary serving cell, if there is interference in the primary serving cell, It is obtained that there is interference in the primary serving cell.
  • the abnormality detection is performed on the primary serving cell
  • the step of obtaining the second root cause corresponding to the primary serving cell may include performing alarms on the primary serving cell, abnormality detection of changes in bearer links and base station configuration parameters , the specific detection content is the same as the above-mentioned abnormality detection process of alarming the serving cell in the serving cell group, and changing the bearer link and base station configuration parameters, and will not be repeated here.
  • the obtained multiple second root causes may be output, or the priority of each second root cause may be Different selection priority is higher as the second root cause of the final output.
  • the priority can be over coverage>alarm>bearer link abnormality>weak coverage>overlapping coverage>interference>configuration parameter change>capacity, among which, the priority of out of service alarms is higher than that of non out of service alarms class.
  • the root cause location method provided in the above embodiment obtains the main serving cell where the service is abnormal, determines the grid corresponding to the main serving cell, and then expands the grid to obtain the grid group and the serving cell group corresponding to the grid group, Finally, anomaly detection is performed on the serving cell group and the main serving cell, so as to obtain the root cause of the abnormal business. Not only the automatic root cause location is realized, but also the service cell group is obtained through expansion, and the anomaly detection of the service cell group also improves the comprehensiveness of the root cause.
  • FIG. 3 is a schematic flow chart of implementing the root cause location method provided by the present application.
  • pause_duration is 3600ms, that is, the waiting time for video service playback is 3600ms, which exceeds the preset index threshold. Therefore, it can be determined that this user-side call ticket is an abnormal call ticket, and the root cause of the service exception needs to be checked for the abnormal call ticket position.
  • the preset offset time is 2 minutes, then the wireless data within 2 minutes before and after the time 2021-04-22 12:35:09.883 can be extracted, as shown in Figure 5, which is a schematic diagram of the extracted wireless data.
  • the wireless data includes the cell ⁇ gnb_length_ran, gnbid_ran, cellid_ran> and the corresponding grid ⁇ regionid, x_offset, y_offset>.
  • the grid position corresponding to the main serving cell can be obtained as ⁇ 4736, -6125, 872 >.
  • the grid is expanded based on the grid to obtain the grid group, and the serving cell group corresponding to the grid group is determined, and finally the serving cell group is obtained as ⁇ serving cell 1, serving cell 2, serving cell 3 ⁇ .
  • the serving cell group is traversed, and whether the bearer links of the three serving cells in the serving cell group are abnormal is judged respectively.
  • BigDNA reports the correspondence between the base station ⁇ gnb_length, gnbid> and the bearer link bearer_link, and the link parameters of the bearer link bearer_link. From this, it can be obtained that the bearer link "SAW0038 to CN" corresponding to serving cell 3 has too large jitter variationdelay.
  • the third-party Mongoose can provide the current value and suggested value of the base station parameter configuration, and no parameter configuration change is found.
  • the first root cause of the service abnormality can be obtained.
  • the first root cause obtained includes ⁇ there is a base station out-of-service alarm in the serving cell 2, and the bearer link corresponding to the serving cell 3" SAW0038 to CN" has a jitter delay variationdelay is too large ⁇ .
  • the primary serving cell is the serving cell 1, and the primary serving cell is in the serving cell group at this time, the primary serving cell is not an over-coverage cell. And because the primary serving cell is in the serving cell group, it means that when the abnormality detection is performed on the serving cell group, the abnormality detection is also performed on the serving cell 1, so there is no need to perform alarms, bearer links, and base station configurations on the primary serving cell Abnormal detection of parameter changes, that is, it can be directly concluded that there is no alarm in the main serving cell; there is no bearer link problem in the main serving cell; there is no parameter configuration change in the main serving cell.
  • the main serving cell carry out coverage detection, interference detection, and capacity detection on the main serving cell, and it can be concluded that the current rsrp value of the main serving cell is -120, and there is weak downlink coverage; the main serving cell does not have interference problems; the main serving cell does not exist Capacity problem; there is no parameter configuration change problem in the main serving cell 1.
  • the second root cause of the service abnormality can be obtained, and the obtained second root cause includes ⁇ weak coverage exists in the primary serving cell 1 ⁇ .
  • the first root cause determined by the serving cell group and the second root cause determined according to the primary serving cell are output as the final determined root cause of the business anomaly, including: ⁇ Serving cell 2 has a base station out-of-service alarm, and serving cell 3
  • the corresponding bearer link "SAW0038 to CN" has too large jitter variationdelay, and the main serving cell 1 has weak coverage ⁇ .
  • FIG. 6 is another schematic flowchart for implementing the root cause location method provided by the present application.
  • the user-side bill collected from the N3 port is read, as shown in FIG. 7 , which is a schematic diagram of another read user-side bill.
  • the buffer_duration is 5868ms, that is, the video service buffering duration is 5868ms, which exceeds the preset index threshold. Therefore, it can be determined that this user-side call ticket is an abnormal call ticket, and the root cause of the service abnormality needs to be located for the abnormal call ticket. .
  • the preset offset time is 2 minutes, then the wireless data within 2 minutes before and after the time 2021-04-20 18:43:56.788 can be extracted, as shown in Figure 8, which is a schematic diagram of another extracted wireless data.
  • the wireless data includes the cell ⁇ bnb_length_ran, gnbid_ran, cellid_ran> and the corresponding grid ⁇ regionid, x_offset, y_offset>.
  • the grid position corresponding to the main serving cell can be obtained as ⁇ 4755, -6135, 889 >.
  • the grid is expanded based on the grid to obtain a grid group, and the serving cell group corresponding to the grid group is determined, and finally the serving cell group is obtained as ⁇ serving cell 2, serving cell 3, and serving cell 4 ⁇ .
  • serving cell 3 Traverse the serving cell group, and judge the alarms of the three serving cells in the serving cell group respectively, judge whether there are alarms in the three serving cells, and if there is an alarm, determine the alarm period of the serving cell and judge the time when the business occurs Whether it is within the warning period. Then it is obtained that serving cell 3 reported a network element disconnection alarm before 2021-04-20 18:43:56.788, and the two cells of serving cell 1 and serving cell 2 had no alarm information.
  • the serving cell group is traversed, and whether the bearer links of the three serving cells in the serving cell group are abnormal is judged respectively.
  • BigDNA reports the corresponding relationship between the base station ⁇ gnb_length, gnbid> and the bearer link bearer_link, and the link parameters of the bearer link bearer_link. From this, it can be obtained that the bearer link "SAW0055 to CN" corresponding to serving cell 2 has an excessive packet loss rate.
  • the third-party Mongoose can provide the current value and suggested value of the base station parameter configuration, and no parameter configuration change is found.
  • the first root cause of the business abnormality can be obtained.
  • the first root cause obtained includes ⁇ serving cell 3 reported before 2021-04-20 18:43:56.788 NE link disconnection alarm, the bearer link "SAW0055 to CN" corresponding to serving cell 2 has an excessive packet loss rate ⁇ .
  • the primary serving cell is the serving cell 1
  • the primary serving cell is not in the serving cell at this time, therefore, the primary serving cell 1 has over-coverage. Then, the primary serving cell 1 is sequentially inspected for alarm, bearer link, coverage detection, interference detection, capacity detection, and base station configuration parameter change. , the obtained second root cause includes ⁇ primary serving cell 1 currently has overcoverage ⁇ .
  • the first root cause determined by the serving cell group and the second root cause determined according to the main serving cell are output as the final determined root cause of the business anomaly, including: ⁇ serving cell 3 at 2021-04-20 18:43 : 56.788 hours ago, a network element disconnection alarm was reported, the bearer link "SAW0055 to CN" corresponding to serving cell 2 had an excessive packet loss rate, and the main serving cell 1 was currently over-covered ⁇ .
  • FIG. 9 is a schematic structural block diagram of a root cause location device provided in the present application.
  • the root cause location device 200 includes a processor 201 and a memory 202, and the processor 201 and the memory 202 are connected through a bus 203, such as an I2C (Inter-integrated Circuit) bus.
  • a bus 203 such as an I2C (Inter-integrated Circuit) bus.
  • the processor 201 is used to provide computing and control capabilities to support the operation of the entire root cause location device.
  • the processor 301 can be a central processing unit (Central Processing Unit, CPU), and the processor 301 can also be other general processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC) ), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory 202 may be a Flash chip, a read-only memory (ROM, Read-Only Memory) disk, an optical disk, a U disk, or a mobile hard disk.
  • FIG. 9 is only a block diagram of a part of the structure related to the embodiment of the present application, and does not constitute a limitation on the root cause locating device to which the embodiment of the present application is applied.
  • a particular server may include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.
  • the processor is configured to run a computer program stored in the memory, and implement any one of the root cause location methods provided in the embodiments of the present application when executing the computer program.
  • the processor is configured to run a computer program stored in the memory, and implement the following steps when executing the computer program:
  • the processor when the processor implements the determination of the grid corresponding to the primary serving cell, it is configured to:
  • the wireless data includes cells where business abnormalities occur and the grid where business abnormalities occur; A grid corresponding to the primary serving cell is determined.
  • the processor when the processor implements the abnormality detection on the serving cell group and the primary serving cell to obtain the root cause of the abnormal service, it is used to realize:
  • Anomaly detection is performed on the serving cells in the serving cell group to obtain a first root cause corresponding to the serving cell group; anomaly detection is performed on the primary serving cell to obtain a second root cause corresponding to the primary serving cell.
  • the processor when the processor implements the abnormal detection of the serving cells in the serving cell group to obtain the first root cause corresponding to the serving cell group, it is used to realize:
  • the processor when the processor realizes the abnormal detection of the serving cells in the serving cell group and obtains the first root cause corresponding to the serving cell group, it is used to realize:
  • the link parameters of the bearer links of the serving cells in the serving cell group and determine whether the bearer links are abnormal according to the link parameters; if the bearer links of the serving cells in the serving cell group exist Abnormal, it is obtained that the bearer link of the serving cell is abnormal.
  • the processor when the processor implements the abnormal detection of the serving cells in the serving cell group to obtain the first root cause corresponding to the serving cell group, it is used to realize:
  • the processor when the processor implements the abnormality detection on the primary serving cell and obtains the second root cause corresponding to the primary serving cell, it is used to realize:
  • the processor when the processor implements the abnormality detection on the primary serving cell and obtains the second root cause corresponding to the primary serving cell, it is used to realize:
  • the embodiments of the present application also provide a storage medium for computer-readable storage, the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the following: The steps of any one of the root cause location methods provided in the description of the embodiments of the present application.
  • the storage medium may be an internal storage unit of the root cause locating device described in the foregoing embodiments, such as a hard disk or a memory of the root cause locating device.
  • the storage medium may also be an external storage device of the root cause locating device, such as a plug-in hard disk equipped on the root cause locating device, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, flash memory card (Flash Card), etc.
  • the functional modules/units in the system, and the device can be implemented as software, firmware, hardware, and an appropriate combination thereof.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical components. Components cooperate to execute.
  • Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit .
  • Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
  • computer storage media includes both volatile and nonvolatile media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. permanent, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer.
  • communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施方式提供一种根因定位方法、根因定位设备及存储介质，属于无线通讯领域。该方法包括：获取发生业务异常的主服务小区，并确定所述主服务小区对应的栅格；对所述栅格进行扩展得到栅格组，并确定所述栅格组对应的服务小区组；对所述服务小区组和所述主服务小区进行异常检测，得到发生业务异常的根因。

Description

根因定位方法、根因定位设备及存储介质
相关申请的交叉引用
本申请要求2021年8月27日提交给中国专利局的第202110998597.3号专利申请的优先权，其全部内容通过引用合并于此。
技术领域
本申请涉及但不限于通信技术领域。
背景技术
随着LTE(Long Term Evolution，长期演进)的普及以及5G SA(Stand Alone)的积极建设，终端已经成为人们生活中必不可少的产品，并且随着视频、游戏业务的蓬勃发展，人们对于终端数据业务的要求也越来越高。但随着用户对于终端数据业务的使用频率的增加，随之而来的就是大量的用户投诉工单。在用户投诉工单中，无线的问题的占比较高，因此，需要对无线小区进行根因定位，确定出现问题的原因，以进行改进。
发明内容
本申请提供一种根因定位方法、根因定位设备及存储介质。
第一方面，本申请提供一种根因定位方法，包括：获取发生业务异常的主服务小区，并确定所述主服务小区对应的栅格；对所述栅格进行扩展得到栅格组，并确定所述栅格组对应的服务小区组；对所述服务小区组和所述主服务小区进行异常检测，得到发生业务异常的根因。
第二方面，本申请还提供一种根因定位设备，所述根因定位设备包括处理器、存储器、存储在所述存储器上并可被所述处理器执行的计算机程序以及用于实现所述处理器和所述存储器之间的连接通信的数据总线，其中所述计算机程序被所述处理器执行时，实现如本文 描述的任一项根因定位方法的步骤。
第三方面，本申请还提供一种存储介质，用于计算机可读存储，所述存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现如本文描述的任一项根因定位方法的步骤。
附图说明
图1为本申请提供的一种根因定位方法的流程示意图；
图2为本申请提供的对栅格进行扩展后得到的栅格组的范围示意图；
图3为本申请提供的根因定位方法的一个流程示意图；
图4为本申请提供的读取到的用户面话单的示意图；
图5为本申请提供的提取的无线数据的示意图；
图6为本申请提供的根因定位方法的另一个流程示意图；
图7为本申请提供的读取到的另一用户面话单的示意图；
图8为本申请提供的提取的另一无线数据的示意图；
图9为本申请提供的一种根因定位设备的结构示意性框图。
具体实施方式
下面将结合本申请实施方式中的附图，对本申请实施方式中的技术方案进行清楚、完整地描述，显然，所描述的实施方式是本申请一部分实施方式，而不是全部的实施方式。基于本申请中的实施方式，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施方式，都属于本申请保护的范围。
附图中所示的流程图仅是示例说明，不是必须包括所有的内容和操作/步骤，也不是必须按所描述的顺序执行。例如，有的操作/步骤还可以分解、组合或部分合并，因此实际执行的顺序有可能根据实际情况改变。
应当理解，在此本申请说明书中所使用的术语仅仅是出于描述特定实施方式的目的而并不意在限制本申请。如在本申请说明书和所 附权利要求书中所使用的那样，除非上下文清楚地指明其它情况，否则单数形式的“一”、“一个”及“该”意在包括复数形式。
随着LTE的普及以及5G SA的积极建设，手机成为人们精神生活中必不可少的核心因素，人们对手机数据业务的要求也越来越高。随着运营商推出的不限流量套餐的盛行，数据业务发展的更为庞大，除了传统的网页浏览业务外，视频、游戏业务的使用量激增，伴随着业务的增长，体验要求的提高，用户投诉问题也随之增加。在用户投诉的问题根因中，无线的问题占比较高，传统的无线定位手段耗时耗力，大量投诉工单亟需快速解决。
为此，本申请实施方式提供一种根因定位方法、根因定位设备及存储介质。其中，该根因定位方法可应用于移动终端中，该移动终端可以手机、平板电脑、笔记本电脑、台式电脑、个人数字助理和穿戴式设备等电子设备。本申请实施方式的技术方案至少能够实现自动的根因定位以及得到根因的全面性。
下面结合附图，对本申请的一些实施方式作详细说明。在不冲突的情况下，下述的实施方式及实施方式中的特征可以相互组合。
图1为本申请提供的一种根因定位方法的流程示意图。
如图1所示，在一个实施方式中，该根因定位方法包括步骤S101至步骤S103。
步骤S101、获取发生业务异常的主服务小区，并确定所述主服务小区对应的栅格。
当发生业务行为异常时，首先获取发生业务行为异常的主服务小区。例如在5G SA组网中，通过在无线基站与核心网5GC(5G Core Network)的用户面功能网元UPF(User Plane Function)之间部署探针probe，采集用户面的原始信令，即可得到用户面话单，用户面话单中包括了业务行为发生的小区。
在一些示例性实施方式中，可以将采集到的用户面话单格式化为如下数据结构data_cn：
Figure PCTCN2022109896-appb-000001
其中，数据结构中数据的含义分别为：
<imsi，msisdn>可唯一标志一个用户信息，<starttime>表示该业务的开始时间，<gnb_length，gnbid，cellid>表示该业务发生的5G小区，<ulflux，dlflux>表示该业务的上下行流量，<duration>表示该业务的持续时长，<ultimeusage，dltimeusage>表示该业务的上下行实际发生业务时长，<pause_duration>表示视频业务播放等待时长，<buffer_duration>表示视频业务缓冲时长，<pause_cnt>表示视频业务卡顿次数。
因此，通过用户面话单中的<gnb_length，gnbid，cellid>即可确定发生业务行为异常的主服务小区。在得到主服务小区后，还需要确定该主服务小区所对应的栅格。在一些示例性实施方式中，栅格可以是预先规划好的，例如对省或市的地图进行划分，将地图划分为多个相同大小的栅格，比如将地图划分为50cm*50cm的栅格。
在一实施方式中，确定主服务小区对应的栅格的步骤可以包括：获取发生业务异常的无线数据，所述无线数据包括发生业务异常的小区数据和所述发生业务异常的栅格数据；根据所述主服务小区、所述业务异常的小区数据和所述发生业务异常的栅格数据确定所述主服务小区对应的栅格。
在获取用户面话单后，根据用户面话单中的<starttime>即可确定发生异常的业务行为的开始时间，然后可以根据该发生异常的业务行为的开始时间来获取相应时刻的无线数据。由于无线数据中包括了发生业务异常的小区以及发生业务异常的栅格，因此，在得到无线数据后，即可根据确定出的主服务小区、无线数据中发生业务异常的小区以及发生业务异常的栅格来确定主服务小区所对应的栅格。若主服务小区与发生异常的小区为同一个小区，则可以认为主服务小区所对应的栅格即为无线数据中发生业务异常的栅格。
在一些示例性实施方式中，在获取发生业务异常的无线数据时，可以仅根据用户面话单中的<starttime>获取相应时刻的无线数据，但考虑到基站和无线侧之间的时间差，还可以获取在预设偏移时间内的无线数据。例如，若根据用户面话单中的<starttime>确定发生异常的业务行为的开始时间为2021-04-22 12：35：09.883，且预设偏移时间为 2分钟，那么在获取无线数据时，可以获取从2021-04-22 12：33：09.883至2021-04-22 12：37：09.883之间的无线数据。可以理解的是，预设偏移时间是一个经验值，可以根据实际应用情况进行修改。
另外，也可以将采集到的无线数据进行格式化，得到如下数据结构data_ran：
Figure PCTCN2022109896-appb-000002
其中，数据结构中数据的含义分别为：
<msi_ran，msisdn_ran>可唯一标志一个用户信息，<starttime_ran>表示该业务的开始时间，<gnb_length_ran，gnbid_ran，cellid_ran>表示该业务发生的小区，<ssb_rsrp>表示该小区的ssb_rsrp值，<regionid，x_offset，y_offset>表示该业务所处的栅格，<ssb_rsrq>表示该小区的ssb_rsrq值，<is_dlweakcover>表示当前小区是否是弱覆盖小区，<pci>表示小区物理标志，<avgrip>表示RIP(Received Interference Power，接收干扰功率)均值，<isrrcuser_overload>表示是否最大激活用户数过高，<isdlprb_overload>表示是否下行prb(Physical Resource Block，物理资源块)利用率过高，<isulprb_overload>表示是否上行prb利用率过高。
在一实施方式中，在得到无线数据后，还可以根据无线数据中发生业务异常的小区，将无线数据与用户面话单进行关联，然后将无线数据中表示栅格的<regionid，x_offset，y_offset>数据回填至用户面扩展话单中。
例如，在将无线数据与用户面话单数据进行关联时的关联条件可以是：
用户面话单中的data_cn.imsi相当于无线数据中的data_ran.imsi_ran，用户面话单中的data_cn.gnb_length相当于无线数据中的data_ran.gnb_length_ran，用户面话单中的data_cn.gnbid相当于无线数据中的data_ran.gnbid_ran，用户面话单中的data_cn.cellid相当于用户面话单中的data_ran.cellid，以及ABS(data_cn.starttime+data_cn.duration/2-data_ran.starttime_ran)< 120。
在一实施方式中，该根因定位方法还可以包括：获取用户面话单，所述用户面话单中包括话单质量参数和小区；若根据所述话单质量参数确定所述用户面话单为异常话单，则将所述小区作为发生业务异常的主服务小区。
由于用户面话单中包括话单质量参数，可以根据用户面话单中的话单质量参数来确定当前获取的用户面话单是否为异常话单，其中，异常话单可以是业务感知较差的话单。在一些示例性实施方式中，若话单质量参数所对应的参数值超过了预设指标门限，则可以认为当前的用户面话单为异常话单，那么该异常话单中的小区即为发生业务异常的主服务小区。
其中，话单质量参数可以包括视频播放时长、视频业务缓冲时长和视频业务卡顿次数中的至少一种，当任意一种话单质量参数所对应的参数值大于其对应的预设指标门限时，则可以认为当前的用户面话单为异常话单，需要对该异常话单进行根因定位。
步骤S102、对所述栅格进行扩展得到栅格组，并确定所述栅格组对应的服务小区组。
在确定发生业务异常的栅格后，基于该栅格进行栅格扩展，得到栅格组。在一些示例性实施方式中，在进行扩展时，可以以当前发生业务异常的栅格为中心，分别向四个象限进行扩展，扩展的范围可以根据经验值设置。例如可以向外扩展3个栅格，如图2所示，为扩展后得到的栅格组的范围示意图，图中标五角星的为发生业务异常的栅格，其余栅格则是以该发生业务异常的栅格为中心进行扩展得到的，将这些扩展出的栅格和发生业务异常的栅格作为栅格组，当栅格为50cm*50cm时，扩展后的栅格组的大小即为350cm*350cm。
在得到栅格组后，即可根据栅格和小区原始规划文件，来确定出栅格组中的各个栅格分别对应的服务小区，从而得到服务小区组。在确定栅格所对应的服务小区时，不同的多个栅格可能会对应同一个服务小区，同一个栅格也可能会对应不同的服务小区。
在一些示例性实施方式中，可以将栅格与服务小区的对应关系 格式化描述为：
Figure PCTCN2022109896-appb-000003
其中，<regionid_n，x_offset_n，y_offset_n>表示栅格位置，<gnb_length_n，gnb_id_n，cellid_n>表示服务小区的位置，<regionid_n，x_offset_n，y_offset_n，gnb_length_n，gnb_id_n，cellid_n>表示位置为<regionid_n，x_offset_n，y_offset_n>的栅格对应的服务小区是<gnb_length_n，gnb_id_n，cellid_n>。
例如，若标记当前发生业务异常的栅格为栅格0，其位置表示为<regionid_0，x_offset_0，y_offset_0>，那么在向相邻方向扩展三个栅格后，得到的扩展栅格组中共包括49个栅格，分别可以表示为：
Figure PCTCN2022109896-appb-000004
基于此，可以确定栅格组中的这49个栅格中，每个栅格所对应的服务小区为：
Figure PCTCN2022109896-appb-000005
然后得到栅格组所对应的服务小区的集合，为：
Figure PCTCN2022109896-appb-000006
在得到服务小区的集合后，可以对服务小区集合中的小区进行去重处理，将去重后的服务小区集合作为栅格组对应的服务小区组，得到的服务小区组为：
Figure PCTCN2022109896-appb-000007
步骤S103、对所述服务小区组和所述主服务小区进行异常检测，得到发生业务异常的根因。
在确定出服务小区组和主服务小区后，此时即可对服务小区组和主服务小区进行异常检测，进行根因定位，从而得出发生业务异常的根因。
在一实施方式中，所述对所述服务小区组和所述主服务小区进行异常检测，得到发生业务异常的根因的步骤可以包括：对所述服务小区组中的服务小区进行异常检测，得到所述服务小区组对应的第一根因；对所述主服务小区进行异常检测，得到所述主服务小区对应的第二根因。
服务小区组中包括多个服务小区，遍历服务小区组中的各个服务小区，对服务小区组中的所有的服务小区均进行异常检测，从而得到服务小区组所对应的第一根因，并且，对主服务小区也进行异常检测，得到主服务小区对应的第二根因。集合第一根因和第二根因，得到发生业务异常的根因。
需要说明的是，由于主服务小区是发生业务异常的小区，因此，主服务小区的异常检测的检测内容可以与服务小区组中的服务小区的异常检测的检测内容有所不同。
在一些示例性实施方式中，在进行异常检测时可能会得到多个第一根因或多个第二根因，可以将得到的所有第一根因或第二根因都做为根因进行输出，也可以从第一根因或第二根因中按照优先级的不同进行选择，将选出的第一根因和第二根因进行输出。例如可以选择优先级靠前的TOP2或TOP5。
在一实施方式中，对所述服务小区组中的服务小区进行异常检测，得到所述服务小区组对应的第一根因的步骤可以包括：获取所述服务小区组中的服务小区的告警时刻，并确定业务异常的发生时刻是否在所述告警时段内；若所述业务异常的发生时刻在所述告警时段内，则得到所述服务小区存在告警。
遍历服务小区组中的每一个服务小区，分别对服务小区组中的每一个服务小区都进行告警类判断，当服务小区出现告警，且业务异常的发生时刻在告警时段内时，可以得到一个第一根因，为该服务小区出现告警。其中，业务异常的发生时刻可以根据用户面话单中的<starttime>来确定。
在一些示例性实施方式中，告警分为退服类告警和非退服类告警。其中，退服类告警可以包括服务小区退服、基站退服、服务小区关区关断以及设备掉电等，非退服类告警则可以包括网元断链告警、基站同步异常、无线干扰检测异常、没有可用的空口时钟源以及天馈链路故障等。
对于退服类告警，主要是在告警发生时刻会对业务产生影响，由于本该附着的基站发生退服导致业务附着到其他基站而发生质差，考虑时间偏差，认为退服前后一段时间内会对业务产生影响，业务发生与告警发生的关联时间关系如下：
service_starttime∈[alarm_starttime-Δt，alarm_starttime+Δt]
其中，service_starttime表示业务发生时刻，alarm_starttime表示告警发生时刻，Δt表示时间偏差，[alarm_starttime-Δt，alarm_starttime+Δt]表示告警时段。
而对于非退服类告警，告警只要存在就会对业务产生影响，业务开始时间只要在告警发生到清除时间范围内则都归因为告警对业务的影响，业务发生与告警发生的关联时间关系如下：
service_starttime∈[alarm_starttime，alarm_cleartime]
其中，service_starttime表示业务发生时刻，alarm_starttime表示告警发生时刻，alarm_cleartime表示告警清除时刻，[alarm_starttime，alarm_cleartime]表示告警时段。
无论是退服类告警，还是非退服类告警，只要业务异常的发生时刻在告警时段内，则可以认为该服务小区的告警对业务的正常进行产生了影响，即可得到一个第一根因，为服务小区存在告警。
在一实施方式中，对所述服务小区组中的服务小区进行异常检测，得到所述服务小区组对应的第一根因的步骤可以包括：获取所述 服务小区组中服务小区的承载链路的链路参数，并根据所述链路参数确定所述承载链路是否存在异常；若所述服务小区组中的服务小区的承载链路存在异常，得到所述服务小区出现承载链路异常。
遍历服务小区组中的每一个服务小区，分别获取服务小区组中的每一个服务小区的承载链路的链路参数，以根据链路参数对承载链路进行异常判断。当服务小区组中有服务小区的承载链路发生异常时，即可得到一个第一根因，为服务小区的承载链路异常。
在一些示例性实施方式中，可以通过发射端网元ME_OID、发射端端口InBoundInf、反射端网元ReflectorMe和反射端端口ReflectorPort来唯一标志一段承载链路,承载链路可以记为hearer_link。然后获取承载链路的链路参数，其中，链路参数可以包括抖动、时延和丢包率中的至少一种。当链路参数中的至少一种超过对应的预设门限值时，则可以认为该承载链路存在异常，可以得到一个第一根因，为服务小区出现承载链路异常。另外，在得到该第一根因时，可以同时给出出现异常的具体链路，以及出现异常的链路参数。
在一实施方式中，对所述服务小区组中的服务小区进行异常检测，得到所述服务小区组对应的第一根因的步骤可以包括：获取所述服务小区组中服务小区对应基站的配置参数和参考参数；若所述配置参数和所述参考参数不一致，得到所述基站发生配置参数变更。
可以借助第三方软件来获取基站当前的配置参数和参考参数，参考参数也即建议值，当当前的配置参数与参考参数不同时，则可以认为该基站有参数上的配置变更，也即得到一个第一根因，为基站发生配置参数变更。
在一实施方式中，在对服务小区组中的服务小区进行异常检测，得到了多种第一根因时，可以将得到的多个第一根因进行输出，还可以按照每种第一根因的优先级的不同选择优先级更靠前的作为最终输出的第一根因。其中，优先级可以是告警>承载链路异常>配置参数变更，其中，告警中退服类告警的优先级又高于非退服类告警的优先级。
在一实施方式中，当服务小区组中有多个服务小区都存在同一 优先级的第一根因时，可以从这多个服务小区中选择离主服务小区对应的栅格最近的小区作为输出。
在一实施方式中，对所述主服务小区进行异常检测，得到所述主服务小区对应的第二根因的步骤可以包括：确定所述服务小区组是否包括所述主服务小区；若所述服务小区组不包括所述主服务小区，得到所述主服务小区过覆盖。
在对主服务小区进行异常检测时，确定服务小区组中是否包括主服务小区，通常情况下，服务小区组内应该包括主服务小区，但若主服务小区出现过覆盖，则可能会出现主服务小区不再服务小区组内的情况，因此，可以判断服务小区组中是否包括主服务小区，来确定主服务小区是否出现过覆盖。若主服务小区不在服务小区组内，也即服务小区组中不包括主服务小区，则认为主服务小区出现过覆盖，可以得到一个第二根因，为主服务小区出现过覆盖。
在一实施方式中，对所述主服务小区进行异常检测，得到所述主服务小区对应的第二根因的步骤可以包括：获取所述主服务小区的容量参数，并根据所述容量参数对所述主服务小区进行容量判断；若所述主服务小区的容量判断异常，得到所述主服务小区容量异常；和/或获取所述主服务小区的覆盖参数，并根据所述覆盖参数对所述主服务小区进行覆盖判断；若所述主服务小区的覆盖判断异常，得到所述主服务小区弱覆盖或重叠覆盖。
其中，容量参数包括主服务小区的最大激活用户数、上行流量、下行流量、上行PRB利用率和下行PRB利用率等。若主服务小区的最大激活用户数过高，则得到一个第二根因，为主服务小区存在最大激活用户数过高；若主服务小区的上行流量大，则得到一个第二根因，为主服务小区上行流量过大；若主服务小区的下行流量大，则得到主服务小区下行流量过大的第二根因；若主服务小区的上行PRB利用率高，则得到一个第二根因，为主服务小区的上行PRB利用率高；若主服务小区的下行PRB利用率高，则得到一个第二根因，为主服务小区的下行PRB利用率高。
其中，覆盖参数包括主服务小区的rsrp(Reference Signal  Received Power参考信号接收功率)值。在对主服务小区进行覆盖判断时，可以根据主服务小区的rsrp值来判断该主服务小区是否属于弱覆盖；通过主服务小区的rsrp值与相邻小区的rsrp值的差值来判断该主服务小区是否存在重叠覆盖。
在一实施方式中，对所述主服务小区进行异常检测，得到所述主服务小区对应的第二根因的步骤可以包括：对所述主服务小区进行干扰判断，若主服务小区存在干扰，得到主服务小区存在干扰。
在一实施方式中，对所述主服务小区进行异常检测，得到所述主服务小区对应的第二根因的步骤可以包括对主服务小区进行告警、承载链路和基站配置参数变更的异常检测，具体检测内容与前述对服务小区组中的服务小区进行告警、承载链路和基站配置参数变更的异常检测的过程相同，在此不再赘述。
在一实施方式中，在对主服务小区进行异常检测，得到多种第二根因后，可以将得到的多个第二根因进行输出，也可以按照每种第二根因的优先级的不同选择优先级更靠前的作为最终输出的第二根因。其中，优先级可以是过覆盖>告警>承载链路异常>弱覆盖>重叠覆盖>干扰>配置参数变更>容量，其中，告警中退服类告警的优先级又高于非退服类告警的优先级。
在得到第一根因和第二根因后，将需要输出的第一根因和需要输出的第二根因的集合进行输出，即为最终得到的导致业务行为发生异常的根因。
上述实施方式提供的根因定位方法，通过获取发生业务异常的主服务小区，并确定主服务小区对应的栅格，然后对栅格进行扩展得到栅格组以及栅格组对应的服务小区组，最终对服务小区组和主服务小区分别进行异常检测，从而得到发生业务异常的根因。不仅实现了自动的根因定位，并且通过扩展得到服务小区组，对服务小区组也进行异常检测也提高了得到根因的全面性。
请参照图3，图3为实施本申请提供的根因定位方法的一个流程示意图。
首先读取到从N3口采集到的用户面话单，如图4所示，为读取 到的用户面话单的示意图。其中，pause_duration为3600ms，也即视频业务播放等待时长为3600ms,超出了预先设置的指标门限，因此可以确定该条用户面话单为异常话单，需要对该异常话单进行业务异常的根因定位。
如图3所示，首先提取出话单中的<imsi,gnb_length,gnbid>，可以确定出发生业务异常的用户4604092003197015所处的服务小区为服务小区1，服务小区1也即主服务小区，以及发生异常的业务行为的开始时间为2021-04-22 12:35:09.883。
预设偏移时间为2分钟，那么可以提取时间2021-04-22 12:35:09.883前后2min范围内的无线数据，如图5所示，为提取的无线数据的示意图。无线数据中包括小区<gnb_length_ran,gnbid_ran,cellid_ran>和对应的栅格<regionid,x_offset,y_offset>，根据无线数据中的小区，可以得到主服务小区对应的栅格位置为<4736,-6125,872>。然后基于该栅格进行栅格扩展得到栅格组，并确定栅格组对应的服务小区组，最终得到服务小区组为{服务小区1、服务小区2、服务小区3}。
遍历该服务小区组，分别对服务小区组中的三个服务小区进行告警判断，分别判断这三个服务小区是否有告警，若有告警，则确定服务小区的告警时段，并判断业务发生的时间是否在告警时段内。进而得到服务小区2在2021-04-22 12:33:09.883--2021-04-22 12:37:09.883范围内有上报基站退服告警，服务小区1和服务小区3这两个小区无告警信息。
然后遍历该服务小区组，分别判断服务小区组中的三个服务小区的承载链路是否存在异常。可以借助第三方BigDNA提供的基站IP与承载网链路对应关系以及承载链路上的链路参数来判断承载链路是否存在异常。BigDNA上报基站<gnb_length，gnbid>与承载链路bearer_link的对应关系，以及承载链路bearer_link的链路参数。由此可以得到服务小区3对应的承载链路“SAW0038 to CN”存在抖动时延variationdelay过大。
然后遍历该服务小区组，分别对服务小区组中的三个服务小区 所对应的基站进行配置参数变更的判断，可以借助第三方Mongoose提供基站参数配置当前值和建议值，发现无参数配置变更。
在对上述的服务小区组异常检测完成后，即可得到发生业务异常的第一根因，得到的第一根因包括{服务小区2存在基站退服告警，服务小区3对应的承载链路“SAW0038 to CN”存在抖动时延variationdelay过大}。
由于主服务小区为服务小区1，此时主服务小区在服务小区组内，因此，主服务小区不是过覆盖小区。并且由于主服务小区在服务小区组内，意味着在对服务小区组进行异常检测时，也对服务小区1进行了异常检测，因此，无需再对主服务小区进行告警、承载链路和基站配置参数变更的异常检测，也即可以直接得出主服务小区不存在告警判断；主服务小区不存在承载链路问题；主服务小区不存在参数配置变更问题。
然后对主服务小区进行覆盖类检测、干扰类检测和容量类检测，可以得出由于主服务小区当前rsrp值为-120，存在下行弱覆盖；主服务小区不存在干扰问题；主服务小区不存在容量问题；主服务小区1不存在参数配置变更问题。
在对主服务小区异常检测完成后，即可得到发生业务异常的第二根因，得到的第二根因包括{主服务小区1存在弱覆盖}。
最终将服务小区组确定的第一根因以及根据主服务小区确定的第二根因作为最终确定的发生业务异常的根因进行输出，包括：{服务小区2存在基站退服告警，服务小区3对应的承载链路“SAW0038 to CN”存在抖动时延variationdelay过大，主服务小区1存在弱覆盖}。
请参照图6，图6为实施本申请提供的根因定位方法的另一个流程示意图。
首先读取到从N3口采集到的用户面话单，如图7所示，为读取到的另一用户面话单的示意图。其中，buffer_duration为5868ms，也即视频业务缓冲时长为5868ms,超出了预先设置的指标门限，因此可以确定该条用户面话单为异常话单，需要对该异常话单进行业务异 常的根因定位。
如图6所示，首先提取出话单中的<imsi,gnb_length,gnbid>，可以确定出发生业务异常的用户4604092003197888所处的服务小区为服务小区1，服务小区1也即主服务小区，以及发生异常的业务行为的开始时间为2021-04-20 18:43:56.788。
预设偏移时间为2分钟，那么可以提取时间2021-04-20 18:43:56.788前后2min范围内的无线数据，如图8所示，为提取的另一无线数据的示意图。无线数据中包括小区<bnb_length_ran,gnbid_ran,cellid_ran>和对应的栅格<regionid,x_offset,y_offset>，根据无线数据中的小区，可以得到主服务小区对应的栅格位置为<4755，-6135，889>。然后基于该栅格进行栅格扩展得到栅格组，并确定栅格组对应的服务小区组，最终得到服务小区组为{服务小区2、服务小区3、服务小区4}。
遍历该服务小区组，分别对服务小区组中的三个服务小区进行告警判断，分别判断这三个服务小区是否有告警，若有告警，则确定服务小区的告警时段，并判断业务发生的时间是否在告警时段内。进而得到服务小区3在2021-04-20 18:43:56.788的时间前有上报网元断链告警，服务小区1和服务小区2这两个小区无告警信息。
然后遍历该服务小区组，分别判断服务小区组中的三个服务小区的承载链路是否存在异常。可以借助第三方BigDNA提供的基站IP与承载网链路对应关系以及承载链路上的链路参数来判断承载链路是否存在异常。BigDNA上报基站<gnb_length，gnbid>与承载链路bearer_link的对应关系，以及载链路bearer_link的链路参数。由此可以得到服务小区2对应的承载链路“SAW0055 to CN”存在丢包率过大。
然后遍历该服务小区组，分别对服务小区组中的三个服务小区所对应的基站进行配置参数变更的判断，可以借助第三方Mongoose提供基站参数配置当前值和建议值，发现无参数配置变更。
在对上述的服务小区组异常检测完成后，即可得到发生业务异常的第一根因，得到的第一根因包括{服务小区3在2021-04-20  18:43:56.788时间前有上报网元断链告警，服务小区2对应的承载链路“SAW0055 to CN”存在丢包率过大}。
由于主服务小区为服务小区1，此时主服务小区不在服务小区内，因此，主服务小区1存在过覆盖。然后再对主服务小区1依次进行告警、承载链路、覆盖类检测、干扰类检测、容量类检测和基站配置参数变更的检测，发现均无异常，则可以得到发生业务异常的第二根因，得到的第二根因包括{主服务小区1当前存在过覆盖}。
最终将服务小区组确定的第一根因以及根据主服务小区确定的第二根因作为最终确定的发生业务异常的根因进行输出，包括：{服务小区3在2021-04-20 18:43:56.788时间前有上报网元断链告警，服务小区2对应的承载链路“SAW0055 to CN”存在丢包率过大，主服务小区1当前存在过覆盖}。
请参阅图9，图9为本申请提供的一种根因定位设备的结构示意性框图。
如图9所示，根因定位设备200包括处理器201和存储器202，处理器201和存储器202通过总线203连接，该总线比如为I2C(Inter-integrated Circuit)总线。
具体地，处理器201用于提供计算和控制能力，支撑整个根因定位设备的运行。处理器301可以是中央处理单元(Central Processing Unit，CPU)，该处理器301还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。其中，通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
具体地，存储器202可以是Flash芯片、只读存储器(ROM，Read-Only Memory)磁盘、光盘、U盘或移动硬盘等。
本领域技术人员可以理解，图9中示出的结构，仅仅是与本申请实施方式方案相关的部分结构的框图，并不构成对本申请实施方式方案所应用于其上的根因定位设备的限定，具体的服务器可以包括比 图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
其中，所述处理器用于运行存储在存储器中的计算机程序，并在执行所述计算机程序时实现本申请实施方式提供的任意一种所述的根因定位方法。
在一实施方式中，所述处理器用于运行存储在存储器中的计算机程序，并在执行所述计算机程序时实现如下步骤：
获取发生业务异常的主服务小区，并确定所述主服务小区对应的栅格；对所述栅格进行扩展得到栅格组，并确定所述栅格组对应的服务小区组；对所述服务小区组和所述主服务小区进行异常检测，得到发生业务异常的根因。
在一实施方式中，所述处理器在实现所述确定所述主服务小区对应的栅格时，用于实现：
获取发生业务异常的无线数据，所述无线数据包括发生业务异常的小区和所述发生业务异常的栅格；根据所述主服务小区、所述业务异常的小区和所述发生业务异常的栅格确定所述主服务小区对应的栅格。
在一实施方式中，所述处理器在实现所述对所述服务小区组和所述主服务小区进行异常检测，得到发生业务异常的根因时，用于实现：
对所述服务小区组中的服务小区进行异常检测，得到所述服务小区组对应的第一根因；对所述主服务小区进行异常检测，得到所述主服务小区对应的第二根因。
在一实施方式中，所述处理器在实现所述对所述服务小区组中的服务小区进行异常检测，得到所述服务小区组对应的第一根因时，用于实现：
获取所述服务小区组中的服务小区的告警时刻，并确定业务异常的发生时刻是否在所述告警时段内；若所述业务异常的发生时刻在所述告警时段内，则得到所述服务小区存在告警。
在一实施方式中，所述处理器在实现所述对所述服务小区组中 的服务小区进行异常检测，得到所述服务小区组对应的第一根因时，用于实现：
获取所述服务小区组中服务小区的承载链路的链路参数，并根据所述链路参数确定所述承载链路是否存在异常；若所述服务小区组中的服务小区的承载链路存在异常，得到所述服务小区出现承载链路异常。
在一实施方式中，所述处理器在实现所述对所述服务小区组中的服务小区进行异常检测，得到所述服务小区组对应的第一根因时，用于实现：
获取所述服务小区组中服务小区对应基站的配置参数和参考参数；若所述配置参数和所述参考参数不一致，得到所述基站发生配置参数变更。
在一实施方式中，所述处理器在实现所述对所述主服务小区进行异常检测，得到所述主服务小区对应的第二根因时，用于实现：
确定所述服务小区组是否包括所述主服务小区；若所述服务小区组不包括所述主服务小区，得到所述主服务小区过覆盖。
在一实施方式中，所述处理器在实现所述对所述主服务小区进行异常检测，得到所述主服务小区对应的第二根因时，用于实现：
获取所述主服务小区的容量参数，并根据所述容量参数对所述主服务小区进行容量判断；若所述主服务小区的容量判断异常，得到所述主服务小区容量异常；和/或获取所述主服务小区的覆盖参数，并根据所述覆盖参数对所述主服务小区进行覆盖判断；若所述主服务小区的覆盖判断异常，得到所述主服务小区弱覆盖或重叠覆盖。
需要说明的是，所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的根因定位设备的具体工作过程，可以参考前述根因定位方法实施方式中的对应过程，在此不再赘述。
本申请实施方式还提供一种存储介质，用于计算机可读存储，所述存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现如本申请实施方式说明书提供的任一项根因定位方法的步骤。
其中，所述存储介质可以是前述实施方式所述的根因定位设备的内部存储单元，例如所述根因定位设备的硬盘或内存。所述存储介质也可以是所述根因定位设备的外部存储设备，例如所述根因定位设备上配备的插接式硬盘，智能存储卡(Smart Media Card，SMC)，安全数字(Secure Digital，SD)卡，闪存卡(Flash Card)等。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
应当理解，在本申请说明书和所附权利要求书中使用的术语“和/或”是指相关联列出的项中的一个或多个的任何组合以及所有可能组合，并且包括这些组合。需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者系统不仅包括那些要素，而且 还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者系统所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者系统中还存在另外的相同要素。
上述本申请实施方式序号仅仅为了描述，不代表实施方式的优劣。以上所述，仅为本申请的示例性实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (10)

  1. 一种根因定位方法，包括：
    获取发生业务异常的主服务小区，并确定所述主服务小区对应的栅格；
    对所述栅格进行扩展得到栅格组，并确定所述栅格组对应的服务小区组；
    对所述服务小区组和所述主服务小区进行异常检测，得到发生业务异常的根因。
  2. 根据权利要求1所述的根因定位方法，其中，所述确定所述主服务小区对应的栅格，包括：
    获取发生业务异常的无线数据，所述无线数据包括发生业务异常的小区数据和所述发生业务异常的栅格数据；
    根据所述主服务小区、所述业务异常的小区数据和所述发生业务异常的栅格数据确定所述主服务小区对应的栅格。
  3. 根据权利要求1所述的根因定位方法，其中，所述对所述服务小区组和所述主服务小区进行异常检测，得到发生业务异常的根因，包括：
    对所述服务小区组中的服务小区进行异常检测，得到所述服务小区组对应的第一根因；
    对所述主服务小区进行异常检测，得到所述主服务小区对应的第二根因。
  4. 根据权利要求3所述的根因定位方法，其中，所述对所述服务小区组中的服务小区进行异常检测，得到所述服务小区组对应的第一根因，包括：
    获取所述服务小区组中的服务小区的告警时刻，并确定业务异常的发生时刻是否在所述告警时段内；
    若所述业务异常的发生时刻在所述告警时段内，则得到所述服务小区存在告警。
  5. 根据权利要求3所述的根因定位方法，其中，所述对所述服 务小区组中的服务小区进行异常检测，得到所述服务小区组对应的第一根因，包括：
    获取所述服务小区组中服务小区的承载链路的链路参数，并根据所述链路参数确定所述承载链路是否存在异常；
    若所述服务小区组中的服务小区的承载链路存在异常，得到所述服务小区出现承载链路异常。
  6. 根据权利要求3所述的根因定位方法，其中，所述对所述服务小区组中的服务小区进行异常检测，得到所述服务小区组对应的第一根因，包括：
    获取所述服务小区组中服务小区对应基站的配置参数和参考参数；
    若所述配置参数和所述参考参数不一致，得到所述基站发生配置参数变更。
  7. 根据权利要求3所述的根因定位方法，其中，所述对所述主服务小区进行异常检测，得到所述主服务小区对应的第二根因，包括：
    确定所述服务小区组是否包括所述主服务小区；
    若所述服务小区组不包括所述主服务小区，得到所述主服务小区过覆盖。
  8. 根据权利要求3所述的根因定位方法，其中，所述对所述主服务小区进行异常检测，得到所述主服务小区对应的第二根因，包括：
    获取所述主服务小区的容量参数，并根据所述容量参数对所述主服务小区进行容量判断；
    若所述主服务小区的容量判断异常，得到所述主服务小区容量异常；和/或
    获取所述主服务小区的覆盖参数，并根据所述覆盖参数对所述主服务小区进行覆盖判断；
    若所述主服务小区的覆盖判断异常，得到所述主服务小区弱覆盖或重叠覆盖。
  9. 一种根因定位设备，其中，所述根因定位设备包括处理器、存储器、存储在所述存储器上并可被所述处理器执行的计算机程序以 及用于实现所述处理器和所述存储器之间的连接通信的数据总线，其中所述计算机程序被所述处理器执行时，实现如权利要求1至8中任一项所述的根因定位方法的步骤。
  10. 一种存储介质，用于计算机可读存储，其中，所述存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现权利要求1至8中任一项所述的根因定位方法的步骤。
PCT/CN2022/109896 2021-08-27 2022-08-03 根因定位方法、根因定位设备及存储介质 WO2023024854A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110998597.3 2021-08-27
CN202110998597.3A CN115734263A (zh) 2021-08-27 2021-08-27 根因定位方法、根因定位设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023024854A1 true WO2023024854A1 (zh) 2023-03-02

Family

ID=85290455

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/109896 WO2023024854A1 (zh) 2021-08-27 2022-08-03 根因定位方法、根因定位设备及存储介质

Country Status (2)

Country Link
CN (1) CN115734263A (zh)
WO (1) WO2023024854A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117560706A (zh) * 2024-01-12 2024-02-13 亚信科技（中国）有限公司 根因分析方法、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009079256A1 (en) * 2007-12-17 2009-06-25 Motorola, Inc. Cell re-selection in a tetra communication network
CN107548086A (zh) * 2016-06-24 2018-01-05 中兴通讯股份有限公司 根因定位方法及装置
CN108271191A (zh) * 2016-12-30 2018-07-10 中国移动通信集团福建有限公司 无线网络问题根因定位方法及装置
CN108990087A (zh) * 2017-06-05 2018-12-11 中兴通讯股份有限公司 无线小区异常覆盖定位方法和装置
CN110401956A (zh) * 2018-04-25 2019-11-01 中国移动通信集团广东有限公司 覆盖评估方法和装置
CN110545557A (zh) * 2018-05-28 2019-12-06 中国移动通信集团设计院有限公司 一种VoLTE问题分析方法、装置、电子设备及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009079256A1 (en) * 2007-12-17 2009-06-25 Motorola, Inc. Cell re-selection in a tetra communication network
CN107548086A (zh) * 2016-06-24 2018-01-05 中兴通讯股份有限公司 根因定位方法及装置
CN108271191A (zh) * 2016-12-30 2018-07-10 中国移动通信集团福建有限公司 无线网络问题根因定位方法及装置
CN108990087A (zh) * 2017-06-05 2018-12-11 中兴通讯股份有限公司 无线小区异常覆盖定位方法和装置
CN110401956A (zh) * 2018-04-25 2019-11-01 中国移动通信集团广东有限公司 覆盖评估方法和装置
CN110545557A (zh) * 2018-05-28 2019-12-06 中国移动通信集团设计院有限公司 一种VoLTE问题分析方法、装置、电子设备及存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117560706A (zh) * 2024-01-12 2024-02-13 亚信科技（中国）有限公司 根因分析方法、装置、电子设备及存储介质
CN117560706B (zh) * 2024-01-12 2024-03-22 亚信科技（中国）有限公司 根因分析方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN115734263A (zh) 2023-03-03

Similar Documents

Publication Publication Date Title
US10912058B2 (en) Discontinuous reception communication synchronization method and apparatus
US9173122B2 (en) Method, terminal and network device for configuring measurement gap
US8433321B2 (en) Method and apparatus for intelligently reporting neighbor information to facilitate automatic neighbor relations
US10034226B2 (en) Method, apparatus and system for acquiring system information
CN108605281A (zh) 核心网络节点、无线网络节点、无线设备以及在其中执行的方法
CN113170392B (zh) 唤醒信号的发送方法和设备
WO2015035807A1 (zh) 一种集群接听用户的异频测量和评估方法及装置
CN108738049A (zh) 处理双连接中的通信的装置及方法
CN109150484A (zh) 一种控制信息传输方法、相关装置及计算机存储介质
WO2023024854A1 (zh) 根因定位方法、根因定位设备及存储介质
EP3661311B1 (en) Resource indication method, system, computer readable storage medium and computer program product
CN109803436B (zh) 一种随机接入方法及装置
WO2023098352A1 (zh) 脱网检测方法、脱网检测设备及存储介质
CN105430721A (zh) 数据交互控制方法、数据交互控制装置和可穿戴设备
EP2750427B1 (en) Method and apparatus for coordinating cell outage compensation and capacity and coverage optimization
WO2018113466A1 (zh) 业务kpi的获取方法和网络设备
WO2016150046A1 (zh) 一种降低掉话率的方法、装置及系统
CN107005991A (zh) 上行数据包的传输方法、终端设备、基站及通信系统
WO2020088626A1 (zh) 一种pdu会话的动态调整方法、装置
CN106535111B (zh) 移动终端及其定位方法
US11902870B2 (en) Notification information display method and apparatus
US11991065B2 (en) Method and system to identify network nodes/cells with performance seasonality based on time series of performance data and external reference data
WO2024036956A1 (zh) 基站配置参数更新方法、设备及存储介质
EP4294093A1 (en) Positioning method and apparatus
CN118741586A (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: 22860200

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE