Traffic congestion analysis method and communication apparatus

Abstract

A traffic congestion analysis method and a communication apparatus. The method comprises: receiving a first message, wherein the first message is used for requesting the execution of a management data analysis (MDA) task, the first message comprises an analysis type, and the analysis type is traffic congestion analysis; and sending a second message, wherein the second message comprises a traffic congestion analysis result. By means of the method, an MDA consumer can be aware of traffic congestion in a timely manner and thus can implement optimization measures, thereby effectively improving the user experience.

Description

Traffic congestion analysis method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on February 8, 2024, with application number 202410178163.2 and application name “Method and Communication Device for Traffic Congestion Analysis”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and more particularly, to a method and a communication device for analyzing traffic congestion. Background Art

[0003] Traffic congestion is a significant issue in mobile communication networks. It can severely impact network quality, potentially preventing devices from accessing the network, making it difficult to initiate or receive calls, and sending short messages. Traffic congestion typically develops over time. As traffic grows to a certain level, user experience deteriorates significantly, leading to user complaints. Excessive congestion can also severely impact network reputation. Therefore, rapidly detecting traffic congestion has become a pressing issue for network operators. Summary of the Invention

[0004] The present application provides a method and a communication device for analyzing traffic congestion, which can timely perceive traffic congestion.

[0005] In a first aspect, a method for analyzing traffic congestion is provided. The method can be performed by a first management device or a component of the first management device (e.g., a chip, a chip system, or a circuit), and this application does not limit this. For example, the first management device is the management device corresponding to the producer of the MDA.

[0006] The method may include: receiving a first message for requesting execution of a management data analysis (MDA) task, the first message including an analysis type, which is traffic congestion analysis; and sending a second message including a traffic congestion analysis result.

[0007] In the above technical solution, by introducing the scenario type of traffic congestion analysis into the management data analysis function, MDA producers can help MDA consumers to perceive traffic congestion in a timely manner, thereby implementing optimization measures and effectively improving user experience.

[0008] In some implementations of the first aspect, the first message includes policy information, the policy information including at least one of first information and second information, the first information being used to identify burst traffic congestion, and the second information being used to identify non-burst traffic congestion.

[0009] In the above technical solution, the first information and / or the second information are carried in the first message, so that the MDA producer can perform an analysis of sudden traffic congestion based on the first information (i.e., identify sudden congestion scenarios) and perform an analysis of non-sudden traffic congestion based on the second information (i.e., identify non-sudden congestion scenarios / daily congestion scenarios).

[0010] In certain implementations of the first aspect, the first information or the second information includes analysis parameters, and the analysis parameters include at least one of an average user number threshold, a physical resource block (PRB) utilization threshold, a downlink user rate threshold, an average user number deviation threshold, and a downlink PRB utilization deviation threshold.

[0011] In the above technical solution, collaborative analysis can be performed based on the configured analysis parameters, that is, it is determined whether the configured analysis parameters are met at the same time, and whether it is a real congestion scenario is determined based on the judgment result.

[0012] In certain implementations of the first aspect, the first message further includes third information, where the third information indicates an applicable scope of the policy information.

[0013] Based on the above technical solution, different policy information can be configured for different ranges, increasing the flexibility of traffic congestion analysis. For example, the third information may include a cell identifier list, a carrier bandwidth identifier list, or a base station identifier list. In certain implementations of the first aspect, the traffic congestion analysis results include a traffic congestion type, which can be bursty or non-bursty. Based on the above technical solution, the MDA consumer can implement different optimization measures for different congestion scenarios based on the traffic congestion type indicated in the traffic congestion analysis results, thereby effectively improving the user experience.

[0014] In certain implementations of the first aspect, the traffic congestion analysis result includes at least one of the following analysis results: traffic congestion status, traffic congestion level, traffic congestion area information, and recommended optimization measures for traffic congestion, wherein the traffic congestion status is potential congestion, actual congestion, or congestion disappearance.

[0015] Based on the above technical solutions, MDA consumers can provide precise optimization measures based on more types of analysis results, thereby effectively improving user experience.

[0016] In certain implementations of the first aspect, the recommended optimization measures include recommended optimization measures for burst traffic congestion and recommended optimization measures for non-burst traffic congestion, wherein the recommended optimization measures for burst traffic congestion include at least one of the following optimization measures: performing mobile robustness optimization MRO, performing mobile load balancing MLB, and performing coverage capacity optimization CCO; the recommended optimization measures for non-burst traffic congestion include at least one of the following optimization measures: performing MRO, performing MLB, performing CCO, adding sectors, and adding base stations.

[0017] In certain implementations of the first aspect, the method further includes: receiving a third message, the third message including an optimization measure for traffic congestion, and the third message instructing execution of the optimization measure.

[0018] In the above technical solution, after the MDA producer sends the traffic congestion analysis result, the MDA consumer can indicate to the MDA producer the optimization measures that need to be implemented based on the traffic congestion analysis result, thereby effectively improving the user experience.

[0019] In some implementations of the first aspect, the first message further includes analysis result request information, where the analysis result request information is used to request a specific analysis result.

[0020] In the above technical solution, the MDA consumer can instruct the MDA producer to report the required specific analysis results, thereby improving the experience of the MDA consumer.

[0021] In a second aspect, a method for analyzing traffic congestion is provided. This method can be performed by a second management device or a component of the second management device (e.g., a chip, a chip system, or a circuit), which is not limited in this application. It is understood that the second management device is the management device corresponding to the MDA consumer.

[0022] The method may include: sending a first message, the first message being used to request execution of a management data analysis (MDA) task, the first message including an analysis type, which is traffic congestion analysis; and receiving a second message including a traffic congestion analysis result.

[0023] For the beneficial effects of the second aspect, please refer to the description of the first aspect and will not be repeated here.

[0024] In some implementations of the second aspect, the first message includes policy information, the policy information including at least one of first information and second information, the first information being used to identify burst traffic congestion, and the second information being used to identify non-burst traffic congestion.

[0025] In certain implementations of the second aspect, the first information or the second information includes analysis parameters, and the analysis parameters include at least one of an average user number threshold, a physical resource block PRB utilization threshold, a downlink user rate threshold, an average user number deviation threshold, and a downlink PRB utilization deviation threshold.

[0026] In certain implementations of the second aspect, the first message further includes third information, where the third information indicates an applicable scope of the policy information.

