Experience issue delimitation method, device, and system

Abstract

Disclosed are an experience issue delimitation method, a device, and a system, relating to the technical field of communications, and solving the problem that when experience issue analysis comprises roughly delimiting an experience issue, an optimization strategy for solving the experience issue cannot be formulated and the user experience cannot be improved due to the range of delimitation being too large, specific root cause issue objects not being delimitable, and the delimitation analysis range being incomplete. The method comprises: a cross-domain MDAS obtains information used for indicating an experience deterioration event, a service access volume, and first information of the service topology of the experience deterioration event and, on the basis of the first information, performs experience issue delimitation to determine an issue object and the root cause of the issue object, and then sends an analysis report to a subscription consumer. The root cause of the issue object is determined by a single-domain MDAS on the basis of second information, and the single-domain MDAS subsequently sends the root cause of the issue object to the cross-domain MDAS. The solution of the present application can be widely used in technical fields such as communications, artificial intelligence, vehicle networking, and smart home networking.

Description

A method, device and system for defining experience problems

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 16, 2023, with application number 202311540168.7 and application name “A method, device and system for delimiting experience problems”, 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 in particular to a method, device, and system for defining an experience problem. Background Art

[0003] Management data analytics (MDA) leverages artificial intelligence (AI) and / or machine learning (ML) technologies to bring automation and intelligence to network service management and orchestration, serving as a key enabler of these technologies. MDA capabilities include service experience analysis (SEA) and coverage-related analytics. SEA is used to analyze, collect statistics on, and predict user experience issues.

[0004] Experience problem analysis involves roughly defining the problem. For example, the analysis can roughly determine that the communication domain causing the problem is the core network domain and / or the wireless network domain. However, if this involves roughly defining the problem, the scope of the definition is too broad and vague, preventing the specific root cause from being identified. Furthermore, the scope of the analysis is incomplete, making it impossible to develop an optimization strategy to resolve the problem and improve the user experience.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a method, device, and system for demarcating an experience problem to solve the problem that, when experience problem analysis includes a rough demarcation of the experience problem, the specific root cause problem object cannot be demarcated because the demarcation scope is too large and not specific, and the demarcation analysis scope is incomplete, resulting in an inability to formulate an optimization strategy to solve the experience problem and an inability to improve the user experience.

[0007] To achieve the above objectives, this application adopts the following technical solutions:

[0008] In the first aspect, the present application provides a method, device and system for demarcating an experience problem. The method can be executed by a cross-domain management data analytics service (MDAS) and a functional module or chip within the cross-domain MDAS. Taking the cross-domain MDAS execution as an example, the method includes: the cross-domain MDAS obtains first information indicating information of an experience degradation event, service access volume, and service topology of the experience degradation event, demarcates the experience problem based on the first information, and determines the problem object and the root cause of the problem object; then, an analysis report indicating the problem object and / or the root cause of the problem object is sent to the subscribing consumer. Among them, the experience degradation event includes an event in which there is an experience problem in the event of service access through the current operator network; the experience problem includes that the access experience does not meet the preset experience requirements; the service access volume includes the total amount of service access belonging to the same service as the experience degradation event through the current operator network; the service topology of the experience degradation event is used to indicate the communication network topology when the user accesses the experience degradation event, and the communication network topology includes multiple communication domains, and each communication domain includes at least one communication node.

[0009] Based on the method described in the first aspect, the cross-domain MDAS can determine the communication domain and / or communication node that caused the experience problem based on the first information, as well as the root cause of the experience problem. Further, an analysis report is sent to the subscribing consumer, indicating the communication domain and / or communication node that caused the experience problem, as well as the root cause of the experience problem. In this way, the subscribing consumer can formulate an optimization strategy to solve the experience problem based on the analysis report to achieve the goal of improving user experience.

[0010] In one possible design, the cross-domain MDAS demarcates the experience problem based on the first information, determines the problem object and the root cause of the problem object, including: the cross-domain MDAS sends second information to the single-domain MDAS, and the second information is used to determine the root cause of the problem object; the cross-domain MDAS generates an analysis report based on the root cause of the problem object sent by the single-domain MDA.

[0011] Based on this possible design, the cross-domain MDAS can determine the root cause of the problem object through the single-domain MDAS. Furthermore, based on the single-domain MDAS, an analysis report can be generated. The generated analysis report can provide effective support for subscribers to develop optimization strategies to solve the experience problem.

[0012] In one possible design, the cross-domain MDAS obtains the service topology of the experience degradation event, including: the cross-domain MDAS obtains first information; the cross-domain MDAS obtains the service topology of the experience degradation event based on the first information and the managed communication domains and / or communication nodes.

[0013] Based on this possible design, the cross-domain MDAS achieves the purpose of obtaining the service topology of the experience degradation event. At the same time, the cross-domain MDAS obtains the service topology of the experience degradation event based on the communication domains and / or communication nodes it manages. The cross-domain MDAS does not need to obtain the service topology of the experience degradation event from the single-domain MDAS through signaling interaction, which reduces the processing complexity of the cross-domain MDAS and the efficiency of obtaining the service topology of the experience degradation event.

[0014] In one possible design, the cross-domain MDAS obtains the business topology of the experience degradation event, including: sending a subscription request to a data source, where the subscription request is used to request first information from the data source; and receiving a subscription response from the data source, where the subscription response includes the first information.

[0015] Based on this possible design, the cross-domain MDAS directly obtains the service topology of the experience degradation event from the data source, providing a possible solution for the cross-domain MDAS to obtain the service topology of the experience degradation event, and improving the flexibility and diversity of the cross-domain MDAS in obtaining the service topology of the experience degradation event.

[0016] In one possible design, the information about the experience degradation event includes at least one of the following: the service type to which the experience degradation event belongs, the network slice identifier where the experience degradation event is located, the application identifier corresponding to the experience degradation event, the area identifier where the experience degradation event occurs, the user identifier where the experience degradation event occurs, the service topology node of the experience degradation event, and the event type of the experience degradation event. The service access volume includes at least one of the following: service type, application identifier, area identifier, user identifier, and service topology node. The single-domain management data analysis service includes at least one of the following: core network domain management data analysis service or wireless network domain management data analysis service.

[0017] Based on this possible design, the cross-domain MDAS can obtain detailed information on experience degradation events, detailed information on business access volume, and detailed information on single-domain management data analysis services, which facilitates the subsequent cross-domain MDAS to determine the problem object and / or the root cause of the problem object of the experience problem.

[0018] In one possible design, the analysis report includes at least one of the following: a problem domain type, the problem object, and a service experience simulation node; wherein the problem domain type is used to indicate the type of domain to which the problem object belongs, including at least one of the terminal side, transmission side, service provider side, wireless network side, and core network side; the service experience simulation node is used to indicate the degree of improvement in user experience after the experience problem is resolved.

[0019] Based on this possible design, subscribing consumers can provide support for solving the experience problem based on the detailed information included in the analysis report, so as to formulate an optimization strategy to solve the experience problem and achieve the goal of improving user experience.

[0020] On the second aspect, the present application provides a method, device and system for demarcating an experience problem. The method can be executed by a single-domain MDAS and a functional module or chip within the single-domain MDAS. Taking the execution of a single-domain MDAS as an example, the method includes: the single-domain MDAS obtains second information, and based on the second information, determines the root cause of the problem object; then, sends the root cause of the problem object to the cross-domain MDAS.

[0021] Based on the method of the second aspect, the single-domain MDAS can determine the root cause of the problem object based on the acquired second information, and send the determined root cause of the problem object to the cross-domain MDAS, so that the cross-domain MDAS can generate an analysis report based on the root cause of the problem object.

[0022] In a third aspect, the present application provides a communication device, which may be a cross-domain MDAS or a chip or system on chip in a cross-domain MDAS, or a functional module in a cross-domain MDAS for implementing the first aspect or any possible design of the method of the first aspect. The communication device can implement the functions performed by the cross-domain MDAS in the above aspects or possible designs, and the functions can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, the communication device may include a processing unit and a transceiver unit. Among them,

[0023] a processing unit, configured to obtain first information, and delimit the experience problem based on the first information, and determine the problem object and the root cause of the problem object;

[0024] The transceiver unit is used to send an analysis report to a subscribing consumer, where the analysis report is used to indicate the problem object and / or the root cause of the problem object.

[0025] Specifically, the relevant descriptions of the first information, the problem object, the root cause of the problem object, and the analysis report can refer to the first aspect or any possible design of the first aspect. At the same time, the execution actions of each unit of the communication device can refer to the first aspect or any possible design of the first aspect and will not be repeated here.

