Experience question delimiting method, device and system

Abstract

The invention discloses an experience problem delimiting method, device and system, relates to the technical field of communication, and solves the problem that the experience problem cannot be delimited due to the fact that the delimiting range is too large and a specific root cause problem object cannot be delimited and the delimiting analysis range is incomplete under the condition that experience problem analysis comprises rough delimiting of an experience problem. The problems that an optimization strategy for solving the experience problem cannot be formulated, and the user experience cannot be improved exist. The method comprises the steps that a cross-domain MDAS obtains information used for indicating an experience degradation event, a service access amount and first information of a service topology of the experience degradation event, experience problem delimitation is carried out based on the first information, a problem object and a root cause of the problem object are determined, and then an analysis report is sent to subscription consumption. Wherein the root cause of the problem object is determined by the single-domain MDAS based on the second information, and then the single-domain MDAS sends the root cause of the problem object to the cross-domain MDAS. The scheme of the invention can be widely applied to the fields of communication technology, artificial intelligence, Internet of Vehicles, smart home networking and the like.

Description

Technical Field

[0001] 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

[0002] Management data analytics (MDA) uses artificial intelligence (AI) and / or machine learning (ML) technologies to bring automation and intelligence to network service management and orchestration, and is a key driver of automation and intelligence. MDA functions include service experience analysis and coverage-related analytics. Among them, service experience analysis is used for experience problem analysis, experience problem statistics, and experience problem prediction.

[0003] Experience problem analysis includes roughly defining the experience problem. For example, the experience problem analysis can roughly determine that the communication domain that causes the experience problem is the core network domain and / or the wireless network domain. When the experience problem analysis includes roughly defining the experience problem, the specific root cause problem object cannot be defined because the scope of the definition is too large and not specific, and the scope of the definition analysis is incomplete. Therefore, it is impossible to formulate an optimization strategy to solve the experience problem and improve the user experience. Summary of the invention

[0004] The embodiments of the present application provide a method, device and system for delimiting an experience problem, so as to solve the problem that when the experience problem analysis includes roughly delimiting the experience problem, the specific root cause problem object cannot be delimited because the delimitation scope is too large and not specific, and the delimitation analysis scope is incomplete, so there is a problem that it is impossible to formulate an optimization strategy to solve the experience problem and improve the user experience.

[0005] In order to achieve the above objectives, this application adopts the following technical solutions:

[0006] In the first aspect, the present application provides a method, device and system for delimiting an experience problem. The method can be executed by a cross-domain management data analytics service (MDAS) and a functional module or chip in the cross-domain MDAS. Taking the cross-domain MDAS execution as an example, the method includes: the cross-domain MDAS obtains information indicating an experience degradation event, service access volume, and first information of the service topology of the experience degradation event, delimits 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 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 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.

[0007] Based on the method described in the first aspect, the cross-domain MDAS can determine the communication domain and / or communication node that causes the experience problem based on the first information, and determine 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 causes the experience problem, and 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.

[0008] In one possible design, the cross-domain MDAS delimits the experience problem based on the first information, and 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.

[0009] Based on this possible design, the cross-domain MDAS can determine the root cause of the problem object through the single-domain MDAS, and further, generate an analysis report based on the single-domain MDAS to determine the root cause of the problem object. The generated analysis report can provide effective support for subscribing consumers to formulate optimization strategies to solve the experience problem.

[0010] 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.

[0011] 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 domain and / or communication node managed by itself, and 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, thereby reducing the processing complexity of the cross-domain MDAS and the efficiency of obtaining the service topology of the experience degradation event.

[0012] 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, the subscription request is used to request first information from the data source; and receiving a subscription response from the data source, the subscription response including the first information.

[0013] Based on this possible design, the cross-domain MDAS directly obtains the business topology of the experience degradation event from the data source, which provides a possible solution for the cross-domain MDAS to obtain the business topology of the experience degradation event, and improves the flexibility and diversity of the cross-domain MDAS to obtain the business topology of the experience degradation event.

[0014] In one possible design, 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, 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.

[0015] 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.

[0016] 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, 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 in user experience after the experience problem is solved.

[0017] 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.

[0018] On the second aspect, the present application provides an experience problem demarcation method, device and system. 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.

[0019] Based on the method described in 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.

[0020] 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 in the first aspect. The communication device may implement the functions performed by the cross-domain MDAS in the above aspects or possible designs, and the functions may 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,

[0021] 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;

[0022] 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.

