Method and apparatus for service monitoring

Abstract

The application discloses a service monitoring method and device, and relates to the technical field of computers. When a monitoring system monitors different operation and maintenance scenes or operation and maintenance events in real time or traces back, the monitoring system can automatically recommend a presentation view matched with the operation and maintenance scene or operation and maintenance event to a user, thereby reducing operation steps of the user. In the method, when the monitoring system needs to present a monitoring picture of a first event, the monitoring system can automatically determine that a recommended view type of the first event is a first view type, so that the monitoring system can present the monitoring picture of the first event to the user in the recommended first view type. Afterward, when the monitoring system continues to need to present a monitoring picture of a second event, the monitoring system can also automatically determine that a recommended view type of the second event is a second view type, so that the monitoring system can present the monitoring picture of the second event to the user in the recommended second view type.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a business monitoring method and apparatus. Background Technology

[0002] With the development of technologies such as the Internet, the Internet of Things (IoT), and cloud computing, more and more enterprises are choosing to manage and operate their businesses through the internet. For businesses, real-time monitoring of business operations ensures smooth operation and allows for immediate troubleshooting, thereby providing users with a highly reliable and stable service experience.

[0003] Currently, after monitoring the operational status of a business, the system typically presents it in a visual format so that users can intuitively view the business's operation. Furthermore, for diverse and complex business applications, monitoring systems often provide visualizations from different perspectives. However, when users need to view a specific visualization, they must manually interact with the monitoring system to trigger the display of that visualization by switching or overlaying it. This not only increases the number of steps required from the user but also impacts the efficiency of business monitoring, making it difficult for users to view the business's operational status in a timely and effective manner. Summary of the Invention

[0004] This application provides a business monitoring method and apparatus that can recommend the best visualization view to the user when monitoring the business, reducing the user's operation steps and enabling the user to quickly understand the current monitoring scenario.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a business monitoring method is provided, the method comprising: when it is necessary to present a monitoring screen of a first event, determining the recommended view type of the first event as a first view type; presenting the monitoring screen of the first event in the first view type; when it is necessary to present a monitoring screen of a second event, determining the recommended view type of the second event as a second view type, wherein the second event is different from the first event, and the second view type is different from the first view type; and presenting the monitoring screen of the second event in the second view type.

[0007] Optionally, the first event and the second event refer to the abnormal operating status or fluctuations in the operating status of a business object detected by the monitoring system within a certain period of time. Taking an autonomous wireless network scenario in an enterprise campus as an example, the first event could be a light turning on in an office, and the second event could be a malfunction of an indoor base station.

[0008] Optionally, the monitoring system can provide multiple view types. When the monitoring scene is presented in different view types, the operation and maintenance personnel can view monitoring information from different dimensions. Taking the monitoring scenario of an autonomous wireless network in an enterprise campus as an example, the monitoring system can provide different view types such as route view, logical cell view, signal strength view, and traffic scatter view, which can meet the monitoring needs of operation and maintenance personnel for different dimensions such as user behavior trajectory, logical cell, signal strength, and traffic volume within the monitoring scenario.

[0009] The solution provided in the first aspect above allows the monitoring system to intelligently recommend the most suitable view type to the user when presenting monitoring screens for different events, instead of using the same view type (such as the default view type) to present monitoring screens for different events. In this way, users can quickly and accurately understand the monitoring information of the current event without having to manually adjust the view type, reducing both user operation costs and information acquisition costs, improving monitoring efficiency, and meeting the different monitoring needs of operations and maintenance personnel facing different events.

[0010] Optionally, determining the recommended view type for the first event as the first view type includes: determining a first processing strategy for the first event; determining a first view type corresponding to the first processing strategy based on the first processing strategy and a preset correspondence between processing strategies and view types; and determining the first view type as the recommended view type for the first event.

[0011] The aforementioned determination of the recommended view type for the second event includes: determining a second processing strategy for the second event; determining the second view type corresponding to the second processing strategy based on the second processing strategy and the preset correspondence between processing strategies and view types; and determining the second view type as the recommended view type for the second event. In this way, when presenting monitoring screens for different events, the monitoring system can determine the processing strategy to be executed for the event and recommend the most suitable view type to the operations and maintenance personnel based on the processing strategy.

[0012] Optionally, determining the first processing strategy for the first event includes: acquiring first monitoring data of the first event; and determining the first processing strategy for the first event based on the first monitoring data. Determining the second processing strategy for the second event includes: acquiring second monitoring data of the second event; and determining the second processing strategy for the second event based on the second monitoring data. In this way, the monitoring system can accurately determine the processing strategy to be executed for an event by using various data monitored within a certain time period during which an event occurs.

[0013] In some scenarios, the correspondence between the above-mentioned preset processing strategies and view types includes: when the processing strategy is an adaptive energy-saving strategy, the corresponding view type is a route view; or when the processing strategy is an adaptive blind spot filling strategy, the corresponding view type is a signal strength view; or when the processing strategy is an adaptive capacity strategy, the corresponding view type is a logical cell view; or when the processing strategy is a regular strategy, the corresponding view type is a traffic scatter view.

[0014] In this way, by binding the various management and maintenance strategies of the monitoring system with the view types that operations and maintenance personnel are most interested in when facing these strategies, the monitoring system can automatically recommend the most suitable view type to operations and maintenance personnel when it needs to display a monitoring screen for a certain event during the monitoring of business objects, based on the processing strategy executed for that event and the aforementioned binding relationship. Operations and maintenance personnel can quickly and accurately understand the monitoring information of the current event without having to manually adjust the view type.

[0015] In one possible implementation, determining the recommended view type for the first event as the first view type includes: determining the first view type corresponding to the first event based on the first event and a preset correspondence between events and view types; and determining the first view type as the recommended view type for the first event. Determining the recommended view type for the second event as the second view type includes: determining the second view type corresponding to the second event based on the second event and a preset correspondence between events and view types; and determining the second view type as the recommended view type for the second event.

[0016] In this way, by associating various events occurring to a business object with the view types that operations and maintenance personnel are most interested in when facing those events, the monitoring system can automatically recommend the most suitable view type to operations and maintenance personnel when it needs to display a monitoring screen for a specific event during the monitoring of the business object, based on the event and the aforementioned binding relationships. Operations and maintenance personnel can quickly and accurately understand the monitoring information of the current event without having to manually adjust the view type.

[0017] Optionally, the business monitoring method further includes: displaying a first interface, which presents monitoring footage for a first time period. This first time period's monitoring footage is used to display monitoring footage of a first event and monitoring footage of a second event. In this way, when the monitoring system rewinds monitoring footage within a specific time period, it can automatically recommend different optimal presentation views based on the events occurring in different time periods, achieving a continuous and natural view switching effect.

[0018] Optionally, the first interface further includes a first control, which is used to set at least one processing strategy to be presented. The business monitoring method further includes: responding to a first operation by the user on the first control, determining the presented processing strategy as a first processing strategy and a second processing strategy based on the first operation; presenting a monitoring screen for a first time period on the first interface, the monitoring screen for the first time period being used to present monitoring screens for at least one event corresponding to the first processing strategy and monitoring screens for at least one event corresponding to the second processing strategy; wherein, the at least one event corresponding to the first processing strategy includes a first event, and the at least one event corresponding to the second processing strategy includes a second event. Thus, the visualization interface provided by the monitoring system can provide a control for filtering processing strategies, allowing maintenance personnel to input the processing strategies they wish to monitor. The monitoring system can then specifically present monitoring screens for events corresponding to the processing strategies selected by the maintenance personnel, and automatically recommend the most suitable view type for each event when presenting the monitoring screens.

[0019] In one scenario, the aforementioned requirement to present the monitoring screen for the first event can include: when the monitoring screen for the first time period is played to the first moment, determining that the monitoring screen for the first event needs to be presented on the first interface; the aforementioned requirement to present the monitoring screen for the second event includes: when the monitoring screen for the first time period is played to the second moment, determining that the monitoring screen for the second event needs to be presented on the first interface. In this way, when the monitoring system rewinds monitoring screens within a specific time period, it can automatically recommend the most suitable view type to present the monitoring screen for that event, following the events played at the current rewind progress.

[0020] In one scenario, the first interface can display a timeline, which shows a first time period. A first event is marked at a first moment on the timeline to indicate its occurrence. A second event is marked at a second moment on the timeline to indicate its occurrence. Based on this, the monitoring screen displaying the first event can include: responding to a user's first operation on the first event's identifier, determining that the monitoring screen for the first event needs to be displayed on the first interface; the monitoring screen displaying the second event can include: responding to a user's second operation on the second event's identifier, determining that the monitoring screen for the second event needs to be displayed on the first interface. Thus, maintenance personnel can also directly trigger the monitoring system to display the monitoring screen for the selected event by clicking on a specific event identifier on the timeline, and automatically recommend the most suitable view type for that event when displaying the monitoring screen.

[0021] In one scenario, the aforementioned first interface may further include a time filter control for setting the monitoring time period to be presented. The business monitoring method may also include: responding to the user's operation on the time filter control, determining the monitoring time period to be presented as the first time period based on the operation. Thus, the visualization interface provided by the monitoring system can also offer controls for filtering monitoring time ranges, allowing maintenance personnel to input the desired monitoring time range. The monitoring system can then specifically present monitoring footage within the time range selected by the maintenance personnel, and when presenting monitoring footage of events occurring within that time range, it automatically recommends the most suitable view type for each event.

[0022] Optionally, the first interface further includes a second control for setting the view type to be presented. After presenting the monitoring screen of the first event in the first view type, the business monitoring method further includes: responding to a second operation by the user on the second control, determining the view type to be presented as a third view type based on the second operation; and presenting the monitoring screen of the first event in the third view type. Thus, when the automatically recommended view type does not meet the user's needs, the visualization interface provided by the monitoring system can also provide a control for view selection, allowing maintenance personnel to input the desired view type, so that the monitoring system can present the monitoring screen of the event in the view type selected by the maintenance personnel.