[0026] In a fourth aspect, the present application provides a communication device, which may be a cross-domain MDAS or a chip or system-on-chip in a cross-domain MDAS. The communication device may implement the functions performed by the cross-domain MDAS in the above-mentioned aspects or possible designs, and the functions may be implemented by hardware. In one possible design, the communication device includes a processor and a communication interface. The processor and the communication interface are used to support the communication device in executing the experience problem demarcation method in the first aspect or any possible design of the first aspect. In another possible design, the communication device may further include a memory, the memory being used to store computer-executable instructions and data necessary for the communication device. When the communication device is running, the processor executes the computer-executable instructions stored in the memory, so that the communication device executes the experience problem demarcation method as described in the above-mentioned first aspect or any possible design of the first aspect.

[0027] In a fifth aspect, the present application provides a communication device, which may be a single-domain MDAS or a chip or system-on-chip in a single-domain MDAS, or a functional module in a single-domain MDAS for implementing the second aspect or any possible design of the second aspect. The communication device can implement the functions performed by the single-domain MDAS in the above aspects or possible designs, and the functions can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, the communication device may include a processing unit and a transceiver unit. Among them,

[0028] a processing unit, configured to obtain second information and determine a root cause of the problem object based on the second information;

[0029] The transceiver unit is used to send the root cause of the problem object to the cross-domain management data analysis service.

[0030] Specifically, the relevant description of the second information and the root cause of the problem object can refer to the second aspect or any possible design of the second aspect. At the same time, the execution actions of each unit of the communication device can refer to the second aspect or any possible design of the second aspect and will not be repeated here.

[0031] In a sixth aspect, the present application provides a communication device, which may be a single-domain MDAS or a chip or system-on-chip in a single-domain MDAS. The communication device may implement the functions performed by the single-domain MDAS in the above-mentioned aspects or possible designs, and the functions may be implemented by hardware. In one possible design, the communication device includes a processor and a communication interface. The processor and the communication interface are used to support the communication device in executing the experience problem demarcation method in the second aspect or any possible design of the second aspect. In another possible design, the communication device may further include a memory, the memory being used to store computer-executable instructions and data necessary for the communication device. When the communication device is running, the processor executes the computer-executable instructions stored in the memory, so that the communication device executes the experience problem demarcation method as described in the above-mentioned second aspect or any possible design of the second aspect.

[0032] In a seventh aspect, the present application provides a communication system, which includes the communication device provided in the third aspect or the fourth aspect, or the communication system includes the communication device provided in the fifth aspect or the sixth aspect.

[0033] In an eighth aspect, the present application provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on a computer, the computer executes the method for defining the experience problem in the first aspect or any possible design of the first aspect; or, the computer executes the method for defining the experience problem in the second aspect or any possible design of the second aspect.

[0034] In a ninth aspect, the present application provides a computer program product comprising computer instructions, which, when executed on a computer, cause the computer to execute the first aspect or the method for defining the experience problem in any possible design of the first aspect; or, cause the computer to execute the second aspect or the method for defining the experience problem in any possible design of the second aspect.

[0035] Among them, the technical effects brought about by any one of the design methods in the third and fourth aspects can refer to the technical effects brought about by the above-mentioned first aspect or any possible design of the first aspect, and no further details are given. The technical effects brought about by any one of the design methods in the fifth and sixth aspects can refer to the technical effects brought about by the above-mentioned second aspect or any possible design of the second aspect, and no further details are given. The technical effects brought about by any one of the design methods in the seventh to ninth aspects can refer to the technical effects brought about by the above-mentioned first aspect or any possible design of the first aspect, or the technical effects brought about by any one of the design methods in the seventh to ninth aspects can refer to the technical effects brought about by the above-mentioned second aspect or any possible design of the second aspect, and no further details are given. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 is a schematic diagram of the MDA architecture;

[0037] FIG2 is a schematic diagram of a communication system provided in an embodiment of the present application;

[0038] FIG3 is a flow chart of a method for defining an experience problem according to an embodiment of the present application;

[0039] FIG4 is a flow chart of a method for defining an experience problem according to an embodiment of the present application;

[0040] FIG5 is a flow chart of a method for defining an experience problem provided in an embodiment of the present application;

[0041] FIG6 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0042] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0043] FIG8 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] Before introducing the embodiments of the present application, some technical terms involved in the embodiments of the present application are explained. It should be noted that the following explanations are intended to make the embodiments of the present application easier to understand and should not be regarded as limiting the scope of protection claimed by the embodiments of the present application.

[0045] Management data analytics (MDA) leverages artificial intelligence (AI) and / or machine learning (ML) technologies to bring automation and intelligence to network service management and orchestration, serving as a key enabler of automation and intelligence. MDA processes and analyzes network management data and provides analytical output. This output is provided by the Management Data Analytics Service (MDAS) producer to the MDA subscriber who requested the analysis.

[0046] MDAS is a service exposed by MDA and can be used by MDA subscribers (hereinafter referred to as subscribers). MDAS may include but is not limited to management service producers / consumers for network and service management, network functions (NF) (such as network data analytics function (NWDAF)), self-organizing networks (SON) functions, network and service optimization tools / functions, service experience analysis (SLS) functions, and application functions (AF), etc.

[0047] It should be understood that the two terms MDAS and management data analytics management service (MDA MnS) in this application are equivalent and can be used interchangeably.

[0048] MDA can perform data analysis on network management data based on the architecture shown in Figure 1. As shown in Figure 1, the network architecture includes: the 3rd Generation Partnership Project (3GPP) cross-domain MDA MnS consumer, the 3GPP cross-domain MDA MnS producer, the core network domain MDA MnS producer (CN-domain MDA MnS producer), the radio access network domain MDA MnS producer (RAN-domain MDA MnS producer), the NWDAF, other 5th-generation mobile communication technology core network functions (other 5GC NFs), and the next generation node b (gNB).

[0049] Among them, the 3GPP cross-domain MDA MnS consumer (referred to as MDA subscription consumer and / or subscription consumer) can interact with the 3GPP cross-domain MDA MnS producer through the MDA MnS node, use the MDA MnS generated by the 3GPP cross-domain MDA MnS producer, and access analysis output.

[0050] Among them, the 3GPP cross-domain MDA MnS producer can exchange data with the single-domain MDA MnS producer (for example, the RAN domain MDA MnS producer and / or the CN domain MDA MnS producer) through the MDA MnS node, use the MDA MnS provided by the single-domain MDA MnS producer (for example, the RAN domain MDA MnS producer and / or the CN domain MDA MnS producer), and generate an MDA MnS that can be used by the 3GPP cross-domain MDA MnS consumer.

[0051] It should be understood that the 3GPP cross-domain MDA MnS producer may base its analysis output on the analysis output of one or more domain MDA MnS producers.

[0052] The CN-domain MDA MnS producer can exchange data with NWDAF and other 5GC NFs to receive network management data. Correspondingly, the CN-domain MDA MnS producer can use the services provided by NWDAF and other 5GC NFs to analyze network management data.

[0053] The RAN-domain MDA MnS producer can interact with the RAN to receive network management data. Correspondingly, the RAN-domain MDA MnS producer can use services provided by the gNB to analyze the network management data.

[0054] Among them, NWDAF is a data-aware analysis network element. 3GPP defines that NWDAF can collect raw data from NF, AF, and operation administration and maintenance (OAM), and perform intelligent analysis on the raw data, and output the analysis data to NF, AF, OAM, etc. for network and service optimization. At the same time, NWDAF can also evaluate and analyze different types of services by collecting information such as network performance, service load in specific areas, and user service experience, and using reliable network performance analysis and prediction models to determine the intrinsic correlation between the service quality of experience (QoE) and the service path, and optimize 5G edge computing, etc. It should be understood that the CN-domain MDA MnS producer and / or 3GPP cross-domain MDA MnS producer can also use the analysis results generated by NWDAF as input.

[0055] Among them, other 5GC NF is used to provide network management data for CN-domain MDA MnS producer, including access and mobility management function (AMF) network element, session management function (SMF) network element, policy control function (PCF) network element, etc.

[0056] Among them, gNB is used for data transmission between terminals and wireless networks, and provides network management data for RAN-domain MDA MnS producers.

[0057] MDA includes the following functions: coverage related analytics, service experience analysis, MDA-assisted fault management, MDA-assisted energy saving, MDA-assisted mobility management, and MDA-assisted critical maintenance management.

[0058] Among them, the service experience analysis function is used to analyze the user's service experience. Specific analysis capabilities include experience problem analysis, experience problem statistics, experience problem prediction, etc. Experience problem refers to the fact that the access experience of MDA subscription consumers does not meet the preset requirements. Specifically, experience problem analysis includes but is not limited to coarse demarcation of the core network domain and the wireless network domain for experience problems. That is, the experience problem analysis can identify that the communication domain that causes the experience problem is the core network domain and / or the wireless network domain, but lacks problem analysis that identifies problems from the terminal side, the transmission side, and the service provider (SP) side, resulting in an incomplete scope of problem analysis.