[0023] Specifically, the relevant descriptions of the first information, the problem object, the root cause of the problem object, and the analysis report may 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 may refer to the first aspect or any possible design of the first aspect and will not be repeated here.

[0024] 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. Among them, the processor and the communication interface are used to support the communication device to execute the experience problem delimiting method in the first aspect or any possible design of the first aspect. In another possible design, the communication device may also 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 delimiting method as described in the above-mentioned first aspect or any possible design of the first aspect.

[0025] 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 method in the second aspect. 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 executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions. For example, the communication device may include a processing unit and a transceiver unit. Among them,

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

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

[0028] Specifically, the relevant description of the second information and the root cause of the problem object may 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 may refer to the second aspect or any possible design of the second aspect, and will not be repeated here.

[0029] 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. Among them, the processor and the communication interface are used to support the communication device to execute the experience problem delimiting method in the second aspect or any possible design of the second aspect. In another possible design, the communication device may also 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 delimiting method as described in the above-mentioned second aspect or any possible design of the second aspect.

[0030] 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.

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

[0032] 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.

[0033] 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 first aspect or any possible design of the first aspect, and will not be repeated. 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 second aspect or any possible design of the second aspect, and will not be repeated. 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 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 second aspect or any possible design of the second aspect, and will not be repeated. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0035] Figure 2 A schematic diagram of a communication system provided in an embodiment of the present application;

[0036] Figure 3 A flowchart of a method for defining an experience problem provided in an embodiment of the present application;

[0037] Figure 4 A flowchart of a method for defining an experience problem provided in an embodiment of the present application;

[0038] Figure 5 A flowchart of a method for defining an experience problem provided in an embodiment of the present application;

[0039] Figure 6 A schematic diagram of the structure of a communication device provided by the present application;

[0040] Figure 7 A schematic diagram of the structure of a communication device provided by the present application;

[0041] Figure 8 A schematic diagram of the structure of a communication device provided in this application. DETAILED DESCRIPTION

[0042] 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 required by the embodiments of the present application.

[0043] Management data analytics (MDA) uses artificial intelligence (AI) and / or machine learning (ML) technologies to bring automation and intelligence to network service management and orchestration, and is a key enabler of automation and intelligence. MDA can perform data processing and data analysis on network management data and provide analysis output. The analysis output is provided by the management data analytics service (MDAS) producer to the MDA subscription consumer who requested the analysis.

[0044] MDAS is a service disclosed 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.

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

[0046] MDA can be based on Figure 1 The architecture shown in the figure is used to analyze network management data. Figure 1 As shown, the network architecture includes: 3rd generation partnership project (3GPP) cross-domain management data analysis management service consumer (cross-domain MDAMnS consumer), 3GPP cross-domain management data analysis management service producer (cross-domain MDA MnS producer), core network domain management data analysis management service producer (corenetwork domain MDA MnS producer, CN-domain MDA MnS producer), radio access network domain management data analysis management service producer (radio access network domain MDA MnS producer, RAN-domainMDA MnS producer), NWDAF, other fifth-generation mobile communication technology core network functions (other 5GCNF), and the next generation base station (the next generation node b, gNB).

[0047] Among them, the 3GPP cross-domain MDA MnS consumer (referred to as MDA subscription consumer and / or subscription consumer for short) 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.

[0048] 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, utilize 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 the MDA MnS available to the 3GPP cross-domain MDA MnS consumer.

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

[0050] Among them, the CN-domain MDA MnS producer can interact 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.

[0051] 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 the services provided by the gNB to analyze the network management data.

[0052] Among them, NWDAF is a data-aware analysis network element. 3GPP defines that NWDAF can collect raw data from NF, AF, operation administration and maintenance (OAM), and perform intelligent analysis on the raw data, and output the analysis data to NF, AF, OAM, etc. for optimizing the network and services. At the same time, NWDAF can also collect information such as network performance, service load in a specific area, user service experience, etc., and use reliable network performance analysis and prediction models to evaluate and analyze different types of services, determine the intrinsic correlation between the service quality of experience (QoE) and the service path, and optimize 5G edge computing. 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.

[0053] 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.

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

[0055] 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.

[0056] Among them, the service experience analysis function is used to analyze the user's service experience. The 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, the experience problem analysis includes but is not limited to the rough demarcation of the core network domain and the wireless network domain for the experience problem. 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, and lacks the problem analysis that identifies the terminal side, the transmission side, and the service provider (service provider, SP) side, resulting in an incomplete scope of the problem analysis.