[0023] Optionally, the business monitoring method further includes: displaying a second interface showing real-time monitoring footage. The requirement to display the monitoring footage for the first event includes: determining, upon detecting the occurrence of the first event, that the monitoring footage for the first event needs to be displayed on the second interface. Similarly, the requirement to display the monitoring footage for the second event includes: determining, upon detecting the occurrence of the second event, that the monitoring footage for the second event needs to be displayed on the second interface. Thus, during long-term or continuous real-time monitoring, the most suitable view type can be automatically recommended to display the monitoring footage for the event based on the real-time events occurring, achieving a continuous and natural view switching effect.

[0024] Optionally, the business monitoring method further includes: when it is necessary to present a monitoring screen for a scenario without events, determining that the recommended view type for the scenario without events is the fourth view type; and presenting the monitoring screen for the scenario without events using the fourth view type. Thus, when the monitoring system presents real-time monitoring footage or rewinds monitoring footage within a specific time period, if no event has occurred at the current moment or the current rewind moment, it can intelligently recommend the most suitable presentation view type to the user.

[0025] Optionally, the above-mentioned determination of the recommended view type for the event-free scenario is the fourth view type, which includes: determining a third processing strategy for the event-free scenario; determining the fourth view type corresponding to the third processing strategy based on the third processing strategy and the preset correspondence between processing strategies and view types; and determining the fourth view type as the recommended view type for the event-free scenario. In this way, when the monitoring system presents different monitoring screens, even if no event has occurred, it can determine the processing strategy executed by the system on the current monitoring screen and recommend the most suitable view type to the operations and maintenance personnel based on the processing strategy.

[0026] Optionally, a third processing strategy for event-free scenarios is determined, including: acquiring third monitoring data for event-free scenarios; and determining the third processing strategy for event-free scenarios based on the third monitoring data. In this way, when the monitoring system presents different monitoring screens, even if no event has occurred, it can accurately determine the processing strategy to be executed based on the various data currently monitored.

[0027] Secondly, a business monitoring device is provided. This device has the function of implementing any of the methods in the first aspect and its possible implementations. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described function. As an example, the business monitoring device may include: a determination module and a presentation module. The determination module is used to determine, when a monitoring screen of a first event needs to be presented, the recommended view type for the first event is a first view type; the presentation module is used to present the monitoring screen of the first event in the first view type. The determination module is further used to determine, when a monitoring screen of a second event needs to be presented, the recommended view type for the second event is a second view type, wherein the second event is different from the first event, and the second view type is different from the first view type; the presentation module is further used to present the monitoring screen of the second event in the second view type.

[0028] Optionally, the aforementioned determining module includes a strategy determining unit, a strategy matching unit, and a view recommending unit. The strategy determining unit determines a first processing strategy for the first event; the strategy matching unit determines a first view type corresponding to the first processing strategy based on the first processing strategy and a preset correspondence between processing strategies and view types; and the view recommending unit determines the first view type as the recommended view type for the first event.

[0029] The strategy determination unit is further configured to determine a second processing strategy for the second event; the strategy matching unit is further configured to determine a second view type corresponding to the second processing strategy based on the second processing strategy and the preset correspondence between processing strategies and view types; the view recommendation unit is further configured to determine the second view type as the recommended view type for the second event.

[0030] Optionally, the strategy determination unit is configured to: acquire first monitoring data of the first event; determine a first processing strategy for the first event based on the first monitoring data; the strategy determination unit is further configured to: acquire second monitoring data of the second event; determine a second processing strategy for the second event based on the second monitoring data.

[0031] Optionally, the service monitoring device may further include a storage module for storing the aforementioned preset correspondence between processing strategies and view types. Optionally, the preset correspondence between processing strategies and view types includes: when the processing strategy is an adaptive energy-saving strategy, the corresponding view type is a route view; or when the processing strategy is an adaptive blind spot filling strategy, the corresponding view type is a signal strength view; or when the processing strategy is an adaptive capacity strategy, the corresponding view type is a logical cell view; or when the processing strategy is a conventional strategy, the corresponding view type is a traffic scatter view.

[0032] Optionally, the aforementioned determining module includes an event matching unit and a view recommendation unit. The event matching unit is used to determine a first view type corresponding to the first event based on the first event and a preset correspondence between event and view types; the view recommendation unit is used to determine the first view type as the recommended view type for the first event. The event matching unit is also used to determine a second view type corresponding to the second event based on the second event and a preset correspondence between event and view types; the view recommendation unit is also used to determine the second view type as the recommended view type for the second event.

[0033] Optionally, the above-mentioned presentation module is further used to: display a first interface, in which a monitoring screen of a first time period is presented, and the monitoring screen of the first time period is used to present the monitoring screen of the first event and the monitoring screen of the second event.

[0034] Optionally, the first interface further includes a first control, which is used to set at least one processing strategy to be presented. The business monitoring device may also include a response module, used to respond to a first operation by the user on the first control, and determine the presented processing strategy as a first processing strategy and a second processing strategy based on the first operation. Based on this, the presentation module is used to present a monitoring screen for a first time period on the first interface. The monitoring screen for the first time period is used to present monitoring screens for at least one event corresponding to the first processing strategy and monitoring screens for at least one event corresponding to the second processing strategy; wherein the at least one event corresponding to the first processing strategy includes a first event, and the at least one event corresponding to the second processing strategy includes a second event.

[0035] Optionally, the first interface further includes a second control, which is used to set the view type to be presented. After the presentation module presents the monitoring screen of the first event in the first view type, the business monitoring device may further include a response module, which is used to respond to a second operation by the user on the second control and determine the view type to be presented as a third view type based on the second operation. Based on this, the presentation module is used to present the monitoring screen of the first event in the third view type.

[0036] Optionally, the aforementioned presentation module is further configured to: display a second interface, wherein the second interface displays a real-time monitoring screen. The business monitoring device may further include a detection module, configured to determine, upon detecting the occurrence of a first event, that the monitoring screen of the first event needs to be displayed on the second interface. The detection module is further configured to determine, upon detecting the occurrence of a second event, that the monitoring screen of the second event needs to be displayed on the second interface.

[0037] Optionally, the aforementioned determining module is further configured to: when it is necessary to present a monitoring screen of a no-event scenario, determine that the recommended view type for the no-event scenario is the fourth view type. The aforementioned presentation module is further configured to: present the monitoring screen of the no-event scenario in the fourth view type.

[0038] Optionally, the aforementioned determining module includes a strategy determining unit, a strategy matching unit, and a view recommending unit. The strategy determining unit is used to determine a third processing strategy for the event-free scenario; the strategy matching unit is used to determine a fourth view type corresponding to the third processing strategy based on the third processing strategy and a preset correspondence between processing strategies and view types; and the view recommending unit is used to determine the fourth view type as the recommended view type for the event-free scenario.

[0039] Optionally, the strategy determination unit is used to acquire third monitoring data for no-event scenarios; and to determine a third processing strategy for no-event scenarios based on the third monitoring data.

[0040] Thirdly, an electronic device is provided, comprising a memory and one or more processors. The memory and processors are coupled. The memory stores computer program code, including computer instructions. When the one or more processors execute the computer instructions, the electronic device performs the business monitoring method as described in the first aspect and any possible design thereof.

[0041] Fourthly, a computer-readable storage medium is provided, the computer-readable storage medium including computer instructions that, when executed on a computer, cause the computer to perform the business monitoring method as described in the first aspect and any possible design thereof.

[0042] Fifthly, a computer program product is provided that, when run on a computer, causes the computer to perform the business monitoring method as described in the first aspect and any possible design of the first aspect.

[0043] It is understood that the beneficial effects achieved by the apparatus described in the second aspect, the device described in the third aspect, the computer-readable storage medium described in the fourth aspect, and the computer program product described in the fifth aspect can be referred to the beneficial effects in the first aspect and any of its possible design embodiments, which will not be repeated here. Attached Figure Description

[0044] Figure 1 A schematic diagram of an interface provided for general-purpose technologies;

[0045] Figure 2 This is a schematic diagram of an application scenario provided by an embodiment of this application;

[0046] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0047] Figure 4 A flowchart of a business monitoring method provided in this application embodiment;

[0048] Figure 5 Interface illustration provided for embodiments of this application Figure 1 ;

[0049] Figure 6 Interface illustration provided for embodiments of this application Figure 2 ;

[0050] Figure 7 Interface illustration provided for embodiments of this application Figure 3 ;

[0051] Figure 8 Interface illustration provided for embodiments of this application Figure 4 ;

[0052] Figure 9 Interface illustration provided for embodiments of this application Figure 5 ;

[0053] Figure 10 Interface illustration provided for embodiments of this application Figure 6 ;

[0054] Figure 11 Interface illustration provided for embodiments of this application Figure 7 . Detailed Implementation

[0055] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0056] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, a and b and c, where a, b, and c can be single or multiple.

[0057] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0058] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0059] The features, structures, or characteristics in this application can be combined in any suitable manner in one or more embodiments. In the various embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0060] Some optional features in the embodiments of this application can be implemented independently without relying on other features in certain scenarios to solve the corresponding technical problems and achieve the corresponding effects. In other scenarios, they can be combined with other features according to needs.

[0061] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The implementation methods of this application do not constitute a limitation on the scope of protection of this application.

[0062] Furthermore, the business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0063] Operation and maintenance (O&M) refers to the process of managing and maintaining business objects such as equipment, networks, and services through a series of steps and methods, enabling the monitoring of these objects. Typically, when O&M or monitoring personnel need to monitor and maintain a particular business object, they can connect that object to an O&M or monitoring system to monitor its operational status, thereby ensuring that the object always maintains normal operation. The following will use an O&M system as an example to illustrate the solution provided in this application's embodiments.

[0064] With the emergence of various operation and maintenance (or monitoring) scenarios such as industrial parks or data centers, a single operation and maintenance area (or monitoring area) typically contains a large number of business objects that need to be monitored and maintained. These business objects can be uniformly connected to a single operation and maintenance system, or they can be connected to different operation and maintenance systems. This operation and maintenance system can detect changes in the operational status of these business objects and record these changes as operation and maintenance events.