[0059] At the same time, when the experience problem analysis roughly delimits the core network domain and / or wireless network domain of the experience problem, if the communication node (for example, user-side network element, base station, etc.) that causes the experience problem is not accurately identified, it is impossible to formulate a corresponding optimization strategy for the experience problem. In other words, it is impossible to support the subsequent optimization closed-loop logic to achieve the goal of solving or alleviating the experience problem.

[0060] In order to solve the problem that a rough demarcation of experience problems cannot support subsequent optimization of closed-loop logic, the present application provides a method for demarcating experience problems, which includes: a cross-domain MDAS obtains first information indicating information of experience degradation events, service visits, and the service topology of the experience degradation events, demarcates the experience problem based on the first information, and determines the problem object and the root cause of the problem object; then, an analysis report is sent to the subscription consumer. The root cause of the problem object is determined by the single-domain MDAS based on the second information, and further, the single-domain MDAS sends the root cause of the problem object to the cross-domain MDAS. In this way, the experience problem can be demarcated based on the information of the experience degradation event, the service visits, and the service topology of the experience degradation event, so that the reference factors when demarcating the experience problem are more comprehensive, the demarcation granularity is refined, and the accuracy of the experience problem demarcation is improved.

[0061] The following describes the method for defining experience problems provided in the embodiments of the present application in conjunction with the accompanying drawings.

[0062] The technical solution of the embodiment of the present application can be used in various communication systems, which may be a third generation partnership project (3GPP) communication system, for example, a long term evolution (LTE) system, or a fifth generation (5G) mobile communication system, a new radio (NR) system, a beyond 5G (B5G) mobile communication system, a future mobile communication system, a new air interface vehicle to everything (NR V2X) system, and can also be applied to a system of LTE and 5G hybrid networking, or a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT), and other future communication systems, or a non-3GPP communication system, without limitation. The following describes the experience problem demarcation method provided in the embodiment of the present application, taking the communication system shown in Figure 2 as an example.

[0063] FIG2 is a schematic diagram of a communication system provided in an embodiment of the present application. As shown in FIG2 , the communication system 20 includes a terminal, a management data analytics function (MDAF), an access network device, a core network device, a transmission device, and a service provider device. It is understood that the devices in the communication system 20 can communicate directly with each other or communicate through forwarding by other devices, and this embodiment of the present application does not specifically limit this.

[0064] It is understood that Figure 2 is merely a schematic diagram and does not limit the applicable scenarios of the technical solutions provided in this application. Those skilled in the art will appreciate that, in a specific implementation, communication system 20 may include fewer devices than shown in Figure 2 , or may include other devices. The number of devices in communication system 20 may also be determined based on specific needs and is not limited. The following describes the devices in the system shown in Figure 2 .

[0065] The management data analysis function is used to obtain network management data and perform data processing and / or data analysis on the obtained network management data, including but not limited to cross-domain MDAS producers and single-domain MDAS producers. Among them, the cross-domain MDAS producer, which can also be simply referred to as cross-domain MDAS, is used to obtain network management data, and perform data processing and / or data analysis on the obtained network management data, and provide analysis reports for subscribing consumers (for example, end users who subscribe to MDA, NFs that subscribe to MDA, etc.). The single-domain MDAS producer, which can also be simply referred to as single-domain MDAS, is used to obtain network management data, and perform data processing and / or data analysis on the obtained network management data, and generate MDA MnS that can be used by cross-domain MDAS producers. The single-domain MDAS producer includes at least one of the following: a core network domain MDA producer, or a wireless network domain MDA producer.

[0066] The terminal may be a terminal device (terminal equipment) or a user equipment (UE) or a mobile station (MS) or a mobile terminal (MT), etc. Specifically, the terminal may be a mobile phone, a tablet computer or a computer with wireless transceiver function, or a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city, a smart home, a vehicle-mounted terminal, etc. In an embodiment of the present application, the device for realizing the function of the terminal may be a terminal, or a device that can support the terminal to realize the function, such as a chip system (such as a processing system composed of a chip or multiple chips) or a modem. The following takes the terminal as an example to describe the experience problem demarcation method provided in an embodiment of the present application.

[0067] The access network device is mainly used to implement functions such as resource scheduling, wireless resource management, and wireless access control of the terminal. Specifically, the access network device can be any one of a small base station, a wireless access point, a transmission receive point (TRP), a transmission point (TP), and some other access nodes. In an embodiment of the present application, the device for implementing the function of the access network device can be an access network device, or it can be a device that can support the access network device to implement the function, such as a chip system (such as a chip, or a processing system composed of multiple chips) or a modem. The following takes the example of the device for implementing the function of the access network device being an access network device to describe the experience problem demarcation method provided in an embodiment of the present application.

[0068] Core network equipment is divided into control plane function (CP) equipment and user plane function (UP) equipment. User plane devices are mainly responsible for packet forwarding, quality of service (QoS) control, and billing information statistics, including user plane function (UPF). Control plane devices are mainly responsible for business process interaction, issuing packet forwarding policies and QoS control policies to the user plane, including network data analytics function (NWDAF), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), application function (AF), network exposure function (NEF), authentication server function (AUSF), network slice selection function (NSSF), network exposure function repository function (NRF), and unified data management (UDM).

[0069] Service provider (SP) equipment: refers to equipment managed by a service provider and used to develop or provide services that meet user needs.

[0070] Transmission equipment refers to the equipment that serves the transmission network. The transmission network, as the core of the entire fiber optic network, is the fastest transmission network in the entire telecommunications network.

[0071] Optionally, each device in Figure 2 (such as a terminal, access network device, core network device, cross-domain MDAS producer, single-domain MDAS producer, etc.) can also be referred to as a communication device, which can be a general device or a dedicated device. The embodiments of this application do not specifically limit this.

[0072] Optionally, the related functions of each device in FIG2 of the present application can be implemented by a single device, or by multiple devices, or by one or more functional modules within a single device, and the embodiments of the present application do not specifically limit this. It is understood that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, or a combination of hardware and software, or virtualized functions instantiated on a platform (e.g., a cloud platform).

[0073] The following describes the experience problem demarcation method provided by an embodiment of the present application in conjunction with the communication system shown in Figure 2. The actions and terms involved in the following embodiments can be cross-referenced. The names of messages or parameter names in messages exchanged between devices in each embodiment are merely examples; other names may be used in specific implementations. For example, the word "corresponding" in the following embodiments can be replaced with "associated."

[0074] FIG3 is a flow chart of a method for defining an experience problem according to an embodiment of the present application. As shown in FIG3 , the method may include:

[0075] S301: The cross-domain MDAS obtains first information.

[0076] Among them, the cross-domain MDAS can be a cross-domain MDAS producer in the MDA function module, which is used to perform data processing and / or data analysis on the acquired information and provide analysis reports for subscribing consumers.

[0077] The first information may be used to indicate information about the experience degradation event, service access volume, and service topology of the experience degradation event.

[0078] Specifically, experience degradation events include events in which experience problems occur during service access through the current operator's network, and experience problems include access experience that does not meet preset experience requirements. Operator refers to the supplier of network services, such as operator A. The preset experience requirements may include but are not limited to meeting the basic requirements for terminal user access experience. For example, when a terminal user accesses a video service with a resolution of 1920*1080, the preset experience requirements include but are not limited to maintaining the transmission bit rate at 8Mbps. Therefore, when the transmission bit rate is lower than 8Mbps, the terminal user will experience unclear video when accessing a video service with a resolution of 1920*1080.

[0079] Service access volume includes the total number of service accesses to the same service as the experience degradation event on the current carrier network. For example, if the experience degradation event is unclear video, the total number of video service accesses on the current carrier network is 200, of which 50 have experience issues, resulting in a poor video quality experience for end users.

[0080] The service topology of the experience degradation event is used to indicate the communication network topology when the user accesses the experience degradation event. The communication network topology includes multiple communication domains, each of which includes at least one communication node. In other words, the communication domain can be a logical network composed of at least one communication node. In this application, the communication domain can be divided into a wireless network domain, a core network domain, a transport network domain, a terminal side, and an SP side according to its function.