[0057] At the same time, when the experience problem analysis roughly delimits the core network domain and / or wireless network domain of the experience problem, the communication node (for example, user-side network element, base station, etc.) that causes the experience problem is not accurately identified, and a corresponding optimization strategy cannot be formulated 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.

[0058] 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. Among them, 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.

[0059] The following describes the experience problem demarcation method provided in the embodiment of the present application in conjunction with the accompanying drawings.

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

[0061] Figure 2 A schematic diagram of a communication system provided in an embodiment of the present application, such as Figure 2 As shown, 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 understandable that the devices in the communication system 20 can communicate directly or through forwarding by other devices, and the embodiment of the present application does not specifically limit this.

[0062] Understandably, the above Figure 2 It is only a schematic diagram and does not constitute a limitation on the applicable scenarios of the technical solution provided in this application. Those skilled in the art should understand that in the specific implementation process, the communication system 20 may also include Figure 2 The communication system 20 may include fewer devices, or other devices. The number of devices in the communication system 20 may also be determined according to specific needs without limitation. Figure 2 The equipment in the system shown is described.

[0063] 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 referred to as the 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, terminal users subscribing to MDA, NF subscribing to MDA, etc.). The single-domain MDAS producer, which can also be referred to as the 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 the cross-domain MDAS producer. 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.

[0064] The terminal may be a terminal equipment (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 may be a device that can support the terminal to realize the function, such as a chip system (e.g., a processing system composed of one chip or multiple chips) or a modem. The following takes the terminal as an example to describe the experience problem delimitation method provided in an embodiment of the present application.

[0065] 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 node in 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 processing system composed of one chip or multiple chips) or a modem. The following takes the device for implementing the function of the access network device as an example, which is an access network device, to describe the experience problem demarcation method provided in an embodiment of the present application.

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

[0067] Service provider (SP) equipment: refers to equipment managed by a service provider, which is used to develop or provide services that meet user needs according to user needs.

[0068] Transmission equipment refers to equipment that serves the transmission network. The transmission network, as the core of the entire optical fiber network, is the network with the fastest transmission rate in the entire telecommunications network.

[0069] Optional, Figure 2 Each device in the communication device (such as a terminal, an access network device, a core network device, a cross-domain MDAS producer, a single-domain MDAS producer, etc.) may also be referred to as a communication device, which may be a general device or a dedicated device. The embodiments of the present application do not specifically limit this.

[0070] Optional, this application Figure 2 The related functions of each device in the network can be implemented by one device, or by multiple devices together, or by one or more functional modules in one device, and the embodiments of the present application do not specifically limit this. It is understandable that the above functions can be network elements in hardware devices, or software functions running on dedicated hardware, or a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0071] Combine the following Figure 2 The communication system shown describes the experience problem demarcation method provided in the embodiment of the present application. The actions, terms, etc. involved in the following embodiments can refer to each other. The message name or parameter name in the message exchanged between devices in each embodiment is only an example. Other names can also be used in specific implementations. For example, "corresponding" in the following embodiments can be replaced by "associated" and the like.

[0072] Figure 3 A flowchart of a method for defining an experience problem provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, it may include:

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

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

[0075] 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.

[0076] Specifically, the experience degradation event includes an event in which there is an experience problem in the event of accessing the service through the current operator's network, and the experience problem includes that the access experience does not meet the preset experience requirements. The operator refers to the supplier of network services, such as operator A, etc. The preset experience requirements may include but are not limited to meeting the basic requirements of the terminal user's access experience. For example, in the case where the terminal user accesses a video service with a resolution of 1920*1080, the preset experience requirements are not limited to maintaining the transmission bit rate at 8Mbps. Therefore, when the transmission bit rate is lower than 8Mbps, the terminal user has the experience problem of unclear video when accessing the video service with a resolution of 1920*1080.

[0077] The service access volume includes the total number of service accesses that belong to the same service as the experience degradation event through the current operator network. For example, when the experience degradation event is unclear video, the total number of video service accesses through the current operator network is 200 times, of which 50 times of video service access experience problems occur, resulting in poor experience quality of terminal users accessing videos.

[0078] 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 communication domain 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 transmission network domain, a terminal side, and an SP side according to the function of the communication domain.

[0079] 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.

[0080] 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.

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

[0082] Method 1: The cross-domain MDAS sends a subscription request to the data source, the subscription request is used to request the first information from the data source; then, the cross-domain MDAS receives a subscription response from the data source, the subscription response includes the first information. The first information is used to indicate information about the experience degradation event, service access volume, and service topology of the experience degradation event.