[0065] Taking a building as an example, this building typically houses a large number of devices such as base stations, routers, lights, and cameras. To ensure these devices maintain normal operation at all times, they can be uniformly connected to an operations and maintenance system to monitor their operational status and promptly identify anomalies. When a device's operational status becomes abnormal (e.g., the uplink / downlink rate of a base station is 0), or when the device's operational status fluctuates significantly (e.g., lights go from off to on, or the uplink / downlink rate of a base station decreases significantly and remains at a low value for a certain period), the operations and maintenance system or monitoring system can detect the change in the device's operational status and record this abnormality or significant fluctuation in operational status over a period of time as an operations and maintenance event.

[0066] Currently, the operations and maintenance (O&M) system can not only obtain the operational parameters of business objects within the O&M area, but also present the current O&M scenario through visualizations of different dimensions. This helps O&M or monitoring personnel view the operational status of business objects within the O&M area from a top-down perspective. However, the current O&M system initially presents the current O&M scenario using a default dimension view. When users want to view different dimensions, they need to manually operate the O&M system to switch to the corresponding dimension view.

[0067] like Figure 1 As shown in (a), the initial visualization screen displayed by the operation and maintenance system in the provided visualization interface 100 is the default screen. Figure 1 The presented visualization. When users want to view the scene presented in other views, they can do so by manually manipulating the view controls in the visualization interface 100. For example... Figure 1 As shown in (b), the visualization interface 100 provided by the operation and maintenance system includes a view Figure 1 ,See Figure 2 ,See Figure 3 Heshi Figure 4 View switching buttons, when the user wants to view... Figure 3 At that time, users can click on the video. Figure 3 The corresponding view switching button 101 triggers the operation and maintenance system to switch from the initially displayed default view. Figure 1 Switch to display view Figure 3 or will be viewed Figure 3 Overlay on the displayed view Figure 1 Above. Thus, users can view the visual interface provided by the operation and maintenance system. Figure 3 The visuals presented.

[0068] It's understandable that when an operations and maintenance system offers a wide variety of view types, the manual operation described above often requires users to search for the view they want from among many options. Furthermore, the fixed positions of view controls mean that some controls are frequently located far away. This not only increases the user's operational costs but also their cognitive and perceptual burdens.

[0069] To address the aforementioned issues, this application provides a business monitoring method. When presenting different operational events or scenarios, the operational system can determine the current operational intent and automatically recommend the best presentation view to operational personnel based on that intent. This eliminates the need for manual view adjustments by operational personnel, reducing their workload and enabling them to intuitively perceive the intelligence of the operational system.

[0070] In this context, the operational intent can be understood as the management and maintenance operations that the operational system intends to perform during the monitoring of business objects; it can also be called the operational strategy or processing strategy.

[0071] Please see Figure 2 , Figure 2 This is a schematic diagram illustrating an application scenario for a business monitoring method provided in an embodiment of this application. The application scenario includes an electronic device 200 and a user 210.

[0072] The electronic device 200 is equipped with operation and maintenance software (or monitoring software) and can connect to a network. The electronic device 200 can obtain the operating parameters of business objects within a designated operation and maintenance area via the network. For example, in a scenario of autonomous wireless network in an enterprise campus, the electronic device 200 can obtain parameters such as the network status within the campus (e.g., the network status of a building, the lighting status), and then feed back the obtained operating parameters of the business objects to the operation and maintenance software, presenting them in a visual interface.

[0073] Optionally, when the operation and maintenance software detects an abnormality in the operating status of a business object based on the obtained operating parameters of the business object, or detects a significant fluctuation in the operating status of the business object within a time period, the operation and maintenance software can treat these abnormalities or significant fluctuations in the operating status within a time period as operation and maintenance events and present them on the interface of the operation and maintenance software in a visual manner.

[0074] User 210 can be an operations and maintenance (O&M) or monitoring personnel. They can use the O&M software on electronic device 200 to monitor the network status in a designated O&M or monitoring area in real time, and view past O&M events for reproduction and summarization. In other words, the O&M software or the electronic device 200 with it installed is primarily responsible for collecting and processing the operational parameters of business objects and other intelligent O&M tasks, and for presenting the O&M results to the user. User 210 is mainly responsible for viewing the overall picture and coordinating planning. This reduces the user's operational steps and improves O&M efficiency.

[0075] As an example, please refer to Figure 3 , Figure 3 This diagram illustrates the hardware structure of an electronic device 300 according to an embodiment of this application. The electronic device 300 may be the aforementioned electronic device 200.

[0076] like Figure 3 As shown, the electronic device 300 may include a processor 310, a memory 320, a communication module 330, a sensor module 340, an audio module 350, buttons 360, a motor 361, an indicator 362, a display screen 370, etc.

[0077] The processor 310 is the control center of the electronic device 300. The processor 310 can connect to various parts of the electronic device 300 through various interfaces and lines. By running or executing software programs and / or application modules stored in the memory 320, and calling data stored in the memory 320, the processor 310 performs various functional applications and data processing of the electronic device 100, such as the presentation of the operation and maintenance interface or monitoring interface.

[0078] Processor 310 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. The different processing units may be independent devices or integrated into one or more processors.

[0079] The memory 320 can be used to store computer executable program code, which includes instructions. The processor 310 executes various functional applications and data processing of the electronic device 300 by running the instructions stored in the memory 320. For example, in this embodiment, the processor 310 can control the audio module 350 to send an alarm sound by executing the instructions stored in the memory 320. The memory 320 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application required for a function, etc. The data storage area may store data created during the use of the electronic device 300, etc. Furthermore, the memory 320 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0080] The communication module 330 may include a mobile communication module and / or a wireless communication module. The mobile communication module can provide wireless communication solutions, including 2G / 3G / 4G / 5G, for use on the electronic device 300. The wireless communication module can provide wireless communication solutions, including wireless local area networks (WLANs) (such as Wi-Fi), Bluetooth, Global Navigation Satellite System (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies, for use on the electronic device 300.

[0081] The sensor module 340 may include a pressure sensor, a touch sensor, etc. The pressure sensor is used to sense pressure signals and convert them into electrical signals. In some embodiments, the pressure sensor may be disposed on the display screen 370. When a touch operation is applied to the display screen 370, the electronic device 300 detects the intensity of the touch operation based on the pressure sensor. The electronic device 300 may also calculate the touch location based on the detection signal from the pressure sensor. In this embodiment, the pressure sensor can be used to detect user click operations on the monitoring interface (or maintenance interface).

[0082] A touch sensor, also known as a "touch panel," can be located on a display screen 370. The touch sensor and the display screen 370 together form a touchscreen, also called a "touch screen." The touch sensor detects touch operations (such as long press, swipe up, swipe left, single click, double click, etc.) applied to or near it. The touch sensor can transmit the detected touch operations to the application processor to determine the touch event type. In this embodiment, the touch sensor can be used to detect touch operations applied to a monitoring interface (or maintenance interface). In this embodiment, the touch operation detected by the touch sensor can be an operation performed by the user's finger on or near the touchscreen, or an operation performed by the user using a stylus, stylus pen, touch ball, or other touch-assisted tool on or near the touchscreen; this application does not impose any limitations.

[0083] Display screen 370 is used to display images, videos, etc. Display screen 370 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Mini LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc.

[0084] In this embodiment, the display screen 370 is used to display a visual image of the monitored area, so that monitoring personnel can view ongoing maintenance events and reproduce past maintenance events.

[0085] Electronic device 300 can implement audio functions through audio module 350. For example, it can provide prompts or warnings when maintenance events occur.

[0086] The buttons 360 include a power button, volume buttons, etc. These buttons can be mechanical or touch-sensitive. The electronic device 300 can receive button input and generate key signal inputs related to user settings and function control.

[0087] Motor 361 can generate vibration alerts. Motor 361 can be used to alert users to abnormalities or fluctuations in business objects, and can also be used for touch vibration feedback.

[0088] Indicator 362 can be an indicator light, used to indicate the abnormal or fluctuating state of business objects in the monitoring area, or to indicate messages, notifications, etc.

[0089] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 300. In other embodiments, the electronic device 300 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0090] It should be noted that the business monitoring method provided in this application can be applied to monitoring or operation and maintenance scenarios that require monitoring one or more business objects. For example, it can be an autonomous wireless network scenario such as an enterprise park or campus park, or a device monitoring scenario such as a production line, factory, or hospital that can be managed and maintained by a management organization. This application does not limit the applicable scenarios.

[0091] Please see Figure 4 , Figure 4 This application provides a method for business monitoring, which can be applied to an operation and maintenance system. The operation and maintenance software corresponding to this system can be installed on the aforementioned electronic device. For example... Figure 4 As shown, the method may include:

[0092] S410, the operation and maintenance system determines the target event currently being presented.

[0093] In this embodiment, when operations and maintenance personnel need to manage and maintain business objects such as devices, networks, and services in a certain operations and maintenance area, they can connect these business objects to an operations and maintenance system or monitoring system to monitor their operational status. Furthermore, when the operations and maintenance system or monitoring system detects abnormal operational status of a business object, or significant fluctuations in its operational status over a period of time, it can record these abnormal operational statuses or fluctuations as operations and maintenance events, allowing operations and maintenance personnel to view currently occurring or historically occurring operations and maintenance events.

[0094] Taking the autonomous wireless network scenario in an enterprise campus as an example, when all devices in a certain area of ​​the campus enter a sleep state, the operation and maintenance system can record it as an operation and maintenance event; when devices in a certain area of ​​the campus enter a working state, such as when a light in an office turns on, the operation and maintenance system can also record it as an operation and maintenance event; when a device in the campus malfunctions, the operation and maintenance system can also record it as an operation and maintenance event, and so on.

[0095] It is understood that the above-mentioned operation and maintenance scenarios and events are merely examples, and the embodiments of this application do not limit the operation and maintenance scenarios and events. For example, when the operation and maintenance scenario is a robotic arm equipment management scenario, the operation and maintenance event could also be a robotic arm in a certain area malfunctioning, or a light in a certain warehouse turning on, etc. As another example, when the operation and maintenance scenario is a tunnel traffic monitoring scenario, the operation and maintenance event could also be a pedestrian crossing the boundary, a device malfunctioning in the tunnel, or road congestion, etc.