[0081] Among them, the wireless network domain may refer to the communication domain responsible for realizing terminal resource scheduling, wireless resource management and other functions, including but not limited to the following communication nodes: cells, base stations. The core network domain may refer to the communication domain responsible for business process interaction, service quality control, data packet forwarding strategy and other functions, including but not limited to the following communication nodes: user plane network element, NWDAF, AMF network element. The transmission network domain may refer to the optical fiber network responsible for data transmission, including but not limited to the following communication nodes: optical fiber. The terminal side may refer to the device responsible for meeting the needs of terminal users, including but not limited to smartphones and tablets. The SP side may refer to the device responsible for providing terminal users with services that meet the needs of terminal users according to the needs of terminal users, including but not limited to the following communication nodes: application servers.

[0082] It should be understood that the wireless network domain is equivalent to the wireless network side, and the two can be used interchangeably; the core network domain is equivalent to the core network side, and the two can be used interchangeably; the transmission network domain is equivalent to the transmission network side, and the two can be used interchangeably.

[0083] Specifically, the cross-domain MDAS may obtain the first information in any of the following two ways:

[0084] Method 1: The cross-domain MDAS sends a subscription request to the data source, requesting first information from the data source. Subsequently, the cross-domain MDAS receives a subscription response from the data source, which includes the first information. The first information indicates information about the experience degradation event, service traffic, and the service topology of the experience degradation event.

[0085] Among them, the data source is used to provide QoE data for the cross-domain MDAS. The QoE data is used to represent the terminal user's experience and feelings of the service and / or network, and may include but is not limited to information about experience degradation events, service access volume, and service topology of experience degradation events. Specifically, the data source may include but is not limited to AF and / or NWDAF. AF can be used to interact with other NFs for data and provide business services to the terminal. NWDAF can be used to collect data from other NFs and / or similar programs (e.g., programs that generate data on demand) through a subscription or request model.

[0086] Specifically, the implementation method may refer to the embodiment corresponding to FIG4 below.

[0087] Method 2: The cross-domain MDAS obtains information about the experience degradation event and service access volume; then, the cross-domain MDAS obtains the service topology of the experience degradation event based on the obtained information about the experience degradation event, service access volume, and managed communication domains and / or communication nodes, and thus obtains the first information.

[0088] Specifically, the implementation method may refer to the embodiment corresponding to FIG5 below.

[0089] S302: The cross-domain MDAS demarcates the experience problem based on the first information, and determines the problem object and the root cause of the problem object.

[0090] The problem object may include the communication domain and / or communication node that causes the experience problem. The root cause of the problem object includes the root cause that causes the experience problem.

[0091] Specifically, the cross-domain MDAS demarcates the experience problem based on the first information, and determines the problem object and the root cause of the problem object, which may include: the cross-domain MDAS sending second information to the single-domain MDAS based on the determined problem object, where the second information is used to indicate the problem object of the experience problem; the single-domain MDAS receiving the second information sent by the cross-domain MDAS and determining the root cause of the problem object based on the second information; and further, the single-domain MDAS sending the root cause of the problem object to the cross-domain MDAS. Correspondingly, the cross-domain MDAS receives the root cause of the problem object sent by the single-domain MDAS.

[0092] Specifically, the implementation method may refer to the embodiments corresponding to FIG. 4 or FIG. 5 below.

[0093] The cross-domain MDAS sends the second information to the single-domain MDAS based on the determined problem object. It should be understood that the single-domain MDAS refers to the single-domain MDAS of the domain to which the problem object belongs. The single-domain MDAS includes at least one of the following: a core network domain MDAS or a wireless network domain MDAS.

[0094] S303: The cross-domain MDAS sends an analysis report to the subscribing consumer, and the subscribing consumer receives the analysis report accordingly.

[0095] The analysis report indicates the problem object and / or its root cause. It may include, but is not limited to, the problem domain type, problem object, and service experience simulation node. The problem domain type indicates the domain to which the problem object belongs, including at least one of the following: terminal side, transmission side, service provider side, wireless network side, and core network side. The service experience simulation node indicates the degree of improvement in user experience after resolving the problem.

[0096] Specifically, the cross-domain MDAS sending the analysis report to the subscribing consumer may include: the cross-domain MDAS generating an analysis report based on the root cause of the problem object sent by the single-domain MDAS, and sending the analysis report to the subscribing consumer. Specifically, this implementation method can refer to the embodiment corresponding to Figure 4 or Figure 5 below.

[0097] Based on the method described in Figure 3, the cross-domain MDAS determines the problem object and the root cause of the problem object based on the information indicating the experience degradation event, the service access volume, and the first information of the service topology of the experience degradation event, thereby implementing experience problem analysis to define the problem object of the experience problem. At the same time, after determining the problem object and the root cause of the problem object, the cross-domain MDAS sends an analysis report to the subscribing consumer, allowing the subscribing consumer to develop an optimization strategy to resolve the experience problem based on the analysis report, thereby achieving the goal of improving user experience.

[0098] In this application, there are two ways for the cross-domain MDAS in Figure 3 to obtain the first information. The first way is for the cross-domain MDAS to obtain the first information from the data source, and the first information is used to indicate the service topology of the experience degradation event. The specific experience problem demarcation method is shown in Figure 4.

[0099] As shown in FIG4 , an experience problem demarcation method provided in an embodiment of the present application includes the following steps:

[0100] S401: An MDA subscription consumer (hereinafter referred to as a subscription consumer) sends an analysis request to a cross-domain management data analysis service (hereinafter referred to as a cross-domain MDAS). In response, the cross-domain management data analysis service receives the analysis request.

[0101] Among them, MDA subscription consumers refer to devices that can consume management data analysis services, such as end users who subscribe to MDA, NFs that subscribe to MDA, etc.

[0102] The analysis request is used to request the cross-domain MDAS to generate analysis output for business experience analysis. It also requests the cross-domain MDAS to create a managed object instance (MOI) for business experience analysis, including but not limited to the MDA type. A managed object instance is an analysis model created by the cross-domain MDAS based on different MDA functions and in accordance with the protocol. This includes enabling data and analysis output.

[0103] Specifically, the MDA type is used to indicate that the MDA function is service experience analysis and to instruct the cross-domain MDAS to create a management object instance for service experience analysis. It should be understood that the management object instance for service experience analysis can be simply referred to as an analysis instance.

[0104] Optionally, the analysis request also includes control attributes related to the MDA output. These control attributes include the MDA output schedule and the geographic location (i.e., regional scope) of the MDA output. The MDA output schedule includes the start, end, and duration of the analysis. The geographic location of the MDA output indicates the target region for obtaining the MDA output.

[0105] Exemplarily, the analysis request includes an MDA type, a time schedule for MDA output, and a geographic location for MDA output. The MDA type indicates that the MDA performs service experience analysis, the time schedule for MDA output indicates that the analysis duration for MDA output is 15 minutes, and the geographic location for MDA output indicates that the target area for obtaining the MDA is the area of ​​network slice ID (NSI_ID) NSI_2.

[0106] S402: The cross-domain MDAS creates an analysis instance based on the analysis request. Subsequently, the cross-domain MDAS sends an analysis request response to the subscribing consumer.

[0107] The analysis request response confirms the successful creation of the analysis instance to the subscribing consumer and carries the identifier of the managed object instance. The identifier of the managed object instance indicates that the managed object instance created by the cross-domain MDAS is a managed object instance for business experience analysis.

[0108] The cross-domain MDAS creates a management object instance based on the MDA type in the analysis request and in accordance with the protocol agreement.

[0109] Specifically, the cross-domain MDAS creates a management object instance for business experience analysis based on the MDA type of the business experience analysis in the analysis request. The management object instance for business experience analysis can be simply referred to as an analysis instance, which includes enabled data and analysis output.

[0110] The enabling data of the analysis instance is used to determine the analysis output of the service experience analysis, including QoE data. It should be understood that the enabling data includes but is not limited to the QoE data provided by this solution, and other data can be supplemented to facilitate the determination of the analysis output. For detailed information on the QoE data, see S403.

[0111] The analysis output of the analysis instance is used to indicate the specific content of the analysis output, and the specific content is shown in Table 1. It should be understood that the analysis output includes but is not limited to the analysis output provided by this solution, and other information can be supplemented to improve the analysis output.

[0112] Table 1

[0113] In Table 1, the service experience problem type is an optional item in the analysis output. The service experience problem type, also known as the problem domain type, is used to indicate the type of domain to which the problem object belongs, including at least one of the terminal side, transmission side, service provider side, wireless network side, and core network side. It should be understood that the service experience problem type can include multiple combinations. If the problem object includes multiple different communication domains, or the problem object includes multiple communication nodes, but the multiple communication nodes belong to different communication domains, the service experience problem type includes multiple combinations.

[0114] For example, assume that the video service experience issue is unclear video, and the problem targets UPF1 and gNB1. In this case, the service experience issue types include core network side and radio network side. Alternatively, if the problem targets UPF1, the service experience issue type includes core network side.