[0083] Among them, the data source is used to provide QoE data for the cross-domain MDAS, and the QoE data is used to represent the terminal user's experience and feelings of the service and / or network, which 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.

[0084] Specifically, the implementation method can refer to the following Figure 4 As described in the corresponding embodiments.

[0085] 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.

[0086] Specifically, the implementation method can refer to the following Figure 5 As described in the corresponding embodiments.

[0087] 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.

[0088] 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.

[0089] Specifically, the cross-domain MDAS delimits 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 sends 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 receives the second information sent by the cross-domain MDAS, and determines the root cause of the problem object based on the second information; further, the single-domain MDAS sends the root cause of the problem object to the cross-domain MDAS. Accordingly, the cross-domain MDAS receives the root cause of the problem object sent by the single-domain MDAS.

[0090] Specifically, the implementation method can refer to the following Figure 4or Figure 5 As described in the corresponding embodiments.

[0091] 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.

[0092] S303: The cross-domain MDAS sends the analysis report to the subscribing consumer. Correspondingly, the subscribing consumer receives the analysis report.

[0093] The analysis report is used to indicate the problem object and / or the root cause of the problem object. The analysis report may include but is not limited to the problem domain type, problem object, and service experience simulation node. 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 solved.

[0094] Specifically, the cross-domain MDAS sending the analysis report to the subscribing consumer may include: the cross-domain MDAS generates an analysis report based on the root cause of the problem object sent by the single-domain MDAS, and sends the analysis report to the subscribing consumer. Figure 4 or Figure 5 As described in the corresponding embodiments.

[0095] based on Figure 3 In the method, 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, so as to implement the experience problem analysis to define the problem object of the experience problem. At the same time, when the cross-domain MDAS determines the problem object and the root cause of the problem object, it sends an analysis report to the subscribing consumer, so that the subscribing consumer can formulate an optimization strategy to solve the experience problem based on the analysis report, so as to achieve the goal of improving the user experience.

[0096] In this application, Figure 3 There are two ways for the cross-domain MDAS to obtain the first information. The first way is that the cross-domain MDAS obtains the first information from the data source, and the first information is used to indicate the service topology of the experience degradation event. Specific experience problem demarcation methods, such as Figure 4 shown.

[0097] like Figure 4 As shown, a method for defining an experience problem is provided in an embodiment of the present application, and the method for defining an experience problem includes the following steps:

[0098] 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). Correspondingly, the cross-domain management data analysis service receives the analysis request.

[0099] 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.

[0100] The analysis request is used to request the cross-domain MDAS for the analysis output of the business experience analysis, and is also used to request the cross-domain MDAS to create a managed object instance (MOI) of the business experience analysis, including but not limited to the MDA type. The managed object instance is the analysis model corresponding to the MDA function created by the cross-domain MDAS according to different MDA functions and in accordance with the protocol agreement, including enabling data and analysis output.

[0101] 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 of service experience analysis. It should be understood that the management object instance of service experience analysis can be referred to as an analysis instance.

[0102] Optionally, the analysis request also includes control attributes related to the MDA output. The control attributes related to the MDA output include the time plan of the MDA output, the geographical location of the MDA output (i.e., the regional scope), etc. Among them, the time plan of the MDA output includes the analysis start, analysis end, and analysis duration of the MDA output; the geographical location of the MDA output is used to indicate the target area for obtaining the MDA output.

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

[0104] 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.

[0105] The analysis request response is used to confirm to the subscribing consumer that the analysis instance has been successfully created, and carries the identifier of the management object instance. The identifier of the management object instance is used to indicate that the management object instance created by the cross-domain MDAS is a management object instance for business experience analysis.

[0106] 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.

[0107] Specifically, the cross-domain MDAS creates a management object instance of the business experience analysis based on the MDA type of the business experience analysis in the analysis request. The management object instance of the business experience analysis can be referred to as an analysis instance, including enabling data and analysis output.

[0108] 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.

[0109] 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.

[0110] Table 1

[0111]

[0112] 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 may include multiple combinations. When 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.

[0113] For example, it is assumed that the experience problem of the video service is that the video is not clear, and the problem objects of the unclear video are UPF1 and gNB1. At this time, the service experience problem types include the core network side and the wireless network side. Alternatively, the problem object of the unclear video is UPF1, and at this time, the service experience problem types include the core network side.

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