[0027] In certain implementations of the second aspect, the traffic congestion analysis result includes a traffic congestion type, where the traffic congestion type is burst traffic congestion or non-burst traffic congestion.

[0028] In certain implementations of the second aspect, the traffic congestion analysis result includes at least one of the following analysis results: traffic congestion status, traffic congestion level, traffic congestion area information, and recommended optimization measures for traffic congestion, wherein the traffic congestion status is potential congestion, actual congestion, or congestion disappearance.

[0029] In certain implementations of the second aspect, the recommended optimization measures include recommended optimization measures for burst traffic congestion and recommended optimization measures for non-burst traffic congestion, wherein the recommended optimization measures for burst traffic congestion include at least one of the following optimization measures: performing mobile robustness optimization MRO, performing mobile load balancing MLB, and performing coverage capacity optimization CCO; the recommended optimization measures for non-burst traffic congestion include at least one of the following optimization measures: performing MRO, performing MLB, performing CCO, adding sectors, and adding base stations.

[0030] In certain implementations of the second aspect, the method further includes: determining a third message based on the traffic congestion analysis result, the third message including optimization measures for the traffic congestion, and the third message instructing execution of the optimization measures; and sending the third message.

[0031] In certain implementations of the second aspect, the first message further includes analysis result request information, where the analysis result request information is used to request a specific analysis result.

[0032] In a third aspect, a communication device is provided, the device being configured to execute the method provided in the first or second aspect. Specifically, the device may include units and / or modules, such as a processing unit and / or a communication unit, for executing the method provided in any of the above implementations of the first or second aspect.

[0033] In one implementation, the apparatus is a management device (e.g., a first management device or a second management device). When the apparatus is a management device, the communication unit may be a transceiver or an input / output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0034] In another implementation, the apparatus is a chip, chip system, or circuit for managing a device. When the apparatus is a chip, chip system, or circuit used in a device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0035] In a fourth aspect, a communication device is provided, comprising: at least one processor configured to execute the method provided in any one of the above-mentioned implementations of the first aspect or the second aspect.

[0036] Optionally, the device further includes: a memory for storing programs; accordingly, at least one processor is used to execute computer programs or instructions stored in the memory.

[0037] Optionally, the device further includes a communication interface, which is coupled to the processor and can be used to input information to the processor or output information from the processor.

[0038] In one implementation, the apparatus is a management device (such as a first management device or a second management device).

[0039] In another implementation, the apparatus is a chip, a chip system, or a circuit for managing a device.

[0040] In a fifth aspect, the present application provides a processor for executing the methods provided in the above aspects.

[0041] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as operations such as processor output and input, or as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0042] In a sixth aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a method provided in any implementation manner of the first or second aspect above.

[0043] In a seventh aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method provided in any one of the implementations of the first or second aspect.

[0044] In an eighth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface and executes the method provided by any implementation of the first or second aspect.

[0045] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is used to execute the method provided in any implementation method of the first aspect or the second aspect above.

[0046] In a ninth aspect, a communication system is provided, comprising a first management device and a second management device, wherein the first management device is configured to execute the method provided in any one of the implementations of the first aspect, and the second management device is configured to execute the method provided in any one of the implementations of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] FIG1 is a schematic diagram of a system architecture 100 suitable for use in the present application.

[0048] FIG2 is a schematic flow chart of a method 200 for analyzing traffic congestion proposed in this application.

[0049] FIG3 is a schematic block diagram of a communication device 300 provided in an embodiment of the present application.

[0050] FIG4 is a schematic diagram of another communication device 400 provided in an embodiment of the present application.

[0051] FIG5 is a schematic diagram of a chip system 500 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0053] Before introducing the embodiments of the present application, the following points are first explained.

[0054] 1. In the description of the embodiments of the present application, unless otherwise specified, “multiple” means two or more.

[0055] 2. In the various embodiments of the present application, unless otherwise specified or provided for by logic, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0056] 3. The various numerical numbers involved in this application are only used for the convenience of description and are not used to limit the scope of this application. The size of the serial numbers involved in this application does not mean the order of execution. The execution order of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third" and various other terminology labels in the specification, claims and drawings of this application are used to distinguish similar objects and are not used to limit the size, content, order, timing, priority or importance of multiple objects. For example, the first information and the second information do not indicate differences in the amount of information, content, priority or importance.

[0057] 4. The terms "comprise", "include", "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.

[0058] 5. In each embodiment of the present application, "network element A sends information A to network element B" can be understood as the destination end of the information A or the intermediate network element in the transmission path between the destination end and the network element B, which may include directly or indirectly sending information to network element B. "Network element B receives information A from network element A" can be understood as the source end of the information A or the intermediate network element in the transmission path between the source end and the network element A, which may include directly or indirectly receiving information from network element A. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in this application can be understood similarly and will not be elaborated here.

[0059] In other words, sending and receiving can be performed between devices, for example, between terminal device #1 and terminal device #2, or can be performed within a device, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, traces or interface.

[0060] 6. In the embodiments of the present application, indications include direct indications (also called explicit indications) and implicit indications. Direct indication of information A refers to including information A; implicit indication of information A refers to indicating information A through the correspondence between information A and information B and the direct indication of information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured.

[0061] 7. In the embodiments of the present application, information C is used to determine information D, which includes information D being determined solely based on information C, as well as information D being determined based on information C and other information. Furthermore, information C can also be used to determine information D indirectly, for example, where information D is determined based on information E, and information E is determined based on information C.

[0062] 8. "Storage" or "saving" in the embodiments of this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be provided in part separately and in part integrated into a decoder, a processor, or a communication device. The type of memory may be any form of storage medium and is not limited in this application.

[0063] 9. The dotted arrows or boxes in the schematic diagrams in the accompanying drawings of this application specification represent optional steps or optional modules.

[0064] The technical solutions of the embodiments of the present application can be applied to various communication systems, including but not limited to: the 5th generation (5G) system or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc. The technical solutions provided in the present application can also be applied to future communication systems, such as the sixth generation mobile communication system. In addition, it can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication system or other communication systems, etc., which are not limited in this article.

[0065] Figure 1 is a schematic diagram of a service management architecture 100 applicable to the present application. Architecture 100 includes a service operation system 110, a cross-domain management function (CD-MnF) 120, a domain management function (Domain-MnF) 130, and a network element 140. The functions of each component are described below.