[0115] In Table 1, the service experience root cause object is an optional item in the analysis output. The service experience root cause object, also known as the problem object, indicates the problem object of the experience problem, including the communication domain and / or communication node that caused the experience problem. The method for determining the problem object is described in S404 below. It should be understood that the problem object includes at least one communication domain and / or communication node that caused the experience problem.

[0116] For example, assuming the video service experience issue is video freeze, and the problem target for video freeze is UPF1, the service experience root cause object in the analysis output includes UPF1. Alternatively, assuming the problem targets for video freeze are UPF1 and gNB1, the service experience root cause objects in the analysis output include UPF1 and gNB1.

[0117] In Table 1, service experience simulation is an optional item in the analysis output. It is used to indicate the degree of improvement in user service experience after the experience problem is resolved. The degree of improvement in user service experience can be quantified through service experience level statistics.

[0118] For example, assuming that the experience problem of the video service is video freeze, the level of the service experience level statistics is 1, indicating that the user is enduring a poor experience. After the service experience simulation indicates that the video freeze is resolved, the level of the service experience level statistics is 5, indicating that the user's experience requirements are fully met.

[0119] In Table 1, for detailed descriptions of the service experience identifier, service information, affected objects, service experience statistics, and service experience prediction, please refer to TS28.104 of the 3GPP protocol.

[0120] S403: The cross-domain MDAS sends a subscription request to the data source based on the analysis instance. In response, the data source sends a subscription response to the cross-domain MDAS.

[0121] The data source is used to provide QoE data for the cross-domain MDAS, including but not limited to AF and / or NWDAF.

[0122] Specifically, the AF can exchange data with other NFs to provide services to terminals. The NWDAF can collect data from other NFs and / or similar data collection programs through a subscription or request model to provide quality of experience (QoE) data to the cross-domain MDAS. QoE data represents a user's subjective perception of the quality and performance of devices, networks, systems, applications, or services, such as latency and throughput.

[0123] The subscription request is used to obtain QoE data, which includes but is not limited to information about experience degradation events, service access volume, and service topology of experience degradation events.

[0124] The subscription response is used to respond to the subscription request sent by the cross-domain MDAS, including QoE data.

[0125] Specifically, the specific content of the experience degradation event information is shown in Table 2, including but not limited to: service type, network slice ID, application ID, area ID, user ID, event topology node, and event type. The detailed explanation of each information is as follows:

[0126] (1) Service type

[0127] Service type is used to indicate the type of service accessed by the terminal user, including but not limited to video service, conversation service, live broadcast service, game service, etc.

[0128] (2) Network slice ID

[0129] Network slice ID, used to identify the network slice for which experience assurance analysis is requested. Network slicing is a new network architecture that provides multiple logical networks on a shared network infrastructure, each serving a specific service type.

[0130] (3) Application ID

[0131] The application ID is used to identify a specific application, including the specific name of the application, for example, Application A, Application B, etc.

[0132] (4) Area ID

[0133] The region ID is used to indicate a specific region, including but not limited to the region name, such as Region A, Region B, etc.

[0134] (5) User ID

[0135] The user identification ID is used to indicate the user identification, including the user identification type and the user identification code.

[0136] The type of user identification is used to indicate the method of identifying the user, including the international mobile subscriber identification number (IMSI) and the mobile station international subscriber identification number (MSISDN).

[0137] Specifically, the IMSI is stored in the subscriber identity module (SIM), which is the ID number of the SIM card and effectively distinguishes mobile users. The subscriber identity module is also referred to as the SIM card. The MSISDN is a number that uniquely identifies a mobile user in the Public Switched Telephone Network (PSTN) numbering plan. Simply put, the MSISDN is the mobile phone number.

[0138] The user identification code is used to indicate a number that can accurately identify the user. The user identification code includes different contents for different types of user identifications.

[0139] When the user identification type is IMSI, the user identification code consists of a string of decimal digits with a maximum length of 15 digits, including the mobile country code (MCC), which is 3 digits long; the mobile network code (MNC), the length of which is determined by the value of MCC and can be 2 or 3 digits; and the mobile subscription identification number (MSIN), the value of which is assigned by the network operator.

[0140] When the user identification type is MSISDN, the user identification code includes: the country code (CC), for example, the country code for country A is 86; the network access code (national destination code, NDC), which is assigned to each network operator by the communications regulatory authority of each country. For example, operator A is assigned access codes 134-139, 150-152, 188, etc., operator B is assigned access codes 130-132, 185-186, etc., and operator C is assigned access codes 133, 153, 180, 189, etc.; and the subscriber number (SN) is assigned by the network operator.

[0141] Exemplarily, the user identification ID includes a user identification type of IMSI and a user identification code of 460 001234567890.

[0142] Exemplarily, the user identification ID includes a user identification type of MSISDN and a user identification code of 8613912345678.

[0143] (6) Event topology node

[0144] The event topology node, also known as the business topology of the experience degradation event, is used to indicate the communication network topology when the user accesses the experience degradation event. The communication network topology includes multiple communication domains, each communication domain includes at least one communication node, including a sequence node list. Among them, the communication network topology refers to the specific physical (i.e. real) or logical (i.e. virtual) arrangement between the communication nodes that constitute the communication network. A communication node refers to a connection point or device in a communication network, used to send, receive or forward data. It can be a hardware device (such as a router, base station) or a software entity (such as an application). The communication domain refers to the scope of the communication network. For example, according to the function of the communication network, the communication domain can be divided into a wireless network domain, a core network domain, a transmission network domain, a terminal side, and an SP side.

[0145] Specifically, the sequence node list includes information of multiple communication nodes, including sequence number, node type, and node ID.

[0146] The sequence number indicates the position of the communication node in the sequence node by a number. For example, the sequence number 1 indicates the front position of the communication node in the sequence node.

[0147] The node type indicates the type of the communication node, including but not limited to a cell and a gNB (a gNB, which is the interface device for mobile devices to access the wireless network). For example, a cell indicates that the communication node is a cell (a cell refers to the wireless area controlled by a base station. A base station can manage multiple cells, and different cells have different cell IDs).

[0148] The node ID is used to indicate the communication node. The node IDs of different types of communication nodes include different contents and are determined by the operator to which the communication node belongs.

[0149] For example, if the communication node type is a cell, the node ID is a cell identity code, which is expressed in decimal form in the range of 0-65535.

[0150] For example, if the communication node type is a base station, the node ID is the location area identification (LAI) code, which includes MCC, MNC, and location area code (LAC). MCC (mobile country code): a three-digit decimal number ranging from 000 to 999, for example, 460 for country A; MNC (mobile network code): a two-digit decimal number ranging from 00 to 99; and LAC (location area code): a range from 1 to 65535.

[0151] (7) Event Type

[0152] Event type: This field indicates the type of event corresponding to the experience degradation event. Different service types have different event types. For example, for video services, event types include but are not limited to freezes and unclear video; for conversation services, event types include but are not limited to dropped calls and swallowed text.

[0153] Table 2

[0154] Specifically, service access volume indicates information about the same service as the experience degradation event, including the total number of service accesses to the same service as the experience degradation event on the current operator's network. The specific content is shown in Table 3, including service type, application ID, area ID, user ID, and topology node.

[0155] The detailed definitions of the service type, application ID, area ID, and user ID can be found in Table 2 and will not be repeated here.

[0156] The topology node indicates the communication domains and / or communication nodes that a user traverses when accessing a service, including a sequence node list. The sequence node list contains information about multiple communication nodes. This information includes sequence numbers, node types, and node IDs. For a detailed explanation, refer to the definition of the sequence node list in the event topology node and will not be repeated here.

[0157] Table 3

[0158] S404: The cross-domain MDAS demarcates the experience problem and determines the problem object based on the received information about the experience degradation event, the service access volume, and the service topology of the experience degradation event.

[0159] The received experience degradation event information, service visits, and service topology of the experience degradation event are included in the subscription response sent by the data source. For details on the experience degradation event information, service visits, and service topology of the experience degradation event, see S403 and will not be repeated here.

[0160] The problem objects include the communication domain and / or communication nodes that cause the experience problem.

[0161] Specifically, the cross-domain MDAS demarcates the experience problem and determines the problem object based on the information of the experience degradation event, the service access volume, and the service topology of the experience degradation event, including: when an experience degradation event occurs when a user accesses a service, poor service quality will be recorded once on each communication node in the event topology node in Table 2. When a user accesses a service (including poor service quality and good service quality), poor service quality or good service quality will be recorded once on each communication node in the topology node in Table 3. The quality difference ratio of each communication node can be obtained through the records in Tables 2 and 3. Furthermore, by comparing the quality difference ratios of each communication node, the communication node suspected of being the problem object can be preliminarily found, and then by using the quality difference transmission logic and comparing the quality difference conditions of adjacent communication nodes, the problem object can be determined, thereby achieving the demarcation of the problem object for the experience problem.