[0115] For example, assuming that the experience problem of the video service is video freeze, the problem object of the video freeze is UPF1, and the service experience root cause object in the analysis output includes UPF1. Alternatively, the problem objects of the video freeze are UPF1 and gNB1, and the service experience root cause objects in the analysis output include UPF1 and gNB1.

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

[0117] 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 bad 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.

[0118] 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.

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

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

[0121] Specifically, AF can exchange data with other NFs to provide business services to terminals. NWDAF can collect data from other NFs and / or similar data collection programs through a subscription or request model to provide QoE data for cross-domain MDAS. QoE data is used to represent the user's subjective perception of the quality and performance of equipment, networks and systems, applications or services, such as latency, traffic, etc.

[0122] 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.

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

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

[0125] (1) Service type

[0126] 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.

[0127] (2) Network Slice ID

[0128] Network slice ID, used to indicate the network slice ID 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 of which serves a specific service type.

[0129] (3) Application ID

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

[0131] (4) Area ID

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

[0133] (5) User ID

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

[0135] Among them, 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 integrated services digital network number (MSISDN).

[0136] Specifically, IMSI is stored in the subscriber identity module (SIM), which refers to the ID number of the SIM card and is effective information for distinguishing mobile users. The subscriber identity module is also referred to as the SIM card. MSISDN is the number that uniquely identifies a mobile user in the public switched telephone network switching network numbering plan. Simply put, MSISDN is the mobile phone number.

[0137] 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.

[0138] 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 nation 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.

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

[0140] Exemplarily, the user identification ID includes a user identification type of IMSI and a user identification code of 460001234567890.

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

[0142] (6) Event topology node

[0143] 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, which is 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.

[0144] Specifically, the sequence node list includes information of multiple communication nodes. The communication node information includes: sequence number, node type, and node ID.

[0145] The sequence number indicates the front and back positions of the communication node in the sequence node by numbers, for example, the sequence number 1 indicates the front position of the communication node in the sequence node;

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

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

[0148] 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.

[0149] For example, if the communication node type is a base station, the node ID is a location area identification (LAI) code, including MCC+MNC+location area code (LAC). MCC (mobile country code): a three-digit decimal number with a value range of 000-999, such as 460 for country A; MNC (mobile network code): a two-digit decimal number with a value range of 00-99; LAC (location area code): a range of 1-65535.

[0150] (7) Event Type

[0151] Event type is used to indicate the event type corresponding to the experience degradation event. There are different event types for different services. For example, for video services, event types include but are not limited to freeze and unclear; for conversation services, event types include but are not limited to dropped calls and swallowed words.

[0152] Table 2

[0153]

[0154]

[0155] Specifically, the service access volume is used to indicate the service information of the same service as the experience degradation event, including the total service access volume of the same service as the experience degradation event through the current operator network. The specific content is shown in Table 3, including service type, application ID, area ID, user ID, and topology node.

[0156] Among them, the detailed interpretations of the service type, application ID, area ID, and user ID can refer to the relevant interpretations in Table 2 and will not be repeated here.

[0157] Among them, the topology node is used to indicate the communication domain and / or communication node that the user passes through when accessing the service, including a sequence node list. The sequence node list includes information of multiple communication nodes. The information of the communication node includes a sequence number, a node type, and a node ID. For detailed explanations, please refer to the relevant explanations of the sequence node list in the event topology node, which will not be repeated here.

[0158] Table 3

[0159]

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

[0161] The received experience degradation event information, service visit volume, and service topology of the experience degradation event are carried in the subscription response sent by the data source. For details of the experience degradation event information, service visit volume, and service topology of the experience degradation event, see S403, which will not be repeated here.

[0162] The problem object includes the communication domain and / or communication node that causes the experience problem.

[0163] Specifically, the cross-domain MDAS delimits 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 situations of adjacent communication nodes, the problem object can be determined, thereby achieving the delimitation of the problem object for the experience problem.

[0164] Specifically, poor service quality means that users experience degradation when accessing services, and good service quality means that users do not experience degradation when accessing services. The poor quality transmission logic exists in the statistics of poor service quality, which means that if a communication node has a problem, the services passing through this communication node will most likely be affected, that is, the communication nodes adjacent to this node and interacting with services can also be counted as poor quality.