[0066] 1) The business operation system 110 is used to provide business operation functions, including: service issuance, service assurance, service scheduling, etc. Illustratively, the business operation system 110 may include a business operation system for a vertical industry, or a business operation system of an operator, such as a business support system (BSS) or a system capable of implementing a communication service management function (CSMF).

[0067] 2) The cross-domain management function unit 120, which may also be called a network management function unit (NMF), may be, for example, a network management entity such as a network management system (NMS) or a network function management service consumer (NFMS_C).

[0068] Among them, the cross-domain management function unit 120 provides one or more of the following management functions or management services: network lifecycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, network optimization function and translation of network intent (intent from communication service provider, Intent-CSP) of business producers, etc.

[0069] The network referred to in the above management function or management service may include one or more network elements, or one or more subnetworks. Exemplarily, it may also be a network slice. That is, the network management function unit may be a network slice management function unit (NSMF), or a cross-domain management data analytical function (MDAF) unit, or a cross-domain self-organization network (SON) function or a cross-domain intent driven management service (MnS).

[0070] Optionally, in certain deployment scenarios, the cross-domain management function unit 120 may also provide sub-network lifecycle management, sub-network deployment, sub-network fault management, sub-network performance management, sub-network configuration management, sub-network assurance, sub-network optimization functions, sub-network service producer network intent (Intent-CSP) or sub-network service consumer network intent (intent from communication service consumer, Intent-CSC) translation, etc. The sub-network here is composed of multiple small sub-networks, which can be a network slice sub-network.

[0071] 3) Domain management function unit 130, which may also be referred to as a sub-network management function unit (NMF) or a network element management function unit. For example, domain management function unit 130 may be a network element management entity such as a wireless automation engine (MAE), an element management system (EMS), or a network function management service provider (NFMS_P).

[0072] The domain management function unit 130 provides one or more of the following functions or management services: lifecycle management of sub-networks or network elements, deployment of sub-networks or network elements, fault management of sub-networks or network elements, performance management of sub-networks or network elements, assurance of sub-networks or network elements, optimization of sub-networks or network elements, and translation of intents from network operators (Intent-NOPs) for sub-networks or network elements. The sub-networks mentioned above include one or more network elements. A sub-network may also include sub-networks, i.e., one or more sub-networks form a larger sub-network.

[0073] Optionally, the above-mentioned subnetwork may be a network slice subnetwork. The domain management system may be a network slice subnet management function unit (NSSMF), a domain management data analytical function (MDAF) unit, a domain self-organization network function (SON) function, a domain intent (Intent Driven) management function unit MnS, etc.

[0074] The domain management function unit 130 may be classified by network type or by administrative region.

[0075] According to the network type, it can be divided into: access network domain management function unit (radio access network domain management function, RAN-Domain-MnF), core network domain management function unit (core network domain management function, CN-Domain-MnF), transport network domain management function unit (transport network domain management function, TN-Domain-MnF), etc.

[0076] It should be noted that the domain management functional unit 130 may also be a domain network management system, which can manage one or more of the access network, the core network or the transmission network.

[0077] According to the administrative region classification, it can be divided into: a domain management function unit 130 of a certain region, such as the Shanghai domain management function unit, the Beijing domain management function unit, etc.

[0078] 4) Network element 140 is an entity that provides network services and may include core network elements and access network elements. Core network elements may include access and mobility management function (AMF) elements, session management function (SMF) elements, policy control function (PCF) elements, network data analysis function (NWDAF) elements, network repository function (NRF) elements, gateways, and other devices. An access network element may be a device for communicating with a terminal device. The access network element may also be referred to as an access network device or a wireless access network device. It may be a transmission reception point (TRP), an evolved NodeB (eNB or eNodeB) in an LTE system, a home base station (for example, home evolved NodeB, or home Node B, HNB), a base band unit (BBU), or a wireless controller in a cloud radio access network (CRAN) scenario. The access network element may be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a 5G network, or a network device in a future evolved public land mobile network (PLMN) network, etc. It may be an access point (AP) in a wireless local area network (WLAN), or a gNB in ​​a new radio system (NR) system. The embodiments of the present application are not limited thereto. In a network structure, the access network element may include a centralized unit (CU) node, a distributed unit (DU) node, a radio access network (RAN) device including a CU node and a DU node, or a RAN device including a control plane CU node (CU-CP node) and a user plane CU node (CU-UP node) and a DU node.

[0079] Among them, network element 140 can provide one or more of the following management functions or management services: network element lifecycle management, network element deployment, network element fault management, network element performance management, network element assurance, network element optimization function and network element intent translation, etc.

[0080] For example, if the management service is a management service provided by the cross-domain management function unit 120 , the cross-domain management function unit 120 is a management service producer, and the business support system 110 is a management service consumer.

[0081] For example, if the management service is a management service provided by the domain management function unit 130 , the domain management function unit 130 is a management service producer, and the cross-domain management function unit 120 is a management service consumer.

[0082] For example, if the management service is a management service provided by the network element 140 , the network element 140 is a management service producer, and the domain management function unit 130 is a management service consumer.

[0083] The aforementioned functions related to managing service consumers and managing service producers can be implemented through a management device. For example, all functions related to managing service consumers and managing service producers can be integrated into the management device via software. For ease of description, this application refers to the network entity corresponding to the management service producer as the first management device, and the network entity corresponding to the management service consumer as the second management device. However, it should be understood that the aforementioned network entities may also have other names, and this embodiment of the application does not limit this.

[0084] Optionally, the system architecture 100 may also include other network entities such as a network controller and a mobility management entity, but the embodiments of the present application are not limited thereto.

[0085] To facilitate understanding of the solutions of the embodiments of the present application, the terms that may be involved in the embodiments of the present application are explained below.

[0086] (1) Management Data Analytics (MDA): MDA is a key enabler of automation and intelligence and is considered a fundamental capability for mobile network and service management. MDA provides the ability to process and analyze data related to the status of network and service events, including performance measurements, key performance indicators (KPIs), quality of experience (QoE) reports, alarms, configuration data, network analysis data, etc., to provide analytical outputs. This includes statistical or predictive root cause analysis of problems, and may also include recommendations for enabling necessary actions for network and service operations. MDA outputs are provided by management data analytics service (MDAS) producers to consumers requesting analysis. MDA can identify ongoing issues that affect network and service performance and help identify potential issues that may lead to potential failures and / or performance degradation in advance. MDA can also help predict network and service requirements to enable timely resource allocation and deployment, thereby achieving rapid network and service deployment. MDA, combined with artificial intelligence (AI) and machine learning (ML) technologies, can bring intelligence and automation to network service management and coordination. MDAS can be used by various consumers, such as MnF (i.e., MnS service producer / consumer for network and service management), network function (NF) (e.g., NWDAF), SON function, network and service optimization tools / functions, service level specification (SLS) assurance function, human operators, etc.