[0162] Specifically, poor service quality refers to a user experience degradation when accessing a service, while good service quality refers to a user experience degradation. The logic behind poor service quality transmission is embedded in the statistics of poor service quality. This means that if a communication node has a problem, services passing through it are likely to be affected. This means that adjacent communication nodes interacting with this node will also be subject to poor service quality.

[0163] For example, the experience degradation event is video freeze. Table 2 records five occurrences of video freeze (experience degradation event). Of the five topology node records, Cell 1 recorded two, gNB1 recorded five, and UPF1 recorded two. Table 3 records 10 video service occurrences. Of the 10 topology node records, Cell 1 recorded eight, gNB1 recorded ten, and UPF1 recorded ten. Based on the records in Tables 2 and 3, we can see that the quality degradation ratio for Cell 1 is 0.25, the quality degradation ratio for gNB1 is 0.5, and the quality degradation ratio for UPF1 is 0.2. The communication node initially suspected to be the problem is gNB1. Furthermore, if the video services of Cells A, B, and C all pass through gNB1, the records in Tables 2 and 3 show that the quality degradation ratio for Cell A is 0.8, the quality degradation ratio for Cell B is 0.2, and the quality degradation ratio for Cell C is 0.1. If the problem is with gNB1, then all video services passing through gNB1 will be affected. That is, the proportion of poor quality in cells B and C should be much higher than the current level. Therefore, it can be determined that the problem is not with gNB1, but with cell A.

[0164] It should be understood that the above method of determining the problem object by counting the proportion of poor quality of communication nodes, the poor quality transmission logic, and comparing the poor quality of adjacent communication nodes is based on manual experience. This solution does not limit the determination of the problem object (i.e., the communication domain and / or communication node that causes the experience problem) and can also be determined by other methods.

[0165] For example, a model for determining the problem object is built through a neural network, with the service topology of the experience degradation event recorded in the obtained QoE data, the service access volume of the same service as the experience degradation event, the communication nodes passed by each service in the service access volume, the service volume carried by each communication node, the proportion of poor quality in each communication node, and other information as input data; the problem object of the experience problem is used as output data; therefore, the cross-domain MDAS can directly obtain the problem object of the experience problem through the output of this model.

[0166] S405: The cross-domain MDAS sends a root cause request to the single-domain MDAS based on the problem object. In response, the single-domain MDAS receives the root cause request.

[0167] The single-domain MDAS is the single-domain MDAS for the domain to which the problem object belongs, and includes at least one of the following: a wireless network domain MDAS or a core network domain MDAS. For example, if the problem object determined in S404 is gNB1, the single-domain MDAS is the wireless network domain MDAS. Alternatively, if the problem objects determined in S404 are gNB1 and UPF1, the single-domain MDAS is the wireless network domain MDAS or the core network domain MDAS.

[0168] The root cause request is used by the cross-domain MDAS to request the root cause of the problem object, including the problem object, from the single-domain MDAS.

[0169] For example, the problem object determined in S404 is AMF1, and the single-domain MDAS is the core network domain MDAS. Subsequently, the cross-domain MDAS sends a root cause request including AMF1 to the core network domain MDAS. Correspondingly, the core network domain MDAS receives the root cause request including AMF1.

[0170] It should be understood that S405 is an optional execution. If it is determined in S404 that the domain to which the problem object belongs is the terminal side and / or SP side, and the relevant configuration information of the problem object cannot be obtained, the experience problem caused by the terminal side and / or SP side cannot be solved through network optimization, and S405 will not be executed.

[0171] If it is determined in S404 that the domain of the problem object is the terminal side and / or the SP side, and relevant configuration information of the problem object can be obtained, the root cause of the problem object can be further determined based on the obtained relevant configuration information of the problem object. And / or, if it is determined in S404 that the domain of the problem object is the RAN domain, CN domain, or TN domain, the experience problem can be resolved through network optimization, and S405 is executed.

[0172] S406: The single-domain MDAS determines the root cause of the problem object based on the root cause request, and sends the root cause of the problem object to the cross-domain MDAS.

[0173] Specifically, the single-domain MDAS determines the root cause of the problem object based on the root cause request, including: the single-domain MDAS directly reads the problem of the problem object from its own stored call history record (CHR) data, alarm data and other data, and the problem of the problem object includes the root cause of the problem object.

[0174] CHR data is a file or data within a file that is written each time a specific event occurs in a device or controlled application, and records the cause of that specific event. For example, CHR data can be written when an application error occurs, recording the cause of the error. Alternatively, CHR data can include a historical record of all events that have occurred in the application.

[0175] Alarm data is a file or data within a file that is written to the file each time an alarm event occurs on a device or in a controlled application. It also records the cause of the alarm event. For example, the cause of the alarm event recorded in the alarm data might be a power alarm or a board load alarm.

[0176] For example, the single-domain MDAS is the wireless network domain MDAS, and the problem object is gNB1. The wireless network domain MDAS reads from the CHR data and alarm data stored in itself that the problems with gNB1 are power alarms, single-board load alarms, etc., including the root cause of gNB1.

[0177] It should be understood that S406 is optional. When S405 is executed, S406 is executed to determine the root cause of the problem object. When S405 is not executed, the experience problem cannot be solved through network optimization, and there is no way to further determine the root cause of the problem object, so S406 is not executed.

[0178] S407: The cross-domain MDAS receives the root cause of the problem object and generates an analysis report.

[0179] The analysis report is used to indicate the problem object and / or the root cause of the problem object. The analysis report includes but is not limited to the content in Table 1. The detailed description is shown in S402.

[0180] Specifically, the analysis report may optionally include the root cause of the problem object. If S406 is executed and the single-domain MDAS can determine the root cause of the problem object, the analysis report may include the root cause of the problem object. If S406 is not executed and the single-domain MDAS cannot determine the root cause of the problem object, the analysis report does not include the root cause of the problem object.

[0181] S408: The cross-domain MDAS sends the analysis report to the notification consumer. Correspondingly, the notification consumer receives the analysis report and forwards the analysis report to the subscribed consumer.

[0182] The notification consumer is used to forward the analysis report to subscribed consumers, such as user terminals, NFs, and APs.

[0183] Based on the experience problem demarcation method shown in Figure 4, the cross-domain MDAS can demarcate the problem object of the experience problem based on the information obtained about the experience degradation event, the service access volume, and the service topology of the experience degradation event, determine the problem object and the root cause of the problem object, so that by optimizing the problem object and / or solving the root cause of the problem object, the logic supporting the subsequent optimization closed loop can be implemented to achieve the goal of resolving or alleviating the experience problem.

[0184] In this application, there are two ways for the cross-domain MDAS in Figure 3 to obtain the first information. The second way is for the cross-domain MDAS to obtain information about the experience degradation event and service access volume. Subsequently, based on the obtained information about the experience degradation event, service access volume, and managed communication domains and / or communication nodes, the cross-domain MDAS obtains the service topology of the experience degradation event, thereby obtaining the first information. The specific experience problem demarcation method is shown in Figure 5.

[0185] FIG5 shows a method for defining an experience problem according to an embodiment of the present application. The method includes the following steps:

[0186] Steps S501 to S502 are the same as steps S401 to S402 and will not be described again here.

[0187] S503: The cross-domain MDAS sends a subscription request to the data source based on the analysis instance. In response, the data source sends a subscription response to the cross-domain MDAS.

[0188] The data source is used to provide QoE data for the cross-domain MDAS, including but not limited to AF and / or NWDAF.

[0189] Specifically, the AF can exchange data with other NFs to provide services to terminals. The NWDAF can collect data from other NFs and / or similar data collection programs through a subscription or request model to provide quality of experience (QoE) data to the cross-domain MDAS. QoE data represents a user's subjective perception of the quality and performance of devices, networks, systems, applications, or services, such as latency and throughput.

[0190] The subscription request is used to obtain QoE data, which includes information about experience degradation events and service access volume.

[0191] The subscription response is used to respond to the subscription request sent by the cross-domain MDAS, including information about experience degradation events and service visits.

[0192] Specifically, the specific content of experience degradation event information and service access volume is shown in Table 4, including but not limited to: service type, network slice ID, application ID, statistics on the proportion of poor quality events in each network element in the wireless network domain, and statistics on the proportion of poor quality events in each network element in the core network domain.

[0193] Table 4

[0194] The percentage of poor quality events for each network element in the wireless network domain indicates the percentage of poor quality events for each network element in the wireless network domain and can be expressed as a percentage. For example, the percentage of poor quality events for cell A is 56%, while the percentage of poor quality events for base station B is 48%.