[0165] Exemplarily, the experience degradation event is video freeze. Table 2 records that video freeze (experience degradation event) occurred five times. Among the records of the topological nodes of the five events, cell 1 recorded 2 times, gNB1 recorded 5 times, and UPF1 recorded 2 times. Table 3 records that the video service occurred 10 times. Among the 10 topological node records, cell 1 recorded 8 times, gNB1 recorded 10 times, and UPF1 recorded 10 times. It can be obtained from the records in Tables 2 and 3 that the quality difference ratio of cell 1 is 0.25, the quality difference ratio of gNB1 is 0.5, and the quality difference ratio of UPF1 is 0.2. The communication node suspected of being the problem object is initially found to be gNB1. Furthermore, if the video services of cells A, B, and C all pass through gNB1, it can be obtained from the records in Tables 2 and 3 that the quality difference ratio of cell A is 0.8, the quality difference ratio of cell B is 0.2, and the quality difference ratio of cell C is 0.1. If the problem is gNB1, then all video services passing through gNB1 will be affected. That is, the proportion of poor quality in cell B and cell C should be much higher than the current level. Therefore, it can be determined that the problem is not on gNB1, but on cell A.

[0166] It should be understood that the above method of determining the problem object by counting the quality difference ratio of communication nodes, quality difference transmission logic, and comparing the quality difference of adjacent communication nodes is based on artificial experience to determine the problem object. 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 means.

[0167] 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 acquired 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 the model.

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

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

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

[0171] Exemplarily, the problem object determined in S404 is AMF1, and the single-domain MDAS is the core network domain MDAS, and then 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.

[0172] 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.

[0173] In S404, if it is determined that the domain to which the problem object belongs is the terminal side and / or the SP side, and the relevant configuration information of the problem object can be obtained, then the root cause of the problem object can be further determined through the obtained relevant configuration information of the problem object. And / or, in S404, if it is determined that the domain to which the problem object belongs is the RAN domain, the CN domain, or the TN domain, then the experience problem can be solved through network optimization, and S405 is executed.

[0174] 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.

[0175] 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 the call history record (CHR) data, alarm data and other data stored in itself, and the problem of the problem object includes the root cause of the problem object.

[0176] CHR data is a file or data in a file that is written every time a specific event occurs in a device or controlled application and records the cause of the specific event. For example, CHR data can be written when an application error occurs and record the cause of the application error. Alternatively, CHR data includes a history of all events that occurred in the program.

[0177] Alarm data is a file or data in a file, which is written to the file each time an alarm event occurs in a device or a controlled application, and records the cause of the alarm event. For example, the cause of the alarm event recorded in the alarm data is power alarm, single board load alarm, etc.

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

[0179] It should be understood that S406 is an optional execution. 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 by network optimization at this time, and there is no way to further determine the root cause of the problem object, so S406 is not executed.

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

[0181] 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, and a detailed description is shown in S402.

[0182] Specifically, the analysis report may optionally include the root cause of the problem object. When 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. When 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.

[0183] 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.

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

[0185] based on Figure 4 The experience problem demarcation method shown in the figure, cross-domain MDAS can demarcate the problem object of the experience problem based on the information of 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 the logic supporting the subsequent optimization closed loop can be implemented by optimizing the problem object and / or solving the root cause of the problem object, so as to achieve the goal of solving or alleviating the experience problem.

[0186] In this application, Figure 3There are two ways for the cross-domain MDAS to obtain the first information. The second way is that the cross-domain MDAS obtains the information of the experience degradation event and the service access volume; then, the cross-domain MDAS obtains the service topology of the experience degradation event based on the obtained information of the experience degradation event, the service access volume, and the managed communication domain and / or communication node, and then obtains the first information. Specific experience problem demarcation methods, such as Figure 5 shown.

[0187] Figure 5 As shown, a method for defining an experience problem is provided in an embodiment of the present application, and the method for defining an experience problem includes the following steps:

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

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

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

[0191] Specifically, AF can exchange data with other NFs to provide business services to terminals. NWDAF can collect data from other NFs and / or similar data collection programs through a subscription or request model to provide QoE data for cross-domain MDAS. QoE data is used to represent the user's subjective perception of the quality and performance of equipment, networks and systems, applications or services, such as latency, traffic, etc.

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

[0193] Among them, the subscription response is used to respond to the subscription request sent by the cross-domain MDAS, including information about experience degradation events and business access volume.

[0194] Specifically, the specific contents of the experience degradation event information and service access volume are 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.

[0195] Table 4

[0196]