[0087] (2) Traffic congestion: The RAN resource demand for transmitting user data exceeds the available RAN capacity for transmitting user data, lasting for several seconds or longer. Traffic congestion can be caused by a variety of factors, such as a sudden increase in users, improper mobility parameter configuration, or unbalanced network traffic load. Traffic congestion can lead to various performance degradations, such as a reduced user experience and insufficient physical resource block (PRB) utilization.

[0088] Traffic congestion typically occurs on an incremental basis. As traffic grows to a certain level, user experience deteriorates significantly, leading to user complaints. Therefore, operators hope to quickly detect traffic congestion and close the loop quickly.

[0089] In view of this, the present application provides a method for analyzing traffic congestion, which can effectively solve the above technical problems. The method proposed in the present application is described in detail below.

[0090] Figure 2 is a schematic flow chart of a method 200 for traffic congestion analysis proposed in this application. This method can be applied to the system architecture 100 shown in Figure 1 , where the first management device is the network entity corresponding to the management service producer, and the second management device is the network device corresponding to the management service consumer. For example, this application describes the MDA service provided by the domain management functional unit as an example. The method includes the following steps.

[0091] S210: The second management device sends a first message to the first management device, the first message being used to request execution of an MDA task and including an analysis type, which is traffic congestion analysis. In response, the first management device receives the first message from the second management device.

[0092] Optionally, the first message includes policy information, and the policy information includes at least one of first information and second information, the first information being used to identify burst traffic congestion, and the second information being used to identify non-burst traffic congestion. It is understood that the first management device can perform burst traffic congestion analysis based on the first information, and the first management device can perform non-burst traffic congestion analysis based on the second information. In this application, the first information may be referred to as a burst traffic congestion identification policy, and the second information may be referred to as a non-burst traffic congestion identification policy. This application does not limit the names of the first information and the second information.

[0093] Non-emergency traffic congestion can be understood as predictable traffic congestion, such as traffic congestion caused by rush hour traffic jams. Sudden traffic congestion can be understood as unpredictable traffic congestion, such as traffic congestion caused by sudden natural disasters or major public health events. In this application, sudden traffic congestion can also be referred to as true traffic congestion, and non-emergency traffic congestion can also be referred to as daily traffic congestion. This application does not limit the terms non-emergency traffic congestion and sudden traffic congestion.

[0094] The analysis type in this application is traffic congestion analysis, which can also be understood as the MDA type being the traffic congestion analysis type.

[0095] Optionally, the first information or the second information includes at least one of the following multiple analysis parameters (also referred to as policy parameters), the multiple policy parameters including at least one of an average number of users threshold, a PRB utilization threshold, a downlink user rate threshold, an average number of users deviation threshold, and a downlink PRB utilization deviation threshold.

[0096] It is understandable that the first management device can perform collaborative analysis based on the analysis parameters configured by the second management device, that is, determine whether the configured analysis parameters are met at the same time, and determine whether it is a real congestion scenario based on the judgment result.

[0097] For example, the above threshold value can be implemented by a data type, which includes a value and a direction, wherein the value represents the threshold value and the direction represents being greater than or less than the threshold value.

[0098] It is understood that a policy parameter includes an indicator information and a threshold information. For example, the policy parameter is average number of users > 100, the indicator information corresponding to the policy parameter is "average number of users", and the corresponding threshold information is ">100". This application does not limit the specific indication method of the policy parameter.

[0099] In one implementation, the indicator information and threshold information corresponding to a policy parameter can be indicated by two attributes. For example, the indication method is shown in Table 1.

[0100] Table 1

[0101] In another implementation, the indicator information and threshold information corresponding to a policy parameter can be indicated by an attribute. For example, the indication method is shown in Table 2.

[0102] Table 2

[0103] It can be understood that the deviation of an indicator (e.g., average number of users deviation, downlink PRB utilization deviation) refers to the offset between the current network value of the indicator and the historical baseline of the indicator. The historical baseline can be obtained from the historical data of the indicator. For example, the deviation can satisfy the following formula: Deviation = (current network value - historical baseline) / historical baseline * 100%. For example, data corresponding to the indicator can be collected within a recent period of time (e.g., within the past week or the first week of the past), and the historical baseline of the indicator can be determined based on the collected historical data, thereby determining the indicator deviation.

[0104] Optionally, the calculation method of the deviation can be customized by the first management device, and this application does not limit it.

[0105] The following example illustrates the policy information, which includes first information and second information. The first information and the second information are as follows.

[0106] For example, the first information includes the following policy parameters:

[0107] (1) Average number of users > 100, downlink PRB utilization > 50%, downlink user rate < 50 Mbps;

[0108] (2) The average number of users deviation threshold is greater than 20%, and the downlink PRB utilization deviation threshold is greater than 20%.

[0109] For example, the second information includes the following policy parameters:

[0110] (1) The average number of users is >150, the downlink PRB utilization is >60%, and the downlink user rate is <50 Mbps.

[0111] (2) The average number of users deviation threshold is less than 10%, and the downlink PRB utilization deviation threshold is less than 10%.

[0112] Optionally, the first message may not include the policy information, and the policy information may be set on the first management device side.

[0113] Optionally, the first message further includes third information, which is used to indicate the applicable scope of the policy information.

[0114] Optionally, the third information may include a cell identifier list, a carrier bandwidth identifier list, or a base station identifier list. For example, if the third information includes a cell identifier list, it indicates that the policy information applies to cells in the cell identifier list. For example, if the third information includes a carrier bandwidth identifier list, it indicates that the policy information applies to cells corresponding to the carrier bandwidths in the carrier bandwidth identifier list.

[0115] Optionally, the first message may include multiple policy information and multiple third information, and the multiple policy information corresponds to the multiple third information in a one-to-one manner. In this solution, different policy information is configured for different ranges, which can improve the flexibility of traffic congestion analysis.

[0116] It can be understood that if the first message does not include the third information, it can be assumed that the policy information is applicable to all carrier bandwidths. It can also be understood that the policy information is applicable to all cells.