[0195] The percentage of poor quality events for each network element in the core network domain indicates the percentage of poor quality events for each network element in the core network domain. For example, the percentage of poor quality events for UPF1 is 61%, and the percentage of poor quality events for AMF1 is 38%.

[0196] Among them, the relevant descriptions of service type, network slice ID, and application ID can be referred to S405 and will not be repeated here.

[0197] S504: The cross-domain MDAS generates a service topology for the experience degradation event based on the subscription response and the managed network element range.

[0198] The subscription response includes the information of the experience degradation event in S503 and the service access volume. The detailed description is given in S503 and will not be repeated here.

[0199] Specifically, the cross-domain MDAS generates the service topology for the experience degradation event. The single-domain MDAS restores the service topology of the single domain based on the service routing policy configuration of the managed network elements. The cross-domain MDAS then stitches the single-domain service topology into a complete service topology. The single-domain MDAS includes the wireless domain MDAS and / or the core domain MDAS.

[0200] For example, the experience degradation event is session swallowing. The wireless network domain MDAS restores the service topology of this session service (this session service can be understood as the service corresponding to the session swallowing) in the wireless network domain to cell 1 and gNB1 according to the service routing policy configuration of the managed network element; the core network domain MDAS restores the service topology of this session service in the core network domain to AMF1, SMF1, and UPF1 according to the service routing policy configuration of the managed network element; then, the cross-domain MDAS splices the service topology of the wireless network domain and the service topology of the core network domain. The complete service topology of the experience degradation event includes cell 1, gNB1, AMF1, SMF1, and UPF1.

[0201] It should be understood that the cross-domain MDAS generates the service topology of the experience degradation event. This method can restore the service topology in the wireless network domain and / or the core network domain, so that the experience problem can be subsequently demarcated to determine the problem object and the root cause of the problem object in the wireless network domain and / or the core network domain.

[0202] Steps S505 to S509 are the same as steps S404 to S408 and will not be described in detail here.

[0203] Based on the experience problem demarcation method shown in Figure 5, the service topology for experience degradation events is obtained without relying on a single-domain MDAS. Instead, the cross-domain MDAS generates the service topology for experience degradation events within the scope of network elements it manages, reducing the processing complexity of the cross-domain MDAS and improving the efficiency of obtaining the service topology for these events. Furthermore, based on the acquired experience degradation event information, service access information, and the generated service topology for the experience degradation event, the cross-domain MDAS demarcates the problem object, identifies the problem object and its root cause, and implements an optimization closed loop to support subsequent issues.

[0204] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the interaction between each network element and the device. It can be understood that each network element and device, such as subscription consumers, notification consumers, cross-domain MDAS, single-domain MDAS, data source, etc., in order to realize the above functions, includes hardware structures and / or software modules corresponding to the execution of each function. It should be easy for those skilled in the art to realize that, in combination with the 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 executed in a hardware or computer software-driven hardware manner 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.

[0205] In the embodiment of the present application, the functional modules of subscription consumers, notification consumers, cross-domain MDAS, single-domain MDAS, data sources, etc. can be grouped according to the above-mentioned method examples. For example, each functional module can be grouped according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the grouping of modules in the embodiment of the present application is schematic and is only a logical functional grouping. There may be other grouping methods in actual implementation.

[0206] Figure 6 shows a structural diagram of a communication device 60, which can be used to perform the cross-domain MDAS (or cross-domain MDAS, or cross-domain management data analysis service) functions involved in the above embodiments. As an implementation method, the communication device 60 shown in Figure 6 includes: a processing unit 601, a transceiver unit 602;

[0207] The processing unit 601 is configured to obtain the first information and, based on the first information, delimit the experience problem, determine the problem object and the root cause of the problem object. For example, the processing unit 601 may be configured to support the communication device 60 in executing S403, S404, and S407, or in executing S503, S504, S505, and S508.

[0208] The transceiver unit 602 is configured to send an analysis report indicating a problem object and / or a root cause of the problem object to a subscribing consumer. For example, the sending unit 602 may support the communication device 60 to execute S408 or S509.

[0209] For the description of the first information, the problem object, the root cause of the problem object, and the analysis report, reference may be made to that in the above method embodiment.

[0210] Specifically, all relevant content of each step involved in the method embodiments shown in Figures 4 and 5 can be referenced in the functional descriptions of the corresponding functional modules and will not be repeated here. Communication device 60 is used to perform the cross-domain MDAS functions in the experience problem demarcation method shown in Figures 4 or 5, thereby achieving the same effect as the above-mentioned experience problem demarcation method.

[0211] As another possible implementation, the communication device 60 shown in FIG6 includes: a processing module and a communication module. The processing module is used to control and manage the operations of the communication device 60. For example, the processing module can integrate the functions of the processing unit 601 and can be used to support the communication device 60 in executing S403, S404, and S407, or can be used to support the communication device in executing S503, S504, S505, S508, and other processes of the technology described herein. The communication module can integrate the functions of the transceiver unit 602 and can be used to support the communication device 60 in executing S408, or can be used to support the communication device 60 in executing S509 and communicating with other network entities, such as communication between the functional modules or network entities shown in FIG4 and FIG5. The communication device 60 may also include a storage module for storing program code and data of the communication device 60.

[0212] Figure 7 shows a structural diagram of a communication device 70, which can be used to perform the functions of the single-domain MDAS (or single-domain management data analysis service) involved in the above embodiments. As an implementation method, the communication device 70 shown in Figure 7 includes: a processing unit 701, a transceiver unit 702;

[0213] Processing unit 701 is configured to obtain second information indicating a problem object experiencing a problem, and to determine a root cause of the problem object based on the second information. For example, processing unit 701 may be configured to support communication device 70 in executing SS405 and SS406, or may be configured to support communication device 70 in executing S506 and S507.

[0214] The transceiver unit 702 is configured to send the root cause of the problem object to the cross-domain management data analysis service. For example, the transceiver unit 702 may support the communication device 70 to execute S406 or S507.

[0215] Among them, the relevant descriptions of the second information, the root cause of the problem object, and the cross-domain management data analysis service (also called cross-domain MDAS) can refer to those described in the above method embodiment.

[0216] Specifically, all relevant content of each step involved in the method embodiments shown in Figures 4 and 5 can be referenced in the functional descriptions of the corresponding functional modules and will not be repeated here. Communication device 70 is used to perform the functions of the single-domain MDAS in the experience problem demarcation method shown in Figures 4 or 5, thereby achieving the same effect as the above-mentioned experience problem demarcation method.

[0217] As another possible implementation, the communication device 70 shown in FIG7 includes: a processing module and a communication module. The processing module is used to control and manage the operations of the communication device 70. For example, the processing module may integrate the functions of the processing unit 701 and may be used to support the communication device 70 in executing SS405, SS406, or executing S506, S507, and other processes of the technology described herein. The communication module may integrate the functions of the transceiver unit 702 and may be used to support the communication device 70 in executing S406 or S507 and communicating with other network entities, such as communication with the functional modules or network entities shown in FIG4 and FIG5. The communication device 70 may also include a storage module for storing program code and data of the communication device 70.

[0218] As mentioned above, the processing module may be a processor or a controller. It may implement or execute the various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication module may be a transceiver circuit or a communication interface, and so on. The storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 60 and the communication device 70 involved in the embodiment of the present application may be the communication device 80 shown in Figure 8. For example, the cross-domain MDAS and single-domain MDAS mentioned above may adopt the composition structure shown in Figure 8 or include the components shown in Figure 8. Figure 8 is a schematic diagram of the composition of a communication device 80 provided in an embodiment of the present application. As shown in Figure 8, the communication device 80 may include a processor 801, a communication line 802 and a communication interface 803.

[0219] Furthermore, the communication device 80 may further include a memory 804 . The processor 801 , the memory 804 and the communication interface 803 may be connected via a communication line 802 .

[0220] The processor 801 may be a central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor 801 may also be other communication devices with processing capabilities, such as circuits, devices, or software modules.

[0221] The communication line 802 is used to transmit information between the components included in the communication device 80.

[0222] The communication interface 803 is used to communicate with other devices or other communication networks. The other communication network can be Ethernet, a radio access network (RAN), a wireless local area network (WLAN), etc. The communication interface 803 can be a radio frequency module, a transceiver, or any communication device capable of achieving communication. The embodiment of the present application is described using the communication interface 803 as an example of a radio frequency module, wherein the radio frequency module may include an antenna, a radio frequency circuit, etc., and the radio frequency circuit may include a radio frequency integrated chip, a power amplifier, etc.