[0197] The proportion of poor quality events of each network element in the wireless network domain is used to indicate the statistical situation of the proportion of poor quality events of each network element in the wireless network domain, which can be expressed as a percentage. For example, the proportion of poor quality events of cell A is 56%; the proportion of poor quality events of base station B is 48%.

[0198] Among them, the proportion of poor quality events of each network element in the core network domain is used to indicate the statistical situation of the proportion of poor quality events of each network element in the core network domain, which can be expressed as a percentage. For example, the proportion of poor quality events of UPF1 is 61%; the proportion of poor quality events of AMF1 is 38%.

[0199] 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.

[0200] 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.

[0201] The subscription response includes the information of the experience degradation event in S503 and the service access volume. For detailed description, see S503 and will not be repeated here.

[0202] Specifically, the cross-domain MDAS generates the service topology of the experience degradation event, including: the single-domain MDAS restores the service topology of the single domain according to the service routing policy configuration of the managed network element, and the cross-domain MDAS then splices the service topology of the single domain into a complete service topology. The single-domain MDAS includes the wireless network domain MDAS and / or the core network domain MDAS.

[0203] 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 elements. 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 elements. Subsequently, 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.

[0204] 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.

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

[0206] based on Figure 5 The experience problem delimitation method shown in the figure achieves the business topology of the experience degradation event without relying on the single-domain MDAS to obtain the business topology of the experience degradation event. The business topology of the experience degradation event is generated by the network element range managed by the cross-domain MDAS itself, which reduces the processing complexity of the cross-domain MDAS and improves the efficiency of obtaining the business topology of the experience degradation event. Furthermore, based on the acquired experience degradation event information, business access information, and the generated business topology of the experience degradation event, the cross-domain MDAS delimits the problem object of the experience problem, determines the problem object and the root cause of the problem object, and realizes an optimization closed loop to support subsequent problems.

[0207] 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 a subscription consumer, a notification consumer, a cross-domain MDAS, a single-domain MDAS, a data source, etc., in order to realize the above functions, includes a hardware structure and / or software module 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 in this article, 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 the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0208] The embodiment of the present application can group the functional modules of subscription consumers, notification consumers, cross-domain MDAS, single-domain MDAS, data sources, etc. according to the above 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 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.

[0209] Figure 6 The structure diagram of a communication device 60 is shown, and the communication device 60 can be used to perform the functions of the cross-domain MDAS (or cross-domain MDAS, or cross-domain management data analysis service) involved in the above embodiments. As an implementable manner, Figure 6The communication device 60 shown includes: a processing unit 601, a transceiver unit 602;

[0210] The processing unit 601 is used to obtain the first information, and to define the experience problem based on the first information, and to determine the problem object and the root cause of the problem object. For example, the processing unit 601 can be used to support the communication device 60 to execute S403, S404, S407, or to execute S503, S504, S505, S508.

[0211] The transceiver unit 602 is used 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.

[0212] Among them, the relevant descriptions of the first information, the problem object, the root cause of the problem object, and the analysis report can refer to those described in the above method embodiment.

[0213] Specifically, the above Figure 4 and Figure 5 All relevant contents of each step involved in the illustrated method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here. The communication device 60 is used to execute Figure 4 or Figure 5 The function of the cross-domain MDAS in the experience problem delimiting method shown can achieve the same effect as the above experience problem delimiting method.

[0214] As another possible way to achieve this, Figure 6 The communication device 60 shown includes: a processing module and a communication module. The processing module is used to control and manage the actions 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 to execute S403, S404, S407, or can be used to support the communication device to execute 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 to execute S408, or can be used to support the communication device 60 to execute S509 and communicate with other network entities, such as with Figure 4 and Figure 5 The communication device 60 may also include a storage module for storing program codes and data of the communication device 60.

[0215] Figure 7 The structure diagram of a communication device 70 is shown, and the communication device 70 can be used to perform the functions of the single-domain MDAS (or called single-domain management data analysis service) involved in the above embodiment. As an implementable manner, Figure 7 The communication device 70 shown includes: a processing unit 701, a transceiver unit 702;

[0216] The processing unit 701 is used to obtain second information of a problem object indicating an experience problem, and determine a root cause of the problem object based on the second information. For example, the processing unit 701 can be used to support the communication device 70 to execute SS405 and SS406, or can be used to support the communication device 70 to execute S506 and S507.

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

[0218] 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 referred to as cross-domain MDAS) can refer to those described in the above method embodiment.