[0096] In this embodiment, after obtaining the operating parameters of business objects in the operation and maintenance area, the operation and maintenance system can present the current scene of the operation and maintenance area, the currently occurring operation and maintenance event, or the reproduced operation and maintenance event through different visualization views. The visualization presented by the operation and maintenance system can be a real-world view of the operation and maintenance area or a constructed three-dimensional (3D) map of the operation and maintenance area or monitoring area. This application does not limit the type of visualization presented by the operation and maintenance system; for example, it can also be a drawn two-dimensional (2D) view of the operation and maintenance area or monitoring area.

[0097] In one scenario, the operations and maintenance (O&M) system can construct a 3D map model of the O&M area, using dots to identify communication devices within that area. Similarly, when people carry portable communication devices such as mobile phones and tablets, dots can be used to identify those using these devices. When presenting O&M events or scenarios, the O&M system can combine this with the 3D map to visualize the event or scenario. For example, taking the O&M event of a light turning on in office 1 as an example, when presenting the visualization of this event, the O&M system can display a simulated image of the light turning on in office 1 on the 3D map, allowing O&M personnel to see the effect of the light turning on in office 1 on the 3D map.

[0098] In this embodiment, the electronic device may have maintenance software installed corresponding to the maintenance system. When the electronic device runs the maintenance software, a visual interface provided by the maintenance system can be displayed on the electronic device's screen.

[0099] Optionally, the visualization interface provided by the operations and maintenance system may include a selection interface for operations and maintenance events, allowing operations and maintenance personnel to determine the operations and maintenance event they wish to view. This desired event can be designated as the target event. After the operations and maintenance personnel determine the target event, the operations and maintenance system can display a visualization of that event.

[0100] In one scenario, when operations and maintenance personnel want to view (monitor) a certain operations and maintenance event, they can roughly locate the event through at least one dimension such as time dimension, event type dimension, etc.

[0101] Optionally, the electronic device can display a first interface on a screen. This first interface includes a time filtering control for maintenance personnel to input the time information they wish to monitor. The first interface can be the display interface of the maintenance software, used to show the maintenance scenarios corresponding to the maintenance area, and to display visual views corresponding to various maintenance events. When a user selects the time information to monitor using the time filtering control, the maintenance system can filter out maintenance events that match the time information selected by the maintenance personnel and display them on the first interface.

[0102] Optionally, the time filter control is a date selection control, allowing operations and maintenance personnel to enter the specific date or date range they wish to view.

[0103] Optionally, the time filter control is a time selection control, allowing operations and maintenance personnel to input the specific time or time range they wish to view. Alternatively, the time selection control can also provide options for one or more commonly used time periods for quick selection by operations and maintenance personnel.

[0104] Optionally, the first interface may also include an event filtering control, allowing operations and maintenance personnel to input the types of events they wish to view, such as abnormal status events or normal status change events. Alternatively, the event filtering control may also provide options for one or more commonly used event types for quick selection by operations and maintenance personnel.

[0105] For example, such as Figure 5 As shown, the display interface 500 of the operation and maintenance software on the electronic device includes a date selection control 501, a time selection control 502, and a type selection control 503, so that operation and maintenance personnel can filter operation and maintenance events by three dimensions: date, time, and event type.

[0106] Optionally, the first interface also includes a timeline. After the operations and maintenance personnel complete the input of the date and time, the timeline in the first interface will be updated accordingly to display the time period set by the operations and maintenance personnel. In this way, after roughly locating the operations and maintenance event by time, the corresponding timeline will also switch to the time period in which the located operations and maintenance event occurred.

[0107] Optionally, maintenance events occurring within the time range displayed on the timeline can be marked on the timeline. As a method, when marking maintenance events, the name, brief description, and occurrence time of the event can also be marked, making it easier for maintenance personnel to quickly understand the general situation of the maintenance event and determine whether it needs to be viewed.

[0108] For example, such as Figure 5As shown, when the maintenance personnel input the first time period set: date "2022 / 12 / 30" and time "8:00~17:00", the time range displayed on the time axis 504 in the maintenance software display interface 500 of the electronic device is updated to 8:00~17:00, and all maintenance events 505 that occur within this time range: maintenance event 1, maintenance event 2, maintenance event 3 and maintenance event 4 are also marked at the corresponding positions below the time axis 504.

[0109] Understandable. Figure 5 The event type selection control 503 displays all event types, meaning that the operations and maintenance personnel did not set a specific event type through the control. Therefore, operations and maintenance events 1, 2, 3, and 4 that occurred within this time frame will all be marked.

[0110] Optionally, if the maintenance personnel pass through Figure 5 The type selection control 503 sets a specific event type, such as the first event type. Then, among the maintenance events that occur within the time range displayed on the time axis, maintenance events that match the first event type can be marked on the time axis.

[0111] In one approach, only maintenance events conforming to the first event type can be marked on the timeline. Alternatively, all maintenance events occurring within the time range displayed on the timeline can be marked, but those conforming to the first event type can be highlighted. Optionally, the highlighting method can be at least one of the following: bolding, using a different font color, or highlighting with a specific color background. This application does not limit the highlighting method.

[0112] Optionally, maintenance personnel can also... Figure 5 The type selection control 503 allows setting multiple event types, such as a first event type and a second event type. Then, among the maintenance events occurring within the time range displayed on the timeline, maintenance events that match both the first and second event types can be marked on the timeline. This achieves multi-selection functionality for event types.

[0113] Understandable. Figure 5 The event type selection control 503 displays all event types, which is equivalent to the event types set by the operations and maintenance personnel. Therefore, all types of operations and maintenance events can be highlighted on the timeline. For example... Figure 5 As shown, all maintenance events that occurred within the time range displayed on timeline 504 are highlighted with a black background.

[0114] In one scenario, operations and maintenance (O&M) personnel can click on any O&M event marked on the timeline. The electronic device can then relay the selected O&M event to the O&M software, allowing the corresponding O&M system to determine the target event that the O&M personnel need to view. The O&M system can then play a visualization of that target event.

[0115] In other words, after an operations and maintenance (O&M) user clicks on a target event marked on the timeline, the O&M system can receive a user-input command to play the target event. The O&M system can then respond to this command by playing a visualization of the target event on the first interface.

[0116] In one scenario, once the operations and maintenance personnel have set up at least one of the above-mentioned filtering conditions, such as date, time, and event type, the operations and maintenance system can filter and locate operations and maintenance events based on the filtering conditions set by the operations and maintenance personnel, and then display the filtered operations and maintenance events.

[0117] Optionally, the operations and maintenance (O&M) system automatically plays a visualization of the O&M area from the initial time point set by the O&M personnel. In this case, the visualization of the O&M area plays continuously, with O&M events occurring in between interspersed throughout the playback. Optionally, all O&M events occurring within the time range set by the O&M personnel can be considered as the O&M events that the O&M personnel currently expect to view. When the O&M system plays any O&M event, that currently playing event can be used as the target event that the O&M personnel currently expect to view.

[0118] For example, such as Figure 5 As shown, after the maintenance personnel set the date "2022 / 12 / 30", time "8:00~17:00", and event type "all types" in the date selection control 501, time selection control 502, and type selection control 503, the maintenance system can filter the maintenance events and update the timeline 504 accordingly. Then, the maintenance system can automatically start from the start time in the timeline 504, that is, the start time of 8:00 set by the maintenance personnel, and reproduce the visualization of the maintenance area. If the above-mentioned 3D map model is controlled to display the corresponding scene simulation screen, the maintenance personnel can view the simulated scene of the maintenance area traced back by the maintenance system through the display interface 500 of the maintenance software on the electronic device.

[0119] Optionally, after the operations and maintenance personnel set at least one of the filtering conditions such as date, time, and event type, the operations and maintenance system can automatically trigger a playback command to automatically play the visualization of the operations and maintenance area from the initial time point set by the operations and maintenance personnel. Alternatively, the first interface may include a play button. When the operations and maintenance personnel click the play button, the operations and maintenance system can receive the playback command input by the user, and thus respond to the command to automatically play the visualization of the operations and maintenance area from the initial time point set by the operations and maintenance personnel.

[0120] Optionally, after an operations and maintenance (O&M) user manually clicks on a target event marked on the timeline, such as clicking on the O&M event name or brief description marked below the timeline, the O&M system can receive the user's instruction to play the target event. The O&M system can then respond to this instruction, starting playback with the occurrence time of the target event as the starting playback time, and begin playing the visualization of that O&M event. When the O&M event playback ends, the visualization will continue playing along the timeline.

[0121] For example, such as Figure 5 As shown, when an operations and maintenance (O&M) user clicks on the text "O&M Event 2" below timeline 504, the O&M software display interface 500 on the electronic device will start playing the visualization of the O&M area from the time "O&M Event 2" occurred at 10:00, i.e., the display of the O&M event "O&M Area". Assuming that O&M Event 2 ends at 14:20, if the playback progress on timeline 504 exceeds 14:20, it will continue playing the visualization of the O&M area from 14:21 to 17:00. This continues until an O&M user clicks on a new O&M event, at which point the visualization corresponding to that new O&M event will be played.

[0122] In one scenario, when an operations and maintenance (O&M) personnel click on a target event marked on the timeline, the O&M software interface displayed on the electronic device may only play the visualization of that target event once, and then stop playing the visualization of the O&M area once the target event ends. Alternatively, the visualization of the target event may be played in a loop.

[0123] S420, the operation and maintenance system obtains the monitoring data corresponding to the target event.

[0124] Once the operations and maintenance (O&M) system identifies the target event being monitored by the O&M personnel, it can display a visualization of that event. The O&M personnel can then view this visualization on the O&M software's interface displayed on their electronic devices. This visualization can be presented through different views.

[0125] Understandably, for a wide variety of business objects with complex application scenarios, the operation and maintenance system usually provides different dimensions of views to present the scenario of the operation and maintenance area, including the operation and maintenance events that are currently happening or have already happened.

[0126] Taking the autonomous wireless network scenario in an enterprise campus as an example, the operation and maintenance system can provide views of different dimensions such as user behavior trajectory, logical cell, signal strength, and call volume, thereby meeting the different monitoring needs of operation and maintenance personnel.