[0117] Optionally, the first message may further include congestion analysis time information, instructing the first management device to perform traffic congestion analysis according to a specified time. The specified time may be a time range, a specific time point, or a time interval. For example, the time information may be set to 60 minutes (min), 15 minutes, or 1 minute (i.e., a time interval), or the time information may be peak hours or holidays, or the time information may be 12:00 every day (i.e., a specific time), or the time information may be from 7:00 a.m. to 9:00 a.m. or from 5:00 p.m. to 7:00 p.m. (i.e., a time range).

[0118] Optionally, the first message also includes fourth information indicating whether the first management device needs to generate optimization suggestions for alleviating traffic congestion. If the fourth information indicates yes, the first management device will generate corresponding recommended optimization measures when detecting traffic congestion. If the fourth information indicates no, the first management device does not need to generate recommended optimization measures when detecting traffic congestion.

[0119] Optionally, the first message also includes an analysis scope.

[0120] For example, the analysis range can directly indicate at least one cell or network element (such as a base station) or a specific network area. For example, the cell in the analysis range can be indicated by a global cell identifier (CGI) or a physical cell identifier (PCI) or a cell identifier (cell ID), the base station in the analysis range can be indicated by a base station identifier, and the network area in the analysis range can be indicated by longitude and latitude, or by a cell identifier list (cell identifiers such as PCI, CGI or cell ID) or a base station identifier list.

[0121] For example, the analysis scope indicates at least one geographical area. For example, if the analysis scope is geographical area A, it indicates all cells or network elements managed by the MDA consumers in area A, or indicates specific cells or network elements managed by the MDA consumers in area A.

[0122] Optionally, the first message is an MDA request message. For example, the MDA producer creates a managed object instance (MOI) for the MDA consumer and requests an information object class (IOC) (see the createMOI operation defined in TS 28.532). The MDA consumer uses relevant attributes in the MDA request message in the operation.

[0123] It can be understood that in this application, MDA can also be called MDAS, and correspondingly, MDA producer can also be called MDAS producer.

[0124] In one possible implementation, the MDA request message includes at least one of the multiple attributes shown in Table 3, namely, requestMDAOutputs, reportingMethod, reportingTarget, analyticsScope, startTime, stopTime, and analysisPolicy. For example, the data type of the MDA request output includes at least one of the multiple attributes shown in Table 4, namely, MDA type (mDAType) and MDA output filter elements (mDAOutputIEFilters).

[0125] Optionally, the analysis policy (analysisPolicy) may also be included in the data type of the MDA request output. Furthermore, the analysis policy (analysisPolicy) includes two attributes, namely, a burst traffic congestion policy and a non-burst traffic congestion policy.

[0126] Table 3

[0127] Table 4

[0128] It can be understood that the MDAS producer (i.e., the first management device) can perform MDA tasks according to the MDA type specified in Table 4 (i.e., an example of the analysis type in the first message) and / or the analysis strategy in Table 3 (i.e., an example of the policy information in the first message).

[0129] S220: The first management device sends a second message to the second management device, where the second message includes a traffic congestion analysis result. Correspondingly, the second management device receives the second message from the first management device.

[0130] Optionally, the traffic congestion analysis results include at least one of the following analysis results: traffic congestion type, traffic congestion status, traffic congestion level, traffic congestion area information, and recommended optimization measures for traffic congestion. The traffic congestion type may also be referred to as the traffic congestion problem, which is not limited in this application. The analysis results listed above are described in detail below.

[0131] (1) Traffic congestion type is burst traffic congestion or non-burst traffic congestion.

[0132] It should be noted that only when all the policy parameters in the first information are met can it be considered that burst traffic congestion has occurred. Similarly, only when all the policy parameters in the second information are met can it be considered that non-burst traffic congestion has occurred.

[0133] Optionally, when determining whether a policy parameter is satisfied, the statistical data of the indicator corresponding to the policy parameter may be compared with the threshold value corresponding to the policy parameter. For example, the statistical data may be statistical data for each cell, or statistical data for each base station, or statistical data for each subnet area, or statistical data for each carrier, and this application does not impose any restrictions on this.

[0134] (2) Traffic congestion status is potential congestion, real congestion, or congestion disappearance.

[0135] Optionally, the traffic congestion status also includes congestion duration.

[0136] (3) Traffic congestion levels can be mild, moderate, or severe.

[0137] For example, light congestion, moderate congestion, and severe congestion can be indicated by level #1, level #2, and level #3, respectively. It is understood that the above levels are only exemplary divisions, and more fine-grained divisions can be performed in actual applications.

[0138] Optionally, the traffic congestion level may be customized by the MDA producer, and this application does not impose any restrictions thereon.

[0139] (4) Traffic congestion area information indicates an area where traffic congestion occurs.

[0140] For example, the traffic congestion area information may include at least one of the following information: longitude and latitude information, a cell identifier, an identifier of a network element (eg, a base station), and a carrier bandwidth identifier.

[0141] For example, when traffic congestion occurs in multiple cells, the traffic congestion area information may include a corresponding cell identification information list, or a corresponding base station identification information list, or a corresponding carrier bandwidth identification information list, or a corresponding latitude and longitude information list, etc.

[0142] (5) Recommended optimization measures include recommended optimization measures for sudden traffic congestion and / or recommended optimization measures for non-sudden traffic congestion.

[0143] Optionally, the congestion analysis result also includes the cell identifier or base station identifier to which the recommended optimization measure applies. For example, the congestion analysis result includes recommended optimization measure #1 and the identifier of cell #1 to which recommended optimization measure #1 applies, and recommended optimization measure #2 and the identifier of cell #2 to which recommended optimization measure #2 applies.

[0144] Based on the above analysis results, the MDA consumer can provide different optimization measures for different congestion scenarios based on the traffic congestion type indicated in the traffic congestion analysis results to improve the user experience. Furthermore, the MDA consumer can also provide precise optimization measures based on the analysis results based on other types mentioned above.

[0145] Optionally, the recommended optimization measures for burst traffic congestion include at least one of the following optimization measures: performing mobility robustness optimization (MRO), performing mobility load balancing (MLB), and performing coverage and capacity optimization (CCO).

[0146] Optionally, the recommended optimization measures for non-burst traffic congestion include at least one of the following optimization measures: performing MRO, performing MLB, performing CCO, adding sectors to the base station, and adding base stations.