[0219] Specifically, the above Figure 4 and Figure 5 All relevant contents of each step involved in the illustrated method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here. The communication device 70 is used to execute Figure 4 or Figure 5 The function of the single-domain MDAS in the experience problem delimitation method shown can therefore achieve the same effect as the above-mentioned experience problem delimitation method.

[0220] As another possible way to achieve this, Figure 7 The communication device 70 shown includes: a processing module and a communication module. The processing module is used to control and manage the actions of the communication device 70. For example, the processing module can integrate the functions of the processing unit 701, and can be used to support the communication device 70 to execute SS405, SS406, or execute S506, S507, and other processes of the technology described in this article. The communication module can integrate the functions of the transceiver unit 702, and can be used to support the communication device 70 to execute S406 or S507 and communicate with other network entities, such as with Figure 4 and Figure 5 The communication device 70 may also include a storage module for storing program codes and data of the communication device 70.

[0221] As mentioned above, the processing module may be a processor or a controller. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the contents disclosed in 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 the like. The communication module may be a transceiver circuit or a communication interface, and the like. 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 embodiments of the present application may be Figure 8 For example, the cross-domain MDAS and single-domain MDAS mentioned above can be used Figure 8 The structure shown may include Figure 8 Parts shown. Figure 8 A schematic diagram of the composition of a communication device 80 provided in an embodiment of the present application is shown as follows: Figure 8 As shown, the communication device 80 may include a processor 801 , a communication line 802 and a communication interface 803 .

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

[0223] 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 functions, such as circuits, devices, or software modules.

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

[0225] The communication interface 803 is used to communicate with other devices or other communication networks. The other communication networks may be Ethernet, a radio access network (RAN), a wireless local area network (WLAN), etc. The communication interface 803 may be a radio frequency module, a transceiver, or any communication device capable of achieving communication. The embodiment of the present application is described by taking the communication interface 803 as a radio frequency module as an example, 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.

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

[0227] 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 compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.

[0228] 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 or program codes or some data, etc. The memory 804 can be located in the communication device 80, or can be located outside the communication device 80, without limitation. The processor 801 is used to execute the instructions stored in the memory 804 to implement the communication method provided in the following embodiments of the present application.

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

[0230] As an optional implementation, the communication device 80 includes multiple processors, for example, Figure 8 In addition to the processor 801, a processor 807 may also be included.

[0231] 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, etc., and the output device 805 is a display screen, a speaker, etc.

[0232] It should be noted that the communication device 80 can 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 Figure 8 In addition, Figure 8 The structure shown in the figure does not constitute a limitation on the communication device, except Figure 8 In addition to the components shown, the communication device may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0233] In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices.

[0234] The embodiment of the present application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be completed by a computer program to instruct the relevant hardware, and the program can be stored in the above computer-readable storage medium. When the program is executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be a terminal of any of the above 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 a terminal. The above computer-readable storage medium can also be an external storage device of the above terminal, such as a plug-in hard disk, a smart memory card (smart media card, SMC), a secure digital (securedigital, SD) card, a flash card (flash card), etc. equipped on the above terminal. Further, the above computer-readable storage medium can also include both the internal storage unit of the above terminal and an external storage device. The above computer-readable storage medium is used to store the above computer program and other programs and data required by the above terminal. The above computer-readable storage medium can also be used to temporarily store data that has been output or is to be output.

[0235] 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 are in compliance with relevant laws and regulations and do 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 authorization of the user, and the same description is not repeated here.

[0236] It should be noted that the terms "first" and "second" in the specification, claims and drawings of the present 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.

[0237] It should be understood that in the present application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means 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 items 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.

[0238] 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 only based on A, but B can also be determined based on A and / or other information. In addition, the "connection" that appears in the embodiments of the present application refers to various connection methods such as direct connection or indirect connection to achieve communication between devices, and the embodiments of the present application do not impose any limitation on this.

[0239] Unless otherwise specified, the "transmission" (transmit / transmission) appearing in the embodiments of the present application refers to bidirectional transmission, including sending and / or receiving actions. 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.

[0240] 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.

[0241] In the several embodiments provided in the present 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 only schematic. For example, the grouping of the modules or units is only a logical function grouping. There may be other grouping methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0242] The units described as separate components may or may not be physically separated, 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.

[0243] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0244] 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, including several instructions to enable a device, such as a single-chip microcomputer, a chip, etc., or a processor (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 USB flash drives, mobile hard drives, ROM, RAM, magnetic disks or optical disks.

[0245] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by any technician familiar with the technical field within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope 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