[0127] However, current operations and maintenance (O&M) systems present the current O&M scenario using a default view. Switching to different views requires manual intervention from O&M personnel. This forces O&M personnel to manually switch view types or overlay views after selecting the O&M events to monitor, increasing their operational costs and reducing monitoring efficiency.

[0128] To address this issue, in this embodiment, the operation and maintenance system can determine the current operational intent or processing strategy when presenting different operation and maintenance events or screens. Based on this intent or strategy, the system can recommend the most suitable view type to the operation and maintenance personnel, instead of using the same view type (such as the default view type) to present different operation and maintenance events or screens. This eliminates the need for users to manually adjust view types, reducing user operations while meeting the diverse monitoring needs of operation and maintenance personnel.

[0129] Optionally, when the operation and maintenance system determines to play a visualization of the target event, it acquires the monitoring data collected by the operation and maintenance system during the time period of the target event, so as to determine the current operation and maintenance intention or handling strategy based on the monitoring data.

[0130] Optionally, monitoring data may include various data of business objects within the operation and maintenance area.

[0131] For example, taking the enterprise campus wireless network autonomy scenario as an example of operation and maintenance, the monitoring data may include user information, monitored device information, logical cell information, and regional total information.

[0132] User information may include whether a user exists, user identity, number of users, user location distribution, and device affiliation. User identity may include regular users and VIP users, and other tiers are also possible. User location distribution indicates the user's current location. Device affiliation indicates the device currently supporting the user, such as the indoor base station providing communication services.

[0133] The information of the monitored devices may include the name or IP address of each monitored device, the number of users or communication devices covered by each monitored device, the number of VIP users covered by each monitored device, working status, running status, coverage area, configuration information, connected device information, and data transmission information of connected devices.

[0134] The number of users covered by each monitored device indicates the number of users currently supported by that device. One method is to determine the number of users covered by each monitored device based on the location of the user's portable communication device. Among the covered users, regular users and VIP users can be identified and their numbers can be counted separately.

[0135] The operating status indicates the current working state of the monitored device. For example, if the monitored device is an indoor base station, the operating status may include three states: off (or deep sleep), low power (or sleep) operation, and normal operation. As another example, if the monitored device is an indoor lighting fixture, the operating status may include three states: light off, low power sleep, and light on.

[0136] The operating status is used to indicate whether the monitored device is operating normally and whether it is online. In one approach, the operating status can include three states: online, offline, and fault.

[0137] Configuration information is used to indicate the current parameter configuration of the monitored device. For example, taking an indoor base station as an example, the configuration information may include power, antenna angle, frequency, etc.

[0138] Coverage range indicates the area supported by the monitored device. One approach is to mesh the 3D map model and represent the coverage range of the monitored device in units of grids. The coverage range can be fixed, for example, with each monitored device having a pre-defined initial range. Alternatively, the coverage range can be dynamically adjusted. For example, taking an indoor base station as an example, the size of the coverage range can be adjusted according to the base station's frequency; the higher the frequency, the smaller the coverage range.

[0139] Connected device information indicates whether the monitored device is connected to supporting devices and the number of supporting devices connected. For example, if the monitored device is an indoor base station, devices such as mobile phones and tablets connected to the network through a certain indoor base station are supporting devices, and each indoor base station can connect to multiple supporting devices.

[0140] The data transmission information of the connected device is used to indicate the data transmission information of each supporting device connected to the monitored device, including uplink rate, downlink rate, etc.

[0141] It can be understood that a logical cell can be a standard logical model of cell radio resources controlled by a radio network controller (RNC). An operational area can be divided into one or more logical cells. Uniform radio resources are provided within a single logical cell.

[0142] The logical cell information in the aforementioned monitoring data may include the number of logical cells and their distribution within the operation and maintenance area.

[0143] Typically, to facilitate parameter distribution and other operational management, the operation and maintenance area is divided into zones. For example, areas with fewer users and fewer running support devices are grouped into one large area, while areas with more users and more running support devices can be divided into zones based on user location distribution and support device location distribution. These divided areas can be called logical cells.

[0144] The total information of the operation and maintenance area can include total power consumption information and total traffic information, which can be used to calculate the total power consumption and total uplink and downlink traffic of the entire current area.

[0145] Optionally, the "current area" can be the entire operations and maintenance (O&M) scenario or a portion thereof. For example, taking an O&M scenario as a building, different O&M areas can be defined by floor. Different O&M strategies can then be provided for different O&M areas.

[0146] It is understood that the above monitoring data is merely an example, and can be reasonably configured according to specific operation and maintenance scenarios. This application does not limit the specific type of monitoring data. For example, taking a hospital scenario as an example, the monitoring data may include general user information, medical staff information, information on monitored medical equipment, information on monitored indoor base stations, lighting fixtures, and air conditioning, etc. As another example, taking a tunnel traffic monitoring scenario as an example, the monitoring data may include pedestrian information, vehicle flow information, information on monitored base stations, lighting fixtures, and traffic lights, etc.

[0147] It is understood that the embodiments of this application present the real-time simulation of the operation and maintenance site in a visual form, and the methods for obtaining various information of the operation and maintenance site involved in the simulation process can be consistent with the methods for obtaining information in the operation and maintenance system in related technologies.

[0148] S430, the operation and maintenance system determines the current processing strategy based on monitoring data.

[0149] In this embodiment of the application, after the operation and maintenance system obtains the monitoring data within the time period of the occurrence of the target event, the operation and maintenance system can determine which processing strategy is appropriate for operation and maintenance or monitoring based on the monitoring data.

[0150] The processing strategy (or operation and maintenance intention) reflects the management and maintenance operations that the operation and maintenance system expects to adopt in the current operation and maintenance scenario. Optionally, the operation and maintenance strategy may include routine operation and maintenance strategies, as well as unconventional operation and maintenance strategies adopted when operation and maintenance events occur. For example, when an indoor base station transmission fails, the operation and maintenance system may adopt an adaptive blind spot compensation strategy, that is, dynamically adjust the configuration parameters of surrounding base stations to cover the coverage area of ​​the faulty base station.

[0151] Optionally, the operations and maintenance (O&M) system can be pre-configured with decision conditions corresponding to different processing strategies (or O&M intentions). Thus, after acquiring monitoring data within the time period of the target event, the O&M system can determine the processing strategy to be adopted for the current O&M scenario by judging the decision conditions corresponding to the processing strategy satisfied by the monitoring data. Optionally, the decision conditions corresponding to different processing strategies can also be set by the O&M personnel themselves.

[0152] In one scenario, if the monitoring data meets the decision conditions corresponding to multiple processing strategies, all of these processing strategies can be used as the currently applicable processing strategy.

[0153] Taking the autonomous wireless network scenario in an enterprise campus as an example, the processing strategies can include adaptive power saving strategies, adaptive capacity strategies, adaptive blind spot filling strategies, and conventional strategies.

[0154] Optionally, the operation and maintenance system can determine whether to use an adaptive energy-saving strategy based on the number of users in the area, the number of users covered by each monitored device, the number of offline monitored devices, the total power consumption in the area, and the total traffic in the area.

[0155] In one possible implementation, the decision conditions for the adaptive energy-saving strategy may be: the number of users is less than a preset threshold (e.g., 10 people), the number of users covered by each monitored device is less than a preset threshold (e.g., 2 people), the number of monitored devices in an offline state exceeds a preset threshold (e.g., 80%), the total power consumption of the area is lower than a preset threshold, the total traffic of the area is lower than a preset threshold, or more than a certain number of monitored devices in the area cover fewer than a preset threshold (e.g., 2 people).

[0156] Optionally, when the above conditions meet a preset number, such as 1, 2 or 3, the operation and maintenance system can consider that it is suitable to monitor or operate with energy saving as the intention, that is, the current processing strategy of the operation and maintenance system is adaptive energy saving intention.

[0157] Optionally, the above conditions can also be set with different priorities, and the operation and maintenance system can determine the processing strategy based on the priority of different conditions. For example, for a high-priority condition, as long as one condition is met, the operation and maintenance system can determine that it is an adaptive energy-saving strategy. For a lower-priority condition, multiple conditions, such as two or three, need to be met before the operation and maintenance system can determine that it is an adaptive energy-saving strategy.

[0158] Optionally, when the operation and maintenance system adopts an adaptive energy-saving strategy for operation and maintenance or monitoring, it can execute the on-demand activation of base stations based on the perceived user location, thereby maximizing energy saving while ensuring user experience.

[0159] In one scenario, when an operations and maintenance (O&M) system employs an adaptive energy-saving strategy for O&M or monitoring, it can select target base stations for priority information sensing, reducing the cost of manually marking target base stations. These target base stations can be detected by radar and report location data in seconds, allowing the O&M system to quickly identify the presence and location of users. The O&M system can then predict user movement routes based on historical location information and preemptively wake up the corresponding base station. Optionally, before controlling the base station to go into sleep mode, the O&M system can drive the base station to send an update message for the tracking area code, prompting portable communication devices carried by users to actively send MSG5 messages. Thus, the O&M system can control the base station to enter sleep mode only after ensuring there are no users carrying portable communication devices in the cell. In this way, an energy-saving scenario can be achieved by using target base stations to wake up the base station when someone arrives (or turn on the light) and put the base station into sleep mode (or turn off the light) when someone leaves.

[0160] Optionally, the operation and maintenance system can determine whether to use an adaptive capacity strategy based on user location distribution, the number and distribution of logical cells, and the total regional traffic.

[0161] In one possible implementation, the decision condition for the adaptive capacity strategy may be at least one of the following: the number of logical cells changes, the number of logical cells exceeds a preset threshold (e.g., 2), the number of users in a certain area of ​​a logical cell exceeds a preset threshold (e.g., 50 people), or the total traffic in a certain area of ​​a logical cell exceeds a preset threshold.

[0162] Similar to the decision conditions of the aforementioned adaptive energy-saving strategy, the operation and maintenance system can also determine whether it is an adaptive capacity strategy by setting a number of conditions and conditions with different priorities.

[0163] In one scenario, when the operation and maintenance system adopts an adaptive capacity strategy for operation and maintenance or monitoring, it can adaptively adjust the number of logical cells according to user activity habits to adapt to different capacity requirements, achieving accurate and effective coverage.