[0147] For example, performing MRO may include adjusting a cell individual offset (CIO), adjusting a cell time to trigger (TTT), and the like.

[0148] For example, executing MLB may include adjusting CIO, adjusting PRB resource allocation, adjusting load balancing trigger mode, adjusting load balancing user number threshold, adjusting load balancing user number bias, adjusting load balancing direction, etc.

[0149] For example, performing CCO may include adjusting radio frequency parameters and beam parameters. Further, adjusting radio frequency parameters may include adjusting downtilt angle, azimuth angle, base station transmit power, and power offset.

[0150] Optionally, the second management device may authorize the first management device to directly execute the recommended optimization measures determined by the first management device without informing the second management device.

[0151] Optionally, the first message also includes analysis result request information, which is used to request a specific analysis result. In this manner, the MDA consumer can instruct the MDA producer to report a specific analysis result, improving the MDA consumer experience. For example, if the specific analysis result is a traffic congestion type, the first management device can determine whether burst traffic congestion or non-burst traffic congestion occurs based on the obtained network element measurement data and policy information.

[0152] Optionally, if the first message does not include analysis result requirement information, the first management device determines a traffic congestion analysis result based on the acquired network element measurement data. The traffic congestion analysis result may include all default analysis results. For example, the traffic congestion analysis result includes the traffic congestion type, traffic congestion status, traffic congestion level, traffic congestion area information, and recommended optimization measures for traffic congestion.

[0153] It can be understood that the MDA output filter element in Table 4 is a possible specific example of the above analysis result requirement information, wherein the specific analysis result requested by the analysis result requirement information is the filter element corresponding to the MDA output filter element.

[0154] Optionally, the second message includes a traffic congestion analysis report, which includes a traffic congestion analysis result.

[0155] In one possible implementation, the traffic congestion analysis report includes at least one of the multiple attributes shown in Table 5, namely, MDA type (mDAType), MDA output list (mdaOutputList), MDA request identifier (mDARequestRef), and analysis window (analyticsWindow). The MDA output list includes at least one of the multiple attributes shown in Table 6, namely, traffic congestion type, traffic congestion status, traffic congestion level, traffic congestion area, traffic congestion start time, traffic congestion end time, and recommended optimization measures.

[0156] Table 5

[0157] Based on the definition of the MDA output list in Table 5, the MDA output list can be expressed using the names of analysis output parameters and their corresponding values. The parameter names here can be the attribute names in Table 6, and the corresponding values ​​can be at least one of the multiple values ​​corresponding to the attribute names. For example, if the MDA output list includes a traffic congestion type, the corresponding value can be "burst traffic congestion." For another example, if the MDA output list includes a traffic congestion area, the corresponding values ​​can be "cell #1" to "cell #5."

[0158] Optionally, if the second management device expects the first management device to perform some optimization measures after obtaining the traffic congestion analysis result, the method further includes S230 and S240.

[0159] S230: The second management device determines a third message based on the traffic congestion analysis result, where the third message includes an optimization measure for the traffic congestion and indicates to execute the optimization measure.

[0160] It is understood that the MDA consumer can determine the optimization measures that need to be implemented based on the traffic congestion analysis results, thereby effectively improving the user experience. For example, the optimization measures in the third message can be optimization measures independently determined by the second management device based on the traffic congestion analysis results, and / or can be optimization measures selected by the second device management device from the recommended optimization measures reported by the first management device. This application is not limited to this.

[0161] S240: The second management device sends a third message to the first management device. Correspondingly, the first management device receives the third message from the second management device and executes the optimization measure in the third message.

[0162] Optionally, before S220, the method further includes S250.

[0163] S250: The first management device performs MDA configuration based on the first message.

[0164] It is understood that configuration here refers to configuring the information or parameters contained in the first message in the first management device (or writing them into the first management device). For example, based on the first message, the MDA type of the first management device is configured to traffic congestion analysis, and based on the policy parameters in the policy information in the first message, the parameters corresponding to the traffic congestion analysis policy of the first management device are modified.

[0165] It is understood that the traffic congestion analysis result in S220 is determined by measuring data of network elements (eg, base stations or cells) within the analysis range. For example, the network elements are cells within the analysis range in S210. Optionally, the method further includes S260 to S280.

[0166] S260: The first management device sends a fourth message to the network element, the fourth message including at least one measurement indicator, and the fourth message is used to request the network element to perform measurement based on the at least one measurement indicator. Correspondingly, the network element receives the fourth message from the first management device.

[0167] It can be understood that the at least one measurement indicator is determined based on the first message. For example, the first message includes information #1 (information #1 is the first information or the second information), then the at least one measurement indicator includes the indicator corresponding to the analysis parameter in information #1. For another example, the first message includes the first information and the second information, then the at least one measurement indicator includes the indicator corresponding to the analysis parameter in the first information and the second information. For another example, if the first message does not carry the first information and the second information, then the at least one measurement indicator includes the indicator corresponding to the analysis parameter in the first information and the second information set (or defaulted) by the first management device.

[0168] S270: The first management device receives a fifth message from the network element, where the fifth message includes measurement data of the network element.

[0169] It can be understood that the measurement data here is data obtained by measuring the network element based on at least one measurement indicator included in the fourth message.

[0170] Optionally, if the fourth message is also used to request the network element to report the current network configuration of the network element, the fifth message also includes the current network configuration of the network element. For example, the network configuration includes at least one of the following configurations: bandwidth, mobility load balancing (MLB) parameters, L3 handover parameters, coverage scenario, synchronization signal block (synchronization signal and PBCH block, SSB) power offset, etc.

[0171] For example, the first management device may carry the obtained network configuration in the second message, and then the second management device may instruct the first management device to adjust the current network configuration based on the received traffic congestion analysis result.

[0172] For example, the first management device may determine a recommended optimization measure based on the acquired current network configuration, where the recommended optimization measure indicates adjusting the current network configuration, and then carry the recommended optimization measure in the second message.

[0173] S280: The first management device determines a traffic congestion analysis result based on the fifth message.

[0174] For specific information included in the traffic congestion analysis result, please refer to the description in S220 and will not be repeated here.

[0175] It can be understood that the method proposed in this application can be applied in the field of wireless network operation and maintenance, including but not limited to network management, network performance optimization and other operation and maintenance activities.

[0176] It can also be understood that the size of the serial numbers of the above-mentioned processes does not mean 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 embodiment of this application.