[0223] The memory 804 is used to store instructions, where the instructions may be computer programs.

[0224] Among them, the memory 804 can be a read-only memory (ROM) or other types of static storage devices that can store static information and / or instructions, or a random access memory (RAM) or other types of dynamic storage devices that can store information and / or instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage, magnetic disk storage media or other magnetic storage devices, and optical disc storage includes compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.

[0225] It should be noted that the memory 804 can exist independently of the processor 801 or can be integrated with the processor 801. The memory 804 can be used to store instructions, program code, or some data. The memory 804 can be located within the communication device 80 or outside the communication device 80, without limitation. The processor 801 is configured to execute the instructions stored in the memory 804 to implement the communication method provided in the following embodiments of this application.

[0226] In one example, the processor 801 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 8 .

[0227] As an optional implementation, the communication device 80 includes multiple processors. For example, in addition to the processor 801 in FIG. 8 , it may also include a processor 807 .

[0228] As an optional implementation, the communication device 80 further includes an output device 805 and an input device 806. The input device 806 is a keyboard, a mouse, a microphone, or a joystick, and the output device 805 is a display screen, a speaker, or other devices.

[0229] It should be noted that the communication device 80 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system, or a device having a structure similar to that shown in FIG8 . Furthermore, the structure shown in FIG8 does not limit the communication device. In addition to the components shown in FIG8 , the communication device may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0230] In the embodiment of the present application, the chip system can be composed of chips, or can include chips and other discrete devices.

[0231] The embodiments of the present application also provide a computer-readable storage medium. All or part of the processes in the above-mentioned method embodiments can be completed by a computer program to instruct the relevant hardware, and the program can be stored in the above-mentioned computer-readable storage medium. When the program is executed, it can include the processes of the above-mentioned method embodiments. The computer-readable storage medium can be a terminal in any of the above-mentioned embodiments, such as: an internal storage unit including a data transmission end and / or a data receiving end, such as a hard disk or memory of the terminal. The above-mentioned computer-readable storage medium can also be an external storage device of the above-mentioned terminal, such as a plug-in hard disk equipped on the above-mentioned terminal, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, a flash card (flash card), etc. Further, the above-mentioned computer-readable storage medium can also include both the internal storage unit of the above-mentioned terminal and an external storage device. The above-mentioned computer-readable storage medium is used to store the above-mentioned computer program and other programs and data required by the above-mentioned terminal. The above-mentioned computer-readable storage medium can also be used to temporarily store data that has been output or is to be output.

[0232] It should be understood that the collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution of this application complies with relevant laws and regulations and does not violate public order and good morals. For example, in the technical solution of this application, the processing of user personal information is carried out with the user's authorization, and the same description is not repeated here.

[0233] It should be noted that the terms "first" and "second" in the specification, claims, and drawings of this application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products, or devices.

[0234] It should be understood that in the present application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural 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", or "a and b and c", where a, b, c can be single or multiple.

[0235] It should be understood that in the embodiments of the present application, "B corresponding to A" means that B is associated with A. For example, B can be determined based on A. It should also be understood that determining B based on A does not mean determining B based solely on A; B can also be determined based on A and / or other information. In addition, the "connection" in the embodiments of the present application refers to various connection methods, such as direct connection and indirect connection, to achieve communication between devices, and the embodiments of the present application do not impose any limitations on this.

[0236] Unless otherwise specified, the "transmission" (transmit / transmission) appearing in the embodiments of the present application refers to bidirectional transmission, including the actions of sending and / or receiving. Specifically, the "transmission" in the embodiments of the present application includes the sending of data, the receiving of data, or the sending of data and the receiving of data. In other words, the data transmission here includes uplink and / or downlink data transmission. Data may include channels and / or signals, uplink data transmission is uplink channel and / or uplink signal transmission, and downlink data transmission is downlink channel and / or downlink signal transmission. The "network" and "system" appearing in the embodiments of the present application express the same concept, and the communication system is the communication network.

[0237] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the grouping of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be grouped into different functional modules to complete all or part of the functions described above.

[0238] In the several embodiments provided in this application, it should be understood that the disclosed communication devices and methods can be implemented in other ways. For example, the communication device embodiments described above are merely illustrative. For example, the grouping of the modules or units is merely a logical functional grouping. In actual implementation, there may be other grouping methods, such as multiple units or components can be combined or integrated into another device, 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 interface, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0239] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0240] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0241] If the integrated unit is implemented in the form of 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 solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device, such as a single-chip microcomputer, a chip, etc., or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media for storing program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0242] 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 the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for defining an experience problem, characterized in that: The method comprises: Acquire first information, where the first information is used to indicate information about an experience degradation event, a service access volume, and a service topology of the experience degradation event; the experience degradation event includes an event in which an experience problem exists in an event of accessing a service through a current operator network, and the experience problem includes that the access experience does not meet a preset experience requirement; the service access volume includes a total amount of service accesses belonging to the same service as the experience degradation event through the current operator network; the service topology of the experience degradation event is used to indicate a communication network topology when a user accesses the experience degradation event, and the communication network topology includes multiple communication domains, and each communication domain includes at least one communication node; Delimit the experience problem based on the first information, and determine the problem object and the root cause of the problem object; the problem object includes the communication domain and / or communication node that causes the experience problem; An analysis report is sent to a subscribing consumer; the analysis report is used to indicate the problem object and / or the root cause of the problem object.

2. The method according to claim 1, characterized in that Defining the experience problem based on the first information to determine the problem object and the root cause of the problem object includes: Sending second information to the single domain management data analysis service; the second information is used to determine the root cause of the problem object; An analysis report is generated based on the root cause of the problem object sent by the single domain management data analysis service.

3. The method according to claim 1, characterized in that The obtaining of the service topology of the experience degradation event includes: acquiring the first information; Based on the first information and the managed communication domain and / or communication node, the service topology of the experience degradation event is acquired.

4. The method according to claim 1, characterized in that: The obtaining of the service topology of the experience degradation event includes: Sending a subscription request to a data source, where the subscription request is used to request the first information from the data source; A subscription response is received from the data source, wherein the subscription response includes the first information.

5. The method according to any one of claims 1 to 4, characterized in that: The information of the experience degradation event includes at least one of the following: the service type to which the experience degradation event belongs, the network slice identifier where the experience degradation event is located, the application identifier corresponding to the experience degradation event, the area identifier where the experience degradation event occurs, the user identifier where the experience degradation event occurs, the service topology node of the experience degradation event, or the event type of the experience degradation event; The service access volume includes at least one of the following: service type, application program identifier, area identifier, user identifier, or service topology node; The single-domain management data analysis service includes at least one of the following: a core network domain management data analysis service, or a wireless network domain management data analysis service.

6. The method according to any one of claims 1 to 5, characterized in that: The analysis report includes at least one of the following: the problem domain type, the problem object, or the business experience simulation node; wherein, The problem domain type is used to indicate the type of the domain to which the problem object belongs, including at least one of the terminal side, the transmission side, the service provider side, the wireless network side, and the core network side; The service experience simulation node is used to indicate the degree of improvement of user experience after the experience problem is solved.

7. A method for defining an experience problem, characterized in that: The method comprises: Acquire second information; the second information is used to indicate the problem object of the experience problem; Based on the second information, determining a root cause of the problem object; The root cause of the problem object is sent to a cross-domain management data analysis service.

8. A communication device, characterized in that: The communication device is applied to cross-domain management and analysis services, and the communication device includes: A processing unit, configured to obtain first information, and define the experience problem based on the first information, and determine the problem object and the root cause of the problem object; The transceiver unit is used to send an analysis report to a subscribing consumer, wherein the analysis report is used to indicate the problem object and / or the root cause of the problem object.

9. A communication device, characterized in that: The communication device comprises a processor and a communication interface, and the processor and the communication interface are used to support the communication device to execute the experience problem delimiting method according to any one of claims 1-6.

10. A communication device, characterized in that: The communication device is applied to a single domain management and analysis service, and the communication device includes: A processing unit, configured to obtain second information, and determine a root cause of the problem object based on the second information; The transceiver unit is used to send the root cause of the problem object to the cross-domain management data analysis service.

11. A communication device, characterized in that: The communication device comprises a processor and a communication interface, and the processor and the communication interface are used to support the communication device to execute the experience problem delimiting method as claimed in claim 7.

12. A communication system, characterized in that: The communication system includes the communication device according to claim 8 or claim 9, or the communication system includes the communication device according to claim 10 or claim 11.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the computer executes the method according to any one of claims 1 to 6, or the computer executes the method according to claim 7.

14. A computer program product, characterized in that The computer program product comprises computer instructions, and when the computer instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 6, or the method according to claim 7.

Images