[0164] For example, when users are concentrated in a certain area within a logical cell, a separate logical cell can be created for that area to provide better service. This separately created logical cell can be called an expanded cell.

[0165] Optionally, the decision to create a separate logical cell can be further based on total traffic or load. For example, if users are concentrated in a certain area within a logical cell, and the total traffic or load in that area exceeds a preset threshold, that area can be separated as an expansion cell. Optionally, capacity adjustment and cell splitting can be performed when the total traffic or load in that area exceeds 80%.

[0166] In this way, when a sudden hotspot occurs within a logical cell, such as during a meeting in a conference room, the excessive number of users and call volume can negatively impact user experience. Therefore, the operations and maintenance system can reduce the number of users and call volume in the high-load cell by activating a backup cell or reorganizing the cell, thus ensuring a good user experience. Of course, when a cell is under low load or idle, the operations and maintenance system can also merge cells. In this way, the operations and maintenance system can automatically adjust logical cells based on changes in call volume, achieving optimal allocation of baseband or channel resources and improving network capacity.

[0167] In some scenarios, when there is only one logical cell, the operation and maintenance system can determine that the current strategy is not adaptive capacity management. However, when there is only one logical cell and that logical cell is split, the operation and maintenance system can determine that the current strategy is adaptive capacity management.

[0168] Optionally, the operation and maintenance system can determine whether to use an adaptive blind spot compensation strategy based on the working status of the monitored equipment.

[0169] In one possible implementation, the decision condition for the adaptive blind spot compensation strategy can be that the monitored device is in a fault state.

[0170] In one scenario, taking an indoor base station as an example, when the indoor base station experiences a transmission failure, the operation and maintenance system can determine that it is suitable to perform monitoring or maintenance with the intention of adaptive coverage. At this time, the operation and maintenance system can dynamically adjust the configuration parameters of surrounding base stations to cover the coverage area of ​​the faulty base station, achieving adaptive coverage and ensuring the user experience within the coverage area of ​​the faulty base station.

[0171] Optionally, if none of the above-mentioned decision conditions for adaptive energy saving, adaptive capacity, and adaptive blind spot compensation are met, the operation and maintenance system can consider that it is appropriate to monitor or maintain the system using a conventional strategy. The operation and maintenance system can determine that the current processing strategy is a conventional strategy. When the operation and maintenance system uses a conventional strategy for monitoring or maintenance, it can meet the basic operation and maintenance needs of the operation and maintenance personnel.

[0172] It is understood that the above processing strategies are merely examples, and can be reasonably configured according to specific operation and maintenance scenarios. This application does not limit the specific type of processing strategy in its embodiments.

[0173] In some embodiments, the event type of the operation and maintenance events mentioned in the foregoing embodiments can be the processing strategy described above. That is, the operation and maintenance system can filter and classify operation and maintenance events according to the processing strategy.

[0174] Optionally, when the operations and maintenance (O&M) system detects an O&M event, it can determine and record the system's handling strategy based on the corresponding monitoring data. Therefore, when reproducing an O&M event, the O&M system can directly categorize the events to be reproduced based on the recorded handling strategy. In this way, O&M personnel can directly input the handling strategy they wish to view to roughly locate the O&M event.

[0175] For example, such as Figure 6 As shown, the display interface 600 of the operation and maintenance software on the electronic device may include an intent selection control 601, allowing operation and maintenance personnel to filter operation and maintenance events by setting intent conditions. Optionally, the intent selection control 601 can provide intent options such as adaptive energy saving, adaptive capacity, adaptive blind spot filling, routine operation and maintenance, and all intents. When the user selects any intent option in the intent selection control 601, such as the adaptive capacity intent option, the operation and maintenance system will display operation and maintenance events that conform to the adaptive capacity intent. That is, the display interface 600 of the operation and maintenance software on the electronic device can play a visualization of operation and maintenance events that conform to the adaptive capacity intent.

[0176] Optionally, the user can also select multiple intent options in the intent selection control 601, such as an adaptive capacity intent option and an adaptive blind spot compensation intent option. In this case, the operation and maintenance system can display operation and maintenance events that conform to the adaptive capacity intent and the adaptive blind spot compensation intent. That is, the display interface 600 of the operation and maintenance software on the electronic device can play visual displays of operation and maintenance events that conform to the adaptive capacity intent and the adaptive blind spot compensation intent.

[0177] Understandable. Figure 6 The intent selection control 601 displays all intents, meaning that the operations and maintenance personnel have not set specific intent conditions in the intent selection control 601. Therefore, all operations and maintenance events that occur within the time frame of the timeline will be displayed.

[0178] S440: The operation and maintenance system recommends a display view of the target event to the user based on the current processing strategy.

[0179] In this embodiment, after determining the current processing strategy, the operation and maintenance system can determine the recommended display view to the user and provide feedback to the electronic device. Thus, when the electronic device displays the operation and maintenance software's interface, it can play a visualization of the target event in the recommended display view. The recommended display view can be the optimal view type for presenting the visualization of the target event.

[0180] Optionally, the operations and maintenance system can provide different dimensions of view to present the scene of the operations and maintenance area, including operations and maintenance events that are currently happening or have already happened.

[0181] Taking an enterprise campus wireless network autonomy scenario as an example, the operation and maintenance system can provide different view types such as route view, logical cell view, signal strength view, and call traffic scatter view. This can meet the monitoring needs of operation and maintenance personnel for different dimensions such as user behavior trajectories, logical cells, signal strength, and call volume within the operation and maintenance area.

[0182] The route view can display the behavioral trajectory of users carrying portable communication devices. Optionally, the route view can also distinguish between regular users and VIP users.

[0183] The logical cell view can display the number of logical cells and the fission process of logical cells.

[0184] The signal strength view can display a gridded 3D map. Different colors can be used to identify the signal strength of each grid. Combinations of multiple grids can represent the signal coverage area.

[0185] The call volume scatter view can display the call volume scatter within the operation and maintenance area. The call volume scatter of a certain area can characterize the call usage in that area and reflect the call volume trend changes in that area.

[0186] It is understood that the above view types are merely examples, and the view types provided by the operation and maintenance system can be reasonably set according to specific operation and maintenance scenarios. This application embodiment does not limit the specific type of view.

[0187] Optionally, different processing strategies correspond to different view types. In one scenario, the operations and maintenance system can have a pre-defined mapping between processing strategies and view types. This mapping can be set by the operations and maintenance personnel themselves.

[0188] For example, please refer to Table 1, which provides an example of the correspondence between processing strategies and view types:

[0189] Table 1

[0190]

[0191]

[0192] The recommended view types for routine operations and maintenance (O&M) can be those representing the O&M scenarios and statuses that O&M personnel typically focus on. For example, during routine policy-based O&M, if O&M personnel are concerned with call volume, a call volume scatter view would be the recommended view type. Similarly, if O&M personnel are concerned with the online, offline, or faulty operational status of devices, a device management view that displays device operational status and distribution would be the recommended view type.

[0193] It is understood that the above-described correspondence between processing strategies and view types is merely an example, and the embodiments of this application do not limit the specific correspondence between processing strategies and view types.

[0194] In one scenario, the relationship between processing strategies and view types can also be many-to-one, meaning that multiple processing strategies can recommend the same view type.

[0195] In one scenario, the relationship between processing strategies and view types can be one-to-many, meaning that a processing strategy can have multiple recommended view types. Optionally, when a processing strategy has multiple recommended view types, these multiple recommended view types can be displayed in a split-screen manner or through a carousel. Optionally, when a processing strategy has multiple recommended view types, the operations and maintenance system can also randomly select one view type for recommendation.

[0196] Optionally, after determining the current processing strategy, the operations and maintenance system can determine the view type corresponding to the current processing strategy based on the pre-set correspondence between processing strategies and view types, and recommend the view type to the operations and maintenance personnel. In this way, when the operations and maintenance system determines that a visualization of a target event is about to be played, it can present the visualization of that event using the optimal view type for that target event. This allows different operations and maintenance events to be presented with different view types.

[0197] In some scenarios, when the operations and maintenance (O&M) system plays a visualization of the O&M area, if an O&M event (target event) occurs at the current playback time, the O&M system can, according to the method described in the aforementioned embodiments, obtain monitoring data within the time period of the O&M event, determine the current processing strategy based on the monitoring data, and recommend a display view type for the O&M event to the user based on the current processing strategy. Thus, when the electronic device displays the O&M software's interface, it plays the visualization of the O&M event using the recommended display view type.

[0198] In some scenarios, when the operations and maintenance (O&M) system plays a visualization of the O&M area, if no O&M events have occurred at the current playback time (i.e., no-event scenario), the O&M system can still obtain monitoring data from the scenario at the current playback time. Based on this monitoring data, it can determine the current processing strategy and recommend the current display view type to the user. Therefore, when the electronic device displays the O&M software's interface, it will play the visualization of the O&M area using the recommended display view type.

[0199] In some scenarios, if the best view type recommended by the operations and maintenance system does not meet the monitoring needs of the operations and maintenance personnel, the operations and maintenance system can also present a visual representation of the operations and maintenance events based on the view type selected by the operations and maintenance personnel.

[0200] In some scenarios, when the operations and maintenance (O&M) system displays a real-time monitoring visualization of the O&M area, if a new O&M event is detected, the O&M system can also follow the method described in the aforementioned embodiments: obtain monitoring data within the time period of the new O&M event, determine the current processing strategy based on the monitoring data, and recommend a display view type for the new O&M event to the user based on the current processing strategy. In this way, when the O&M system detects a new O&M event in real time, it can promptly display the visualization of the new O&M event using the recommended display view type.

[0201] Optionally, when the operation and maintenance system displays a real-time monitoring visualization of the operation and maintenance area, if a new operation and maintenance event is detected, the operation and maintenance system can notify the user of the occurrence of the new operation and maintenance event, or prompt the user to switch the view type in real time, so that the user can be prepared for the view type switch in advance and avoid giving the user an abrupt experience when switching the view type.