[0177] It is also understood that in some of the above embodiments, devices in existing network architectures are mainly used as examples for illustrative purposes. It is understood that the embodiments of the present application do not limit the specific form of the devices. For example, devices that can achieve the same functions in the future are applicable to the embodiments of the present application.

[0178] It is understandable that in the above-mentioned various method embodiments, the methods and operations implemented by the management device (such as the first management device and the second management device) may also be implemented by components of the device (such as chips or circuits).

[0179] The method provided in the embodiments of the present application is described in detail above in conjunction with Figures 1 and 2 . The method is primarily described from the perspective of the interaction between the first management device and the second management device. It is understood that, in order to implement the aforementioned functions, the first management device and the second management device include hardware structures and / or software modules corresponding to the respective functions.

[0180] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0181] Below, the communication device provided by the embodiment of the present application is described in conjunction with Figures 3 and 4. It can be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for the content that is not described in detail, please refer to the above method embodiment. For the sake of brevity, some content will not be repeated. The embodiment of the present application can divide the functional modules of the device according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.

[0182] The method provided in this application has been described in detail above. The following describes the communication device provided in this application. In one possible implementation, the device is used to implement the steps or processes corresponding to the first management device in the above method embodiment. In another possible implementation, the device is used to implement the steps or processes corresponding to the second management device in the above method embodiment.

[0183] Figure 3 is a schematic diagram of a communication device 300 provided in an embodiment of the present application. Transceiver unit 310 is provided. Transceiver unit 310 can be used to implement corresponding communication functions. Transceiver unit 310 can also be referred to as a communication interface or communication unit. Optionally, the device 300 also includes a processing unit 320 for processing.

[0184] Optionally, the device 300 may further include a storage unit, which may be used to store instructions and / or data. The processing unit 320 may read the instructions and / or data in the storage unit so that the device implements the aforementioned method embodiment.

[0185] In a first possible design, the apparatus 300 may be the first management device in the aforementioned embodiment, and the apparatus 300 may implement the steps or processes corresponding to those performed by the first management device in the above method embodiment. The transceiver unit 310 may be configured to perform transceiver-related operations (such as operations of sending and / or receiving data or messages) of the first management device in the above method embodiment, and the processing unit 320 may be configured to perform processing-related operations of the first management device in the above method embodiment, or operations other than transceiver operations (such as operations other than sending and / or receiving data or messages).

[0186] In one possible implementation, the transceiver unit 310 is used to receive a first message, where the first message is used to request the execution of a management data analysis (MDA) task, and the first message includes an analysis type, which is a traffic congestion analysis. The transceiver unit 310 is also used to send a second message, where the second message includes a traffic congestion analysis result.

[0187] Optionally, the processing unit 320 is configured to determine a traffic congestion analysis result.

[0188] Optionally, the transceiver unit 310 is further configured to receive a third message, the third message including optimization measures for traffic congestion, and the third message instructs execution of the optimization measures; the processing unit 320 is configured to execute the optimization measures.

[0189] In a second possible design, the apparatus 300 may be the second management device in the aforementioned embodiment, and the apparatus 300 may implement the steps or processes corresponding to those performed by the second management device in the above method embodiment. The transceiver unit 310 may be configured to perform transceiver-related operations (such as operations of sending and / or receiving data or messages) of the second management device in the above method embodiment, and the processing unit 320 may be configured to perform processing-related operations of the second management device in the above method embodiment, or operations other than transceiver operations (such as operations other than sending and / or receiving data or messages).

[0190] In one possible implementation, the transceiver unit 310 is used to send a first message, where the first message is used to request the execution of a management data analysis (MDA) task, and the first message includes an analysis type, which is a traffic congestion analysis. The transceiver unit 310 is also used to receive a second message, where the second message includes a traffic congestion analysis result.

[0191] Optionally, the processing unit 320 is configured to determine a third message based on the traffic congestion analysis result, where the third message includes optimization measures for the traffic congestion and instructs execution of the optimization measures; the transceiver unit 310 is further configured to send the third message.

[0192] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0193] It should also be understood that the device 300 here is embodied in the form of a functional unit. The term "unit" here can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art can understand that the device 300 can be specifically the management device in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the management device in the above-mentioned method embodiments. To avoid repetition, they will not be described here.

[0194] The apparatus 300 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the management device (such as the first management device, and the second management device) in the above-mentioned method. The functions can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0195] In addition, the transceiver unit 310 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.

[0196] It should be noted that the apparatus in FIG3 can be the management device in the aforementioned embodiment (such as the first management device or the second management device), or can be a chip or chip system, such as a system on chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit can be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0197] FIG4 is a schematic diagram of another communication device 400 provided in an embodiment of the present application. The device 400 includes a processor 410, which is coupled to a memory 420. The memory 420 is used to store computer programs or instructions and / or data. The processor 410 is used to execute the computer programs or instructions stored in the memory 420, or read the data stored in the memory 420, to perform the methods in the above method embodiments.

[0198] Optionally, there are one or more processors 410 .

[0199] Optionally, there are one or more memories 420 .

[0200] Optionally, the memory 420 is integrated with the processor 410 or provided separately.

[0201] Optionally, as shown in Figure 4, the apparatus 400 further includes a transceiver 430, which is configured to receive and / or transmit signals. For example, the processor 410 is configured to control the transceiver 430 to receive and / or transmit signals.

[0202] As an example, the processor 410 may have the function of the processing unit 320 shown in FIG. 3 , the memory 420 may have the function of a storage unit, and the transceiver 430 may have the function of the transceiver unit 310 shown in FIG. 3 .

[0203] As a solution, the apparatus 400 is used to implement the operations performed by the management device (eg, the first management device, or the second management device) in the above method embodiments.

[0204] For example, the processor 410 is configured to execute computer programs or instructions stored in the memory 420 to implement relevant operations of managing the device in the above various method embodiments.

[0205] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0206] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0207] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0208] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0209] 5 is a schematic diagram of a chip system 500 provided in an embodiment of the present application. The chip system 500 (or also referred to as a processing system) includes a logic circuit 510 and an input / output interface 520 .

[0210] The logic circuit 510 may be a processing circuit in the chip system 500. The logic circuit 510 may be coupled to a storage unit and call instructions in the storage unit so that the chip system 500 can implement the methods and functions of the various embodiments of the present application. The input / output interface 520 may be an input / output circuit in the chip system 500, outputting information processed by the chip system 500 or inputting data or signaling information to be processed into the chip system 500 for processing.