[0202] Optionally, the operations and maintenance system can also store a preset mapping between operations and maintenance events and view types. This mapping can be set by the operations and maintenance personnel. In this way, when the operations and maintenance system needs to display a visualization of a first event, it can directly find the corresponding first view type from the preset mapping and recommend that first view type to the user. When the operations and maintenance system needs to display a visualization of a second event, it can directly find the corresponding second view type from the preset mapping and recommend that second view type to the user.

[0203] For example, taking a tunnel traffic monitoring scenario as an example, when the maintenance event is a road congestion event, the recommended view type is a traffic flow view, which presents the traffic flow situation within the tunnel area; when the maintenance event is a tunnel equipment failure, the recommended view type is an equipment management view, which presents the working status of the equipment within the tunnel area. Thus, when the maintenance system rewinds historical monitoring footage and returns to the monitoring footage of a road congestion event, it can automatically present the monitoring footage of that road congestion event according to the recommended view type corresponding to that road congestion event, namely the traffic flow view. When the maintenance system continues to rewind to the monitoring footage of a road congestion event, it can automatically present the monitoring footage of that road congestion event according to the recommended view type corresponding to that road congestion event, namely the equipment management view. Therefore, when presenting different maintenance events, the maintenance system can automatically recommend the most suitable view type to maintenance personnel, instead of using the same view type (such as the default view type) to present different maintenance events or scenarios.

[0204] In some scenarios, when the operations and maintenance (O&M) system replays the visualization of the O&M area, if multiple O&M events occurred at the current playback time, the O&M system can also follow the method described in the aforementioned embodiments: acquiring monitoring data within the time period of each O&M event, determining the current processing strategy for each O&M event based on the monitoring data, and recommending a display view type for each O&M event to the user based on the current processing strategy. Thus, when the electronic device displays the O&M software's interface, it plays the visualization of each O&M event according to the recommended display view type for each O&M event.

[0205] As one approach, if two maintenance events occur at the current playback time, such as event one and event two, the maintenance system can recommend the display view type for each event to the user. For example, the recommended view type for event one would be the first view type, and the recommended view type for event two would be the second view type. When displaying the monitoring screen at the current playback time, the electronic device can split the monitoring screens of the two maintenance events into a single screen. For example, the display area of ​​the electronic device can be divided into a first display area and a second display area, so that the monitoring screen of event one is displayed in the first display area, and the monitoring screen of event two is displayed in the second display area. Furthermore, the system can play the visualizations of the two maintenance events according to their respective recommended display view types. For example, the monitoring screen of event one is presented in the first display area using the first view type, and the monitoring screen of event two is presented in the second display area using the second view type. In this way, when the maintenance system reviews the monitoring screen at a certain moment, if multiple maintenance events occur simultaneously, it can automatically recommend the best presentation view to the user based on each maintenance event, so that maintenance personnel can quickly view the information they need.

[0206] It is understandable that if more than two maintenance events occur at the current playback time, the electronic device can display the monitoring screens of the two or more maintenance events separately when displaying the monitoring screen at the current playback time.

[0207] In some scenarios, when the operations and maintenance (O&M) system displays a real-time monitoring visualization of the O&M area, if multiple new O&M events are detected, the O&M system can also follow the method described in the aforementioned embodiments: acquiring monitoring data within the time period of each new O&M event, determining the current processing strategy for each new O&M event based on the monitoring data, and recommending a display view type for each new O&M event to the user based on the current processing strategy. In this way, when the O&M system detects multiple new O&M events in real time, it can promptly display the visualizations of these multiple new O&M events using the recommended display view type.

[0208] It is understandable that when the operation and maintenance system presents a real-time monitoring visualization of the operation and maintenance area, if multiple new operation and maintenance events are detected, the electronic device can also display the monitoring screens of the multiple new operation and maintenance events separately while displaying the real-time monitoring screen.

[0209] As one approach, when the operations and maintenance (O&M) system presents a real-time monitoring visualization of the O&M area, if it detects two new O&M events, such as event one and event two, the O&M system can recommend the display view type for each event to the user. For example, the recommended view type for event one would be the first view type, and the recommended view type for event two would be the second view type. When displaying real-time monitoring footage, electronic devices can split the real-time monitoring footage of the two new O&M events into a single screen. For instance, the real-time monitoring footage of event one could be presented in the first display area using the first view type, and the real-time monitoring footage of event two could be presented in the second display area using the second view type. In this way, when the O&M system detects multiple new O&M events occurring simultaneously, it can automatically recommend the best presentation view for each event, allowing O&M personnel to quickly view the information they need.

[0210] The following will take the autonomous operation and maintenance scenario of an enterprise campus wireless network as an example to introduce the application of the service monitoring method provided in the embodiments of this application.

[0211] Please see Figure 6In the operation and maintenance software's display interface 600, if the user's input filter criteria for operation and maintenance events are "all intents" and "December 30, 2022, 8:00-17:00," then the timeline 602 in the display interface 500 will be updated to show the time period from 8:00 to 17:00 on December 30, 2022, and all operation and maintenance events occurring within that time period will be marked under timeline 602. At this time, the operation and maintenance system can obtain a visual view of the enterprise park within that time period and start playing the visual view from 8:00 on December 30, 2022, with the operation and maintenance events occurring in between interspersed in the playback screen.

[0212] Optionally, users can also select a specific maintenance event, such as clicking on the text of maintenance event 603 "Some office lights are on". In this way, the maintenance system can start playing a visual display of the enterprise campus from 08:30, the time when the maintenance event "Some office lights are on" occurred.

[0213] Optionally, the visualization of the enterprise park played by the operation and maintenance system can be a simulation of a 3D map model of the enterprise park, or a digital twin. For example... Figure 6 The twin screen 604 on the second floor of the display interface 600 shown.

[0214] like Figure 6 As shown, when the operation and maintenance system plays operation and maintenance event 603 "Some office lights are on" which occurred at 08:30, the system can determine the current processing strategy as an adaptive energy-saving strategy based on monitoring data such as user information, monitored equipment information, logical cell information, and regional total information corresponding to the event. The optimal presentation view type for this adaptive energy-saving strategy is a route view. Simultaneously, if the system detects a VIP user, it can display the VIP user's walking route view at this time.

[0215] like Figure 6 As shown, at this time, the twin screen 604 of the second floor is played in the route view on the display interface 600 of the operation and maintenance software. This route view displays the walking route 605 of VIP users. Optionally, as... Figure 6 As shown, the name or code 606 of the VIP user can also be displayed in the route view.

[0216] It's understandable that when the operations and maintenance (O&M) system plays O&M event 603 "Some office lights are on" which occurred at 08:30, it can obtain monitoring data for the time period of O&M event 603. This means that at this time, the first employee might be arriving at the second floor, and the number of users in the second-floor area is relatively small. Therefore, the O&M system is currently suitable for monitoring or maintenance with energy-saving as its primary objective. Thus, the O&M system can determine that O&M event 603 "Some office lights are on" occurring at 08:30, and the corresponding processing strategy for the O&M system is an adaptive energy-saving strategy. Consequently, the O&M system can recommend the route view as the display view to the user.

[0217] like Figure 7 As shown, when the operations and maintenance system plays the operations and maintenance event 607 "Meeting Room Expansion" that occurred at 10:00, employees gather in the meeting room for a meeting. The operations and maintenance system expands the capacity of a single cell in the meeting room. At this time, the operations and maintenance system can determine the current processing strategy as an adaptive capacity strategy based on the increase in the number of logical cells. The optimal presentation view type corresponding to this adaptive capacity strategy is the logical cell view. Therefore, the operations and maintenance system can recommend the logical cell view as the display view to the user.

[0218] like Figure 7 As shown, the twin view of the second floor is displayed in the logical cell view on the operation and maintenance software's display interface 600. This logical cell view shows two cells: logical cell 608 and expanded cell 609. Optionally, the expanded cell can be zoomed in to display it.

[0219] like Figure 8 As shown, when the operation and maintenance system plays the video at 12:30, there are currently no operation and maintenance events. At this time, the operation and maintenance system can determine, based on monitoring data such as user information, monitored equipment information, logical cell information, and regional total information, that the adaptive capacity strategy, adaptive energy-saving strategy, and adaptive blind spot compensation strategy are all not applicable. Therefore, it can be assumed that the operation and maintenance system is performing monitoring or operation and maintenance with the intention of routine operation and maintenance during the 12:30 time period. Thus, the operation and maintenance system can determine the operation and maintenance scenario at 12:30, and the corresponding processing strategy is the routine operation and maintenance strategy. The optimal presentation view type for this routine operation and maintenance strategy is the call traffic scatter view. Therefore, the operation and maintenance system can recommend the call traffic scatter view as the display view to the user.

[0220] like Figure 8 As shown, the twin screen of the second floor is displayed in the call traffic scatter view on the operation and maintenance software's display interface 600. The call traffic scatter view displays the dot markers 610 of the communication devices that have generated call traffic.

[0221] It's understandable that 13:00-14:00 is typically employees' lunch break time, during which time equipment in the park enters a dormant state, call volume decreases, and many scattered calls disappear. For example... Figure 9As shown, when the operation and maintenance system plays to 13:00, the twin screen of the second floor is displayed in the logical cell view on the operation and maintenance software's display interface 600. This logical cell view displays a small number of dot markers 610 for communication devices that are experiencing call volume. Figure 8 Most of the dots representing the communication devices that generate call volume shown in Figure 610 have disappeared.

[0222] Optionally, the display of the identifiers for communication devices with high call volume and those with low call volume can be different.

[0223] like Figure 10 As shown, when the operation and maintenance system plays the operation and maintenance event 611 "Fault Self-Repair" that occurred at 14:30, the operation and maintenance system can detect a fault in indoor base station 2 based on the monitoring data during the time period of operation and maintenance event 611. At this time, it can be assumed that the operation and maintenance system is monitoring or performing operation and maintenance with the intention of adaptive blind spot compensation during the time period of operation and maintenance event 611. Therefore, the operation and maintenance system can determine that the corresponding processing strategy for operation and maintenance event 611 is an adaptive blind spot compensation strategy, and the optimal presentation view type corresponding to this adaptive blind spot compensation strategy is the signal strength view. Thus, the operation and maintenance system can recommend the signal strength view as the display view to the user.

[0224] like Figure 10 As shown, the twin view 603 of the second floor is displayed in the signal strength view on the operation and maintenance software's display interface 600. This signal strength view displays a gridded map of the second floor. The signal strength of each grid can be filled with a different color to indicate its position. At the same time, the information 612 of the indoor base station 2 that has failed can be highlighted in this signal strength view.

[0225] Optionally, the signal strength view can display the coverage area of ​​each indoor base station using multiple grids. When an indoor base station fails, the area around the failed base station may not be displayed in the signal strength view to represent the scenario of no signal coverage for the failed base station. Optionally, the area around the failed indoor base station may also display a grid of weak signal strength to represent the scenario of weak signal coverage for the failed base station.

[0226] Optionally, when the operation and maintenance system monitors or performs operation and maintenance using an adaptive coverage strategy, it can adjust the transmission power of other indoor base stations (such as indoor base station 1 and indoor base station 3) around the faulty indoor base station 2 to achieve emergency signal coverage. Thus, when the operation and maintenance system plays the operation and maintenance event 611 "Fault Self-Repair" that occurred at 14:30, the system recommends a signal strength view to the user, allowing the user to see the system's adaptive coverage process. This process begins with a decrease in the number of covered grids or a weakening of the signal strength around the faulty indoor base station 2, and then increases the number of covered grids or strengthens the signal strength around indoor base stations 1 and 3 to cover the area surrounding the faulty indoor base station 2.

[0227] In some scenarios, when the optimal view type recommended by the operations and maintenance system does not meet the user's needs, the user can manually specify the view type. For example... Figure 11 As shown, the display interface 600 of the operation and maintenance software includes a view selection control 613. This view selection control 613 can display the best presentation view type automatically recommended by the operation and maintenance system—the route view—to prompt the user that the current route view is the presentation view automatically recommended by the operation and maintenance system. When the user needs to switch to another presentation view type, the user can click on the view selection control 613 to trigger the display of a drop-down selection page 614. The user can select a view type from the multiple view type options provided in the drop-down selection page 614.

[0228] Optionally, when a user manually switches view types, the switched view type and corresponding processing strategy can be recorded to track the frequency of user switching. If the switching frequency of the view type for events corresponding to the target processing strategy reaches a preset frequency, and the number of times the switched view type is the same view type (such as the target view type) reaches a preset number, the operation and maintenance system can bind the switched target view type to the target processing strategy and store it in the aforementioned preset mapping between processing strategies and view types. Thus, when the operation and maintenance system subsequently presents an event, if the processing strategy corresponding to that event is the target processing strategy, the system can automatically use the target view type as the recommended view type to present the monitoring screen for that event.

[0229] In one approach, the operation and maintenance system can directly replace the original correspondence between the target processing strategy and the target view type in the aforementioned preset correspondence between processing strategies and view types with the correspondence between the target view type and the target processing strategy after the switch.

[0230] Alternatively, the operations and maintenance system can combine the original correspondence between the target processing strategy and the target view type in the aforementioned preset correspondence between processing strategies and view types with the correspondence between the target view type and the target processing strategy after the switch. That is, the target processing strategy can correspond to two recommended view types. In this way, when the operations and maintenance system subsequently presents an event, if the processing strategy corresponding to that event is the target processing strategy, the system can automatically present the monitoring screen of that event using these two recommended view types. Optionally, the monitoring screens presented by the two recommended view types can be displayed in a split-screen format or switched between them.

[0231] It is understood that the business monitoring method provided in this application can automatically recommend the best presentation view matching the operation and maintenance scenario or event to the user based on the monitoring data or operation and maintenance data of that specific time period when the operation and maintenance system retraces the operation and maintenance scenario or event within that specific time period. Thus, during long-term or continuous monitoring, different best presentation views can be automatically recommended based on the operation and maintenance scenario or event in different time periods, achieving a continuous and natural view switching effect. This reduces user operation costs while also reducing information acquisition costs, improving monitoring efficiency, and meeting the diverse monitoring needs of operation and maintenance personnel.

[0232] It is understood that, in order to achieve the above-mentioned functions, electronic devices include hardware and / or software modules that perform the respective functions. Based on the algorithmic steps of the examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.

[0233] This embodiment can divide the electronic device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0234] This application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the electronic device performs the various functions or steps performed by the operation and maintenance system in the above-described method embodiments.

[0235] This application also provides a business monitoring device. This device is used to execute various functions or steps performed by the operation and maintenance system in the above method embodiments.

[0236] This application also provides a chip system including at least one processor and at least one interface circuit. The processor and the interface circuit are interconnected via lines. The interface circuit can read instructions stored in a memory and send the instructions to the processor. When the instructions are executed by the processor, the electronic device can perform various functions or steps performed by the operation and maintenance system in the above method embodiments. Of course, the chip system may also include other discrete devices, and this application does not specifically limit this.

[0237] This application also provides a computer-readable storage medium including computer instructions that, when executed on the aforementioned operation and maintenance system, cause the operation and maintenance system to perform various functions or steps performed by the operation and maintenance system in the above method embodiments.

[0238] This application also provides a computer program product that, when run on an operation and maintenance system, causes the operation and maintenance system to perform various functions or steps performed by the operation and maintenance system in the above method embodiments.

[0239] In this embodiment, the electronic device, business monitoring device, computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0240] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0241] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0242] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0243] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0244] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0245] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A business monitoring method, characterized in that, The method includes: When it is necessary to display the monitoring screen of the first event, determine that the recommended view type for the first event is the first view type; The monitoring screen of the first event is presented in the first view type; When it is necessary to display the monitoring screen of the second event, the recommended view type for the second event is determined to be the second view type, wherein the second event is different from the first event and the second view type is different from the first view type; The monitoring screen of the second event is presented in the second view type; Displaying a first interface, the first interface including a first control, the first control being used to set at least one processing strategy for presentation, the method further including: responding to a first operation by a user on the first control, determining the presented processing strategy as a first processing strategy and a second processing strategy based on the first operation; presenting a monitoring screen for a first time period in the first interface, the monitoring screen for the first time period being used to present monitoring screens of at least one event corresponding to the first processing strategy and monitoring screens of at least one event corresponding to the second processing strategy; wherein, the at least one event corresponding to the first processing strategy includes the first event, and the at least one event corresponding to the second processing strategy includes the second event. The first interface further includes a second control, which is used to set the view type to be presented; in response to a second operation by the user on the second control, the view type to be presented is determined to be a third view type according to the second operation; and the monitoring screen of the first event is presented in the third view type.

2. The method according to claim 1, characterized in that, The step of determining that the recommended view type for the first event is the first view type includes: Determine a first processing strategy for the first event; Based on the first processing strategy and the preset correspondence between processing strategies and view types, determine the first view type corresponding to the first processing strategy; The first view type is determined as the recommended view type for the first event; The step of determining the recommended view type for the second event as the second view type includes: Determine a second handling strategy for the second event; Based on the second processing strategy and the preset correspondence between processing strategies and view types, determine the second view type corresponding to the second processing strategy; The second view type is determined as the recommended view type for the second event.

3. The method according to claim 2, characterized in that, Determining the first processing strategy for the first event includes: Obtain the first monitoring data of the first event; Based on the first monitoring data, a first processing strategy for the first event is determined; The determination of the second processing strategy for the second event includes: Obtain the second monitoring data for the second event; Based on the second monitoring data, a second handling strategy is determined for the second event.

4. The method according to claim 2 or 3, characterized in that, The preset processing strategy and view type correspondence includes: When the processing strategy is an adaptive energy-saving strategy, the corresponding view type is a route view; or When the processing strategy is an adaptive blind spot filling strategy, the corresponding view type is a signal strength view; or When the processing strategy is an adaptive capacity strategy, the corresponding view type is a logical cell view; or When the processing strategy is a conventional strategy, the corresponding view type is a call scatter view.

5. The method according to claim 1, characterized in that, The step of determining that the recommended view type for the first event is the first view type includes: Based on the first event and the preset correspondence between events and view types, determine the first view type corresponding to the first event; The first view type is determined as the recommended view type for the first event; The step of determining the recommended view type for the second event as the second view type includes: Based on the second event and the preset correspondence between events and view types, determine the second view type corresponding to the second event; The second view type is determined as the recommended view type for the second event.

6. The method according to any one of claims 1-3 and 5, characterized in that, The first interface displays the monitoring footage for a first time period, which is used to display the monitoring footage of the first event and the monitoring footage of the second event.

7. The method according to any one of claims 1-3 and 5, characterized in that, The method further includes: The second interface is displayed, which shows a real-time monitoring screen; The monitoring screen that needs to be presented for the first event includes: Upon detecting the occurrence of the first event, it is determined that the monitoring screen of the first event needs to be displayed on the second interface; The monitoring screen that needs to display the second event includes: When the second event is detected, it is determined that the monitoring screen of the second event needs to be displayed on the second interface.

8. The method according to any one of claims 1-3 and 5, characterized in that, The method further includes: When it is necessary to present the monitoring screen of a scenario without events, the recommended view type for the scenario without events is determined to be the fourth view type. The monitoring screen of the event-free scenario is presented in the fourth view type.

9. The method according to claim 8, characterized in that, The step of determining the recommended view type for the event-free scenario as the fourth view type includes: Determine a third processing strategy for the event-free scenario; Based on the third processing strategy and the preset correspondence between processing strategies and view types, determine the fourth view type corresponding to the third processing strategy; The fourth view type is determined as the recommended view type for the event-free scenario.

10. The method according to claim 9, characterized in that, The determination of the third processing strategy for the event-free scenario includes: Obtain third-party monitoring data for the event-free scenario; Based on the third monitoring data, a third processing strategy is determined for the event-free scenario.

11. A business monitoring device, characterized in that, The device includes a memory and one or more processors; the memory and the processors are coupled; the memory is used to store computer program code, the computer program code including computer instructions, and when the processor executes the computer instructions, the device performs the method as described in any one of claims 1-10.

12. A computer-readable storage medium, characterized in that, Includes computer instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-10.

13. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1-10.

Images