[0211] As a solution, the chip system 500 is used to implement the operations performed by the management device (such as the first management device and the second management device) in the above various method embodiments.

[0212] For example, the logic circuit 510 is used to implement the processing-related operations performed by the management device (such as the first management device, or the second management device) in the above method embodiments; the input / output interface 520 is used to implement the sending and / or receiving-related operations performed by the management device (such as the first management device, or the second management device) in the above method embodiments.

[0213] An embodiment of the present application further provides a computer-readable storage medium storing computer instructions for implementing the methods executed by a management device (such as the first management device or the second management device) in the above-mentioned method embodiments.

[0214] For example, when the computer program is executed by a computer, the computer can implement the method executed by the management device (such as the first management device or the second management device) in each embodiment of the above method.

[0215] An embodiment of the present application further provides a computer program product comprising instructions, which, when executed by a computer, implement the methods performed by a management device (such as the first management device or the second management device) in the above-mentioned method embodiments.

[0216] The present application also provides a communication system, which includes the first management device and / or the second management device in the above embodiments. For example, the system includes the first management device and the second management device in the embodiment of FIG.

[0217] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0218] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0219] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium includes, but is not limited to, various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0220] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for analyzing traffic congestion, characterized in that: include: receiving a first message, the first message being used to request execution of a management data analysis (MDA) task, the first message including an analysis type, the analysis type being traffic congestion analysis; A second message is sent, where the second message includes a traffic congestion analysis result.

2. The method according to claim 1, characterized in that The first message includes policy information, and the policy information includes at least one of first information and second information, the first information is used to identify burst traffic congestion, and the second information is used to identify non-burst traffic congestion.

3. The method according to claim 2, characterized in that The first information or the second information includes analysis parameters, and the analysis parameters include at least one of an average user number threshold, a physical resource block (PRB) utilization threshold, a downlink user rate threshold, an average user number deviation threshold, and a downlink PRB utilization deviation threshold.

4. The method according to claim 2 or 3, characterized in that The first message further includes third information, where the third information indicates an applicable scope of the policy information.

5. The method according to any one of claims 1 to 4, characterized in that The traffic congestion analysis result includes the traffic congestion type, and the traffic congestion type is burst traffic congestion or non-burst traffic congestion.

6. The method according to any one of claims 1 to 5, characterized in that The traffic congestion analysis result includes at least one of the following analysis results: traffic congestion status, traffic congestion level, traffic congestion area information, and recommended optimization measures for traffic congestion, wherein the traffic congestion status is potential congestion, real congestion, or congestion disappearance.

7. The method according to claim 6, characterized in that The suggested optimization measures include suggested optimization measures for sudden traffic congestion and suggested optimization measures for non-sudden traffic congestion, wherein: The proposed optimization measures for sudden traffic congestion include at least one of the following optimization measures: performing mobility robustness optimization (MRO), performing mobility load balancing (MLB), and performing coverage capacity optimization (CCO). The suggested optimization measures for non-burst traffic congestion include at least one of the following optimization measures: performing MRO, performing MLB, performing CCO, adding sectors, and adding base stations.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: A third message is received, the third message including an optimization measure for traffic congestion, the third message instructing to perform the optimization measure.

9. The method according to any one of claims 1 to 8, characterized in that The first message further includes analysis result request information, where the analysis result request information is used to request a specific analysis result.

10. A method for analyzing traffic congestion, characterized in that: include: Sending a first message, where the first message is used to request execution of a management data analysis (MDA) task, and the first message includes an analysis type, where the analysis type is traffic congestion analysis; A second message is received, where the second message includes a traffic congestion analysis result.

11. The method according to claim 10, characterized in that The first message includes policy information, and the policy information includes at least one of first information and second information, the first information is used to identify burst traffic congestion, and the second information is used to identify non-burst traffic congestion.

12. The method according to claim 11, characterized in that The first information or the second information includes analysis parameters, and the analysis parameters include at least one of an average user number threshold, a physical resource block (PRB) utilization threshold, a downlink user rate threshold, an average user number deviation threshold, and a downlink PRB utilization deviation threshold.

13. The method according to claim 11 or 12, characterized in that The first message further includes third information, where the third information indicates an applicable scope of the policy information.

14. The method according to any one of claims 10 to 13, characterized in that The traffic congestion analysis result includes the traffic congestion type, and the traffic congestion type is burst traffic congestion or non-burst traffic congestion.

15. The method according to any one of claims 10 to 14, characterized in that The traffic congestion analysis result includes at least one of the following analysis results: traffic congestion status, traffic congestion level, traffic congestion area information, and recommended optimization measures for traffic congestion, wherein the traffic congestion status is potential congestion, real congestion, or congestion disappearance.

16. The method according to claim 15, characterized in that The suggested optimization measures include suggested optimization measures for sudden traffic congestion and suggested optimization measures for non-sudden traffic congestion, wherein: The proposed optimization measures for sudden traffic congestion include at least one of the following optimization measures: performing mobility robustness optimization (MRO), performing mobility load balancing (MLB), and performing coverage capacity optimization (CCO). The suggested optimization measures for non-burst traffic congestion include at least one of the following optimization measures: performing MRO, performing MLB, performing CCO, adding sectors, and adding base stations.

17. The method according to any one of claims 10 to 16, characterized in that The method further comprises: Determining a third message based on the traffic congestion analysis result, the third message including an optimization measure for the traffic congestion, and the third message instructing execution of the optimization measure; The third message is sent.

18. The method according to any one of claims 10 to 17, characterized in that The first message further includes analysis result request information, where the analysis result request information is used to request a specific analysis result.

19. A communication device, characterized in that: The method comprises modules or units for executing the method according to any one of claims 1 to 18.

20. A communication device, characterized in that: comprising at least one processor; The at least one processor is configured to execute a computer program or instruction stored in the memory, so that the method according to any one of claims 1 to 18 is performed.

21. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program or instructions, and when the computer program or instructions are executed on a communication device, the communication device is caused to perform the method according to any one of claims 1 to 18.

22. A computer program product, characterized in that The computer program product comprises a computer program or instructions for performing the method according to any one of claims 1 to 18.

23. A communication system, characterized in that: comprising a first management device and a second management device, The first management device is used to execute the method according to any one of claims 1 to 9, and the second management device is used to execute the method according to any one of claims 10 to 18.

Images